- This topic has 132 replies, 11 voices, and was last updated Mar 7-12:58 am by stevesr0.
-
Posts
-
Brian Masinick
Congratulations on your success and thanks for sharing your success and the solution.
--
Brian Masinickstevesr0
Hi Brian The Mas,
Thanks.
Just going to keep testing this to see what works and what doesn’t. mpv and the Firefox browser play music where I want it (headphones or internal speakers), but alsaplayer didn’t (might be a simple problem with alsaplayer, since I haven’t hardly used it.)
Yesterday, after playing music for a long time, the browser started freezing. Worked on restart, but then froze again (IIRC). Doesn’t seem to be associated with heavy cpu or memory use. I will watch this and see if it is consistent.
Today no problem (but haven’t started playing music.)
My system has a total of 1024 installed packages. Not sure how that compares to others seeking “minimal” installs or “regular” installs (full or Sid or…). Should be feasible for me to provide a list of what I have for anyone else trying to make Pipewire work.
stevesr0
Update – no change – Pipewire still working without systemd, as far as I can tell.
Attaching a text file with my 1304 installed packages. If anyone is interested in seeing what might be necessary or unnecessary to make Pipewire run. This might enable some folks struggling to run Pipewire to identify what packages they might lack (if that is a common reason for failure).
Interested in any comments. If others are running Pipewire on antiX, I would like to hear from them.
stevesr0
olsztyn
Attaching a text file with my 1304 installed packages. If anyone is interested in seeing what might be necessary or unnecessary to make Pipewire run. This might enable some folks struggling to run Pipewire to identify what packages they might lack (if that is a common reason for failure).
From the attached list it appears to me that libelogind0 is no longer installed. It is no longer required to pipewire per your previous post I suppose.
However as I understand the script you posted recently must be run before installation of pipewire?Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHi olsztyn,
Thanks for reply and for searching my packages <g>.
No, the pipewire packages were already installed. (The latest nosystemd versions only!)
(Before installing the script, pipewire only worked with libelogind0 installed.)
Now, WITHOUT libelogind0 installed, I just run the script before starting Xorg with startx.
Pipewire, wireplumber and pavucontrol are all working automagically.
I don’t have to run the EXPORT part.
stevesr0
P.S.
My next step is to get a liveusb of this current install (without libelogind0) and see if Pipewire works smoothly on my other two computers.
Hi all,
I reinstalled the (so far) latest SID nosystemd VLC packages (3.0.18-1.0nosystemd1) on my working Pipewire nosystemd install. Required installing the specific version of vlc, vlc-bin, libvlc-bin, libvlc5, libvlccore9, vlc-plugin-base, vlc-plugin-qt, vlc-plugin-video-output and vlc-data. When I installed vlc-plugin-base, libprotobuf-lite32 also had to be installed.
It works (even after a reboot <g>).
As I wrote before, my next step will be to make a liveusb from an iso-snapshot of this install to try on my other systems.
In another thread (“vlc can’t be installed on antix-22”), I posted the standard way to install specific versions of packages.
stevesr0
- This reply was modified 4 months, 2 weeks ago by stevesr0.
Brian Masinick
Looks like you have been making good progress on this effort.
Thanks for sharing as you continue to test and learn how the software works and what is still needed; this is important and very helpful.
--
Brian MasinickHi The Mas,
thank you.
In case anyone is interested, my routine for avoiding systemd additions with upgrades is as follows:
1. Run sudo apt update && sudo apt full-upgrade
2. Say “no” when asked if you want to proceed with the upgrade.
3. Launch aptitude and examine each candidate upgrade package.
4. Make a list of all packages that change from a nosystemd version to a regular debian one.
5. Hold all the packages on the list using
sudo apt-mark hold <package name>6. Rerun #1.
7. If not comfortable, recheck any suspicious package.
8. When comfortable, rerun #1 and “yes”.
9. run the initiation script and then startx and check that Pipewire still works.
N.B. when a package upgrade to a nosystemd version appears, I unhold the package before upgrading by running
sudo apt-mark unhold <package name>Might seem tedious, but I only do this for the Sid machine and it usually involves only one cycle.
Of course if someone has a better way to do this, I would appreciate learning it.
stevesr0
- This reply was modified 4 months, 2 weeks ago by stevesr0.
- This reply was modified 4 months, 2 weeks ago by stevesr0.
Might seem tedious, but I only do this for the Sid machine and it usually involves only one cycle.
I am not proposing any better way to avoid introduction of systemd versions of packages here but I just want to mention I am using an easy manual method:
List in Synaptic upgradeable packages and:
– If a package upgrade is from ‘nosystemd’ or ‘antix’ specific to a ‘regular’ Debian then do not mark for upgrade
– The remaining ones mark for upgrade if they do not cause any other damage, such as removal of Runit modules (lsbase does this) or introduction of libelogind0.This seems a rather manual way but I found that this is rather quick in practice as I am keeping my SID antiX upgraded frequently. For example yesterday’s upgrade showed just about 40 packages I did not mark for upgrade and this included also those with Beta level modifications of the same version of the package.
I am running (typing this post from such one) antiX 22 Full version of SID Runit. For antiX Base SID it would be probably even fewer than 40 packages not eligible for upgrade. If you want to to allow upgrade packages of the same versions to include Beta modifications, then it seems about just 20 not eligible for upgrade.
This method I am using is manual but I found it quick and easy, particularly that I quickly became familiar with which packages would case damage…
I keep my antiX SID Full upgraded to the max and I found it equally stable and reliable as the ‘old production’ at this point with the above precautions. I do not have pipewire implemented yet though…Having said this, your method is more systematic, while mine is quite manual.
- This reply was modified 4 months, 2 weeks ago by olsztyn.
- This reply was modified 4 months, 2 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHi olsztyn,
Thanks for information on your approach.
I think mine is quite manual!
I think of my setup as a minimalistic one, but I don’t know how it compares in number of packages to an antiX-22 Sid runit setup such as you have.
I use “bare” Openbox without much else.
One application I don’t have is Synaptic. I use aptitude instead. Not sure why – perhaps there were too many required packages (although IIRC aptitude had a significant number also).
I don’t look at packages to identify “beta” upgrades from other ones. I shall try to look at those in the future. Oftentimes, a package just upgraded is upgraded again the next day. I assume this is because the developer was notified about a bug in the upgraded code. So, I just upgrade it again.
But that might have nothing to do with “beta” status. In truth, I consider all of Sid to be “beta” <g>.
Of course the major focus in both of our routines is to avoid upgrading from a nosystemd version to a “regular” systemd dependent one. (Holding or pinning the systemd packages is another valuable thing to do.)
By the way – to anyone reading this, best wishes for happy holidays and a good next year.
stevesr0
I use “bare” Openbox without much else.
One application I don’t have is Synaptic. I use aptitude instead. Not sure why – perhaps there were too many required packages (although IIRC aptitude had a significant number also).I see. We seem to have a rather different configuration of antiX. I do not have openbox but just standard set of antiX WMs, such as IceWM, JWM, etc. Also pretty much all apps that come with antiX Full, such as Openoffice, etc…
My goal was to have such antiX Full Runit but based on SID fully customized for look and feel of desktop and everything that I like to have in the regular ‘production’ system so I can actually use it full time. I have not discovered any adverse impact yet, but even if I happen to introduce any issue in the future then I will fall back to the previous ‘yesterday’s’ version USB Live stick and look at what caused the issue. All my antiX SID instances are Live…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersCorrection: I DO have Synaptic installed. I have just been used to aptitude. Interestingly, apt and Synaptic both report 1314 installed packages while aptitude lists only 1058 (but there are others found by search that are also listed as installed ??!).
olsztyn, your setup and approach sounds much more polished and secure than mine. I stand in awe and hope to learn from you..
By the way, I just posted a suggestion that a thread on staying nosystemd pure should be pinned to the top of the “Recent Posts” page with other HOW-TOs.
stevesr0
- This reply was modified 4 months, 2 weeks ago by stevesr0.
Hi all,
Pipewire and VLC continue to work fine without systemd (using seatd).
Anyone else out there using Pipewire on antiX? Love to hear from you…
stevesr0
Pipewire and VLC continue to work fine without systemd (using seatd).
Congrats on your successful implementation of Pipewire…
Although it is my goal for the future, I have not come yet to the point of understanding all pieces necessary for pipewire implementation. If at some point in the future it becomes possible for you to outline the steps to implement it, it will be greatly appreciated.
Thanks and regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHi olsztyn,
Thank you.
In response to your request,
Although it is my goal for the future, I have not come yet to the point of understanding all pieces necessary for pipewire implementation. If at some point in the future it becomes possible for you to outline the steps to implement it, it will be greatly appreciated.I am happy to attempt this. Since you are requesting it and we both are running Sid AND the recent versions of Pipewire are said to be more usable than the older ones, I will work on Sid specific directions.
I received assistance from Xecure in setting up Pipewire while using elogind and libelogind0 (he posted about this in the context of antiX-21 (Thread: “Pipewire to manage audio in antiX-21”, OP#59060).
I think that perhaps the only thing you might need beyond installing the nosystemd versions of the required packages and editing a config file MIGHT BE the use of the script and ./profile that activates gpg-agent.
I will review my system and (hopefully) post a step-by-step by the end of the weekend.
stevesr0
- You must be logged in to reply to this topic.
