KDE & Gnome crashing after upgrade to FC40

I upgraded one of my systems that has KDE installed from 39 to 40. I didn’t get the display to login. checking the log kwin_wayland was crashing over and over. I tried installing gnome and changed the dm and i got the login display but after logging in anytime i opened a new windows gnome-session would crash and i’d get the login display. I tried both wayland and x11 for KDE/Gnome and both fail. Finally installed Cinnamon and i could login and actually open apps and windows. So my system is currently stable with Cinnamon. I noticed all the crash info under .cache/drkonqi and thought i should gets these reported so the issue can be fixed. So my 2nd issue is that i can’t get drkonqi to work. the systemd-coredump services fail with a “service reached run time limit”. I’ve not finding any good info on how to resolve this and get drkonqi to report these crashes. Does anyone know where i can find info to fix/debug drkonqi?

4:46 PM drkonqi-coredump-processor@13-39194-0.service: Failed with result 'timeout'.
4:46 PM drkonqi-coredump-processor@13-39194-0.service: Service reached runtime time limit. Stopping.
4:41 PM Started drkonqi-coredump-processor@13-39194-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.

hardware info

System:
  Kernel: 6.9.6-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Console: pty pts/1 DM: 1: GDM 2: KDM note: stopped 3: LightDM note: stopped
    4: SDDM note: stopped 5: XDM Distro: Fedora Linux 40 (Forty)
Machine:
  Type: Desktop Mobo: ASRock model: 970M Pro3 serial: <filter>
    UEFI-[Legacy]: American Megatrends v: P1.60 date: 06/17/2016
CPU:
  Info: 8-core model: AMD FX-8370E bits: 64 type: MCP arch: Piledriver rev: 0
    cache: L1: 384 KiB L2: 8 MiB L3: 8 MiB
  Speed (MHz): avg: 1587 high: 1900 min/max: 1400/3300 boost: enabled cores:
    1: 1400 2: 1400 3: 1900 4: 1400 5: 1900 6: 1400 7: 1900 8: 1400 bogomips: 51300
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: XFX Pine
    driver: radeon v: kernel arch: GCN-1 pcie: speed: 5 GT/s lanes: 8 ports:
    active: HDMI-A-1 empty: DVI-D-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6613
    temp: 47.0 C
  Display: server: X.org v: 1.20.14 with: Xwayland v: 24.1.0 driver: X:
    loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
    tty: 84x26
  Monitor-1: HDMI-A-1 model: LG (GoldStar) HDR 4K res: 3840x2160 dpi: 139
    diag: 806mm (31.7")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm:
    drv: radeonsi surfaceless: drv: radeonsi inactive: wayland,x11
  API: OpenGL v: 4.5 vendor: mesa v: 24.1.2 note: console (EGL sourced)
    renderer: OLAND (radeonsi LLVM 18.1.6 DRM 2.50 6.9.6-200.fc40.x86_64), llvmpipe
    (LLVM 18.1.6 256 bits)
  API: Vulkan v: 1.3.283 surfaces: N/A device: 0 type: cpu driver: N/A
    device-ID: 10005:0000
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel v: kernel
    bus-ID: 00:14.2 chip-ID: 1002:4383
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000
    Series] vendor: XFX Pine driver: snd_hda_intel v: kernel pcie: speed: 5 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 1002:aab0
  API: ALSA v: k6.9.6-200.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 05:00.0 chip-ID: 10ec:8168
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: macvtap0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-2: macvtap1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-3: macvtap3 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-4: virbr1 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-5: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-6: vnet1 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-7: vnet3 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
RAID:
  Device-1: md0 type: mdraid level: mirror status: active size: 499.7 MiB
  Info: report: 2/2 UU blocks: 511680 chunk-size: N/A super-blocks: 1.2
  Components: Online: 1: sdb1 2: sda1
  Device-2: md1 type: mdraid level: mirror status: active size: 446.52 GiB
  Info: report: 2/2 UU blocks: 468206592 chunk-size: N/A super-blocks: 1.2
  Components: Online: 1: sdb2 2: sda2
  Device-3: md2 type: mdraid level: mirror status: active size: 476.81 GiB
  Info: report: 2/2 UU blocks: 499975168 chunk-size: N/A super-blocks: 1.2
  Components: Online: 0: sde1 1: sdf1
  Device-4: md3 type: mdraid level: mirror status: active size: 953.74 GiB
  Info: report: 2/2 UU blocks: 1000071168 chunk-size: N/A super-blocks: 1.2
  Components: Online: 0: sdc1 1: sdd1
Drives:
  Local Storage: total: raw: 3.67 TiB usable: 1.83 TiB lvm-free: 10.77 GiB
    used: 1.08 TiB (58.7%)
  ID-1: /dev/sda vendor: A-Data model: SP550 size: 447.13 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 32 C
  ID-2: /dev/sdb vendor: A-Data model: SP550 size: 447.13 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 28 C
  ID-3: /dev/sdc vendor: A-Data model: SU800 size: 953.87 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 28 C
  ID-4: /dev/sdd vendor: A-Data model: SU800 size: 953.87 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 26 C
  ID-5: /dev/sde vendor: A-Data model: SU800 size: 476.94 GiB speed: <unknown>
    serial: <filter> temp: 53 C
  ID-6: /dev/sdf vendor: A-Data model: SU800 size: 476.94 GiB speed: <unknown>
    serial: <filter> temp: 53 C
Partition:
  ID-1: / size: 49.98 GiB used: 18.77 GiB (37.6%) fs: xfs dev: /dev/dm-0
    mapped: fedora_vmserver-root
  ID-2: /boot size: 473.7 MiB used: 399.8 MiB (84.4%) fs: ext4 dev: /dev/md0
  ID-3: /home size: 369.82 GiB used: 215.34 GiB (58.2%) fs: xfs dev: /dev/dm-2
    mapped: fedora_vmserver-home
Swap:
  ID-1: swap-1 type: partition size: 15.75 GiB used: 1.2 MiB (0.0%) priority: -2
    dev: /dev/dm-1 mapped: fedora_vmserver-swap
Sensors:
  System Temperatures: cpu: 45.0 C mobo: 39.0 C gpu: radeon temp: 47.0 C
  Fan Speeds (rpm): fan-1: 1310 fan-2: 934 fan-3: 0 fan-4: 0 fan-5: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.26 vbat: 3.38
Info:
  Memory: total: 32 GiB available: 31.31 GiB used: 20.6 GiB (65.8%)
  Processes: 360 Power: uptime: 9h 17m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: Compilers: gcc: 14.1.1 Shell: Bash v: 5.2.26 running-in: pty pts/1
    inxi: 3.3.34

Welcome to :fedora:

Can you provide journalctl -xe | fpaste --raw-url for us? Paste the url it returns here so we can have a look at the logs from the crash.

Also journalctl -b -1 | fpaste --raw-url to collect logs from the previous boot

Sounds like this topic: Gnome apps cause WM to fail on Fedora 40

1 Like

thank you, downgrading mesa fixed the issue with kde/gnome. I guess i’ll worry about drkonqi later if i need it.

So Mesa 24.X.X not really working well with older AMD cards? GCN1

Yeah, more specifically, those that use the radeon driver. Appears that some code was added to mesa that is valid for amdgpu, but not radeon. So if you are using the radeon driver, it crashes. I was lucky enough to have a card that works fine with amdgpu, so I just bypassed the issue by switching over via kernel parameters - and I plan to just stay with amdgpu. If you don’t have amdgpu supported hardware the only solution is to downgrade to the previous mesa release and wait. Hopefully it will be fixed soon. There are alot of folks that use the radeon driver.

1 Like