Skip to main content ↑ ↓
Topic: Artix Wiki Totally Wrong and Overdue Fix (Read 813 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Artix Wiki Totally Wrong and Overdue Fix

Since the fiasco with apps vs pipewire or fiasco of pipewire vs apps (that totally kills CPU), I took a look directly at some of the specifications: xdg and rc init.

Artix wiki is totally wrong. First autostart via desktop file will not start as it driven by.... long and behold SYSTEMD. So Archwiki claiming that DEs provide autostart is wrong.  It will not work in Artix, beacuse what Arix wiki says is done via systemd (!). Sure you can go to KDE's GUI and try to add script or better a desktop file,  and click apply then put your pass in the popup (as long as you put kdsesu in usr/bin, because its not the default...). You can try use the special command to check your desktop file to "fix" what KDEs GUI provided, i.e. to add absolute path (exe= is correct but "Path=" is missig when creating it via KDE's GU..). You can also update via desktop files via another special command, but.... it won't work, because according to xdg specs it is managed by systemd.

After looking in the runit folder and doing pacman searches I can only see there's nothing to manage KDEs (xdg) creation of autostart in ~.config/autostart/. Theres no service to mange it as there's nothing for runit for this, neither there is "rc init"- no "-runit" (despite config file saying its "Artix", there's not "exit 0" either at the end...).  Nothing for bothe of those. No "-runit" serivce equivalent.

So running various pacman commands (Rns) and carefully removing pulse and outdated pulse leftovers bring us to nothing.

User cannot make pipewire to start with the system. We need Artix devs, to finally sit down and wirte runit service for pipewire. Sure one can add some tray icon for the short bash script and click it after login. But this is NOT A GOOD SOLUTION. One would like to have login suound for example. (And if you click it twice, weird things will happen....). Nice shutown via runit will also be nice (not just killall).

Some articles, when I was searching the subject, brought the review of Artix and there was some talk about pipewire not being done.
Per my testing pulse is finished. Done. Not working anymore. So the users are left with incomplete system.

Then of course is the matter of KDEs settings of NTP/Time (systmd/timesyncd), where gui will not work. This is fixable but only with direct Konsole commands and tweaking IPs after chrony installation. I'm saying this because more and more drifts apart and is left unfixed after departure from systemd.

So for now we need "pipewire-runit". Wiki solution is not a solution as all of those is systemd.

Re: Artix Wiki Totally Wrong and Overdue Fix

Reply #1 –
what

Re: Artix Wiki Totally Wrong and Overdue Fix

Reply #2 –
Quote
First autostart via desktop file will not start as it driven by.... long and behold SYSTEMD.

I think it has nothing to do with SystemD. See this.

Quote
Wiki solution is not a solution as all of those is systemd.

Have you ever read the follows at this page:

Quote
Or add it to your ~/.xinitrc, if you use it:

Re: Artix Wiki Totally Wrong and Overdue Fix

Reply #3 –
I ran with the wiki (albeit the migration from Arch) and I only had one beef with it, resolv.conf should have been left along (or at least till after getting all the packages etc.

Easy to work around with a temp resolv at that moment.  Of course, I opted for OpenRC so perhaps your experience was different than mine.

Of course, this has nothing to do with pipewire - so I probably should have just held my toungue
Supercalifragilisticexpialidocious