Hide Forgot
Description of problem: Version-Release number of selected component: usermode-gtk-1.111-3.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gparted crash_function: handle_error executable: /usr/bin/consolehelper-gtk kernel: 3.10.10-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Sep 14 09:51:56 mediaserver abrt[1609]: Saved core dump of pid 1601 (/usr/bin/consolehelper-gtk) to /var/tmp/abrt/ccpp-2013-09-14-09:51:56-1601 (13041664 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #7 XkbGetState at XKB.c:489 #8 gdk_keymap_get_direction at gdkkeys-x11.c:761 #9 gtk_entry_draw_cursor at gtkentry.c:5648 #10 gtk_entry_expose at gtkentry.c:3460 #11 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #16 gtk_widget_event_internal at gtkwidget.c:5017 #17 gtk_widget_send_expose at gtkwidget.c:4846 #18 gtk_main_do_event at gtkmain.c:1610
Created attachment 800145 [details] File: backtrace
Created attachment 800146 [details] File: cgroup
Created attachment 800147 [details] File: core_backtrace
Created attachment 800148 [details] File: dso_list
Created attachment 800149 [details] File: environ
Created attachment 800150 [details] File: limits
Created attachment 800151 [details] File: maps
Created attachment 800152 [details] File: open_fds
Created attachment 800153 [details] File: proc_pid_status
Thanks for your report. Can you reproduce the crash? If so, how?
Hi, I found this on abrt problem list so I'm not able to specify how it happened and didn't occours anymore.
I'm sorry, I should have mentioned it was apparently triggered by starting gparted. Can you start gparted now?
Just reproduced nut I don't know if is a valid scenario: ssh -X myhost launched gparted as normal user (display is correctly exported since I'm using this ssh session for other programs)
Created attachment 805520 [details] usermode-debug.patch (In reply to smanocch from comment #13) > Just reproduced nut I don't know if is a valid scenario: > > ssh -X myhost > launched gparted as normal user (display is correctly exported since I'm > using this ssh session for other programs) Thank you. At the very least it is expected not to crash. (What kind of X server is used on the "client" running ssh? An ordinary Linux workstation? Something else?) To debug further, it will be necessary to test against an updated usermode package with the attached patch. Can you do the test build yourself, or would you prefer a pre-built RPM?
Hi, I've fedora 19 x64 on both systems. I prefer a re-built rpm. Thanks.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.