Description of problem: journalctl snippet org.kde.KScreen[3842]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4 kscreen.xrandr: Connected output 83 to CRTC 79 kscreen.xcb.helper: Detected XRandR 1.4 kscreen.xcb.helper: Event Base: 89 kscreen.xcb.helper: Event Error: 147 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. journalctl | grep -i kscreen 2. 3. Reproducible: Steps to Reproduce:
Blocks: (none) => 17523
Assignee: bugsquad => mageia
Please report this bug upstream
Keywords: (none) => UPSTREAM
URL: (none) => https://bugs.kde.org/show_bug.cgi?id=365165Summary: mga6: kscreen.xcb.helper: Event Error: 147 => 6_s1: kscreen.xcb.helper: Event Error: 145
[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145 What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Sebastian Kügler <sebas@kde.org> --- 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.
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.
Source RPM: libkscreen-5.5.4-1.mga6.src.rpm => xrandr-1.5.0-1.mga6.src.rpm
(In reply to Bit Twister from comment #2) > [KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145 > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |UNMAINTAINED [...] > > 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. Well, that's convenient... So basically as a stable distro we're on our own, since upstream considers Plasma 5.6.5 unmaintained two weeks after it's released...
(In reply to Rémi Verschelde from comment #4) > Well, that's convenient... So basically as a stable distro we're on our own, > since upstream considers Plasma 5.6.5 unmaintained two weeks after it's > released... It do make the developer's job much easier. :( (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 A little happy that QA seems to like the idea of using the newer KDE release. Still guessing xrandr will be scrape goat for slow kde login. Slow Plymouth login is not going to help general public acceptance either. I added splash back to kernel boot but plymouth login screen is still slow, bug 17530 and bug 17521
is this bug still valid under Plasma 5.7.1 ?
(In reply to Nicolas Lécureuil from comment #6) > is this bug still valid under Plasma 5.7.1 ? Yes.
Assignee: mageia => kde
is it still valid with current cauldron ?
CC: (none) => mageia
(In reply to Nicolas Lécureuil from comment #8) > is it still valid with current cauldron ? My, my, aren't we in a bit of a hurry. :) I've been working since 1am testing my bug reports. Since you are in such a hurry, I'll close this because journalctl | grep -i kscreen | grep Error does not return Error 145
Status: NEW => RESOLVEDResolution: (none) => FIXED