[SOLVED] No audio on Excalibur through pipewire on KDE wayland

zapper · Today 02:20:28

@golinux two things... should I watch this conversation with popcorn?

And also, if you think my nonsense was painfully stupid, look up qanon and pizzagate.

golinux · Today 02:21:26

We have a weekly jitsi meet and you are welcome to join us. Also feel free to talk to us on our IRC channels where the devs hang out. The forum is more for user assistance than development issues.

golinux · Today 02:22:28

zapper . . . do you ever have anything useful to say?

zapper · Today 02:26:15

@golinux Not sure, just that this whole thread has been derailed pretty well.

I am almost jealous I didn't derail it this bad

I am not a programmer either btw. I know as much on how to code as you do. just my two cents.

steve_v · Today 02:44:50

So, IOW "There is no formal procedure to become a Devuan contributor."

Why do I even bother. Guess I'll go see if #devuan-dev is still a whole bunch of resounding silence.

zapper . . . do you ever have anything useful to say?

Good to know I'm not the only one who has noticed.

derailed

The answer(s) to the original question and comments on the situation in general have been covered ad-nauseam in another thread, what else is there to do?

Last edited by steve_v (Today 02:50:38)

golinux · Today 04:09:41

So, IOW "There is no formal procedure to become a Devuan contributor."

Perhaps that task has been waiting for YOU to suggest it, set it up and keep track of all its moving parts.

Also, be aware that there are several irc channels that deal with different aspects of devuan's development.

steve_v · Today 05:13:20

Perhaps that task has been waiting for YOU to suggest it, set it up and keep track of all its moving parts.

Keep repeating the same bullshit Go, maybe it will come true. Or just go back to your CSS and conferences.
The dev channel is utterly dead, forum questions get canned responses, nothing ever changes. I'm done here.
This right here is why you have no new devs. If you can't figure that out, you have my sympathy... But not my motivation or any of my time. I'll spend those on a distro where somebody gives a fuck.

different aspects of devuan's development

How many aspects can *crickets* and that one dude giving up because *crickets* have?

Last edited by steve_v (Today 05:23:31)

radiatedradio · Today 15:01:01

I wrote the openRC init script, if you want to use it, replace "radio" with your own username, or if anyone works on maintaining stuff can figure out some solution to automatically fill in the user field, or maybe if I have some free time outside work, I'll make some kind of script that gets your users name and replaces it.

@steve_v

Indeed. While it is likely a dead horse, I'll flog it some more here: Devuan, as a supposed leader in systemd-free distros... Does precious little leading.
Where real work is needed to get things working without systemd, solutions are lifted from Gentoo (eudev, elogind, opentmpfiles etc.). Everything else is just banning packages rather than fixing them, or shipping broken setups like we see here with wayland and pipewire.
I have asked repeatedly what Devuan's direction and preferred solution for user-units is, and all I get is a bunch of "nothing, wait for Debian to fix it" wilful inaction.

I've been on and off using devuan for ~3 years. My original post came off as uneducated, but that's because I never even used pipewire before, or wayland too much. If possible at least some kind of warning when installing any wayland/pipewire based desktop should come up, that you might run into issues, or that you should check the forum.

heres the init script, don't just copy it in, change the user name. It works fine for me with KDE, probably would work with any other desktop. It's quite makeshift, I've written very few init scripts before, but it gets the job done. The killing processes part could be removed, I just went off of the one I found here.

#!/sbin/openrc-run

name="pipewire"
description="pipewire"
command_user="radio"

depend() {
    after bootmisc
}

start() {
    ebegin "Starting Pipewire"
    
# kill 
    pkill -u "radio" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
    pkill -u "radio" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
    pkill -u "radio" -fx /usr/bin/pipewire 1>/dev/null 2>&1
    
    # start 
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/pipewire.pid \
        --user radio --exec /usr/bin/pipewire
    
    # wait
    local timeout=10
    while [ $timeout -gt 0 ] && [ "$(pgrep -u radio -f /usr/bin/pipewire)" = "" ]; do
        sleep 1
        timeout=$((timeout - 1))
    done
    
    if [ "$(pgrep -u radio -f /usr/bin/pipewire)" = "" ]; then
        eend 1 "no workie"
        return 1
    fi
    
    # wireplumber
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/wireplumber.pid \
        --user radio --exec /usr/bin/wireplumber
    
    # pulse
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/pipewire-pulse.pid \
        --user radio --exec /usr/bin/pipewire-pulse
    
    eend 0
}

stop() {
    ebegin "Stopping Pipewire"
    
    start-stop-daemon --stop --pidfile /var/run/pipewire-pulse.pid
    start-stop-daemon --stop --pidfile /var/run/wireplumber.pid
    start-stop-daemon --stop --pidfile /var/run/pipewire.pid
    
    pkill -u "radio" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
    pkill -u "radio" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
    pkill -u "radio" -fx /usr/bin/pipewire 1>/dev/null 2>&1
    
    rm -f /var/run/pipewire.pid /var/run/wireplumber.pid /var/run/pipewire-pulse.pid
    
    eend 0
}

restart() {
    stop
    sleep 1
    start
}

Last edited by radiatedradio (Today 15:03:39)

radiatedradio · Today 15:10:59

Also it's amazing how fast this thread turned into not a discussion about pipewire and things like that, just bickering between forum members, never expected this when I just wanted to ask a question on here.

radiatedradio · Today 16:42:01

I wrote an autoinstall script for it, because I got bored. Run as the user you're starting your desktop with, supports both doas and sudo for priv escalation. It's extremely janky, but it works:

if command -v sudo &> /dev/null; then
    export SUDO_OR_DOAS="sudo"
elif command -v doas &> /dev/null; then
    export SUDO_OR_DOAS="doas"
fi

mkdir ~/pipewire
cd ~/pipewire

tee ~/pipewire/pipewire << 'EOF'
#!/sbin/openrc-run

name="pipewire"
description="pipewire"
command_user="USER"

depend() {
    after bootmisc
}

start() {
    ebegin "Starting Pipewire"
    
    # start 
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/pipewire.pid \
        --user USER --exec /usr/bin/pipewire
    
    # wait
    local timeout=10
    while [ $timeout -gt 0 ] && [ "$(pgrep -u USER -f /usr/bin/pipewire)" = "" ]; do
        sleep 1
        timeout=$((timeout - 1))
    done
    
    if [ "$(pgrep -u USER -f /usr/bin/pipewire)" = "" ]; then
        eend 1 "no workie"
        return 1
    fi
    
    # wireplumber
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/wireplumber.pid \
        --user USER --exec /usr/bin/wireplumber
    
    # pulse
    start-stop-daemon --start --background --make-pidfile --pidfile /var/run/pipewire-pulse.pid \
        --user USER --exec /usr/bin/pipewire-pulse
    
    eend 0
}

stop() {
    ebegin "Stopping Pipewire"
    
    start-stop-daemon --stop --pidfile /var/run/pipewire-pulse.pid
    start-stop-daemon --stop --pidfile /var/run/wireplumber.pid
    start-stop-daemon --stop --pidfile /var/run/pipewire.pid
    
    pkill -u "USER" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
    pkill -u "USER" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
    pkill -u "USER" -fx /usr/bin/pipewire 1>/dev/null 2>&1
    
    rm -f /var/run/pipewire.pid /var/run/wireplumber.pid /var/run/pipewire-pulse.pid
    
    eend 0
}

restart() {
    stop
    sleep 1
    start
}
EOF
\
sed -i "s/USER/$USER/g" ~/pipewire/pipewire &&
$SUDO_OR_DOAS mv ~/pipewire/pipewire /etc/init.d/pipewire &&
$SUDO_OR_DOAS chown root:root /etc/init.d/pipewire &&
$SUDO_OR_DOAS chmod 755 /etc/init.d/pipewire &&
$SUDO_OR_DOAS rc-update add pipewire &&
$SUDO_OR_DOAS rc-service pipewire start

rbit · Today 19:19:05

I wrote the openRC init script, if you want to use it, replace "radio" with your own username, or if anyone works on maintaining stuff can figure out some solution to automatically fill in the user field, or maybe if I have some free time outside work, I'll make some kind of script that gets your users name and replaces it.

There are a few ways to do this. Replace command_user="radio" with command_user="$USER" is one way (probably the way that makes the most sense). Another option is command_user="$(whoami)". If you want a non-sensical solution, use command_user="$(env | grep ^USER= | cut -c 6-)" (but that is a very strange way to get the USER).

The officially official Devuan Forum!

#26 Today 02:20:28

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#27 Today 02:21:26

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#28 Today 02:22:28

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#29 Today 02:26:15

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#30 Today 02:44:50

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#31 Today 04:09:41

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#32 Today 05:13:20

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#33 Today 15:01:01

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#34 Today 15:10:59

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#35 Today 16:42:01

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

#36 Today 19:19:05

Re: [SOLVED] No audio on Excalibur through pipewire on KDE wayland

Board footer