Arch Linux

lmello

Member

From: Brazil

Registered: 2012-11-06

Posts: 300

*possibly* dangerous gdm message?

Hi, everytime gdm comes in my journal spits this:

May 15 22:00:42 maxwell gdm-password][3925]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
May 15 22:00:42 maxwell gdm-password][3925]: gkr-pam: couldn't unlock the login keyring.
May 15 22:00:42 maxwell gdm[1362]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Suggestions? There *is* a serious bug I reported both on Arch's and GNOME's that *might* have something to do with it.

---

Fundamental Axiom of the Universe (aka Murphy's Law): Whatever can go wrong, will go wrong.
First Digital Deduction: Nothing obeys Murphy's Law so well as computers.
Second Digital Deduction: Everything go wrong at least once.
Third Digital Deduction: Things go wrong even when there's absolutely no possibility of anything go wrong.

olantwin

Member

Registered: 2014-05-21

Posts: 33

Re: *possibly* dangerous gdm message?

I have the same error messages, reliably replicatable by bringing up gdm through locking etc.
Have not encountered any consequences though. gnome-keyring seems to work absolutely fine.

May 21 11:31:39 xkoba gdm-password][26227]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
May 21 11:31:39 xkoba gdm-password][26227]: gkr-pam: couldn't unlock the login keyring.
May 21 11:31:39 xkoba gdm[365]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Have you found out anything else? The problem has been around for at least 2 weeks or so, but since it doesn't seem to have any other consequences it's hard to be sure.