Version-Release number of selected component: gnome-shell-3.13.90-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.16.1-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #2 x_io_error at wayland/meta-xwayland.c:327 #3 _XIOError at XlibInt.c:1498 #4 _XEventsQueued at xcb_io.c:366 #5 XPending at Pending.c:55 #6 gdk_check_xpending at gdkeventsource.c:266 #7 gdk_event_source_prepare at gdkeventsource.c:284 #8 g_main_context_prepare at gmain.c:3352 #11 meta_run at core/main.c:481 Potential duplicate: bug 1065109
Created attachment 930153 [details] File: backtrace
Created attachment 930154 [details] File: cgroup
Created attachment 930155 [details] File: core_backtrace
Created attachment 930156 [details] File: dso_list
Created attachment 930157 [details] File: environ
Created attachment 930158 [details] File: limits
Created attachment 930159 [details] File: maps
Created attachment 930160 [details] File: open_fds
Created attachment 930161 [details] File: proc_pid_status
Created attachment 930162 [details] File: var_log_messages
Another user experienced a similar problem: Logged into wayland's gnome shell in QEMU. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.16.0-1.fc21.x86_64 package: gnome-shell-3.13.90-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
I just hit this when closing a new message window in Evolution.
Another user experienced a similar problem: Occurs when I launch Google Chrome reporter: libreport-2.3.0 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.17.2-300.fc21.i686+PAE package: gnome-shell-3.14.1.5-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1001
I faced this problem when I launch Geary
Issue still affects gnome-shell-3.14.2-1.fc21 when printing from Firefox into a file at the moment when the main windows was greyed out and the progress window was expected to pop up.
Another user experienced a similar problem: Problem occured while playing vlc reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.17.6-300.fc21.x86_64 package: gnome-shell-3.14.2-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1001
When running Gnome Shell in Wayland mode, when watching a full-screen YouTube video (HTML5) in Chrome, after screen lock (timeout) begins the session will die and I will be prompted with the login screen. If using X11 it's fine, if not using fullscreen mode it's fine.
Another user experienced a similar problem: Occurs when I remove usb bluetooth dongle reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.17.7-300.fc21.i686+PAE package: gnome-shell-3.14.3-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1001
This happens for me when opening a specific pdf document in firefox.
More precisely, this document: https://subs.linuxvoice.com/wp-content/uploads/2015/01/2015.pdf
I ran into this bug today. I'm not sure what caused it but the last steps I did were: close gnome-terminal and hit Super key to get to overview (I did this almost simultaneously)
Again hit this bug few times in gnome-shell-wayland when I was switching between ttys.
Way to reproduce this bug with two monitors (works for me): 1. start gnome-shell under wayland 2. run terminal and mutter --wayland in it 3. move mutter (which is running on X11 clutter backend) to second display 4. close the terminal (confirm that you want the close it even with running application) 5. crash!
I just hit this with gnome-shell 3.16.0.1.fc22.x86_64, according to ABRT. I'll upload the report logs.
Created attachment 1008187 [details] c26 journalctl
Created attachment 1008188 [details] c26 core_backtrace
Created attachment 1008189 [details] c26 environ
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.
@mchalupa: Can you still reproduce this issue?