Bug 889680 - evolution stuck on sending mail
Summary: evolution stuck on sending mail
Keywords:
Status: CLOSED DUPLICATE of bug 888172
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-22 14:42 UTC by Mikhail
Modified: 2013-01-07 10:41 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-07 10:41:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
evolution backtrace (18.10 KB, text/plain)
2012-12-22 14:42 UTC, Mikhail 		no flags Details
evolution-addressbook-factory backtrace (4.11 KB, text/plain)
2012-12-22 14:50 UTC, Mikhail 		no flags Details
evolution-calendar-factory backtrace (4.59 KB, text/plain)
2012-12-22 14:53 UTC, Mikhail 		no flags Details
evolution-source-registry backtrace (2.93 KB, text/plain)
2012-12-22 14:57 UTC, Mikhail 		no flags Details
evolution-alarm-notify backtrace (2.36 KB, text/plain)
2012-12-22 14:58 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2012-12-22 14:42:17 UTC 
Created attachment 667689 [details]
evolution backtrace

Description of problem:
evolution stuck on sending mail
Comment 1 Mikhail 2012-12-22 14:50:04 UTC 
Created attachment 667690 [details]
evolution-addressbook-factory backtrace
Comment 2 Mikhail 2012-12-22 14:53:04 UTC 
Created attachment 667691 [details]
evolution-calendar-factory backtrace
Comment 3 Mikhail 2012-12-22 14:57:05 UTC 
Created attachment 667697 [details]
evolution-source-registry backtrace
Comment 4 Mikhail 2012-12-22 14:58:53 UTC 
Created attachment 667698 [details]
evolution-alarm-notify backtrace
Comment 5 Milan Crha 2013-01-07 10:41:54 UTC 
Thanks for a bug report. This is exactly the same as yours bug #888172, thus I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 888172 ***
Note You need to log in before you can comment on or make changes to this bug.