On 12.12.2021 at 19:49, eho scribbled:
> Am Sun, 12 Dec 2021 18:27:19 +0100 schrieb Aragorn:
>
> > Okular is a KDE-native application. In its presentation mode, it
> > will prevent the KDE-specific screensaver (or screen locker) from
> > kicking in.
> >
> > It does this by communicating with the window manager by way of
> > qdbus, which is a qt-specific IPC bus that KDE software uses quite
> > extensively. But you're running XFCE, which is entirely GTK-based.
>
> Thanks. That explains it. I logged into a plasma wayland session,
> and the error message did not show up.
Plasma is great. Wayland, not so much yet at this point. ;)
> Thus it seems that starting a kde program like okular in xfce4
> generates problems, or at least error messages?
Well, most of those error messages should rather be interpreted as
warnings. They don't stop the application from working.
> So that, as long as I stick to xfce4, I should avoid using kde
> programs like okular.
Not necessarily. But you do have to keep in mind that the application
only performs optimally when used in the environment that it was
designed for.
>
> Well then, another problem came up. I tried to just log out from
> xfce4- session by using the "log out" button, but the screen just
> froze. Had to do that manually. Is this a xfce4 or slackware current
> problem?
It might just be a glitch in Current. You have to liken it somewhat to
the Testing branches of other distributions. The software is
constantly evolving, so getting it to work flawlessly is a moving
target.
> >> Why did this message come up after an upgrade (sadly I don't
> >> remember which)?
> >
> > Probably because of a change upstream, or perhaps because of a
> > change in packaging.
>
> This seems to mean that a kde program will not always run under other
> desktop environments?
It will, but — see higher up — not optimally. A lot also depends on
whether the application ships with a distro-specific default
configuration or not — hence my reference to the packaging.