-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
0.5.0 uninstallable on Qubes OS / Debian Testing VM: "xdg-desktop-menu: No writable system menu directory found" #848
Comments
The problem is a known bug in xdg The workaround: and to start the client: |
Yup, mkdir /usr/share/desktop-directories/ Still think a nit like a menu problem should not cause the install to hard-fail, but neither do I know much about Debian package building and the constraints thereof. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still broken, and the workaround still works. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Also happening in Debian based distributions. Please re-open. |
This problem is still here after 5 years... can't the desktop file (which is unused as per the README) be removed? It's causing major pain to install on qubes; it breaks the fundamental file layout concepts of qubes. The .deb package should be installable in the TemplateVM, not the AppVM. |
Qubes OS is a fully virtualized OS, ie. everything is a virtual machine, so Bisq must install in one of those VMs. In my main Qubes Debian Testing VM, when I
dpkg -i Bisq-64bit-0.5.0.deb
(even after the addition of --force-all) I get this result:
Preparing to unpack Bisq-64bit-0.5.0.deb ...
Removing shortcut
xdg-desktop-menu: No writable system menu directory found.
dpkg: warning: subprocess old pre-removal script returned error exit status 3
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking bisq (0.5.0) over (0.5.0) ...
Setting up bisq (0.5.0) ...
Adding shortcut to the menu
xdg-desktop-menu: No writable system menu directory found.
dpkg: error processing package bisq (--install):
subprocess installed post-installation script returned error exit status 3
Errors were encountered while processing:
bisq
This was a bit shorter the first time, the above is a retry but ends with the same result: the package is in (according to the package manager) a not-fully-installed state. It must be removed before any other packages may be installed or upgraded in the future, ergo it must be removed.
--force-all does not get around this, and I don't have a work-around at the moment. Note that the same package installs fine for me on exactly the same revision of hard-metal Debian Testing.
Menu entries are an entirely secondary and unimportant feature, perhaps they should fail with just a warning and not break the whole install process?
The text was updated successfully, but these errors were encountered: