Bug 669978

Summary: [abrt] gpodder-2.8-2.fc14: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steve Smethurst <ssmethurst>
Component: gpodderAssignee: Jef Spaleta <jspaleta>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: jspaleta, vpvainio
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:be6558a28055977a643fb4812ef9dc78543200f8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-16 22:36:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Steve Smethurst 2011-01-16 13:19:37 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gpodder
comment: I'm not sure I could reproduce it.  This is normal activity for me, and this is the first time GPodder has responded by crashing.
component: gpodder
executable: /usr/bin/python
kernel: 2.6.35.10-74.fc14.i686
package: gpodder-2.8-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295183162
uid: 1000

How to reproduce
-----
1. GPodder had been working for a few days unattended
2. I was reading pages in Firefox, plugged in my usb podplayer, nautilus windows opened 
3. Gpodder crashed
Comment 1 Steve Smethurst 2011-01-16 13:19:41 UTC 
Created attachment 473698 [details]
File: backtrace
Comment 2 Ville-Pekka Vainio 2011-01-16 22:36:10 UTC 
The backtrace is incomplete and doesn't show where the crash is happening. The rest of the backtrace of thread one points to ffmpeg, which is not in Fedora. For these reasons, I'll close this bug. If you find out a way to reproduce the bug and get a complete backtrace, you can report the bug to the repository you installed ffmpeg from.