Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#32317 - [gnome-keyring] freezes with gnome online accounts

Attached to Project: Arch Linux
Opened by Josh (iqpi) - Wednesday, 31 October 2012, 09:23 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 23 July 2013, 15:16 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

[DESCRIPTION]
gnome 3.6 just updated, I tried to add my gmail accounts to gnome onlince accounts to sync contacts, calendar, mail and all that stuff.
I follow the steps over the google app, and finally, when it is done, gnome-keyring asks for the google account password

If you fail typing it, it warns you were wrong. But, if you success with the password it freezes and you cannot use the graphical enviroment. It is needed to go into a terminal
and kill the process.

[ADDITIONAL INFO]
* package version(s): gnome-keyring 3.6.1-1
* config and/or log files etc.

[GDB STACKTRACE]
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/gnome-control-center...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnome-control-center
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3400.1-gdb.py", line 9, in <module>
from gobject import register
File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffd0851700 (LWP 2837)]
[New Thread 0x7fffcb3b8700 (LWP 2850)]
[New Thread 0x7fffcabb7700 (LWP 2851)]
[New Thread 0x7fffca1b0700 (LWP 2852)]
[New Thread 0x7fffc99af700 (LWP 2853)]
[New Thread 0x7fffc90ae700 (LWP 2854)]
[New Thread 0x7fff7b997700 (LWP 2855)]
[New Thread 0x7fff7ac37700 (LWP 2856)]
[New Thread 0x7fff7a436700 (LWP 2857)]
[Thread 0x7fff7a436700 (LWP 2857) exited]
[Thread 0x7fffcabb7700 (LWP 2851) exited]
[Thread 0x7fffca1b0700 (LWP 2852) exited]
[Thread 0x7fff7ac37700 (LWP 2856) exited]
[New Thread 0x7fff7ac37700 (LWP 2859)]
[New Thread 0x7fffca1b0700 (LWP 2860)]
[Thread 0x7fffca1b0700 (LWP 2860) exited]
[New Thread 0x7fffca1b0700 (LWP 2861)]
[Thread 0x7fff7ac37700 (LWP 2859) exited]
[Thread 0x7fffca1b0700 (LWP 2861) exited]
/*
* At this point it freezes and there is no
* way to stop it unless you go to tty and
* try to take up the control.
* I've tried to stop manually gdb, but it is possible
* I don't know how gdb works, so finally I exited with
* Control C
*/
end
quit
exit
end
quit
exit
fin
quit
^C
Program received signal SIGINT, Interrupt.
0x00007ffff5b6418d in poll () from /usr/lib/libc.so.6
(gdb) quit
A debugging session is active.

Inferior 1 [process 2833] will be killed.

Quit anyway? (y or n) y

/* End of the stacktrace*/

[STEPS TO REPRODUCE]
1- Open gnome online accounts
2- Add a new google account
3- Follow the steps of the google's app
4- Gnome-keyring will ask for the google account password to add it to the keyring.
5- Here you have your beautiful freeze.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 23 July 2013, 15:16 GMT
Reason for closing:  No response
Comment by Jairo Alonso Velásquez (JohnnyDeacon) - Thursday, 01 November 2012, 13:41 GMT
Works fine for me, I upgrade form 3.4 to 3.6
Comment by alex (kabolt) - Saturday, 03 November 2012, 10:57 GMT
same problem but with the addition that everything freezes if you are also asked to enter passphrase for an encrypted device (see report  FS#32116 ).
It seems as if something isn't threadsafe what should be threadsafe.
Comment by David Glanzman (limescout) - Saturday, 03 November 2012, 21:04 GMT
works fine for me, gnome 3.6.1 on x86_64
Comment by Greg (dolby) - Saturday, 17 November 2012, 09:40 GMT
Still a problem with 3.6.2?
Comment by LB06 (LB06) - Thursday, 22 November 2012, 01:09 GMT
For me, the problems started with 3.6.2. At boot time, the desktop just 'hangs' there for a minute or so and then goes on to display the UI elements. My logs reported I was still using an 'old' keyring in ~/.gnome2/. Removing the keyring worked, but whenever I create a new keyring, it causes the same problems. It also causes me not be able to log into my SSH accounts using my keypair. The dialogue for entering my passphrase never appears.
Comment by Jan de Groot (JGC) - Monday, 01 July 2013, 08:41 GMT
Is this fixed with gnome 3.8?

Loading...