FS#35009 - [gnome-shell] crashes on user switch with int3

Attached to Project: Arch Linux
Opened by Artiom Molchanov (artiom) - Sunday, 28 April 2013, 08:02 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 05 July 2015, 15:08 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

When I switch a user the gnome-shell in previous session is crashed. It worked well with gnome 3.6 and started just after the recent upgrade to 3.8.
I found that gnome-screensaver is still on 3.6 version and usually it is activated after a session switch.
Can be also related to https://bugs.archlinux.org/task/32594


Additional info:
* package version(s)

gnome-shell 3.8.1-1
gnome-shell-extensions 3.8.1-1
gnome-screensaver 3.6.1-3
nvidia 313.30-4
nvidia-libgl 313.30-2
nvidia-utils 313.30-2
opencl-nvidia 313.30-2

xorg-server 1.14.1-1
xorg-server-common 1.14.1-1
xorg-server-utils 7.6-3

* config and/or log files etc.

Apr 27 16:55:41 localhost kernel: [ 9523.984960] traps: gnome-shell[14072] trap int3 ip:7f6c56972ead sp:7fff09b9afe0 error:0
Apr 27 16:55:41 localhost /etc/gdm/Xsession[13976]: gnome-session[13976]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Apr 27 16:55:41 localhost gnome-session[13976]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Apr 27 16:55:43 localhost /etc/gdm/Xsession[13976]: (gnome-shell:12318): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
Apr 27 16:55:44 localhost /usr/bin/dbus-launch[12305]: (gnome-shell:12345): Gvc-WARNING **: Failed to connect context: OK
Apr 27 16:55:48 localhost /etc/gdm/Xsession[13976]: (gnome-shell:12318): Cogl-ERROR **: Failed to create an OpenGL framebuffer object
Apr 27 16:55:48 localhost kernel: [ 9531.392434] traps: gnome-shell[12318] trap int3 ip:7f63dfa3aead sp:7fff13d02820 error:0
Apr 27 16:55:49 localhost /etc/gdm/Xsession[13976]: gnome-session[13976]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Apr 27 16:55:49 localhost /etc/gdm/Xsession[13976]: gnome-session[13976]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Apr 27 16:55:49 localhost gnome-session[13976]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Apr 27 16:55:49 localhost gnome-session[13976]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Apr 27 17:00:41 localhost /etc/gdm/Xsession[12463]: (gnome-shell:12542): St-CRITICAL **: setup_framebuffers: assertion `width > 0' failed
Apr 27 17:00:41 localhost /etc/gdm/Xsession[12463]: (gnome-shell:12542): St-CRITICAL **: setup_framebuffers: assertion `width > 0' failed

Steps to reproduce:
1. Open a session.
2. From the menu select "Switch user".
3. Go back to the previous session.
4. PROFIT
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 05 July 2015, 15:08 GMT
Reason for closing:  No response
Comment by Artiom Molchanov (artiom) - Sunday, 28 April 2013, 08:13 GMT
In steps to reproduce I forget to precise that in the step 2 you need to open another session. If you switch back just from GDM screen it don't crash.
I have no custom gnome-shell extensions only those from package. Anyway it crashes even with all extensions disabled.
Comment by Jason Russell (jrussell) - Sunday, 28 April 2013, 10:14 GMT
Disable extensions and remove gnome-screensaver 3.6, see what happens
Comment by Artiom Molchanov (artiom) - Monday, 29 April 2013, 08:34 GMT
The same with disabled extensions and without gnome-screensaver
This bug is reproducible at 100% in any combination. 2 sessions of gnome-shell = crash.
Comment by Artiom Molchanov (artiom) - Monday, 29 April 2013, 17:13 GMT
Here is a messages.log extract taken during the switch.
At 18:42 I clicked "Switch User" menu.
Then at 18:43 I logged in with another user.
All this with all extension deactivated.
At the point where I didn't start another session (just GDM screen) I can switch to previous session. It has some strange behaviour, It look like working but some buttons are not clickable and some windows controls are not working with mouse. With keyboard all works. If I restart the shell (Alt+F2 r) It repairs all. But after a second session login it crashes completely with a full screen message about disabling all extension (already disabled by the way %( ).
   bug38.log (17.1 KiB)
Comment by Artiom Molchanov (artiom) - Monday, 29 April 2013, 17:32 GMT
New crash experience:
I've just started another GDM with "Switch User" menu and continued to work in my session (writing this bug report).
7 minutes later I switched back to GDM and found it crashed.
Here is the log.
I noticed this message in both logs:
Cogl-ERROR **: Failed to create an OpenGL framebuffer object

OpenGL works well and the direct rendering is on.
   gdm38_crash.log (5.3 KiB)
Comment by Valerio Mariani (valmar) - Friday, 03 May 2013, 09:51 GMT
Artiom, are you by chance using proprietary nvidia drivers? I have the same problem as you, which disappears if I use only the nouveau driver
Comment by Valerio Mariani (valmar) - Friday, 03 May 2013, 09:51 GMT
Also, I could reproduce this problem also on other distros (OpenSuse). So this looks like an upstream bug
Comment by Artiom Molchanov (artiom) - Friday, 03 May 2013, 15:01 GMT
Yes, I am using nvidia driver
Comment by Valerio Mariani (valmar) - Friday, 03 May 2013, 15:09 GMT
The problem does not exists when using nouveau (I know, I know). And it's cross distro, like I said. I would like to report it upstream but the gnome bug website seems a little bit of a mess...
Comment by Artiom Molchanov (artiom) - Sunday, 05 May 2013, 15:37 GMT
Yes, it works with nouveau. And also it works if I replace nvidia-libgl by mesa-libgl. However the interface response is very slow with mesa + nvidia.
After installing nvidia kms driver I also noticed that the crash happens just before the screensaver locks the screen, so I see all my windows without decorations and can click some menus.
Comment by Timo Saarinen (timosa) - Wednesday, 26 June 2013, 08:27 GMT
I have the exactly same problem with gnome-shell 3.8.3-1 and the proprietary nVidia drivers.
Comment by Valerio Mariani (valmar) - Wednesday, 26 June 2013, 23:31 GMT
It is very possible that this was fixed in 3.8.3-2. Please see this link:

http://worldofgnome.org/fedoras-gs-3-8-3-2-fixes-regression-with-nvidia/
Comment by Cameron Matheson (cmatheson) - Thursday, 27 June 2013, 08:22 GMT
3.8.3-2 didn't fix the issue for me.
Comment by Valerio Mariani (valmar) - Thursday, 27 June 2013, 09:33 GMT
Yes, this did not solve for me either. I also confirm it happens on other distros (Fedora, OpenSuse), so it still looks like an upstream bug. I don't know how such a bug, which is in my opinion critical, can go uncorrrected for a whole gnome release.
Comment by Timo Saarinen (timosa) - Thursday, 27 June 2013, 12:48 GMT
The 4th number in the version is distro specific. Is there an upstream ticket about this issue?
Comment by Valerio Mariani (valmar) - Thursday, 27 June 2013, 12:54 GMT
I created one today, but it's not going well...

https://bugzilla.gnome.org/show_bug.cgi?id=703174
Comment by Artiom Molchanov (artiom) - Monday, 01 July 2013, 10:03 GMT
I also saw this bug with Nouveau. It happens very rarely on shutdown.
Comment by Valerio Mariani (valmar) - Monday, 01 July 2013, 11:36 GMT
Artiom, It would be really great if you could report your experience in the upstream bug ticket here:

https://bugzilla.gnome.org/show_bug.cgi?id=703174

They tend to blame it on the NVIDIA driver and dismiss it as a driver bug, your experience could change this.

Valerio
Comment by Doug Newgard (Scimmia) - Tuesday, 12 May 2015, 17:08 GMT
Status?

Loading...