Description of problem: The crash happens while using the command: padsp gtick When you hit stop (obviously, after starting it), you get the crash. Version-Release number of selected component: gtick-0.4.2-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gtick crash_function: pa_memblock_unref kernel: 3.6.7-4.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 pa_memblock_unref at pulsecore/memblock.c:590 : #3 pa_memexport_process_release at pulsecore/memblock.c:1110 : #4 pa_memexport_free at pulsecore/memblock.c:1069 : #5 pa_pstream_unlink at pulsecore/pstream.c:974 : #7 context_unlink at pulse/context.c:211 : #8 pa_context_set_state at pulse/context.c:294 : #10 fd_info_free at utils/padsp.c:403 : #11 fd_info_unref at utils/padsp.c:448 : #12 close at utils/padsp.c:2418 : #13 dsp_close at dsp.c:605
Created attachment 655573 [details] File: core_backtrace
Created attachment 655574 [details] File: environ
Created attachment 655577 [details] File: limits
Created attachment 655579 [details] File: backtrace
Created attachment 655581 [details] File: cgroup
Created attachment 655583 [details] File: smolt_data
Created attachment 655585 [details] File: executable
Created attachment 655587 [details] File: maps
Created attachment 655589 [details] File: dso_list
Created attachment 655591 [details] File: proc_pid_status
Created attachment 655593 [details] File: var_log_messages
Created attachment 655595 [details] File: open_fds
I've rebased gtick to version 0.5.1, which among other things supports pulseaudio natively: https://admin.fedoraproject.org/updates/gtick-0.5.1-1.fc17 Please test if you see a crash with that version (using PA natively, or with padsp). Thanks!
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
mega whoops! It works fine now... in Fedora 19. Sorry, didn't see this up until now.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.