Bug 646055 - [abrt] crash in gnome-disk-utility-2.30.1-1.fc13: gdu_shell_get_toplevel: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-disk-utility-2.30.1-1.fc13: gdu_shell_get_toplevel: Pro...
Keywords:
Status: CLOSED DUPLICATE of bug 606998
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-disk-utility
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:11636257add6b7ccca30209254e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-24 06:46 UTC by Johnson Lai
Modified: 2013-03-06 04:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:53:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.01 KB, text/plain)
2010-10-24 06:46 UTC, Johnson Lai
no flags Details

Description Johnson Lai 2010-10-24 06:46:30 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: palimpsest
comment: I was using DISK Utiliy to check the filesystem of the MOUNTED and ACTIVE partitioned and then it gave me errors shown.
component: gnome-disk-utility
crash_function: gdu_shell_get_toplevel
executable: /usr/bin/palimpsest
global_uuid: 11636257add6b7ccca30209254ec057a21246fd7
kernel: 2.6.33.3-85.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)

How to reproduce
-----
1. Open DISK UTILITY (Ver 2.30.1)
2. Select the ACTIVE and MOUNTED disk partitions
3. Select Check Filesystem

Comment 1 Johnson Lai 2010-10-24 06:46:33 UTC
Created attachment 455312 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:53:37 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:53:37 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 #606998.

Sorry for the inconvenience.


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