Problèmes et questions sur les environnements graphiques et les applications.
Répondre

Fujitsu Lifebook A557 ne démarre plus.

#1Messageil y a 4 ans

Bonjour,

Cela fait bien longtemps que j'ai pas trop posté pour un problème ici :D
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 
Erreur networkmanager :

-- 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
-- 
Erreur lightdm :

-- 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.

Fujitsu Lifebook A557 ne démarre plus.

#2Messageil y a 4 ans

bonjour

as tu été voir dans ce cas dans la log journal ?

sudo journalctl -b -p 4
je n'ai pas pour Xfce dbus-x11 installé après vérification en local

Fujitsu Lifebook A557 ne démarre plus.

#3Messageil y a 4 ans

Bonjour.
J'essayerais en chroot pacman -Syyuu && systemctl disable lightdm.service et au reboot après connexion en TTY, startxfce4.
Ça permettra de voir si c'est lié à la pile graphique ou à lightdm.

Fujitsu Lifebook A557 ne démarre plus.

#4Messageil y a 4 ans

Ok je vais tenté ça.
J'ai justement pensé que c'était dbus qui planté donc je les remplacé par dbus-x11 mais cela ne rien changé.
J'ai donc même tenté de passer en unstable mais ça na rien changé non plus.
J'ai vérifié j'ai la toute dernière version de dbus-x11.

Ok ça fonctionne :

j'ai désactivé lightdm et networkmanager et j'ai lancé : startxfce4

Fujitsu Lifebook A557 ne démarre plus.

#5Messageil y a 4 ans

OK voici mon retour de sudo journalctl -b -p 4

-- Logs begin at Tue 2019-05-07 10:41:05 CEST, end at Wed 2019-10-23 09:51:09 CEST. --
oct. 23 09:45:40 pcp170019 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
oct. 23 09:45:40 pcp170019 kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
oct. 23 09:45:40 pcp170019 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admi>
oct. 23 09:45:40 pcp170019 kernel:  #3
oct. 23 09:45:40 pcp170019 kernel: platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
oct. 23 09:45:40 pcp170019 kernel: acpi MSFT0101:00: platform device creation failed: -16
oct. 23 09:45:40 pcp170019 kernel: ACPI: Invalid passive threshold
oct. 23 09:45:40 pcp170019 kernel: usb: port power management may be unreliable
oct. 23 09:45:41 pcp170019 kernel: r8168: loading out-of-tree module taints kernel.
oct. 23 09:45:41 pcp170019 kernel: r8168 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
oct. 23 09:45:41 pcp170019 kernel: r8168  Copyright (C) 2019  Realtek NIC software team <nicfae@realtek.com>
                                    This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licens>
                                    This is free software, and you are welcome to redistribute it under certain conditions; see <http:>
oct. 23 09:45:41 pcp170019 systemd-vconsole-setup[335]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not impl>
oct. 23 09:45:41 pcp170019 systemd-vconsole-setup[335]: Fonts will not be copied to remaining consoles
oct. 23 09:45:41 pcp170019 systemd-udevd[285]: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
oct. 23 09:45:41 pcp170019 kernel: uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not initialized!
oct. 23 09:45:41 pcp170019 kernel: uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized!
oct. 23 09:45:41 pcp170019 kernel: uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized!
oct. 23 09:45:41 pcp170019 ModemManager[384]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name
oct. 23 09:45:41 pcp170019 ModemManager[384]: <warn>  [sleep-monitor] failed to acquire logind proxy: Could not connect: No such file >
oct. 23 09:45:42 pcp170019 kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
oct. 23 09:45:42 pcp170019 systemd-udevd[322]: Config file /usr/lib/systemd/network/99-default.link applies to device based on potenti>
oct. 23 09:45:42 pcp170019 systemd-logind[379]: Failed to read /var/run/utmp, ignoring: No such file or directory
oct. 23 09:45:42 pcp170019 systemd-udevd[291]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
oct. 23 09:45:47 pcp170019 kernel: kauditd_printk_skb: 22 callbacks suppressed
oct. 23 09:46:17 pcp170019 gvfs-udisks2-vo[778]: monitor says it's not supported
oct. 23 09:46:17 pcp170019 gvfs-udisks2-vo[778]: monitor says it's not supported
oct. 23 09:46:17 pcp170019 tumblerd[733]: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
oct. 23 09:46:18 pcp170019 systemd-coredump[796]: Process 750 (light-locker) of user 1000 dumped core.
                                                 
                                                  Stack trace of thread 750:
                                                  #0  0x00007f32db45c1c6 n/a (libglib-2.0.so.0)
                                                  #1  0x00007f32db450f67 g_log_default_handler (libglib-2.0.so.0)
                                                  #2  0x00007f32db45c3fd g_logv (libglib-2.0.so.0)
                                                  #3  0x00007f32db45c600 g_log (libglib-2.0.so.0)
                                                  #4  0x0000563a9db8bcb4 n/a (light-locker)
                                                  #5  0x00007f32db537340 g_type_create_instance (libgobject-2.0.so.0)
                                                  #6  0x00007f32db553746 n/a (libgobject-2.0.so.0)
                                                  #7  0x00007f32db554b95 g_object_new_with_properties (libgobject-2.0.so.0)
                                                  #8  0x00007f32db554c92 g_object_new (libgobject-2.0.so.0)
                                                  #9  0x0000563a9db8e4f3 gs_listener_new (light-locker)
                                                  #10 0x0000563a9db8a484 n/a (light-locker)
                                                  #11 0x00007f32db537340 g_type_create_instance (libgobject-2.0.so.0)
                                                  #12 0x00007f32db553746 n/a (libgobject-2.0.so.0)
                                                  #13 0x00007f32db554b95 g_object_new_with_properties (libgobject-2.0.so.0)
                                                  #14 0x00007f32db554c92 g_object_new (libgobject-2.0.so.0)
                                                  #15 0x0000563a9db8ab03 gs_monitor_new (light-locker)
                                                  #16 0x0000563a9db89339 main (light-locker)
                                                  #17 0x00007f32daf91153 __libc_start_main (libc.so.6)
                                                  #18 0x0000563a9db8948e _start (light-locker)
                                                 
                                                  Stack trace of thread 759:
                                                  #0  0x00007f32db05e9ef __poll (libc.so.6)
                                                  #1  0x00007f32db464180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f32db464251 g_main_context_iteration (libglib-2.0.so.0)
                                                  #3  0x00007f32dc44ce5e n/a (libdconfsettings.so)
                                                  #4  0x00007f32db440c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f32da7b34cf start_thread (libpthread.so.0)
                                                  #6  0x00007f32db0692d3 __clone (libc.so.6)
                                                 
                                                  Stack trace of thread 758:
                                                  #0  0x00007f32db05e9ef __poll (libc.so.6)
                                                  #1  0x00007f32db464180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f32db464251 g_main_context_iteration (libglib-2.0.so.0)
                                                  #3  0x00007f32db4642a2 n/a (libglib-2.0.so.0)
                                                  #4  0x00007f32db440c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f32da7b34cf start_thread (libpthread.so.0)
                                                  #6  0x00007f32db0692d3 __clone (libc.so.6)
                                                 
                                                  Stack trace of thread 764:
                                                  #0  0x00007f32db05e9ef __poll (libc.so.6)
                                                  #1  0x00007f32db464180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f32db465123 g_main_loop_run (libglib-2.0.so.0)
                                                  #3  0x00007f32db84cb48 n/a (libgio-2.0.so.0)
                                                  #4  0x00007f32db440c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f32da7b34cf start_thread (libpthread.so.0)
                                                  #6  0x00007f32db0692d3 __clone (libc.so.6)
oct. 23 09:46:41 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:47:06 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:47:11 pcp170019 systemd[1]: chronyd.service: Start operation timed out. Terminating.
oct. 23 09:47:11 pcp170019 systemd[1]: chronyd.service: Failed with result 'timeout'.
oct. 23 09:47:11 pcp170019 systemd[1]: Failed to start NTP client/server.
oct. 23 09:47:31 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:47:46 pcp170019 systemd[589]: pulseaudio.service: Start operation timed out. Terminating.
oct. 23 09:47:46 pcp170019 systemd[589]: pulseaudio.service: Failed with result 'timeout'.
oct. 23 09:47:46 pcp170019 systemd[589]: Failed to start Sound Service.
oct. 23 09:47:56 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:48:21 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:48:46 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:49:11 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:49:16 pcp170019 systemd[589]: pulseaudio.service: Start operation timed out. Terminating.
oct. 23 09:49:16 pcp170019 systemd[589]: pulseaudio.service: Failed with result 'timeout'.
oct. 23 09:49:16 pcp170019 systemd[589]: Failed to start Sound Service.
oct. 23 09:49:36 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:50:01 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:50:14 pcp170019 gvfs-udisks2-vo[778]: monitor says it's not supported
oct. 23 09:50:26 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:50:47 pcp170019 systemd[589]: pulseaudio.service: Start operation timed out. Terminating.
oct. 23 09:50:47 pcp170019 systemd[589]: pulseaudio.service: Failed with result 'timeout'.
oct. 23 09:50:47 pcp170019 systemd[589]: Failed to start Sound Service.
oct. 23 09:50:51 pcp170019 rtkit-daemon[695]: Warning: PolicyKit call failed: Failed to activate service 'org.freedesktop.PolicyKit1':>
oct. 23 09:50:51 pcp170019 rtkit-daemon[695]: dbus_message_get_unix_user() failed: Could not get UID of name ':1.79': no such name
J'ai aussi supprimé light-locker pour tester...

Voici un petit retour : https://github.com/the-cavalry/light-locker/issues/88
J'ai effectivement aucun retour sur sur $XDG_SESSION_PATH
Mais je ne trouve pas comment le corriger.

Corrigé !
Répondre