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

Wike does not run in Ubuntu 24.04: Failed to fully launch dbus-proxy #181

Open
archisman-panigrahi opened this issue Apr 10, 2024 · 2 comments

Comments

@archisman-panigrahi
Copy link
Contributor

Wike (deb package/compiled version) does not run in Ubuntu 24.04 possibly due to some interference between apparmor and webkit.

$ wike

(process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
bwrap: setting up uid map: Permission denied

** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: Child process exited with code 1
Trace/breakpoint trap

A similar error is occuring in Foliate johnfactotum/foliate#1262


A workaround is to create the file /etc/apparmor.d/wike with the following contents:

# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"

abi <abi/4.0>,
include <tunables/global>

profile wike /usr/bin/wike flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists <local/wike>
}

Then run sudo systemctl restart apparmor.service


The flatpak most likely works without any error.

@hugolabe
Copy link
Owner

Sorry I can't help with this. I have no knowledge about deb packaging.

@archisman-panigrahi
Copy link
Contributor Author

Sorry I can't help with this. I have no knowledge about deb packaging.

It is a bug introduced by new changes in apparmor. It is an apparmor bug. Way too many apps are affected by this, and the version of Wike shipped with Ubuntu is also affected.

Just wanted to mention that the issue is present in Ubuntu 24.04, and there is the workaround until a fix is released.

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

2 participants