Bug 705921 - [abrt] gnome-disk-utility-2.32.0-1.fc14: gdu_shell_get_toplevel: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-disk-utility-2.32.0-1.fc14: gdu_shell_get_toplevel: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 666373
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-disk-utility
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c69b9b935e5b81b6a60a1490720...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 21:18 UTC by Ms. S. Barill
Modified: 2013-03-06 04:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:23:20 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (18.56 KB, text/plain)
2011-05-18 21:18 UTC, Ms. S. Barill
no flags Details

Description Ms. S. Barill 2011-05-18 21:18:53 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 19006 bytes
cmdline: palimpsest --show-volume /dev/sde1
component: gnome-disk-utility
Attached file: coredump, 3985408 bytes
crash_function: gdu_shell_get_toplevel
executable: /usr/bin/palimpsest
kernel: 2.6.35.13-91.fc14.i686
package: gnome-disk-utility-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305753086
uid: 500

How to reproduce
-----
1.unknown
2.
3.

Comment 1 Ms. S. Barill 2011-05-18 21:18:55 UTC
Created attachment 499697 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 17:23:20 UTC
Backtrace analysis found this bug to be similar to bug #666373, closing as duplicate.

Bugs which were found to be similar to this bug: bug #581526, bug #609430, bug #611117, bug #621874, bug #666373, bug #667687, bug #671247, bug #708754

This comment is automatically generated.

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


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