[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2010-03-18 Thread Vish
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2010-02-27 Thread Omer Akram
There have been many changes to gwibber since this bug was reported can any one using the development release or at minimum gwibber 2.0 please confirm if this is still an issue. ** Changed in: gwibber (Ubuntu) Status: Triaged = Incomplete -- gwibber crashed with NoKeyringDaemonError in

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-07-04 Thread Alexander Sack
setting upstreamed bugs to Triaged ** Changed in: gwibber (Ubuntu) Importance: Undecided = Medium ** Changed in: gwibber (Ubuntu) Status: Confirmed = Triaged -- gwibber crashed with NoKeyringDaemonError in get_data() https://bugs.launchpad.net/bugs/344426 You received this bug

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-04-07 Thread azeey
I just upgraded to Jaunty and have the same issue. I ran the gnome-keyring-daemon process as a foreground process and tried to change my twitter password setting in gwibber. The daemon aborted with: gnome-keyring-daemon: egg-secure-memory.c:324: sec_check_guards: Assertion

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-04-06 Thread Juanje Ojeda
This happens to me, but I think the problem was the gnome-keyring didn't launch at the begining of the session. Once I've launched the gnome-keyring, the Gwibber let me create and use the accounts. -- gwibber crashed with NoKeyringDaemonError in get_data() https://bugs.launchpad.net/bugs/344426

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-04-06 Thread Sebastien Bacher
the issue doesn't seem to be with gnome-keyring but rather with how gwibber use it ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-keyring (Ubuntu) Status: New = Invalid -- gwibber crashed with NoKeyringDaemonError in get_data()

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-04-06 Thread Mathieu Marquer
But with me gnome-keyring is actually running. $ ps aux | grep keyring root 22752 0.0 0.0 67788 1156 ?S00:02 0:00 gnome-keyring-daemon When launching gwibber : $ gwibber ** (gwibber:23682): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET:

[Bug 344426] Re: gwibber crashed with NoKeyringDaemonError in get_data()

2009-04-06 Thread Andrew Barilla
I did a fresh install of Arch Linux with Gnome 2.26 and this same error occurred. It appears that it gnome-keyring-daemon doesn't start correctly in Gnome 2.26 and this might now be distro specific. -- gwibber crashed with NoKeyringDaemonError in get_data()