abrt detected a crash. Comment ----- Print setup dialog crashes From Kickoff Application Launcher, choose Applications - Administration - Printing Then from the print dialog menu choose Server - New - Printer Dialog crashes with Python error Attached file: backtrace cmdline: python /usr/share/system-config-printer/system-config-printer.py component: python executable: /usr/bin/python kernel: 2.6.31.5-127.fc12.i686.PAE package: python-2.6.2-2.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 374514 [details] File: backtrace
Thank you for reporting this bug. What version of system-config-printer do you have installed? Looking at the backtrace, it looks like the problem occurred in thread #1 in _dbus_watch_invalidate Reassigning component from "python" to "system-config-printer"
The version of system-config-printer is 1.1.13 (In reply to comment #2) > Thank you for reporting this bug. > > What version of system-config-printer do you have installed? > > Looking at the backtrace, it looks like the problem occurred in thread #1 in > _dbus_watch_invalidate > > Reassigning component from "python" to "system-config-printer"
Seems to be in a call to gtk.events_pending, so I think it must be this call stack: system-config-printer.py:3451 in GUI.on_new_printer_activate: self.busy (self.PrintersWindow) system-config-printer.py:1186 in GUI.busy: while gtk.events_pending (): How reproducible is this for you? Does it happen every time?
*** Bug 543641 has been marked as a duplicate of this bug. ***
Created attachment 375564 [details] Screenshots and terminal output
It's 90% reproducible. In 10 trials, it failed 9 times. I was able to successfully add a printer one time without crashing. Sometimes it prompts twice for the superuser password using different dialogs (see attached screen shots). When run from the command line, it gives the following message: $ system-config-printer process 2023: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted (core dumped) I uploaded another coredump and backtrace to bug 543641 which had a different description: Fatal error in "memmove" in /usr/share/system-config-printer/system-config-printer.py I marked 543641 as a duplicate of this issue, but it may have useful info in the backtrace. (In reply to comment #4) > Seems to be in a call to gtk.events_pending, so I think it must be this call > stack: > > system-config-printer.py:3451 in GUI.on_new_printer_activate: > self.busy (self.PrintersWindow) > system-config-printer.py:1186 in GUI.busy: > while gtk.events_pending (): > > How reproducible is this for you? Does it happen every time?
> I uploaded another coredump and backtrace to bug 543641 which had a different > description: Fatal error in "memmove" in > /usr/share/system-config-printer/system-config-printer.py (I'm getting a flood of bugzilla reports via ABRT against "python" for every coredump involving /usr/bin/python so I wrote a script to help me rename and reassign the bugs; the different "Summary" fields are probably due to different revisions of my script; sorry for any confusion)
Can you please run this command from the terminal and attach the output?: system-config-printer --debug Thanks.
(In reply to comment #9) > Can you please run this command from the terminal and attach the output?: > > system-config-printer --debug > > Thanks. Here are a couple runs with --debug. Run #1 - crashed before getting superuser password [mb@fr2 ~]$ system-config-printer --debug Connected as user mb refresh Created subscription 21 <monitor.Monitor instance at 0x90245ac>: printers and jobs lists provided update_jobs Authentication pass: 1 Authentication: password callback set Authentication pass: 1 Authentication: password callback set Authentication pass: 1 Authentication: password callback set get_notifications update_jobs Calling <bound method NewPrinterGUI.fetchDevices of <__main__.NewPrinterGUI instance at 0x90189ac>> fetchDevices Connected as user mb in get_devices: connected Fetching local devices Authentication pass: 1 Authentication: password callback set Segmentation fault (core dumped) Run #2 - successfully authenticated as root, then crashed after I clicked 'Cancel' on the 'New Printer' dialog [mb@fr2 ~]$ system-config-printer --debug Connected as user mb refresh Created subscription 22 <monitor.Monitor instance at 0x9cad5ac>: printers and jobs lists provided update_jobs Authentication pass: 1 Authentication: password callback set Authentication pass: 1 Authentication: password callback set Authentication pass: 1 Authentication: password callback set get_notifications update_jobs Calling <bound method NewPrinterGUI.fetchDevices of <__main__.NewPrinterGUI instance at 0x9ca19ac>> fetchDevices Connected as user mb in get_devices: connected Fetching local devices Authentication pass: 1 Authentication: password callback set Got devices Done Calling <bound method NewPrinterGUI.fetchDevices of <__main__.NewPrinterGUI instance at 0x9ca19ac>> fetchDevices Connected as user mb in get_devices: connected Fetching network devices Authentication pass: 1 Authentication: password callback set Command canceled Segmentation fault (core dumped)
I think this might be caused by bug #549749. *** This bug has been marked as a duplicate of bug 549749 ***