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
ulauncher: 4.4.0.r1 -> 5.6.1 #81207
ulauncher: 4.4.0.r1 -> 5.6.1 #81207
Conversation
It's weird these weren't in
just reading the docs and inspecting |
It seems we have a file in the incorrect directory again
|
Yeah, I noticed some of these missing dependencies but somehow Ulauncher worked without them. I don't fully understand this.
Thank you so much for the helpful feedback so far. I'll push some more commits to this PR tomorrow :-)
|
So I tried to start it on my computer, and I get this error while running with my regular user:
When I run it as root (which is bad °o°), it works perfectly expect all extensions crash. I don't know why, but probably because it is launched from the root space instead of the user space. Let me know if you want more testing :) |
The notification error was fixed by me starting a notifications daemon, so I think that problem was on my end (i.e. it isn't a problem with the derivation). I also figured out the permissions error. Patch coming soon! |
Turns out the permission error was caused by ulauncher copying its default themes from the nix store (which is read-only). Other than that, I just added the dependencies @worldofpeace suggested then switched python36 to python3 :-) |
@aaronjanse You can actually PR that fix-permissions.patch upstream. This is a frequent bug in software where they don't chmod the file to the correct permissions, and it won't just affect NixOS (so it isn't nixos specific code) |
On that note, I've discovered a nixos specific bug 😁 I noticed this error while running the app:
this lead me to believe some sort of config file has hardcoded paths to the old output. From looking at |
If so, that's a tricky. Do you recommend patching ulauncher in this PR to address the bug? |
I'm not sure why they need an The easiest thing would be to somehow make it always be |
My understanding is that the icons are for Ulauncher search results. For example, a search for "duck" might show:
My understanding is that Ulauncher provides default icons that can be overwritten by the user. I assume that if Ulauncher updates its default icons, users relying on the default icons should have their icons updated. So yes, |
Is there any existing Nix derivation (or documentation) you recommend I look at for learning how to use |
I've found the code https://github.com/Ulauncher/Ulauncher/blob/42b83349406c42ee8d23dc7eae1d2a9d42ba6937/ulauncher/config.py#L45. The code to do this would be https://github.com/Ulauncher/Ulauncher/blob/42b83349406c42ee8d23dc7eae1d2a9d42ba6937/ulauncher/config.py#L26 but with |
Hmm, my understanding is that putting files in If so, should the |
As a side note, I do think it would be nice to have a module for Ulauncher. I assume most people using Ulauncher would want it running in a systemd service. |
No it doesn't. That is because it's one of the directories that automatically gets linked from |
Hmm. On my system, EDIT: ohhh, I think you meant to say it's only linked when the package is put in
Hmm, I guess I don't understand. Should I patch ulauncher so that it, instead of turning |
Ohh, I see what you mean. If the wrapper adds this entry
that would defeat the purpose if we choose that entry. But XDG_DATA_DIRS is a list (in pyxdg)
and one of those entries on NixOS will always be So similar to how this code is
we should add something to filter out |
Hum I tested the application, and it seems really good :) I get a new error though. It seems that the python
|
Would you mind providing reproduction steps for the Also, I think I just fixed the |
So I tried to reproduce again but on a different computer. Sadly, it is a different setup on KDE and I get different errors that block when I want to open the configuration window.
The first line is when I start the application itself. The 2 lines in the middle are print in the console when I open the configuration window. And finally the last line is related to this issue I guess: https://source.puri.sm/Librem5/OS-issues/issues/17 Tonight (french timezone), I'll try to reproduce the |
Sorry for the delay. I'll be able to work on this tomorrow afternoon. |
The extensions error should be fixed. I'm not sure how to resolve the pixbuf warning but everything seems to be working afaict. |
Everything works well for me on Gnome, but it is still broken on my KDE. Still the same error :) |
Hmm. I just installed KDE and could not reproduce the issue. Could you try deleting/moving the ulauncher state ( |
I still get the same error after deleting both folders. But I start to think it is my configuration since I have issues with other GTK application. I guess there is something wrong somewhere. |
@aaronjanse I got to making the patch that does what I described 81ae12d, though it's not the best. You will get an exception if you use the package outside nixos, perhaps we can fallback to the oldcode. |
Thank you @worldofpeace! Is there anything else that needs to be done to this PR before it's ready to be merged? |
@aaronjanse The history just needs to be cleaned up, but I think it should be good. |
81ae12d
to
276bfbc
Compare
The git history has been cleaned 👍 |
Motivation for this change
Package update request #81178
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)For some reason, I got the following non-fatal error upon first run (or
rm -rf ~/.cache/ulauncher_cache ~/.config/ulauncher
), which didn't seem to break anything:Also, when changing the theme, I get a permission error for a cache file. This is fixed by running with
sudo
, but, of course, running as root doesn't sound like a good idea.Other than the issues listed above, Ulauncher seems to work fine.
I don't know what to do about the test in the derivation and the
disabled
attribute.