Red Hat Bugzilla – Bug 869439
[abrt] control-center-3.6.1-1.fc18: g_slist_prepend: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Last modified: 2014-02-05 07:41:30 EST
Description of problem:
1. System Settings
4. Add New Printer
5. Select a network printer (Brother HL-4070CDW)
6. Select ADD
7. Crash. Printer not added.
Version-Release number of selected component:
libreport version: 2.0.16
cmdline: gnome-control-center --overview
:Thread no. 1 (10 frames)
: #0 g_slist_prepend at gslist.c:266
: #1 g_object_class_install_property at gobject.c:562
: #2 gtk_message_dialog_class_init at gtkmessagedialog.c:202
: #3 gtk_message_dialog_class_intern_init at gtkmessagedialog.c:143
: #4 type_class_init_Wm at gtype.c:2217
: #5 g_type_class_ref at gtype.c:2924
: #6 g_object_new_valist at gobject.c:1796
: #8 gtk_message_dialog_new at gtkmessagedialog.c:620
: #9 new_printer_dialog_response_cb at cc-printers-panel.c:1726
: #10 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
Created attachment 632406 [details]
Created attachment 632407 [details]
Created attachment 632408 [details]
Created attachment 632409 [details]
Created attachment 632410 [details]
Created attachment 632411 [details]
Created attachment 632412 [details]
Created attachment 632413 [details]
Created attachment 632414 [details]
Created attachment 632415 [details]
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 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?
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.