Discover keeps crashing

Issues & Assistance
1

For the last two weeks or so, discover crashes when trying to update. Discover hangs when fetching the updates, and after a short while, the app crashes.

I tried to uninstall and reinstall Discover and also removed to .config file, but I keep having the same problem. I do not have the same problem on my laptop. It only happens on my desktop.

garuda-inxi

a-optiplex9020 ~]$ garuda-inxi
System:
  Kernel: 6.4.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=31d43c73-77b7-46ce-aa52-aa8b9f29c9fb rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_wayland vt: 1
    dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Dell product: OptiPlex 9020 v: 00
    serial: <superuser required> Chassis: type: 15 serial: <superuser required>
  Mobo: Dell model: 0XCR8D v: A02 serial: <superuser required> UEFI: Dell
    v: A20 date: 05/23/2017
CPU:
  Info: model: Intel Core i7-4770 bits: 64 type: MT MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1694 high: 3900 min/max: 800/3900 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1230 2: 800 3: 798
    4: 2046 5: 3184 6: 3900 7: 800 8: 800 bogomips: 54274
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: Dell driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: HDMI-A-1 empty: DP-1, DP-2, HDMI-A-2, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
  Device-2: ARC Camera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6.3:7 chip-ID: 05a3:9331
    class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-1 res: 2560x1080 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 23.1.3 renderer: Mesa Intel HD Graphics 4600 (HSW
    GT2) direct-render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
    class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell 8
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-3: C-Media Audio Adapter (Unitek Y-247A)
    driver: cmedia_hs100b,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-3:2 chip-ID: 0d8c:0014 class-ID: 0300
  Device-4: ARC Camera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6.3:7 chip-ID: 05a3:9331
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.4.2-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.73 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 Ethernet I217-LM vendor: Dell driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: wlp0s20u9 state: down mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1
    bus-ID: 3-6.4.2:10 chip-ID: 0a12:0001 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
  Local Storage: total: 417.33 GiB used: 338.64 GiB (81.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: LITE-ON IT model: LCS-128M6S 2.5 7mm
    128GB size: 119.24 GiB block-size: physical: 512 B logical: 512 B
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 10E scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MQ01ACF032
    size: 298.09 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: 1D scheme: MBR
Partition:
  ID-1: / raw-size: 43.95 GiB size: 43.95 GiB (100.00%)
    used: 17.81 GiB (40.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-2: /boot/efi raw-size: 550 MiB size: 548.9 MiB (99.80%)
    used: 576 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 74.75 GiB size: 74.75 GiB (100.00%)
    used: 38.87 GiB (52.0%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-4: /var/log raw-size: 43.95 GiB size: 43.95 GiB (100.00%)
    used: 17.81 GiB (40.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-5: /var/tmp raw-size: 43.95 GiB size: 43.95 GiB (100.00%)
    used: 17.81 GiB (40.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.53 GiB used: 342.5 MiB (2.2%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 321 Uptime: 11h 25m wakeups: 0 Memory: available: 15.53 GiB
  used: 10.65 GiB (68.5%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1597
  libs: 399 tools: octopi,paru,yay pm: flatpak pkgs: 0 Shell: Bash v: 5.1.16
  running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
  System install date:     2023-07-03
  Last full system update: 2023-07-08
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
2

With Garuda Linux, you should not use the Discover app to update your system. Instead, update in the terminal with this command:

garuda-update

You can learn more about the Garuda Update script and the available options it can be used with here:

7 Likes
3

You shouldn't even have Discover installed.

1 Like
4

Discover is fine for browsing for software, but I wouldn't recommend it for system updates.

4 Likes
5

Just to make clear. I am not using Discover for system updates. Just to update some of the software installed through Discover. Mainly flatpak apps and themes.
I either use Octopi or terminal to update my system. I have been using Linux for about 20 years. Not an expert, but not a noob either.

I am just wondering how I could reset Discover so that it will do what it is supposed to be doing. :grinning:

1 Like
6

And most definitely not update from it. As for installing apps Octopi or Pacseek or straight up command line.

7

Try creating a new user on your system and test if the Discover application is working properly for them.

2 Likes
8

Please stop this rhetoric. It is inaccurate and misleading.

Discover is fine to install, and you should install it, just don’t use it to update your system. What it is good for is updating any themes from your System Settings or widgets obtained from the KDE Store or Pling. In fact, it is the only software that will update these. Not even a ‘garuda-update’ will update these applications. Use it only for that purpose.

5 Likes
9

Exactly. If you want to keep your KDE themes updated, the easiest (only?) way is using Discover. The alternative, AFAIK, is by updating them one by one through the theme installer.

10

I had not thought about that. It worked indeed. This means that something is corrupted in my current settings. If I can not find the reason, I probably will migrate to the new profile.

11

I understand what you are saying. If discovery is not the way to go, could you suggest to me how I could easily update themes and icon packs etc. without Discover?

12

It might be a long shot, but you could try deleting the cache directory or moving it to backup. I'm not sure what other user-specific files Discover maintains.

mv ~/.cache/discover/ ~/.cache/discover.bak

Then re-open Discover and check for improvement.

4 Likes
13

I keep it around explicitly for the same reasons Rodney does. Hardly ever use it; it's just there. Flatpak, too, just in case I run into a game I can't live without, that's all.

Don't install packagekit-qt5 (optional dependency) and you're fine.

5 Likes
14

I tried this, but it did not work. I have no idea what files are corrupted. Furthermore, I removed the discoverrc file as well. It does not seem to make any difference.
For now, I will log in into the guest account to update. This seems to work.