Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel.testing > #1399 > unrolled thread
| Started by | Elija Goitke <pxlkngdev@gmail.com> |
|---|---|
| First post | 2023-06-18 02:50 +0200 |
| Last post | 2025-07-24 02:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.devel.testing
Bug#1038418: upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm Elija Goitke <pxlkngdev@gmail.com> - 2023-06-18 02:50 +0200
Bug#1038418: marked as done (upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-07-24 02:50 +0200
| From | Elija Goitke <pxlkngdev@gmail.com> |
|---|---|
| Date | 2023-06-18 02:50 +0200 |
| Subject | Bug#1038418: upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm |
| Message-ID | <GHOM9-gGL2-1@gated-at.bofh.it> |
Package: upgrade-reports
Severity: normal
The described issue can be reproduced on a fresh bullseye install made
through the latest
official bullseye installer. The issue only concerns the KDE Plasma desktop
environment version of Debian.
My previous release is: bullseye
I am upgrading to: bookworm
Upgrade date: 17.6.2023
Method: Minimal upgrade steps according to
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-
upgrading.en.html
Contents of /etc/apt/sources.list:
untouched, except changing "bullseye" to "bookworm" in order to
upgrade.
- Were there any non-Debian packages installed before the upgrade? If
so, what were they?
No
- Was the system pre-update a 'pure' system only containing packages
from the previous release? If not, which packages were not from that
release?
Yes, fresh install directly from official installer.
- Did any packages fail to upgrade?
No
- Were there any problems with the system after upgrading?
Yes, see below
Further Comments/Problems:
A fresh Debian 12 Bookworm installation (directly from the official
installer)
with the KDE Plasma desktop environment uses the pulseaudio server as a
default audio
middleware, but when upgrading from a fresh "off-the-shelf" Debian
11 Bullseye to 12 Bookworm (with the steps as advised by
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-
upgrading.en.html) pipewire-pulse and wireplumber get installed
automatically (apparently per
suggestion by package plasma-pa) and replace
pulseaudio from there on. Pulseaudio remains installed,
only being suppressed by pipewire-pulse.
I noticed this first on my own private Debian installation, where I recently
upgraded. I was also able to reproduce this on a fresh Debian 11 Bullseye
install where I then upgraded to Bookworm. (according to upgrade guidelines)
This behavior does not break system sound or usability as far as I can
assess, but since it
does deviate from the default KDE Plasma setup that you get from installing
Debian Bookworm directly from installer rather than upgrading to it, as
well as changing the
sound server from pulseaudio to pipewire without informing or asking the
user,
I assume this is still unwanted behavior and hence a bug.
Best regards.
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-07-24 02:50 +0200 |
| Subject | Bug#1038418: marked as done (upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm) |
| Message-ID | <LbSjL-2b8a-15@gated-at.bofh.it> |
| In reply to | #1399 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Thu, 24 Jul 2025 02:39:58 +0200 with message-id <aIGA3uo8wa9RPAi_@per.namespace.at> and subject line Re: Bug#1038418: upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm has caused the Debian Bug report #1038418, regarding upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1038418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038418 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.devel.testing
csiph-web