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
Created attachment 637854 [details] File: core_backtrace
Created attachment 637855 [details] File: environ
Created attachment 637856 [details] File: backtrace
Created attachment 637857 [details] File: limits
Created attachment 637858 [details] File: cgroup
Created attachment 637859 [details] File: executable
Created attachment 637860 [details] File: maps
Created attachment 637861 [details] File: dso_list
Created attachment 637862 [details] File: proc_pid_status
Created attachment 637863 [details] File: open_fds
Created attachment 637864 [details] File: var_log_messages
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
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.