Bug 672454 - [abrt] gtkpod-1.0.0-2.fc14: dequeue_pending_request: Process /usr/bin/gtkpod was killed by signal 6 (SIGABRT)
Summary: [abrt] gtkpod-1.0.0-2.fc14: dequeue_pending_request: Process /usr/bin/gtkpod ...
Keywords:
Status: CLOSED DUPLICATE of bug 706603
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkpod
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Todd Zullinger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9286be154a509ad85859beec940...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 06:47 UTC by MG
Modified: 2012-03-21 14:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 14:59:34 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (37.12 KB, text/plain)
2011-01-25 06:47 UTC, MG 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description MG 2011-01-25 06:47:55 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gtkpod
component: gtkpod
crash_function: dequeue_pending_request
executable: /usr/bin/gtkpod
kernel: 2.6.35.10-74.fc14.i686.PAE
package: gtkpod-1.0.0-2.fc14
rating: 4
reason: Process /usr/bin/gtkpod was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295936390
uid: 500

How to reproduce
-----
1. Connect IPOD and mount (if not auto mounted)
2. Fire Up gtkpod
3. Filter tracks to copy from iPod

Filter applied was:  "Special Tab" => Logic: ALL => Modified:  > 10/12/2010 0:00

4. Select All tracks
5. Select "Export Tracks from Database" => Selected Tracks
6. Watch the extract execute and then crash.
Comment 1 MG 2011-01-25 06:47:58 UTC 
Created attachment 475112 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:59:34 UTC 
Backtrace analysis found this bug to be similar to bug #706603, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 706603 ***
Note You need to log in before you can comment on or make changes to this bug.