Gnome-Shell crashes at first login

[xjonquilx]

I had the same problem when I first tried logging in. Also in Live mode it will not let me log in at all.

[stunter]

I still can't log into gnome. I just finished the latest updates and same, same. It bails out with a message saying it ran into a problem. So, instead of just bailing out, I flipped to a terminal, logged in as root and made a copy of the .xsessions-error file. Here the end of it. there were some minor errors before this, but nothing that would seem to stop it (some stuff with AWN and other minor stuff).

I don't see what would kill it.


"usr/share/applications/firefox.desktop'
JS LOG: GNOME Shell started at Sun Oct 09 2011 12:24:14 GMT-0700 (PDT)
JS ERROR: !!! Exception was: Error: Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
JS ERROR: !!! lineNumber = '0'
JS ERROR: !!! fileName = '"gjs_throw"'
JS ERROR: !!! stack = '"("Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files")@gjs_throw:0
([object _private_TelepathyGLib_AccountManager],[object _private_Gio_SimpleAsyncResult])@/usr/share/gnome-shell/js/ui/telepathyClient.js:371
"'
JS ERROR: !!! message = '"Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files"'

(gnome-shell:1516): folks-WARNING **: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus 0x800005 () with a timestamp of 0. This shouldn't happen!

(awn-applet:1573): Wnck-CRITICAL **: wnck_window_is_visible_on_workspace: assertion `WNCK_IS_WORKSPACE (workspace)' failed

(awn-applet:1573): Wnck-CRITICAL **: wnck_window_is_visible_on_workspace: assertion `WNCK_IS_WORKSPACE (workspace)' failed
Do.Universe.Linux.GNOMESpecialLocationsItemSource "GNOME Special Locations" encountered an error in UpdateItems: System.IO.FileNotFoundException: Could not find file "/home/stunter/.gtk-bookmarks".
File name: '/home/stunter/.gtk-bookmarks'
at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] in <filename unknown>:0
at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,Sy stem.IO.FileShare)
at System.IO.File.OpenRead (System.String path) [0x00000] in <filename unknown>:0
at System.IO.StreamReader..ctor (System.String path, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) [0x00000] in <filename unknown>:0
at System.IO.StreamReader..ctor (System.String path) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.IO.StreamReader:.ctor (string)
at Do.Universe.Linux.GNOMESpecialLocationsItemSource+ <ReadBookmarkItems>c__Iterator3.MoveNext () [0x00000] in <filename unknown>:0
at Do.Universe.Linux.GNOMESpecialLocationsItemSource. UpdateItems () [0x00000] in <filename unknown>:0
at Do.Universe.Safe.SafeItemSource.UpdateItems () [0x00000] in <filename unknown>:0 .
Do.Universe.Linux.GNOMESpecialLocationsItemSource "GNOME Special Locations" encountered an error in UpdateItems: System.IO.FileNotFoundException: Could not find file "/home/stunter/.gtk-bookmarks".
File name: '/home/stunter/.gtk-bookmarks'
at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] in <filename unknown>:0
at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,Sy stem.IO.FileShare)
at System.IO.File.OpenRead (System.String path) [0x00000] in <filename unknown>:0
at System.IO.StreamReader..ctor (System.String path, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) [0x00000] in <filename unknown>:0
at System.IO.StreamReader..ctor (System.String path) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.IO.StreamReader:.ctor (string)
at Do.Universe.Linux.GNOMESpecialLocationsItemSource+ <ReadBookmarkItems>c__Iterator3.MoveNext () [0x00000] in <filename unknown>:0
at Do.Universe.Linux.GNOMESpecialLocationsItemSource. UpdateItems () [0x00000] in <filename unknown>:0
at Do.Universe.Safe.SafeItemSource.UpdateItems () [0x00000] in <filename unknown>:0 ."

[stunter]

So, no ideas?

looks like it could be a telepathy Bug?

[DBelton]

I get that same telepathy error, but it doesn't prevent gnome shell from starting up and running.

** Message: applet now removed from the notification area
      JS LOG: GNOME Shell started at Tue Oct 11 2011 22:54:04 GMT-0500 (CDT)
failed to create drawable
    JS ERROR: !!!   Exception was: Error: Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files")@gjs_throw:0
([object _private_TelepathyGLib_AccountManager],[object _private_Gio_SimpleAsyncResult])@/usr/share/gnome-shell/js/ui/telepathyClient.js:371
"'
    JS ERROR: !!!     message = '"Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files"'

(gnome-shell:1506): folks-WARNING **: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
** Message: applet now embedded in the notification area
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"

BTW, does anyone have an idea on how to prevent libsocialweb from establishing a connection with that freakin twitter every time I start up my system? It does it on a random port, so blocking the port is not the answer. I have NO use for that social web crap, and have NO accounts configured, in Fedora, Gnome, or even on twitter. But libsocialweb hits twitter every time I start my machine.

[stunter]

The weird part is, I can get into gnome fine as root. I look at the .xsessions log and it's pretty much identical. There's clearly a telepathy bug, but it doesn't prevent it from running as root. That's why I keep thinking that it's some sort of selinux issue or permission issue.

I also get the pk-gtk-module error, it's just higher up the chain for some reason.

Would it be worthwhile, do ya think, to delete my user account from root and set up a new account?

[DBelton]

You seem to be getting a lot of messages pertaining to Gnome Do in there.

What happens if you uninstall Gnome Do? (If you don't have a lot of custom configs or anything that would make it hard to get it back)

Possibly it could be something conflicting between gnome shell and gnome do since gnome do really wasn't written for gnome shell.

[stunter]

I killed the start up for gnome do and also the avant window navigator I was running. No change, still bails when it's just about up. I'll copy another xsessions-errors and post it when I get home.

[snoze]

I am no longer gnome fan and switched completely to KDE. gnome-shell sucks and will never touch it. New fedora seems like mouth of gnome.. Gnome is a great(best) without gnome shell.

[stunter]

I'd just like to know why it puking. Seems weird.

[rjd1212]

Originally Posted by stunter

I'd just like to know why it puking. Seems weird.

Good question.

Well, all I can say is after 6 installs of the beta release, I get the same issue AFTER I update the gnome-shell.

When this happens, there is no way I can obtain a useful workaround. Getting into a vt is all but impossible and even when I boot into root via init 3 and initiate the startx command, it crashes once again with the same message.

Right now it seems the only workaround is either NOT doing any yum updates while using gnome, or simply running KDE regardless of updating, which is what I'm doing right now

Otherwise, with the exception of the firewall, everything else seems to be working fine

[stunter]

Yea, I'm pretty much the same way. I'm running KDE. I try after every update to log into gnome, but I get the same thing (the frowny computer face is cute but getting old). I again tried to log in, got the crash and flipped over to a terminal and again copied the .xsessions-errors log and I just can't see anything that would cause it to bail. A lot of "gee, this needs to be fixed" stuff, but no critical errors that would stop the bus. And it still works fine loging in as root.

Just seems like this has to be some sort of bizarre permissions or selinux problem.

[AdamW]

there should be a specific smoking gun message in .xsession-errors - something like 'X is respawning too fast' - any time you see the 'fail whale'. the fail whale is the 'something has gone wrong!' screen which doesn't let you do anything but log out. The other one you can get is the 'i'm in fallback mode' screen, which just tells you you're in fallback mode then lets you go ahead and use it. can you say for sure which one you're seeing?

[rjd1212]

Originally Posted by AdamW

there should be a specific smoking gun message in .xsession-errors - something like 'X is respawning too fast' - any time you see the 'fail whale'. the fail whale is the 'something has gone wrong!' screen which doesn't let you do anything but log out. The other one you can get is the 'i'm in fallback mode' screen, which just tells you you're in fallback mode then lets you go ahead and use it. can you say for sure which one you're seeing?

Well AdamW, in my case, I was getting the "fail whale" message. Then alongside that message was a button and another message having to do with unloading certain "gnome extensions" in order to successfully log back on. But it was a repeating loop and didn't seem to unload the problem extension[s]

Unfortunately, I didn't save the . xsessions error log to present here, even though there were no occurrences of "X is respawning too fast" that I could see.

[DBelton]

Just to let everyone here know..

The people that are getting the message Gtk-Message: Failed to load module "pk-gtk-module" in their .xsessions-errors can fix it by installing the PackageKit-gtk3-module package.

yum install PackageKit-gtk3-module