Bug 589430 - [abrt] crash in xfce4-session-4.6.1-5.fc13: g_execute: Process /usr/bin/xfce4-session was killed by signal 11 (SIGSEGV)
[abrt] crash in xfce4-session-4.6.1-5.fc13: g_execute: Process /usr/bin/xfce4...
Status: CLOSED DUPLICATE of bug 572309
Product: Fedora
Classification: Fedora
Component: xfce4-session (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Kevin Fenzi
Fedora Extras Quality Assurance
abrt_hash:b6539346892031255197a9e404a...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-06 02:47 EDT by Pavel Alexeev
Modified: 2010-05-25 06:04 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 06:04:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (25.39 KB, text/plain)
2010-05-06 02:47 EDT, Pavel Alexeev
no flags Details

  None (edit)
Description Pavel Alexeev 2010-05-06 02:47:06 EDT
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/xfce4-session
comment: Start session
component: xfce4-session
crash_function: g_execute
executable: /usr/bin/xfce4-session
global_uuid: b6539346892031255197a9e404a9b681a095aa9a
kernel: 2.6.33.1-24.fc13.i686
package: xfce4-session-4.6.1-5.fc13
rating: 4
reason: Process /usr/bin/xfce4-session was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Pavel Alexeev 2010-05-06 02:47:08 EDT
Created attachment 411840 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 06:04:53 EDT

*** This bug has been marked as a duplicate of bug 572309 ***
Comment 3 Karel Klíč 2010-05-25 06:04:53 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #572309.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.