Bug 1105255

Summary: [abrt] mate-screensaver: g_thread_new(): mate-screensaver-dialog killed by SIGTRAP
Product: [Fedora] Fedora Reporter: thraex
Component: mate-screensaverAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/602228a90eed0b71873e35892696f322b578d499
Whiteboard: abrt_hash:bb524b1c604d4fa6a2b077872810b33c3e0b557e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-04 15:23:54 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

Description thraex 2014-06-05 17:03:04 UTC 
Version-Release number of selected component:
mate-screensaver-1.6.2-1.fc19

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/libexec/mate-screensaver-dialog --status-message= --enable-switch
crash_function: g_thread_new
executable:     /usr/libexec/mate-screensaver-dialog
kernel:         3.14.4-100.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: Jun  5 18:57:17 localhost abrt-hook-ccpp[23440]: Saved core dump of pid 23428 (/usr/libexec/mate-screensaver-dialog) to /var/tmp/abrt/ccpp-2014-06-05-18:57:16-23428 (19243008 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:839
 #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:2640
 #6 g_bus_get_sync at gdbusconnection.c:6882
 #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:3762
 #13 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81
 #14 g_thread_proxy at gthread.c:798
Comment 1 thraex 2014-06-05 17:03:07 UTC 
Created attachment 902603 [details]
File: backtrace
Comment 2 thraex 2014-06-05 17:03:08 UTC 
Created attachment 902604 [details]
File: cgroup
Comment 3 thraex 2014-06-05 17:03:09 UTC 
Created attachment 902605 [details]
File: core_backtrace
Comment 4 thraex 2014-06-05 17:03:11 UTC 
Created attachment 902606 [details]
File: dso_list
Comment 5 thraex 2014-06-05 17:03:12 UTC 
Created attachment 902607 [details]
File: environ
Comment 6 thraex 2014-06-05 17:03:13 UTC 
Created attachment 902608 [details]
File: limits
Comment 7 thraex 2014-06-05 17:03:14 UTC 
Created attachment 902609 [details]
File: maps
Comment 8 thraex 2014-06-05 17:03:15 UTC 
Created attachment 902610 [details]
File: open_fds
Comment 9 thraex 2014-06-05 17:03:16 UTC 
Created attachment 902611 [details]
File: proc_pid_status
Comment 10 Wolfgang Ulbrich 2014-06-21 16:08:10 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 11 thraex 2014-06-26 11:58:45 UTC 
Hi Wolfgang,

I don't remember what caused this, sorry about that. All I can tell is that it didn't happen again after the report (nor before it otherwise I would have reported it earlier) so it occurs extremely rarely.
Comment 12 Wolfgang Ulbrich 2014-06-26 14:39:10 UTC 
Hi thraex,
ok, np, i will leave the report a while open to see if it happens again.
Comment 13 Wolfgang Ulbrich 2014-10-04 15:23:54 UTC 
feel free to report again here, if it happens again. I will re-open it than.