[Bug 883904] New: Gnome is broken for Intel graphics (20140620 factory snapshot)
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c0 Summary: Gnome is broken for Intel graphics (20140620 factory snapshot) Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: nrickert@ameritech.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 Using factory, and up-to-date with factory repos, as of Jun 23, 2014. I tried login to Gnome this morning. The Gnome session did not fully start. I was left with a blank gray screen. The system has Intel graphics (Haswell). I tried deleting (actually moving) all startup files. Still the same failure. I switch the login GUI from "lightdm" to "gdm". However, "gdm" fails to fully start, leaving me with a blank gray screen. I downloaded the live Gnome snapshot for 20140620, and booted from that (on a USB). I ended up with a blank gray screen. I tried the same live Gnome USB on a different computer (nVidia graphics), and it booted up fine though probably would not have worked very well without the nVidia driver. I then tried the same live Gnome USB on my laptop with Intel Arrandale graphics. I ended up with a blank gray screen. Incidentally, KDE, Icewm and twm all work fine on the system with Intel Haswell. On one of my Gnome tests, I connected locally (with ssh from another box), and ran "top". There did not seem to be anything looping. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c1 Atri Bhattacharya <badshah400@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |badshah400@gmail.com --- Comment #1 from Atri Bhattacharya <badshah400@gmail.com> 2014-06-24 00:35:34 UTC --- Sorry for the "me too" message but I see the same issue seen with openSUSE:13.1 + GNOME:STABLE:3.12 + X11:Xorg packages, so it really does look like a conflict between gdm and intel video driver version 2.99.912. I have since switched my Xserver packages back to the default openSUSE:13.1 version and can log in again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c2 --- Comment #2 from Atri Bhattacharya <badshah400@gmail.com> 2014-07-04 00:37:45 UTC --- Still an issue in Factory snapshot Jun 30. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c3 --- Comment #3 from Atri Bhattacharya <badshah400@gmail.com> 2014-07-04 04:55:42 UTC --- Created an attachment (id=597275) --> (http://bugzilla.novell.com/attachment.cgi?id=597275) /var/log/message file in a tarball (big file) In case it helps, I attach my /var/log/messages file. This line looks interesting and could be the cause of the problem: 2014-07-03T17:31:55.316230-07:00 linux-tda5 /usr/bin/dbus-launch[1167]: libGL error: dlopen /usr/lib64/dri/updates/i965_dri.so failed (/usr/lib64/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory) Indeed, /usr/lib64/dri/updates/i965_dri.so does not exist (after updating to X11:XOrg packages), but /usr/lib64/dri/i965_dri.so does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c4 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |dimstar@opensuse.org InfoProvider| |badshah400@gmail.com --- Comment #4 from Dominique Leuenberger <dimstar@opensuse.org> 2014-07-23 00:21:34 UTC --- (In reply to comment #3)
2014-07-03T17:31:55.316230-07:00 linux-tda5 /usr/bin/dbus-launch[1167]: libGL error: dlopen /usr/lib64/dri/updates/i965_dri.so failed (/usr/lib64/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory)
Sadly, that would be too easy :) Mesa tests first for drivers in /update and then falls back one directory higher.. (even I have similar entries on my system: Jul 22 18:01:40 linux gnome-session[1392]: libGL error: dlopen /usr/lib64/dri/updates/nouveau_dri.so failed (/usr/lib64/dri/updates/nouveau_dri.so: cannot open shared object file: No such file or directory) )
From your log file, though, this sounds more fatal:
2014-07-03T18:31:28.364481-07:00 linux-tda5 xdm[2050]: Starting service gdm<5>Failed to give slave programs access to the display. Trying to proceed. 2014-07-03T18:31:28.466802-07:00 linux-tda5 gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (unknown)(uid=0) (gdm not having access to the display?!) What is the output of: getfacl /dev/dri/card0 ? Is your user member of the 'video' group (this should not be needed nowadays; but worthy a test at least) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c5 Atri Bhattacharya <badshah400@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|badshah400@gmail.com | --- Comment #5 from Atri Bhattacharya <badshah400@gmail.com> 2014-07-23 00:34:22 UTC --- Hi Dominique! It seems I am not a member of the video group:
getfacl /dev/dri/card0 getfacl: Removing leading '/' from absolute path names # file: dev/dri/card0 # owner: root # group: video user::rw- user:badshah:rw- group::rw- mask::rw- other::---
Do you suggest I add myself to the video group and give it a shot with updated XOrg packages (I downgraded these to the stock openSUSE 13.1 versions)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c6 --- Comment #6 from Dominique Leuenberger <dimstar@opensuse.org> 2014-07-23 00:48:30 UTC --- It is worth a try (but the acl gives your user permission as expected, so i don't see this fixing the issue). You say that downgrading the X stack, and nothing else, made the problem go away? Ir so, we should at least cc the x maintainer -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c7 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.de --- Comment #7 from Dominique Leuenberger <dimstar@opensuse.org> 2014-07-23 00:50:20 UTC --- Stefan, This sounds like an intel driver issue.. What do you think? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c8 --- Comment #8 from Atri Bhattacharya <badshah400@gmail.com> 2014-07-23 01:14:17 UTC --- (In reply to comment #6)
It is worth a try (but the acl gives your user permission as expected, so i don't see this fixing the issue).
You say that downgrading the X stack, and nothing else, made the problem go away? Ir so, we should at least cc the x maintainer
glxgears
Yes so it did. Now I updated the X stack to the version from X11:XOrg again, and i can access gdm again, but after logging in several applications (esp gtk3 ones, e.g. gnome-control-center) cause the X-server to crash. In fact even running glxgears fails: libGL error: dlopen /usr/lib64/dri/updates/i965_dri.so failed (/usr/lib64/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory) Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 149 () Minor opcode of failed request: 2 Serial number of failed request: 35 Current serial number in output stream: 36 So most likely it is in fact as issue with the updated intel driver at X11:XOrg. Now to restore the entire X-stack back to stock versions again... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c9 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |X.Org AssignedTo|bnc-team-gnome@forge.provo. |bnc-team-xorg-bugs@forge.pr |novell.com |ovo.novell.com QAContact|qa-bugs@suse.de |xorg-maintainer-bugs@forge. | |provo.novell.com --- Comment #9 from Dominique Leuenberger <dimstar@opensuse.org> 2014-07-24 18:53:05 UTC --- Changing component to X.Org: considering that simply up/downgrading the X-stack triggers it implies that the bug resides in that code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c10 --- Comment #10 from Neil Rickert <nrickert@ameritech.net> 2014-07-24 20:22:22 UTC --- I have just rechecked this, using factory snapshot 20140721. And it now appears to be working. I've tried starting Gnome from "kdm" and from "gdm", and both work. I note that the installed intel driver is xf86-video-intel-2.99.912-1.2 so I am not sure what changed that "fixed" the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883904 https://bugzilla.novell.com/show_bug.cgi?id=883904#c Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com