This is now in the stable channel. Thanks for the feedback!
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Ubuntu 18.04 clean install.
Installed chromium snap from stable channel and found the problem
(browser worked till I entered my google account and saved password on
keyring).
Fond this bug (from https://forum.snapcraft.io/t/call-for-testing-
chromium-65-0-3325-146/4390/21 ), changed to candidate
Hello Olivier, today(27.04) i have installed the new Ubuntu 18.04 and
Chromium. After i have logged into the Google-Account, i cant start
chromium. I have read the thread, and i understand that you have a fix.
I dont know where and how to insert which code. Is the fix already in
the new chromium
The fix is in the candidate channel for all supported architectures now.
I'll leave it there for a couple of days to give people an opportunity to test
and report, after which I will promote to the stable channel in no issue is
raised.
--
You received this bug notification because you are a
For reference, the following commits fix the issue:
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snappy-
packaging/commit/?id=5f40c7e269a6990b68669229cf4b7db2c41096bc
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snappy-
Thanks for testing!
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1763829
Title:
For me, chromium starts now as intended. Thanks for the fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1763829
Title:
[snap] chromium won't start after logging in to
Revision 277 in the candidate channel (amd64) has the fix, please test
with
snap refresh chromium --candidate
and add your feedback here. Thanks!
(note: a glitch in the store means publication has to be manually
approved for now, so builds for the other supported architectures will
be
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1763829
Title:
[snap] chromium won't start
Unfortunately bug #1763641 is blocking publication in the store, I'm
working with store people to try and resolve this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1763829
I have pushed both fixes to the git repository, a build is scheduled and
as soon as it's done I will publish it to the candidate channel (I will
add a comment here when it's ready for testing).
--
You received this bug notification because you are a member of Desktop
Packages, which is
Is the chromium snap in the stable branch already containing the
libsecret-1.so.0?
Would it be possible to push the snap with the libsecret-1.so.0 and the wrapper
in the candidate channel so that the users would be able to test it?
--
You received this bug notification because you are a member
Calling the following in the wrapper and checking for the return code
should do the trick:
dbus-send --session --dest=org.freedesktop.secrets
/org/freedesktop/secrets --print-reply
org.freedesktop.DBus.Properties.GetAll
string:'org.freedesktop.Secret.Service'
--
You received this bug
In chromium, in function os_crypt::SelectBackend()¹, when GNOME is
detected, the backend is SelectedLinuxBackend::GNOME_ANY, which is
documented as "GNOME_KEYRING or GNOME_LIBSECRET, whichever is
available". This piece of code doesn't seem to automatically fall back
to the basic (unencrypted)
I wonder whether, as a workaround, the snap wrapper that launches
chromium could detect whether the password-manager-service interface is
connected, and if not add the --password-store=basic command-line
option.
--
You received this bug notification because you are a member of Desktop
Packages,
Full wrapper:
#!/bin/sh
PASSWORD_STORE=gnome
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
if [ "$?" -ne "0" ]; then
PASSWORD_STORE=basic
fi
exec
The following verbose log suggests that libsecret is missing from the
snap:
[8021:8236:0413/194753.217679:VERBOSE1:key_storage_util_linux.cc(53)] Password
storage detected desktop environment: GNOME
[8021:8236:0413/194753.218064:VERBOSE1:libsecret_util_linux.cc(101)] Could not
load
17 matches
Mail list logo
