Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 175046 - evolution crashes when trying to access stored passwords
Summary: evolution crashes when trying to access stored passwords
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-18 08:58 UTC by Helmut Eberharter
Modified: 2007-04-19 09:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge--info,3.70 KB, text/plain)
2007-04-19 07:05 UTC, Helmut Eberharter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Eberharter 2007-04-18 08:58:01 UTC
evolution crashes at start, if i let evolution save my caldav-calendar-passwords in the gnome-keyring. If i delete the passwords from the keyring, evoltuion starts fine.

Reproducible: Always

Steps to Reproduce:
1. start evolution, add a cladav-calendar and let evolution save password
2. close evolution
3. start evolution

Actual Results:  
evolution crashes, bug buddy jumps in

Expected Results:  
evolution starts up

Bug Buddy crash details:

Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.1 2007-04-16 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-gentoo-r4 #1 SMP Fri Feb 2 13:07:02 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gartoon

Memory status: size: 33128448 vsize: 33128448 resident: 11493376 share: 9347072 rss: 11493376 rss_rlim: 4294967295
CPU usage: start_time: 1176886129 rtime: 40 utime: 36 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.10'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
...reapted ~70 times...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1234463040 (LWP 8602)]
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6997bb3 in __waitpid_nocancel () from /lib/libpthread.so.0
#2  0xb76019d1 in ?? () from /usr/lib/libgnomeui-2.so.0
#3  0x0000219b in ?? ()
#4  0xbfeb3cf8 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread -1234463040 (LWP 8602)):
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb6997bb3 in __waitpid_nocancel () from /lib/libpthread.so.0
No symbol table info available.
#2  0xb76019d1 in ?? () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3  0x0000219b in ?? ()
No symbol table info available.
#4  0xbfeb3cf8 in ?? ()
No symbol table info available.
#5  0x00000000 in ?? ()
No symbol table info available.
#0  0xffffe410 in __kernel_vsyscall ()
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (21522 sec old) ---------------------
HEADER.FIELDS (DATE FROM TO CC SUBJECT REFERENCES IN-REPLY-TO MESSAGE-ID MIME-VERSION CONTENT-TYPE X-MAILING-LIST X-LOOP LIST-ID LIST-POST MAILING-LIST ORIGINATOR X-LIST SENDER RETURN-PATH X-BEENTHERE
 Header string finally is ********** 
HEADER.FIELDS (DATE FROM TO CC SUBJECT REFERENCES IN-REPLY-TO MESSAGE-ID MIME-VERSION CONTENT-TYPE X-MAILING-LIST X-LOOP LIST-ID LIST-POST MAILING-LIST ORIGINATOR X-LIST SENDER RETURN-PATH X-BEENTHERE
 Header string finally is ********** 
HEADER.FIELDS (DATE FROM TO CC SUBJECT REFERENCES IN-REPLY-TO MESSAGE-ID MIME-VERSION CONTENT-TYPE X-MAILING-LIST X-LOOP LIST-ID LIST-POST MAILING-LIST ORIGINATOR X-LIST SENDER RETURN-PATH X-BEENTHERE
 Header string finally is ********** 
HEADER.FIELDS (DATE FROM TO CC SUBJECT REFERENCES IN-REPLY-TO MESSAGE-ID MIME-VERSION CONTENT-TYPE X-MAILING-LIST X-LOOP LIST-ID LIST-POST MAILING-LIST ORIGINATOR X-LIST SENDER RETURN-PATH X-BEENTHERE
 Header string finally is ********** 
HEADER.FIELDS (DATE FROM TO CC SUBJECT REFERENCES IN-REPLY-TO MESSAGE-ID MIME-VERSION CONTENT-TYPE X-MAILING-LIST X-LOOP LIST-ID LIST-POST MAILING-LIST ORIGINATOR X-LIST SENDER RETURN-PATH X-BEENTHERE
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Helmut Eberharter 2007-04-18 08:59:36 UTC
forgot to mention, that everything works, if i enter my caldav-passwords maually, and don't let evolution store them.
Comment 2 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-04-18 09:09:32 UTC
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
Comment 3 Helmut Eberharter 2007-04-18 12:23:54 UTC
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
Comment 4 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-04-18 12:39:37 UTC
are you by any chance using an exchange server ?
Comment 5 Helmut Eberharter 2007-04-18 12:54:17 UTC
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...
Comment 6 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-04-18 13:42:54 UTC
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.
Comment 7 Helmut Eberharter 2007-04-18 15:02:52 UTC
(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.
Comment 8 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-04-18 15:28:25 UTC
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.
Comment 9 Helmut Eberharter 2007-04-19 07:05:11 UTC
Created attachment 116708 [details]
emerge --info
Comment 10 Helmut Eberharter 2007-04-19 07:10:57 UTC
(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

Comment 11 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-04-19 08:40:25 UTC
(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.
Comment 12 Helmut Eberharter 2007-04-19 08:56:57 UTC
(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! 

Comment 13 Helmut Eberharter 2007-04-19 09:04:35 UTC
Gnome Bugzilla Bug #431281 http://bugzilla.gnome.org/show_bug.cgi?id=431281