Opened 4 years ago

Closed 17 months ago

#15742 closed bug (fixed)

Media Services jams up if accessed too soon after booting up

Reported by: dsuden Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc: ttcoder
Blocked By: Blocking:
Platform: All

Description

On computers we've tried here (AMD based), we have trouble if we try to play music too soon after first booting up. Normally what happens is that audio doesn't come out of the output jack (HDA output 0). Once the problem has occurred, we usually have to reboot the computer to solve it. If we wait at least 30 seconds after booting, before playing the first audio, everything goes well from then on. Currently testing here using MSI AMD FM2+ A68H motherboard and AMD AD740KYBJABOX A6-7400 processor.

Change History (5)

comment:1 by ttcoder, 4 years ago

Cc: ttcoder added

comment:2 by mmlr, 4 years ago

Please test if the workaround is still needed after hrev54464.

Also is a reboot strictly necessary or does restarting media services also resolve the issue?

comment:3 by ttcoder, 4 years ago

Discussing with Dane, I think he'll probably wait until there's a fix for the app_server crash, and upgrade only then and test both app_server stability and this ticket (delay in HDA audio availability after boot). Thanks for all you do!

in reply to:  2 comment:4 by ttcoder, 4 years ago

Replying to mmlr:

Also is a reboot strictly necessary or does restarting media services also resolve the issue?

FWIW, the delay-after-boot (as in #16222) is also reliably reproducible currently on my T410, booting to beta2. So I just tested as you ask : if I restart media services, then wait a few seconds, sound is available immediately then. So it's a good work-around for lack of audio in this case. Though the "speaker" icon in deskbar no longer allows setting volume with the wheel, but that's probably a completely unrelated problem.

BTW I'm surprised the owners of other tickets didn't come back with results.. Maybe it's a case of "no news good news" ? :-)

comment:5 by waddlesplash, 17 months ago

Resolution: fixed
Status: newclosed

By all other accounts this problem was indeed fixed by those changes. If it wasn't or some other problem still clearly persists a new ticket should probably be opened.

Note: See TracTickets for help on using tickets.