Pulseaudio doesn't start, impossible to adjust sound volume

Bug #557795 reported by dreadyman
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: pulseaudio

I've just re-installed ubuntu 10.04 beta and update this fresh new install because of this bug.

The problem : I could not adjust sound volume from keyboard, the sound applet in gnome panel was absent, opening "volume control" in preferences was blocking at "waiting for sound server...". I had sound but i could not adjust it from globally. I could adjust volume separately from each application.

The error :
$ pulseaudio
E: module-stream-restore.c: Failed to parse module arguments
E: module.c: Failed to load module "module-stream-restore" (argument: "restore_device=false restore_device=false"): initialization failed.
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.

The solution : i renamed my ~/.pulse to ~/.pulse_ to force pulseaudio to create a new .pulse directory.

The new output :
$ pulseaudio
E: pid.c: Daemon already running.
E: main.c: pa_pid_file_create() failed.

Now it works, when i press volume down/up onto my keyboard, i see the notification for volume changed (with libnotify) that was not showing before renaming the .pulse directory

So this was a configuration problem, but i did not edit any file in ~/.pulse directory.

Joined the whole ~/.pulse directory which caused the problem with pulseaudio.

I hope you will considerate this as a bug because i'have just spend much time to resolve this very annoying problem.

Other infos :

Description: Ubuntu lucid (development branch)
Release: 10.04

$ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  Candidate: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  Version table:
 *** 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Anthony

Revision history for this message
dreadyman (dreadyman16) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :

This is very likely caused by the same issue as in bug 557421

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.