Description of problem: Tried to log into Gnome 3 Wayland. Password was accepted but instead of showing the desktop it goes back to the login-screen. Version-Release number of selected component: gnome-shell-3.17.4-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 1930 kernel: 4.2.0-0.rc5.git0.2.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 _g_log_abort at gmessages.c:316 #3 meta_clutter_init at backends/meta-backend.c:629 #4 meta_init at core/main.c:358 Potential duplicate: bug 1243011
Created attachment 1062446 [details] File: backtrace
Created attachment 1062447 [details] File: cgroup
Created attachment 1062448 [details] File: core_backtrace
Created attachment 1062449 [details] File: dso_list
Created attachment 1062450 [details] File: environ
Created attachment 1062451 [details] File: limits
Created attachment 1062452 [details] File: maps
Created attachment 1062453 [details] File: mountinfo
Created attachment 1062454 [details] File: namespaces
Created attachment 1062455 [details] File: open_fds
Created attachment 1062456 [details] File: proc_pid_status
Created attachment 1062457 [details] File: var_log_messages
I have the same issue with the same steps to reproduce as Tobias Schönberg.
(In reply to Matej Habrnal from comment #13) > I have the same issue with the same steps to reproduce as Tobias Schönberg. According to logs you sent me to #1254296 the cause is this: mutter-WARNING **: Could not stat /dev/dri/card0: Adresář nebo soubor neexistuje Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any mutter-ERROR **: Unable to initialize Clutter. It could be coupled with https://bugzilla.gnome.org/show_bug.cgi?id=753434 What is you're graphics card?
$ lspci -v ... 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 220c Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 ...
Created attachment 1069682 [details] journalctl -b _COMM=gdm-x-session
Talked to reporter and here are few helpful things: reporter has no /dev/dri nor /sys/class/drm folders $ glxinfo | grep -E 'render(ing|er).*:' direct rendering: Yes OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits) Xorg log (attached by Matej in #16): (EE) open /dev/dri/card0: No such file or directory (EE) open /dev/dri/card0: No such file or directory (EE) open /dev/fb0: No such file or directory (EE) open /dev/fb0: No such file or directory (EE) Screen 0 deleted because of no matching config section. (EE) Screen 0 deleted because of no matching config section. (II) AIGLX: Screen 0 is not DRI2 capable (EE) AIGLX: reverting to software rendering (II) GLX: Initialized DRISWRAST GL provider for screen 0
Tried again with fresh install of F23-Beta in VirtualBox. Still no luck with logging into Wayland session.
Another user experienced a similar problem: I opened the new liveusb creator (from the new-ui branch) and the whole desktop freezed. After an attempt to switch the VT, the session wasn't there anymore. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 28573 kernel: 4.2.3-300.fc23.x86_64 package: gnome-shell-3.18.1-1.fc23 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I tried to use sushi (space key) on a jpg file to preview it, and my whole session was immediatelly killed and I appeared in gdm. After logging in again, I can use sushi previewer on that particular picture, can't reproduce the crash again. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 1074c0bf8b7cc91ae2143439721111212400000012180000 crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 6370 kernel: 4.2.3-300.fc23.x86_64 package: gnome-shell-3.18.1-1.fc23 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This occurred while I was trying to use GNOME Boxes to make a Fedora virtual machine. It appears that there are severe issues on this device whenever I try to use Boxes for virtualization, and this time was the most severe of past events. Steps: 1) Create virtual machine in Boxes 2) Wait while it starets up 3) Computer becomes slow and unresponsive, does not respond to clicks or keyboard presses 4) GNOME shell crashes 5) Later followed by NetworkManager and then systemd crashing (thereby logging me out) reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 10436 kernel: 4.2.3-300.fc23.x86_64 package: gnome-shell-3.18.1-1.fc23 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
I'd change Severity to something like critical, maybe even a blocker. I do nothing but browse, having Firefox, Chrome, Thunderbird when this happens and I get kicked ouf of Gnome. Sometimes I'd get "dummy audio" in settings and to bring audio/sounds back I have to reboot.
Created attachment 1086132 [details] journal log
(In reply to lejeczek from comment #22) > I'd change Severity to something like critical, maybe even a blocker. > I do nothing but browse, having Firefox, Chrome, Thunderbird when this > happens and I get kicked ouf of Gnome. Sometimes I'd get "dummy audio" in > settings and to bring audio/sounds back I have to reboot. The backtrace in this bug is actually a symptom not the problem - what happens is that when the X server crashes, gnome-shell is respawned but can't connect and then dies with this backtrace. (That is a bug in itself, but I've been avoiding fixing it until I really understand everything that is going on.) The log you've attached (which I don't quite undertand - it doesn't look like a typical journal log with timestamps, etc.) seems to show an X server segfault: (EE) (EE) Backtrace: (EE) 0: ? (?+0x0) [0x10059acf0] (EE) 1: ? (?+0x0) [0x7f8f9e368b1f] (EE) 2: ? (?+0x0) [0x7f8f98f69d40] (EE) 3: ? (?+0x0) [0x7f8f98f9f6d0] (EE) 4: ? (?+0x0) [0x10043b160] (EE) 5: ? (?+0x0) [0x100593640] (EE) 6: ? (?+0x0) [0x100436570] (EE) 7: ? (?+0x0) [0x10043a440] (EE) 8: ? (?+0x0) [0x7f8f9e354490] (EE) 9: ? (?+0x0) [0x100424b50] (EE) 10: ? (?+0x0) [0x100000000] (EE) (EE) Segmentation fault at address 0x80 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) Do you know if abrt reported this as well? perhaps with more useful symbol information.
(In reply to Owen Taylor from comment #24) > The log you've attached (which I don't quite undertand - it doesn't look > like a typical journal log with timestamps, etc.) seems to show an X server > segfault: > > (EE) > (EE) Backtrace: > (EE) 0: ? (?+0x0) [0x10059acf0] > (EE) 1: ? (?+0x0) [0x7f8f9e368b1f] > (EE) 2: ? (?+0x0) [0x7f8f98f69d40] > (EE) 3: ? (?+0x0) [0x7f8f98f9f6d0] > (EE) 4: ? (?+0x0) [0x10043b160] > (EE) 5: ? (?+0x0) [0x100593640] > (EE) 6: ? (?+0x0) [0x100436570] > (EE) 7: ? (?+0x0) [0x10043a440] > (EE) 8: ? (?+0x0) [0x7f8f9e354490] > (EE) 9: ? (?+0x0) [0x100424b50] > (EE) 10: ? (?+0x0) [0x100000000] > (EE) > (EE) Segmentation fault at address 0x80 > (EE) > Fatal server error: > (EE) Caught signal 11 (Segmentation fault). Server aborting > (EE) > > Do you know if abrt reported this as well? perhaps with more useful symbol > information. Very similar to my problem: https://bugzilla.redhat.com/show_bug.cgi?id=1264739
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.