Bug 1147674 - USB speakers not working after resume from suspend
Summary: USB speakers not working after resume from suspend
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-29 20:03 UTC by James
Modified: 2016-07-19 12:10 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:10:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
pulseaudio -vvvv output (260.72 KB, text/plain)
2014-10-05 19:44 UTC, James
no flags Details
pulseaudio -vvvv (261.65 KB, text/plain)
2014-10-17 12:33 UTC, Mark van Rossum
no flags Details
Output of pactl -list (22.71 KB, text/plain)
2014-10-17 12:33 UTC, Mark van Rossum
no flags Details
output of alsa-info (51.04 KB, text/plain)
2014-10-17 15:24 UTC, Mark van Rossum
no flags Details
alsa-info after resume (no sound from USB speakers) (31.20 KB, text/plain)
2014-10-17 19:31 UTC, James
no flags Details
alsa-info before suspend (with working sound) (31.03 KB, text/plain)
2014-10-17 19:32 UTC, James
no flags Details

Description James 2014-09-29 20:03:36 UTC
Description of problem:
I have sound output configured for my external USB speakers. Upon resume from suspend-to-RAM, they are present in Pulseaudio but there is no sound from them. To get them to work again I must replug them.

Version-Release number of selected component (if applicable):
kernel-3.16.3-302.fc21.x86_64
pulseaudio-5.0-10.fc21.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Plug in and switch to USB speakers.
2. Suspend.
3. Resume.

Actual results:
No sound.

Expected results:
Sound resumes.

Additional info:
The speakers are attached to an external hub on a USB3 port, but the same happens when they are directly-attached to a USB2 port.

The switch-on-connect plugin is loaded.

Reporting this against PA to start things off, I appreciate this could be a driver bug.

[ 2537.798411] usb 3-2.5.5: new full-speed USB device number 14 using xhci_hcd
[ 2537.887712] usb 3-2.5.5: New USB device found, idVendor=18c3, idProduct=6255
[ 2537.887722] usb 3-2.5.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2537.887727] usb 3-2.5.5: Product: USB Audio Device
[ 2537.887731] usb 3-2.5.5: Manufacturer: Elite Silicon
[ 2537.919512] input: Elite Silicon USB Audio Device as /devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb3/3-2/3-2.5/3-2.5.5/3-2.5.5:1.2/0003:18C3:6255.0008/input/input26
[ 2537.920157] hid-generic 0003:18C3:6255.0008: input,hidraw3: USB HID v1.00 Device [Elite Silicon USB Audio Device] on usb-0000:03:00.0-2.5.5/input2

Comment 1 James 2014-10-05 19:44:20 UTC
Created attachment 944082 [details]
pulseaudio -vvvv output

When this log was taken:
- PA was started with the USB speaker detached
- The speaker was attached
- The "test speaker" button in the GNOME volume control was check output
- Machine suspended and resumed
- "Test speaker" run again, no sound
- Speaker re-plugged and re-tested successfully.

Comment 2 Mark van Rossum 2014-10-17 12:32:40 UTC
See also bugs 1151424 and 1152321.

I have the same problem with ASUS Xonar U3 USB sound card.
The log shows (full log attached)

I: [pulseaudio] alsa-sink.c: Using 4.0 fragments of size 4408 bytes (24.99ms), buffer size is 17632 bytes (99.95ms)
D: [pulseaudio] alsa-sink.c: hwbuf_unused=0
D: [pulseaudio] alsa-sink.c: setting avail_min=1
W: [pulseaudio] alsa-util.c: Unable to set sw params: Permission denied
E: [pulseaudio] alsa-sink.c: Failed to set software parameters: Permission denied

Comment 3 Mark van Rossum 2014-10-17 12:33:10 UTC
Created attachment 947874 [details]
pulseaudio -vvvv

Comment 4 Mark van Rossum 2014-10-17 12:33:36 UTC
Created attachment 947875 [details]
Output of pactl -list

Comment 5 Mark van Rossum 2014-10-17 12:36:25 UTC
I should have mentioned that my problem remains after re-plugging. So might be different bug.

Comment 6 Rex Dieter 2014-10-17 13:14:53 UTC
This is often a kernel/alsa issue, reassigning.

Please post the output of 'alsa-info', thanks.

Comment 7 Mark van Rossum 2014-10-17 15:24:56 UTC
Created attachment 947934 [details]
output of alsa-info

Comment 8 James 2014-10-17 18:54:58 UTC
(In reply to Rex Dieter from comment #6)
> This is often a kernel/alsa issue, reassigning.
> 
> Please post the output of 'alsa-info', thanks.

Do you want this taken:

 - when the speakers are working, before suspend;
 - when they've gone quiet, after resume; or
 - both of the above?

Comment 9 Rex Dieter 2014-10-17 18:59:29 UTC
Good question, I assume it's probably better to have too much information than too little, so both?

Comment 10 James 2014-10-17 19:31:27 UTC
Created attachment 948006 [details]
alsa-info after resume (no sound from USB speakers)

Comment 11 James 2014-10-17 19:32:06 UTC
Created attachment 948007 [details]
alsa-info before suspend (with working sound)

Uploaded both as there's a small diff.

Comment 12 Mark van Rossum 2014-10-30 11:16:45 UTC
My problem is solved by doing 

chmod a+rw /dev/snd/*

after plugging in the USB device.

Comment 13 Fedora End Of Life 2015-11-04 14:58:13 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 James 2015-11-04 19:32:59 UTC
Still about in kernel-4.2.3-200.fc22.x86_64

Comment 15 Fedora End Of Life 2016-07-19 12:10:37 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.