Bug 859507 - [abrt] python-2.7.3-7.2.fc17: gtk_accel_groups_activate: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Summary: [abrt] python-2.7.3-7.2.fc17: gtk_accel_groups_activate: Process /usr/bin/pyt...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gajim
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Schmidt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:330edc4be1ae076813ba3c9a56f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-21 17:26 UTC by Tobias Mueller
Modified: 2013-03-20 12:39 UTC (History)
6 users (show)

Fixed In Version: gajim-0.15.2-1.fc17
Clone Of:
Environment:
Last Closed: 2013-03-20 12:39:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: core_backtrace (3.27 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: environ (3.35 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: backtrace (63.92 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: limits (1.29 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: cgroup (129 bytes, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: maps (101.57 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: dso_list (19.09 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: var_log_messages (153 bytes, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details
File: open_fds (1.73 KB, text/plain)
2012-09-21 17:26 UTC, Tobias Mueller
no flags Details

Description Tobias Mueller 2012-09-21 17:26:31 UTC
Description of problem:
Hm. I pressed Escape in a chat window Gajim. And FWIW my gnome-settings-daemon is dead due to some other bug where it consumes all CPU.
Reproducing the issue is a bit tricky as one has to be quick closing the window. I.e. double click a roster item and then quickly press escape. If you're lucky, Gajim crashes. If not, rinse and repeat. After a couple of times, Gajim crashes for me.

There is already something in b.f.o: bug 551834
Upstream knows here about it: https://bugzilla.gnome.org/show_bug.cgi?id=599971


Version-Release number of selected component:
python-2.7.3-7.2.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        /usr/bin/python -OO gajim.py
crash_function: gtk_accel_groups_activate
kernel:         3.5.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 gtk_accel_groups_activate at gtkaccelgroup.c
: #1 gtk_window_activate_key at gtkwindow.c
: #2 gtk_window_key_press_event at gtkwindow.c
: #3 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c
: #8 gtk_widget_event_internal at gtkwidget.c
: #9 gtk_widget_event at gtkwidget.c
: #10 gtk_propagate_event at gtkmain.c
: #11 gtk_main_do_event at gtkmain.c
: #17 gtk_main at gtkmain.c
: #18 _wrap_gtk_main at ./gtk.override

Comment 1 Tobias Mueller 2012-09-21 17:26:34 UTC
Created attachment 615533 [details]
File: core_backtrace

Comment 2 Tobias Mueller 2012-09-21 17:26:37 UTC
Created attachment 615534 [details]
File: environ

Comment 3 Tobias Mueller 2012-09-21 17:26:41 UTC
Created attachment 615535 [details]
File: backtrace

Comment 4 Tobias Mueller 2012-09-21 17:26:43 UTC
Created attachment 615536 [details]
File: limits

Comment 5 Tobias Mueller 2012-09-21 17:26:46 UTC
Created attachment 615537 [details]
File: cgroup

Comment 6 Tobias Mueller 2012-09-21 17:26:49 UTC
Created attachment 615538 [details]
File: maps

Comment 7 Tobias Mueller 2012-09-21 17:26:51 UTC
Created attachment 615539 [details]
File: dso_list

Comment 8 Tobias Mueller 2012-09-21 17:26:53 UTC
Created attachment 615540 [details]
File: var_log_messages

Comment 9 Tobias Mueller 2012-09-21 17:26:57 UTC
Created attachment 615541 [details]
File: open_fds

Comment 10 Michal Schmidt 2013-03-20 12:39:44 UTC
I see that you reported it had been fixed in Gajim upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=599971#c20
The fix has been included since 0.15.2.


Note You need to log in before you can comment on or make changes to this bug.