GNOME Bugzilla – Bug 324259
Old deleted Signatures may crash evolution
Last modified: 2013-09-10 14:04:09 UTC
Distribution: Suse 10.0 Package: Evolution Priority: Normal Version: GNOME2.12.0 unspecified Gnome-Distributor: SUSE Synopsis: Old deleted Signatures may crash evolution Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: After I've removed my $HOME/.evolution directory the old Signature was still present in the account preferences. I've tried to delete it and Evolution is crashed. Steps to reproduce the crash: 1. Create a signature 2. Close Evolution. 3. Remove $HOME/.evolution 4. Start Evolution 5. Delete the old signature in the account preferences. Expected Results: Evolution crash. How often does this happen? Every time you perform upper steps. Debugging Information: See attacched backtrace. ------- Bug moved to this database by unknown@gnome.bugs 2005-12-16 11:43 UTC ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. 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 antenore@gmail.com.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Uhm... Why do we need a stacktrace here anyway? Detailed steps to reproduce are given in the original report. Get your own stacktrace. :) REOPENing. Adjusting Severity, setting Target Milestone. Basically this bug is caused due to manually removing the signature file inside ~/.evolution pointed at by the settings saved in GConf. While the user sure is not expected to manually mess with these files, Evo should not crash either.
Doh, reopening this time.
Evolution doesnt crash for the steps given above on my setup on evolution 2.5.x Please provide stack trace to fix the crash issue. Regarding displaying signature even after .evolution is deleted, that entry is displayed from gconf, gconf cleanup has not happened, this is different issue. As a priority we should fix this crash issue.
Hi, At the moment I've the problem, instead of (or before) reproducing it again, with a stack trace, is there anything you would like to check on this, not working, installation? I'm not enough experienced in bugs submission so please, point me out in the right direction to give you all the needed information; steps, stack trace, and so on. Thanks in advance Regards Antenore.
Hmm, strange. I just tried to reproduce this, but Evo does not crash for me. Neither after manually removing the signature files, nor after removing the entire ~/.evolution/signatures/ directory. Antenore, please just try to reproduce this crash and provide a stacktrace. The given link should assist you in getting the stacktrace we need. Thanks. The output of the following command (run in a terminal) may be interesting as well: $ ls -la ~/.evolution Partha: Dude, there is absolutely no reason in throwing the very same stock response at the reporter *again*. Antenore is willing to provide all details you may need -- please help him in doing so.
Created attachment 59251 [details] Evolution stack trace
Hi Karsten and thanks for the support, here the directory list ls -la .evolution/ totale 105 drwxr-xr-x 8 antenore users 320 2006-02-13 12:10 . drwxr-xr-x 69 antenore users 4592 2006-02-13 12:14 .. drwxr-xr-x 3 antenore users 72 2006-02-13 12:05 addressbook drwx------ 3 antenore users 80 2006-02-13 12:05 cache drwxr-xr-x 4 antenore users 96 2006-02-13 12:05 calendar -rw------- 1 antenore users 3 2006-02-13 12:10 camel-cert.db -rw------- 1 antenore users 65536 2006-02-13 12:05 cert8.db -rw------- 1 antenore users 16384 2006-02-13 12:05 key3.db drwxr-xr-x 6 antenore users 144 2006-02-13 12:06 mail -rw------- 1 antenore users 16384 2006-02-13 12:05 secmod.db drwx------ 2 antenore users 48 2006-02-13 12:12 signatures drwxr-xr-x 4 antenore users 96 2006-02-13 12:05 tasks I've also attached the stack trace. Hope it can help. Thanks in advance Regards Antenore.
The stack trace attached in Comment #8 is not useful, since it does not provide any information. Changing to NEEDINFO. please reopen with a good stack trace. We need a stack trace since we are unable to reproduce the problem, and only a good stack might give us some clues regarding the problem
Please don't misunderstand me, but I'm a bit bothered about this issue. And it's a lot of hard to help you to investigate on the problem without your support. Remember that most of us (users) are not developers/hacker or similar stuff. I've just followed all the steps from http://live.gnome.org/GettingTraces . Please don't take offence... I can workaround the problem and work with Evolution, but, only with your support, I also can make a better debug. Because I'm be able to reproduce the error all the time you want. Are you interested? If not I can use better email clients or just ignore this problem. Make your choice. Sorry for the rage... Antenore.
Hi, antenore, For comment 8, I think you should use the binary program in gdb. the evolution file under /opt/gnome/bin is just probably a script file. You should start your binary file but i dont' know where it is because your machine environment is different with mine. You can know it by looking in file /opt/gnome/bin/evolution. Start that file in gdb then use "thread apply all bt" to get stack trace. Please don't be boring. Without your help, evolution can't become better. Thanks.
Thanks a lot... It's my fault, I should read the documetation :( This time the stack trace should be right. I'm going to attach it. BR Antenore.
Created attachment 60550 [details] Evolution Stack trace Evolution Stack trace
gail bug? *shrug*
stacktrace in comment #14 is the same stacktrace as in bug 327159, therefore marking as duplicate. *** This bug has been marked as a duplicate of 327159 ***