Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25956 - [gnome-shell] crashes when logging in

Attached to Project: Arch Linux
Opened by Tomas M. (eldragon) - Saturday, 10 September 2011, 22:43 GMT
Last edited by Allan McRae (Allan) - Saturday, 17 November 2012, 06:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

gnome-shell crashes when logging in in the following scenario
- NetworkManager is not installed in the system
- Wireless connection established already through netcfg

if i disable the wireless connection or disconnect netcfg stopping its daemon and THEN login, there is no crash. i can then establish a connection and use the desktop normally

im attaching the xsession-error file
   gnome3-nm (2.6 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 17 November 2012, 06:49 GMT
Reason for closing:  Fixed
Comment by Ionut Biru (wonder) - Sunday, 11 September 2011, 05:55 GMT
Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

it means that X crashed
Comment by Tomas M. (eldragon) - Sunday, 11 September 2011, 15:05 GMT
just to add some info. the crash is not a like a regular x crash.

gnome-shell displays the "aw snap" message. Thats why i thought it would be gnome-shell.

i will upload a Xorg log when i get the chance.

Comment by Jan Alexander Steffens (heftig) - Wednesday, 19 October 2011, 15:51 GMT
I'm more interested in the ~/.xsession-errors.

Still an issue?
Comment by Tomas M. (eldragon) - Sunday, 15 January 2012, 21:58 GMT
sorry for the delay in the reply.

i dont reboot that often, and when i do, i have to setup the network manually.

what i uploaded IS the ~/.xsession-errors file. i just renamed it in my debug dir to id it. sorry for the mix up.

this is still an issue (had forgotten all about this till i was hit again today. google pointed me to my own bug report!)

i wonder if there is anything else i can test.

Comment by Tomas M. (eldragon) - Wednesday, 18 January 2012, 18:55 GMT
testing with gnome-shell and mutter 3.2.2, same problem.

i get the oops something went wrong, please logout and login again.

attaching a fresh xsessions-error WHEN FAILED and WHEN LOGGED IN

i can only log in if im not connected to any network, i dont use network manager. i use netcfg to connect.

   xsession-errors_failed (3.2 KiB)
Comment by Tomas M. (eldragon) - Wednesday, 18 January 2012, 18:56 GMT
this is from a successful login (network was brought down before loging in)
   xsession-errors_logged (3.2 KiB)
Comment by Jan Alexander Steffens (heftig) - Wednesday, 18 January 2012, 19:35 GMT
Looks like gnome-settings-daemon hangs or crashes.
Comment by Allan McRae (Allan) - Saturday, 02 June 2012, 12:33 GMT
Status?
Comment by Morris (kabum) - Thursday, 15 November 2012, 00:01 GMT
  • Field changed: Percent Complete (100% → 0%)
Same issue here. But with NetworkManager. If I unplug cable or on other system disable Wifi, then login succeed. So it's fully reproducable on two systems and I could contribute logs and so on.
Comment by Greg (dolby) - Saturday, 17 November 2012, 06:28 GMT
@kabum: please report to bugzilla.gnome.org and paste the link here.
Comment by Morris (kabum) - Saturday, 17 November 2012, 06:46 GMT
For me it's fixed in gnome-shell 3.6.1

Loading...