Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on first run activating plugin hamster #969

Closed
42sol-eu opened this issue Apr 16, 2023 · 4 comments
Closed

Error on first run activating plugin hamster #969

42sol-eu opened this issue Apr 16, 2023 · 4 comments
Labels
duplicate patch-or-wont-happen Core maintainers would like this, but lack time/energy. Contribute a patch or it won't happen. plugins Plugins and extra backends priority:high

Comments

@42sol-eu
Copy link

Context: Global generic exception

Hamster installed and running - but maybe a interface is missing?

Traceback (most recent call last):
  File "/app/lib/python3.9/site-packages/dbus/bus.py", line 177, in activate_name_owner
    return self.get_name_owner(bus_name)
  File "/app/lib/python3.9/site-packages/dbus/bus.py", line 361, in get_name_owner
    return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
  File "/app/lib/python3.9/site-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: org.freedesktop.DBus.Error.NameHasNoOwner

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/lib/python3.9/site-packages/GTG/gtk/plugins.py", line 216, in on_plugin_toggle
    self.pengine.activate_plugins([plugin])
  File "/app/lib/python3.9/site-packages/GTG/core/plugins/engine.py", line 202, in activate_plugins
    plugin.instance.activate(api)
  File "/app/lib/python3.9/site-packages/GTG/plugins/hamster/hamster.py", line 155, in activate
    self.hamster = dbus.SessionBus().get_object('org.gnome.Hamster',
  File "/app/lib/python3.9/site-packages/dbus/bus.py", line 241, in get_object
    return self.ProxyObjectClass(self, bus_name, object_path,
  File "/app/lib/python3.9/site-packages/dbus/proxies.py", line 250, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/app/lib/python3.9/site-packages/dbus/bus.py", line 182, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/app/lib/python3.9/site-packages/dbus/bus.py", line 277, in start_service_by_name
    return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
  File "/app/lib/python3.9/site-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown

Software versions:

  • Getting Things GNOME! v0.6
  • CPython 3.9.9 (main, Nov 10 2011, 15:00:00) [GCC 11.3.0]
  • GTK 3.24.34, GLib 2.70.5
  • PyGLib 3.42.2, PyGObject 3.42.2
  • Linux-6.2.10-arch1-1-x86_64-with-glibc2.33
@PermaFreez
Copy link

I'm having the same problem too. All versions are the same, except for my kernel, which is 1 version ahead. I went into ~/.local/share/flatpak/app/org.gnome.GTG/current/active/files/lib/python3.9/site-packages/GTG/plugins/ and then deleted both the hamster.gtg-plugin file and the hamster directory (this of course disables the plugin). It does start after that, but a fix would be appreciated.

@deephack1982
Copy link

Can confirm that this work around works however the flatpak by default does not work at present without making these changes. Seems like a fairly serious problem.

@nekohayo
Copy link
Member

At the moment I think we're not touching the flatpak until we have a new release ready (because we're too stretched and we would probably just break more things), which depends on solving #737 first; after that's done, hopefully someone shows up to maintain that plugin again in time for 0.7 (maybe @flavin if still interested?), otherwise as the plugin's code previously did not have significant development activity for over a decade and is probably woefully out of date, we could disable the hamster plugin by moving it to the "unmaintained" subfolder.

@nekohayo nekohayo added priority:high patch-or-wont-happen Core maintainers would like this, but lack time/energy. Contribute a patch or it won't happen. plugins Plugins and extra backends labels Nov 28, 2023
@nekohayo
Copy link
Member

Duplicate of #683

@nekohayo nekohayo marked this as a duplicate of #683 Feb 26, 2024
@nekohayo nekohayo closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate patch-or-wont-happen Core maintainers would like this, but lack time/energy. Contribute a patch or it won't happen. plugins Plugins and extra backends priority:high
Projects
None yet
Development

No branches or pull requests

4 participants