Hello.

Using current 64 with xfce4, when I open a pdf with okular,
it opens flawlessly, but on the terminal I get the
message:

Icon theme "gnome" not found.
Icon theme "crystalsvg" not found.

Installed every theme* from SBo.

But now, since an upgrade,
when I open the pdf and close it, above message appears.
BUT when I inside okular start presentation mode (STRG+SHIFT+P),
this comes up (command line):

org.kde.okular.ui: Unable to inhibit screensaver
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.freedesktop.ScreenSaver was not provided by any .service files")

Killed xfce-screensaver, which didn't work anyway, same message.

xpdf triggers no error message, but it seems to have no presentation mode.
gv : no error message.

I guess I configured something badly.
But, above all, I'd like to understand.

What has okular to do with screensaver?
Why did this message come up after an upgrade
(sadly I don't remember which)?

cheers Erich

--

c·o·m·p·e·l·l·e·i·n·t·r·a·r·e·at·p·o·s·t·e·o·.·m·e

On 12.12.2021 at 16:54, eho scribbled:

> BUT when I inside okular start presentation mode (STRG+SHIFT+P),
> this comes up (command line):
>
> org.kde.okular.ui: Unable to inhibit screensaver
> QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
> org.freedesktop.ScreenSaver was not provided by any .service files")
>
> [...]
>
> What has okular to do with screensaver?

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.

> 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.

--
With respect,
= Aragorn =

Am Sun, 12 Dec 2021 18:27:19 +0100 schrieb Aragorn:

> On 12.12.2021 at 16:54, eho scribbled:
>
(...)
>> org.kde.okular.ui: Unable to inhibit screensaver
>> [...]
>>
>> What has okular to do with screensaver?
>
> 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.

Thus it seems that starting a kde program like okular in xfce4 generates
problems, or at least error messages? So that, as long as I stick
to xfce4, I should avoid using kde programs like okular.

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?

>> 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?

I tried to compile evince and zathura from SBo, but it did not work.
Alien seems not to have them.

Thanks Erich

--

c·o·m·p·e·l·l·e·i·n·t·r·a·r·e·at·p·o·s·t·e·o·.·m·e

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.

--
With respect,
= Aragorn

On 2021-12-12, eho <adress@signatu.re> wrote:
> Hello.
>
> Using current 64 with xfce4, when I open a pdf with okular,
> it opens flawlessly, but on the terminal I get the
> message:
>
> Icon theme "gnome" not found.
> Icon theme "crystalsvg" not found.
>
> Installed every theme* from SBo.
>
> But now, since an upgrade,
> when I open the pdf and close it, above message appears.
> BUT when I inside okular start presentation mode (STRG+SHIFT+P),
> this comes up (command line):
>
> org.kde.okular.ui: Unable to inhibit screensaver
> QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
> org.freedesktop.ScreenSaver was not provided by any .service files")
>
> Killed xfce-screensaver, which didn't work anyway, same message.
>
> xpdf triggers no error message, but it seems to have no presentation mode.
> gv : no error message.
>
> I guess I configured something badly.
> But, above all, I'd like to understand.
>
> What has okular to do with screensaver?
> Why did this message come up after an upgrade
> (sadly I don't remember which)?
>
> cheers Erich
>

Try installing oxygen-icons (packages, not SBo). It will fix most
icon issues outside KDE if you didn't install it fully.
On the screensaver, maybe xscreensaver and the xfce4-screensaver one clash
with each other. I'd remove xscreensaver with slackpkg.

Am Mon, 13 Dec 2021 09:01:47 +0100 schrieb Aragorn:

> On 12.12.2021 at 19:49, eho scribbled:
>
>> Am Sun, 12 Dec 2021 18:27:19 +0100 schrieb Aragorn:
[...]
>> 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. ;)

I thought Wayland is still under development, so it might improve=

[...]
> But you do have to keep in mind that the application
> only performs optimally when used in the environment that it was
> designed for.

Works for me.

[...]
> 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.

Oh, I'm not complaining. There is no perfection under the heavens, and an
OS is not a religion after all... in fact, after upgrading current today I
saw that there is a slackware64-15.0 mirror additionally to slackware64-
current, and though I think I'll swich to 15.0 stable, considering the
remarkable stability of current up to now, I'll keep it installed. It has
become a habit to regularily look into the changelogs and upgrade... ;)

[...]

Thanks a lot!

Erich

--

c·o·m·p·e·l·l·e·i·n·t·r·a·r·e·at·p·o·s·t·e·o·.·m·e

Am Tue, 14 Dec 2021 23:14:46 -0000 (UTC) schrieb Ander:

> On 2021-12-12, eho <adress@signatu.re> wrote:
[...]
>> org.kde.okular.ui: Unable to inhibit screensaver
>> QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
>> org.freedesktop.ScreenSaver was not provided by any .service files")
>>
>> Killed xfce-screensaver, which didn't work anyway, same message.
[...]

> Try installing oxygen-icons (packages, not SBo). It will fix most icon
> issues outside KDE if you didn't install it fully.
> On the screensaver, maybe xscreensaver and the xfce4-screensaver one
> clash with each other. I'd remove xscreensaver with slackpkg.

Here are my installed oxygen* packages:

32100 Dez 1 05:23 oxygen-5.23.4-x86_64-1
882 Okt 1 18:04 oxygen-fonts-5.4.3-noarch-4
1882 Okt 1 18:04 oxygen-gtk2-1.4.6-x86_64-4
410287 Dez 13 07:15 oxygen-icons5-5.89.0-noarch-1

So this seems not to turn out as the problem...;)

removed xscreensaver, no result. But, it's just messages, the programs
work, and
I can always alias ,okular='okular 2>/dev/null' and I don't see them any
more.

I'm happy with the OS.

Thanks erich

--

c·o·m·p·e·l·l·e·i·n·t·r·a·r·e·at·p·o·s·t·e·o·.·m·e

Am Wed, 15 Dec 2021 08:07:26 -0000 (UTC) schrieb eho:

> [...]
>> It might just be a glitch in Current.
[...]
> Oh, I'm not complaining. There is no perfection
> [...]

The glitch is gone.
As you said, it's all under development.

Or it was me who as the first person after the creation
of the world fiddlediddled something wrong himself
and my name is BSIFOTO (acronym I invented myself,
meaning "bug sitting in front of the OS" ;-)

Cheers Erich

--

c·o·m·p·e·l·l·e·i·n·t·r·a·r·e·at·p·o·s·t·e·o·.·m·e