Christopher Schramm

> If blueman is using the Gtk.StatusIcon instead of the StatusNotifier then it's expected it breaks as it relies on X11. Oh, true, GTK's Wayland backend does not support it....

`StatusNotifierItem` is the default as the applet plugin is enabled by default (its `__autoload__` defaults to `True`) and its indicator implementation takes precedence over the fallback. Please show us `dconf...

It makes sense if we cannot make any progress. In this case we're still waiting on data on our assumption that people might be running into the GTK implementation, see...

This might just be #1241 / #620. I don't think the application actually crashes, does it?

The systemd unit is a dbus service that invokes the application when its well-known name gets addressed on the bus. I'm not familiar with Fedora things, but most probably `/etc/xdg/autostart/blueman.desktop`...

I can only repeat what I already wrote: It's #1241 / #620. The application does not crash at all. It's a harmless exception from GLib code. Fedora's ABRT picks it...

@engn33r: Sure, it will be contained in 2.4, but there is no schedule.

I'm not sure if that's a proper way. At least it's compatibility hell. There's `org.xfce.ScreenSaver`, `org.mate.ScreenSaver`, `org.cinnamon.ScreenSaver`, `com.deepin.ScreenSaver`, ... and other lockers do not have such an interface at all.

> If they expose org.freedesktop.ScreenSaver I don't have to specifically handle them. They don't. The names I mentioned are both the bus and interface names. Object paths differ as well....

I still don't get why it doesn't. If you look at https://cgit.freedesktop.org/xdg/xdg-utils/tree/scripts/xdg-screensaver.in, you see that it should do exactly what you're doing here in its `screensaver_freedesktop` function. If your change...