Bugzilla – Bug 115098
Evolution strangeness as mail handler for Firefox with development warning enabled
Last modified: 2006-09-28 13:25:25 UTC
When evolution still has the development warning enabled at start, I saw strange behavior when clicking on a <a href="mailto:someemail@somedomain.com">someemail@somedomain.com</a> link if there is already a copy of evolution running. What would happen is that another copy of evolution would be launched, even though evolution was already running, which led to a crash. Once I disabled the start-up warning message, I could not reproduce the behavior. I am assuming that warning will not be present in the final version, so it is probably a non-issue, but thought I should report just in case. Steps to reproduce: Vanilla installation, launch evolution, leaving the warning enabled Launch Firefox Go to a site with a mailto: style email link Select the link, and another instance of evolution will try to launch
Leah: Can you install debuginfo packages and get a stack trace ? Create a new user account in your box and try with the above steps. If you again get the crash, please attach the stack trace to this bug.
I can reproduce the problem with a new user account. I was able to grab some information from the GNOME bug buddy stuff and I will attach the info it got from the application crash, but it is not much. I did not see a debuginfo package for ppc?
Created attachment 48697 [details] bug buddy crash output
Leah: stack trace does not provide much info. So you may need to find debuginfo package for PPC and install it in your box. After that get the stack trace and attach to this bug.
I see. I am having trouble finding that package. Should it be included, or should I look elsewhere?
There are no -debug packages for 10.0. Which makes gdb usage on 10.0-ppc useless.
this seems to work for me. at least when running kde, start evolution, configure it for pop3, send a message, start firefox, go to a website with an email link. after a while, the compose message window appears. what warning message should I expect to see?
appears to work also in a gnomesession.
reopen if 10.1 has the same error