| Summary: | [abrt] evolution-3.3.91-1.fc17: check_invalidate_pixbuf: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 17 | CC: | bugzilla_rhn, guillaumepoiriermorency, lucilanga, mbarnes, mcrha, pbrobinson, psimerda | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i686 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:c962e8e4b1dc3306f6f5346853914b5c6a7867ba | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2013-08-01 03:40:29 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Mikhail
2012-03-12 09:46:15 UTC
Created attachment 569324 [details]
File: gconf_subtree
Created attachment 569325 [details]
File: build_ids
Created attachment 569326 [details]
File: dso_list
Created attachment 569327 [details]
File: xsession_errors
Created attachment 569328 [details]
File: maps
Created attachment 569329 [details]
File: backtrace
Thanks for a bug report. Are there any steps to reproduce the issue, please? What I see from the backtrace is that the Thread 4 is under an RPC call, probably invoked by evolution-mapi, though the root frame, the #8, shows only ??. The Thread 5 is trying to read folder structure from your MAPI account, waiting for finish of the Thread 4. The thing is that the crash itself happened deep in gtk+ code, while redrawing the window and I do not see from the backtrace what could cause the crash. *** Bug 802310 has been marked as a duplicate of this bug. *** Attempting to send a mail via exchange. backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) Running evolution to send mail. Password had recently been changed but updated in evolution· backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I have changed the authentification from CRAM-MD5 to connexion in sending settings. Evolution was telling me that CRAM-MD5 wasen't working... backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) just pressed send/receive button there are two account in my evolution, one is @qq.com via imap+ another is an @gmail.com added automaticly by set the ferora online account with google account backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I had mistaken the password for one imap+ (google) account and was retrying to see if I got the password dialog again when it crashed backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) 1. I opened evolution 2. I clicked on Send/Receive button 3. Evolution crashed backtrace_rating: 4 Package: evolution-3.4.2-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) Sending e-mail backtrace_rating: 4 Package: evolution-3.4.2-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I typed my password to authenticate with my local SMTP server, and it quickly popped up a message at the top of the screen and I think it said something about a bad response from server, then crashed the evolution client. backtrace_rating: 4 Package: evolution-3.4.2-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I was getting access denied when I tried to send an email. In Account Editor / Sending Email / Server Configuration, I checked Server requires authentication. I tried Send / Receive. Evolution crashed. When I restarted Evolution, I was prompted for the password for the SMTP server as expected. backtrace_rating: 4 Package: evolution-3.4.3-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) Trying to send using inaccesible SMTP connection. I'm happy that evolution does not send it, but it should not crash on it. backtrace_rating: 4 Package: evolution-3.4.3-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I have downloaded my emails and one has a forward to another account, i did a clic on Send/Receive on the toolbar, the email was sent and evolution closed immediatly. backtrace_rating: 4 Package: evolution-3.4.3-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) Sending mail through authenticated SMTP backtrace_rating: 4 Package: evolution-3.4.3-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) new imap password and send a new mail backtrace_rating: 4 Package: evolution-3.4.3-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I was applying a filter. backtrace_rating: 4 Package: evolution-3.4.4-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) https://bugzilla.redhat.com/show_bug.cgi?id=854545 backtrace_rating: 4 Package: evolution-3.4.4-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |