Feature #6873

No sound because of multiple sound card

Added by sajolida 2014-03-07 11:08:54 . Updated 2018-02-08 07:58:31 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2014-03-07
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

We receive quite often user question about having no sound when they have multiple sound cards and the wrong one is selected by default.

If would be great to document how to solve that in the FAQ.

Users facing this error should help us understand how to change the configuration of multiple sound cards to activate the one of their choice. That might be possible to do from System → Preferences → Sound.

Subtasks

Related issues

Related to Tails - Bug #7245: Find out the best way to select the default sound card Confirmed
Related to Tails - Bug #7246: Persistence preset: default sound card Confirmed 2014-05-14

History

#1 Updated by sajolida 2014-04-14 14:03:27

  • Subject changed from FAQ: No sound because of multiple sound card to No sound because of multiple sound card
  • Category set to 208

#2 Updated by sajolida 2014-04-29 17:51:00

  • Description updated

#3 Updated by intrigeri 2014-04-29 18:56:32

Worst case, ~/.asoundrc (or similar, I don’t remember exactly) can
select the preferred output device, and can be made persistent with
the Dotfiles feature.

#4 Updated by sajolida 2014-06-22 09:02:34

  • related to Bug #7245: Find out the best way to select the default sound card added

#5 Updated by sajolida 2014-06-22 09:02:43

  • related to Bug #7246: Persistence preset: default sound card added

#6 Updated by BitingBird 2015-01-07 16:58:30

  • Category set to Hardware support

#7 Updated by intrigeri 2015-01-10 09:48:23

  • Affected tool deleted (FAQ)

#8 Updated by BitingBird 2015-07-24 04:00:42

  • Type of work changed from End-user documentation to Test

This should be tested in Tails Jessie

#9 Updated by BitingBird 2015-07-24 04:01:19

  • Target version set to Tails_2.0

#10 Updated by intrigeri 2015-08-03 05:18:02

  • Target version deleted (Tails_2.0)

(The need to test on Tails/Jessie does not automatically turn a ticket into a Tails 2.0 release blocker.)

It also could be tested in Tails/Wheezy, I’ve seen no report about it, after hints were provided in the ticket description.

#11 Updated by Anonymous 2018-01-19 14:36:06

@help desk: is this still a question often raised by users?

#12 Updated by Anonymous 2018-01-19 14:45:00

  • Assignee set to sajolida
  • QA Check set to Info Needed
  • Type of work changed from Test to End-user documentation

This is undocumented in the known issues. Let’s add the workaround there?

#13 Updated by Anonymous 2018-01-19 14:46:05

emmapeel tells me this was in the known issues page before and is not there anymore. If this is correct, then we can assume it got solved and we can instead reject this ticket.

#14 Updated by sajolida 2018-02-08 07:58:31

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

I cannot see any previous entry related to that in the Git history of support/known_issues. So I don’t think it was documented previously.

This issue dates back from Wheezy, so let’s close it for now and reopen it only if new bug reports come in.