You are not logged in.
Hello everyone,
I am under Arch Wayland-Hyprlan , since a recent update at boot time and before having my sddm connection console, I get the following message on my console several times
failed to start remount root and kernel file system
for info my inxi
CPU: 8-core AMD Ryzen 7 5700U with Radeon Graphics (-MT MCP-)
speed/min/max: 2624/400/4372 MHz Kernel: 6.7.1-zen1-1-zen x86_64 Up: 9m
Mem: 6.96/38.5 GiB (18.1%) Storage: 1.82 TiB (44.6% used)
Procs: 414 Shell: fish inxi: 3.3.31Then when I connect, I have a hyprlan crash and I systematically return to my login page
Result of the boot log `journalctl -p 3 -xb`; see the line Process 1705 (Hyprland) of user 1000 dumped core..
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: __common_interrupt: 0.110 No irq handler for vector
févr. 01 10:49:20 HashPlus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P000 (20230628/dspkginit-438)
févr. 01 10:49:25 HashPlus kernel: Error: Driver 'rtw89_8852ae' is already registered, aborting...
févr. 01 10:49:28 HashPlus bluetoothd[799]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
févr. 01 10:49:29 HashPlus kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
févr. 01 10:49:29 HashPlus kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
févr. 01 10:49:31 HashPlus dbus-broker-launch[1137]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
févr. 01 10:49:31 HashPlus dbus-broker-launch[1137]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
févr. 01 10:49:36 HashPlus sddm-helper[1614]: gkr-pam: unable to locate daemon control file
févr. 01 10:49:37 HashPlus dbus-broker-launch[1655]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
févr. 01 10:49:37 HashPlus dbus-broker-launch[1655]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
févr. 01 10:49:37 HashPlus systemd-coredump[1868]: Process 1705 (Hyprland) of user 1000 dumped core.
Stack trace of thread 1705:
#0 0x0000756f506ac83c n/a (libc.so.6 + 0x8a83c)
#1 0x0000756f5065c668 raise (libc.so.6 + 0x3a668)
#2 0x0000756f506444b8 abort (libc.so.6 + 0x224b8)
#3 0x00005fce10969c96 _Z25handleUnrecoverableSignali (Hyprland + 0xcec96)
#4 0x0000756f5065c710 n/a (libc.so.6 + 0x3a710)
#5 0x0000756f506ac83c n/a (libc.so.6 + 0x8a83c)
#6 0x0000756f5065c668 raise (libc.so.6 + 0x3a668)
#7 0x0000756f506444b8 abort (libc.so.6 + 0x224b8)
#8 0x0000756f5089ca6f _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x9ca6f)
#9 0x0000756f508b011c _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xb011c)
#10 0x0000756f508b0189 _ZSt9terminatev (libstdc++.so.6 + 0xb0189)
#11 0x0000756f508b03ed __cxa_throw (libstdc++.so.6 + 0xb03ed)
#12 0x00005fce109286cd _Z10throwErrorRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE.cold (Hyprland + 0x8d6cd)
#13 0x00005fce1097e74d _ZN11CCompositor10initServerEv (Hyprland + 0xe374d)
#14 0x00005fce10953be5 main (Hyprland + 0xb8be5)
#15 0x0000756f50645cd0 n/a (libc.so.6 + 0x23cd0)
#16 0x0000756f50645d8a __libc_start_main (libc.so.6 + 0x23d8a)
#17 0x00005fce10969b15 _start (Hyprland + 0xceb15)
Stack trace of thread 1800:
#0 0x0000756f506a74ae n/a (libc.so.6 + 0x854ae)
#1 0x0000756f506a9d40 pthread_cond_wait (libc.so.6 + 0x87d40)
#2 0x0000756f508d9e11 __gthread_cond_wait (libstdc++.so.6 + 0xd9e11)
#3 0x00005fce10a67c3d _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJZN9CWatchdogC4EvEUlvE_EEEEE6_M_runEv (Hyprland + 0x1ccc3d)
#4 0x0000756f508e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#5 0x0000756f506aa9eb n/a (libc.so.6 + 0x889eb)
#6 0x0000756f5072e8ac n/a (libc.so.6 + 0x10c8ac)
ELF object binary architecture: AMD x86-64
░░ Subject: Le processus 1705 (Hyprland) a généré un fichier « core »
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Le processus 1705 (Hyprland) a planté et généré un fichier « core ».
░░
░░ Cela indique généralement une erreur de programmation dans le programme
░░ incriminé, et cela devrait être notifié à son concepteur comme un défaut (bug).
févr. 01 10:49:53 HashPlus dbus-broker-launch[2606]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
févr. 01 10:49:53 HashPlus dbus-broker-launch[2606]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.OK, I was able to restart from an earlier btrfs snapshot, but every time I perform an update I have this problem on reboot.
Any ideas to help me track down what's causing this, is there already a patch to fix it?
Thanks !
Offline