You are not logged in.

#1 2018-04-01 13:56:19

jfk
Member
Registered: 2017-12-11
Posts: 131

Primary display nuked on startup after updating (Plasma)

After doing my monthly -Syu, my primary display (external monitor) came up nuked (no taskbar, no wallpaper). I'm running on Plasma 5, X.org. Two points are striking:

1.  When I go to the display settings, my primary monitor is set right. If I make my laptop monitor primary and then go back, the issue is solved.

2. If I log-off after doing (1.), the problem does not reappear. But if I restart, my external monitor is nuked again.

There is an issue at startup. Do you know which process could be at stake?

Offline

#2 2018-04-03 22:26:49

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

OK I dig a little and I believe the issue comes from plasmashell that doesn't wanna start at boot. Here is what I got if anyone could identify the problem (which is referred on other forums but without a clear answer):

$ kbuildsycoca5 && kquitapp5 plasmashell && kstart5 plasmashell
kbuildsycoca5 running...
kf5.kservice.services: The desktop entry file "/usr/share/applications/org.kde.systemmonitor.desktop" has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :  "/usr/share/applications/org.kde.systemmonitor.desktop"
org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo"
org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo"
org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo"
trying to show an empty dialog
Omitting both --window and --windowclass arguments is not recommended
[fabien@xps-13-fp ~]$ org.kde.plasmaquick: Applet preload policy set to 1
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
kf5.kpackage: No metadata file in the package, expected it at: "/home/fabien/Téléchargements/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/fabien/Téléchargements/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/fabien/Téléchargements/"
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:294:17: QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:294:17: QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:294:17: QML Text: Binding loop detected for property "width"
couldn't convert QVariant(QJSValue, ) to translate
Empty filename passed to function
Empty filename passed to function
couldn't convert QVariant(QJSValue, ) to translate
org.kde.plasmaquick: New Applet  "Tiled Menu" with a weight of 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Loading Calendar plugin PimEventsPlugin(0x559ce648b580)
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Horloge numérique" with a weight of 0
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
trying to show an empty dialog
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
org.kde.plasmaquick: New Applet  "Notifications" with a weight of 0
org.kde.plasmaquick: New Applet  "Volume audio" with a weight of 0
Plasma Shell startup completed
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/code/logic.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/logic.js")
org.kde.plasmaquick: New Applet  "Batterie et luminosité" with a weight of 0
Both point size and pixel size set. Using pixel size.
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/code/logic.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js")
org.kde.plasmaquick: New Applet  "Bluetooth" with a weight of 0
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices"
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Capabilities"
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "ConnectivityCheckAvailable"
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "ConnectivityCheckEnabled"
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices"
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "GlobalDnsConfiguration"
networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
org.kde.plasmaquick: New Applet  "Réseaux" with a weight of 0
trying to show an empty dialog
qml: rootModel.refresh.star 1522794047243
KActivities: Database connection:  "kactivities_db_resources_140663507425280_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Nothing to load - the client id is empty
qml: rootModel.refresh.done 1522794047287
qml: allAppsModel.refresh().star 1522794047345
qml: allAppsModel.refresh().done 1522794047367

Last edited by jfk (2018-04-03 22:29:19)

Offline

#3 2018-04-04 02:33:31

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,456

Re: Primary display nuked on startup after updating (Plasma)

Try creating a new user and log in as that user (i.e. a clean Plasma/KDE profile), does the problem go away? If so, it's likely one of your .config settings; you could then try the instructions at the Wiki to isolate it: https://wiki.archlinux.org/index.php/KD … _strangely.

Edit: also describe how are you starting KDE/Plasma? Are you using SDDM?

Last edited by twelveeighty (2018-04-04 02:35:22)

Offline

#4 2018-04-10 16:30:54

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

Hi

Thank you for your reply.

I tried to follow your advise but the new user cannot connect to Xserver. Is it normal?

Thanks

n.b. I also tried to remove .cache and .config with my user but the problem persists.

Last edited by jfk (2018-04-10 16:32:39)

Offline

#5 2018-04-11 11:24:42

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,557

Re: Primary display nuked on startup after updating (Plasma)

twelveeighty wrote:

Edit: also describe how are you starting KDE/Plasma? Are you using SDDM?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#6 2018-04-13 20:23:52

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

Hi,

Thanks for your help.

Yes I'm using SDDM. But KDE's splash screen is always well displayed so I'm not sure the problem comes from SDDM.

I must add that I noticed the issue happens 8 times out of 10. Sometimes the session starts normally.

Last edited by jfk (2018-04-13 20:28:02)

Offline

#7 2018-04-14 00:17:51

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,456

Re: Primary display nuked on startup after updating (Plasma)

jfk wrote:

the new user cannot connect to Xserver

Just so I'm understanding you correctly: with a *new* user you have the *exact same* problem, or is there different behavior logging in as a new user?

Also, please help us help you by providing the exact, verbatim error logs: "cannot connect to Xserver" can mean a lot of things, or could be an incorrect interpretation of the actual error/issue.

Offline

#8 2018-04-14 14:12:26

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,557

Re: Primary display nuked on startup after updating (Plasma)

KActivities: Database connection:  "kactivities_db_resources_140663507425280_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Nothing to load - the client id is empty

There have been problems with kactivitymanagerd recently, try removing ~/.local/share/kactivitymanagerd/  folder


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#9 2018-04-30 22:04:52

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

Thank you for your answers (sorry been very busy).

1.

Also, please help us help you by providing the exact, verbatim error logs: "cannot connect to Xserver" can mean a lot of things, or could be an incorrect interpretation of the actual error/issue.

What I did is:

1. useradd -m user
2. passwd user
3. log-off
4. su user / passwd
5. startx

and there I got :

Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused.
xinit: server error


2.

There have been problems with kactivitymanagerd recently, try removing ~/.local/share/kactivitymanagerd/  folder

I tried that but without success.

Offline

#10 2018-05-01 11:17:02

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,557

Re: Primary display nuked on startup after updating (Plasma)

3. log-off
4. su user / passwd
5. startx

Why are you using the su command there instead of logout & login as the new user ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#11 2018-05-01 13:53:53

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

Why are you using the su command there instead of logout & login as the new user ?

I'm on auto-login with the primary user (through a getty script). It's simpler than modifying the auto-login.

Offline

#12 2018-05-03 08:18:39

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,557

Re: Primary display nuked on startup after updating (Plasma)

I do think there have been cases where su / startx didn't work but log out / logon did .

Try Alt+F2 ( or 3,4,5,6 ) to open  a new tty and login as the new user on that one .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#13 2018-05-05 16:44:04

jfk
Member
Registered: 2017-12-11
Posts: 131

Re: Primary display nuked on startup after updating (Plasma)

Try Alt+F2 ( or 3,4,5,6 ) to open  a new tty and login as the new user on that one .

Thanks I managed to connect that way (startx, then startkde).

Unfortunately the problem persists even on a brand new user session. Something went wrong on a deeper level apparently.

Last edited by jfk (2018-05-06 10:56:56)

Offline

Board footer

Powered by FluxBB