Summary: | =gnome-base/gnome-shell-3.10.4-r1 stabilization request (gnome-base/gnome-shell-3.10.4 fails to link with libgnome-bluetooth-applet.so with ld.gold, causes gdm to show only mouse cursor) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amigadave |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugzilla.gnome.org/show_bug.cgi?id=726435 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gdm.log
Xorg.0.log gdm.log lightdm-root.log lightdm-jlec.log |
Description
Justin Lecher (RETIRED)
2014-03-09 07:42:11 UTC
Created attachment 372152 [details]
gdm.log
journalctl -u gdm -b > gdm.log
Created attachment 372154 [details]
Xorg.0.log
Xorg.0.log
logs seems normal to me. Do you see anything interesting when running "systemctl restart gdm" in journalctl -e output? (not filtering for "gdm"). Also, please try to install, for example, lightdm and try to login in your gnome-shell session to confirm it works Also, do you only see mouse cursor or also the clock at the top? Apart of that, I thought CFLAGS like -ftracer -frecord-gcc-switches were a bit risky for system-wide usage :/ Another thing, is this reproducible when gdm is started by systemd directly while booting at first time? (In reply to Pacho Ramos from comment #3) > logs seems normal to me. Do you see anything interesting when running > "systemctl restart gdm" in journalctl -e output? (not filtering for "gdm"). > Also, please try to install, for example, lightdm and try to login in your > gnome-shell session to confirm it works I will check that. (In reply to Pacho Ramos from comment #4) > Also, do you only see mouse cursor or also the clock at the top? Apart of > that, I thought CFLAGS like -ftracer -frecord-gcc-switches were a bit risky > for system-wide usage :/ -frecord-gcc-switches is perfectly fine. And I never had problems with -ftracer too. > > Another thing, is this reproducible when gdm is started by systemd directly > while booting at first time? It's the same when restarting gdm. Created attachment 372156 [details]
gdm.log
complete journalctl of gdm restart
(In reply to Pacho Ramos from comment #4) > Also, do you only see mouse cursor or also the clock at the top? It's only the mouse. (In reply to Justin Lecher from comment #6) [...] > > Another thing, is this reproducible when gdm is started by systemd directly > > while booting at first time? > > It's the same when restarting gdm. Then, it fails in the same way even on fresh boot without you didn't even logged in in a console or so? OK (In reply to Justin Lecher from comment #8) > (In reply to Pacho Ramos from comment #4) > > Also, do you only see mouse cursor or also the clock at the top? > > It's only the mouse. Uh, this is a new "kind of issue" for me then. Did you try with lightdm+gnome-shell to confirm you are able to login in? You can also try this: # systemctl stop gdm # pkill -u gdm (and ensure everything from gdm user is killed) # gdm In logs I see crashes from Xorg: Mar 09 09:12:44 leo.jlec.de gdm[2204]: GdmSimpleSlave: Started X server Mar 09 09:12:44 leo.jlec.de abrt[2213]: Can't open file '/etc/system-release': No such file or directory Mar 09 09:12:44 leo.jlec.de abrt[2213]: Saved core dump of pid 2100 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2014-03-09-09:12:44-2100 (22884352 bytes) Mar 09 09:12:44 leo.jlec.de abrtd[564]: Directory 'ccpp-2014-03-09-09:12:44-2100' creation detected Mar 09 09:12:44 leo.jlec.de abrtd[564]: Lock file '/var/spool/abrt/ccpp-2014-02-25-20:37:40-31311/.lock' is locked by process 2213 Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmCommon: process (pid:2100) done (signal:6) Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmServer: Server died Mar 09 09:12:44 leo.jlec.de gdm[2077]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmSlave: Stopping slave Mar 09 09:12:44 leo.jlec.de gdm[2077]: Slave finished This is neither normal: Mar 09 09:12:45 leo.jlec.de /usr/bin/dbus-launch[2227]: Window manager warning: Log level 16: Failed to load shared library 'libgnome-bluetooth-applet.so.0' referenced by the typelib: libgnome-bluetooth-applet.so.0: cannot open shared object file: No such file or directory I guess you did revdep-rebuild ans similar? (In reply to Pacho Ramos from comment #9) > Then, it fails in the same way even on fresh boot without you didn't even > logged in in a console or so? OK In any combination it doesn't work. > Uh, this is a new "kind of issue" for me then. Did you try with > lightdm+gnome-shell to confirm you are able to login in? lightdm+gnome-shell doesn't work either. Even with a fresh account. > > You can also try this: > # systemctl stop gdm > # pkill -u gdm (and ensure everything from gdm user is killed) > # gdm > Same issue. > In logs I see crashes from Xorg: > Mar 09 09:12:44 leo.jlec.de gdm[2204]: GdmSimpleSlave: Started X server > Mar 09 09:12:44 leo.jlec.de abrt[2213]: Can't open file > '/etc/system-release': No such file or directory > Mar 09 09:12:44 leo.jlec.de abrt[2213]: Saved core dump of pid 2100 > (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2014-03-09-09:12:44-2100 (22884352 > bytes) > Mar 09 09:12:44 leo.jlec.de abrtd[564]: Directory > 'ccpp-2014-03-09-09:12:44-2100' creation detected > Mar 09 09:12:44 leo.jlec.de abrtd[564]: Lock file > '/var/spool/abrt/ccpp-2014-02-25-20:37:40-31311/.lock' is locked by process > 2213 > Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmCommon: process (pid:2100) done > (signal:6) > Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmServer: Server died > Mar 09 09:12:44 leo.jlec.de gdm[2077]: GLib-GObject: g_object_unref: > assertion 'object->ref_count > 0' failed > Mar 09 09:12:44 leo.jlec.de gdm[2077]: GdmSlave: Stopping slave > Mar 09 09:12:44 leo.jlec.de gdm[2077]: Slave finished > > This is neither normal: > Mar 09 09:12:45 leo.jlec.de /usr/bin/dbus-launch[2227]: Window manager > warning: Log level 16: Failed to load shared library > 'libgnome-bluetooth-applet.so.0' referenced by the typelib: > libgnome-bluetooth-applet.so.0: cannot open shared object file: No such file > or directory > > I guess you did revdep-rebuild ans similar? Sure and I manually rebuilt bluez and net-wireless/gnome-bluetooth If it doesn't work the problem is more important than gdm :| Could you try to use lightdm+icewm (or any other WM) to verify your 3D is working ok? (games, glxinfo | grep Direct...) I just checked nvidia vs nouveau w/o success. Will try icevm now Tested icewm and it works Detected OpenGL version 2.0 or greater. Shaders available. Detected GLSL version 1.30. OpenGL graphics engine: GL_VENDOR: nouveau GL_RENDERER: Gallium 0.4 on NVE6 GL_VERSION: 3.0 Mesa 10.1.0 Detected 8 CPU cores. Enabled multithreaded rendering. I don't know what is occurring then. Are you running systemd-210 or 208? (208 works ok for me, I haven't yet tried 210) Also, try login in on gnome and look at journalctl output while it is "black" on a console as root and on other as the user you are login in. Also try to login as root on gnome to discard it's some kind of permissions issue. Also, I guess you get exactly the same issue with nvidia and nouveau? (In reply to Pacho Ramos from comment #15) > Also, I guess you get exactly the same issue with nvidia and nouveau? yes. Created attachment 372190 [details]
lightdm-root.log
journalctl log from root
Created attachment 372192 [details]
lightdm-jlec.log
journalctl from jlec
(In reply to Pacho Ramos from comment #14) > I don't know what is occurring then. Are you running systemd-210 or 208? > (208 works ok for me, I haven't yet tried 210) Same with both versions. I am having this issue since 3 weeks or so. Always ith all package updated to latest ~arch > > Also, try login in on gnome and look at journalctl output while it is > "black" on a console as root and on other as the user you are login in. Also > try to login as root on gnome to discard it's some kind of permissions issue. root can't login either. Logs will be attached soon Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Window manager warning: Log level 16: Failed to load shared library 'libgnome-bluetooth-applet.so.0' referenced by the typelib: libgnome-bluetooth-applet.so.0: cannot open shared object file: No such file or directory Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: (gnome-shell:3486): Gjs-WARNING **: JS ERROR: Exception in callback for signal: sessions-loaded: Error: Unsupported type void, deriving from fundamental void Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Indicator<._init@/usr/share/gnome-shell/js/ui/status/bluetooth.js:35 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _Base._construct@/usr/share/gjs-1.0/lang.js:154 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: AggregateMenu<._init@/usr/share/gnome-shell/js/ui/panel.js:819 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _Base._construct@/usr/share/gjs-1.0/lang.js:154 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Panel<._ensureIndicator@/usr/share/gnome-shell/js/ui/panel.js:1106 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Panel<._updateBox@/usr/share/gnome-shell/js/ui/panel.js:1117 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Panel<._updatePanel@/usr/share/gnome-shell/js/ui/panel.js:1069 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Panel<._init@/usr/share/gnome-shell/js/ui/panel.js:913 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: wrapper@/usr/share/gjs-1.0/lang.js:213 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _Base._construct@/usr/share/gjs-1.0/lang.js:154 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _initializeUI@/usr/share/gnome-shell/js/ui/main.js:173 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _sessionsLoaded@/usr/share/gnome-shell/js/ui/main.js:122 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: _emit@/usr/share/gjs-1.0/signals.js:124 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: SessionMode<.init/<@/usr/share/gnome-shell/js/ui/sessionMode.js:166 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: done@/usr/share/gnome-shell/js/misc/fileUtils.js:33 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: @/usr/share/gnome-shell/js/misc/fileUtils.js:51 Mar 09 12:43:39 leo.jlec.de gnome-session[3390]: onNextFileComplete@/usr/share/gnome-shell/js/misc/fileUtils.js:21 Not sure what is still wrong with your bluetooth stuff :S I have it at: $ equery b /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 * Searching for /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 ... net-wireless/gnome-bluetooth-3.10.0 (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 -> libgnome-bluetooth-applet.so.0.0.0) net-wireless/gnome-bluetooth-3.10.0 (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0.0.0) Please check it and ensure you run "emerge @preserved-rebuild" to drop old libs I also see some traces are being collected by abrt, maybe you can run "abrt-gui" as user jlec to look at them (I would look to the gnome-shell trace if any) (In reply to Pacho Ramos from comment #20) > Not sure what is still wrong with your bluetooth stuff :S > > I have it at: > $ equery b /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 > * Searching for /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 > ... > net-wireless/gnome-bluetooth-3.10.0 > (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 -> > libgnome-bluetooth-applet.so.0.0.0) > net-wireless/gnome-bluetooth-3.10.0 > (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0.0.0) same here # equery b /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 * Searching for /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 ... net-wireless/gnome-bluetooth-3.10.0 (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 -> libgnome-bluetooth-applet.so.0.0.0) net-wireless/gnome-bluetooth-3.10.0 (/usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0.0.0) > > Please check it and ensure you run "emerge @preserved-rebuild" to drop old > libs did that. But nothing changed. (In reply to Pacho Ramos from comment #21) > I also see some traces are being collected by abrt, maybe you can run > "abrt-gui" as user jlec to look at them (I would look to the gnome-shell > trace if any) Nothing interesting here. And not reproducible. I just deleted everything and repeated the login procedure, but didn't got any abrt results. I guess rebuilding gnome-bluetooth-3.10.0, spidermonkey-17.0.0-r3, gjs-1.38.1 and gnome-shell-3.10.4 don't help? :S Please ensure the libs had the proper permissions: $ ls -l /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0* lrwxrwxrwx 1 root root 34 feb 9 01:36 /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0 -> libgnome-bluetooth-applet.so.0.0.0 -rwxr-xr-x 1 root root 31568 feb 9 01:36 /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0.0.0 Maybe they can't be loaded for some strange reason, but I don't know how to test that I found the reason, gnome-shell + ld.gold. But this means somewhere gnome-shell has errors in the way it gets linked. Indeed. When building with ld.bfd: # scanelf -n /usr/bin/gnome-shell | grep bluetooth || echo "not found" ET_EXEC libgnome-shell.so,libgnome-shell-js.so,libatk-bridge-2.0.so.0,libgjs.so.0,libgirepository-1.0.so.1,libtelepathy-glib.so.0,libmutter.so.0,libgtk-3.so.0,libclutter-1.0.so.0,libcogl-pango.so.15,libgio-2.0.so.0,libpangocairo-1.0.so.0,libgobject-2.0.so.0,libglib-2.0.so.0,libgnome-bluetooth-applet.so.0,libpthread.so.0,libc.so.6 /usr/bin/gnome-shell But after rebuilding with ld.gold: # scanelf -n /usr/bin/gnome-shell | grep bluetooth || echo "not found" not found Wrote an obvious patch and submitted it upstream at https://bugzilla.gnome.org/show_bug.cgi?id=726435 +*gnome-shell-3.10.4-r1 (15 Mar 2014) + + 15 Mar 2014; Alexandre Rostovtsev <tetromino@gentoo.org> + +gnome-shell-3.10.4-r1.ebuild, + +files/gnome-shell-3.10.4-bluetooth-gold.patch, + +files/gnome-shell-3.10.4-fix-background-manager.patch: + Fix silent linking failure to gnome-bluetooth when using ld.gold (bug + #503952, thanks to Justin Lecher) and background corruption with multiple + minitors (bug #504530, thanks to Chandler Paul). Pacho, since leaving users with a blank screen in gdm is rather bad, I think we should stabilize this quickly. Since 3.10.4 was stabilized only a week ago, and leaving users who are using ld.gold with a blank screen in gdm is a rather bad bug, I suggest we ought to get 3.10.4-r1 stable quickly. So please test and stabilize =gnome-base/gnome-shell-3.10.4-r1 for amd64 and x86. Well, ld.gold is not the default for system wide usage, but I have no problem with fast stabilizing it either ;) x86 stable amd64 stable |