[snap] kwallet not detected as password store

Bug #1847470 reported by Olivier Tilloy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
High
Olivier Tilloy

Bug Description

(initially reported at https://forum.snapcraft.io/t/call-for-testing-chromium-browser-deb-to-snap-transition/11772/8)

« The test command¹ you use to detect backend:

dbus-send --session --dest=org.freedesktop.secrets /org/freedesktop/secrets --print-reply org.freedesktop.DBus.Properties.GetAll string:'org.freedesktop.Secret.Service' >/dev/null 2>&1

fails o my system (Ubuntu 19.04 + KDE session + kwallet) saying that nothing provides org.freedesktop.Secret.Service and chromium fallbacks to plain backend (losing my passwords). When I add --password-store=kwallet to desktop file command it works correctly.

So current approach for backed detection is broken in my case (maybe in general for kwallet). Maybe it’s possible to test also kwallet equivalent of that command however I don’t know what i should be. »

¹ https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=stable#n45

Tags: snap
Olivier Tilloy (osomon)
tags: added: snap
Revision history for this message
Olivier Tilloy (osomon) wrote :

I can reliably reproduce the problem in a Kubuntu 18.04.3 VM.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Olivier Tilloy (osomon)
Revision history for this message
Olivier Tilloy (osomon) wrote :

The following test should do the trick:

dbus-send --session --dest=org.kde.kwalletd5 /modules/kwalletd5 --print-reply org.freedesktop.DBus.Properties.GetAll string:'org.kde.KWallet'

Changed in chromium-browser (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Olivier Tilloy (osomon) wrote :
Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Committed
Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.