Cannot Log in after upgrade to 44

Ask Fedora
, , ,
1

Hi, I’m unable to login to my account. When I try to log in (through plasma login manager), I get a black screen and am eventually dumped back to plasma login manager.

I’m able to work around it by opening a tty terminal and running startplasma

Creating a test user, and logging in as them also worked – but I’d rather keep my user config if possible.

Logs
https://gist.github.com/TheDestroyer19/7767b08120cf7fb5323ffb06d164402e

Steps taken for this log:

  1. Reboot system
  2. Try to login as ‘the’ (UID is 1000)
  3. Watch black screen until it returns to login screen
  4. Switch to tty5
  5. Login, and run the below command:
    journalctl -b > may30.log

System Specs:

I’m running Fedora KDE

the@arcadia ~> inxi -Fzxx
System:
  Kernel: 7.0.10-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
  Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A wm: kwin_wayland dm: 1: LightDM
    note: stopped 2: SDDM note: stopped Distro: Fedora Linux 44 (KDE Plasma
    Desktop Edition)
Machine:
  Type: Desktop Mobo: ASRock model: X570 Phantom Gaming-ITX/TB3
    serial: <superuser required> Firmware: UEFI vendor: American Megatrends
    v: P2.60 date: 08/27/2020
CPU:
  Info: 8-core model: AMD Ryzen 7 3800XT bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
  Speed (MHz): avg: 2200 min/max: 2200/4723 boost: enabled cores: 1: 2200
    2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200
    11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 bogomips: 124807
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Gigabyte
    driver: nvidia v: 595.71.05 arch: Turing pcie: speed: 5 GT/s lanes: 16
    ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1 bus-ID: 2a:00.0
    chip-ID: 10de:1e84
  Device-2: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6.4.1:6 chip-ID: 0c45:6367
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
    gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DP-2 model: ASUS VP247 res: 1920x1080 dpi: 94
    diag: 598mm (23.5")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 595.71.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070
    SUPER/PCIe/SSE2 display-ID: :0.0
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:1e84 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: swaymsg,wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 2a:00.1 chip-ID: 10de:10f8
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 2c:00.4 chip-ID: 1022:1487
  Device-3: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6.4.1:6 chip-ID: 0c45:6367
  Device-4: Audio-Technica ATR2100x-USB Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 3-6.4.4:9 chip-ID: 0909:004d
  API: ALSA v: k7.0.10-201.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.6 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: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
    lanes: 1 bus-ID: 25:00.0 chip-ID: 8086:2723
  IF: wlp37s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 26:00.0 chip-ID: 8086:1539
  IF: enp38s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 5-2:2 chip-ID: 8087:0029
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
Drives:
  Local Storage: total: 3.19 TiB used: 492.07 GiB (15.1%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW010T8 size: 953.87 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 46.9 C
  ID-2: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Western Digital model: WD20EZRZ-00Z5HB0
    size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 952.28 GiB used: 413.35 GiB (43.4%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 731.7 MiB (75.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 952.28 GiB used: 413.35 GiB (43.4%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 59.2 C mobo: 37.6 C
  Fan Speeds (rpm): fan-1: 1133 fan-2: 1152 fan-3: 3361 fan-4: 0
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 5.74 GiB (18.4%)
  Processes: 540 Power: uptime: 35m wakeups: 0 Init: systemd v: 259
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 14
    Compilers: clang: 22.1.6 gcc: 16.1.1 Shell: fish v: 4.6.0
    running-in: konsole inxi: 3.3.40
2

Asrock shows many updates for your bios firmware, ending with this one.

image
image1138×127 19.9 KB

on this site
https://pg.asrock.com/mb/AMD/X570%20Phantom%20Gaming-ITXTB3/index.asp#BIOS

I would look at upgrading the almost 6 year old bios on that machine first.

3

Thank you for the tip on updating the BIOS. Didn’t affect my issue with plasma failing to start, but I think it might’ve helped with an werid IRQ message I’d been seeing occassionally.

Probably going to have to start checking for differences between my account and the test account that works. Is there anything outside of the home directory that’s user specific?

5

Good point.

Not that I know of, but you could compare your username and the test one in
/var/lib/AccountsService/users/

The may30.log shows a lot of segfaults, the first one being:

May 30 11:22:05 arcadia kernel: wayland-session[4443]: segfault at 7fff384fcd00 ip 000055855ce532df sp 00007fff384fcd00 error 6 in bash[382df,55855ce1b000+10a000] likely on CPU 9 (core 1, socket 0)
May 30 11:22:05 arcadia kernel: Code: 8a 48 89 5d e8 e8 a1 93 fc ff 90 f3 0f 1e fa e9 a7 fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 e5 48 81 ec 00 10 00 00 <48> 83 0c 24 00 48 83 ec 20 8b 05 4a c7 13 00 64 48 8b 14 25 28 00
May 30 11:22:05 arcadia systemd-coredump[4444]: Process 4443 (wayland-session) of user 1000 terminated abnormally with signal 11/SEGV, processing...

It shows also:

May 30 11:22:46 arcadia plasmalogin-helper[4578]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                                  Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                                  If this causes problems, reconfigure your locale. See the locale(1) manual
                                                  for more information.

Try perhaps to correct your locale in your shell profiles, or backup them and replace
them with the default files located in /etc/skel.

6

Ok, had some time today to troubleshoot further. Short version: I had mangled my path in my ~/.profile.

Found this by moving all the dot files out of my home directory, and then moving them back in a handful at a time until logging into plasma failed again.