gnome sometimes forgets default mixer tracks device

Bug #195939 reported by Graham C
12
Affects Status Importance Assigned to Milestone
Ubuntu
New
Wishlist
Unassigned

Bug Description

Binary package hint: gnome-control-center

In current Hardy (and also Gutsy), when I reboot Gnome often forgets which mixer device I've chosen as default. This results in my volume control hotkeys not working as expected (controlling the volume on the wrong device) until I launch gnome-sound-properties again to choose the right device.

I think this behaviour is related to which of my two sound cards is initialised first by ALSA, as this seems to change quite randomly. Gnome should still be able to control the correct mixer wherever it turns up though, and it certainly manages to always play through the same card.

Tags: gutsy hardy
Revision history for this message
Renaud Denis (renaud.denis) wrote :

Same issue for me

Revision history for this message
Philippe (philippepiatkiewitz) wrote :

Same issue here.

In the past (older Ubuntu versions) the issue could be solved by putting
  asoundconf set-default-card CK804
in the Session Preferences, but that only takes care of setting sound output to the correct card. The Mixer on my keyboard is randomly assigned to one of my two soundcards after a reboot. I need to go into System -> Preferences -> Sound to set the Default Mixer Tracks to the correct device.

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

Unfortunately PCI device enumeration seems tricky (i.e., nondeterministic) for audio devices, so the best we can rely on is using the PulseAudio suite. In this situation, you want to use pavucontrol. There's a bug in hardy's pulseaudio source package (but fixed in intrepid's) where the gconf module is loaded after restoring the devices and streams.

Daniel T Chen (crimsun)
Changed in linux:
assignee: nobody → ubuntu-audio
importance: Undecided → Wishlist
status: New → Confirmed
Changed in linux (Ubuntu):
assignee: Ubuntu Audio Team (ubuntu-audio) → nobody
penalvch (penalvch)
tags: added: gutsy hardy
affects: linux (Ubuntu) → ubuntu
Changed in ubuntu:
status: Confirmed → New
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Daniel and the others is this bug still valid in current Ubuntu versions (12.04 LTS and above)?

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.