This bug was fixed in the package pipewire-media-session -
0.4.1-2ubuntu1
---
pipewire-media-session (0.4.1-2ubuntu1) jammy; urgency=medium
* Configure with-module-sets="" to disable audio by default (LP: #1953052)
You can reenable it by creating an empty file:
We do need pipewire-media-session since according to GNOME upstream
without it gnome shell recording would just stay pause and not actually
work, unsure if that's still true so worth testing
** Also affects: pipewire-media-session (Ubuntu Jammy)
Importance: Undecided
Assignee: Daniel van
It might be possible to refine further if not all of these need
removing:
> with-audio = [
> metadata
> default-nodes
> default-profile
> default-routes
> alsa-seq
> alsa-monitor
> ]
Hard to tell because the docs either aren't built properly in places,
don't exist at all for some things, or are
The offending package seems to be coming via:
ubuntu-meta >
gnome-remote-desktop >
pipewire-media-session | wireplumber
So it's a dependency we probably can't drop. Maybe a config change is
the only real option.
** No longer affects: alsa-utils (Ubuntu)
** No longer affects: pulseaudio
** Changed in: alsa-utils (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: pipewire (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this
Thanks Cam Cope, that's an interesting fix.
It's probably better if we can avoid starting pipewire-media-session in
GNOME sessions without other config changes. I don't want to cripple
pipewire-media-session to the point of it not being able to replace
PulseAudio in other session types.
--
You
So I can confirm that copying /usr/share/pipewire/media-session.conf to
/etc/pipewire/media-session.d/media-session.conf and deleting these lines fixes
the issue:
$ diff /etc/pipewire/media-session.d/media-session.conf
/usr/share/pipewire/media-session.d/media-session.conf
94a95,116
>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pipewire (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
> TL;DR: pipewire-pulse and PulseAudio should *not* be installed at the
same time as they serve the same function and applications don't know
the difference.
This is not the case at least for the default Ubuntu flavor (w/ GNOME).
$ curl -s
I don't think the points I raised are upstream ones and I wouldn't take
them upstream myself. I think it's good (in the long term) and
appropriate that PipeWire upstream is a daemon, just not appropriate in
Ubuntu 22.04 since we've decided to stick with PulseAudio. Hence the
configuration changes
Daniel, I disagree.
PipeWire is meant to be a *drop-in replacement* for PulseAudio.
Applications that recognize PulseAudio are supposed to use it instead if
it's available in lieu of PulseAudio.
Both options need to be available, otherwise the entire goal of
PipeWire's audio capabilities of
This is definitely a bug and one we need to solve before the masses
start using jammy. So just closing it wouldn't be helpful.
I'm reminded a little of bug 1897965. Maybe we need either:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1897965/comments/16
or to modify
Ubuntu Studio lead here. We have been very closely watching the
development of PipeWire as it is of interest to a large amount of our
user base in the Audio Production world.
Please note that PipeWire, in its current iteration, is meant to be a
drop-in replacement for both PulseAudio and Jack
Corrado, this is still not ideal - while it appears to work at the
moment, having two audio servers with their own idea of volumes would
probably cause trouble going on.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
Problem seems solved for my 2 desktop and on my laptop:
corrado@corrado-n4-jammy-0202:~$ lsof /dev/snd/*
COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
pipewire 1393 corrado 43u CHR 116,1 0t0 566 /dev/snd/seq
pipewire 1393 corrado 44u CHR 116,1 0t0 566
After last updates problem disappeared again
corrado@corrado-n4-jj-0203:~$ lsof /dev/snd/*
COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
pipewire 1611 corrado 43u CHR 116,1 0t0 621 /dev/snd/seq
pipewire 1611 corrado 44u CHR 116,1 0t0 621 /dev/snd/seq
OK that matches what we have observed elsewhere. In theory there is an
audio device reservation protocol which is obeyed by both pulseaudio and
pipewire, but in practice it looks like at least some versions of
pipewire media server component do not obey the protocol in full (i.e.
are still using
Igor, I'm responding as someone also affected by this issue. Using the
command you gave in comment #25 I saw that both pulseaudio and pipewire
were using the same audio device(s).
I used the command 'sudo systemctl disable --global pipewire' to disable
pipewire and deleted the ~/.config/pulse/
Please have a look which apps are using audio devices: 'lsof /dev/snd/*
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
On a different Jammy install on a different desktop the problem dos
still occur.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after
On my desktop after a lot of new updates the sound level is NOT reset at
reboot.
I see pipewire and pulseaudio are both installed but i don't know if
they are active.
corrado@corrado-p5-jj-0203:~$ dpkg -l | grep pipewire
ii gstreamer1.0-pipewire:amd640.3.45-1
Sebastien, if distribution is intended to provide pipewire function for
video only, there is no need to install audio parts. At very least
'with-pulse' 'with-jack' and other files directly or transitively
enabling 'with-audio' pipewire parts should not be installed so pipewire
media session daemon
I can confirm that after stopping pipewire temporarily by:
$ systemctl --user stop pipewire.socket pipewire.service
The volume level is properly recovered across plugging in and out a headset for
example, which is good.
Both pulseaudio and pipewire are installed out of the box and running if
I'm
what's the output of
$ dpkg -l | grep pipewire
?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status in alsa-utils
how can i tell if i have pulseaudio and pipewire activated?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status in
Do you have both pulseaudio and pipewire audio enabled simultaneously?
At least system log suggests pipewire with session manager is also being
activated, this could cause issues if both attempt to restore volumes
for some reason.
--
You received this bug notification because you are a member of
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Problem reappeared
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status in alsa-utils package in Ubuntu:
Confirmed
Bug
Problem disappeared after today updates(?) on my 2 desktop 3 different install
of Jammy.
but NOT disappeared on my laptop also updated today.
Let me know what useful information I can provide.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I did some tests by changing the volume and inserting and removing the
headphones but I don't see anything in the journalctl.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
not 'journalctl -b 1 > log' but 'journalctl -b-1 > log'
.. log attached
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+attachment/5557907/+files/log
--
You received this bug notification because you are a member of Desktop
Packages, which is
It's a bit weird, trying in a VM in a simple wmaker session, changing
the level in pavucontrol and restarting the machine the sound is
correctly restored on the same position after the restart so the systemd
unit seems to be working as expected.
Could someone having the issue change the level,
This bug also affects me. I am using Ubuntu MATE (Jammy).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status in
Volume is reset to 70% also when i insert or remove headset.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status in
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
Status
My Jammy was not upgraded from impish but fresh install from ISO.
and i see the problem on 2 different install on same PC.
I don't have the problem on impish installed on different partition of same
disk same PC.
--
You received this bug notification because you are a member of Desktop
Did the issue started after upgrading to the new serie or was it already
there in impish?
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
I would like to add that my computer resets the volume to 70% after I
resume from suspending.
DM: gdm
DE: gnome flashback
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
@corrado venturini
Thanks for reporting this bug as i was about to do the same.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after
Saving the state and restoring it is alsa's job, gnome-control-center
isn't a service and not doing anything when not started
** Summary changed:
- In Jammy gnome-control-center sound reset after reboot
+ In Jammy sound level reset after reboot
** Package changed: gnome-control-center (Ubuntu)
41 matches
Mail list logo
