staudi
(Staudi)
November 8, 2024, 9:59am
1
Hi since I updated my Fedora 40 KDE system to Fedora 41 I have the issue that after I login in the sddm and KDE is already started another tty is created where the sddm is displayed and it prompts me to login again. I also see that the splash screen does not get displayed for 30s or so after logging in through sddm (I do not know if that is relevant). I would apreciate getting help debugging this behaviour as I am relatively new to Linux and do not know how to.
System info:
output journalctl -kab
journalctl -kab
Nov 08 11:35:23 sebi-fedora kernel: Linux version 6.11.5-300.fc41.x86_64 (mockbuild@a0564de4e00d4277aa3a51770ad85255) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.43.1-2.fc41) #1 SMP PREEMPT_DYNAMIC Tue Oct 22 20:11:15 UTC 2024
Nov 08 11:35:23 sebi-fedora kernel: Command line: BOOT_IMAGE=(hd3,gpt2)/vmlinuz-6.11.5-300.fc41.x86_64 root=UUID=285c2020-8575-4cd5-a4f8-b786de603277 ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rd.luks.uuid=luks-94e60366-4266-4e58-bc40-222483cdb817 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau amd_iommu=on iommu=pt kvm.ignore_msrs=1 vfio-pci.ids=10de:1e84,10de:10f8,10de:1ad8,10de:1ad9
Nov 08 11:35:23 sebi-fedora kernel: BIOS-provided physical RAM map:
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d1efff] usable
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x0000000009d1f000-0x0000000009ffffff] reserved
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a210fff] ACPI NVS
Nov 08 11:35:23 sebi-fedora kernel: BIOS-e820: [mem 0x000000000a211000-0x00000000c3278fff] usable
This file has been truncated. show original
Edit:
Additional behaviour I have watched. It seems like this behaviour only occures on the first boot of the day as after a reboot the tty does not open.
barryascott
(Barry A Scott)
November 8, 2024, 10:22am
2
Do you have the rpmfusion nvidia drivers installed?
What is the output of `inxi -Fzxx’?
You can login on a console, type ctrl-alt-f3 to get a login prompt.
staudi
(Staudi)
November 8, 2024, 10:55am
3
Yes I have the nvidia rpmfusion drivers installed.
Here is the output from inxi -Fzxx
if the kernel version and KDE plasma version do not match with the system information above that is because I tried updating to the latest version
System:
Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 41 (KDE Plasma)
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 4408
date: 10/27/2022
CPU:
Info: 8-core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 550 min/max: 550/4426 boost: enabled cores: 1: 550
2: 550 3: 550 4: 550 5: 550 6: 550 7: 550 8: 550 9: 550 10: 550 11: 550
12: 550 13: 550 14: 550 15: 550 16: 550 bogomips: 114972
Flags: 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: ASUSTeK
driver: nvidia v: 560.35.03 arch: Turing pcie: speed: 8 GT/s lanes: 16
ports: active: none off: DP-2,HDMI-A-2 empty: DP-1,HDMI-A-1,Unknown-2
bus-ID: 0b:00.0 chip-ID: 10de:1e84
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: N/A d-rect: 4480x2520 display-ID: 0
Monitor-1: DP-2 pos: top-right res: 2560x1440 size: N/A
Monitor-2: HDMI-A-2 pos: bottom-l res: 1920x1080 size: N/A
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: 560.35.03
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070
SUPER/PCIe/SSE2 display-ID: :0.0
API: Vulkan v: 1.3.296 surfaces: xcb,xlib,wayland device: 0
type: discrete-gpu driver: N/A device-ID: 10de:1e84 device: 1 type: cpu
driver: N/A device-ID: 10005:0000
Audio:
Device-1: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 10de:10f8
Device-2: Advanced Micro Devices [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
Device-3: SteelSeries ApS Arctis 7+
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 bus-ID: 3-3:2 chip-ID: 1038:220e
Device-4: C-Media USB Advanced Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 bus-ID: 7-1.1:5 chip-ID: 0d8c:01c2
Device-5: C-Media Q9-1 driver: hid-generic,snd-usb-audio,usbhid type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 7-4:4 chip-ID: 0d8c:0135
API: ALSA v: k6.11.6-300.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.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: 05:00.0 chip-ID: 8086:2723
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0 chip-ID: 10ec:8125
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0 chip-ID: 8086:1539
IF: enp7s0 state: down mac: <filter>
IF-ID-1: br-290a9ea3715f state: down mac: <filter>
IF-ID-2: br-e1b747f0ef17 state: down mac: <filter>
IF-ID-3: docker0 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 bus-ID: 1-1:2
chip-ID: 0a12:0001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6
Device-2: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-6:4 chip-ID: 8087:0029
Report: ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 5.2 lmp-v: 11
Drives:
Local Storage: total: 6.37 TiB used: 441.55 GiB (6.8%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 38.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 38.9 C
ID-3: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
speed: 6.0 Gb/s serial: <filter>
ID-4: /dev/sdb vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 1.82 TiB used: 440.99 GiB (23.7%) fs: btrfs dev: /dev/dm-0
mapped: luks-94e60366-4266-4e58-bc40-222483cdb817
ID-2: /boot size: 973.4 MiB used: 461.7 MiB (47.4%) 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: 1.82 TiB used: 440.99 GiB (23.7%) fs: btrfs
dev: /dev/dm-0 mapped: luks-94e60366-4266-4e58-bc40-222483cdb817
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.0 C mobo: 34.0 C
Fan Speeds (rpm): fan-2: 1587 fan-3: 1634 fan-4: 1566 fan-5: 1260
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 4.1 GiB (13.1%)
Processes: 619 Power: uptime: 34m wakeups: 1 Init: systemd v: 256
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 7 Compilers:
clang: 17 alt: 18 gcc: 14.2.1 Shell: fish v: 3.7.0 running-in: konsole
inxi: 3.3.36
barryascott
(Barry A Scott)
November 8, 2024, 10:49pm
4
The spec of your system gives me no concerns.
After you get returned to the login screen note the time and then look at the system journal leading up to that time for errors.
You may also need to check the user journal for the same time as the error may not be in the system journal.
staudi
(Staudi)
November 12, 2024, 4:24pm
5
I am closing this as it seems updates in last few days fixed this issue for me