Bug 1141617

Summary: [abrt] mate-notification-daemon: g_thread_new(): mate-notification-daemon killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Brandon Amaro <omega13a>
Component: mate-notification-daemonAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, omega13a, raveit65.sun, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/289d7e8406f983f41202e39326bc83974ff4a020
Whiteboard: abrt_hash:4297c24dbc00014f9af2916971a196f83ce546bb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-12 20:23: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:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brandon Amaro 2014-09-15 03:38:27 UTC 
Version-Release number of selected component:
mate-notification-daemon-1.8.0-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/mate-notification-daemon
crash_function: g_thread_new
executable:     /usr/libexec/mate-notification-daemon
kernel:         3.15.10-201.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:840
 #3 _g_dbus_shared_thread_ref at gdbusprivate.c:306
 #4 _g_dbus_worker_new at gdbusprivate.c:1680
 #5 initable_init at gdbusconnection.c:2652
 #6 g_bus_get_sync at gdbusconnection.c:7033
 #7 dconf_gdbus_get_bus_in_worker at dconf-gdbus-thread.c:184
 #8 dconf_gdbus_method_call at dconf-gdbus-thread.c:242
 #12 g_main_context_iteration at gmain.c:3774
 #13 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81
 #14 g_thread_proxy at gthread.c:798

Potential duplicate: bug 1072609
Comment 1 Brandon Amaro 2014-09-15 03:38:30 UTC 
Created attachment 937417 [details]
File: backtrace
Comment 2 Brandon Amaro 2014-09-15 03:38:31 UTC 
Created attachment 937418 [details]
File: cgroup
Comment 3 Brandon Amaro 2014-09-15 03:38:32 UTC 
Created attachment 937419 [details]
File: core_backtrace
Comment 4 Brandon Amaro 2014-09-15 03:38:33 UTC 
Created attachment 937420 [details]
File: dso_list
Comment 5 Brandon Amaro 2014-09-15 03:38:34 UTC 
Created attachment 937421 [details]
File: environ
Comment 6 Brandon Amaro 2014-09-15 03:38:35 UTC 
Created attachment 937422 [details]
File: limits
Comment 7 Brandon Amaro 2014-09-15 03:38:36 UTC 
Created attachment 937423 [details]
File: maps
Comment 8 Brandon Amaro 2014-09-15 03:38:37 UTC 
Created attachment 937424 [details]
File: open_fds
Comment 9 Brandon Amaro 2014-09-15 03:38:38 UTC 
Created attachment 937425 [details]
File: proc_pid_status
Comment 10 Brandon Amaro 2014-09-15 03:38:38 UTC 
Created attachment 937426 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2014-10-04 15:06:24 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 12 Wolfgang Ulbrich 2014-11-12 20:23:29 UTC 
no answer from reporter