[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#785097: linux-image-4.0.0-1-amd64: Screen flickering on kernel 4.0



On Tue, 23 Jun 2015 21:52:17 +0100 Francesco Negri <francesconegri@gmail.com> wrote:
> This is still a problem on my laptop, an Asus F201E running sid and
> updated regularly.
>
> Changing the session from "Gnome Wayland" to "Gnome" as I mentioned in
> my previous comment was not a permanent fix: the problem re-appeared
> after reboot.
>
> Best workaround I've found so far:
> * boot debian (screen flickers on GDM login screen)
> * login into gnome shell (screen continues to flicker)
> * press the "lock screen" icon (screen continues to flicker on the GDM screen)
> * wait about 1 second and the screen goes black
> * move the pointer: the screen comes back and it's not flickering anymore
>
> I have not done additional research on the root cause but I'm happy to
> provide additional information if useful.
>
> Francesco
>
>
> On Thu, 14 May 2015 10:02:27 +0200 "carnotan@gmail.com"
> <carnotan@gmail.com> wrote:
> > On Thu, 14 May 2015 00:53:49 +0100 Francesco Negri <francesconegri@gmail.com>
> > wrote:
> > > I have the same issue.
> > >
> > > It seems to be related to Wayland, see:
> > > https://bugs.archlinux.org/task/44779
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1199890
> > >
> > > I fixed it on my machine by logging out and selecting "Gnome" instead
> > > of "Gnome Wayland" as the GDM session (little cog icon under your
> > > username). I'm not sure on how to change this setting from a config
> > > file rather than from the GUI.
> > >
> > >
> > Thanks for the info. That should really help the developers to find where
> > is the real problem.
> > I don't have Gnome on my machine. I really don't like it , so it's not even
> > installed. I have KDE,
> > and therefore KDM as session manager. Probably this problem also affeccts
> > KDM.
> >
> > Thanks
> > Iván Lago.
>
>
I'm also still suffering this bug (Toshiba Satellite P750-11W). I've not found any workaround for
it. Only solution is not using kernel 4, so it seems clear to me that the problem lies there.
I will also be more than happy to provide as much feedback as necessary.
Iván Lago

Reply to: