Bug 494340 - Plasma Discover won't start after plasma upgrade from 6.1.5 to 6.2
Summary: Plasma Discover won't start after plasma upgrade from 6.1.5 to 6.2
Status: REOPENED
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 6.2.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-09 10:50 UTC by angelo.orru
Modified: 2025-11-18 07:56 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description angelo.orru 2024-10-09 10:50:20 UTC
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
Comment 1 angelo.orru 2024-10-09 10:51:22 UTC
The Graphic Platform I'm using is Wayland
Comment 2 angelo.orru 2024-10-09 11:29:17 UTC
Kernel Version: 6.8.0-45-generic (64-bit)
Comment 3 Nate Graham 2024-10-10 17:45:29 UTC
How did you update? Interactive or offline? If it was an interactive update, did you remember to reboot afterwards?
Comment 4 angelo.orru 2024-10-11 14:15:07 UTC
I update the PC using Discover
Comment 5 Nate Graham 2024-10-15 22:41:35 UTC
What OS are you using, and what version of Qt does it ship? I suspect this is a known Qt regression.
Comment 6 Bug Janitor Service 2024-10-30 03:46:55 UTC
๐Ÿ›๐Ÿงน โš ๏ธ 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!
Comment 7 Bug Janitor Service 2024-11-14 03:46:48 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 8 Jeff.Davis 2025-01-08 06:16:16 UTC
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
Comment 9 Harald Sitter 2025-01-25 12:42:58 UTC
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
Comment 10 Bug Janitor Service 2025-02-09 03:47:01 UTC
๐Ÿ›๐Ÿงน โš ๏ธ 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!
Comment 11 Jeff.Davis 2025-02-11 02:45:12 UTC
(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.
Comment 12 Nate Graham 2025-02-11 14:39:00 UTC
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.
Comment 13 Bug Janitor Service 2025-02-26 03:46:42 UTC
๐Ÿ›๐Ÿงน โš ๏ธ 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!
Comment 14 Bug Janitor Service 2025-03-13 03:47:12 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 15 owan 2025-11-09 04:10:35 UTC
the root cause is like `plasma-discover` loading sequence

ref. https://discuss.kde.org/t/kde-neon-plasma-discovery-and-notify-icon-not-working-properly/27881/5


In my enviroment, the available backends are listed as follows:

```
plasma-discover --listbackends
libEGL warning: egl: failed to create dri2 screen
Available backends:
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
 * packagekit-backend
 * snap-backend
 * kns-backend
 * flatpak-backend
 * fwupd-backend
```

When loading the backends in this sequence (with packagekit loaded first):
plasma-discover will not respond.

```
$ plasma-discover --backends packagekit,snap,kns,flatpak,fwupd
libEGL warning: egl: failed to create dri2 screen
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x5edef99063e0)
```

However, if packagekit is moved to the last position in the sequence, plasma-discover starts normally.

```
$ plasma-discover --backends snap,kns,flatpak,fwupd,packagekit
libEGL warning: egl: failed to create dri2 screen
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x5c43fe86ec10)
looking up wrong category or too early "Games"
looking up wrong category or too early "Development"
qrc:/qt/qml/org/kde/kirigami/private/PrivateActionToolButton.qml:71:5: QML Binding: Binding loop detected for property "value":
qrc:/qt/qml/org/kde/kirigami/private/PrivateActionToolButton.qml:74:9
```
Comment 16 Dennis 2025-11-18 07:56:01 UTC
I experience exactly the same:

plasma-discover --listbackends
libEGL warning: egl: failed to create dri2 screen
Available backends:
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
 * kns-backend
 * packagekit-backend
 * snap-backend
 * flatpak-backend
 * fwupd-backend

Discover does NOT start with:
plasma-discover --backends kns,packagekit,snap,flatpak,fwupd

Discover DOES start with:
plasma-discover --backends kns,snap,flatpak,fwupd,packagekit

system details:
Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.3
Kernel Version: 6.14.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 ร— AMD Ryzen 9 5900 12-Core Processor
Memory: 32 GiB of RAM (31,2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3070
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.24.0