search

blue-build / modules

BlueBuild standard modules used for building your Atomic Images
Apache License 2.0
24 stars 5 forks source link

yafti doesn't autostart on sericea images #159

Open RoyalOughtness opened 11 months ago

RoyalOughtness commented 11 months ago

To reproduce:

rebase to a ublue sericea image

Expected behavior:

yafti autostarts

Actual behavior:

yafti doesn't appear

bsherman commented 10 months ago

Yafti is not included in any of the *-main, *-nvidia images, regardless of silverblue, kinoite, sericea, etc.

It IS included in Bluefin and Bazzite images, though those are not sericea based.

If you want yafti on sericea, you'll need to build a custom image and include it.

RoyalOughtness commented 10 months ago

@bsherman Whoops! This should have been created against yafti or startingpoint I think. The issue is that when yafti is included in startingpoint-based images for KDE and GNOME, it works fine, but not for Sway.

xynydev commented 10 months ago

Sway doesn't autostart programs in the same way full-blown DEs do and that's why the desktop file doesn't cut it. I guess it could be replaced with a startup service but idk if that would work. You could try doing that with a similar approach as the default-flatpaks module and report the findings if interested.

Otherwise, this is a known limitation and there's not much else we can do about it.

bsherman commented 10 months ago

Well, I agree that stock sway itself does not automatically start desktop files, however... Fedora Sericea pre-configures sway to start *.desktop apps in $HOME/.config/autostart/ .

@qoijjj that said, i think you're asking for a feature, not reporting a bug, right?

RoyalOughtness commented 10 months ago

@bsherman yeah it's either a request to extend the feature to work with sericea out of the box, or a report of a bug where the feature is broken on sericea :smile:

xynydev commented 10 months ago

Fedora Sericea pre-configures sway to start *.desktop apps in $HOME/.config/autostart/.

Interesting. If that works, it should mean that yafti works normally. @qoijjj are you on Sericea? There could be something in some log file somewhere indicating a failure to start due to missing deps or something...

Heus-Sueh commented 10 months ago

I can confirm that Yafti doesn't start on Hyprland either

This is my repository in case anyone wants to investigate further https://github.com/Heus-Sueh/Viper-OS

fiftydinar commented 1 month ago

Setting the additional issue label to blocked, as this is something that upstream (Universal Blue) should solve.

Maybe it's smart to make the issue about this in their repo, as I can't see any that are related to this: https://github.com/ublue-os/yafti/

Maybe yafti rewrite will solve this, as current autostart logic looks hacky.