Bug 872897

Summary: [abrt] control-center-3.6.2-1.fc18: g_object_notify_queue_thaw: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mike H <mrpquter>
Component: control-centerAssignee: Marek Kašík <mkasik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: control-center-maint, kem, mkasik, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1be2616abb1a57d02092f1fc60459d9d78789f57
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 12:50:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages none

Description Mike H 2012-11-04 02:22:52 UTC 
Description of problem:
Invoked System Settings | Printers |  unlocked the tab, then clicked 'Add new printer' |  The network printer was detected correctly, and I clicked on the 'Add' button, which was followed by this crash.

Version-Release number of selected component:
control-center-3.6.2-1.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: g_object_notify_queue_thaw
kernel:         3.6.5-2.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_object_notify_queue_thaw at gobject.c:284
: #1 g_object_thaw_notify at gobject.c:1269
: #2 gtk_label_set_selectable at gtklabel.c:5175
: #3 gtk_message_dialog_init at gtkmessagedialog.c:348
: #4 g_type_create_instance at gtype.c:1890
: #5 g_object_constructor at gobject.c:1854
: #7 g_object_new_valist at gobject.c:1835
: #9 gtk_message_dialog_new at gtkmessagedialog.c:620
: #10 new_printer_dialog_response_cb at cc-printers-panel.c:1726
: #11 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
Comment 1 Mike H 2012-11-04 02:22:55 UTC 
Created attachment 637854 [details]
File: core_backtrace
Comment 2 Mike H 2012-11-04 02:22:57 UTC 
Created attachment 637855 [details]
File: environ
Comment 3 Mike H 2012-11-04 02:22:59 UTC 
Created attachment 637856 [details]
File: backtrace
Comment 4 Mike H 2012-11-04 02:23:00 UTC 
Created attachment 637857 [details]
File: limits
Comment 5 Mike H 2012-11-04 02:23:02 UTC 
Created attachment 637858 [details]
File: cgroup
Comment 6 Mike H 2012-11-04 02:23:04 UTC 
Created attachment 637859 [details]
File: executable
Comment 7 Mike H 2012-11-04 02:23:06 UTC 
Created attachment 637860 [details]
File: maps
Comment 8 Mike H 2012-11-04 02:23:08 UTC 
Created attachment 637861 [details]
File: dso_list
Comment 9 Mike H 2012-11-04 02:23:10 UTC 
Created attachment 637862 [details]
File: proc_pid_status
Comment 10 Mike H 2012-11-04 02:23:12 UTC 
Created attachment 637863 [details]
File: open_fds
Comment 11 Mike H 2012-11-04 02:23:13 UTC 
Created attachment 637864 [details]
File: var_log_messages
Comment 12 Marek Kašík 2012-11-05 13:39:03 UTC 
Hi Mike,

unfortunately, I can not reproduce the problem. Is it reproducible for you?
If yes could you try to run it under valgrind (with debuginfo installed)?

e.g.: valgrind -v --track-origins=yes --trace-children=yes --num-callers=32 gnome-control-center printers &> valgrind.log

  - it will be really slow

It could be also useful to get output of "lpinfo -l -v" (under root).

Did you enter address of the printer into the search entry or the printer was already present in the list?

Regards

Marek
Comment 13 Fedora End Of Life 2013-12-21 09:16:44 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 14 Fedora End Of Life 2014-02-05 12:50:47 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.