GNOME Bugzilla – Bug 346740
Crash, Password related
Last modified: 2013-09-14 16:49:26 UTC
Distribution: Ubuntu 6.10 (edgy) Package: Evolution Severity: critical Version: GNOME2.15.2 2.7.x Gnome-Distributor: Ubuntu Description: Steps to reproduce the crash: 1. write an email signed with your gpg key 2. send it 3. evo crash Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231935824 (LWP 9678)] [New Thread -1299764320 (LWP 9693)] [New Thread -1321641056 (LWP 9692)] [New Thread -1291334752 (LWP 9689)] [New Thread -1274549344 (LWP 9687)] [New Thread -1282942048 (LWP 9686)] [New Thread -1266156640 (LWP 9681)] [New Thread -1257763936 (LWP 9680)] [New Thread -1249371232 (LWP 9679)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 69214
Thread 1 (Thread -1231935824 (LWP 9678))
unique stacktrace. is this totally reproducible?
yes, but that's maybe an ubuntu bug, the package just got uploaded...
maybe an ubuntu bug... *shrug* CC'ing sebastien, also with regard to bug 342279.
I doubt the bug is Ubuntu specific, that's rather an upstream bug of the new 2.7.3 version. As pointed that seems to be the same issue than bug #342279 which has been marked as duplicate of bug #315012. Maybe the same should be done with that one?
sebastien: seems to be ubuntu specific, see bug 347226 comment 3 - i would mark this one here as a duplicate if you do not contradict. :-)
*** Bug 347428 has been marked as a duplicate of this bug. ***
sebastien: i really am not able to get this to crash on a suse box. Dont have an ubuntu available to check on that. Could it be ubuntu specific issue??
*** Bug 347690 has been marked as a duplicate of this bug. ***
*** Bug 347781 has been marked as a duplicate of this bug. ***
Note, *all* duplicates (and the probabledup bug 347685) are reported using Ubuntu 6.10 (edgy). I can not find any similar stacktrace on any other distribution or even version. Re comment 3 and comment 4: Looking at the stacktraces I do not see how this could be related to bug 342279.
can anybody get a backtrace with evolution-dbg and evolution-data-server-dbg installed?
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.4 2006-07-11 (Ubuntu) BugBuddy Version: 2.15.0 Memmory status: size: 154820608 vsize: 0 resident: 154820608 share: 0 rss: 31027200 rss_rlim: 0 CPU usage: start_time: 1153148097 rtime: 0 utime: 438 stime: 0 cutime:378 cstime: 0 timeout: 60 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1231788368 (LWP 12114)] [New Thread -1324090464 (LWP 12140)] [New Thread -1321702496 (LWP 12138)] [New Thread -1282810976 (LWP 12136)] [New Thread -1257632864 (LWP 12135)] [New Thread -1291203680 (LWP 12128)] [New Thread -1299678304 (LWP 12127)] [New Thread -1274418272 (LWP 12123)] [New Thread -1266025568 (LWP 12122)] [New Thread -1249240160 (LWP 12120)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 69392
Thread 1 (Thread -1231788368 (LWP 12114))
bug 347885 could be another duplicate, too. leaving this for the ubuntu folks to find out. :-)
*** Bug 348815 has been marked as a duplicate of this bug. ***
*** Bug 348623 has been marked as a duplicate of this bug. ***
Although the stacktraces are slightly different, I believe bug 348815 and bug 348623 actually to be duplicates of this bug. Note that the descriptions are not the same anyway. Doesn't seem to be related to GPG. According to the duplicates (Ubuntu 6.10, Evolution 2.7.x, GNOME 2.15.x) and by a quick look at the code, I seriously suspect the gnome-keyring integration to cause all these crashes. Moving over to e-d-s. Bug 347685 probably is another dupe, though I'm not sure there.
*** Bug 348889 has been marked as a duplicate of this bug. ***
bug 349048 on evo 2.6 also looks very similar and includes line numbers:
+ Trace 69742
*** Bug 349028 has been marked as a duplicate of this bug. ***
*** Bug 349096 has been marked as a duplicate of this bug. ***
*** Bug 349084 has been marked as a duplicate of this bug. ***
This just seems to be calling strcmp() on a NULL pointer.
the offending line was added when gnome-keyring-manager integration was added by srini, see http://cvs.gnome.org/viewcvs/evolution-data-server/libedataserverui/e-passwords.c?annotate=1.33 as ubuntu uses keyring-manager integration, this explains the number of ubuntu folks running into this. raising priority as this bites many people. copying sven's last comment at bug 349084: "This looks like you're calling strcmp() without checking its arguments for NULL."
*** Bug 349048 has been marked as a duplicate of this bug. ***
*** Bug 349319 has been marked as a duplicate of this bug. ***
*** Bug 349460 has been marked as a duplicate of this bug. ***
*** Bug 349464 has been marked as a duplicate of this bug. ***
Thought the top traces are same. There are two core issues. - One during signing a message (Passphrases are not remembered across sessions) So they dont have a service url. - LDAP addressbook loading. the url is little different since the user name is part of ou=user and not proto://user@host:/path Ill fix them right away. Thanks for the traces.
> Ill fix them right away. Thanks for the traces. You're welcome, Thanks for your work !!
Created attachment 70017 [details] [review] Proposed patch
This should behave in the following approach. - LDAP key is used as the user name (Even the .gnome_private behaves the same way) - Passphrases are stored for the session ( -same-as-above ) It shouldnt crash now on.
*** Bug 346526 has been marked as a duplicate of this bug. ***
*** Bug 347685 has been marked as a duplicate of this bug. ***
*** Bug 349574 has been marked as a duplicate of this bug. ***
varadhan, sushma: review ?
the patch works fine and fix the crasher on my edgy desktop (GNOME 2.15.90)
(In reply to comment #35) > varadhan, sushma: review ? > Srini: Keyring part looks fine to me.
*** Bug 349704 has been marked as a duplicate of this bug. ***
Fixed to head. Should be there for the next dot release.
*** Bug 351184 has been marked as a duplicate of this bug. ***
*** Bug 347885 has been marked as a duplicate of this bug. ***
*** Bug 352730 has been marked as a duplicate of this bug. ***
*** Bug 353408 has been marked as a duplicate of this bug. ***