Version-Release number of selected component: veusz-1.17.1-1.fc19 Additional info: reporter: libreport-2.1.5 cmdline: /usr/bin/python /usr/bin/veusz dso_list: dbus-python-1.1.1-5.fc19.x86_64 executable: /usr/bin/veusz kernel: 3.9.9-301.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: bus.py:122:__new__: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/lib64/python2.7/site-packages/veusz/veusz_main.py", line 148, in run initImports() File "/usr/lib64/python2.7/site-packages/veusz/veusz_main.py", line 140, in initImports vzdbus.setup() File "/usr/lib64/python2.7/site-packages/veusz/utils/vzdbus.py", line 38, in setup sessionbus = dbus.SessionBus() File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) 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: mainloop: None address_or_type: 0 cls: <class 'dbus._dbus.SessionBus'>
Created attachment 774875 [details] File: backtrace
Created attachment 774876 [details] File: core_backtrace
Created attachment 774877 [details] File: environ
Interesting. It looks like there's some problem communicating with the dbus service on your system. If I search, I find similar errors for other software. Is the problem reproducable? It won't be hard to ignore the error, but if it's not reproducable it could perhaps wait until the next release.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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