Bug 645029 - [abrt] gnome-disk-utility-2.30.1-1.fc13: gdu_shell_get_toplevel: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-disk-utility-2.30.1-1.fc13: gdu_shell_get_toplevel: Process /usr...
Status: CLOSED DUPLICATE of bug 597444
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-disk-utility   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:efac55be8120b06242292324f2d...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-20 18:31 UTC by Glineur
Modified: 2013-03-06 04:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 17:35:08 UTC
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 (19.00 KB, text/plain)
2010-10-20 18:31 UTC, Glineur 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Glineur 2010-10-20 18:31:01 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: palimpsest
component: gnome-disk-utility
crash_function: gdu_shell_get_toplevel
executable: /usr/bin/palimpsest
kernel: 2.6.34.7-56.fc13.x86_64
package: gnome-disk-utility-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1287599415
uid: 500
Comment 1 Glineur 2010-10-20 18:31:04 UTC 
Created attachment 454637 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:35:08 UTC 

*** This bug has been marked as a duplicate of bug 597444 ***
Comment 3 Karel Klíč 2010-11-08 17:35:08 UTC 
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 #597444.

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