Summary: | No plasma shell, black screen after today's update | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Alemar <dark.guy.2008> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | CC: | changoscalientes |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alemar
2020-10-09 16:55:11 UTC
Running kquitapp5 plasmashell kstart5 plasmashell Makes it work, but no window decorations, I'm stuck with openbox now. 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' ''' 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!! *** This bug has been marked as a duplicate of bug 427498 *** |