~scoopta/wofi#223: 
Libadwaita don't launch correctly

Fedora 40 WorkStation Linux 6.8.7-300.fc40.x86_64 Uses Wayfire WM

Some libadwaita-based applications, such as Nautilus, are unable to be launched using Wofi. This appears to be because DBusActivatable=true is not implemented correctly, as it launches successfully using Rofi and via the terminal. It appears that the application's gapplication daemon (launched via application --gapplication-service) is not being launched correctly, then directly loaded from dbus, as this issue does not occur if the gapplication-service is started manually beforehand in another terminal.

Status
REPORTED
Submitter
Jliwin98
Assigned to
No-one
Submitted
7 months ago
Updated
7 months ago
Labels
No labels applied.

~scoopta 7 months ago

Hmmm, I might spin up a fedora VM? This is interesting because on Debian this does not happen, I daily drive nautilus and quite a few other libadwaita apps and haven't experienced this. Additionally the dbus handling is passed off to GIO and not directly done by wofi which makes this slightly more puzzling. Wofi does have a different code path for dealing with dbus apps but this is primarily to avoid prematurely closing and killing the app before it starts due to the asynchronous nature of dbus execution.

Johnathon Li 7 months ago ยท edit

Sure, thanks! Specially, it's running nautilus version 46.1 and wofi 1.4.1. Interestingly, the issue doesn't happen on GNOME, likely because of integration between GNOME and DBus that doesn't happen with other DEs. I have reproduced this behaviour on sway and WayFire, both running wlroots.

~scoopta 7 months ago

Maybe it's an issue caused by nautilus 46. I'm on Debian sid(unstable rolling release) and running sway but we're still on nautilus 45.2 so possibly something changed there.

Register here or Log in to comment, or comment via email.