falkon works for me.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
Matching subscriptions: kubuntu-bugs, kubuntu-bugs, kubuntu-bugs, kubuntu-bugs,
kubuntu-bugs, kubuntu-bugs, kubuntu-bugs, kubuntu-bugs
** Changed in: akregator (Ubuntu)
Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore)
** Changed in: digikam (Ubuntu)
Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore)
** Changed in: kontact (Ubuntu)
Assignee: (unassigned) => Scarlett Gately Moore
Yes for the appimages that are affected they should be reported
upstream. There are some things that upstream can do to make appimages
work under the restriction, ideally they would do it dynamically based
on whether the user namespace is available than just based on distro
which is the quick fix
We have finally found the problem (thanks Scarlett Moore). The apparmor
profiles of Akregator, Kontact and Digikam have x86_64-linux-gnu
hardcoded in the path for QtWebEngineProcess. So reassigning to those 3
packages.
** Package changed: qtwebengine-opensource-src (Ubuntu) => akregator
(Ubuntu)
You have been subscribed to a public bug:
kontact cannot start after upgrade to Noble on arm based Lenovo ThinkPad
X13s:
Error Message in terminal:
LaunchProcess: failed to execvp:
/usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess
LaunchProcess: failed to execvp:
Yep, this is fine. I just wanted to make it clear for others, because
one of the comment above might be misleading and even though I know the
area of the code impacted by userns, I was actually thinking you got a
fix landed on AppArmor side to avoid the need for a dedicated profile.
AppImage
