Skip to main content ↑ ↓
Topic: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups (Read 4383 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups

Reply #15 –
 @linux4ever You need to seriously reflect upon what you are doing wrong. Save the alsa state AFTER you unmute the audio by doing

alsactl store

then reboot and see if:

alsactl restore

unmutes the audio. If it does, then add the line to rc.local.

Re: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups

Reply #16 –
Apparently, rc.local worked for them, but not alsa-utils-openrc. Not that it should matter, since installing and enabling the alsa service should ultimately do the same thing, and there aren't any obvious issues in the openrc script (despite it being significantly bigger than its matches in other inits).

The error being "sound server" related makes me think installing alsa-utils-openrc was just a coincidence and they somehow broke PulseAudio/Pipewire instead.

Quote from: ugluk – on
Surprisingly, setting SUID did work both on shutdown and reboot.

I took a look into it and found out halt is a C program (poweroff and reboot being links to it), and shutdown is a shell script that calls into it.

So setting SUID on reboot (and by proxy, on halt and poweroff) actually works, and as long as you don't use any features that rely on the shutdown script itself being root (like delayed shutdown, forcing fsck, etc.), the fact that SUID doesn't apply to scripts is irrelevant (I guess you can remove SUID from shutdown, and it won't make a difference).

Quote from: gripped – on
Surely it's better to run the server services you chose when you chose rather than when something wants to connect to you ?

Well, there's faster boot times, lower idle RAM usage, and it takes off the burden of having to choose when to start in the first place.

Also, AFAIK, inetd got abandoned because systemd ate it; most services on systemd distros use "socket activation" (systemd's rebrand of inetd's features), to the point (for example) Arch patches GPG to keep it despite the feature having been deprecated and explicitly not supported upstream.

I'm mostly playing devil's advocate here, because you can save RAM with none of the reliability trade-offs by just using swap space, and inetd services often lead to increased startup time and RAM usage per instance if they're not refactored in ways that make then more awkward to use (like how most programs made for ucspi-tcp use a binary config file so that each instance doesn't spend time and RAM analyzing a text config).

Re: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups

Reply #17 –
Quote from: gripped – on
I stand corrected. I still think it's a dubious idea though.

It was asked about the implementation and not whether it makes sense to use inetd, so I can't really understand your excitement.


"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups

Reply #19 –
Damn, I've been struggling for a couple of days already with pulseaudio on a fresh installation. It mutes on every damn reboot. Finally found out that I needed alsa-utils-runit package. Thanks, guys.
 

Re: [SOLVED] Artix/runit: muted sound, shutdown/reboot, cups

Reply #20 –
@ugluk thanks, your solution worked perfectly for mute audio on every reboot. Can you also help with bluetooth turned on,num lock off and brightness at lowest on booting? I am using cinnamon with dinit.
Edit- I could not figure how to remember state of these things on each startup, but installing tcl,numlockx and brightnessctl, then adding their commands in rc.local worked for me. Thanks @ugluk for the idea though.