On Tue, 02 Feb 2021 at 17:06:15 +0100, Guillem Jover wrote:
> This also affects msmtp when using its Secret Service support. Its
> debugging output is not great by default (need to send a patch for
> that), but once trapping the GError from the libsecret calls, it
> mentions that it cannot spawn a
Control: affects -1 msmtp
On Tue, 2021-02-02 at 09:20:44 +, Simon McVittie wrote:
> On Mon, 01 Feb 2021 at 19:19:41 -0500, Charles Malaheenee wrote:
> > But I'm asking myself - is it only gnome-keyring affected or this
> > "security hardening" could break other GNOME/MATE parts?
>
> The secur
Processing control commands:
> affects -1 msmtp
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring on some systems since GLib 2.66.4-2
Added indication that 981420 affects msmtp
--
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tra
On Mon, 01 Feb 2021 at 19:19:41 -0500, Charles Malaheenee wrote:
> But I'm asking myself - is it only gnome-keyring affected or this
> "security hardening" could break other GNOME/MATE parts?
The security hardening change affects programs that are linked to GLib,
and are either setuid or have elev
Hello Simon,
Thank you for your efforts!
> Do you have the dbus-user-session package installed?
I had to install it. Indeed, it helps - now gnome-keyring is working fine with
latest package version of libglib.
> If you rely on the ability to have a separate D-Bus session bus per
> X11 display
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305
On Sun, 31 Jan 2021 at 18:53:09 -0500, Charles Malaheenee wrote:
> In journalctl there are a lot messages from systemd or dbus-daemon, like
> "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service
> 'or
Processing control commands:
> forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/glib/-/issues/2305'.
--
981420: https://bugs.debia
Hello Simon,
Thank you for the attention to this bug!
Our DE is Mate. Probably, the problem is related to the mix of components ?
Here is the output (I do not remember to have to change the permissions of
gnome-keyring-daemon):
ls -l /usr/bin/gnome-keyring-daemon
-rwxr-xr-x 1 root root 1143712
On Sun, 31 Jan 2021 at 11:45:08 +, Simon McVittie wrote:
> I suspect I know what change triggered this: it'll be the security hardening
> imported from the upstream glib-2-66 branch in 2.66.4-2. However, I couldn't
> reproduce this failure to unlock in a test VM.
I've prepared several sets of
Processing control commands:
> severity -1 serious
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login
keyring
Severity set to 'serious' from 'important'
--
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.d
10 matches
Mail list logo
