Your message dated Mon, 5 Dec 2022 09:38:06 +0100
with message-id
<CA+6XHwRHas35LVdTSNofkJ36a2gi8ut=4jw4jgvs4zj-4bq...@mail.gmail.com>
and subject line Re: Bug#1025453: Bug#1024093: The problem is still present in
0.3.61-1
has caused the Debian Bug report #1025453,
regarding pipewire: Upgrade to pipewire 0.3.60-1 breaks sound
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 [email protected]
immediately.)
--
1025453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025453
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.60-1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
using pipewire 0.59-1 under debian testing (with pusleaudio package uninstalled
if this should matter) makes no problem. I have copied
/usr/share/doc/pipewire/examples/alsa.conf.d to /etc/alsa . However, after
upgrading today to pipewire 0.3.60-1 (and rebooting) sound is broken. KDE
notifications, firefox on yoputube or a aplay x.wav do not make any sound to
come out of my speakers. After downgrading again, everything seems to work fine
again.
Thanks,
Chris
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire depends on:
ii adduser 3.129
ii init-system-helpers 1.65.2
ii libpipewire-0.3-modules 0.3.60-1
ii pipewire-bin 0.3.60-1
pipewire recommends no packages.
pipewire suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Le lun. 5 déc. 2022 à 00:15, James Bottomley
<[email protected]> a écrit :
>
> On Sun, 2022-12-04 at 23:49 +0100, Dylan Aïssi wrote:
> > Le dim. 4 déc. 2022 à 23:28, James Bottomley
> >
> > So please restore the state of this bug report and open your own bug
> > report.
>
> I'm not really as expert in the bug control system as debian developers
> are supposed to be but I think I got this done.
>
By cloning #1024093, its full history was imported in your bug report #1025453.
And because both are fully unrelated, this is not needed and create more noise
than it is helpful. It's better to create a new bug report from scratch, if you
are not comfortable with the Debian BTS, you can use debian tool like
"reportbug" to create a proper bug report.
https://manpages.debian.org/unstable/reportbug/reportbug.1.en.html
Dylan
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
