Your message dated Tue, 25 Sep 2018 08:25:17 +0200
with message-id <20180925062517.ohhor7mk6sx2u...@toy.home.lxtec.de>
and subject line Re: [Pkg-alsa-devel] Bug#675857: pulseaudio creates
.config/pulse in a root directory
has caused the Debian Bug report #675857,
regarding /etc/init.d/alsa-utils creates /.config/pulse under sysvinit
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 ow...@bugs.debian.org
immediately.)
--
675857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.0.25-4
Severity: important
When pulseaudio is installed, which basically replaces alsa whith
itself for userspace, /etc/init.d/alsa-utils starts creating
.pulse files in system root directory during system startup/shutdown
(when the script is run):
$ ls -ld /.pulse*
drwx------ 2 root root 4096 May 25 07:54 /.pulse/
-rw------- 1 root root 256 Feb 15 20:10 /.pulse-cookie
This happens on all systems where alsa-utils and pulseaudio
is installed.
When the root filesystem is read-only, running /etc/init.d/alsa-utils
produces this:
# /etc/init.d/alsa-utils start
Setting up ALSA...Failed to create secure directory: Read-only file system
Failed to create secure directory: Read-only file system
Failed to create secure directory: Read-only file system
[message repeated 74 times total]
Failed to create secure directory: Read-only file system
done.
In all these cases, it tries to create /.pulse/ directory, and
before that, it tries to create /.pulse-cookie.
(this happens when $HOME is unset, if it is set and the script
run as root, it creates files in ~root obviously).
I'm filing this against alsa-utils instead of pulseaudio package
(but it might be pulseaudio bug after all), because the alsa-utils
initscript calls amixer and explicitly tells it to act on specified
_hardware_ devices, so that pulse should not be called, but yet it
is being called. If that's a function marked as a constructor in
libpulse, that should be libpulse bug.
At any rate it is definitely a bug, -- it should not mess with
the root directory like that.
Thanks,
/mjt
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 3.2.0-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages alsa-utils depends on:
ii dialog 1.1-20120215-2
ii kmod 9-3
ii libasound2 1.0.25-4
ii libc6 2.13-38
ii libncursesw5 5.9-10
ii libsamplerate0 0.1.8-5
ii libtinfo5 5.9-10
ii lsb-base 4.1+Debian8+deb7u1
ii whiptail 0.52.14-11.1
Versions of packages alsa-utils recommends:
ii alsa-base 1.0.25+3~deb7u1
ii pciutils 1:3.1.9-6
alsa-utils suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi gents,
* Niels Thykier <ni...@thykier.net> [2018-09-24 06:24 +0000]:
[...]
> Hi,
>
> I added a MR on salsa for this issue[1] fixing a missing call to
> alsactl. I could not see any (direct) calls to aumix, so these are not
> covered. There are some calls to amixer but it does not seem to create
> .config if missing despite looking for it.
>
> Admittedly, Daniel's solution of simply setting HOME is probably easier
> to maintain in the long run and less like to "miss" a call.
Just for the record: In stable we have 1.1.3-1 which doesn't fit to
this bug. Debian alsa pkg maintainers won't fix any older version
than that. So I close this bug hereby. BTW stable can run sysvinit
very well.
Elimar
--
Never make anything simple and efficient when a way
can be found to make it complex and wonderful ;-)
--- End Message ---
