Bug 482069

Summary: No Krunner after upgrading from 5.27 to 6.0
Product: [KDE Neon] neon Reporter: mattias.lundahl
Component: Packages User EditionAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: jr, neon-bugs, sitter
Priority: NOR Keywords: qt6
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description mattias.lundahl 2024-02-29 17:55:17 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I upgraded from 5.27 to 6.0 using Discover and after a reboot I can't use Krunner.

STEPS TO REPRODUCE
1. Upgrade from 5.27 to 6.0 via Discover
2. Reboot
3. Log in

OBSERVED RESULT
It is not possible to open Krunner using its keyboard shortcut. A faint sound effect plays when I try to launch Krunner. I tried launching it from Konsole and get the following message:

warning: queue 0x5614e29df530 destroyed while proxies still attached:
  wl_registry@38 still attached
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[destroyed object]: error 7: importing the supplied dmabufs failed
The Wayland connection experienced a fatal error: Protocol error


EXPECTED RESULT
Krunner should work as usual

SOFTWARE/OS VERSIONS
Linux: 6.5
KDE Plasma Version: 6.0
KDE Frameworks Version: 6.0
Qt Version: 6.6

ADDITIONAL INFORMATION
Booting from the latest Neon User ISO works as expected
Comment 1 Antonio Rojas 2024-02-29 18:03:27 UTC

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