Bug 365165

Summary: org.kde.KScreen kscreen.xcb.helper: Event Error: 145
Product: [Plasma] KScreen Reporter: Bit Twister <bittwister2>
Component: libkscreenAssignee: Sebastian Kügler <sebas>
Status: RESOLVED WAITINGFORINFO    
Severity: normal    
Priority: NOR    
Version: 5.6.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: test procedure
kinfocenter screen shot

Description Bit Twister 2016-07-06 17:39:04 UTC
org.kde.KScreen[3856]: kscreen.xcb.helper: Event Error:  145

journalctl snippet
# looking in journalctl  
org.kde.KScreen[3856]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is:  1 . 5
 org.kde.KScreen[3856]: kscreen: Skipping "XRandR 1.1" backend
 org.kde.KScreen[3856]: kscreen.xrandr: Connected output 83 to CRTC 79
 org.kde.KScreen[3856]: kscreen.xcb.helper: Detected XRandR 1.5
 org.kde.KScreen[3856]: kscreen.xcb.helper: Event Base:  88
 org.kde.KScreen[3856]: kscreen.xcb.helper: Event Error:  145
 org.kde.KScreen[3856]: kscreen: Loading "XRandR" backend
 org.kde.KScreen[3856]: kscreen.xrandr: XRandR::setConfig
Comment 1 Bit Twister 2016-07-06 17:42:47 UTC
Created attachment 99891 [details]
test procedure
Comment 2 Sebastian Kügler 2016-07-06 22:45:36 UTC
Do you experience any functional problem, or is this just about the noise in your journal?

(In the latter case, you can disable the logging output in your ~/.config/QtProject/qtlogging.ini

It seems that the wrong backend is picked, do you have the KSCREEN_BACKEND env var set?

In any case, you're running an old version of Plasma, which we don't maintain anymore. I'd advise to upgrade to Plasma 5.7.
Comment 3 Bit Twister 2016-07-06 23:18:52 UTC
> Do you experience any functional problem,
Taking 30+ seconds to get a usable desktop.

> It seems that the wrong backend is picked, do you have the KSCREEN_BACKEND env var set?
No.

> In any case, you're running an old version of Plasma, which we don't maintain anymore. 

What command would I use to get the current Plasma version?
Comment 4 Sebastian Kügler 2016-07-07 00:45:06 UTC
Could you be more precise? Does it take 30 seconds to log in, to apply changes, or ... ?

kinfocenter shows the current Plasma version.

It seems that the wrong backend is picked by kscreen for whatever reason. You could try exporting KSCREEN_BACKEND=xrandr to force the correct backend (xrandr 1.1 is deprecated, your X actually provides xrandr 1.5, but the xrandr 1.1 backends doesn't understand it.
Comment 5 Bit Twister 2016-07-07 01:40:24 UTC
(In reply to Sebastian Kügler from comment #4)
> Could you be more precise? Does it take 30 seconds to log in, 
Yes, running plymouth login screen.
Timing starts after hitting enter after passwd.
I get a quick x11 X cursor then the little circle indicating working, ~20 seconds latter KDE splash screen.

> kinfocenter shows the current Plasma version.
OK, ran it down, I needed the command line app for dumping that for my bug_report script.

$  kf5-config --version
Qt: 5.6.1
KDE Frameworks: 5.23.0
kf5-config: 1.0

> It seems that the wrong backend is picked by kscreen for whatever reason.
> You could try exporting KSCREEN_BACKEND=xrandr to force the correct backend
> (xrandr 1.1 is deprecated, your X actually provides xrandr 1.5, but the
> xrandr 1.1 backends doesn't understand it.

Wow, setting KSCREEN_BACKEND=xrandr  jumped me right to the KDE splash screen.
Good news, all my autostart scripts ran.
Bad news,  No plasma desktop, just a black screen, no taskbar, no desktop shortcuts, no Alt+Space bar,.....

Just checked, and desktop and whatnot showed up while writing this message.
Going to move https://bugs.mageia.org/show_bug.cgi?id=17658 from kscreen to xrandr.

Thank you for your time and patience.
Comment 6 Sebastian Kügler 2016-07-07 11:29:16 UTC
That's not the Plasma version, but the Frameworks version. As I said, please run kinfocenter to find out.
Comment 7 Bit Twister 2016-07-07 12:18:15 UTC
Created attachment 99922 [details]
kinfocenter screen shot
Comment 8 Bit Twister 2016-07-07 12:21:48 UTC
(In reply to Sebastian Kügler from comment #6)
> That's not the Plasma version, but the Frameworks version. As I said, please
> run kinfocenter to find out.

Can not find any plasma version information in kinfocenter.

See kinfocenter screen shot attachment.

Quick launch of kde splash screen in comment 5, was a leftover/not dead yet process from previous login.   :(

Guessing this will help
$ plasmashell --version
plasmashell 5.6.5
Comment 9 Bit Twister 2016-07-07 12:24:29 UTC
 get_src_rpm /usr/bin/kinfocenter

      Installed rpm : kinfocenter-5.6.5-1.mga6
      Source rpm    : kinfocenter-5.6.5-1.mga6.src.rpm
      Information   : https://www.kde.org/
Comment 10 Sebastian Kügler 2016-07-07 12:35:47 UTC
Apparently, your distro changes the session file for plasma.desktop. Please find out the version in your distro.
Comment 11 Sebastian Kügler 2016-07-07 12:41:25 UTC
Please upgrade to Plasma 5.7 and show me the output of kscreen-doctor -b
Comment 12 Bit Twister 2016-07-07 12:55:12 UTC
(In reply to Sebastian Kügler from comment #10)
> Apparently, your distro changes the session file for plasma.desktop. Please
> find out the version in your distro.

You might need to give me specific file name when possible. I am just a dumb user here. Guessing

$ get_src_rpm /usr/share/xsessions/01plasma.desktop

      Installed rpm : plasma-workspace-5.6.5.1-1.mga6
      Source rpm    : plasma-workspace-5.6.5.1-1.mga6.src.rpm
      Information   : https://www.kde.org/
Comment 13 Bit Twister 2016-07-08 13:45:39 UTC
(In reply to Sebastian Kügler from comment #11)
> Please upgrade to Plasma 5.7 

Ok, Mageia developers have upgraded.
$ plasmashell --version
plasmashell 5.7.0

FYI: kinfocenter does not show plasma version.
$ get_src_rpm /usr/bin/kinfocenter

      Installed rpm : kinfocenter-5.7.0-1.mga6
      Source rpm    : kinfocenter-5.7.0-1.mga6.src.rpm
      Information   : https://www.kde.org/

> and show me the output of kscreen-doctor -b

$  kscreen-doctor -b
Environment: 
  * KSCREEN_BACKEND is        : [not set]
  * KSCREEN_BACKEND_INPROCESS : [not set]
Preferred KScreen backend : KSC_XRandR.so
Available KScreen backends:
  * KSC_Fake.so: /usr/lib64/qt5/plugins/kf5/kscreen/KSC_Fake.so
  * KSC_KWayland.so: /usr/lib64/qt5/plugins/kf5/kscreen/KSC_KWayland.so
  * KSC_QScreen.so: /usr/lib64/qt5/plugins/kf5/kscreen/KSC_QScreen.so
  * KSC_XRandR.so: /usr/lib64/qt5/plugins/kf5/kscreen/KSC_XRandR.so
  * KSC_XRandR11.so: /usr/lib64/qt5/plugins/kf5/kscreen/KSC_XRandR11.so

kscreen.xcb.helper: Event Error: 145 still occurs

set  export KSCREEN_BACKEND=KSC_XRandR.so over in /etc/profile.d/mu_custom_env.sh
rebooted, problem no longer shows up in the log.

kde/plasma launch  time still too long.
> (In reply to Sebastian Kügler from comment #4) > Could you be more precise? 

No idea about anyone's boot time but mine is pretty sad even after converting to
systemd networking knocking off ~40 seconds.

1. 40.62 seconds from grub2 launch to Plymouth login screen.
2. 35.42 seconds from pw enter to kde splash screen
3. 57.78 seconds until operational Plasma desktop.

1 and 3 gives me about 1 minute 38.40 seconds "boot" time.
with about 22.36 seconds Plasma time.

Is there somewhere other than user shell environment script that aught to  set KSCREEN_BACKEND ?