Version-Release number of selected component: gnome-shell-3.8.1-1.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _gdk_x11_display_error_event executable: /usr/bin/gnome-shell kernel: 3.9.0-0.rc6.git2.3.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2556 #5 handle_error at xcb_io.c:212 #7 XIQueryDevice at XIQueryDevice.c:60 #8 translate_hierarchy_event at x11/clutter-device-manager-xi2.c:411 #9 clutter_device_manager_xi2_translate_event at x11/clutter-device-manager-xi2.c:725 #10 clutter_backend_real_translate_event at ./clutter-backend.c:572 #11 clutter_x11_handle_event at x11/clutter-event-x11.c:199 #12 gnome_shell_plugin_xevent_filter at gnome-shell-plugin.c:392 #13 meta_compositor_process_event at compositor/compositor.c:958 #14 event_callback at core/display.c:2917
Created attachment 737922 [details] File: backtrace
Created attachment 737923 [details] File: cgroup
Created attachment 737924 [details] File: core_backtrace
Created attachment 737925 [details] File: dso_list
Created attachment 737926 [details] File: environ
Created attachment 737927 [details] File: limits
Created attachment 737928 [details] File: maps
Created attachment 737929 [details] File: open_fds
Created attachment 737930 [details] File: proc_pid_status
Created attachment 737931 [details] File: var_log_messages
It was immediately after resuming, I think the unlock prompt came up ... and then it crashed before I entered the password and I was in and gnome shell was working as expected. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _gdk_x11_display_error_event executable: /usr/bin/gnome-shell kernel: 3.9.4-301.fc19.x86_64 package: gnome-shell-3.8.2-3.fc19 reason: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000
GDK traps errors when calling XIQueryDevice, since devices can disappear at any time. Clutter should do the same.
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=701974
*** Bug 879864 has been marked as a duplicate of this bug. ***
*** Bug 893865 has been marked as a duplicate of this bug. ***
Can we get this fixed in F19, please? I wonder why it isn't as visible with older GNOME versions.
clutter-1.14.4-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/clutter-1.14.4-3.fc19
Proposed as a Freeze Exception for 19-final by Fedora user mclasen using the blocker tracking app because: crash in critpath
Discussed at 2013-06-24 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-blocker-review-8.2013-06-24-16.00.log.txt . This is obviously a significant issue, but as user accounts on the live images are not valuable in any way, there are only corner cases which would benefit from fixing this in the release package set (users of the live media persistency features with 'valuable' user accounts). Given this, and the fact that it's only 3 days till go/no-go, we decided to go 'safety first' and reject this as an FE issue for now. If we wind up slipping the release, we'll probably make this acceptedFE and slip it into one of the early post-slip builds.
Package clutter-1.14.4-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing clutter-1.14.4-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-11606/clutter-1.14.4-3.fc19 then log in and leave karma (feedback).
clutter-1.14.4-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/clutter-1.14.4-4.fc19
clutter-1.14.4-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
after standby, there is no passwort required clutter1.14.4-4.fc19 Gnome 64bit AMD Graphic os driver sabertooth 990fx r2 luks My Notebook is working fine, 32bit, HP NC2400
*** Bug 977031 has been marked as a duplicate of this bug. ***
*** Bug 974762 has been marked as a duplicate of this bug. ***
thx its working. ;)
edit: same problem, after standby no password is required
(In reply to markus from comment #27) > edit: > same problem, after standby no password is required What's your version of clutter? Please run "rpm -q clutter".
(In reply to Florian Weimer from comment #28) > (In reply to markus from comment #27) > > edit: > > same problem, after standby no password is required > > What's your version of clutter? Please run "rpm -q clutter". Hi, I'm not Markus, but I'm using clutter-1.14.4-4.fc19 and gnome-shell-3.8.3-3.fc19 and getting the same error it seems. I don't seem to get any core dumped, so I straced gnome-shell and got the attached files. Currently I'm unable to run GUI desktop on my main work box, so this is kinda urgent.
Created attachment 769107 [details] gnome-shell strace file Sorry. This is the attachment I mentioned in the previous comment.
(In reply to Ken Sugawara from comment #30) > Created attachment 769107 [details] > gnome-shell strace file > > Sorry. This is the attachment I mentioned in the previous comment. Hmm. Can you provide us with a backtrace (attach GDB to the running process from a VTY console) and the warning messages printed to stderr? They are truncated in the strace output. I suspect this is a different bug. In my case, there weren't as many Cogl warnings.
Created attachment 769132 [details] gdb session log (gdb gnome-shell /var/tmp/ccpp-*/coredump ) Ok, I found a half baked abrt report (?) in /var/tmp/abrt/ccpp-* where coredump file was of gnome-shell killed by SIGTRAP. The attached file is the log of gdb session. If it turns out to be a different bug, I'll submit a new bug. Thanks,
(In reply to Ken Sugawara from comment #32) > Created attachment 769132 [details] > gdb session log (gdb gnome-shell /var/tmp/ccpp-*/coredump ) > > Ok, I found a half baked abrt report (?) in /var/tmp/abrt/ccpp-* where > coredump file was of gnome-shell killed by SIGTRAP. The attached file is the > log of gdb session. > > If it turns out to be a different bug, I'll submit a new bug. Your Cogl error is "Failed to create an OpenGL framebuffer object", that's different from the error reported in this bug, "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'XI_BadDevice (invalid Device parameter)'.\n (Details: serial 70478 error_code 1". This is probably a different bug.
(In reply to Florian Weimer from comment #33) > Your Cogl error is "Failed to create an OpenGL framebuffer object", that's > different from the error reported in this bug, "The program 'gnome-shell' > received an X Window System error.\nThis probably reflects a bug in the > program.\nThe error was 'XI_BadDevice (invalid Device parameter)'.\n > (Details: serial 70478 error_code 1". This is probably a different bug. Thanks. I'll submit a new one.
[root@localhost markus]# rpm -q clutter clutter-1.14.4-4.fc19.x86_64