Bug 979186 - [abrt] evolution-3.8.3-2.fc19: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-3.8.3-2.fc19: magazine_chain_pop_head: Process /usr/bin/evol...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7adfd265ae56226ddbca7f785fa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-27 21:01 UTC by Boricua
Modified: 2013-07-01 18:02 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-01 08:51:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (101.58 KB, text/plain)
2013-06-27 21:01 UTC, Boricua 		no flags Details
File: cgroup (140 bytes, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: core_backtrace (4.16 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: dso_list (25.41 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: environ (1.34 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: limits (1.29 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: maps (123.63 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: open_fds (2.39 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: proc_pid_status (935 bytes, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
File: var_log_messages (15.31 KB, text/plain)
2013-06-27 21:02 UTC, Boricua 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 703373 0 None None None Never

Description Boricua 2013-06-27 21:01:52 UTC 
Description of problem:
I just launched Evo to check my IMAP acounts.

Version-Release number of selected component:
evolution-3.8.3-2.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        evolution
crash_function: magazine_chain_pop_head
executable:     /usr/bin/evolution
kernel:         3.9.6-301.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 g_slice_alloc0 at gslice.c:1029
 #4 g_object_notify_queue_freeze at gobject.c:237
 #5 g_object_init at gobject.c:958
 #6 g_type_create_instance at gtype.c:1909
 #7 g_object_constructor at gobject.c:1855
 #10 g_dbus_message_new at gdbusmessage.c:627
 #11 g_dbus_message_new_method_call at gdbusmessage.c:656

Potential duplicate: bug 701604
Comment 1 Boricua 2013-06-27 21:01:58 UTC 
Created attachment 766338 [details]
File: backtrace
Comment 2 Boricua 2013-06-27 21:02:01 UTC 
Created attachment 766339 [details]
File: cgroup
Comment 3 Boricua 2013-06-27 21:02:05 UTC 
Created attachment 766340 [details]
File: core_backtrace
Comment 4 Boricua 2013-06-27 21:02:09 UTC 
Created attachment 766341 [details]
File: dso_list
Comment 5 Boricua 2013-06-27 21:02:12 UTC 
Created attachment 766342 [details]
File: environ
Comment 6 Boricua 2013-06-27 21:02:16 UTC 
Created attachment 766343 [details]
File: limits
Comment 7 Boricua 2013-06-27 21:02:21 UTC 
Created attachment 766344 [details]
File: maps
Comment 8 Boricua 2013-06-27 21:02:24 UTC 
Created attachment 766345 [details]
File: open_fds
Comment 9 Boricua 2013-06-27 21:02:27 UTC 
Created attachment 766346 [details]
File: proc_pid_status
Comment 10 Boricua 2013-06-27 21:02:30 UTC 
Created attachment 766347 [details]
File: var_log_messages
Comment 11 Milan Crha 2013-07-01 08:51:17 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=703373
Comment 12 Boricua 2013-07-01 18:02:04 UTC 
OK, thanks for the info.
Note You need to log in before you can comment on or make changes to this bug.