Bug 886974

Summary: [abrt] mate-window-manager-1.5.2-7.fc17: g_logv: Process /usr/bin/marco was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Dirk Hoffmann <hoffmann>
Component: mate-window-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dan.mashal, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fd116ba4cb7e694f40f032db5f20a24c227af333
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-14 08:02:37 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Dirk Hoffmann 2012-12-13 17:41:11 UTC 
Description of problem:
After installation of f17 from DVD, I launched "yum update" today. 
Since then, I have a lot of new problems, among them mate does not start any more.


Version-Release number of selected component:
mate-window-manager-1.5.2-7.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        marco
crash_function: g_logv
kernel:         3.3.4-5.fc17.x86_64

truncated backtrace:
:Thread no. 1 (6 frames)
: #0 g_logv at gmessages.h:101
: #2 g_settings_set_property at gsettings.c:492
: #3 object_set_property at gobject.c:1352
: #4 g_object_constructor at gobject.c:1863
: #6 g_object_new_valist at gobject.c:1830
: #8 meta_prefs_init at core/prefs.c:859
Comment 1 Dirk Hoffmann 2012-12-13 17:41:13 UTC 
Created attachment 663082 [details]
File: core_backtrace
Comment 2 Dirk Hoffmann 2012-12-13 17:41:15 UTC 
Created attachment 663083 [details]
File: environ
Comment 3 Dirk Hoffmann 2012-12-13 17:41:17 UTC 
Created attachment 663084 [details]
File: limits
Comment 4 Dirk Hoffmann 2012-12-13 17:41:20 UTC 
Created attachment 663085 [details]
File: backtrace
Comment 5 Dirk Hoffmann 2012-12-13 17:41:22 UTC 
Created attachment 663086 [details]
File: cgroup
Comment 6 Dirk Hoffmann 2012-12-13 17:41:23 UTC 
Created attachment 663087 [details]
File: smolt_data
Comment 7 Dirk Hoffmann 2012-12-13 17:41:25 UTC 
Created attachment 663088 [details]
File: executable
Comment 8 Dirk Hoffmann 2012-12-13 17:41:28 UTC 
Created attachment 663089 [details]
File: maps
Comment 9 Dirk Hoffmann 2012-12-13 17:41:30 UTC 
Created attachment 663090 [details]
File: dso_list
Comment 10 Dirk Hoffmann 2012-12-13 17:41:32 UTC 
Created attachment 663091 [details]
File: proc_pid_status
Comment 11 Dirk Hoffmann 2012-12-13 17:41:34 UTC 
Created attachment 663092 [details]
File: var_log_messages
Comment 12 Dirk Hoffmann 2012-12-13 17:41:36 UTC 
Created attachment 663093 [details]
File: open_fds
Comment 13 Dirk Hoffmann 2012-12-13 22:14:05 UTC 
I beleive that I gave a partial analysis of this bug in #887040
Comment 14 Dirk Hoffmann 2012-12-13 22:14:51 UTC 
(In reply to comment #13)
> I beleive that I gave a partial analysis of this bug in #887040

bug #887040?
Comment 15 Dan Mashal 2012-12-14 05:53:02 UTC 
Please run "su -c 'yum update --enablerepo=updates-testing'" and report back.
Comment 16 Dirk Hoffmann 2012-12-14 08:02:37 UTC 

*** This bug has been marked as a duplicate of bug 887040 ***