Bug 1068768 - [abrt] evolution-data-server: g_thread_new(): evolution-source-registry killed by SIGTRAP
Summary: [abrt] evolution-data-server: g_thread_new(): evolution-source-registry kille...
Keywords:
Status: CLOSED DUPLICATE of bug 1068741
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:9bad1662a52c3125b88d7fdea47...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-21 20:31 UTC by Brian J. Murrell
Modified: 2015-07-15 13:42 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-24 08:46:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (81.12 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: cgroup (172 bytes, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: core_backtrace (38.15 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: dso_list (17.08 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: environ (1.20 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: limits (1.29 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: maps (81.45 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: open_fds (1.43 KB, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: proc_pid_status (938 bytes, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
File: var_log_messages (390 bytes, text/plain)
2014-02-21 20:31 UTC, Brian J. Murrell 		no flags Details
View All

Description Brian J. Murrell 2014-02-21 20:31:10 UTC 
Version-Release number of selected component:
evolution-data-server-3.10.4-1.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-source-registry
crash_function: g_thread_new
executable:     /usr/libexec/evolution-source-registry
kernel:         3.12.6-300.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:840
 #3 authentication_mediator_initable_init at /lib64/libebackend-1.2.so.7
 #4 g_initable_new_valist at ginitable.c:231
 #5 g_initable_new at ginitable.c:149
 #6 e_authentication_mediator_new at /lib64/libebackend-1.2.so.7
 #7 source_registry_server_authenticate_cb at /lib64/libebackend-1.2.so.7
 #8 ffi_call_unix64 at ../src/x86/unix64.S:76
 #9 ffi_call at ../src/x86/ffi64.c:522
 #10 g_cclosure_marshal_generic at gclosure.c:1454
 #13 g_signal_emitv at gsignal.c:3063
Comment 1 Brian J. Murrell 2014-02-21 20:31:13 UTC 
Created attachment 866259 [details]
File: backtrace
Comment 2 Brian J. Murrell 2014-02-21 20:31:16 UTC 
Created attachment 866260 [details]
File: cgroup
Comment 3 Brian J. Murrell 2014-02-21 20:31:18 UTC 
Created attachment 866261 [details]
File: core_backtrace
Comment 4 Brian J. Murrell 2014-02-21 20:31:22 UTC 
Created attachment 866262 [details]
File: dso_list
Comment 5 Brian J. Murrell 2014-02-21 20:31:24 UTC 
Created attachment 866263 [details]
File: environ
Comment 6 Brian J. Murrell 2014-02-21 20:31:25 UTC 
Created attachment 866264 [details]
File: limits
Comment 7 Brian J. Murrell 2014-02-21 20:31:27 UTC 
Created attachment 866265 [details]
File: maps
Comment 8 Brian J. Murrell 2014-02-21 20:31:29 UTC 
Created attachment 866266 [details]
File: open_fds
Comment 9 Brian J. Murrell 2014-02-21 20:31:30 UTC 
Created attachment 866267 [details]
File: proc_pid_status
Comment 10 Brian J. Murrell 2014-02-21 20:31:36 UTC 
Created attachment 866268 [details]
File: var_log_messages
Comment 11 Milan Crha 2014-02-24 08:46:29 UTC 
Thanks for a bug report. I'm afraid this is related to your recent crash reports, like bug #1068741, thus I mark this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 1068741 ***
Comment 12 Brian J. Murrell 2014-02-24 13:46:48 UTC 
I'm getting more of these this morning.  3 and counting so far, according to abrt and I can assure you, looking at the little performance meters on the taskbar of this machine that memory is _nowhere_ near exhausted.  It's been pretty steady all morning and currently at:

MemTotal:       14300624 kB
MemFree:         3564840 kB
Buffers:          570628 kB
Cached:          3979528 kB
SwapCached:            0 kB
Active:          7951204 kB
Inactive:        1640316 kB
Active(anon):    5051048 kB
Inactive(anon):    43252 kB
Active(file):    2900156 kB
Inactive(file):  1597064 kB
Unevictable:       21996 kB
Mlocked:           21996 kB
SwapTotal:      16777212 kB
SwapFree:       16777212 kB
Dirty:               420 kB
Writeback:             0 kB
AnonPages:       5063352 kB
Mapped:           337176 kB
Shmem:             47148 kB
Slab:             767640 kB
SReclaimable:     661064 kB
SUnreclaim:       106576 kB
KernelStack:       10704 kB
PageTables:       123820 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    23927524 kB
Committed_AS:   13097424 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      366744 kB
VmallocChunk:   34359363376 kB
HardwareCorrupted:     0 kB
AnonHugePages:   2510848 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      479132 kB
DirectMap2M:    14131200 kB
Comment 13 Brian J. Murrell 2014-02-24 22:33:07 UTC 
I just had this happen again.  This time it happened immediately after an occurrence of bug 1031662 -- that is Gnome-Online-Accounts dying.

Maybe that helps.
Comment 14 Brian J. Murrell 2014-02-25 12:34:48 UTC 
This is happening with pretty decent regularity.  Or at least abrt thinks so.  Unfortunately once a abrt thinks a particular crash is a duplicate of something filed there's not much more looking into it you can do with abrt.
Note You need to log in before you can comment on or make changes to this bug.