Cela fait bien longtemps que j'ai pas trop posté pour un problème ici
Donc voilà je poste mon problème.
Je suis très surpris de mon soucis car il arrive ainsi sans manipulation extravagante ou autre un simple reboot.
J'ai un pc XFCE x64 avec luks et il ne démarre plus j'aimerais bien avoir vos avis sur la question.
inxi -F :
12System: 12Host manjaro 12Kernel 5.3.6-1-MANJARO x86_64 12bits 64 12Desktop Xfce 12Distro Manjaro Linux
12Machine: 12Type Laptop 12System FUJITSU 12product LIFEBOOK A557 12v N/A 12serial <filter>
12Mobo FUJITSU 12model FJNBB50 12v 716944-01R6909022 12serial <filter> 12UEFI FUJITSU // Insyde
12v Version 1.05 12date 09/05/2016
12Battery: 12ID-1 BAT1 12charge 24.0 Wh 12condition 42.5/48.6 Wh (88%)
12CPU: 12Topology Dual Core 12model Intel Core i5-7200U 12bits 64 12type MT MCP 12L2 cache 3072 KiB
12Speed 900 MHz 12min/max 400/3100 MHz 12Core speeds (MHz) 121 900 122 900 123 900 124 901
12Graphics: 12Device-1 Intel HD Graphics 620 12driver i915 12v kernel
12Display x11 12server X.org 1.20.5 12driver intel 12unloaded modesetting 12tty N/A
12Message Advanced graphics data unavailable for root.
12Audio: 12Device-1 Intel Sunrise Point-LP HD Audio 12driver snd_hda_intel
12Sound Server ALSA 12v k5.3.6-1-MANJARO
12Network: 12Device-1 Intel Wireless 7265 12driver iwlwifi
12IF wlp2s0 12state down 12mac <filter>
12Device-2 Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 12driver r8169
12IF enp3s0 12state down 12mac <filter>
12IF-ID-1 enp0s20f0u5 12state unknown 12speed N/A 12duplex N/A 12mac <filter>
12Drives: 12Local Storage 12total 253.26 GiB 12used 100.28 GiB (39.6%)
12ID-1 /dev/sda 12vendor Crucial 12model CT240BX500SSD1 12size 223.57 GiB
12ID-2 /dev/sdb 12type USB 12model 058f 6387 12size 29.69 GiB
12Partition: 12ID-1 / 12size 218.77 GiB 12used 100.15 GiB (45.8%) 12fs ext4 12dev /dev/dm-0
12Sensors: 12System Temperatures 12cpu 37.0 C 12mobo N/A
12Fan Speeds (RPM) N/A
12Info: 12Processes 189 12Uptime 1h 28m 12Memory 7.68 GiB 12used 1.60 GiB (20.9%)
12Client Unknown Client: systemd 12inxi 3.0.36
-- Automatic restarting of the unit NetworkManager.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 22 12:54:57 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" e>
Oct 22 12:54:57 pcp170019 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" ex>
Oct 22 12:54:57 pcp170019 systemd[1]: Stopped Network Manager.
-- Subject: A stop job for unit NetworkManager.service has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A stop job for unit NetworkManager.service has finished.
--
-- The job identifier is 1709 and the job result is done.
Oct 22 12:54:57 pcp170019 systemd[1]: NetworkManager.service: Start request repeated too quickly.
Oct 22 12:54:57 pcp170019 systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit NetworkManager.service has entered the 'failed' state with result 'exit-code'.
Oct 22 12:54:57 pcp170019 systemd[1]: Failed to start Network Manager.
-- Subject: A start job for unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A start job for unit lightdm.service has begun execution.
Oct 22 12:50:23 pcp170019 lightdm[550]: Failed to get system bus: Could not connect: No such file or directory
Oct 22 12:50:23 pcp170019 lightdm[550]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:23 pcp170019 lightdm[550]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:23 pcp170019 lightdm[550]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:23 pcp170019 lightdm[550]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:23 pcp170019 lightdm[550]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:23 pcp170019 lightdm[550]: Failed to get D-Bus connection
Oct 22 12:50:23 pcp170019 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit lightdm.service has exited.
Oct 22 12:50:23 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 22 12:50:23 pcp170019 systemd[1]: lightdm.service: Failed with result 'exit-code'.
-- The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit lightdm.service has failed
-- A start job for unit lightdm.service has finished with a failure.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
-- Automatic restarting of the unit lightdm.service has been scheduled, as the result for
-- Subject: A stop job for unit lightdm.service has finished
-- A stop job for unit lightdm.service has finished.
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Subject: A start job for unit lightdm.service has begun execution
-- A start job for unit lightdm.service has begun execution.
Oct 22 12:50:25 pcp170019 lightdm[592]: Failed to get system bus: Could not connect: No such file or directory
Oct 22 12:50:25 pcp170019 lightdm[592]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[592]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[592]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[592]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[592]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[592]: Failed to get D-Bus connection
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit lightdm.service has exited.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Failed with result 'exit-code'.
-- The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit lightdm.service has failed
-- A start job for unit lightdm.service has finished with a failure.
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
-- Automatic restarting of the unit lightdm.service has been scheduled, as the result for
-- Subject: A stop job for unit lightdm.service has finished
-- A stop job for unit lightdm.service has finished.
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Subject: A start job for unit lightdm.service has begun execution
-- A start job for unit lightdm.service has begun execution.
Oct 22 12:50:25 pcp170019 lightdm[616]: Failed to get system bus: Could not connect: No such file or directory
Oct 22 12:50:25 pcp170019 lightdm[616]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[616]: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[616]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[616]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[616]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 22 12:50:25 pcp170019 lightdm[616]: Failed to get D-Bus connection
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit lightdm.service has exited.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Failed with result 'exit-code'.
-- The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit lightdm.service has failed
-- A start job for unit lightdm.service has finished with a failure.
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
-- Automatic restarting of the unit lightdm.service has been scheduled, as the result for
-- Subject: A stop job for unit lightdm.service has finished
-- A stop job for unit lightdm.service has finished.
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 22 12:50:25 pcp170019 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Start request repeated too quickly.
Oct 22 12:50:25 pcp170019 systemd[1]: lightdm.service: Failed with result 'exit-code'.
-- The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit lightdm.service has failed
-- A start job for unit lightdm.service has finished with a failure.
Voici aussi le post sur l'inter : https://forum.manjaro.org/t/fujitsu-lif ... r-restart/
Si vous avez des idées hésitez pas.