Bug 641959

Summary:

[abrt] gmixer-1.3-17.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)

Product:

[Fedora] Fedora

Reporter:

Terry Wallwork <terrywallwork>

Component:

libxcb

Assignee:

Adam Jackson <ajax>

Status:

CLOSED DUPLICATE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

low

Version:

CC:

ajax, leigh123linux, mads, otte, tomspur

Target Milestone:

---

Keywords:

Reopened

Target Release:

---

Hardware:

i686

OS:

Linux

Whiteboard:

abrt_hash:e96059c446643390e94551082252aa50350845b6

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2010-11-16 19:09:12 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 Terry Wallwork 2010-10-11 15:53:33 UTC

abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python -OO /usr/bin/gmixer -d
component: gmixer
crash_function: raise
executable: /usr/bin/python
kernel: 2.6.34.7-56.fc13.i686
package: gmixer-1.3-17.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286215514
uid: 500

Comment 1 Terry Wallwork 2010-10-11 15:53:38 UTC

Created attachment 452749 [details]
File: backtrace

Comment 2 Thomas Spura 2010-10-11 16:44:38 UTC

*** Bug 641960 has been marked as a duplicate of this bug. ***

Comment 3 Thomas Spura 2010-10-11 16:50:11 UTC

Thanks for the bug report.

Meego has a similar crash:
http://140.211.166.227/backtrace.php?number=11396

There cromium was the reason for the crash, so gmixer should'nt be the fault...

This looks more than a bug in gstreamer:
#1  0x001e2df6 in __poll (fds=0xafd001c0, nfds=2, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
        resultvar = <value optimized out>
        resultvar = <value optimized out>
        oldtype = -516
        result = <value optimized out>
#2  0x00a11c8f in task_monitor_alsa (data=0xa0fa2d8) at gstalsamixer.c:453
        pfds = 0xafd001c0
        nfds = 1
        rnfds = <value optimized out>
        revents = <value optimized out>
        mixer = 0xa0fa2d8
        ret = <value optimized out>
        __PRETTY_FUNCTION__ = "task_monitor_alsa"
#3  0x0360c0b1 in gst_task_func (task=0xa0b5918) at gsttask.c:271
        lock = 0xa0fa3f8
        tself = 0xa0fa7a8
        priv = 0xa0b5968
        __PRETTY_FUNCTION__ = "gst_task_func"


-> reassigning and hoping they have more knowledge, what's going on.

Comment 4 Benjamin Otte 2010-10-14 16:12:48 UTC

It's not the topmost thread printed that is causing the crash, but the other one. And that's a known bug in Xlib/X.

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

Comment 5 Mads Kiilerich 2010-10-28 14:27:19 UTC

Why is this gmixer bug marked as a duplicate of a firefox bug? I assume that was a typo and will reopen. If it was intentional please explain how they are related.

Comment 6 Benjamin Otte 2010-11-16 19:09:12 UTC

What part of my explanation above was unclear? It's a bug in X and as both Firefox and gmixer use X, they both suffer from the same bugs.

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

Comment 7 Mads Kiilerich 2010-11-16 19:36:58 UTC

I'm sorry. It wasn't clear to me why it was marked as a duplicate of a libxcb bug when it was a known bug in Xlib/X bug.