Bug 1460517 - pulseaudio errors when starting gtk app with enabled canberra-gtk-module
pulseaudio errors when starting gtk app with enabled canberra-gtk-module
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
25
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-11 15:01 EDT by Peter Backes
Modified: 2017-11-16 18:17 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-16 18:17:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Backes 2017-06-11 15:01:04 EDT
Description of problem:
When I start xarchiver while canberra-gtk-module is enabled, I get pulseaudio errors in the journal. No such errors when canberra-gtk-module is disabled.

Version-Release number of selected component (if applicable):
pulseaudio-10.0-2.fc25.i686

How reproducible:
always

Steps to Reproduce:
1. sudo dnf install libcanberra-gtk2-0.30-11.fc24.i686 xarchiver-0.5.4-3.fc24.i686
2. echo gtk-modules=canberra-gtk-module >> ~/.gtkrc-2.0
3. xarchiver

Actual results:
The following errors show up in journal:

Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] shm.c: mmap() failed: Cannot allocate memory
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] pstream.c: Failed to create permanent mapping for memfd region with ID = 460474063
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] protocol-native.c: Failed to register memfd mempool. Reason: could not attach memfd SHM ID to pipe
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] shm.c: mmap() failed: Cannot allocate memory
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] protocol-native.c: Disabling srbchannel, reason: Failed to allocate shared writable memory pool.
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] shm.c: mmap() failed: Cannot allocate memory
Jun 11 20:48:35 localhost pulseaudio[1185]: [pulseaudio] pstream.c: Failed to create permanent mapping for memfd region with ID = 2058202185

Expected results:
no errors

Additional info:
The same thing actually happens with gvim, which uses gtk3 (sudo dnf install libcanberra-gtk3-0.30-11.fc24.i686 vim-X11-8.0.617-1.fc25.i686; test -f ~/.config/gtk-3.0/settings.ini || echo '[Settings]' > ~/.config/gtk-3.0/settings.ini; echo 'gtk-modules=canberra-gtk-module' >> ~/.config/gtk-3.0/settings.ini; gvim)
Comment 1 Fedora End Of Life 2017-11-16 14:06:07 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 2 Peter Backes 2017-11-16 18:17:11 EST
Cannot reproduce the issue anymore with pulseaudio-11.1-2.fc26.x86_64

Note You need to log in before you can comment on or make changes to this bug.