Description of problem: Pressed search for printer driver? Version-Release number of selected component: system-config-printer-1.4.6-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py crash_function: dequeue_pending_request executable: /usr/bin/python2.7 kernel: 3.16.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #4 dequeue_pending_request at xcb_io.c:177 #6 XIQueryPointer at XIQueryPointer.c:74 #7 gdk_x11_device_xi2_query_state at gdkdevice-xi2.c:350 #8 gdk_x11_device_xi2_get_state at gdkdevice-xi2.c:267 #9 gtk_window_has_mnemonic_modifier_pressed at gtkwindow.c:7533 #10 gtk_window_focus_in_event at gtkwindow.c:7564 #11 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85 #16 gtk_widget_event_internal at gtkwidget.c:7168 #17 gtk_widget_event at gtkwidget.c:6830 #18 gtk_main_do_event at gtkmain.c:1657
Created attachment 950553 [details] File: backtrace
Created attachment 950554 [details] File: cgroup
Created attachment 950555 [details] File: core_backtrace
Created attachment 950556 [details] File: dso_list
Created attachment 950557 [details] File: environ
Created attachment 950558 [details] File: limits
Created attachment 950559 [details] File: maps
Created attachment 950560 [details] File: open_fds
Created attachment 950561 [details] File: proc_pid_status
Created attachment 950562 [details] File: var_log_messages
Can you make this happen again? What steps do you follow to do that?
Another user experienced a similar problem: I wanted to add printer using Printer Settings utility. My network printer (Canon MG5520) was visible in the list of priters. I choose it and clicked to Forward button. "Searching for driver" window appeared and then it crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py crash_function: dequeue_pending_request executable: /usr/bin/python2.7 kernel: 3.16.7-200.fc20.i686 package: system-config-printer-1.4.6-1.fc20 reason: python2.7 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Threads 1 (main) and 3 (OpenPrinting) are both using the GTK+ API at the same time. This was fixed upstream in commit 822d83db2ad7c0b24062973ee9bd5a1d13f15ae9: https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.x&id=822d83db2ad7c0b24062973ee9bd5a1d13f15ae9
system-config-printer-1.4.7-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/system-config-printer-1.4.7-1.fc20
Package system-config-printer-1.4.7-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing system-config-printer-1.4.7-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14778/system-config-printer-1.4.7-1.fc20 then log in and leave karma (feedback).
*** Bug 1162984 has been marked as a duplicate of this bug. ***
*** Bug 1164016 has been marked as a duplicate of this bug. ***
system-config-printer-1.4.7-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.