Bug 575958

Summary: SIGSEGV with 0x1 tag in metadataparse_handle_unit_tags running /home/fauz/.python-eggs/elisa_plugin_amp-0.4.egg-tmp/elisa/plugins/amp/slave.py
Product: [Fedora] Fedora Reporter: johnteasley
Component: gstreamerAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ajax, dmalcolm, ivazqueznet, james.antill, jonathansteffan, otte
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:8e05045c59e6d4cf48969a575fb925e4145b45b1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-23 15:20:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description johnteasley 2010-03-22 19:46:12 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /home/fauz/.python-eggs/elisa_plugin_amp-0.4.egg-tmp/elisa/plugins/amp/slave.py elisa.plugins.gstreamer.amp_slave.run_slave unix:/tmp/elisa-metadata-HdlPkQ.socket Slave-2042
component: python
executable: /usr/bin/python
kernel: 2.6.32.9-70.fc12.x86_64
package: python-2.6.2-4.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 johnteasley 2010-03-22 19:46:15 UTC 
Created attachment 401857 [details]
File: backtrace
Comment 2 johnteasley 2010-03-22 20:01:38 UTC 

Comment
-----
have not had the issue happen again after a python update.
Comment 3 Dave Malcolm 2010-03-22 22:52:19 UTC 
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running the following command?
  rpm -qa "gstreamer*"

Looking at the backtrace, it looks like the problem occurred in thread #1 in IA__g_str_hash, within metadataparse_handle_unit_tags (frame #7), with a invalid tag pointer of 0x1.

Reassigning component from "python" to "gstreamer";  hopefully the gstreamer maintainer will be able to figure this out further or reassign as necessary.
Comment 4 Benjamin Otte 2010-03-23 15:20:01 UTC 
This looks like a duplicate of bug 572800 to me, so I'm going to close this. If you can reproduce this bug with gstreamer-0.10.28-2 or newer, please reopen it.

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