Bug 681792 – kde-plasma/plasma-workspace-5.14.5.1 : sess2Str is not a member of KDisplayManager; class KDisplayManager has no member named lockSwitchVT; NETRootInfo was not declared in this scope; ri was not declared in this scope

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pistos 2019-03-26 12:55:40 UTC]

kde-plasma/plasma-workspace-5.14.5.1 repeatedly refuses to emerge (compile).  I have recently upgraded gcc versions to 8.2.0 .  I followed https://wiki.gentoo.org/wiki/Upgrading_GCC as regards libtool, llvm and clang rebuilds.  Recently (2019-03-25), I rebuilt all installed packages matching /.*qt.*/ (getting the list of packages with `eix -cI qt`).  Full build log and emerge --info attached.  Please advise.

Reproducible: Always

Steps to Reproduce:
1. emerge plasma-workspace

Actual Results:  
The emerge fails.  See attached build log.

Expected Results:  
The emerge should succeed.

KDE is in an unstable state.  After suspending to RAM and waking back up again, there is a message about the screen locker being broken, and logging back in cannot be performed.  KDE must be restarted (e.g. via /etc/init.d/xdm restart).  Also, the usual launcher that comes up via Alt-F2 is broken: It appears, but when you start typing, it goes away, and nothing happens.  When the K menu is activated, and you start typing, it seems like the whole task bar and other KDE widgets disappear or crash.  The windows remain.  But, again, KDE must be restarted to get a functioning experience.

All these symptoms could be distinct from the emerge problem, but I'm just mentioning them anyway, in case it could provide clues.

[Comment 1 Pistos 2019-03-26 12:59:01 UTC]

Created attachment 570838 [details]
Full build log for plasma-workspace-5.14.5.1

[Comment 2 Pistos 2019-03-26 13:00:15 UTC]

Created attachment 570840 [details]
emerge --info for system that fails to emerge plasma-workspace-5.14.5.1

[Comment 3 Pistos 2019-03-26 13:23:25 UTC]

Created attachment 570844 [details]
emerge --info for DIFFERENT system that has the exact same four error messages when attempting to emerge plasma-workspace

Full build log (for this different system) can be provided if desired, but eyeballing the error output, I see what appears to be exactly the same four error messages as is already shown in the currently-attached build log (from the first system).

[Comment 4 Andreas Sturmlechner 2019-03-26 13:57:09 UTC]

Why do you have ~arch cmake on your arch system?

> dev-util/cmake:           3.14.0::gentoo

It might be fixed by applying this patch:

https://cgit.kde.org/plasma-workspace.git/patch/?id=c534fdf1ba34d0ea8a08b9b5266384a3243271e0

[Comment 5 Pistos 2019-03-26 14:16:27 UTC]

> Why do you have ~arch cmake on your arch system?

My package.accept_keywords says it is needed by media-sound/musescore-3.0.1-r1  .  However, I am happy to downgrade that if it means stabilizing my system.  I will try.

[Comment 6 Pistos 2019-03-26 16:01:24 UTC]

I was able to emerge kde-plasma/plasa-meta-5.15.3, and all other dependent kde-plasma/*-5.15.3 packages.  Provided that the rest of my KDE system can stay stable alongside that, this is a satisfactory workaround for me.

[Comment 7 Pistos 2019-03-27 00:22:53 UTC]

Just adding more data:

On the second system, I emerged only musescore 2.x, and so was able to keep cmake at version 3.9.6 there.  plasma-workspace still didn't emerge successfully, but then I re-emerged all installed qt packages, and then all kde-plasma/*, and then plasma-workspace finally emerged successfully.

So, I got it emerged on both systems, in different ways.  I guess it has to do with matching cmake with the qt packages and the plasma packages.

[Comment 8 Andreas Sturmlechner 2019-03-27 20:21:09 UTC]

(In reply to Pistos from comment #7)
> but then I re-emerged all installed qt packages, and then all
> kde-plasma/*, and then plasma-workspace finally emerged successfully.
I guess *something* was fixed, but without knowing about the second error (that may have been something else entirely, did you check?) it is difficult to draw conclusions.

[Comment 9 QIN Yuhao 2019-03-31 03:29:58 UTC]

(In reply to Pistos from comment #7)
> Just adding more data:
> 
> On the second system, I emerged only musescore 2.x, and so was able to keep
> cmake at version 3.9.6 there.  plasma-workspace still didn't emerge
> successfully, but then I re-emerged all installed qt packages, and then all
> kde-plasma/*, and then plasma-workspace finally emerged successfully.
> 
> So, I got it emerged on both systems, in different ways.  I guess it has to
> do with matching cmake with the qt packages and the plasma packages.

No need of emerging all of them. kde-plasma/libkworkspace and kde-plasma/plasma-workspace are enough.

By the way, media-gfx/graphviz also seems to be affected by this 'bug'.

[Comment 10 Michael Palimaka (kensington) 2019-04-01 09:45:27 UTC]

Do you have any failing build logs available for libkworkspace?

[Comment 11 QIN Yuhao 2019-04-01 10:03:15 UTC]

(In reply to Michael Palimaka (kensington) from comment #10)
> Do you have any failing build logs available for libkworkspace?

kde-plasma/libkworkspace was built with lots of warnings about TRUE defined as 0, just like plasma-workspace.

[Comment 12 Michael Palimaka (kensington) 2019-04-01 10:06:13 UTC]

(In reply to QIN Yuhao from comment #11)
> (In reply to Michael Palimaka (kensington) from comment #10)
> > Do you have any failing build logs available for libkworkspace?
> 
> kde-plasma/libkworkspace was built with lots of warnings about TRUE defined
> as 0, just like plasma-workspace.

Great, this is fixed in 5.15 branch with patch identified in comment #4.

[Comment 13 QIN Yuhao 2019-04-01 11:18:22 UTC]

(In reply to Michael Palimaka (kensington) from comment #12)
> (In reply to QIN Yuhao from comment #11)
> > (In reply to Michael Palimaka (kensington) from comment #10)
> > > Do you have any failing build logs available for libkworkspace?
> > 
> > kde-plasma/libkworkspace was built with lots of warnings about TRUE defined
> > as 0, just like plasma-workspace.
> 
> Great, this is fixed in 5.15 branch with patch identified in comment #4.

I think a patch for libkworkspace is also in need. I cannot walkthrough by only patching plasma-workspace, as libkworkspace IS compiled WITHOUT X11 support by cmake-3.14.

[Comment 14 Michael Palimaka (kensington) 2019-04-01 11:24:55 UTC]

libkworkspace is split downstream from from plasma-workspace, so the upstream patch applies to both.