Describe the bug
I discovered today a really fun feature: installing web apps in chromium. For instance, if you browse to https://xournal.online/ on chromium, you can install the app locally:

Once installation is done, the website now runs as a separate application. You also should see on your desktop:

and in chrome://apps/ the app you installed. If you directly launch the app from chrome://apps/ it works directly. However, if you click on the app from the desktop, nothing happens. When inspecting the .desktop file, the reason is clear: it contains a line pointing to the unwrapped chromium:
Exec=/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium --profile-directory=Default --app-id=ncokflffjgpjncjjifkomecgbombmdgj
Instead, it should point to the wrapped chromium.
Steps To Reproduce
Steps to reproduce the behavior:
- Go to https://xournal.online/
- Install the app (button in url bar)
- Launch it from the shortcut added in your desktop (at least appears in KDE plasma)
How to fix it (edited)
I think the issue comes from this line in the wrapper script:
exec "/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium" "$@"
To ensure the name of the executable is propagated properly, I guess it should instead be something like:
exec -a "$0" "/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium" "$@"
Notify maintainers
@primeos @danielfullmer @Frostman @thefloweringash
Describe the bug
I discovered today a really fun feature: installing web apps in chromium. For instance, if you browse to https://xournal.online/ on chromium, you can install the app locally:
Once installation is done, the website now runs as a separate application. You also should see on your desktop:
and in chrome://apps/ the app you installed. If you directly launch the app from chrome://apps/ it works directly. However, if you click on the app from the desktop, nothing happens. When inspecting the
.desktop file, the reason is clear: it contains a line pointing to the unwrapped chromium:Instead, it should point to the wrapped chromium.
Steps To Reproduce
Steps to reproduce the behavior:
How to fix it (edited)
I think the issue comes from this line in the wrapper script:
To ensure the name of the executable is propagated properly, I guess it should instead be something like:
Notify maintainers
@primeos @danielfullmer @Frostman @thefloweringash