Zorin 17.3 does not detect audio card on HP x360 Spectre

[Gorm]

Hmm, the Audio usergroup? I tried, see screenshot. Correct approach?

Also, I've tested the alsa_reload.sh executable file, it works!

But, I'm prompted for the password when it runs, hence my thoughts of adding the pw in the script somewhere?

[swarfendor437]

No I meant this:

sudo usermod -aG audio your_username

[Gorm]

I did that in a terminal window first. Do I have to add that command to the alsa_ reload.sh file too?

[swarfendor437]

No, you just have to be a member of that group.

[Gorm]

So the audio group is listed among other groups. Can I assume that any group that's listed, is a group my user "dag" is a member of?

Currently my alsa_reload.sh file looks like this:

and my Startup Applications Preferences:

I think I must be very close to make this work, what am I missing?

[swarfendor437]

You don't need audio group in startup, the command just makes your user a part of the audio group with privileges that belong to that group.

[Gorm]

Meaning that once I have ran the command "
sudo usermod -aG audio dag", the user keeps its membership, even at reboots? OK, copy that.

The script alsa_reload.sh works when I run it manually, but will still not load automatically at startup.

I found a theory that commands often need the desktop to be fully loaded. If they are ran using Startup Applications they often run too soon and break.

Hence, there's a need for a little time break before the actual command runs. So I took the advice to introduce the following command to Startup Applications:
/bin/bash -c "sleep 15 && alsa_reload.sh /home/dag/alsa_reload.sh"

I assume that sleep 15 means that there is a delay of 15 seconds before alsa_reload.sh is started, right?
Anyhow, 15 seconds after the desktop was fully loaded, nothing happened. Still no script launched.
Have I perhaps made an error in the adaption to my user?

The original command looks like this:
/bin/bash -c "sleep 15 && xmodmap /home/seph/Code/Ubuntu\ Scripts/Xmodmap"

[swarfendor437]

If I'm honest I am fairly new to this concept myself. I have been having issues in other OS's regarding virt-manager not launching because network hardware not 'sticking'. The advice being to create a .bashrc file.

So wondering if the script needs to be there.