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

flatpak 0.6 fatal error #848

Closed
worsco opened this issue Mar 5, 2022 · 3 comments
Closed

flatpak 0.6 fatal error #848

worsco opened this issue Mar 5, 2022 · 3 comments

Comments

@worsco
Copy link

worsco commented Mar 5, 2022

Any advice on troubleshooting flatpak version of the 0.6 release? 0.5 worked fine. This is the error from the 0.6 flatpak:

$ flatpak run org.gnome.GTG
2022-03-05 10:32:24,284 - WARNING - general_preferences:get_default_editor_font:89 - Using deprecated but still working font way (UnicodeDecodeError('utf-8', b'p\xb4\xb3\xec\\U 9', 1, 2, 'invalid start byte'))
2022-03-05 10:32:24,765 - ERROR - application:do_activate:153 - Exception during activation
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/application.py", line 148, in do_activate
    self.init_shared()
  File "/app/lib/python3.9/site-packages/GTG/gtk/application.py", line 229, in init_shared
    self.init_plugin_engine()
  File "/app/lib/python3.9/site-packages/GTG/gtk/application.py", line 255, in init_plugin_engine
    self.plugin_engine.activate_plugins()
  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
2022-03-05 10:32:29,085 - INFO - errorhandler:handle_response:163 - Going to exit because either of fatal error or user choice

@Neui
Copy link
Contributor

Neui commented Mar 5, 2022

You need to disable the Hamster plugin (this unfortunately occurs if you don't have the hamster plugin installed), see #770 (comment)

@worsco
Copy link
Author

worsco commented Mar 5, 2022

Thank you. vim ~/.var/app/org.gnome.GTG/config/gtg/gtg.conf and removing ,hamster from the enabled = list in section [plugins] fixed the start-up issue.

@worsco worsco closed this as completed Mar 5, 2022
@jorgeecardona
Copy link

jorgeecardona commented Apr 26, 2022

In my case it was not enough to remove hamster from the list of enabled plugins. GTG would open just once and the same fatal error would appear after. Somehow hamster was enabled again. Adding hamster to the list of disabled plugins work.

Also, this should not be closed, it makes no sense that the whole app crashes just for not being able to use a plugin. Disable the plugin, or mark it as unsuable somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants