Bug 1032406

Summary: [abrt] pavucontrol-2.0-4.fc20: read_callback: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: igor.redhat <igor.redhat>
Component: pavucontrolAssignee: Lennart Poettering <lpoetter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: abask, belegdol, jones.peter.busi, lpoetter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c0fe3520fdf42a7182cd25bc6fe580d4ae0a19cc
Whiteboard: abrt_hash:7ea4f2d0f8b7fde7bfe9c71df5d7ee0e9cad0eaa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:02:54 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description igor.redhat@gmail.com 2013-11-20 06:32:13 UTC
Version-Release number of selected component:
pavucontrol-2.0-4.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        pavucontrol
crash_function: read_callback
executable:     /usr/bin/pavucontrol
kernel:         3.11.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 read_callback at mainwindow.cc:494
 #1 pstream_memblock_callback at pulse/context.c:365
 #2 do_read at pulsecore/pstream.c:865
 #3 do_pstream_read_write at pulsecore/pstream.c:185
 #4 dispatch_func at pulse/glib-mainloop.c:584
 #9 gtk_main at gtkmain.c:1158
 #10 Gtk::Main::run at main.cc:399

Comment 1 igor.redhat@gmail.com 2013-11-20 06:32:20 UTC
Created attachment 826445 [details]
File: backtrace

Comment 2 igor.redhat@gmail.com 2013-11-20 06:32:23 UTC
Created attachment 826446 [details]
File: cgroup

Comment 3 igor.redhat@gmail.com 2013-11-20 06:32:28 UTC
Created attachment 826447 [details]
File: core_backtrace

Comment 4 igor.redhat@gmail.com 2013-11-20 06:32:32 UTC
Created attachment 826448 [details]
File: dso_list

Comment 5 igor.redhat@gmail.com 2013-11-20 06:32:35 UTC
Created attachment 826449 [details]
File: environ

Comment 6 igor.redhat@gmail.com 2013-11-20 06:32:38 UTC
Created attachment 826450 [details]
File: exploitable

Comment 7 igor.redhat@gmail.com 2013-11-20 06:32:41 UTC
Created attachment 826451 [details]
File: limits

Comment 8 igor.redhat@gmail.com 2013-11-20 06:32:45 UTC
Created attachment 826452 [details]
File: maps

Comment 9 igor.redhat@gmail.com 2013-11-20 06:32:48 UTC
Created attachment 826453 [details]
File: open_fds

Comment 10 igor.redhat@gmail.com 2013-11-20 06:32:51 UTC
Created attachment 826454 [details]
File: proc_pid_status

Comment 11 igor.redhat@gmail.com 2013-11-20 06:32:54 UTC
Created attachment 826455 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 09:48:48 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2015-06-29 13:02:54 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.