Bug 427495 (Horacio) - No plasma shell, black screen after today's update
Summary: No plasma shell, black screen after today's update
Status: RESOLVED DUPLICATE of bug 427498
Alias: Horacio
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: master
Platform: Neon Linux
: NOR critical
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-09 16:55 UTC by Alemar
Modified: 2020-10-10 05:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alemar 2020-10-09 16:55:11 UTC
SUMMARY

https://www.reddit.com/r/kdeneon/comments/j82fgk/kde_neon_latest_update_as_of_today_broke_my/

Okay so I can't post screenshots or anything, I have a bare firefox window with no decorations, plasma or desktop or anything whatsoever. I can't even move windows.

Basically, today Discover showed up some updates for KDE apps (as usual), I hit update, all good. Then I decide to reboot the computer and boom. I get the spinning logo where it says "Plasma made by KDE" and it stays there. I have mouse cursor, but only a black background.

Running "krunner" doesn't work.

Creating a new user didn't work, same result. I can't even logout from it (I could logout from my normal user) so the issue isn't my user/home dir, but the system.

I can run ksysguard, but no window decorations, ALT+drag, nada.

I can logout, the login manager appears, I can pick either X11 or Wayland. X11 goes through, Wayland just gets me back to the login manager.

Any help is greatly welcome, I'm stuck with a faulty system now :(

Edit: I was able to go to the console and install openbox and have a rudimentary taskbar with tint2. Plasma is broken though, this feels so 2000...

STEPS TO REPRODUCE
1. Update your packages as of today. Discover showed up a bunch of updates for KDE apps
2. Reboot
3. Boom.

OBSERVED RESULT
Black screen. Can work around it by using ALT+Space to launch other shells (I ran openbox and tint2). Rebooting doesn't work at all.

EXPECTED RESULT
My normal desktop, I need to work!

SOFTWARE/OS VERSIONS
Windows: Not relevant
macOS: Not relevant
Linux/KDE Plasma: 5.19.5 ? Latest as of today
(available in About System)
KDE Plasma Version: ???
KDE Frameworks Version: ???
Qt Version: ???

ADDITIONAL INFORMATION
Comment 1 Alemar 2020-10-09 17:01:42 UTC
Running

kquitapp5 plasmashell
kstart5 plasmashell 

Makes it work, but no window decorations, I'm stuck with openbox now.
Comment 2 Chango 2020-10-09 21:57:10 UTC
I can confirm this issue: After login only get a black screen and maouse cursor. Can run some app with ALT+F2 search bar but wihtout window manager

if execute 
  
''' cat ~/.xsession-errors | tail

kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 1250, result = 0
kdeinit5: opened connection to :0
kdeinit5: Got SETENV 'XCURSOR_THEME=Breeze_Snow' from launcher.
kdeinit5: Got SETENV 'XCURSOR_SIZE=24' from launcher.
kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/horacio/.gtkrc:/home/horacio/.config/gtkrc' from launcher.
kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/horacio/.gtkrc-2.0:/home/horacio/.config/gtkrc-2.0' from launcher.
/usr/bin/kwin_x11: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'

'''
Comment 3 Chango 2020-10-09 22:09:23 UTC
So far I only find this. 

*Log in kde 
*only get a black screen
* ALT + F2
* type "Konsole"
* in konsole execute "kwin" 
* it returns: 

kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE



Thanks!!
Comment 4 Christoph Feck 2020-10-10 05:06:48 UTC

*** This bug has been marked as a duplicate of bug 427498 ***