FS#48772 - [gnome-shell] After a few minutes the screen goes black

Attached to Project: Arch Linux
Opened by Dario Ostuni (dariost) - Thursday, 31 March 2016, 14:53 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 12 April 2016, 19:21 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 24
Private No

Details

Description:
After a few minutes I've logged in gnome-shell the screen goes black and I can't do anything.

Additional info:

gnome-shell is version 3.20.0-1
The only 2 installed extensions are: gnome-shell-extension-freon and gnome-shell-extension-gravatar
In dmesg it says "[ 330.712504] traps: gnome-shell[702] trap int3 ip:7fa24bd967eb sp:7ffd156555c0 error:0"

Steps to reproduce:
Log in gnome-shell and wait some minutes
   dmesg.log (59.2 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 12 April 2016, 19:21 GMT
Reason for closing:  Fixed
Comment by Frederic Bezies (fredbezies) - Friday, 01 April 2016, 02:05 GMT
It could be helpful to add Xorg.0.log to see if it is not related in some way to any xorg driver badly supported with linux kernel 4.5-1.

Just a guess, of course :)
Comment by Dario Ostuni (dariost) - Friday, 01 April 2016, 09:23 GMT
These are the Xorg.*.log after the crash
Also I should mention that "echo $DISPLAY" gives ":1"
   Xorg.0.log (40.1 KiB)
   Xorg.1.log (41.4 KiB)
Comment by Dmitrii (HansAnderson) - Friday, 01 April 2016, 15:08 GMT
Have same problem, and yet help nothing.
   journalctl (17.7 KiB)
Comment by Dario Ostuni (dariost) - Friday, 01 April 2016, 16:52 GMT
I haven't set any custom boot parameters.
In the attachments there are /boot/grub/grub.cfg and /etc/default/grub
   grub.cfg (5.2 KiB)
   grub (1.5 KiB)
Comment by andrey demidov (ademidov) - Saturday, 02 April 2016, 22:47 GMT
I have same problem. Here is information from journalctl: http://pastebin.com/sQC5Z8jv
   journalctl (12.4 KiB)
Comment by andrey demidov (ademidov) - Sunday, 03 April 2016, 04:02 GMT
I have replaced GDB by SDDM and problem disappeared
Comment by Dmitrii (HansAnderson) - Sunday, 03 April 2016, 21:23 GMT
I am admit , replace GDM by lightdm solved problem.
Comment by Jean-Patrick Guerrero (kilbith) - Monday, 04 April 2016, 15:04 GMT
Same problem here, using i965 chipset.

I get the same errors in journalctl than ademidov.
   journalctl (4.3 KiB)
Comment by Thorsten Reinbold (Thorsten Reinbold) - Monday, 04 April 2016, 20:58 GMT
Same problem here. Journalctl: http://pastebin.com/Ke2SerJP

Comment by Börje Holmberg (linfan) - Tuesday, 05 April 2016, 00:30 GMT
For me only gdm works, cannto start gnome-3.20 with startx with exec gnome-session in .xinitrc, so I decided it is premature to install it yet. Will wait til after April 15 :-) I simply refuse to use any login apps.
Comment by Thorsten Reinbold (Thorsten Reinbold) - Tuesday, 05 April 2016, 01:13 GMT
One note:

"Description:
After a few minutes I've logged in gnome-shell the screen goes black and I can't do anything."

I can switch to TTY2 when the screen went black. I only have a garbaged wallpaper, after alt+f2 and 'r' (restarting the shell), everything is well again.
Comment by Dario Ostuni (dariost) - Tuesday, 05 April 2016, 16:58 GMT
I didn't try that before because my TTY2 doesn't work due to the nVidia driver, but going to TTY2 and then blindly (because the screen is still black) press Alt + F2, r and Enter makes everything work again.
Comment by Jan de Groot (JGC) - Wednesday, 06 April 2016, 08:28 GMT
Please try with cogl from testing.
Comment by andrey demidov (ademidov) - Wednesday, 06 April 2016, 08:49 GMT
I have cogl installed from testing, but the problem remain.
Comment by Thorsten Reinbold (Thorsten Reinbold) - Wednesday, 06 April 2016, 10:47 GMT
Yes, same for me. Updated cogl and reenabled gdm (using lightdm as a workaround), but the screen still went black after some minutes.

Journalctl: http://pastebin.com/NTnmwnGZ
Comment by Jan de Groot (JGC) - Wednesday, 06 April 2016, 11:03 GMT
So far it looks like this is only when using nvidia drivers.

Try disabling wayland for gdm: https://wiki.archlinux.org/index.php/GDM#Use_Xorg_backend
Comment by andrey demidov (ademidov) - Wednesday, 06 April 2016, 11:05 GMT
It was the first I have tried, but it doesn't help me:

╰─$ cat /etc/gdm/custom.conf
# GDM configuration storage

[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false

And, yes I have nvidia drivers.
Comment by Thorsten Reinbold (Thorsten Reinbold) - Wednesday, 06 April 2016, 11:11 GMT
"And, yes I have nvidia drivers."

Indeed. With nouveau, the problem does not occur, so it seems to be related. Replaced nvidia with xf86-video-nouveau and the system runs stable for now. I'm using an GTX 760.
Comment by Thorsten Reinbold (Thorsten Reinbold) - Wednesday, 06 April 2016, 11:32 GMT
I've also tested to disable wayland, as JGC has suggested, but had no luck with this setting.
Comment by Jan de Groot (JGC) - Wednesday, 06 April 2016, 12:10 GMT
Next round of questions:
- was this a problem with GNOME 3.18 also (same cogl version)?
- is this still a problem when using nvidia drivers from extra?

Looks like cogl_framebuffer_allocate fails with nvidia drivers at some point, causing a fatal error leading to SIGABRT.

Also, can anyone recompile cogl with debug symbols and post complete backtraces?
Comment by Jean-Patrick Guerrero (kilbith) - Wednesday, 06 April 2016, 12:13 GMT
Please note I'm only using a Intel GPU (i965) and my screen goes black right after starting a X session with GNOME.
Comment by Jan de Groot (JGC) - Wednesday, 06 April 2016, 12:19 GMT
You're not suffering from this bug, you have unofficial fontconfig packages installed that lack some symbols. This bug is about gdm/gnome-shell crashing when VT-switched away and taking the logged in session with it.
Comment by andrey demidov (ademidov) - Wednesday, 06 April 2016, 12:27 GMT
>> was this a problem with GNOME 3.18 also

I am not sure, but I think - no. There was no this problem with Gnome 3.18. I had fresh install of system with Gnome 3.18 and worked with it only 4-5 hours, but there was not this problem.

>> is this still a problem when using nvidia drivers from extra?

I have installed nvidia drivers from extra right now, and yes - there problem is still here
Comment by Thorsten Reinbold (Thorsten Reinbold) - Wednesday, 06 April 2016, 12:28 GMT
@JGC:

1: No.
2: Yes, I've tested it some minutes ago. Same result. (nvidia-361.28-4)
3: Maybe I can make a backtrace later, I will be busy at work for now.

@ademidov: Are you sure, you're using nvidia from extra and not from testing?
Comment by andrey demidov (ademidov) - Wednesday, 06 April 2016, 12:34 GMT
Yes:

╭─demas@localhost ~
╰─$ pacman -Ss nvidia
extra/libvdpau 1.1.1-2 [установлен]
Nvidia VDPAU library
extra/nvidia 361.28-4 [установлен]
NVIDIA drivers for linux
extra/nvidia-libgl 361.28-5 [установлен]
NVIDIA drivers libraries symlinks
extra/nvidia-utils 361.28-5 [установлен]
NVIDIA drivers utilities


Comment by Thorsten Reinbold (Thorsten Reinbold) - Wednesday, 06 April 2016, 13:42 GMT
Sorry, I wasn't able to get a proper backtrace. Maybe someone more experienced could try?
Comment by andrey demidov (ademidov) - Wednesday, 06 April 2016, 14:10 GMT
Sorry, I don't have such experience. If there is a detailes guide I can try to do it.
Now I don't understand which file do I need to run with `# gdb /path/to/file`
Comment by Dmitrii (HansAnderson) - Wednesday, 06 April 2016, 18:20 GMT
I am glad it helped
backtrace
   bt_full (25.8 KiB)
Comment by Jonni Westphalen (swizzor) - Saturday, 09 April 2016, 16:04 GMT
I've got the same error.

extra/libvdpau 1.1.1-2
extra/nvidia 361.28-4
extra/nvidia-libgl 361.28-5
extra/nvidia-utils 361.28-5
multilib/lib32-nvidia-libgl 361.28-4
multilib/lib32-nvidia-utils 361.28-4

extra/gnome-desktop 1:3.20.0-1
extra/gdm 3.20.0-1

journalctl: http://pastebin.com/raw/TXNqF2A8
Comment by Severen Redwood (Shrike) - Sunday, 10 April 2016, 07:09 GMT
I seem to be having the same problem since upgrading to Gnome 3.20 from Gnome 3.18 today. At first I can login fine, but after a few minutes GDM crashes and pulls me over to TTY1. I can switch back to TTY2 and my session is still there. If I logout GDM will start up again, only to crash in the same fashion.

Packages:
(crash happens on both linux and linux-zen)
core/linux 4.4.5-1
extra/linux-zen 4.4.5-1

extra/libvdpau 1.1.1-2
extra/nvidia-dkms 361.28-4
extra/nvidia-libgl 361.28-5
extra/nvidia-utils 361.28-5
multilib/lib32-nvidia-libgl 361.28-4
multilib/lib32-nvidia-utils 361.28-4

extra/gnome-desktop 1:3.20.0-1
extra/gdm 3.20.0-1
extra/libgdm 3.20.0-1

Logs:

gdm.service status: http://pastebin.com/ACcA5Kiw

( ⌁ ) dmesg | grep gnome
[ 396.473419] traps: gnome-shell[1101] trap int3 ip:7f2faa2117eb sp:7ffc6340ea00 error:0
   Xorg.0.log (42.7 KiB)
   Xorg.1.log (36.2 KiB)
Comment by Michael (mrl4214) - Monday, 11 April 2016, 05:42 GMT
Having this problem aswell.
Comment by Tom Ebeling (Bollie) - Monday, 11 April 2016, 07:43 GMT
Having exactly the same issue here. I'm also using the proprietary nvidia module.
Comment by Manuel Reimer (M-Reimer) - Monday, 11 April 2016, 07:55 GMT
I just want to add, that I have exactly the same problem since I got the update to Gnome 3.20. So far I wasn't able to find any upstream bug. I tried to ask on mailing list, but maybe I asked on the wrong one:

http://comments.gmane.org/gmane.comp.gnome.gdm.general/2710

My logs:

http://m-reimer.de/tmp/gdm-crash-bug/journal
http://m-reimer.de/tmp/gdm-crash-bug/coredump

Can someone tell me if there are any disadvantages if I use an alternative login manager? Is it still possible to lock the screen or switch the user?
Comment by nylan (nylan) - Monday, 11 April 2016, 09:11 GMT
Same issue here, I'm also using the proprietary nvidia module.
Comment by Jan de Groot (JGC) - Monday, 11 April 2016, 11:21 GMT
Please test packages from http://pkgbuild.com/~jgc/

Patch that should fix this issue (at least the backtraces) is in that directory too.

Cogl allocates framebuffer objects lazy on the first drawing operation. The check on offscreen != COGL_INVALID_HANDLE in gnome-shell will never fail, as NULL/COGL_INVALID_HANDLE is never returned from the function that creates the offscreen object.

Comment by Thorsten Reinbold (Thorsten Reinbold) - Monday, 11 April 2016, 11:36 GMT
Tested gnome-shell-3.20.0-2.1-x86_64. Problem is solved on my system. :)
Comment by Jan Alexander Steffens (heftig) - Monday, 11 April 2016, 11:53 GMT
Shouldn't the second `priv->old_offscreen = COGL_INVALID_HANDLE;` use `priv->new_offscreen` instead?
Comment by Dario Ostuni (dariost) - Monday, 11 April 2016, 11:57 GMT
I can confirm, gnome-shell-3.20.0-2.1-x86_64 solves the problem
Comment by Jan de Groot (JGC) - Monday, 11 April 2016, 13:28 GMT
Yes, the patch has a bug, though you'll probably won't hit it because when it fails it will fail on the first allocation failure. Will adjust the patch and file a bug upstream.
Comment by Oscar Garcia (ogarcia) - Monday, 11 April 2016, 23:31 GMT
  • Field changed: Percent Complete (100% → 0%)
Sorry, but bug stills. I'm using propietary nvidia driver with a GeForce GTX 660.
Comment by Michael (mrl4214) - Monday, 11 April 2016, 23:35 GMT
Still seeing this issue as well
Comment by Jan de Groot (JGC) - Tuesday, 12 April 2016, 04:33 GMT
There's only one user who provided backtraces and that one has been fixed, so unless you provide detailed information, this bug will be closed again.
Comment by Michael (mrl4214) - Tuesday, 12 April 2016, 04:35 GMT
I can attempt to post a backtrace. Can I get some details on what files you need (and where they are located)?
Comment by Oscar Garcia (ogarcia) - Tuesday, 12 April 2016, 06:34 GMT
I try testing package 3.20.0-3 and seems fixed. If you can wait to this afternoon (CEST) I do more intense tests and confirm this.
Comment by LordBalmung (lordbalmung) - Tuesday, 12 April 2016, 16:57 GMT
Hi, I comfirm this is happening, here is the journal
Edit: More info,

linux: 4.4.5-1-ARCH
vga: nvidia 361.28-4
gnome: 3.20.1
   journal.txt (40.1 KiB)
Comment by Jan de Groot (JGC) - Tuesday, 12 April 2016, 17:46 GMT
What version of gnome-shell do you have? Backtrace is the same as what is already fixed in 3.20.0-3.
Comment by LordBalmung (lordbalmung) - Tuesday, 12 April 2016, 19:06 GMT
gnome-shell version is 3.20.0-2 (Extra)
Comment by Oscar Garcia (ogarcia) - Tuesday, 12 April 2016, 19:19 GMT
After several tests, in my case:

3.20.0-2 -> Bug still present.
3.20.0-3 -> Bug fixed. ;)

Thanks and sorry for my reopen.

Loading...