Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Gnome-shell failed to start after login [solved]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
droide
n00b
n00b


Joined: 27 Jul 2007
Posts: 20

PostPosted: Tue Oct 04, 2011 9:01 am    Post subject: Gnome-shell failed to start after login [solved] Reply with quote

Hello,

I have upgrade gnome 3.0 to 3.2 and I have some problems.

My first problem is with GDM. GDM failed to start.
To solve this probleme, I emerge GDM without gnome-shell use flag :

Code:
     Available versions:  2.20.11 (~)2.20.11-r1 [M](~)2.32.1 [M](~)2.32.1-r1 {M}(~)3.0.4-r2[1] {M}(~)3.2.0[1] {accessibility afs branding +consolekit debug dmx elibc_glibc fprint gnome-keyring +gnome-shell +introspection ipv6 pam remote selinux smartcard tcpd test xinerama +xklavier}
     Installed versions:  3.2.0[1](17:07:22 03/10/2011)(consolekit elibc_glibc gnome-keyring introspection ipv6 tcpd xklavier -accessibility -debug -fprint -gnome-shell -selinux -smartcard -test -xinerama)
     Homepage:            http://www.gnome.org/projects/gdm/
     Description:         GNOME Display Manager


My second problem is after login.
GDM show me the login form, I select my user and enter my password. Gnome-shell show me his error-screen like this :

http://25.media.tumblr.com/tumblr_llb0ez6GrO1qzi8iao1_500.jpg

I try to delete the .config, .local, .gnome2 folders to reset my settings and the problem doesn't change.

This is my .xsession-error :

Code:
/etc/gdm/Xsession: Beginning session setup...
which: no keychain in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/opt/stuffit/bin:/opt/android-sdk-update-manager/tools:/opt/android-sdk-update-manager/platform-tools:/usr/lib64/subversion/bin:/usr/games/bin)
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session
gnome-session[4559]: WARNING: Could not parse desktop file /home/droide/.config/autostart/xfce4-settings-helper-autostart.desktop: Le fichier de clés n'a pas de clé « Name »
gnome-session[4559]: WARNING: could not read /home/droide/.config/autostart/xfce4-settings-helper-autostart.desktop
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
GNOME_KEYRING_CONTROL=/tmp/keyring-44LUmh
SSH_AUTH_SOCK=/tmp/keyring-44LUmh/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-44LUmh
SSH_AUTH_SOCK=/tmp/keyring-44LUmh/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-44LUmh
SSH_AUTH_SOCK=/tmp/keyring-44LUmh/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-44LUmh
SSH_AUTH_SOCK=/tmp/keyring-44LUmh/ssh
GPG_AGENT_INFO=/tmp/keyring-44LUmh/gpg:0:1

(gnome-settings-daemon:4583): power-plugin-WARNING **: Unable to start power manager: Could not set DPMS timeouts

(gnome-settings-daemon:4583): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/home/droide/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/droide/.local/share/tracker/tracker-miner-fs.log'
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/home/droide/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/droide/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/droide/.local/share/tracker/tracker-store.log'
** Message: applet now removed from the notification area
/usr/bin/gnome-shell: symbol lookup error: /usr/lib64/gio/modules/libgiognomeproxy.so: undefined symbol: g_mutex_new
Failed to play sound: File or data not found

(nm-applet:4632): libnotify-WARNING **: Failed to connect to proxy

** (nm-applet:4632): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.

** (nm-applet:4632): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.

** (nm-applet:4632): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: Aucun résultat)
/usr/bin/gnome-shell: symbol lookup error: /usr/lib64/gio/modules/libgiognomeproxy.so: undefined symbol: g_mutex_new
gnome-session[4559]: WARNING: App 'gnome-shell.desktop' respawning too quickly

(gnome-settings-daemon:4583): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: Active session changed

** (gnome-user-share:4640): WARNING **: Couldn't request the name: Unable to find session for cookie

(nm-applet:4632): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.


(gdu-notification-daemon:4633): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.


(gnome-screensaver:4649): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Complété'

(tracker-miner-fs:4634): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: La connexion est fermée

(tracker-miner-fs:4634): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: La connexion est fermée

(tracker-miner-fs:4634): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.gtk.Private.RemoteVolumeMonitor',sender='org.gtk.Private.GPhoto2VolumeMonitor',': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(tracker-miner-fs:4634): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.gtk.Private.GPhoto2VolumeMonitor'': org.freedesktop.DBus.Error.Disconnected: Connection is closed

(tracker-miner-fs:4634): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.gtk.Private.RemoteVolumeMonitor',sender='org.gtk.Private.GduVolumeMonitor',': org.freedesktop.DBus.Error.Disconnected: Connection is closed

(tracker-miner-fs:4634): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.gtk.Private.GduVolumeMonitor'': org.freedesktop.DBus.Error.Disconnected: Connection is closed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

OK


Received signal:15->'Complété'
OK

(evolution-alarm-notify:4651): libecal-DEBUG: GDBus connection is closed, remote peer vanished: Underlying GIOStream returned 0 bytes on an async read
(evolution-alarm-notify:4651): libecal-DEBUG: e-cal-client.c:359: ECalClient GDBus connection is closed, remote peer vanished: Underlying GIOStream returned 0 bytes on an async read
(evolution-alarm-notify:4651): libecal-DEBUG: e-cal-client.c:359: ECalClient GDBus connection is closed, remote peer vanished: Underlying GIOStream returned 0 bytes on an async read
(evolution-alarm-notify:4651): libecal-DEBUG: e-cal-client.c:359: ECalClient GDBus connection is closed, remote peer vanished: Underlying GIOStream returned 0 bytes on an async read
(evolution-alarm-notify:4651): libecal-DEBUG: e-cal-client.c:359: ECalClient GDBus connection is closed, remote peer vanished: Underlying GIOStream returned 0 bytes on an async read
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.


Help me please.
_________________
http://www.waccabac.com/ ( Hébergement Web Professionnel )


Last edited by droide on Wed Oct 05, 2011 7:42 am; edited 1 time in total
Back to top
View user's profile Send private message
tetromino
Retired Dev
Retired Dev


Joined: 02 Dec 2003
Posts: 215

PostPosted: Tue Oct 04, 2011 9:43 am    Post subject: Reply with quote

Does dmesg contain many entries like "gnome-shell .... segfault at 0 ip"?

If so, it would mean that gnome-shell is segfaulting immediately after starting.

The first thing you should probably check is for problems with video drivers, whether your user is in the "video" group, etc.

Another thing to do is to rebuild gnome-shell, and gjs, clutter and cogl with debug symbols (see http://www.gentoo.org/proj/en/qa/backtraces.xml), then enable core dumps ("ulimit -c unlimited") and use gdb to analyze the core file to get a backtrace of the crashed gnome-shell process.

As a temporary workaround, you can force gnome to start in fallback mode. Simply run "gsettings set org.gnome.desktop.session session-name gnome-fallback" (if you are doing this from the console or over ssh, you will need to run "dbus-launch gsettings set org.gnome.desktop.session session-name gnome-fallback").
Back to top
View user's profile Send private message
droide
n00b
n00b


Joined: 27 Jul 2007
Posts: 20

PostPosted: Tue Oct 04, 2011 10:28 am    Post subject: Reply with quote

Thank for the response.

I had my user to video group and I re-emerge nvidia-drivers.

I have segfaulting in dmegs :

Code:
[ 4829.592704] gnome-settings-[26569]: segfault at 7f47fc4b3c80 ip 00007f47fc4b3c80 sp 00007fffbbb82de8 error 14 in libcanberra.so.0.2.5[7f47fcdb0000+e000]
[ 4918.075424] gnome-settings-[26970]: segfault at 7f4e6f703c80 ip 00007f4e6f703c80 sp 00007ffffd21dbe8 error 14
[ 5135.332196] gnome-settings-[17423]: segfault at 7f39209d2c80 ip 00007f39209d2c80 sp 00007fff945cb798 error 14 in libcanberra.so.0.2.5[7f39212cf000+e000]
[ 5545.179501] gnome-settings-[21327]: segfault at 7f3bdd856c80 ip 00007f3bdd856c80 sp 00007fff5c94bc48 error 14 in libcanberra.so.0.2.5[7f3bde153000+e000]


So, with the fallback parameter, gnome boot ! :)

After these works, gnome doesn't start in normal mode...
_________________
http://www.waccabac.com/ ( Hébergement Web Professionnel )
Back to top
View user's profile Send private message
misterjack
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1603
Location: Germany -> Saxony -> Leipzig

PostPosted: Tue Oct 04, 2011 9:30 pm    Post subject: Reply with quote

same prob here. now working with nouveau, but this shit is very slow :)
_________________
„Meine Meinung steht fest! Bitte verwirren Sie mich nicht mit Tatsachen.“
Back to top
View user's profile Send private message
tetromino
Retired Dev
Retired Dev


Joined: 02 Dec 2003
Posts: 215

PostPosted: Tue Oct 04, 2011 10:47 pm    Post subject: Reply with quote

If you had trouble with gdm-3.2 crashing on a system nvidia-drivers, try emerging gdm-3.2.0-r1 (just added to the overlay).
Back to top
View user's profile Send private message
ChrisJumper
Advocate
Advocate


Joined: 12 Mar 2005
Posts: 2220
Location: Germany

PostPosted: Tue Oct 04, 2011 11:28 pm    Post subject: Reply with quote

Quote:
usr/bin/gnome-shell: symbol lookup error: /usr/lib64/gio/modules/libgiognomeproxy.so: undefined symbol: g_mutex_new
gnome-session[4559]: WARNING: App 'gnome-shell.desktop' respawning too quickly


If you got an error like this, do something like that:

Code:
equery b  /usr/lib64/gio/modules/libgiognomeproy.so
* Searching for /usr/lib64/gio/modules/libgiognomeproxy.so ...
net-libs/glib-networking-2.30.0 (/usr/lib64/gio/modules/libgiognomeproxy.so)


And if you now rebuild glib-networking-2.30.0, you will got another errormessage.

I got this done after many times of rebooting, reread my .xsession-errors and had to fix some libraries that are not fixed by lafixer --justfixid. So that is what i had to done:

Code:
# cd /usr/lib64/
ln -s libecal-1.2.so.10.2.2  libecal-1.2.so.8
ln -s libedataserverui-3.0.so libedataserverui-3.0.so.1
ln -s libedataserverui-3.0.so.1 libedataserverui-3.0.so
ln -s libedataserverui-3.0.so libedataserverui-3.0.so.0
ln -s libebook-1.2.so.12.3.1 libebook-1.2.so.10
ln -s libcamel-1.2.so.29.0.0 libcamel-1.2.so.23
ln -s libedataserver-1.2.so.15.0.0 libedataserver-1.2.so.14


And i had often use the "equery b" command and recompile that files that still hat the g_mutex errors.

Now i got some errors fixed and i am sure that my gnome will launch fine with the x11-drivers/xf86-video-nouveau dirvers, but still will not use them. With the proprietary nvidia drivers it seems that gome 3.2. would not launch.

Or did someone know how to disable the 3d render effects?

regards,

chris
Back to top
View user's profile Send private message
tetromino
Retired Dev
Retired Dev


Joined: 02 Dec 2003
Posts: 215

PostPosted: Wed Oct 05, 2011 4:30 am    Post subject: Reply with quote

ChrisJumper wrote:
ln -s libebook-1.2.so.12.3.1 libebook-1.2.so.10
ln -s libcamel-1.2.so.29.0.0 libcamel-1.2.so.23
ln -s libedataserver-1.2.so.15.0.0 libedataserver-1.2.so.14

...
...
...

I must apologize, but there is really no polite way of expressing my reaction to this post.

ChrisJumper, the libraries that you are symlinking together are incompatible. If these commands are really the sorts of things that you inflict on your system, then by now it is probably quite broken.
Back to top
View user's profile Send private message
droide
n00b
n00b


Joined: 27 Jul 2007
Posts: 20

PostPosted: Wed Oct 05, 2011 7:41 am    Post subject: Reply with quote

tetromino wrote:
If you had trouble with gdm-3.2 crashing on a system nvidia-drivers, try emerging gdm-3.2.0-r1 (just added to the overlay).


Thanks ! This update solve my problem ! I'm happy :lol:

Thanks all !
_________________
http://www.waccabac.com/ ( Hébergement Web Professionnel )
Back to top
View user's profile Send private message
ChrisJumper
Advocate
Advocate


Joined: 12 Mar 2005
Posts: 2220
Location: Germany

PostPosted: Wed Oct 05, 2011 11:21 am    Post subject: Reply with quote

:oops:

tetromino, i post this really late in the morning, and got sigh of compiling gnome3. These linking was just a try to get rid of some errors. So i removed them today, sync the overlay, rebuild gnome-settings-daemon, evolution-data-server, gnome-shell and.. it did not work. Surly there is some 9999 packages..
Back to top
View user's profile Send private message
misterjack
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1603
Location: Germany -> Saxony -> Leipzig

PostPosted: Wed Oct 05, 2011 5:57 pm    Post subject: Reply with quote

droide wrote:
tetromino wrote:
try emerging gdm-3.2.0-r1.

This update solve my problem


same here, nice
_________________
„Meine Meinung steht fest! Bitte verwirren Sie mich nicht mit Tatsachen.“
Back to top
View user's profile Send private message
Thistled
Guru
Guru


Joined: 06 Jan 2011
Posts: 548
Location: Scotland

PostPosted: Wed Oct 12, 2011 12:28 pm    Post subject: Reply with quote

It's the same for me, but none of the above has fixed my problem.
The shell is broken it seems, and I can only log in using fallback.
When I try to log into the shell, I experience several segfaults. A different one each time. :?

Code:
Oct 12 12:44:53 pig kernel: [36472.713368] gnome-settings-[23857]: segfault at b240be10 ip b240be10 sp bf8ecc1c error 4 in libpulse-mainloop-glib.so.0.0.4[b24e5000+3000]
Oct 12 12:44:55 pig gnome-session[23825]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal


I have built glib many times now.

Code:
Oct 12 12:48:08 pig gnome-session[4164]: WARNING: Application 'gnome-shell.desktop' killed by signal
Oct 12 12:48:16 pig kernel: [  142.334174] gnome-settings-[4454]: segfault at b22c6e10 ip b22c6e10 sp bfc61b2c error 4 in user[b2331000+4000]
Oct 12 12:48:16 pig gnome-session[4164]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal


Dunno what it means by "user"

Code:
Oct 12 12:52:44 pig gnome-keyring-daemon[8428]: couldn't access conrol socket: /tmp/keyring-GqhfcY/control: No such file or directory
Oct 12 12:52:44 pig gnome-keyring-daemon[8429]: couldn't access conrol socket: /tmp/keyring-GqhfcY/control: No such file or directory
Oct 12 12:52:44 pig gnome-keyring-daemon[8432]: couldn't access conrol socket: /tmp/keyring-GqhfcY/control: No such file or directory
Oct 12 12:52:44 pig gnome-keyring-daemon[8435]: couldn't access conrol socket: /tmp/keyring-GqhfcY/control: No such file or directory
Oct 12 12:52:44 pig kernel: [  410.540984] gnome-settings-[8431]: segfault at 411 ip b706baee sp bf964338 error 6 in libc-2.13.so[b6ffb000+159000]
Oct 12 12:52:44 pig gnome-session[8400]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal


Well, I am stuck with glibc-2.13-r4 and I can't downgrade. (as we all know what that does)

Code:
Oct 12 12:53:59 pig kernel: [  484.848730] gnome-shell[9643] general protection ip:b6746884 sp:bf8b9114 error:0 in libmozjs185.so.1.0.0[b6709000+2f1000]
Oct 12 12:53:59 pig polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session2 (system bus name :1.47, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8) (disconnected from bus)
Oct 12 12:53:59 pig gnome-session[9564]: WARNING: Application 'gnome-shell.desktop' killed by signal
Oct 12 12:54:00 pig polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session2 (system bus name :1.51 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
Oct 12 12:54:01 pig kernel: [  486.998489] gnome-shell[9763] general protection ip:b66fa884 sp:bff15a14 error:0 in libmozjs185.so.1.0.0[b66bd000+2f1000]
Oct 12 12:54:01 pig polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session2 (system bus name :1.51, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8) (disconnected from bus)
Oct 12 12:54:01 pig gnome-session[9564]: WARNING: Application 'gnome-shell.desktop' killed by signal
Oct 12 12:54:01 pig gnome-session[9564]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Oct 12 12:54:02 pig kernel: [  488.668243] gnome-settings-[9595]: segfault at b2428e10 ip b2428e10 sp bfa5c7fc error 4 in user[b24e9000+4000]
Oct 12 12:54:03 pig gnome-session[9564]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal


I nearly always see the "gnome-shell" "general protection" error which seems to be caused by xulrunner, as libmozjs.185.so is linked to that. I have rebuilt xulrunner-2.0.1-r1 and it still happens.

I get the feeling someone is going to say it is because I am using the dreaded glibc-2.13-r4

The most frustrating thing of all, I have been using the shell for months, without a problem, and now this, thanks Gnome.
_________________
Whatever you do, do it properly!
Back to top
View user's profile Send private message
misterjack
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1603
Location: Germany -> Saxony -> Leipzig

PostPosted: Wed Oct 12, 2011 2:04 pm    Post subject: Reply with quote

you have a problem with gnome-settings-daemon, which segfaults. this is another problem, you should open a new thread for this. gnome-shell needs the settings-daemon to start
_________________
„Meine Meinung steht fest! Bitte verwirren Sie mich nicht mit Tatsachen.“
Back to top
View user's profile Send private message
Thistled
Guru
Guru


Joined: 06 Jan 2011
Posts: 548
Location: Scotland

PostPosted: Wed Oct 12, 2011 2:06 pm    Post subject: Reply with quote

Cool. Thanks misterjack.

I've recompiled that to, but to no avail.

Will open a new thread.
_________________
Whatever you do, do it properly!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum