Bug 1000807

Summary: [abrt] mate-system-log-1.6.0-7.fc19: g_settings_set_property: Process /usr/sbin/mate-system-log was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Moez Roy <moez.roy>
Component: mate-utilsAssignee: Dan Mashal <dan.mashal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a9d9f33b1443a108b98e553b832814fae15cc6ec
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-09 01:22:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 Moez Roy 2013-08-25 14:11:29 UTC 
Version-Release number of selected component:
mate-system-log-1.6.0-7.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        mate-system-log
crash_function: g_settings_set_property
executable:     /usr/sbin/mate-system-log
kernel:         3.10.9-200.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_set_property at gsettings.c:492
 #3 object_set_property at gobject.c:1358
 #4 g_object_constructor at gobject.c:1869
 #6 g_object_new_valist at gobject.c:1836
 #8 g_settings_new at gsettings.c:869
 #9 logview_prefs_init at logview-prefs.c:308
 #10 g_type_create_instance at gtype.c:1917
 #11 g_object_constructor at gobject.c:1855
 #14 logview_prefs_get at logview-prefs.c:324
 #15 logview_app_init at logview-app.c:309

Potential duplicate: bug 988278
Comment 1 Moez Roy 2013-08-25 14:11:33 UTC 
Created attachment 790083 [details]
File: backtrace
Comment 2 Moez Roy 2013-08-25 14:11:36 UTC 
Created attachment 790084 [details]
File: cgroup
Comment 3 Moez Roy 2013-08-25 14:11:39 UTC 
Created attachment 790085 [details]
File: core_backtrace
Comment 4 Moez Roy 2013-08-25 14:11:42 UTC 
Created attachment 790086 [details]
File: dso_list
Comment 5 Moez Roy 2013-08-25 14:11:44 UTC 
Created attachment 790087 [details]
File: environ
Comment 6 Moez Roy 2013-08-25 14:11:47 UTC 
Created attachment 790088 [details]
File: limits
Comment 7 Moez Roy 2013-08-25 14:11:50 UTC 
Created attachment 790089 [details]
File: maps
Comment 8 Moez Roy 2013-08-25 14:11:55 UTC 
Created attachment 790090 [details]
File: open_fds
Comment 9 Moez Roy 2013-08-25 14:11:58 UTC 
Created attachment 790091 [details]
File: proc_pid_status
Comment 10 Moez Roy 2013-08-25 14:12:01 UTC 
Created attachment 790092 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2013-08-25 14:21:13 UTC 
LOGNAME=root
USER=root
HOME=/root
SUDO_COMMAND=/sbin/mate-system-log
SUDO_USER=user
SUDO_UID=1000
SUDO_GID=1000

You are working as root, no support!
Comment 12 Moez Roy 2013-10-08 23:13:37 UTC 
ABRT is directing me to this bug even though I clicked run unprivileged (not root)
Comment 13 Moez Roy 2013-10-08 23:14:38 UTC 
also don't you need root privileges to actually read the messages (dmesg) logs?
Comment 14 Wolfgang Ulbrich 2013-10-09 01:22:45 UTC 
login as a normal user!