| Summary: | evolution crashes when trying to access stored passwords | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Helmut Eberharter <Henry78> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | critical | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info | ||
|
Description
Helmut Eberharter
2007-04-18 08:58:01 UTC
forgot to mention, that everything works, if i enter my caldav-passwords maually, and don't let evolution store them. Thanks for reporting. Unfortunately the backtrace doesn't provide much information. Could you reinstall at least evolution, evolution-data-server and gnome-keyring with debug informations. See instructions at http://live.gnome.org/GettingTraces/DistroSpecificInstructions and http://www.gentoo.org/proj/en/qa/backtraces.xml Did that, unfortunately Bug Buddy doesn't spit out a more before (just less 'no debugging symbols found' lines). If I start evolution from gdb i get (username and exchange url masked manually): GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread -1234176320 (LWP 17940)] CalDAV Eplugin starting up ... get OFFICE\user exchange://OFFICE%5cuser;auth=Basic@owa.domain.tld/ Find Items 0 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1234176320 (LWP 17940)] 0xb67e8188 in strcmp () from /lib/libc.so.6 (gdb) q The program is running. Exit anyway? (y or n) y are you by any chance using an exchange server ? Yes, I am. Via the evolution-exchange plugin. But the exchange-plugins are not affected by the error, i've them stored in the keyring, and evo works fine. I think it just shows up in the backtrace, because everythin start up at the smae time... hu, btw, noticed that you directly exited from gdb instead of printing the backtrace. Could you attach it ? (just type bt to get it) If it doesn't get any better, I think you'll need to recompile more of the stack with debugging smybols (following gentoo doc) or wait for somebody smarter to comment :). If you do compile with debugging symbols, I suggest you enable split-debug FEATURE in make.conf so that you can clean up your system more easily later on when this issue is solved. (In reply to comment #6) Ups. It's my first time with gdm, sorry for not reading the docs properly, here's the bactrace (account et al masked again): #0 0xb683e188 in strcmp () from /lib/libc.so.6 #1 0xb7d5feed in ep_get_password_keyring (msg=0x80b93c0) at e-passwords.c:671 #2 0xb7d5fab2 in ep_idle_dispatch (data=0x0) at e-passwords.c:128 #3 0xb7d5fb85 in ep_msg_send (msg=0x80b93c0) at e-passwords.c:184 #4 0xb7d61c52 in e_passwords_get_password (component_name=0xb6624f7e "Exchange", key=0x80bd9e8 "exchange://OFFICE%5cusername;auth=Basic@owa.domain.tld/") at e-passwords.c:1095 #5 0xb661549f in exchange_config_listener_authenticate (ex_conf_listener=0x806b790, account=0x80b6410) at exchange-config-listener.c:708 #6 0xb66164ec in account_added (account_list=0x806b790, account=0x806eab8) at exchange-config-listener.c:890 #7 0xb699c6c4 in g_cclosure_marshal_VOID__OBJECT () from /usr/lib/libgobject-2.0.so.0 #8 0xbfc6b11c in ?? () #9 0x00000550 in ?? () #10 0x0806b790 in ?? () #11 0xb69be668 in ?? () from /usr/lib/libgobject-2.0.so.0 #12 0xbfc6b11c in ?? () #13 0x080e46d0 in ?? () #14 0x080e46d0 in ?? () #15 0xb698f558 in ?? () from /usr/lib/libgobject-2.0.so.0 #16 0x080e46d0 in ?? () #17 0x00000000 in ?? () I already enabled splig-debug, as suggested int the gentoo-backtraces doc. that's better. There it seems that the crash is when evo try to get the password for the exchange account. To debug the issue you need to explore what happens in "ep_get_password_keyring (msg=0x80b93c0)" could you also attach you "emerge --info". If nothing obvious shows up, your probably good to bring this upstream. Created attachment 116708 [details]
emerge --info
(In reply to comment #8) > There it seems that the crash is when evo try to get the password for the > exchange account. But evolution only crashes, if i save my *caldav* passwords. If i don't evo doesn't crash, and exchange works fine... > To debug the issue you need to explore what happens in "ep_get_password_keyring > (msg=0x80b93c0)" > > could you also attach you "emerge --info". If nothing obvious shows up, your > probably good to bring this upstream. Is attached (In reply to comment #10) > (In reply to comment #8) > > There it seems that the crash is when evo try to get the password for the > > exchange account. > But evolution only crashes, if i save my *caldav* passwords. If i don't evo > doesn't crash, and exchange works fine... hum, do you have other passwords for evo stored in the keyring ? I understand that it crashes only when you store your caldav password, but the backtrace shows that it crashes just while/after getting the password from the keyring. > > > To debug the issue you need to explore what happens in "ep_get_password_keyring > > (msg=0x80b93c0)" > > > > could you also attach you "emerge --info". If nothing obvious shows up, your > > probably good to bring this upstream. > Is attached > I see nothing wrong there and since I don't have an exchange server myself, I can't reproduce the issue so you'll have to bring this upstream. Be sure to provide them the backtrace, the link to this bug and post the gnome's bugzilla link here. Again, thanks for your time. (In reply to comment #11) > hum, do you have other passwords for evo stored in the keyring ? > I understand that it crashes only when you store your caldav password, but the > backtrace shows that it crashes just while/after getting the password from the > keyring. I got quite some password stored: 1 POP account, 5 IMAP accounts, 1 exchange account, 1 LDAP adress book, 4 webcal calendars ;-) > I see nothing wrong there and since I don't have an exchange server myself, I > can't reproduce the issue so you'll have to bring this upstream. Be sure to > provide them the backtrace, the link to this bug and post the gnome's bugzilla > link here. > > Again, thanks for your time. I'll bring this upstream. I've to thank for YOUR TIME! Gnome Bugzilla Bug #431281 http://bugzilla.gnome.org/show_bug.cgi?id=431281 |
