Automatically unlocking the keyring works and stored credentials for
other applications are available too. Thanks :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Unlocking SSH keys with the passphrase that is saved to gnome-keyring
now works too. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails
This bug was fixed in the package gnome-shell - 46.0-0ubuntu5
---
gnome-shell (46.0-0ubuntu5) noble; urgency=medium
[ Daniel van Vugt ]
* Drop loginDialog-Create-footer-container.patch - it's buggy and still
under active development (LP: #2060893)
[ Marco Trevisan
Can you give me an answer to my question if this is related or if I
should file a new bug?
https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/2060575/comments/20
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring
Please share the link to the commit code.
Usually how long it takes after a commit is pushed until the new package
is available for upgrade in the repo?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
> I believe that the evolution mail program and google accounts are to
blame.
Those programs are just using the keyring to store credentials. The
prompt is only visible if something tries to get a secret.
A fix has been uploaded now
https://launchpad.net/ubuntu/+source/gnome-shell/46.0-0ubuntu5
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco
I believe that the evolution mail program and google accounts are to
blame.
The problem went away for me after I deleted my keyring and switched
from evolution to thunderbird.
Trying to (re-)add a mail account to evolution immediately brings the
problem is back.
--
You received this bug
Got it, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock login keyring after recent
updates in noble
Status
Allen, gnome-keyring is not the package that needs to be updated for
this issue. It's gdm3.
https://launchpad.net/bugs/2060575
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
Same issue here. I don't understand the status, "Won't fix"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock login
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
I noticed another problem which makes me wonder if it's related to this.
When you unlock the keyring yourself it still fails to unlock ssh keys.
If you do:
$ export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh
it starts working again.
Is this related or should I report a separate bug?
--
You
This is unlikely to be a problem in Gnome Keyring, as SDDM has no
problem unlocking in on log-in. I'm therefore adding here GDM3.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** No longer
Ok, I understand. However, wifi passwords are stored by the netplan.io
package instead of in the gnome-keyring.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
@jbicha sorry if I added noise. But the WiFi problem only happens with
secured WiFi networks, not open ones. It seemed plausible that they are
related, as the password for the WiFi network needs to be retrieved
somewhere (the keyring, I assumed). But I will report a different bug
report then.
--
Please don't leave comments here to mention only that you are
experiencing this issue. It is already known that this bug affects
Ubuntu 24.04 LTS.
Nicolás, this bug has nothing to do with Wifi.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I am having the same problem on 24.04 beta
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock login keyring after recent
I am having the same problem after upgrading from 23.10 on a Thinkpad
T14 AMD Gen 2. Another problem I am having is that WiFi is not
automatically connected after log-in. I suppose it is related to this
bug, is anyone else having this issue?
--
You received this bug notification because you are
I can confirm the behaviour after a recent upgrade from mantic to noble
and has also been reported in https://discourse.ubuntu.com/t/noble-dev-
branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt-
install-work-but-apt-upgrade-fail/43979
Another oddity is, that I seem to have to
Same issue on an MSI b350m bazooka Mobo with Ryzen 5600 and rtx 3090
(proprietary drivers, v550)
Fresh install of 24.04 beta
I believe this bug is related to render hangs and DE crashes I've been
experiencing at login. If the bug is circumvented by changing to a blank
password for the keyring,
Same issue after upgrading from 23.10 on a Lenovo Legion 5 15ARH7H
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock
I'm also experiencing this issue, although my keyring still exists under
~/.local/share/keyrings/login.keyring and after authenticating using the
popup after logging in, all my passwords can be seen when starting
"seahorse". The only problem I'm experiencing is that the keyring
doesn't
I've just updated my password (unrelated to the issue) and now I only
get one popup to unlock the keyring after login - the gnome full-screen
one. The non-gnome-shell one has gone away.
Attached is a screenshot of the one that is still there.
** Attachment added: "popup1.png"
This affects me on a Microsoft Surface Pro 7+ which I upgraded in-place
from 23.10 to 24.04-beta with `do-release-upgrade -d` yesterday.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
I have the same issue. Keyring and Login passwords are identical but
keyring `Login` does not get unlocked automatically on startup. I
noticed it couple of days ago after some updates for my 22.04 devel
--
You received this bug notification because you are a member of Desktop
Packages, which is
Yeah, I was just testing something else and did a couple of installs in
VirtualBox and the issue didn't come up (agreed that VMs might behave
very differently). Could this somehow be vendor related? I'm running a
ThinkPad E14 AMD Gen 3 - this could also just be a coincidence and the
fact, that
But it can't be affecting all installations. I installed one or two dailies
before the beta. The error appeared after an upgrade. Currently fully upgraded.
Maybe just re-install... It's annoying to type the password three times at each
login. :D
ThinkPad P14s AMD Gen 3
--
You received this
I'm having the same issue after upgrading to the noble beta yesterday:
ProblemType: Bug
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2022-04-23 (720 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Package: gnome-keyring 46.1-2build1
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically
It seems that the usual password keyring called Login is not
automatically created in gnome-keyring. In fact there are no credentials
of any kind in there on logging in after a clean install.
If you change your password via the control panel, the login keyring is
then created.
However, when you
** Tags added: rls-nn-incoming
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
35 matches
Mail list logo
