Your message dated Fri, 18 Jul 2008 13:22:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#491270: pulseaudio: PulseAudio freezes the boot
process in some situations
has caused the Debian Bug report #491270,
regarding pulseaudio: PulseAudio freezes the boot process in some situations
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.)
--
491270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491270
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pulseaudio
Version: 0.9.10-2
Severity: critical
Justification: breaks the whole system
Hi,
in the following situation, pulseaudio freezes the boot process:
- pulseaudio system start enabled (in /etc/default/pulseaudio)
- some bad permissions in the /dev directory (due to bug #491114 in my case).
In my case, the error message was:
Jul 18 07:22:56 tatanka pulseaudio[2715]: main.c:
setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Jul 18 07:22:56 tatanka pulseaudio[2715]: main.c:
setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
In understand that the origin of the bug doesn't lie in pulseaudio, and that
is has been fixed already (see #491114). But, whatever causes pulseaudio to
fail its startup, I think it shouldn't freeze the whole boot process, but
rather die gracefully.
Kind regards,
Gabriel Kerneis
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-rc5-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages pulseaudio depends on:
ii adduser 3.108 add and remove users and groups
ii libasound2 1.0.16-2 ALSA library
ii libasyncns0 0.3-1 Asyncronous name service query lib
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst
ii libflac8 1.2.1-1.2 Free Lossless Audio Codec - runtim
ii libltdl3 1.5.26-4 A system independent dlopen wrappe
ii libogg0 1.1.3-4 Ogg Bitstream Library
ii liboil0.3 0.3.15-1 Library of Optimized Inner Loops
ii libpulsecore5 0.9.10-2 PulseAudio sound server core
ii libsamplerate0 0.1.4-1 audio rate conversion library
ii libsndfile1 1.0.17-4 Library for reading/writing audio
ii libwrap0 7.6.q-15 Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-15 Linux Standard Base 3.2 init scrip
Versions of packages pulseaudio recommends:
ii gstreamer0.10-pulseaudio 0.9.7-2 GStreamer plugin for PulseAudio
ii libasound2-plugins 1.0.16-1+b1 ALSA library additional plugins
ii padevchooser 0.9.3-2 PulseAudio Device Chooser
ii paprefs 0.9.6-2 PulseAudio Preferences
ii pulseaudio-esound-compat 0.9.10-2 PulseAudio ESD compatibility layer
ii pulseaudio-module-hal 0.9.10-2 HAL device detection module for Pu
ii pulseaudio-module-x11 0.9.10-2 X11 module for PulseAudio sound se
Versions of packages pulseaudio suggests:
ii paman 0.9.4-1 PulseAudio Manager
ii pavucontrol 0.9.6+svn20080426-1 PulseAudio Volume Control
ii pavumeter 0.9.3-1 PulseAudio Volume Meter
ii pulseaudio-utils 0.9.10-2 Command line tools for the PulseAu
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Jul 18, 2008 at 12:45:48PM +0200, Gabriel Kerneis wrote:
> Because everything under /dev was 660 instead of 666 (belonging to root).
> But you made me realize that it might as well have been the case that the
> devices did not even exist (#491114 messed up *many* things).
>
> I don't see why a device that do not exist at all should be treated
> differently from a device that you can't open because of bad permissions.
I have tested this here and verified that pulseaudio does *not* block if
the device does not exist *or* has incorrect permissions. In both cases
pulseaudio terminates with an appropriate error message. (ie. File not
found or Permission denied)
> Then again, I might be wrong on the real origin of the problem. If this the
> case, please forgive me and close this bug report. But seeing pulseaudio
> hanging on startup and blocking the whole system (for whatever reason) didn't
> seem the "right thing" to me — unless it times out and I wasn't patient
> enough.
I’m going to close this now, but if you find something that causes
pulseaudio to block on start-up, please let me know.
Thanks.
--
CJ van den Berg
mailto:[EMAIL PROTECTED]
xmpp:[EMAIL PROTECTED]
--- End Message ---
