Bug 722719 - [abrt] rhythmbox-0.13.3-1.fc14: pad_block_callback_marshal: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.3-1.fc14: pad_block_callback_marshal: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 666071
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:27cae2646bd272728d04d034c63...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-16 23:58 UTC by N. A. Courtney
Modified: 2012-03-20 17:44 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (120.73 KB, text/plain)
2011-07-16 23:58 UTC, N. A. Courtney 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description N. A. Courtney 2011-07-16 23:58:18 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 123628 bytes
cmdline: rhythmbox
comment: No comments, the program just crashed
component: rhythmbox
Attached file: coredump, 185348096 bytes
crash_function: pad_block_callback_marshal
executable: /usr/bin/rhythmbox
kernel: 2.6.35.13-92.fc14.i686
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. I couldn't tell you this is the first time it happened.
time: 1310859502
uid: 500
Comment 1 N. A. Courtney 2011-07-16 23:58:20 UTC 
Created attachment 513504 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:44:25 UTC 
Backtrace analysis found this bug to be similar to bug #666071, closing as duplicate.

Bugs which were found to be similar to this bug: bug #662812, bug #666071, bug #675457, bug #724012

This comment is automatically generated.

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