Bug 1073693
| Summary: | [abrt] system-config-printer: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the ... | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | pcp | ||||||
| Component: | system-config-printer | Assignee: | Tim Waugh <twaugh> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | jpopelka, pcp, twaugh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/b4f482dec1e60236bc1fd6e4c98b36ca1b6cee04 | ||||||||
| Whiteboard: | abrt_hash:0b59b9ff6889ecc663cf7206ca4d14f2423a9efb | ||||||||
| Fixed In Version: | system-config-printer-1.4.4-1.fc20 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-03-30 06:02:55 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 871711 [details]
File: backtrace
Created attachment 871712 [details]
File: environ
Did this only happen once? (In reply to Tim Waugh from comment #3) > Did this only happen once? Have replied once already to an email from bugzilla.com about this, but don't know if that got through. Yes, as far as I can remember it only happened once. Early attempts to report it to Bugzilla failed, but with recent updates to the gnome-abrt reporting packages I tried again. So it probably happened a week or so earlier than the reporting date of this bug. By then I had switched from gdm to kdm as the login manager and my recently upgraded fedora 19 (from 18 using yum) was behaving much better. Gnome 3 setup kept hanging with gdm as the login manager and it wouldn't accept other desktop managers such as xmonad and xfce under gdm. The desktop managers work OK now under kdm. Should be fixed upstream in commit d49e1e3. https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?id=d49e1e36e87fc396ec7dd1c755cc4f5b2f1b5bdf Happened again today. First time since initially reported. system-config-printer-1.4.4-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/system-config-printer-1.4.4-1.fc20 Package system-config-printer-1.4.4-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.4-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4014/system-config-printer-1.4.4-1.fc20 then log in and leave karma (feedback). system-config-printer-1.4.4-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |
Version-Release number of selected component: system-config-printer-1.4.3-2.fc19 Additional info: reporter: libreport-2.1.12 cmdline: /usr/bin/python /usr/share/system-config-printer/applet.py dso_list: dbus-python-1.1.1-5.fc19.i686 executable: /usr/share/system-config-printer/applet.py kernel: 3.13.5-101.fc19.i686 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/share/system-config-printer/applet.py", line 441, in <module> runloop = RunLoop (session_bus, system_bus, loop) File "/usr/share/system-config-printer/applet.py", line 324, in __init__ dbus_interface=self.DBUS_IFACE) File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 160, in add_signal_receiver self.add_match_string(str(match)) File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 398, in add_match_string BUS_DAEMON_IFACE, 'AddMatch', 's', (rule,)) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x8baacbc> args: ("type='signal',path='/com/redhat/PrinterSpooler',interface='com.redhat.PrinterSpooler'",) object_path: '/org/freedesktop/DBus' signature: 's' bus_name: 'org.freedesktop.DBus' get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: -1.0 kwargs: {} dbus_interface: 'org.freedesktop.DBus' message: <dbus.lowlevel.MethodCallMessage path: /org/freedesktop/DBus, iface: org.freedesktop.DBus, member: AddMatch dest: org.freedesktop.DBus> method: 'AddMatch'