Bug 598758 - [abrt] crash in gnome-panel-2.30.0-1.fc13: raise: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: raise: Process /usr/bin/gnome-pane...
Keywords:
Status: CLOSED DUPLICATE of bug 619272
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5f5080348c468c159b6b40e47fd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 00:52 UTC by evans ferdinand
Modified: 2010-11-06 06:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-06 06:10:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (45.19 KB, text/plain)
2010-06-02 00:52 UTC, evans ferdinand
no flags Details

Description evans ferdinand 2010-06-02 00:52:17 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: raise
executable: /usr/bin/gnome-panel
global_uuid: 5f5080348c468c159b6b40e47fded608d45835bc
kernel: 2.6.33.3-85.fc13.i686.PAE
package: gnome-panel-2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 evans ferdinand 2010-06-02 00:52:22 UTC
Created attachment 418869 [details]
File: backtrace

Comment 2 sayag 2010-11-01 15:11:56 UTC
Package: gnome-panel-2.30.0-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. go to ntfs drive
2. sarch a chm file
3. open it with gnochm


Comment
-----
https://bugzilla.redhat.com/show_bug.cgi?id=648533 => python bug linked to this crash

Comment 3 Jeff Raber 2010-11-06 06:10:04 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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


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