Thanks all!
I uninstalled my flatpak apps, flatpak, and dbus-user-session... then
rebooted and all's well. Uninstalling with --purge seems to have taken
care of the /etc file markuslet pointed to.
$ flatpak list
$ flatpak --system uninstall com.xamarin.MonoDevelop
$ flatpak --system uninstall
The Status dropdown is for "Affects" and flatpak affects this issue (not
that it's the sole culprit).
** Changed in: flatpak (Ubuntu)
Status: Invalid => Confirmed
** Also affects: dbus
Importance: Undecided
Status: New
--
You received this bug notification because you are a
FWIW, my problem started after installing PPAs about a week before I
first posted here (June 17). I just checked my /etc/apt/sources.list
and it was last modified June 10. Perhaps it is coincidence... but
right when some PPAs went in, my problem started.
--
You received this bug notification
@MikeRushton... do you have any PPAs installed on your machines without
flatpak?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
Status
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
The problem really is isolated to gnome-keyring (as OP and others
stated).
Here's my workaround for Chrome... it might help others (like Photon).
But in the end it is only a workaround. It does demonstrate that if you
bypass the display manager (lightdm, gdm) triggering the gnome-keyring
for
For reference... https://github.com/karma-runner/karma-chrome-
launcher/issues/76
** Bug watch added: github.com/karma-runner/karma-chrome-launcher/issues #76
https://github.com/karma-runner/karma-chrome-launcher/issues/76
--
You received this bug notification because you are a member of
Maybe a clearer capture of something amiss... logging in and out and in
repeatedly causes the keyring daemon process to be started again and
again (as lightdm and as the user). Please see attached.
** Attachment added: "log_in_and_out.txt"
I uncovered another problematic side effect but I am unsure of the
significance; perhaps this will trigger an idea for someone
There are three user accounts on my box. Here's a flow:
1) Reboot box
2) Sign in as user 1
3) Examine running processes (as MikeD mentioned in #33) and observe two
I agree with comments #25 and #26. It's likely a red herring, but this
issue arose for me right after I installed the flatpak PPA and a pile of
mono/M$ stuff. I still figure that those actions are orthogonal, but
just in case everyone else recently installed similar stuff or a new PPA
or...
--
11 matches
Mail list logo
