After upgrading from Fedora 29 to Fedora 31 with dnf system upgrade, guake (guake-3.6.3-1.fc31.noarch) fails to start. This is what I get on stdout when I attempt to launch it from terminal (guake -p gets the same output in case that's relevant): Guake not running, starting it Loading Gnome schema from: /usr/local/share/glib-2.0/schemas Language previously loaded from: /usr/local/share/locale Traceback (most recent call last): File "/usr/lib64/python3.7/site-packages/dbus/bus.py", line 175, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib64/python3.7/site-packages/dbus/bus.py", line 361, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib64/python3.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: The name does not have an owner During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/guake/main.py", line 389, in main remote_object = bus.get_object(DBUS_NAME, DBUS_PATH) File "/usr/lib64/python3.7/site-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib64/python3.7/site-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib64/python3.7/site-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib64/python3.7/site-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib64/python3.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/guake", line 10, in <module> sys.exit(exec_main()) File "/usr/local/lib/python3.7/site-packages/guake/main.py", line 518, in exec_main if not main(): File "/usr/local/lib/python3.7/site-packages/guake/main.py", line 404, in main instance = Guake() File "/usr/local/lib/python3.7/site-packages/guake/guake_app.py", line 137, in __init__ super(Guake, self).__init__(gladefile('guake.glade')) File "/usr/local/lib/python3.7/site-packages/guake/common.py", line 65, in gladefile raise IOError('No such file or directory: %s' % f) OSError: No such file or directory: /usr/local/share/guake/guake.glade
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.