Bug 892622 - [abrt] evolution-3.6.2-3.fc18: g_wakeup_new: Process /usr/bin/evolution was killed by signal 5 (SIGTRAP)
Summary: [abrt] evolution-3.6.2-3.fc18: g_wakeup_new: Process /usr/bin/evolution was k...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:00563713cb8f7c7c75415aefd65...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 12:30 UTC by Petr Muller
Modified: 2016-09-20 02:09 UTC (History)
4 users (show)

Fixed In Version: evolution-3.6.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 13:26:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (136.90 KB, text/plain)
2013-01-07 12:30 UTC, Petr Muller 		no flags Details
File: build_ids (10.25 KB, text/plain)
2013-01-07 12:30 UTC, Petr Muller 		no flags Details
File: cgroup (127 bytes, text/plain)
2013-01-07 12:30 UTC, Petr Muller 		no flags Details
File: core_backtrace (1.39 KB, text/plain)
2013-01-07 12:30 UTC, Petr Muller 		no flags Details
File: dso_list (26.11 KB, text/plain)
2013-01-07 12:30 UTC, Petr Muller 		no flags Details
File: environ (1.57 KB, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
File: limits (1.29 KB, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
File: maps (126.53 KB, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
File: open_fds (92.46 KB, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
File: proc_pid_status (936 bytes, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
File: var_log_messages (2.65 KB, text/plain)
2013-01-07 12:31 UTC, Petr Muller 		no flags Details
View All

Description Petr Muller 2013-01-07 12:30:34 UTC 
Description of problem:
Attempting to load images to the message via Ctrl-I. Very reproducible (happens every time I try that on that message)

Version-Release number of selected component:
evolution-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        evolution
crash_function: g_wakeup_new
executable:     /usr/bin/evolution
kernel:         3.6.11-3.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_wakeup_new at gwakeup.c:163
 #3 g_main_context_new at gmain.c:590
 #4 handle_http_request at e-http-request.c:316
 #5 run_in_thread at gsimpleasyncresult.c:869
 #6 io_job_thread at gioscheduler.c:162
 #8 g_thread_proxy at gthread.c:797
Comment 1 Petr Muller 2013-01-07 12:30:37 UTC 
Created attachment 673977 [details]
File: backtrace
Comment 2 Petr Muller 2013-01-07 12:30:39 UTC 
Created attachment 673978 [details]
File: build_ids
Comment 3 Petr Muller 2013-01-07 12:30:52 UTC 
Created attachment 673979 [details]
File: cgroup
Comment 4 Petr Muller 2013-01-07 12:30:55 UTC 
Created attachment 673980 [details]
File: core_backtrace
Comment 5 Petr Muller 2013-01-07 12:30:59 UTC 
Created attachment 673981 [details]
File: dso_list
Comment 6 Petr Muller 2013-01-07 12:31:01 UTC 
Created attachment 673982 [details]
File: environ
Comment 7 Petr Muller 2013-01-07 12:31:04 UTC 
Created attachment 673984 [details]
File: limits
Comment 8 Petr Muller 2013-01-07 12:31:07 UTC 
Created attachment 673985 [details]
File: maps
Comment 9 Petr Muller 2013-01-07 12:31:13 UTC 
Created attachment 673986 [details]
File: open_fds
Comment 10 Petr Muller 2013-01-07 12:31:19 UTC 
Created attachment 673987 [details]
File: proc_pid_status
Comment 11 Petr Muller 2013-01-07 12:31:21 UTC 
Created attachment 673988 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-01-08 13:26:38 UTC 
Thanks for a bug report. Crashes in g_wakeup_new() usually mean that you got out of file descriptors. This was caused by evolution itself, and should be fixed by this commit [1], which will be part of evolution-3.6.3.

[1] http://git.gnome.org/browse/evolution/commit/?h=gnome-3-6&id=c7f5afb6d9179
Note You need to log in before you can comment on or make changes to this bug.