staging.inyokaproject.org

themroc schrieb:

Ach die APCI Fehler beim booten tauschen seit kurzem auf.

Seit dem Kernel-Update in dem solche Meldungen nicht mehr unterdrückt werden, ja. Wenn es exakt die gleiche Meldung ist, könnt ihr alle testweise die Bootoption libata.noacpi=1 probieren. Aber: das deaktiviert acpi für alles an diesem Bus!

Ansonsten bitte genau darauf achten, wessen Symbole nicht gelesen werden können (das meiste sind eh Folgefehler, der erste ist wichtig).

Mir ist es vorgestern wieder passiert, nachdem ich eine Einstellung für das 7.1 Onboard Audio geändert hatte. Wie es aussieht, war das kein "Abmelden ohne Nachfragen", sondern es hat die komplette Sitzung gerissen:

:~$ ll /var/crash/
insgesamt 42M
drwxrwsrwt  2 root whoopsie 4,0K Jul 29 22:00 ./
drwxr-xr-x 14 root root     4,0K Apr 19 12:10 ../
-rw-r-----  1 dide whoopsie 8,2M Jul 28 16:03 _usr_bin_kwin_x11.1000.crash
-rw-r-----  1 dide whoopsie  25M Jul 28 16:03 _usr_bin_plasmashell.1000.crash
-rw-r-----  1 dide whoopsie 966K Jul 28 16:03 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash
-rw-r-----  1 root whoopsie 8,5M Jul 28 16:03 _usr_lib_xorg_Xorg.0.crash

Mein "Eingebautes Tongerät" (Analog Devices AD1988 7.1 Dolby Surround) war falsch konfiguriert - ich hatte die Desktop-Lautsprecher an der "Side"-Buchse angeschlossen und das Profil auf "Analog Stereo-Ausgabe" gesetzt. Seitdem ich das korrigiert habe, bin ich nicht mehr rausgeflogen.

Interessant. Das sollte allerdings nicht die ganze X-Session zum Absturz bringen. Ist das reproduzierbar, wenn du wieder umstöpselst? Gibt es entsprechende Infos im journalctl? Da müsste ja dann vor dem GUI-crash Alsa, PulseAudio, Pipewire, Jack, whatever du als Audiosystem hast ein Problem haben, sprich abstürzen. Ich würde mit Kernelmeldungen anfangen (Alsa).

Laut journalctl ist zur fraglichen Zeit folgendes passiert:

Jul 28 16:03:33 studio1 acpid[773]: client 1159[0:0] has disconnected
Jul 28 16:03:34 studio1 systemd[1]: Started Getty on tty2.
Jul 28 16:03:34 studio1 systemd[1]: Started crash report submission.
Jul 28 16:03:34 studio1 whoopsie[6216]: [16:03:34] Using lock path: /var/lock/whoopsie/lock
Jul 28 16:03:34 studio1 systemd[1]: whoopsie.service: Deactivated successfully.
Jul 28 16:03:35 studio1 systemd[1]: Started crash report submission.
Jul 28 16:03:35 studio1 kscreen_backend_launcher[1727]: The X11 connection broke (error 1). Did the X11 server die?
Jul 28 16:03:36 studio1 kglobalaccel5[1577]: The X11 connection broke (error 1). Did the X11 server die?
Jul 28 16:03:36 studio1 kglobalaccel5[1577]: The X11 connection broke: I/O error (code 1)
Jul 28 16:03:36 studio1 kglobalaccel5[1577]: X connection to :0 broken (explicit kill or server shutdown).
Jul 28 16:03:36 studio1 xdg-desktop-portal-kde[1966]: The X11 connection broke (error 1). Did the X11 server die?
Jul 28 16:03:36 studio1 polkitd(authority=local)[807]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.67, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from bus)
Jul 28 16:03:36 studio1 kactivitymanagerd[1630]: The X11 connection broke (error 1). Did the X11 server die?
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kactivitymanagerd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 16:03:36 studio1 sddm-helper[1355]: pam_unix(sddm:session): session closed for user dide
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Jul 28 16:03:36 studio1 sddm-helper[1355]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 16:03:36 studio1 sddm-helper[1355]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kscreen.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 16:03:36 studio1 systemd[1357]: plasma-kscreen.service: Failed with result 'exit-code'.
Jul 28 16:03:36 studio1 systemd[1357]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 16:03:36 studio1 systemd[1357]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Jul 28 16:03:36 studio1 systemd[1357]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 16:03:36 studio1 systemd[1357]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Jul 28 16:03:36 studio1 systemd[1357]: app-claws\x2dmail-e89466b275974896892f7f14f17341d4.scope: Consumed 1.908s CPU time.
Jul 28 16:03:36 studio1 systemd[1357]: snap.firefox.firefox.96f24c5f-62ed-4236-b80b-2ca95c41872a.scope: Consumed 4min 14.094s CPU time.
Jul 28 16:03:36 studio1 sddm-helper[1355]: [PAM] Closing session
Jul 28 16:03:36 studio1 systemd[1357]: app-systemsettings-2e26b83e39004597a7aa26410cbf2144.scope: Consumed 7.650s CPU time.
Jul 28 16:03:36 studio1 sddm-helper[1355]: [PAM] Ended.
Jul 28 16:03:36 studio1 sddm[1093]: Auth: sddm-helper exited successfully
Jul 28 16:03:36 studio1 sddm[1093]: Socket server stopping...
Jul 28 16:03:36 studio1 sddm[1093]: Socket server stopped.
Jul 28 16:03:36 studio1 sddm[1093]: Display server stopping...
Jul 28 16:03:36 studio1 systemd-logind[850]: Session 3 logged out. Waiting for processes to exit.

Der Ausschnitt zeigt, dass es wohl den XServer gerissen hat. Da lässt sich von Plasma aus wenig machen (außer auf Wayland wechsen). Falls es einen systemd-coredump gibt (meist /var/log/crash), kannst du mit coredumpctl info, bzw. coredumctl gdb arbeiten. Ohne ein solches file müsstest du X so debuggen. Da X ein Netzwerkprotokoll ist, lässt sich das gut über nen zweiten Rechner prüfen.→ https://x.org/wiki/Development/Documentation/ServerDebugging/
Der Nachteil ist, das es erst wieder crashen muss und die Oberfläche wohl sehr langsam sein dürfte. War zumindest früher so.

Am 8. September ist es wieder passiert. Und nach der erneuten Anmeldung gleich nochmal.

Nach dem Reboot lief Plasma wieder stabil. Da bis dahin Ruhe war, habe ich einen Verdacht: Ich hatte mit Muon das Paket libreoffice-java-common nachinstalliert und anschließend überprüft, ob LibreOffice das installierte default-jre findet.

Kann es sein, daß der Gebrauch von Muon KDE Plasma instabil macht?

seriousness schrieb:

Kann es sein, daß der Gebrauch von Muon KDE Plasma instabil macht?

KANN sein.

journalctl -b -1 -p warning
# bzw.
journalctl -b -2 -p warning

für den letzten/vorletzten Bootvorgang bei dem der Crash auftrat.

Eigentlich war nur dieser Boot betroffen, bei dem mir zweimal die Sitzung abgeschmiert ist:

dide@studio1:~$ journalctl -b -5 -p warning
Sep 08 12:27:08 studio1 kernel: DMAR-IR: This system BIOS has enabled interrupt remapping
                                on a chipset that contains an erratum making that
                                feature unstable.  To maintain system stability
                                interrupt remapping is being disabled.  Please
                                contact your BIOS vendor for an update
Sep 08 12:27:08 studio1 kernel: core: CPUID marked event: 'bus cycles' unavailable
Sep 08 12:27:08 studio1 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln>
Sep 08 12:27:08 studio1 kernel:  #5 #6 #7
Sep 08 12:27:08 studio1 kernel: tpm tpm0: tpm_try_transmit: send(): error -62
Sep 08 12:27:08 studio1 kernel: tpm tpm0: Operation Timed out
Sep 08 12:27:08 studio1 kernel: tpm tpm0: tpm_try_transmit: send(): error -62
Sep 08 12:27:08 studio1 kernel: i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
Sep 08 12:27:08 studio1 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the>
Sep 08 12:27:08 studio1 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 08 12:27:08 studio1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ima: Error Communicating to TPM chip
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x00>
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00>
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x000000000000118C-0x00>
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001198-0x00>
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00>
Sep 08 12:27:08 studio1 kernel: ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00>
Sep 08 12:27:08 studio1 kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 08 12:27:08 studio1 kernel: i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD
Sep 08 12:27:08 studio1 kernel: mtd device must be supplied (device name is empty)
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.0: can't derive routing for PCI INT A
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.0: PCI INT A: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.1: can't derive routing for PCI INT B
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.1: PCI INT B: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.2: can't derive routing for PCI INT C
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.2: PCI INT C: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.3: can't derive routing for PCI INT D
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.3: PCI INT D: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.4: can't derive routing for PCI INT A
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.4: PCI INT A: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.5: can't derive routing for PCI INT B
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.5: PCI INT B: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.6: can't derive routing for PCI INT C
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.6: PCI INT C: no GSI
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.7: can't derive routing for PCI INT D
Sep 08 12:27:19 studio1 kernel: ioatdma 0000:00:16.7: PCI INT D: no GSI
Sep 08 12:27:19 studio1 kernel: kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
Sep 08 12:27:19 studio1 kernel: nvidia: loading out-of-tree module taints kernel.
Sep 08 12:27:19 studio1 kernel: nvidia: module license 'NVIDIA' taints kernel.
Sep 08 12:27:19 studio1 kernel: Disabling lock debugging due to kernel taint
Sep 08 12:27:19 studio1 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 UTC 2022 (using threaded interrupts)
Sep 08 12:27:19 studio1 kernel: mtd device must be supplied (device name is empty)
Sep 08 12:27:19 studio1 kernel: mtd device must be supplied (device name is empty)
Sep 08 12:27:19 studio1 kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d00>
Sep 08 12:27:19 studio1 kernel: caller os_map_kernel_space.part.0+0x10d/0x160 [nvidia] mapping multiple BARs
Sep 08 12:27:19 studio1 kernel: mtd device must be supplied (device name is empty)
Sep 08 12:27:12 studio1 systemd-udevd[469]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
Sep 08 12:27:12 studio1 systemd-udevd[475]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
Sep 08 12:27:12 studio1 systemd-udevd[482]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Sep 08 12:27:13 studio1 systemd-udevd[457]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code >
Sep 08 12:27:13 studio1 systemd-udevd[476]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code >
Sep 08 12:27:16 studio1 systemd-udevd[474]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code >
Sep 08 12:27:17 studio1 systemd-udevd[477]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code >
Sep 08 12:27:27 studio1 thermald[787]: NO RAPL sysfs present
Sep 08 12:27:28 studio1 udisksd[804]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Sep 08 12:27:28 studio1 udisksd[804]: Failed to load the 'mdraid' libblockdev plugin
Sep 08 12:27:36 studio1 kernel: kauditd_printk_skb: 21 callbacks suppressed
Sep 08 12:27:36 studio1 systemd[1]: kerneloops.service: Found left-over process 1162 (kerneloops) in control group while starting unit. Ignoring.
Sep 08 12:27:36 studio1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 08 12:27:36 studio1 avahi-daemon[752]: Host name conflict, retrying with studio1-2
Sep 08 12:27:40 studio1 kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d00>
Sep 08 12:27:40 studio1 kernel: caller os_map_kernel_space.part.0+0x10d/0x160 [nvidia] mapping multiple BARs
Sep 08 12:27:46 studio1 sddm-greeter[1227]: QFont::fromString: Invalid description '(empty)'
Sep 08 12:27:49 studio1 sddm-greeter[1227]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7fffa20114c0), parent's thread is QThread(0x55ce9549c970), current thread>
Sep 08 12:27:49 studio1 sddm-greeter[1227]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7fffa20114c0), parent's thread is QThread(0x55ce9549c970), current thread>
Sep 08 12:27:48 studio1 sddm-greeter[1227]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7fffa20114c0), parent's thread is QThread(0x55ce9549c970), current thread>
Sep 08 12:27:48 studio1 sddm-greeter[1227]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Sep 08 12:28:11 studio1 pulseaudio[1226]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes>
Sep 08 12:34:41 studio1 sddm-helper[1341]: gkr-pam: unable to locate daemon control file
Sep 08 12:34:42 studio1 pipewire[1352]: mod.rt: could not set nice-level to -11: Keine Berechtigung
Sep 08 12:34:44 studio1 systemd[1343]: fluidsynth.service: Failed with result 'protocol'.
Sep 08 12:34:44 studio1 systemd[1343]: Failed to start FluidSynth Daemon.
Sep 08 12:34:53 studio1 org.kde.powerdevil.backlighthelper[1690]: org.kde.powerdevil: no kernel backlight interface found
Sep 08 12:34:57 studio1 systemd[1]: user@120.service: State 'stop-sigterm' timed out. Killing.
Sep 08 12:34:57 studio1 systemd[1]: user@120.service: Main process exited, code=killed, status=9/KILL
Sep 08 12:34:57 studio1 systemd[1]: user@120.service: Failed with result 'timeout'.
Sep 08 12:35:06 studio1 org.jackaudio.service[1735]: no message buffer overruns
Sep 08 12:35:06 studio1 org.jackaudio.service[1735]: no message buffer overruns
Sep 08 12:35:07 studio1 org.jackaudio.service[1735]: no message buffer overruns
Sep 08 12:35:08 studio1 pulseaudio[1354]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes>
Sep 08 12:35:09 studio1 systemd[1343]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Sep 08 12:35:09 studio1 systemd[1343]: pulseaudio.service: Failed with result 'signal'.
Sep 08 12:35:09 studio1 org.jackaudio.service[1745]: no message buffer overruns
Sep 08 12:35:09 studio1 org.jackaudio.service[1745]: no message buffer overruns
Sep 08 12:35:09 studio1 org.jackaudio.service[1745]: no message buffer overruns
Sep 08 12:35:09 studio1 pulseaudio[1744]: Stale PID file, overwriting.
Sep 08 12:35:34 studio1 pulseaudio[1744]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes>
Sep 08 12:35:51 studio1 io.snapcraft.Settings[2086]: userd.go:93: Starting snap userd
Sep 08 12:40:09 studio1 org.kubuntu.qaptworker3[4062]: locked? true
Sep 08 12:40:09 studio1 org.kubuntu.qaptworker3[4062]: locked? true
Sep 08 12:40:09 studio1 org.kubuntu.qaptworker3[4062]: locked? true
Sep 08 12:40:57 studio1 kernel: kauditd_printk_skb: 10 callbacks suppressed
Sep 08 12:44:40 studio1 kernel: kauditd_printk_skb: 2 callbacks suppressed
Sep 08 12:44:47 studio1 kernel: kauditd_printk_skb: 206 callbacks suppressed
Sep 08 12:45:11 studio1 kernel: kauditd_printk_skb: 980 callbacks suppressed
Sep 08 16:35:09 studio1 systemd[1343]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Sep 08 16:35:09 studio1 systemd[1343]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Sep 08 16:35:09 studio1 systemd[1343]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
Sep 08 16:35:09 studio1 systemd[1343]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Sep 08 16:35:10 studio1 sddm[1067]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Sep 08 16:35:11 studio1 sddm-greeter[9224]: QFont::fromString: Invalid description '(empty)'
Sep 08 16:35:11 studio1 sddm-greeter[9224]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7ffd1ab93260), parent's thread is QThread(0x56454c360970), current thread>
Sep 08 16:35:11 studio1 sddm-greeter[9224]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7ffd1ab93260), parent's thread is QThread(0x56454c360970), current thread>
Sep 08 16:35:11 studio1 sddm-greeter[9224]: QObject: Cannot create children for a parent that is in a different thread.
                                            (Parent is QGuiApplication(0x7ffd1ab93260), parent's thread is QThread(0x56454c360970), current thread>
Sep 08 16:35:11 studio1 sddm-greeter[9224]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Sep 08 16:35:16 studio1 systemd[1]: whoopsie.service: Start request repeated too quickly.
Sep 08 16:35:16 studio1 systemd[1]: whoopsie.service: Failed with result 'start-limit-hit'.
Sep 08 16:35:16 studio1 systemd[1]: Failed to start crash report submission.
Sep 08 16:35:16 studio1 systemd[1]: whoopsie.path: Failed with result 'unit-start-limit-hit'.
Sep 08 16:35:26 studio1 sddm-helper[9294]: gkr-pam: unable to locate daemon control file
Sep 08 16:35:28 studio1 org.kde.powerdevil.backlighthelper[9600]: org.kde.powerdevil: no kernel backlight interface found
Sep 08 16:35:36 studio1 pulseaudio[9223]: Lost I/O connection in module "module-gsettings"
Sep 08 16:35:36 studio1 pulseaudio[9635]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':>
Sep 08 16:35:38 studio1 org.jackaudio.service[9675]: no message buffer overruns
Sep 08 16:35:38 studio1 org.jackaudio.service[9675]: no message buffer overruns
Sep 08 16:35:38 studio1 org.jackaudio.service[9675]: no message buffer overruns
Sep 08 16:35:40 studio1 systemd[1343]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Sep 08 16:35:40 studio1 systemd[1343]: pulseaudio.service: Failed with result 'signal'.
Sep 08 16:35:40 studio1 org.jackaudio.service[9685]: no message buffer overruns
Sep 08 16:35:40 studio1 org.jackaudio.service[9685]: no message buffer overruns
Sep 08 16:35:40 studio1 org.jackaudio.service[9685]: no message buffer overruns
Sep 08 16:35:40 studio1 pulseaudio[9686]: Stale PID file, overwriting.
Sep 08 16:35:41 studio1 systemd[1]: user@120.service: State 'stop-sigterm' timed out. Killing.
Sep 08 16:35:41 studio1 systemd[1]: user@120.service: Main process exited, code=killed, status=9/KILL
Sep 08 16:35:41 studio1 systemd[1]: user@120.service: Failed with result 'timeout'.
Sep 08 16:36:06 studio1 pulseaudio[9686]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes>
Sep 08 16:36:41 studio1 systemd[1343]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
Sep 08 16:36:41 studio1 systemd[1343]: plasma-kscreen.service: Failed with result 'exit-code'.
Sep 08 16:36:41 studio1 systemd[1343]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Sep 08 16:36:42 studio1 sddm-greeter[10444]: QFont::fromString: Invalid description '(empty)'
Sep 08 16:36:42 studio1 sddm-greeter[10444]: QObject: Cannot create children for a parent that is in a different thread.
                                             (Parent is QGuiApplication(0x7ffc20551640), parent's thread is QThread(0x55b0aa8b1970), current threa>
Sep 08 16:36:42 studio1 sddm-greeter[10444]: QObject: Cannot create children for a parent that is in a different thread.
                                             (Parent is QGuiApplication(0x7ffc20551640), parent's thread is QThread(0x55b0aa8b1970), current threa>
Sep 08 16:36:42 studio1 sddm-greeter[10444]: QObject: Cannot create children for a parent that is in a different thread.
                                             (Parent is QGuiApplication(0x7ffc20551640), parent's thread is QThread(0x55b0aa8b1970), current threa>
Sep 08 16:36:42 studio1 sddm-greeter[10444]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Sep 08 16:37:08 studio1 pulseaudio[10440]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible cause>
Sep 08 16:37:18 studio1 sddm[1067]: Error from greeter session: "Process crashed"
Sep 08 16:37:18 studio1 sddm[1067]: Auth: sddm-helper crashed (exit code 15)
Sep 08 16:37:18 studio1 sddm[1067]: Error from greeter session: "Process crashed"
Sep 08 16:37:18 studio1 sddm[1067]: Auth: sddm-helper exited with 15
Sep 08 16:37:18 studio1 sddm[1067]: Signal received: SIGTERM
Sep 08 16:37:18 studio1 systemd[1343]: xdg-permission-store.service: Failed with result 'exit-code'.
Sep 08 16:37:18 studio1 pulseaudio[10440]: Lost I/O connection in module "module-gsettings"
Sep 08 16:37:18 studio1 pulseaudio[10440]: Error opening PCM device front:0: Datei oder Verzeichnis nicht gefunden
Sep 08 16:37:18 studio1 pulseaudio[10440]: Error opening PCM device iec958:0: Datei oder Verzeichnis nicht gefunden
Sep 08 16:37:18 studio1 pulseaudio[10440]: Error opening PCM device front:2: Datei oder Verzeichnis nicht gefunden
Sep 08 16:37:18 studio1 systemd[1343]: xdg-document-portal.service: Failed with result 'exit-code'.
Sep 08 16:37:24 studio1 systemd[1]: user@120.service: State 'stop-sigterm' timed out. Killing.
Sep 08 16:37:24 studio1 systemd[1]: user@120.service: Main process exited, code=killed, status=9/KILL
Sep 08 16:37:24 studio1 systemd[1]: user@120.service: Failed with result 'timeout'.
lines 128-177/177 (END)

seriousness schrieb:

Sep 08 12:27:08 studio1 kernel: DMAR-IR: This system BIOS has enabled interrupt remapping

Dachte dieser Intel-Bug wäre seit Äonen behoben (> 2-3 Jahre). Prüfe mal, ob es ein UEFI-Update gibt und ob es darin die Möglichkeit gibt IRQ-remapping zu (de-)aktivieren. Ansonsten per Bootoption intremap=off erzwingen. Update wäre natürlich besser, das könnte auch die TPM-Fehler beheben.

EISA-Meldungen („Cannot allocate resource for EISA“) sind auch seltsam in der heutigen Zeit. Kann ich so ausm Stehgreif auch nichts mit anfangen. Was ist das für ein Gerät?

1001286 ist auch an Bord 😉 (sollte mit einem aktuellen Kernel aber behoben sein).

Plasma selbst schweigt sich ziemlich aus mit „Failed with result 'exit-code'.“ Allerdings sehe ich da (mal wieder) xdg-desktop-portal-{gtk,kde}.service. Das schmiert offenbar öfter ab, in die Materie bin ich aber auch noch nicht eingetaucht. Daneben scheint es noch einen Konflikt zwischen PulseAudio, Jack und PipeWire zu geben. Das kann immer etwas tricky sein. In dessen Folge schmiert sddm-helper ab, was dazu führen dürfte, das die Session beendet wird. Da kann man dir in Multimedia vielleicht mit helfen.

Die Abstürze sind seltener geworden, aber nicht ganz behoben. Dieses Mal hat es "nur" kwin gerissen. Das erste Event laut journalctl ist stets

Nov 29 16:04:07 studio1 acpid[762]: client 1196[0:0] has disconnected

Auslöser ist immer das Ändern der Lautstärke mit der Tastatur. Zu diesem Thema habe ich Bugreports gefunden, aber noch keine Lösung.

seriousness schrieb:

Auslöser ist immer das Ändern der Lautstärke mit der Tastatur. Zu diesem Thema habe ich Bugreports gefunden, aber noch keine Lösung.

Ich habe das doch tatsächlich auch ein paarmal gehabt, damals mit Jammy Jellyfish, aber nur dann, wenn ich die Sondertasten auf der Tastatur nutzte, was ich über Jahrzehnte sonst nicht tat und erst auf die Idee kam zu nutzen, als mein alter Bluetooth Kopfhörer zerbröselte, so dass jeder Griff nach den Lautstärketasten zum auf dem Kopf balancierten zerbröselnden Gebilde die Gefahr brachte, dass das Ding noch gänzlich zerfällt. Es war mir dann aber unklar, ob nicht auch der alte Bluetoothkopfhörer der Fehlerauslöser hätte sein können.

Mit Kinetik Kudu passiert das nun nicht mehr, dort ist nun Pipewire der Server. Und beim Discounter gab es später dann auch gerade passend neue Bluetoothkopfhörer im Angebot, die mit dem Kinetic Kudu fein funktionieren. 👍