Bug 617814 - [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 ...
Keywords:
Status: CLOSED DUPLICATE of bug 628187
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkpod
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Todd Zullinger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0efd79fa02ed67becd87a019664...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-24 06:55 UTC by Jochen Brinkmann
Modified: 2010-11-09 16:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:17:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (62.70 KB, text/plain)
2010-07-24 06:55 UTC, Jochen Brinkmann
no flags Details

Description Jochen Brinkmann 2010-07-24 06:55:02 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gtkpod
comment: tried to copy the content of my iPod to my Linux notebook
component: gtkpod
crash_function: IA__gdk_window_set_geometry_hints
executable: /usr/bin/gtkpod
global_uuid: 0efd79fa02ed67becd87a019664df7463fbd22ce
kernel: 2.6.33.6-147.fc13.x86_64
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. Connect iPod model xB913
2. right click Ipod in playlist
3. select 'copy tracks to file system'
4. ARGH!

Comment 1 Jochen Brinkmann 2010-07-24 06:55:05 UTC
Created attachment 434110 [details]
File: backtrace

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

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

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

Sorry for the inconvenience.


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