Reply to topic

Issues with kdeinit5: Could not connect to any X display.

kaszak
Registered Member
Posts
1
Karma
0
Hello!

Recently i've been having some issues with my KDE setup. Sometimes, when i open Dolphin, the thumbnails stop showing up, and i can no longer open files by double-clicking them. For some files just nothing happens, for others (mostly text files) it shows an error like this:
Image
which translates to "KDEInit can't open /bin/kate". Whenever it starts happening, the journal is spammed with these messages (in this example i tried opening an image):
Code: Select all
lis 27 08:30:04 laptopk kdeinit5[2738]: qt.qpa.screen: QXcbConnection: Could not connect to display :0
lis 27 08:30:04 laptopk kdeinit5[2738]: Could not connect to any X display.
lis 27 08:36:02 laptopk gwenview[3076]: qt.qpa.screen: QXcbConnection: Could not connect to display :0
lis 27 08:36:02 laptopk gwenview[3076]: Could not connect to any X display.

It's odd, since Xorg is running normally, i can launch applications manually and they manage to find X just fine, it only happens through Dolphin, and desktop icons. The issue gets fixed when i manually invoke "kdeinit5" in shell, until it decides to start happening again. Here's the log from shell when i do that:

Code: Select all
 ~  kdeinit5
kdeinit5: Shutting down running client.
kdeinit5: preparing to launch '/usr/lib/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 5000, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0
Icon theme "gnome" not found.
kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/thumbnail.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/thumbnail.so'
Qt: Session management error: networkIdsList argument is NULL
Icon theme "gnome" not found.


My setup:
Kernel 4.19.4
Plasma 5.14.3
Frameworks 5.52.0
Dolphin 18.08.3
Qt 5.11.2

It's worth noting that my CMOS battery is busted, so i'm relying on NTP service to grab correct time on launch. The battery's been busted for years, but the issue just started happening recently on KDE, but could it be related?

EDIT:

I seem to have fixed it by adding
Code: Select all
xhost +si:localuser:kaszak
to my .xprofile. It doesn't address the underlying problem (which i suppose is my busted clock :-\ ), but i'll take it.

Reply to topic

Bookmarks



Who is online

Registered users: amkek, Baidu [Spider], Bing [Bot], boudewijn, bovender, Exabot [Bot], Google [Bot], robgriff444, shansson, totoro