Fedora 43/Gnome 49 crashing apps

I have moved from Windows 11 to Fedora 43 and I have been using it for a couple of months now. I have used previous versions of Fedora in the past, and I always loved it. But with Fedora 43, things have been very different and difficult for me.

Apps keep crashing for no obvious reason(App has stopped working. Force to Quit). NOT A SINGLE DAY PASSES WITHOUT ME HAVING TO FORCEFULLY SHUTDOWN THE LAPTOP MULTIPLE TIMES(and no, it is not an exaggeration). Just before writing this I had just shutdown the laptop because My Files, of all apps stopped working and the screen just froze. I thought VS Code was the problem since I am always on it and maybe the extensions were too much for the laptop, uninstalled the extensions, still nothing. I have a basic workspace: VS Code, Cursor, Firefox, Zen, Docker, and Chrome, that’s it.

But using the OS has been unbearable.

I have a 11th Gen Intel Core i3 x4 Lenovo laptop, 12GB RAM DDR4, 256GB NVMe

post the output from inxi -Fzxx (as preformatted text) so we can see the full spec of the machine, version of stuff in use and so on.

If you can, view the output from journalctl for the time of the last lock-up and see if there’s anything in there which gives any indication of something failing - there may not be anything though, given that if it’s a hard-lock the buffers may not be flushed to dump the smoking gun information to the journal.

1 Like

Can you perform a memory test (memtest86+ - Fedora Packages) making sure this is not caused by a memory failure?

Is a Fedora 42 or Fedora 43 live system running stable without crashes?

System:
Kernel: 6.18.6-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: GNOME v: 49.3 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
Distro: Fedora Linux 43 (Workstation Edition)
Machine:
Type: Laptop System: LENOVO product: 82KB v: Lenovo V15 G2 ITL
serial: Chassis: type: 10 v: Lenovo V15 G2 ITL
serial:
Mobo: LENOVO model: LNVNB161216 v: NO DPK serial:
part-nu: LENOVO_MT_82KB_BU_idea_FM_V15 G2 ITL Firmware: UEFI vendor: LENOVO
v: GGCN59WW date: 04/11/2024
Battery:
ID-1: BAT0 charge: 29.3 Wh (100%) condition: 29.3/38 Wh (77.1%) volts: 8.56
min: 7.68 model: SMP L20M2PF0 serial: charging: status: full
cycles: 1169
CPU:
Info: dual core model: 11th Gen Intel Core i3-1115G4 bits: 64 type: MT MCP
arch: Tiger Lake rev: 1 cache: L1: 160 KiB L2: 2.5 MiB L3: 6 MiB
Speed (MHz): avg: 1418 min/max: 400/4100 cores: 1: 1418 2: 1418 3: 1418
4: 1418 bogomips: 23961
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Tiger Lake-LP GT2 [UHD Graphics G4] vendor: Lenovo
driver: i915 v: kernel arch: Xe ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 0000:00:02.0 chip-ID: 8086:9a78
Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 3-5:2 chip-ID: 04f2:b725
Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
driver: gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x08d5 res: 1920x1080 dpi: 142
diag: 395mm (15.5")
API: OpenGL v: 4.6 vendor: intel mesa v: 25.2.7 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel UHD Graphics (TGL GT2)
device-ID: 8086:9a78 display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr

RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b
Drives:
Local Storage: total: 238.47 GiB used: 39.89 GiB (16.7%)
ID-1: /dev/nvme0n1 vendor: KIOXIA model: SSSTC CL1-4D256 size: 238.47 GiB
speed: 31.6 Gb/s lanes: 4 serial: temp: 38.9 C
Partition:
ID-1: / size: 235.89 GiB used: 39.38 GiB (16.7%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 1.9 GiB used: 499.9 MiB (25.7%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 235.89 GiB used: 39.38 GiB (16.7%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 8 GiB (100.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 12 GiB note: est. available: 11.46 GiB
used: 10.16 GiB (88.7%)
Processes: 445 Power: uptime: 1h 46m wakeups: 0 Init: systemd v: 258
default: graphical
Packages: 33 pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 21
pm: snap pkgs: 12 Compilers: N/A Shell: Zsh v: 5.9 running-in: ptyxis-agent
inxi: 3.3.40

Also, at the last crash, and for the entire minute of the crash the log has been:

gnome-shell[2015]: Can’t update stage view actor (something…) is on because it needs an allocation

Can you post the output from coredumpctl list | tail -n 20 to show the last 20 crashes. If this is (mostly|always) gnome-shell, can you also list what extensions you have installed.

It would be handy to get that exact error message from journalctl too, if possible, rather than an elided version. If this is a frequent error message which you notice appearing alongside crashes, output from journalctl for several of them would be useful to ascertain if there’s a pattern.

Sun 2026-01-04 15:00:31 EET 887055 1000 1000 SIGABRT missing /usr/libexec/glycin-loaders/2+/glycin-svg -
Wed 2026-01-07 15:30:54 EET 33144 1000 1000 SIGABRT missing /usr/libexec/glycin-loaders/2+/glycin-svg -
Thu 2026-01-08 17:00:59 EET 5715 1000 1000 SIGABRT missing /home/jeanmako/.MathWorks/ServiceHost/-mw_shared_installs/v2026.1.0.2/bin/glnxa64/MathWorksServiceHost-Monitor -
Fri 2026-01-09 11:20:41 EET 10268 1000 1000 SIGSEGV missing /app/extra/wps-office/office6/wpscloudsvr -
Fri 2026-01-09 11:20:49 EET 10252 1000 1000 SIGSEGV missing /app/extra/wps-office/office6/wpp -
Fri 2026-01-09 11:21:00 EET 10567 1000 1000 SIGSEGV missing /app/extra/wps-office/office6/wpscloudsvr -
Sun 2026-01-11 09:03:58 EET 347547 1000 1000 SIGBUS missing /usr/share/cursor/chrome_crashpad_handler -
Thu 2026-01-15 15:22:52 EET 7675 1000 1000 SIGTRAP missing /opt/google/chrome/chrome -
Thu 2026-01-15 15:22:53 EET 3954 1000 1000 SIGSEGV missing /usr/bin/gnome-shell -
Thu 2026-01-15 18:26:51 EET 1402786 1000 1000 SIGABRT missing /usr/libexec/glycin-loaders/2+/glycin-svg -
Fri 2026-01-16 20:08:53 EET 616862 1000 1000 SIGILL present /opt/google/chrome/chrome 17.6M
Fri 2026-01-16 20:11:07 EET 634056 1000 1000 SIGILL present /opt/google/chrome/chrome 9.3M
Thu 2026-01-22 17:21:43 EET 698304 1000 1000 SIGBUS present /usr/share/cursor/chrome_crashpad_handler 45.7K
Fri 2026-01-23 17:30:44 EET 266344 1000 1000 SIGTRAP present /opt/google/chrome/chrome 32.4M
Sun 2026-01-25 11:14:13 EET 290423 1000 1000 SIGBUS present /usr/share/cursor/chrome_crashpad_handler 46.1K
Sun 2026-01-25 15:34:06 EET 505920 1000 1000 SIGABRT present /usr/libexec/glycin-loaders/2+/glycin-svg 592.5K
Sun 2026-01-25 17:46:00 EET 273855 1000 1000 SIGTRAP present /opt/google/chrome/chrome 30.3M
Thu 2026-01-29 16:47:42 EET 426935 1000 1000 SIGBUS present /usr/share/cursor/chrome_crashpad_handler 46.7K
Fri 2026-01-30 03:38:29 EET 812882 0 0 SIGABRT inaccessible /usr/lib/systemd/systemd-executor -
Fri 2026-01-30 12:23:54 EET 27986 1000 1000 SIGBUS present /usr/share/cursor/chrome_crashpad_handler 46.1K

If you remove the dash-to-dock extension, and see if the crash frequency reduces. I suspect it will.