The stack of arrows on the right edge of your screenshot indicates more channels that are hidden. Can you expand your window to show the hidden channels to the right, then post another screenshot of all output channels.
Also in alsamixer If you hit F6 are other soundcards listed?
What is effect if you unmute the [S/PDIF] channel?
Another thing to think about is linux kernel version and support for your audio hardware. Can you tell us the make/model/spec of your computer?
If it is very old or very new machine the linux kernel version could be a factor.
yes, I did some changes including unmuting speaker channel, enabling auto-mute, changing s/pdif settings. nothings seems to work.
as of now I am keeping the sound settings window open and minimized. that stops the icon from flashing and also stops media from unpausing itself.
Also there is one thing I would like to share is that whenever I shut down my laptop, for a split second it shows a black screen with continuous string of ^@^@^@^@^@^@^@^@^@^@^@.....and I have reasons to believe that one "icon flash" is equal to one "^@". more flashes means the string is longer and when I use the system without the earphone, it gives no trouble and also no string at the time of shutdown. I have not yet confirmed that it is indeed the situation.
I am also attaching screen shots from other forums for your reference.
and yes, I did tried pulse audio volume control previously. I don't exactly remember if I was using manjaro or zorin 16 at that time, but it did not solve the issue. i would try once again in this OS as well.
Do you have any options in your BIOS for any kind of sound / headphone option pop-up when plugged in or HW actions when unplugged? That sounds kind of like HW actions are being performed when that device port has activity..
@pradyuman15 Windows 10+ will keep some devices active across reboots - ran into this with dual-booting 16.3 Core and Win11 myself. Just had to shutdown Win before booting Zorin and it was good to go. If I forgot, just had to reboot into Win, shutdown, then boot back into Zorin.
2nd time shuting down.
I didn't use my earphones so there was no issues and screen went straight to shutdown logo. there was no black screen.
3rd time I intentionally plugged the earphone untill the sign flashes 5 times.
here a screenshot of black screen after shutdown. exactly 5 times ^@ appeared in that string.
OK. So Zorin 17 Core only OS installed. Noted "Secure Boot" disabled confirmed.
As you didn't have these problems on older version Z16 and kernels, did you try my advice about booting an older kernel from grub screen on startup?
i.e. via grub "Additional Options for Zorin" menu item.
Did you check the SHA256 checksum of your ZorinOS 17 downloaded .iso file against the published value on Zorin website?
If you boot your ZorinOS installation USB and do "Try Zorin" do you have same sound problem etc?
I agree that this sounds like a kernel issue - where a driver includes a regression that has remained. On LiveUSB or at initial boot, you are on a generic driver, but once you upgrade and use the associated driver instead of the generic; the issue begins.
Have you tested using the kernel that is present on the initial install of Zorin OS 16?
Hello,
I don't remember what kernel it was on Zorin 16. if you could tell me then I would try booting zorin 17 using that kernel. But in zorin 16, software store didn't work at all, I had to use terminal to install and uninstall even the standard applications. I don't know if that related but That's my fear.
I had Z15.3 for extended time before I installed Z16.3, so I think the first kernel I had with Z16.3 was 5.15.0-56.
I have read somewhere that Z16 initially had a 5.11.#-## kernel, but I can't confirm that from my own experience.
to test it, you must reboot, then enter the Grub Menu (tap esc or tab at boot) and from Grub menu, select Advanced Options for Zorin > Zorin on 5.15.0-83 to boot from.
That is odd... What troubleshooting did you try to fix Gnome Software Store?
The files on your hard drive are likely corrupted. I recommend booting to LiveUSB and running boot repair, checking your drive with a S.M.A.R.T. test and possibly running fsck from LiveUSB (Never ever run fsck on a mounted file system).