Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#71971 - pipewire 1:0.3.34-1 error saving pavucontrol config file

Attached to Project: Arch Linux
Opened by Bruno (pazitos10) - Tuesday, 31 August 2021, 23:02 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 13 November 2021, 14:41 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Replaced pulseaudio with pipewire. To do so, I installed the following packages:

* pipewire
* pipewire-alsa
* pipewire-media-session
* pipewire-pulse

And obviously deleted pulseaudio and everything worked out of the box, no problem at all until today.


This morning I updated those packages from version 1:0.3.31-1 to 1:0.3.34-1 but when I was trying to mute my mic and close pavucontrol, an error message appeared saying "Error writing config file %s/home/[user]/.config/pavucontrol.ini: Bad state" so my settings didn't save.

Additional info:
* package version(s): 1:0.3.34-1
* config and/or log files etc.: nothing related to pipewire on journalctl, unfortunately. I attached the config file with the "problem", which my user can read/write (has permissions).

Steps to reproduce:
1. Update packages to version 1:0.3.34-1
2. Update sound related settings with pavucontrol.
3. Close pavucontrol.
4. An error pops up with the following message: "Error writing config file %s/home/[user]/.config/pavucontrol.ini: Bad state"

Could't solve it on my own, tried to google the error message but nothing really was related to pavucontrol and pipewire. For now I downgraded those packages to the previous version and now it's working again.



This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Saturday, 13 November 2021, 14:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  pipewire 1:0.3.40-1
Comment by Bruno (pazitos10) - Saturday, 13 November 2021, 14:35 GMT
I can confirm the bug is not present in pipewire 1:0.3.40-1.

Loading...