Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Committed
|
Medium
|
Nathan Teodosio |
Bug Description
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to decrypt its password store.
This makes all stored passwords unavailable as soon as the system is upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-------
[5362:5362:
[5362:5362:
[5362:5362:
[5362:5362:
[5362:5362:
[5362:5362:
-------
Followed by hundreds of messages as the following:
-------
ERROR:login_
-------
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to the patterns:
-------
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https:/
#
dbus (receive, send)
bus=session
path=
interface=
peer=
dbus (receive, send)
bus=session
path=
interface=
peer=
-------
I hope that at least this report may be found by other people running into the same trouble I just did...
description: | updated |
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
assignee: | nobody → Nathan Teodosio (nteodosio) |
Changed in chromium-browser (Ubuntu): | |
status: | Triaged → Fix Committed |
Hi Gunter, thanks for the report. From what I understand Plasma 6 is not (and will not be) available in Ubuntu 24.04, did you get it in by building it from source or by using some PPA? I ask because it would be nice to reproduce your observations before incorporating a fix.
Many thanks for raising this way before Plasma 6 is released to Ubuntu, this way we can assure this bug is gone by the time Plasma 6 becomes officially supported in Ubuntu.