PipeWire integration discussion?

[dolphin_oracle]

new package's scripts and setup are working for me in xfce, fluxbox, and KDE, sysVinit & systemd, although the kde on the systemd side is a bit of a hack.

here's the change made to the fluxbox/startup file for launching pipewire.

Code: Select all

#start pulseaudio before volumeicon so unmute works
#start-pulseaudio-x11 &
#launch pipewire
pipewire-start
sleep 
volumeicon -c volumeicon-fluxbox & 

and the pactl info

Code: Select all

dolphin@mxflux:~
$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 35
Is Local: yes
Client Index: 94
Tile Size: 65472
User Name: dolphin
Host Name: mxflux
Server Name: PulseAudio (on PipeWire 0.3.58)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
Default Source: alsa_input.pci-0000_00_1b.0.analog-stereo
Cookie: 565e:a25c

[AVLinux]

Woohoo, EFL volume control works. Now i can adjust volume from the keyboard.

Onwards and upward.

(systemd)

Just a quick note to you and anyone else testing/trying the Enlightenment stuff, it is recommended to boot with systemd, in fact if you talk to the E developer on IRC about running Enlightenment with sysvinit you will get laughed at...
In my PipeWire testing here I'm with you, everything is working perfectly with systemd boot however sysvinit isn't but I'm not going to waste anyone's time with that for a small edge-case of a D.E that MX doesn't support. PulseAudio works as expected on the Live system and anyone installing the Enlightenment ISO build will be recommended to boot systemd which will now get PipeWire engaged without any need for setting by the User...

Next on the testing block is a fresh AV Linux MX Edition install which being XFCE4 based I'm not expecting any issues...

Anyway enough rambling about that...@dolphin_oracle a heartfelt THANK-YOU! for your work on this and for being open to some small changes, this is why I LOVE MX Linux!!

[dolphin_oracle]

Woohoo, EFL volume control works. Now i can adjust volume from the keyboard.

Onwards and upward.

(systemd)

Just a quick note to you and anyone else testing/trying the Enlightenment stuff, it is recommended to boot with systemd, in fact if you talk to the E developer on IRC about running Enlightenment with sysvinit you will get laughed at...
In my PipeWire testing here I'm with you, everything is working perfectly with systemd boot however sysvinit isn't but I'm not going to waste anyone's time with that for a small edge-case of a D.E that MX doesn't support. PulseAudio works as expected on the Live system and anyone installing the Enlightenment ISO build will be recommended to boot systemd which will now get PipeWire engaged without any need for setting by the User...

Next on the testing block is a fresh AV Linux MX Edition install which being XFCE4 based I'm not expecting any issues...

Anyway enough rambling about that...@dolphin_oracle a heartfelt THANK-YOU! for your work on this and for being open to some small changes, this is why I LOVE MX Linux!!

your enlightenment spin does not set a XDG_RUNTIME_DIR environment variable. for the default 1000 user, it would be /run/user/1000, which does exist but there is no environment variable set.

Code: Select all

export XDG_RUNTIME_DIR=/run/user/1000

then then pipewire will start up fine. the info is buried in the pipewire error messages...

[anticapitalista]

Ok thanks.


The autostart entry doesn’t seem to work on kde. Got to figure that out

Actually, I've been having some issues getting sysvinit working as well, I haven't troubled you about it yet because I haven't tested it on a pure MX install yet and so far testing has been in an Enlightenment VM. What's interesting is that PipeWire systemd is working perfectly there so perhaps the sysvinit issue is not D.E. related, just mentioning it now since the other post has come to light. Maybe what you come up with will work on all D.E's. Happy to test! What is @anticapitalista doing on the antiX side with PipeWire without systemd?

For bullseye, nothing.
We have systemd/elogind-free debs for Debian testing/sid, but they are not fully tested.

[AVLinux]

your enlightenment spin does not set a XDG_RUNTIME_DIR environment variable. for the default 1000 user, it would be /run/user/1000, which does exist but there is no environment variable set.

Code: Select all

export XDG_RUNTIME_DIR=/run/user/1000

then then pipewire will start up fine. the info is buried in the pipewire error messages...

Now you're my hero!

Thanks so much for even thinking about looking into that! If I wanted to make that a global variable where would that normally get set? /etc/profile? Enlightenment is a weird beast and cherry picks XDG stuff it does and doesn't do...

@anticapitalista

Ahhh OK, got it! I had forgotten you aren't really looking to do this on Bullseye for antiX. Thanks for the reply!

[dolphin_oracle]

@AVLinux its being set on first login, but not if you login/logout. I'm not sure why its not being set.

that said on first login I still cant' get the pipewire to start at login, so the environment variable is part of hte story but not all of it.

**possibly rest of story...I think autostart entries under /etc/xdg/autostart, depsite being listed in the settings->applications->startup applications aren't actually starting. if I copy the /etc/xdg/autostart/pipewire-pulse.desktop to ~/.e/e/config/startup/ then pipewire appears to startup up, at least on first boot.

however on logout/login this is not processed because the XDG_RUNTIME_DIR is not present. i think there is something wrong with the slim configuration or possibly the logout from e. that variable not being present could affect more than just pipewire, its used by other things.

**I think that when I logout of e, slim fails to start and X restarts, and you lose your dbus session, which causes all sort of problems. that might just be on my virtualbox system, but I havent changed anything from the defaults. but pipewire does work on first login now if the autostart desktop file is in ~/.e/e/config/startup/

[AVLinux]

@AVLinux its being set on first login, but not if you login/logout. I'm not sure why its not being set.

that said on first login I still cant' get the pipewire to start at login, so the environment variable is part of hte story but not all of it.

**possibly rest of story...I think autostart entries under /etc/xdg/autostart, depsite being listed in the settings->applications->startup applications aren't actually starting. if I copy the /etc/xdg/autostart/pipewire-pulse.desktop to ~/.e/e/config/startup/ then pipewire appears to startup up, at least on first boot.

however on logout/login this is not processed because the XDG_RUNTIME_DIR is not present. i think there is something wrong with the slim configuration or possibly the logout from e. that variable not being present could affect more than just pipewire, its used by other things.

**I think that when I logout of e, slim fails to start and X restarts, and you lose your dbus session, which causes all sort of problems. that might just be on my virtualbox system, but I havent changed anything from the defaults. but pipewire does work on first login now if the autostart desktop file is in ~/.e/e/config/startup/

Thanks, great info and very much appreciated, I will test further tonight or tomorrow (I have a family thing today).

In fairness (or criticism) to SLiM, in my experience even with XFCE4 it goes off the rails on logout and logging back in on a session, in XFCE4 you lose shutdown permissions (and probably more) if you log out and log back in. Googling 'slim shutdown permissions' will bring up lots of hits...

Why do I use it...? It's so simple and very easy to theme and self-contained and 99% of AV Linux Users run single-user system and either login once or use autologin so that has masked some of these potential problems but a good point is raised that perhaps an Enlightenment spin designed to introduce more people to Enlightenment DE shouldn't have such a cranky Login Manager, I will do some more testing with lightDM..

Lastly regarding XDG, I believe Enlightenment does probably ignore /etc/xdg/autostart... It has it's own mechanisms for Policykit, Bluetooth, Connman, Packagekit and for startup (as you've done manually now)

For the record the wrench icon on the Enlightenment Panel will take you to the Enlightenment Settings and everything in E-world is configured from there

shot-2022-10-23_09-53-02.jpg

I will come back later with more findings, thanks so much for the help!

[dolphin_oracle]

Ok then its slim and not E, because the symptoms are the same.

[oops]

... I hope than pipewire-setup-mx will be avalaible for MX19 too ?

[dolphin_oracle]

... I hope than pipewire-setup-mx will be avalaible for MX19 too ?

not likely. right now the required pipewire packages are not backported to mx19 or to debain 10 buster.