Opened 2 years ago

Last modified 2 years ago

#17956 new bug

no audio after an update a while ago

Reported by: rodney Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Audio & Video Version: R1/beta3
Keywords: red x Cc:
Blocked By: Blocking:
Platform: All

Description

after an update, a red x appeared over the audio icon and no audio was heard from the computer any more. I tried another OS (linux) on the computer and it produced sound. So it is not a hardware issue.

Attachments (5)

screenshot1.png​ (41.4 KB ) - added by rodney 2 years ago.
neofetch data
screenshot2.png​ (58.5 KB ) - added by rodney 2 years ago.
about this system
screenshot3.png​ (96.0 KB ) - added by rodney 2 years ago.
audio icon
screenshot4.png​ (1.3 MB ) - added by rodney 2 years ago.
updated to nightly build, issue remains
syslog.txt​ (172.2 KB ) - added by rodney 2 years ago.

Download all attachments as: .zip

Change History (12)

by rodney, 2 years ago

Attachment: screenshot1.png​ added

neofetch data

by rodney, 2 years ago

Attachment: screenshot2.png​ added

about this system

by rodney, 2 years ago

Attachment: screenshot3.png​ added

audio icon

comment:1 by bipolar, 2 years ago

Can you attaching here a copy of /boot/system/var/log/syslog?

Have you tried a recent nightly image yet? The beta3 is rather old at this point.

Version 0, edited 2 years ago by bipolar (next)

comment:2 by rodney, 2 years ago

.

Last edited 2 years ago by rodney (previous) (diff)

comment:3 by rodney, 2 years ago

I have not been keeping up to date! Will look into nightly builds.

Last edited 2 years ago by rodney (previous) (diff)

by rodney, 2 years ago

Attachment: screenshot4.png​ added

updated to nightly build, issue remains

in reply to:  1 comment:4 by rodney, 2 years ago

I have updated to hrev56473 and the issue remains. The icon appears normal after a reboot and then when a audio file is played, the red "x" appears.

Replying to bipolar:

Can you attach here a copy of /boot/system/var/log/syslog?

Have you tried a recent nightly image yet? The beta3 is rather old at this point.

comment:5 by bipolar, 2 years ago

I think my broken "English" failed me. Next time you can just attach the syslog in the same way you did with the images (as to avoid the wall of text here :-).

Too bad it wasn't fixed on the nightlies already, but it is always worth a try.

In any case, with some luck, one of the developers (I'm just another user) might be able to spot the issue with your HDA, based on those syslog messages.

in reply to:  5 comment:6 by rodney, 2 years ago

No worries, I am new to bug reporting! Thanks for letting me know the proper conventions, I will fix it.

Replying to bipolar:

I think my broken "English" failed me. Next time you can just attach the syslog in the same way you did with the images (as to avoid the wall of text here :-).

Too bad it wasn't fixed on the nightlies already, but it is always worth a try.

In any case, with some luck, one of the developers (I'm just another user) might be able to spot the issue with your HDA, based on those syslog messages.

by rodney, 2 years ago

Attachment: syslog.txt​ added

comment:7 by waddlesplash, 2 years ago

Please determine what update caused the problem if you can, or see if a fresh install does not have the issue.

Note: See TracTickets for help on using tickets.