SUMMARY Plasma Discover won't start after plasma upgrade from 6.1.5 to 6.2 STEPS TO REPRODUCE 1. Upgrade to Plasma 6.2 2. Attempt to open Discover OBSERVED RESULT When clicking to open Discover, the application won't start. Running the application from terminal with `plasma-discover` leaves the terminal hanging indefinitely. When using sudo however `sudo palsma-discover` this is what I see: ``` libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin") org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true adding empty sources model QStandardItemModel(0x565a7db34610) ``` Then the terminal hangs indefinitely. EXPECTED RESULT Discover should open when the icon is clicked and when executed from terminal SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Processor: AMD Ryzen 9 7950X 16-Core Processor Memory: 62.4 GiB of RAM GPU: Radeon RX 7900 XTX Manufacturer: ASUS
The Graphic Platform I'm using is Wayland
Kernel Version: 6.8.0-45-generic (64-bit)
How did you update? Interactive or offline? If it was an interactive update, did you remember to reboot afterwards?
I update the PC using Discover
What OS are you using, and what version of Qt does it ship? I suspect this is a known Qt regression.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
SUMMARY - Plasma Discover won't work correctly. I am posting a link. You can read a more in-depth version here. https://discuss.kde.org/t/kde-neon-plasma-discovery-and-notify-icon-not-working-properly/27881 Here is my OS info - No LSB modules are available. Distributor ID: Neon Description: KDE neon 6.2 Release: 24.04 Codename: noble Kernel: Linux 6.8.0-51-generic Architecture: x86-64 STEPS TO REPRODUCE 1, Upgrade to Plasma 6.2 2. Attempt to open Discover OBSERVED RESULT have had the plasma-discover not want to load when I click on the icon in the task bar when I want to install a new app or check for updates, or when the (plasma-discover notify) icon in the notification area pops-up and lets me know I have updates. Also, when I try to load plasma-discovery in konsole discover hangs. However, when loading it with one of the following commands it comes up - plasma-discover --backends packagekit,fwupd,kns,snap,flatpak or plasma-discover --backends packagekit-backend EXPECTED RESULT Clicking on the plasma-dicover icon in the start menu, or taskbar, or shortcut on desktop, the icon in the notify area, along with starting it in konsole should allow the plasma-discover to come up and be usable. ADDITIONAL OS / APPS INFO KDE Plasma v6.2.5 KDE Framework v6.9.0 Discover v6.2.5 Konsole v24.12.0 QT v6.8.1 HARDWARE INFO Processor: 16 × AMD Ryzen 7 4800U with Radeon Graphics Memory: 15.0 GiB of RAM Graphic Processor: AMD Radeon Graphics Graphics Platform: Wayland Manufacturer: AZW
Please run the following command when that happens. This should ultimately lead to the crash report wizard appearing. You can use that to file a bug report about the hang. killall -SEGV plasma-discover
(In reply to Harald Sitter from comment #9) > Please run the following command when that happens. This should ultimately > lead to the crash report wizard appearing. You can use that to file a bug > report about the hang. > > killall -SEGV plasma-discover I get - plasma-discover: no process found It's more hit or miss now with opening it up from the panel or desktop panel (taskbar). Sometimes it works, and other time it doesn't. It will still not open from the discovery icon in the notification area.
Jeff, does `which plasma-discover` also fail to find anything? If so, then your system is in an incorrect state, which is likely unrelated to the originally reported issue here.