From je-vv at e.email Tue Jan 9 19:36:48 2024 From: je-vv at e.email (Javier) Date: Tue, 9 Jan 2024 12:36:48 -0600 Subject: [artix-general] Any impacto on artix about changing towards dbus-broker? Message-ID: Hello, just to understand about the arch announcement and its impact on artix. Perhaps artix will follow, but removing the systemd components. Or perhaps artix won't make the change and remain with dbus-daemon. For a while they'll coexist, but on arch, pacman will ask for which to select, and arch recommends the default. Actually on such questions, most of the time I choose default. Will artix follow on the selection criteria as well? Thanks a lot ! -- Javier [1] https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Tue Jan 9 21:40:02 2024 From: somenxavier at posteo.net (Xavier B.) Date: Tue, 9 Jan 2024 20:40:02 +0000 Subject: [artix-general] Any impacto on artix about changing towards dbus-broker? In-Reply-To: References: Message-ID: <20240109214002.fcfc92b71d72c4c5b401b43a@posteo.net> I'm interested too in the official policy of the artix regarding this issue. Regards, Xavier On Tue, 9 Jan 2024 12:36:48 -0600 Javier ha escrit: > Hello, just to understand about the arch announcement and its impact on artix. > > Perhaps artix will follow, but removing the systemd components. Or perhaps artix won't make the change and remain with dbus-daemon. For a while they'll coexist, but on arch, pacman will ask for which to select, and arch recommends the default. Actually on such questions, most of the time I choose default. Will artix follow on the selection criteria as well? > > Thanks a lot ! > > -- > Javier > > > [1] https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon From je-vv at e.email Wed Jan 10 01:52:12 2024 From: je-vv at e.email (Javier) Date: Tue, 9 Jan 2024 18:52:12 -0600 Subject: [artix-general] offtopic: waybar simple quick launch buttons Message-ID: <4a875958-6c3f-4c0b-89e9-712917309bb1@e.email> Happy 2024 ! For those using waybar on wayland... AFAIK waybar doesn't offer quick launch buttons, but it does offer custom modules, which one can use to mimic such buttons. I'm using custom modules in a pretty simple way, for example for librewolf (I didn't find an awesome icon font for it, so using the FF one): > "custom/librewolf": { > "format": "?", > "interval": "once", > "on-click": "librewolf", > }, I have some other ones for other applications. I do use keybindings as well, and I can use wofi to search for the applications, but none of them are really alternatives for other users. It does work ! However I was looking for a very simple way to add what official modules, like a "tooltip-format" which is part of the official modules. Not sure why on earth it's not part of the custom modules. So for example, I'd look for something similar to: > "custom/librewolf": { > "format": "?", > "tooltip-format" "Firefox Browser" > "interval": "once", > "on-click": "librewolf", > }, So that if someone doesn't recognize the awesome font icon, one could just find out by the tip shown when getting the mouse on top of the button. As this is not supported. Is there any simple way to do that? Hopefully not requiring to add several scripts just for this. Something that might be part os such snippet, and pretty simple would be great, ? Please let me know of suggestions. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Wed Jan 10 23:12:07 2024 From: je-vv at e.email (Javier) Date: Wed, 10 Jan 2024 16:12:07 -0600 Subject: [artix-general] Any impacto on artix about changing towards dbus-broker? In-Reply-To: <20240109214002.fcfc92b71d72c4c5b401b43a@posteo.net> References: <20240109214002.fcfc92b71d72c4c5b401b43a@posteo.net> Message-ID: <33750b57-847f-4541-a5ba-09fbb851d7a8@e.email> On 1/9/24 14:40, Xavier B. wrote: > On Tue, 9 Jan 2024 12:36:48 -0600 > Javier ha escrit: > >> Hello, just to understand about the arch announcement and its impact on artix. >> >> Perhaps artix will follow, but removing the systemd components. Or perhaps artix won't make the change and remain with dbus-daemon. For a while they'll coexist, but on arch, pacman will ask for which to select, and arch recommends the default. Actually on such questions, most of the time I choose default. Will artix follow on the selection criteria as well? >> >> >> [1] https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon To be honest, the only thing I have dependent on dbus system wide is dbus-dinit: > % sudo dinitctl list | grep dbus > [{+} ] dbus (pid: 505) > [{+} ] dbus-pre As user before calling wayfire (wayland): > % grep dbus .local/bin/wayfire.sh > eval "$(dbus-launch --sh-syntax --exit-with-session)" And once wayfire is running, on one of its auto-start applications: > % grep dbus .config/wayfire.ini > a0 = dbus-update-activation-environment --all So, as long as those things keep working, if there's a change perhaps I don't even notice, and as on artix the services are packaged as -, maybe if there's any change it would be even more transparent to artix users. But still it would be good to know what artix will do, and if there's any user intervention at all... Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Thu Jan 25 19:07:58 2024 From: je-vv at e.email (Javier) Date: Thu, 25 Jan 2024 12:07:58 -0600 Subject: [artix-general] librewolf requiring rebuild given libvpx upgrade Message-ID: <99e93c40-1761-42bb-93e6-7933df9f9948@e.email> Xul depends on libvpx.so.8: > % ldd /usr/lib/librewolf/libxul.so > ... > libvpx.so.8 => /usr/lib/libvpx.so.8 (0x00007fa291400000) > ... However libvpx upgrade bumps the library to "libvpx.so.9", and breaks librewolf. My current work around was to revert the following packages: > % pacman -U /var/cache/pacman/pkg/libvpx-1.13.1-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/rav1e-0.6.6-3-x86_64.pkg.tar.zst /var/cache/pacman/pkg/libavif-1.0.3-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/ffmpeg4.4-4.4.4-3.1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/ffmpeg-2\:6.1.1-2-x86_64.pkg.tar.zst /var/cache/pacman/pkg/thunderbird-115.6.1-1-x86_64.pkg.tar.zst And then prevent the following ones from upgrading, until librewolf gets rebuilt: > % 'grep' '^IgnorePkg' /etc/pacman.conf > IgnorePkg = libvpx rav1e This leads to: > :: Starting full system upgrade... > warning: aurutils: local (18.5-1) is newer than galaxy (10b-1) > warning: birdtray: local (1.11.4-1) is newer than galaxy (1.9.0-2) > warning: conan: local (2.0.17-1) is newer than galaxy (1.45.0-1) > warning: jami-daemon: local (20231123-1) is newer than world (20230922-1) > warning: libvpx: ignoring package upgrade (1.13.1-1 => 1.14.0-1) > warning: nvm: local (0.39.7-1) is newer than galaxy (0.39.3-1) > warning: pandoc-bin: local (3.1.11-1) is newer than world (3.1.5-1) > warning: python-node-semver: local (0.8.1-2) is newer than galaxy (0.8.0-6) > warning: python-pluginbase: local (1.0.1-0) is newer than galaxy (1.0.0-5) > warning: rav1e: ignoring package upgrade (0.6.6-3 => 0.7.1-1) > warning: wayfire-plugins-extra: local (0.8.0-2) is newer than laur (0.8.0-1) > resolving dependencies... > warning: ignoring package rav1e-0.7.1-1 > warning: ignoring package rav1e-0.7.1-1 > warning: cannot resolve "librav1e.so=0.7-64", a dependency of "ffmpeg" > warning: ignoring package libvpx-1.14.0-1 > warning: ignoring package libvpx-1.14.0-1 > warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg" > warning: ignoring package rav1e-0.7.1-1 > warning: ignoring package rav1e-0.7.1-1 > warning: cannot resolve "librav1e.so=0.7-64", a dependency of "ffmpeg4.4" > warning: ignoring package libvpx-1.14.0-1 > warning: ignoring package libvpx-1.14.0-1 > warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg4.4" > warning: ignoring package rav1e-0.7.1-1 > warning: ignoring package rav1e-0.7.1-1 > warning: cannot resolve "librav1e.so=0.7-64", a dependency of "libavif" > warning: ignoring package libvpx-1.14.0-1 > warning: ignoring package libvpx-1.14.0-1 > warning: cannot resolve "libvpx.so=9-64", a dependency of "thunderbird" > warning: ignoring package rav1e-0.7.1-1 > warning: ignoring package rav1e-0.7.1-1 > warning: cannot resolve "librav1e.so=0.7-64", a dependency of "ffmpeg" > warning: ignoring package libvpx-1.14.0-1 > warning: ignoring package libvpx-1.14.0-1 > warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg" > :: The following packages cannot be upgraded due to unresolvable dependencies: > ffmpeg ffmpeg4.4 libavif thunderbird > > :: Do you want to skip the above packages for this upgrade? [y/N] y > looking for conflicting packages... > there is nothing to do I'm not sure if other packages broke with such revert, because the libvpx upgrade came with several other upgrades related to media: > Packages (20) ffmpeg-2:6.1.1-3 ffmpeg4.4-4.4.4-4 gst-libav-1.22.9-1 gst-plugin-gtk-1.22.9-1 gst-plugins-bad-1.22.9-1 gst-plugins-bad-libs-1.22.9-1 > gst-plugins-base-1.22.9-1 gst-plugins-base-libs-1.22.9-1 gst-plugins-good-1.22.9-1 gst-plugins-ugly-1.22.9-1 gst-python-1.22.9-1 gstreamer-1.22.9-1 > gstreamer-vaapi-1.22.9-1 libavif-1.0.3-2 libheif-1.17.6-3 libvpx-1.14.0-1 qt5-webengine-5.15.16-3 rav1e-0.7.1-1 suitesparse-7.6.0-1 But I didn't want to revert everything unnecessarily... Bottom line, librewolf needs a rebuild, :) Thanks a lot ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From artist at artixlinux.org Thu Jan 25 20:07:53 2024 From: artist at artixlinux.org (artist) Date: Thu, 25 Jan 2024 20:07:53 +0100 Subject: [artix-general] librewolf requiring rebuild given libvpx upgrade In-Reply-To: <99e93c40-1761-42bb-93e6-7933df9f9948@e.email> References: <99e93c40-1761-42bb-93e6-7933df9f9948@e.email> Message-ID: <46cb1d45-9d92-4393-9592-8211b92d84bf@artixlinux.org> rebuild was/is running, but takes a while; about 2 hrs left to go On a bended knee, or systemd, you will never live free On 1/25/24 19:07, Javier wrote: > Xul depends on libvpx.so.8: > >> % ldd /usr/lib/librewolf/libxul.so >> ... >> ??????? libvpx.so.8 => /usr/lib/libvpx.so.8 (0x00007fa291400000) >> ... > > However libvpx upgrade bumps the library to "libvpx.so.9", and breaks > librewolf.? My current work around was to revert the following packages: > >> % pacman -U /var/cache/pacman/pkg/libvpx-1.13.1-1-x86_64.pkg.tar.zst >> /var/cache/pacman/pkg/rav1e-0.6.6-3-x86_64.pkg.tar.zst >> /var/cache/pacman/pkg/libavif-1.0.3-1-x86_64.pkg.tar.zst >> /var/cache/pacman/pkg/ffmpeg4.4-4.4.4-3.1-x86_64.pkg.tar.zst >> /var/cache/pacman/pkg/ffmpeg-2\:6.1.1-2-x86_64.pkg.tar.zst >> /var/cache/pacman/pkg/thunderbird-115.6.1-1-x86_64.pkg.tar.zst > > And then prevent the following ones from upgrading, until librewolf > gets rebuilt: > >> % 'grep' '^IgnorePkg' /etc/pacman.conf >> IgnorePkg?? = libvpx rav1e > > This leads to: > >> :: Starting full system upgrade... >> warning: aurutils: local (18.5-1) is newer than galaxy (10b-1) >> warning: birdtray: local (1.11.4-1) is newer than galaxy (1.9.0-2) >> warning: conan: local (2.0.17-1) is newer than galaxy (1.45.0-1) >> warning: jami-daemon: local (20231123-1) is newer than world >> (20230922-1) >> warning: libvpx: ignoring package upgrade (1.13.1-1 => 1.14.0-1) >> warning: nvm: local (0.39.7-1) is newer than galaxy (0.39.3-1) >> warning: pandoc-bin: local (3.1.11-1) is newer than world (3.1.5-1) >> warning: python-node-semver: local (0.8.1-2) is newer than galaxy >> (0.8.0-6) >> warning: python-pluginbase: local (1.0.1-0) is newer than galaxy >> (1.0.0-5) >> warning: rav1e: ignoring package upgrade (0.6.6-3 => 0.7.1-1) >> warning: wayfire-plugins-extra: local (0.8.0-2) is newer than laur >> (0.8.0-1) >> resolving dependencies... >> warning: ignoring package rav1e-0.7.1-1 >> warning: ignoring package rav1e-0.7.1-1 >> warning: cannot resolve "librav1e.so=0.7-64", a dependency of "ffmpeg" >> warning: ignoring package libvpx-1.14.0-1 >> warning: ignoring package libvpx-1.14.0-1 >> warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg" >> warning: ignoring package rav1e-0.7.1-1 >> warning: ignoring package rav1e-0.7.1-1 >> warning: cannot resolve "librav1e.so=0.7-64", a dependency of >> "ffmpeg4.4" >> warning: ignoring package libvpx-1.14.0-1 >> warning: ignoring package libvpx-1.14.0-1 >> warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg4.4" >> warning: ignoring package rav1e-0.7.1-1 >> warning: ignoring package rav1e-0.7.1-1 >> warning: cannot resolve "librav1e.so=0.7-64", a dependency of "libavif" >> warning: ignoring package libvpx-1.14.0-1 >> warning: ignoring package libvpx-1.14.0-1 >> warning: cannot resolve "libvpx.so=9-64", a dependency of "thunderbird" >> warning: ignoring package rav1e-0.7.1-1 >> warning: ignoring package rav1e-0.7.1-1 >> warning: cannot resolve "librav1e.so=0.7-64", a dependency of "ffmpeg" >> warning: ignoring package libvpx-1.14.0-1 >> warning: ignoring package libvpx-1.14.0-1 >> warning: cannot resolve "libvpx.so=9-64", a dependency of "ffmpeg" >> :: The following packages cannot be upgraded due to unresolvable >> dependencies: >> ????? ffmpeg? ffmpeg4.4? libavif? thunderbird >> >> :: Do you want to skip the above packages for this upgrade? [y/N] y >> looking for conflicting packages... >> ?there is nothing to do > > I'm not sure if other packages broke with such revert, because the > libvpx upgrade came with several other upgrades related to media: > >> Packages (20) ffmpeg-2:6.1.1-3 ffmpeg4.4-4.4.4-4? gst-libav-1.22.9-1? >> gst-plugin-gtk-1.22.9-1 gst-plugins-bad-1.22.9-1? >> gst-plugins-bad-libs-1.22.9-1 >> ????????????? gst-plugins-base-1.22.9-1 >> gst-plugins-base-libs-1.22.9-1? gst-plugins-good-1.22.9-1 >> gst-plugins-ugly-1.22.9-1? gst-python-1.22.9-1 gstreamer-1.22.9-1 >> ????????????? gstreamer-vaapi-1.22.9-1? libavif-1.0.3-2 >> libheif-1.17.6-3? libvpx-1.14.0-1? qt5-webengine-5.15.16-3 >> rav1e-0.7.1-1? suitesparse-7.6.0-1 > > But I didn't want to revert everything unnecessarily... > > Bottom line, librewolf needs a rebuild, :) > > Thanks a lot ! > > From je-vv at e.email Thu Jan 25 23:03:22 2024 From: je-vv at e.email (Javier) Date: Thu, 25 Jan 2024 16:03:22 -0600 Subject: [artix-general] librewolf requiring rebuild given libvpx upgrade In-Reply-To: <46cb1d45-9d92-4393-9592-8211b92d84bf@artixlinux.org> References: <99e93c40-1761-42bb-93e6-7933df9f9948@e.email> <46cb1d45-9d92-4393-9592-8211b92d84bf@artixlinux.org> Message-ID: <7f475995-fa21-4a4c-9576-9a436c909a76@e.email> On 1/25/24 13:07, artist wrote: > rebuild was/is running, but takes a while; about 2 hrs left to go Already on mirrors. Thanks a lot ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: