VirtualBox Intel HD Audio and PipeWire Incompatibility / Audio broken after increasing ram to 5 GB / No sound after latest updates - PipeWire Bug?

VirtualBox
1

I discovered sound doesn’t play in Workstation after upgrading. It appears to be the entire VM. No sound in Tor Browser, VLC, or anything else.

Disabling and re-enabling audio from the virtual machine menu while running did not fix it.
Fully restarting the Workstation did not fix it.
I tried changing the audio controller in VB but it did not fix it.

I take VM snapshots before upgrading so I restored to before the upgrades and sure enough sound works.

I don’t know how to troubleshoot this issue if you could provide guidance please. I am using Whonix 17.

2

Upgraded builds can be more hassle than new builds.

Can you try a new build first? Once that works, we can attempt to fix the existing Whonix installation.

3

I’ve done some troubleshooting.

My existing workstation is upgraded from 17.0.4.5
I downloaded and imported a fresh workstation to test and it is version 17.1.1.5

The problem seemed to begin after the new swap file feature appeared in bootup, so I played around with the amount of RAM dedicated to the workstation:

  • Fresh boot with default 2 GiB RAM: works
  • RAM increased to 4 GiB: BROKEN
  • RAM increased to 9 GiB: BROKEN
  • RAM decreased back to 2 GiB: works again

This occurs without making any other changes to the machine.

To clarify “broken”: Videos do not play at all in Tor Browser (they buffer but freeze immediately and do not play, and no sound). Videos in VLC play but do not have sound.

I have 8 GiB RAM dedicated to my existing workstation. I tried setting it back to 2 GiB but it did not work unlike the test workstation.

4

Confirmed.

I think this is most likely a pipewire bug. I was able to reproduce this issue.

Non-issues:
swap-file-creator is not the cause. To exclude that possiblity, disable swap-file-creator.

More likely changes causing this:

debug output:

journalctl | grep pipew

Jan 24 13:31:12 host pipewire-pulse[1088]: mod.protocol-pulse: client 0x591d3aff9870 [VLC media player (LibVLC 3.0.20)]: stream 0x591d3afa39f0 OVERFLOW channel:0
Jan 24 13:31:12 host pipewire-pulse[1088]: mod.protocol-pulse: client 0x591d3aff9870 [VLC media player (LibVLC 3.0.20)]: stream 0x591d3afa39f0 OVERFLOW channel:0
Jan 24 13:31:12 host pipewire-pulse[1088]: mod.protocol-pulse: client 0x591d3aff9870 [VLC media player (LibVLC 3.0.20)]: stream 0x591d3afa39f0 OVERFLOW channel:0

cvlc Downloads/videoplayback.m4a

VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
[00005863995bcc70] dummy interface: using the dummy interface module…
[000077b04c000e60] mp4 demux: Fragment sequence discontinuity detected 1 != 0
[0000586399594210] pulse audio output error: overflow, flushing
[0000586399594210] pulse audio output error: overflow, flushing
[0000586399594210] pulse audio output error: overflow, flushing

mpv Downloads/videoplayback.m4a

(+) Audio --aid=1 --alang=eng (*) (aac 2ch 44100Hz)
AO: [pipewire] 44100Hz stereo 2ch floatp
A: -00:00:00 / 00:02:23 (0%)

This issue might be unspecific to Whonix. Generic Bug Reproduction might be required.

This could be a a pipewire bug. There are some bug reports against the Debian pipewire package (but upstream issues).

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pipewire

For example: OOM killed

Speculation: More RAM being available might confuse pipewire and trigger some memory leak, resulting in pipewire RAM usage ballooning and therefore getting OOM killed. But really it could be anything.

I don’t have a solution and this issue might be difficult to fix, meaning might remain unfixed for a long time unless a contributor helps. Related: Self Support First Policy

5

Confirmed on YouTube. Very most likely same issue was described in this forum thread.

6

This began happening after a certain date. Before then the extra RAM wasn’t an issue. My last working snapshot is from 12/2/23 so the breakage would’ve occurred after that time. Would it be possible to downgrade pipewire and see if that resolves the issue for the time being? I don’t have much technical knowledge but I might try doing it myself to see if it works. If we could determine which update broke the audio pipewire devs might even be able to identify the issue with git blame.

7

No update. Was a port. port from pulseaudio to pipewire for audio support

1 Like
8

I found this page after I encountered the same problem:
I have installed the newest version of Whonix 17 (fresh Virtualbox install) and I have increased the RAM to 6GB.
After increasing the RAM, I observed that the audio wasn’t working anymore.

Was there a fix for this problem? Is there an easy workaround for this issue (outside of setting the Audio controller from “Intel HD Audio” to “ICH AC97”)?

9

I had the same problem and managed to fix it. Now my audio works with 6 GB of RAM.

First uninstall both pipewire and pulseaudio:

sudo apt remove --purge pipewire pipewire-audio-client-libraries pipewire-pulse
sudo apt remove --purge pulseaudio pulseaudio-utils
sudo apt autoremove

Then install pulseaudio:

sudo apt update
sudo apt install pulseaudio pulseaudio-utils
sudo apt install pavucontrol

Then enable and start the pulse audio service:

systemctl --user enable pulseaudio
systemctl --user start pulseaudio

Then power off the system and start it again.

Make sure pulse audio is working.
pulseaudio --check should return nothing (if it returns something its an error).

Also make sure the service is active:

systemctl --user status pulseaudio

It should say active in green.

Then everything should be working even with 6 GB of RAM.

Note that my Audio Host Driver was set to Default and my Audio Controller was set to Intel HD Audio.

5 Likes
10

Try it?

1 Like
11

Bug reproduced with Whonix-Virtualbox.
Bug reproduced with Kicksecure-Virtualbox.

Cant reproduce it with Debian-Virtualbox.
Cant reproduce it with Whonix-Qubes.
Cant reproduce it with Debian-Qubes.

Thats mean for surely its not pipewire to be blamed, rather something effecting pipewire with specifically whonix/kicksecure on virtualbox.

Could it be vboxguest-addition/dkms which is installed from debian?

1 Like
12

Can it be produced on Whonix (or Kicksecure) KVM?

Did these use PipeWire? They might not use PipeWire by default.

Could be. Could be many reasons. Even ones hard to imagine.

Try removal.

sudo apt purge virtualbox-guest*

Then reboot.

Does that fix PipeWire?

13

There is no working sound there at the moment:

Yes:

  • Debian-Qubes
user@debian-personal:~$ pw-cli ls Node
	id 29, type PipeWire:Interface:Node/3
 		object.serial = "29"
 		factory.id = "10"
 		priority.driver = "20000"
 		node.name = "Dummy-Driver"
	id 30, type PipeWire:Interface:Node/3
 		object.serial = "30"
 		factory.id = "10"
 		priority.driver = "19000"
 		node.name = "Freewheel-Driver"
	id 37, type PipeWire:Interface:Node/3
 		object.serial = "37"
 		factory.id = "18"
 		client.id = "35"
 		priority.driver = "21499"
 		node.description = "Qubes Virtual Audio Sink"
 		node.name = "qubes-sink"
 		media.class = "Audio/Sink"
 		media.type = "Audio"
	id 38, type PipeWire:Interface:Node/3
 		object.serial = "38"
 		factory.id = "18"
 		client.id = "35"
 		priority.driver = "21500"
 		node.description = "Qubes Virtual Audio Source"
 		node.name = "qubes-source"
 		media.class = "Audio/Source"
 		media.type = "Audio"
	id 46, type PipeWire:Interface:Node/3
 		object.serial = "47"
 		factory.id = "10"
 		client.id = "33"
 		node.name = "Midi-Bridge"
 		media.class = "Midi/Bridge"
	id 58, type PipeWire:Interface:Node/3
 		object.serial = "69"
 		object.path = "alsa:pcm:0:front:0:playback"
 		factory.id = "18"
 		client.id = "33"
 		device.id = "57"
 		priority.session = "1009"
 		priority.driver = "1009"
 		node.description = "USB Audio Device Analog Stereo"
 		node.name = "alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo"
 		node.nick = "USB Audio Device"
 		media.class = "Audio/Sink"
	id 59, type PipeWire:Interface:Node/3
 		object.serial = "70"
 		object.path = "alsa:pcm:0:hw:0:capture"
 		factory.id = "18"
 		client.id = "33"
 		device.id = "57"
 		priority.session = "2000"
 		priority.driver = "2000"
 		node.description = "USB Audio Device Mono"
 		node.name = "alsa_input.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.mono-fallback"
 		node.nick = "USB Audio Device"
 		media.class = "Audio/Source"
user@debian-personal:~$
  • Whonix-Qubes
[workstation user ~]% pw-cli ls Node
	id 29, type PipeWire:Interface:Node/3
 		object.serial = "29"
 		factory.id = "10"
 		priority.driver = "20000"
 		node.name = "Dummy-Driver"
	id 30, type PipeWire:Interface:Node/3
 		object.serial = "30"
 		factory.id = "10"
 		priority.driver = "19000"
 		node.name = "Freewheel-Driver"
	id 36, type PipeWire:Interface:Node/3
 		object.serial = "36"
 		factory.id = "18"
 		client.id = "35"
 		priority.driver = "21499"
 		node.description = "Qubes Virtual Audio Sink"
 		node.name = "qubes-sink"
 		media.class = "Audio/Sink"
 		media.type = "Audio"
	id 39, type PipeWire:Interface:Node/3
 		object.serial = "39"
 		factory.id = "18"
 		client.id = "35"
 		priority.driver = "21500"
 		node.description = "Qubes Virtual Audio Source"
 		node.name = "qubes-source"
 		media.class = "Audio/Source"
 		media.type = "Audio"
	id 46, type PipeWire:Interface:Node/3
 		object.serial = "47"
 		factory.id = "10"
 		client.id = "33"
 		node.name = "Midi-Bridge"
 		media.class = "Midi/Bridge"
[workstation user ~]%

Sadly did not.

1 Like
14

We need help from upstream PipeWire to debug / report a bug / fix this.

Could you report this to upstream please? Just tell them upfront. Functional in Debian, broken in Kicksecure for VirtualBox.

15

Not sure how did you managed that without these errors:

[user ~]% sudo apt remove "--purge" pipewire pipewire-pulse pipewire-alsa*
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'pipewire-alsa' for glob 'pipewire-alsa*'
The following packages were automatically installed and are no longer required:
  libfreeaptx0 liblc3-0 libldacbt-abr2 libldacbt-enc2 liblilv-0-0 liblua5.3-0
  libpipewire-0.3-0 libpipewire-0.3-modules libsbc1 libserd-0-0 libsord-0-0
  libspa-0.2-bluetooth libspa-0.2-modules libsratom-0-0 libwireplumber-0.4-0
  pipewire-bin
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libasound2-plugins libpulsedsp libwrap0 pulseaudio pulseaudio-utils rtkit
Suggested packages:
  pavumeter paprefs avahi-daemon
The following packages will be REMOVED:
  kicksecure-xfce-vm* non-qubes-audio* pipewire* pipewire-alsa*
  pipewire-audio* pipewire-pulse* wireplumber*
The following NEW packages will be installed:
  libasound2-plugins libpulsedsp libwrap0 pulseaudio pulseaudio-utils rtkit
0 upgraded, 6 newly installed, 7 to remove and 0 not upgraded.
Need to get 1463 kB of archives.
After this operation, 6617 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://deb.debian.org/debian bookworm/main amd64 libwrap0 amd64 7.6.q-32 [54.9 kB]
Get:2 https://deb.debian.org/debian bookworm/main amd64 libasound2-plugins amd64 1.2.7.1-1 [75.2 kB]
Get:3 https://deb.debian.org/debian bookworm/main amd64 libpulsedsp amd64 16.1+dfsg1-2+b1 [36.8 kB]
Get:4 https://deb.debian.org/debian bookworm/main amd64 pulseaudio-utils amd64 16.1+dfsg1-2+b1 [88.8 kB]
Get:5 https://deb.debian.org/debian bookworm/main amd64 pulseaudio amd64 16.1+dfsg1-2+b1 [1174 kB]
Get:6 https://deb.debian.org/debian bookworm/main amd64 rtkit amd64 0.13-5 [33.3 kB]
Fetched 1463 kB in 0s (4229 kB/s) 
(Reading database ... 115099 files and directories currently installed.)
Removing kicksecure-xfce-vm (3:29.9-1) ...
Removing non-qubes-audio (3:29.9-1) ...
Removing pipewire-audio (0.3.65-3+deb12u1) ...
Removing wireplumber (0.4.13-1) ...
Removing pipewire-pulse (0.3.65-3+deb12u1) ...
Removing pipewire-alsa:amd64 (0.3.65-3+deb12u1) ...
Removing pipewire:amd64 (0.3.65-3+deb12u1) ...
Selecting previously unselected package libwrap0:amd64.
(Reading database ... 114953 files and directories currently installed.)
Preparing to unpack .../0-libwrap0_7.6.q-32_amd64.deb ...
Unpacking libwrap0:amd64 (7.6.q-32) ...
Selecting previously unselected package libasound2-plugins:amd64.
Preparing to unpack .../1-libasound2-plugins_1.2.7.1-1_amd64.deb ...
Unpacking libasound2-plugins:amd64 (1.2.7.1-1) ...
Selecting previously unselected package libpulsedsp:amd64.
Preparing to unpack .../2-libpulsedsp_16.1+dfsg1-2+b1_amd64.deb ...
Unpacking libpulsedsp:amd64 (16.1+dfsg1-2+b1) ...
Selecting previously unselected package pulseaudio-utils.
Preparing to unpack .../3-pulseaudio-utils_16.1+dfsg1-2+b1_amd64.deb ...
Unpacking pulseaudio-utils (16.1+dfsg1-2+b1) ...
Selecting previously unselected package pulseaudio.
Preparing to unpack .../4-pulseaudio_16.1+dfsg1-2+b1_amd64.deb ...
Unpacking pulseaudio (16.1+dfsg1-2+b1) ...
Selecting previously unselected package rtkit.
Preparing to unpack .../5-rtkit_0.13-5_amd64.deb ...
Unpacking rtkit (0.13-5) ...
Setting up rtkit (0.13-5) ...
Setting up libasound2-plugins:amd64 (1.2.7.1-1) ...
Setting up libpulsedsp:amd64 (16.1+dfsg1-2+b1) ...
Setting up libwrap0:amd64 (7.6.q-32) ...
Setting up pulseaudio-utils (16.1+dfsg1-2+b1) ...
Setting up pulseaudio (16.1+dfsg1-2+b1) ...
Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr
/lib/systemd/user/pulseaudio.service.
Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/
lib/systemd/user/pulseaudio.socket.
Processing triggers for security-misc (3:38.7-1) ...
INFO: triggered security-misc: 'security-misc' security-misc DPKG_MAINTSCRIPT_NA
ME: 'postinst' $\@: 'triggered /usr' 2: '/usr'
/usr/libexec/security-misc/mmap-rnd-bits: INFO: Successfully written ASLR map co
nfig file:
/etc/sysctl.d/30_security-misc_aslr-mmap.conf
Running SUID Disabler and Permission Hardener... See also:
https://www.kicksecure.com/wiki/SUID_Disabler_and_Permission_Hardener
/var/lib/dpkg/info/security-misc.postinst: INFO: running: permission-hardener en
able
permission-hardener: [NOTICE]: Run: dpkg-statoverride --add --update root root 0
644 /etc/hosts.allow
permission-hardener: [NOTICE]: Run: dpkg-statoverride --add --update root root 0
644 /etc/hosts.deny
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/xen’: Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/w83977f_wdt.ko’: 
Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/w83877f_wdt.ko’: 
Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/xen_wdt.ko’: Bad 
message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wdat_wdt.ko’: Bad
 message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/watchdog.ko’: Bad
 message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wafer5823wdt.ko’:
 Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wdt_pci.ko’: Bad 
message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/xen’: Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/w83977f_wdt.ko’: 
Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/w83877f_wdt.ko’: 
Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/xen_wdt.ko’: Bad 
message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wdat_wdt.ko’: Bad
 message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/watchdog.ko’: Bad
 message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wafer5823wdt.ko’:
 Bad message
find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/watchdog/wdt_pci.ko’: Bad 
message
permission-hardener: [NOTICE]: To compare the current and previous permission mo
des, install 'meld' (or preferred diff tool) for comparison of file mode changes
:
    sudo apt install --no-install-recommends meld
    meld /var/lib/permission-hardener/existing_mode/statoverride /var/lib/permis
sion-hardener/new_mode/statoverride
/var/lib/dpkg/info/security-misc.postinst: INFO: Permission hardening success.
dpkg: unrecoverable fatal error, aborting:
 unable to truncate for updated status of 'security-misc': Read-only file system
dpkg: error: unable to access the dpkg database directory /var/lib/dpkg: Read-on
ly file system
E: Sub-process /usr/bin/dpkg returned an error code (2)
E: Sub-process dpkg --set-selections returned an error code (2)
E: Couldn't revert dpkg selection for approved remove/purge after an error was encountered!
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - pkgDPkgPM::Go (30: Read-only file system)
zsh: exit 100   sudo apt remove "--purge" pipewire pipewire-pulse pipewire-alsa*
[user ~]% sudo apt update && sudo apt full-upgrade && sudo apt autoremove "--purge" && sudo apt autoclean
Hit:1 https://deb.debian.org/debian bookworm InRelease
Err:1 https://deb.debian.org/debian bookworm InRelease                         
  Couldn't create temporary file /tmp/apt.conf.RVCvgd for passing config to apt-key
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease                 
Err:2 https://deb.debian.org/debian bookworm-updates InRelease                 
  Couldn't create temporary file /tmp/apt.conf.BbSWYh for passing config to apt-key
Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease       
Err:3 https://deb.debian.org/debian-security bookworm-security InRelease       
  Couldn't create temporary file /tmp/apt.conf.tihpxx for passing config to apt-key
Hit:4 https://deb.debian.org/debian bookworm-backports InRelease               
Err:4 https://deb.debian.org/debian bookworm-backports InRelease               
  Couldn't create temporary file /tmp/apt.conf.liD9Jr for passing config to apt-key
Ign:5 https://fasttrack.debian.net/debian bookworm-fasttrack InRelease         
Hit:6 tor+https://deb.kicksecure.com bookworm InRelease                        
Err:6 tor+https://deb.kicksecure.com bookworm InRelease 
  Couldn't create temporary file /tmp/apt.conf.O1QGgO for passing config to apt-key
Err:7 https://fasttrack.debian.net/debian bookworm-fasttrack Release
  Could not open file /var/lib/apt/lists/partial/fasttrack.debian.net_debian_dists_bookworm-fasttrack_Release - open (30: Read-only file system) [IP: 185.181.160.236 443]
Reading package lists... Done                           
W: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/lib/apt/lists/lock
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.NkjK4F - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.IagP1Q - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.siK6lV - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.W8TuRt - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.8KzlqI - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.gbKrtj - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_bookworm_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian bookworm InRelease: Couldn't create temporary file /tmp/apt.conf.RVCvgd for passing config to apt-key
W: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_bookworm-updates_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian bookworm-updates InRelease: Couldn't create temporary file /tmp/apt.conf.BbSWYh for passing config to apt-key
W: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian-security_dists_bookworm-security_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian-security bookworm-security InRelease: Couldn't create temporary file /tmp/apt.conf.tihpxx for passing config to apt-key
W: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_bookworm-backports_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-backports_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-backports_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-backports_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-backports_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian bookworm-backports InRelease: Couldn't create temporary file /tmp/apt.conf.liD9Jr for passing config to apt-key
W: Problem unlinking the file /var/lib/apt/lists/partial/fasttrack.debian.net_debian_dists_bookworm-fasttrack_InRelease - PrepareFiles (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/deb.kicksecure.com_dists_bookworm_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/deb.kicksecure.com_dists_bookworm_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/deb.kicksecure.com_dists_bookworm_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/deb.kicksecure.com_dists_bookworm_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/deb.kicksecure.com_dists_bookworm_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: tor+https://deb.kicksecure.com bookworm InRelease: Couldn't create temporary file /tmp/apt.conf.O1QGgO for passing config to apt-key
W: Problem unlinking the file /var/lib/apt/lists/partial/fasttrack.debian.net_debian_dists_bookworm-fasttrack_Release - PrepareFiles (30: Read-only file system)
E: The repository 'https://fasttrack.debian.net/debian bookworm-fasttrack Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (30: Read-only file system)
zsh: exit 100   sudo apt update
[user ~]%

once pipewire going to be removed, the system will automatically install pulseaudio which lead to permission mess.

1 Like
16
1 Like
17

Found the issue, its within virtualbox settings for the VM:

Audio Controller on Debian plain VM used is ICH AC97, while in kicksecure is Intel HD Audio, switching it to ICH AC97 will make it work properly.

Thank you for the hint :rose: .

1 Like
18

This seems like an important bug to fix. And not an easy bug to reproduce. But it is most likely unrelated to PipeWire and PulseAudio. Could be a bug in permission hardener (security-misc) or other system issue. Created `find: ‘/usr/lib/modules/6.1.0-25-amd64/kernel/drivers/xen’: Bad message` / `unable to truncate for updated status of 'security-misc': Read-only file system` for it.

19

The original poster said this bug only happens if using 5 GB of VM RAM.

But to confirm, clarify, you were able to reproduce this bug irrespective of VM RAM settings?

20

Same result, anything above 2GB RAM with Intel HD Audio will result into the same issue.

1 Like