abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py --debug component: system-config-printer crash_function: remove_entry executable: /usr/bin/python kernel: 2.6.35.9-64.fc14.x86_64 package: system-config-printer-1.2.5-6.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1291982895 uid: 500 comment ----- system-config-printer-1.2.5-6.fc14.x86_64 or system-config-printer-1.2.4-2.fc14.x86_64 cups-1.4.4-11.fc14.x86_64 or cups-1.4.5-1.fc14.x86_64 cups-pk-helper-0.0.4-13.fc14.x86_64 polkit-0.98-4.fc14.x86_64 polkit-kde-0.95.1-6.fc14.x86_64 polkit-qt-0.96.1-4.fc14.x86_64 How to reproduce ----- 1. in troubleshooter evoke some action that requires authentication, like choosing printer and pressing Forward or enabling debug No PolicyKit1 dialog appears and s-c-p crashes. The last few lines usually are: Authentication pass: 1 Authentication: password callback set Segmentation fault (core dumped) Once I saw this instead of the crash: ERROR:dbus.connection:Unable to set arguments (0, 0, [], []) according to signature u'iss': <type 'exceptions.TypeError'>: Expected a string or unicode object DevicesGet API exception; using old signature PolicyKit call to DevicesGet did not work: PolicyKit communication issue
Created attachment 467963 [details] File: backtrace
Looks like maybe threads 2 and 3 are both using D-Bus at the same time? Probably the troubleshooter needs to be using the newer asyncconn module for asynchronous calling instead of timeops.
Created attachment 468371 [details] another backtrace
In this one, threads 1 and 2 are both using D-Bus at the same time. One work-around would be to change AuthConnFactory so that it creates a cups.Connection instead of an authconn.Connection -- although the side effect would be that authentication would always be denied. An alternative would be to adjust authconn.Connection so that the caller can prevent the underlying object being a cupspk.Connection (which uses D-Bus). The real fix would be to use the proper asynchronous calling interface, asyncconn.
Should be fixed by this commit actually: commit 7480e83f04ec73cc1cccbefae440c26b1ba5c5a4 Author: Tim Waugh <twaugh> Date: Thu Dec 16 14:31:04 2010 +0000 Initialise D-Bus threading in timedops module (bug #662047). Initialise threading for D-Bus. This is needed as long as it is used from two separate threads. We only do this in a few places now, but in particular the troubleshooter does this.
system-config-printer-1.2.6-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/system-config-printer-1.2.6-1.fc14
system-config-printer-1.2.6-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/system-config-printer-1.2.6-1.fc13
system-config-printer-1.2.6-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/system-config-printer-1.2.6-2.fc13
system-config-printer-1.2.6-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
system-config-printer-1.2.7-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.