Bug 621982 - [abrt] crash in gtkpod-0.99.16-1.fc13: Process /usr/bin/gtkpod was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gtkpod-0.99.16-1.fc13: Process /usr/bin/gtkpod was killed by ...
Status: CLOSED DUPLICATE of bug 628187
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkpod   
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Todd Zullinger
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:73c7dbbc98e2d1c63d44a18153c...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-06 17:04 UTC by madanthonywayne
Modified: 2010-11-09 16:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 16:17:13 UTC
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 (46.75 KB, text/plain)
2010-08-06 17:04 UTC, madanthonywayne
no flags Details

Description madanthonywayne 2010-08-06 17:04:21 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gtkpod
component: gtkpod
crash_function: IA__gdk_window_set_geometry_hints
executable: /usr/bin/gtkpod
global_uuid: 73c7dbbc98e2d1c63d44a18153c17f7d02cadba5
package: gtkpod-0.99.16-1.fc13
rating: 4
reason: Process /usr/bin/gtkpod was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.Loaded gtkpod
2.Selected my ipod's library and copy'd to filesystem
3. gtkpod crashed

Comment 1 madanthonywayne 2010-08-06 17:04:23 UTC
Created attachment 437213 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 16:17:13 UTC

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

Comment 3 Karel Klíč 2010-11-09 16:17:13 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 #628187.

Sorry for the inconvenience.

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