Hi everyone, I have this issue since I upgraded to Fedora 40 (Workstation)
To reproduce my issue:
- Go to activity view (from the top left corner or pressing super)
- Lock the screen (press Super + L)
Some logs: https://file.io/ddevVkVFXFCy
I also made an updgrade F39-F40 and when I do what you explain it just log’s me out. Logging in again lets me work without rebooting the system.
It looks like that you have gnome photos involved for your screensaver/login screen ?
Please first try to sudo dnf upgrade --refresh to being up to date and also check if you can resolve the issue with gnome photo. Check which version you have installed (Flatpak, which source or RPM)
Hi, sorry for the late response, but I still have this issue.
My system is updated.
Gnome photos version:
gnome-photos.x86_64 44.0-4.fc40
I just tried it twice and no problem unlocking and no Gnome crash. In fact I use it daily as I lock my PC when unattended during the day. Perhaps understanding a bit more about your system would give some clues to help us solve this.
Hi, thanks for your response, here’s some more informations.
âžś inxi -Fzxx
System:
Kernel: 6.8.11-300.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: GNOME v: 46.2 tk: GTK v: 3.24.42 wm: gnome-shell dm: GDM
Distro: Fedora Linux 40 (Workstation Edition)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550-PLUS v: Rev X.0x
serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 3202
date: 06/15/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Vertical Advanced Ergonomic
Mouse serial: <filter> charge: 100% (should be ignored)
status: discharging
CPU:
Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+
rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
Speed (MHz): avg: 2768 high: 3700 min/max: 2200/4650 boost: enabled cores:
1: 2200 2: 3033 3: 2200 4: 2200 5: 3589 6: 3700 7: 2403 8: 2200 9: 2200
10: 2200 11: 3700 12: 3593 bogomips: 88635
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Sapphire Nitro+ driver: amdgpu v: kernel arch: GCN-4 pcie:
speed: 2.5 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2,
DVI-D-1, HDMI-A-2 bus-ID: 0b:00.0 chip-ID: 1002:67df temp: 32.0 C
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.0
compositor: gnome-shell driver: gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102
diag: 551mm (21.7")
API: OpenGL v: 4.6 vendor: amd mesa v: 24.1.1 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi polaris10
LLVM 18.1.6 DRM 3.57 6.8.11-300.fc40.x86_64) device-ID: 1002:67df
display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: Sapphire driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:aaf0
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487
API: ALSA v: k6.8.11-300.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.7 status: active 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
driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
bus-ID: 06:00.0 chip-ID: 10ec:8168
IF: enp6s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0 chip-ID: 10ec:8125
IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
Device-1: TP-Link UB500 Adapter driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 2357:0604
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
Drives:
Local Storage: total: 2.74 TiB used: 698.57 GiB (24.9%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L7
size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 28.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 44.9 C
ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 976.56 GiB used: 486.32 GiB (49.8%) fs: btrfs
dev: /dev/nvme1n1p2
ID-2: /boot/efi size: 511 MiB used: 19 MiB (3.7%) fs: vfat
dev: /dev/nvme1n1p1
ID-3: /home size: 976.56 GiB used: 486.32 GiB (49.8%) fs: btrfs
dev: /dev/nvme1n1p2
ID-4: /var/log size: 976.56 GiB used: 486.32 GiB (49.8%) fs: btrfs
dev: /dev/nvme1n1p2
ID-5: /var/tmp size: 976.56 GiB used: 486.32 GiB (49.8%) fs: btrfs
dev: /dev/nvme1n1p2
Swap:
ID-1: swap-1 type: zram size: 31.24 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.5 C mobo: 30.0 C gpu: amdgpu temp: 32.0 C
Fan Speeds (rpm): fan-1: 0 fan-2: 715 fan-3: 387 fan-4: 0 fan-5: 0
fan-6: 0 fan-7: 0 gpu: amdgpu fan: 1743
Info:
Memory: total: 32 GiB available: 31.24 GiB used: 4.66 GiB (14.9%)
Processes: 492 Power: uptime: 5m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 62 Compilers: clang: 18.1.6 gcc: 14.1.1
Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.34
âžś sudo dmesg | grep gnome
[15670.356769] gnome-shell[2908]: segfault at 7265766f68 ip 00007ffa4937e52b sp 00007fff7f258328 error 4 in libc.so.6[7ffa4923b000+169000] likely on CPU 4 (core 4, socket 0)
[15805.927705] gnome-shell[156408]: segfault at 562e00000001 ip 00007fc9e4994e3b sp 00007ffcbbf865b0 error 4 in libst-14.so[7fc9e4964000+5b000] likely on CPU 1 (core 1, socket 0)
[15894.146091] gnome-shell[159732]: segfault at 55d657b0efe4 ip 00007efe21ae8e38 sp 00007fff6ea7f440 error 4 in libst-14.so[7efe21ab8000+5b000] likely on CPU 11 (core 5, socket 0)
[15964.845791] gnome-shell[162778]: segfault at 0 ip 00007f89c47c2e3b sp 00007ffc45525050 error 4 in libst-14.so[7f89c4792000+5b000] likely on CPU 10 (core 4, socket 0)
More logs
âžś journalctl -b -u gdm
giu 23 10:39:04 <redacted-hostname> systemd[1]: Starting gdm.service - GNOME Display Manager...
giu 23 10:39:04 <redacted-hostname> systemd[1]: Started gdm.service - GNOME Display Manager.
giu 23 10:39:24 <redacted-hostname> gdm-password][2654]: gkr-pam: unable to locate daemon control file
giu 23 10:39:24 <redacted-hostname> gdm-password][2654]: gkr-pam: stashed password to try later in open session
giu 23 10:39:25 <redacted-hostname> gdm[1772]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 10:39:27 <redacted-hostname> gdm[1772]: Gdm: Child process -1901 was already dead.
giu 23 10:39:27 <redacted-hostname> gdm[1772]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:08:03 <redacted-hostname> gdm[1772]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:08:03 <redacted-hostname> gdm[1772]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:08:14 <redacted-hostname> gdm-password][140220]: gkr-pam: unable to locate daemon control file
giu 23 13:08:14 <redacted-hostname> gdm-password][140220]: gkr-pam: stashed password to try later in open session
giu 23 13:08:15 <redacted-hostname> gdm[1772]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:08:17 <redacted-hostname> gdm[1772]: Gdm: Child process -139643 was already dead.
giu 23 13:08:17 <redacted-hostname> gdm[1772]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:10:20 <redacted-hostname> gdm[1772]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:10:20 <redacted-hostname> gdm[1772]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:14:16 <redacted-hostname> gdm-password][144019]: gkr-pam: unable to locate daemon control file
giu 23 13:14:16 <redacted-hostname> gdm-password][144019]: gkr-pam: stashed password to try later in open session
giu 23 13:14:17 <redacted-hostname> gdm[1772]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
giu 23 13:14:19 <redacted-hostname> gdm[1772]: Gdm: Child process -143371 was already dead.
giu 23 13:14:19 <redacted-hostname> gdm[1772]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
No problem here as well.
Did you already try to disable all extensions you are using?
1 Like
journalctl --no-hostname -b -u gdm is easier to create that <redacted-hostname> and needs less sideways scrolling on laptop screens.
Crashes in Gnome shell can be caused by defective extensions. It is often helpful to create a new vanilla login to see if the crash occurs there.
2 Likes
Hi, thank you for the tip.
I tried creating a new account and the crash doesn’t occur.
Here the list of installed extensions in my main account
âžś gnome-extensions list
launch-new-instance@gnome-shell-extensions.gcampax.github.com
window-list@gnome-shell-extensions.gcampax.github.com
apps-menu@gnome-shell-extensions.gcampax.github.com
just-perfection-desktop@just-perfection
app-hider@lynith.dev
appindicatorsupport@rgcjonas.gmail.com
background-logo@fedorahosted.org
places-menu@gnome-shell-extensions.gcampax.github.com
user-theme@gnome-shell-extensions.gcampax.github.com
dash-to-dock@micxgx.gmail.com
gamemode@christian.kellner.me
Ok. Try to disable them all, and see if the crash still occours.
If it doesn’t occour, try to enable the extensions one at a time.
1 Like
Make a list of extensions that are installed with current Fedora packages.
You may be able to find the extension with the issue using journalctl, if not, disable the ones that aren’t from Fedora packages, check for a package and install that, and then enable the others one at a time. If those all work, you can try disabling the ones from Fedora packages.
Okay, I found the extension that causes the problem, it is dash-to-dock
2 Likes
I ran into the same problem, and it turned out that the “Lock Screen Background” extension was causing the crash. After disabling it, everything is working fine now. However, I can no longer customize my background, and it has reverted to a gray screen. While it’s not ideal, I’m glad the issue has resolved.
It was indeed some of the extensions we added.
Welcome to Fedora @lorem
Can you please give some more specifications? Versions etc.
If you are testing the F41 Beta it might be that the Extension is not ready for F41 yet.
HI, thank you
I’ve been using Fedora for almost 5 months and I really love it.
if you are talking about the extension version
here:
I have received notification about the extension from software store, it’s gonna update now it’s so fast
You posted in a 4 month old topic. I like to know how your setup looks like now, today. Fedora Linux version etc.
Yes making an update of the extension is always good.