Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 612540 - [abrt] crash in xfce4-panel-4.6.4-1.fc13: raise: Process /usr/bin/xfce4-panel was killed by signal 6 (SIGABRT)
[abrt] crash in xfce4-panel-4.6.4-1.fc13: raise: Process /usr/bin/xfce4-panel...
Status: CLOSED DUPLICATE of bug 603338
Product: Fedora
Classification: Fedora
Component: xfce4-panel (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Kevin Fenzi
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-08 09:34 EDT by Joerg Stephan
Modified: 2010-07-18 15:55 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-18 15:55:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (26.60 KB, text/plain)
2010-07-08 09:35 EDT, Joerg Stephan
no flags Details

  None (edit)
Description Joerg Stephan 2010-07-08 09:34:59 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: xfce4-panel --sm-client-id 27ec6af07-fad9-4465-9077-c5040e4ff9e1
component: xfce4-panel
crash_function: raise
executable: /usr/bin/xfce4-panel
global_uuid: cc5cc54aad1bee8f974bee115d6b52f935bafb22
package: xfce4-panel-4.6.4-1.fc13
rating: 4
reason: Process /usr/bin/xfce4-panel was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Joerg Stephan 2010-07-08 09:35:01 EDT
Created attachment 430359 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-07-18 15:09:12 EDT
What were you doing when this crash happened? Can you duplicate it ?
Comment 3 Kevin Fenzi 2010-07-18 15:55:09 EDT
This looks very similar to 603338, so I am going to mark it as a dup and continue there.

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

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