Version-Release number of selected component: system-config-printer-libs-1.4.6-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py crash_function: g_wakeup_signal executable: /usr/bin/python2.7 kernel: 3.16.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_wakeup_signal at /lib64/libglib-2.0.so.0 #1 g_cancellable_cancel at /lib64/libgio-2.0.so.0 #2 gtk_file_chooser_button_destroy at /lib64/libgtk-3.so.0 #7 gtk_widget_dispose at /lib64/libgtk-3.so.0 #9 gtk_box_forall at /lib64/libgtk-3.so.0 #10 gtk_container_destroy at /lib64/libgtk-3.so.0 #15 gtk_widget_dispose at /lib64/libgtk-3.so.0 #17 gtk_box_forall at /lib64/libgtk-3.so.0 #18 gtk_container_destroy at /lib64/libgtk-3.so.0 #23 gtk_widget_dispose at /lib64/libgtk-3.so.0
Created attachment 950172 [details] File: backtrace
Created attachment 950173 [details] File: cgroup
Created attachment 950174 [details] File: core_backtrace
Created attachment 950175 [details] File: dso_list
Created attachment 950176 [details] File: environ
Created attachment 950177 [details] File: exploitable
Created attachment 950178 [details] File: limits
Created attachment 950179 [details] File: maps
Created attachment 950180 [details] File: open_fds
Created attachment 950181 [details] File: proc_pid_status
Created attachment 950182 [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: When add this Bixolon SRP-275A receipt printer for POS. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py crash_function: g_wakeup_signal executable: /usr/bin/python2.7 kernel: 3.16.6-200.fc20.x86_64 package: system-config-printer-libs-1.4.6-1.fc20 reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days