Error on ubuntu 19.10 #326
Assignees
Comments
|
Hi mwilck, I didn't know I need to install it from sources... so I though enabling it from Central Extension Repository was enoght, so I installed the version published by elbenfreund in, that is a 3.20: Here it is the "jounralctl --user" output from the last hour (the full one started on month ago and is hudge): I will try with sources. Thanks for your time, |
No, it's not enough. Grab my GNOME 3.36 branch, unpack it, and follow the instructions in README.rst under "Manual Installation For Testing and Development" (no need to run |
|
For clarity: The plan is to make the extension on extensions.gnome.org again up-to-date and sufficient, but we're starting up development again after a long hiatus, so we're not there yet. In the meanwhile, testing using local installs is helpful! |
|
@matthijskooijman, I wonder if we could add a sticky note to our repo telling users that it makes no sense to test the stuff from e.g.o with late GNOME versions currently and that we're actively working on it, and providing instructions for installing / testing the |
|
I think you can mark issues as sticky (or pin them, dunno how it's called), that might be useful? |
|
I just created a sticky note (#327), please check it out. |
|
Thanks for the explanation. Hamster is one of my favorite programs ever and I love to help but I don't know python and gnome-shell and all this sounds like vudu for me... so please, be patien. :-) Despite that, I can follow instructions (the README file is very clear). As said, I don't know python but some missing chains don't look like a real issue so I follow with the installation process but I don't see any new extension in my extensions.gnome.org/local or with Tweak Tool. I reboot and the problem is still the same. After that I tried with 3.34 (that as far as I see it the version packaged with ubuntu 19.10 and the problem persists. Then I tried pulling the code from github (dev branch) and I got a different error during make dist (pulling issues with a dependent repo). |
|
Please help us understand your issue better by using English error messages. Run `export LC_MESSAGES=C" before running any other commands. Don't worry about python, the respective parts of the README are misleading, unfortunately. The python-related setup steps are only necessary for setting up hamster itself, not for the GNOME extension, and I believe you already have hamster running. It seems you're missing the "msgfmt" tool. In my distro (SUSE), it's in the |
Sure, sorry for this: Adding "gettext" package was enough to fix the error with langs: Maybe would be nice to mention this in the README. About the issue, the extension is still not shown in gnome-extensions-local or in tweak tools.
Cheers, |
|
You need to create a directory Please provide |
|
I did it (3 times now :-)) but it never shows... I follow your README instructions step by step: Here you have teh journalctl output of the last hour: |
|
I forget to mention that I installed hamster app/service from snap (just in case it could be related). |
|
Have you restarted the GNOME shell? You have to log in / out, or restart (Alt-F2, then type "r" into the popup window). Restart doesn't work under wayland. |
|
Thanks for the tip. Alt-F2 + r worked like a charm. Now the extension is shown in the list but when enabled, does not appear in the panel. Here you have the journalctl output: |
Big step forward. The extension starts. Now you seem to have a problem with the autostart of the hamster-windows-service. Normally the extension should be able to start the hamster DBus service automatically. Now it looks as if your snap package was having an issue. Try firing up the program "d-feet", select the Session Bus at the top, and type "hams" in the search window. You should see Otherwise: Can you start "hamster" from the command line? If you do, leave the window open, and restart the GNOME shell again, does the extension work? You may also want to look |
|
What if I install the regular version instead of snap one? |
|
Try it. In theory it shouldn't matter, but the error message I quoted above points toward a problem with hamster itself. |
|
@extraymond should be able to comment on the snap package. That's not my area of expertise. |
|
@marcbria
Screenshot is d-feet(non-snap app) inspecting interfaces of hamster. |
|
@extraymond , does that mean auto-activation of the service doesn't work with snap? |
|
That's right. At the moment all snap's will behave this way, because snap's is still too strict about allowing external services to launch user session dbus-services. snap related discussion So in order to launch the snap, currently the launcher will manually wake up the dbus service before the GUI client. For desktop use cases it might be alright, but it will make extensions a bit hard to use. |
|
That's a problem for the extension, because the extension is started right after login, and by that time, the hamster-windows-service won't be started yet (Edit: I'm not certain about that), even if you create an autostart file to do that (if that's possible with snap, I don't know). The extension gives up after failing to start the DBus service. Even if the service becomes available later, the extension won't be activated again, at least not in the GNOME panel (perhaps that's a bug, but I have no idea how to fix it). So, basically, users of the snap package and the GNOME extension will need to launch hamster manually after logging in, and then type |
|
This is worth a separate issue. @marcbria, please report if manually starting hamster and |
|
Thanks for the info, that sounds really bad. So either the extension have to start hamster service manually, or it would need to have some delay after it can detect the snap has started. |
|
@extraymond, in the discussion you linked someone said that autostart does work. So that might be worth a try. I honestly don't know if autostart will be "soon enough" - at worst it might cause timing issues, and work sometimes, sometimes not. Anyway, it would open the possiblity to implement a poor man's workaround by simply waiting a few seconds in the extension. |
|
Autostart works either via snap itself or putting it in the xdg autostart directory. But you are correct that it might not be soon enough for the extension to pick it up. Another option I can think of,is that since the extension is unconfined, which can launch the snap, maybe it would make more sense to let the extension launch hamster on first run, therefore the extension will always be launched with the service ready. |
Honestly, I don't like that idea. DBus service activation is nice and clean. Replacing this with an executable forked and exec'd from a shell extension sounds ugly to me. Anyway I've forked #328 now. |
|
sorry, but I get lost in the DBus discussion. About the request of reporting in a different issue... What do you want me to report? |
|
In summary:
We're discussing this because it seems that you are running into the problem where the extension can't find the dbus-service. And we're suspecting it's due to snap. You can try the non-snap version or try the advice #326 (comment) after you can see the hamster service up and running. I believe what @mwilck mean by reporting, is to narrow down the scope of the problem, and let snap specific stuff go to #328 so people can find better issues they bump into. Did you made that work if you start the service before hand? I'm quite interested. |
|
Guys, don't expect a solution on the exension side soon. We're currently working on getting the support for recent GNOME versions merged. After that, we'll be willing to take patches, but I don't think we'll actively work on this in the near future. At least I have different priorities, both with the extension and otherwise. I don't want to reject or disappoint anyone, I just want to avoid raising expectations too high. |
|
Ok... so we just need to avoid snap. Today I need to focus in work. I will try to test your suggestion during the weekend or on Monday. Thanks a lot for your time, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Looks like is failing on ubuntu 19.10 that packages gnome-extensions 3.34.1.
How to reproduce the error:
Error
The text was updated successfully, but these errors were encountered: