gnome-keyring-daemon crashed with signal 5 in g_thread_join()

StacktraceTop:g_thread_join_posix_impl (thread=0x959d884)
IA__g_thread_join (thread=0x959d868)
gck_timer_shutdown () at gck-timer.c:137
gck_module_finalize (obj=0x95a2008) at gck-module.c:611
gck_user_module_finalize (obj=0x95a2008)

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=590004

Upstream is asking for more information, may someone please attach the output of gnome-keyring-daemon this happens. This may be in /var/log/auth.log or ~/.xsession-errors ; Thanks in advance.

Adding files as requested, these logs follow my duplicate bug report 405884.

1) ~/.xsession-errors

2) /var/log/auth.log

Note time of crash in logs around 4:17pm on 28th July. Hope this gives you the info required.

Hi,

I attach an abstract from my /var/log/authlog for all of today's activity.

I also attach ~/xsession-errors in its entirety - all 2MB of it.

Kind regards,
Bert

Pedro Villavicencio wrote:
> Upstream is asking for more information, may someone please attach the
> output of gnome-keyring-daemon this happens. This may be in
> /var/log/auth.log or ~/.xsession-errors ; Thanks in advance.
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Triaged => Incomplete
>

Hi,

Further to mine of a few minutes ago, I attach a more sensible abstract
of my ~/.xsession-errors file.

I hope you find it more useful.

Kind regards,
Bert

Pedro Villavicencio wrote:
> Upstream is asking for more information, may someone please attach the
> output of gnome-keyring-daemon this happens. This may be in
> /var/log/auth.log or ~/.xsession-errors ; Thanks in advance.
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Triaged => Incomplete
>

/var/log/auth.log
Aug 1 12:35:34 greg-desktop gnome-keyring-daemon[3371]: mount_added: assertion `identifier' failed

Affects me also, report sent.

Affects me too...
the necessary info has been [/var/log/auth.log or ~/.xsession-errors]

This crash happened as I was mounting a shared VirtualBox folder. I'm running UNR Karmic as the guest OS. Up-to-date Jaunty is the host OS for Sun VirtualBox v3.0.4 r50677 with Guest Additions (e.g. accelerated video).

I think this crash happens when it's in the mood.

Telic wrote:
> This crash happened as I was mounting a shared VirtualBox folder. I'm
> running UNR Karmic as the guest OS. Up-to-date Jaunty is the host OS for
> Sun VirtualBox v3.0.4 r50677 with Guest Additions (e.g. accelerated
> video).
>
>

This just happened to me after i ran the update program. karmic netbook remix on macbook pro.

I restarted after updating the system and I got the crash report.

This just happened while browsing the Internet.

Installing Karmic for the first time and it crashed.

I'm using Karmic since alpha 1. After one of the "big updates" this error started to pop every single time I started my computer.

Crashes on login every time I start up.

I upgraded to Karmic 9.10 Alpha and this bug follows me around everywhere on every boot up.

this bug affects me too
karmic 9.10 AMD64

Affects me as well. Asus Eee PC 1000h

Affects me too.
Karmic Alpha 4 i386.
Daemon crashes in 10-20 seconds after UbuntuOne client start.

I upgraded to Karmic AMD64, it crashes every time I log in.

The bug has been confirmed, triaged, sent upstream, there is no need to keep adding comment to say you get the issue

(you can also add the button below the table to say that without spamming all the subscribers)

volume icon turned to muted when I restarted my system and when i tried to change it, this crash happened

I have a similar issue. My volume icon is always muted. When I increase the
volume, it goes to back minimum (mute) in a couple mins.

On Sat, Aug 22, 2009 at 3:47 PM, Sunil U <email address hidden> wrote:

> volume icon turned to muted when I restarted my system and when i tried
> to change it, this crash happened
>
> --
> gnome-keyring-daemon crashed with signal 5 in g_thread_join()
> https://bugs.launchpad.net/bugs/405667
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME keyring services: New
> Status in “gnome-keyring” package in Ubuntu: Triaged
> Status in gnome-keyring in Ubuntu Karmic: Triaged
>
> Bug description:
> Binary package hint: gnome-keyring
>
> I wasn't doing anything particular, just using Nautilus and the error
> appeared on the screen.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Jul 28 17:10:17 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/gnome-keyring-daemon
> Package: gnome-keyring 2.27.5-0ubuntu1
> ProcCmdline: gnome-keyring-daemon --start
> ProcEnviron:
> LANG=en_AU.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
> Signal: 5
> SourcePackage: gnome-keyring
> StacktraceTop:
> ?? () from /usr/lib/libgthread-2.0.so.0
> g_thread_join () from /usr/lib/libglib-2.0.so.0
> ?? ()
> ?? ()
> ?? ()
> Title: gnome-keyring-daemon crashed with signal 5 in g_thread_join()
> Uname: Linux 2.6.31-4-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev
> plugdev sambashare tape vboxusers video
>

--
Love,
James

affecting my 9.10 amd64 too

affected me too in 9.10 alpha 4 i386

affected after startup gnome

Linux 2.6.31-6-generic #26-Ubuntu SMP Fri Aug 21 17:48:16 UTC 2009 i686 GNU/Linux
9.10 Alpha 4

Started up the computer with the latest 2.6.31-7 Kernel on Karmic 64 Alpha 4 all updates applied and got these crashes at startup.

It just happened when i force to terminate a file duplication by click the cancel key.

affecting my 9.10 amd64 too

yep - I have to subscribe - for each boot, same bunch of problems - Karmic alpha 4

Just ran a partial upgrade with Karmic alpha 4 and got crash report.

the bug has been fixed upstream now

This bug was fixed in the package gnome-keyring - 2.27.90-0ubuntu2

---------------
gnome-keyring (2.27.90-0ubuntu2) karmic; urgency=low

  * debian/patches/90_git_change_rework_signal_handler.patch:
    - git change to rework signal handlers, should fix a crasher at logout
      (lp: #405667)

 -- Sebastien Bacher <email address hidden> Mon, 31 Aug 2009 11:21:58 +0200

I have gnome-keyring 2.27.90-0ubuntu2 and i just got this error also. I am using Karmic with an eeepc 1101ha.

I am not sure to wich status change, so I took Confirmed. If this is not the right one, please tell me for further reference.

Thank you.

> I have gnome-keyring 2.27.90-0ubuntu2 and i just got this error also.

did you restart your session twice since the upgrade? one to make sure to run the new version and one to get the crash?

No. I mean, I am sure i have restarted machine at least once after update, but I did not checked twice. I have rebooted now again, and there is no error at all. If it appears i will come back here.

closing the bug then you can reopen if you get it again now