Discover software no longer works since last kde update
‘To use Discover for apps, install your preferred module on the Settings page, under Missing Backends.’
How would I go about remedying ths?
Please always include your garuda-inxi as required in the topic template.
This is clearly a KDE bug, there is nothing we can do about it other than wait.
Or better, use pacman for installing and garuda-update for updating.
It could be this bug, but KDE is getting around 200 bug reports / day after KDE6 release, so, also searching is a jungle…
https://bugs.kde.org/show_bug.cgi?id=481993
4 Likes
Sorry, please see garuda-inxi
garuda-inxi
System:
Kernel: 6.8.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4888c917-7368-4db7-9b43-4b9817ee22d8 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.0.2 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7B51 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: MPG Z390 GAMING PLUS (MS-7B51) v: 1.0
serial: <superuser required> uuid: <superuser required>
UEFI: American Megatrends v: 1.E1 date: 11/17/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K540e
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i5-9600K bits: 64 type: MCP arch: Coffee Lake
gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xD (13) microcode: 0xFC
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
desc: 1x9 MiB
Speed (MHz): avg: 4400 high: 4401 min/max: 800/4600 scaling:
driver: intel_pstate governor: performance cores: 1: 4400 2: 4400 3: 4400
4: 4400 5: 4400 6: 4401 bogomips: 44398
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
vendor: Micro-Star MSI driver: nvidia v: 550.54.14
alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: none off: DP-3 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
Device-2: Realtek EKACOM-K20E driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 0bda:5696
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x392mm (27.64x15.43")
s-diag: 804mm (31.65")
Monitor-1: DP-3 mapped: DP-4 note: disabled model: Samsung U32R59x
serial: <filter> built: 2022 res: 3840x2160 hz: 60 dpi: 140 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB
API: Vulkan v: 1.3.279 layers: 5 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3060 driver: nvidia v: 550.54.14
device-ID: 10de:2504 surfaces: xcb,xlib
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228e
class-ID: 0403
Device-3: Realtek EKACOM-K20E driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 0bda:5696
class-ID: 0102 serial: <filter>
API: ALSA v: k6.8.1-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:5
chip-ID: 8087:0aaa class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 16.94 TiB used: 279.94 GiB (1.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:6 vendor: Western Digital
model: WDS500G2B0C-00PXH0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 211210WD temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Samsung
model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 38.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T3X0C-00SJG0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 111110WD temp: 35.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD101FZBX-00ATAA0 size: 9.1 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD30EFRX-68EUZN0 size: 2.73 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A82 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD20PURZ-85GU6Y0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A80 scheme: GPT
ID-7: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WDS100T2B0A-00SM50 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 00WD
scheme: GPT
ID-8: /dev/sdf maj-min: 8:80 vendor: NorelSys model: 1081CS1
size: 119.08 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 279.94 GiB (60.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:9
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:8
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 279.94 GiB (60.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:9
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 279.94 GiB (60.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:9
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 279.94 GiB (60.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:9
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 6 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 33.0 C pch: 65.0 C mobo: N/A gpu: nvidia
temp: 54 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.28 GiB used: 5.06 GiB (16.2%)
Processes: 308 Power: uptime: 2h 23m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1715 libs: 509 tools: octopi,paru Compilers:
gcc: 13.2.1 Shell: garuda-inxi default: Bash v: 5.2.26 running-in: konsole
inxi: 3.3.33
Garuda (2.6.23-1):
System install date: 2024-02-27
Last full system update: 2024-03-21 ↻
Is partially upgraded: No
Relevant software: snapper(custom) NetworkManager dracut nvidia-dkms
Windows dual boot: Probably (Run as root to verify)
Failed units:
1 Like
Just in case, a reboot is peding, but I believe the issue is due to a KDE bug.
1 Like
OK thanks.
I wish Octopi had a decent GUI, as this wouldn’t be needed.
Actually Discover works just fine, it just doesn’t currently load to the systray. As for Octopi having a decent GUI that’s a matter of interpretation. Personally I install Bauh-staging so if I want to see all updates available in an orderly list I can. As for doing updates I run upd (alias for garuda-update) then Topgrade then Discover to see if there are any theme components that need updating that the other two didn’t pickup.
2 Likes
Wait, I had the same problem. It is just a matter of adding this optional dependency
https://archlinux.org/packages/extra/x86_64/packagekit-qt6/
sudo pacman -Syu packagekit-qt6
Now it works fine for me as well.
5 Likes
That’s the wrong backend–it enables updating Arch repos, a no-no-no-no.
1 Like
Then post the right one and not just wag your finger while hollering shame shame shame. 
1 Like
Did this and while the command ran my screen went completely black, text came up said something was “taking over the console” and I panicked and powered off my PC. Restoring snapshots didn’t work but current one did so I just booted fine it seems…
Any ideas what happened?
Please, open new help request and follow the template.
All I can say is that I have discover but do not use it.
Opening it I found the error message of the OP, but installing the backend seemed to work, in the sense that there was no longer an error and the screen was “showing applications”.
I have already suggested too many times not to use these tools to install (once already today).
I honestly don’t know what the problems behind it might be.
For me, if you can use it to search with in an easy way (without installing or updating) the tool does its job (the minimum, for me).
That being said, there were other backends only for flatpak and fwupd (they might be added as well). I didn’t notice anything else.
2 Likes
Discover is also a tool (although broken currently in Plasma 6) that is the ONLY tool that lets you automate updating themes and widgets with ease, and yes, you need packagekit-qt6 installed to do so. You should not, as noted, use it to update anything else. It serves as a great visual package and description viewer.
3 Likes
Broken on SOME Plasma 6 desktops? I haven’t had an issue with it here other than it not sitting in the systray, which adding the one file fixed.
NO, you do not. Packagekit-qt5 was not needed in Plasma 5, and neither is -qt6 needed in Plasma 6.
It is ONLY needed when installing/updating repositories. Or in @someotheruser’s case, his anus-to-mouth function. 
thx that helped
discover was working for me before plasma6 upgrade
so maybe there should be a dependency on packagekit-qt6 somewhere
1 Like
Just clinically defining what an “anus” is, Rodney.
Nothing to see here, Citizen.
Move on.
1 Like
I don’t think most people do, but in Arch it is a part of the “plasma-meta” group and default. I have always usually used the “plasma” subgroup by itself, which excludes Discover, but not always.
Historically, I didn’t start paying any attention to it until one of @RodneyCK’s earlier posts commentating on the necessity of a Discover in maintaining non-Garuda stuff, I think, such as themes, icons, etc. That’s when I started using it to install Plasma theming, etc. in Discover, in Arch (I dunno if Rodney was running Garuda or Arch in those posts).
Discover was working with the normal dependencies (none) until, for me, a clean install yesterday. That included the ability to install theming, icons, yada, etc. except flatpaks because I installed & enabled it.
It’s (apparently) not true that Discover is broken for all, not every function. But is it broken? Yes, for now.
Look, I ducked, hedged, groused as loud as anyone about the upcoming Plasma 6. But it is the best Operating System I’ve run since IBM PC DOS 2.0. Including DR-DOS.
RIP Gary Kildall.
2 Likes
Oh just explaining that you’re one, so nothing new we didn’t already know.