Bug 639169

Summary: [abrt] xfce4-session-4.6.2-1.fc13: g_execute: Process /usr/bin/xfce4-session was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brendan Jones <brendan.jones.it>
Component: xfce4-sessionAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: any0n3, jlabocki, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:bfb4cc9656645cc10351e6bf8cb536f9f2144ede
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-30 23:21:34 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

Description Brendan Jones 2010-09-30 23:11:29 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/xfce4-session
component: xfce4-session
crash_function: g_execute
executable: /usr/bin/xfce4-session
kernel: 2.6.34.7-56.fc13.i686
package: xfce4-session-4.6.2-1.fc13
rating: 4
reason: Process /usr/bin/xfce4-session was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285887845
uid: 500

comment
-----
Autostart:
Compiz window manager running with Emerald Window decorator
Yakuake

How to reproduce
-----
1.Logged into XFCE4 from GDM after reboot
2.Happens every time
Comment 1 Brendan Jones 2010-09-30 23:11:33 UTC 
Created attachment 450907 [details]
File: backtrace
Comment 2 Michael Spahn 2010-09-30 23:17:49 UTC 
Does it work if you disable the autostart?

Disable one by one to check where it happens.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Kevin Fenzi 2010-09-30 23:21:34 UTC 
This looks like a dup of 572309. Moving over there. There's a debug step you can do there.

*** This bug has been marked as a duplicate of bug 572309 ***
Comment 4 Ruediger Landmann 2011-04-17 00:35:31 UTC 
*** Bug 692664 has been marked as a duplicate of this bug. ***