GNOME Bugzilla – Bug 312022
Entering address details in evolution when it locked up
Last modified: 2013-09-10 13:57:07 UTC
Distribution: Fedora Core release 4 (Stentz) Package: Evolution Priority: Normal Version: GNOME2.10.0 2.2.2 Gnome-Distributor: Red Hat, Inc Synopsis: Entering address details in evolution when it locked up Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.2.2 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread -1208371520 (LWP 3952)] [New Thread -1233855568 (LWP 4053)] [New Thread -1211769936 (LWP 4052)] [New Thread -1211503696 (LWP 4051)] [New Thread -1211237456 (LWP 4050)] [New Thread -1223365712 (LWP 4034)] [New Thread -1212871760 (LWP 3990)] (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) (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) 0x00e9a402 in ?? ()
+ Trace 62086
Thread 1 (Thread -1208371520 (LWP 3952))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-30 05:27 UTC ------- Unknown version 2.2.2 in product Evolution. Setting version to "2.2.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was bob@fsleng.com.
bob: Looks like when you are adding new signature evolution crashed ? Can you please provide the steps to reproduce this bug ?
closing this bug as the reporter has not responded. Please reopen the bug if you find this happening in the latest version with the needed information.
Re-opening the bug as its reported again in bug 315482 with the same stack trace.
*** Bug 315482 has been marked as a duplicate of this bug. ***
stacktrace a bit similar to bug 321871/bug 323877
Looks like a crash in account editor.
Am not able to reporduce this at all. Bob do you still face this issue??
*** Bug 324787 has been marked as a duplicate of this bug. ***
*** Bug 325371 has been marked as a duplicate of this bug. ***
*** Bug 325936 has been marked as a duplicate of this bug. ***
*** Bug 325938 has been marked as a duplicate of this bug. ***
*** Bug 316408 has been marked as a duplicate of this bug. ***
i haven't seen a single report dealing with signature editing crashes (see the duplicates) for 2.4, so i really assume that this has been fixed in the meantime.
*** Bug 326968 has been marked as a duplicate of this bug. ***
*** Bug 329122 has been marked as a duplicate of this bug. ***
There you go with the very same issue using Evo 2.4. REOPENing.
*** Bug 329157 has been marked as a duplicate of this bug. ***
Another 2.4 confirmation. Adjusting version, bumping Priority.
And i have absolutely no idea as to how i could reproduce this. I never got a crash.
Anybody able to reproduce this bug consistently, please give me the details. There is no way am able to reproduce this.
*** Bug 330366 has been marked as a duplicate of this bug. ***
Another confirmation from Evo 2.4.x. If anyone can reproduce this, please provide as much details as possible. Thanks.
I've reported 330366. I've never add this problem in 2.2. only in this Ubuntu instalation of 2.4. I'll try to check it in a Debian sid Evo 2.4 instalation latter. which specific details do you need? I can try to provide you with it.
Thanks Diogo. :) If you can reproduce this, please describe the steps taken, including any detail you can provide. Does it happen for particluar data only? Is this a general issue? Reproducible? Since this is a crash, getting a stacktrace with debugging symbols would be a great help. Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Steps to reproduce: 1. open evo e email component; 2. open account editor trough menu edit -> preferences -> email accounts; 3. select add new signature; 4. write a name and text; 5. press save button; 6. crashes; This is odd! This time it didn't crashed. All other times before I manually added a signature throught Composer Preferences, it crashed but I can't remember if it crashed after that). So I can't send the trace at this time. But I'll try to reproduce that in a test machine later. Damned bugs, they only appear when they shouldn't...
setting to NEEDINFO
At least 10 duplicates, and there are a bunch of bugs with *very* similar stacktraces out there... Ignoring by setting the status to NEEDINFO is *not* a solution. At a very minimum, you need to tell the reports what info you need *exactly*, and how to get it. REOPEN.
*** Bug 320021 has been marked as a duplicate of this bug. ***
*** Bug 323877 has been marked as a duplicate of this bug. ***
still happens in 2.5
I went thru all the dulicate busgs and tried all means of reproducing the error on Evolution 2.5 but wasn't able to reproduce it.
*** Bug 332694 has been marked as a duplicate of this bug. ***
*** Bug 333840 has been marked as a duplicate of this bug. ***
there is another howto-example at bug 333840
*** Bug 334649 has been marked as a duplicate of this bug. ***
*** Bug 335287 has been marked as a duplicate of this bug. ***
I have gotten a crash trying to write emails on v2.6 w/FC5 should I try to get the debug version of evolution and do a stacktrace? Should I get the debug versions of any other packages?
this happens way too often (take a look at all those duplicates), therefore retargetting this to 2.6.
*** Bug 336038 has been marked as a duplicate of this bug. ***
(In reply to comment #37) > I have gotten a crash trying to write emails on v2.6 w/FC5 should I try to get > the debug version of evolution and do a stacktrace? Should I get the debug > versions of any other packages? > Actually, once I fixed the evolution-data-server crash, this seems to have gone away.
*** Bug 341293 has been marked as a duplicate of this bug. ***
*** Bug 329427 has been marked as a duplicate of this bug. ***
Set target milestone to 2.8
/me still clueless... Any stack trace. would be of great help. please look at live.gnome.org/GettingTraces to get more info on how to get traces
Folks, It is painfully obvious that you need a mechanism that will accurately tell you what was happening when a crash occurred that does not involve the user doing anything. Although I have the skills to do so, I do not have the time at work to rebuild Evolution with debugging turned on just to obtain a crash dump. At work, I work. At home I use Thunderbird, and I have a million other things to do. Rebuilding Evolution is well below the line. It takes less time for me to curse and then restart than it does to rebuild. But even if I had the time, there are thousands of others who use Evolution and who don't have the skills to rebuild Evolution with debugging turned on. Without some mechanism to capture what was happening when a crash occurred, you cannot get any useful information from them. Ever. And I happen to believe that there are many more people who can't rebuild Evolution than those who can. I strongly suggest that you look at how the CrossOver Office folks have set things up. They use a command line option to choose among several different kinds of logging. For example: ~/cxoffice/bin/wine --debugmsg +relay,+seh --cx-log start.log.gz <EXE> But, this is just a suggestion. Regardless of the mechanism chosen, you will fail to get the information you need to debug and fix Evolution crashes unless you incorporate what you need in standard builds. Please don't whine to me about this being free software, yadda yadda yadda. I know that. You are not getting the information you need. You will have to take action, otherwise the situation will not change.
vladimir: somehow you're right, however that's not an evolution-only issue, but an entire gnome problem. if distros would always install the devel packages by default, this would be a hell easier.
You dont have to build from sources to get the debug-info. You can install debuginfor rpms.
using ubuntu edgy and it still does not crash. I'm sure am missing something in this bug... Looking thru all the duplicates that are there - i found another useful stack trace by poornima (on bug 324787):
+ Trace 82859
Here you can see the line number information also shown. The only possible reason for the crash is a NULL priv in the emae parameter that is passed to emae_signature_added in frame #7 Is there any specific signature for which it crashes.. I have tried all kinds of possiblities, html, non-html. If someone could give me a signature for which evo crashes would be great. Hopefully i can try and reproduce then. This bug is lurking around for way too long.
I could reproduce this bug on actual evolution version only when reverting patch from bug #300881, so I bet the above reports are on old version, before the patch was applied. My steps are: 1) open account editor 2) change account type (it will (without a patch) re-register events on signatures) 3) close this account editor and reopen it again 4) try add signature, see part of crash log below: 0x0000003d3040d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 155633
Bumping version to a stable release.
The issue is no more reproducible on 2.22.3.1. As per comment#49 this is a dup of bug 300881.Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 300881 ***