Ubuntu-fr

fran6co

Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Bonjour,

J'ai installé Mate sur un vieux core2Quad. C'est la seule distribution qui ait tenue sur ce PC.
J'ai dû gérer des soucis divers avec mes recherches sur internet mais quand je les ai tous solutionnés, j'ai rencontré un nouveau souci : l'ordinateur ne répond pas à la commande graphique d'extinction.
Cela fonctionne quand-même lorsque j'utilise la commande sudo reboot ou shutdown.

Quelqu'un sait-il où je peux m'orienter pour trouver une solution ? Merci pour votre aide.

Fran6

Voici la réponse à la commande 4.4 de cette page :https://doc.ubuntu-fr.org/diagnostic_outil

Aug  9 23:33:09 fran6-cr10 avahi-daemon[616]: Registering new address record for 192.168.0.15 on ens2.IPv4.
Aug  9 23:33:09 fran6-cr10 NetworkManager[621]: <info>  [1691616789.9378] device (ens2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0525] device (ens2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0538] device (ens2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0553] manager: NetworkManager state is now CONNECTED_LOCAL
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0565] manager: NetworkManager state is now CONNECTED_SITE
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0573] policy: set 'Connexion filaire 1' (ens2) as default for IPv4 routing and DNS
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0600] device (ens2): Activation: successful, device activated.
Aug  9 23:33:10 fran6-cr10 systemd-resolved[491]: ens2: Bus client set default route setting: yes
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0617] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug  9 23:33:10 fran6-cr10 systemd-resolved[491]: ens2: Bus client set DNS server list to: 89.2.0.1, 89.2.0.2
Aug  9 23:33:10 fran6-cr10 NetworkManager[621]: <info>  [1691616790.0627] manager: startup complete
Aug  9 23:33:10 fran6-cr10 systemd[1]: Finished Network Manager Wait Online.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Reached target Network is Online.
Aug  9 23:33:10 fran6-cr10 nm-dispatcher[853]: /etc/network/if-up.d/resolved: 12: mystatedir: not found
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started Download data for packages that failed at package install time.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started Check to see whether there is a new version of Ubuntu available.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Reached target Timer Units.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started Make remote CUPS printers available locally.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started NoMachine Server daemon.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Condition check resulted in Ubuntu Pro Background Auto Attach being skipped.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started crash report submission.
Aug  9 23:33:10 fran6-cr10 systemd[1]: kerneloops.service: Found left-over process 865 (kerneloops) in control group while starting unit. Ignoring.
Aug  9 23:33:10 fran6-cr10 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug  9 23:33:10 fran6-cr10 systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Aug  9 23:33:11 fran6-cr10 nm-dispatcher[896]: /etc/network/if-up.d/resolved: 12: mystatedir: not found
Aug  9 23:33:11 fran6-cr10 whoopsie[857]: [23:33:11] Using lock path: /var/lock/whoopsie/lock
Aug  9 23:33:11 fran6-cr10 ModemManager[758]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin
Aug  9 23:33:11 fran6-cr10 systemd[1]: whoopsie.service: Deactivated successfully.
Aug  9 23:33:13 fran6-cr10 snapd[636]: overlord.go:272: Acquiring state lock file
Aug  9 23:33:13 fran6-cr10 snapd[636]: overlord.go:277: Acquired state lock file
Aug  9 23:33:13 fran6-cr10 systemd[1]: systemd-fsckd.service: Deactivated successfully.
Aug  9 23:33:14 fran6-cr10 snapd[636]: daemon.go:247: started snapd/2.59.5 (series 16; classic) ubuntu/22.04 (amd64) linux/6.2.0-26-generic.
Aug  9 23:33:14 fran6-cr10 kernel: [   58.916948] loop25: detected capacity change from 0 to 8
Aug  9 23:33:14 fran6-cr10 snapd[636]: daemon.go:340: adjusting startup timeout by 2m0s (pessimistic estimate of 30s plus 5s per snap)
Aug  9 23:33:14 fran6-cr10 systemd[1]: tmp-syscheck\x2dmountpoint\x2d193380886.mount: Deactivated successfully.
Aug  9 23:33:15 fran6-cr10 systemd-resolved[491]: Clock change detected. Flushing caches.
Aug  9 23:33:15 fran6-cr10 systemd-timesyncd[493]: Initial synchronization to time server 91.189.91.157:123 (ntp.ubuntu.com).
Aug  9 23:33:16 fran6-cr10 systemd[1]: Started Disk Manager.
Aug  9 23:33:16 fran6-cr10 udisksd[654]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Aug  9 23:33:17 fran6-cr10 systemd[1]: Started Bluetooth management mechanism.
Aug  9 23:33:18 fran6-cr10 snapd[636]: backends.go:58: AppArmor status: apparmor is enabled and all features are available
Aug  9 23:33:19 fran6-cr10 systemd[1]: Started Snap Daemon.
Aug  9 23:33:19 fran6-cr10 dbus-daemon[620]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32' (uid=0 pid=636 comm="/usr/lib/snapd/snapd " label="unconfined")
Aug  9 23:33:19 fran6-cr10 systemd[1]: Starting Wait until snapd is fully seeded...
Aug  9 23:33:19 fran6-cr10 systemd[1]: Starting Time & Date Service...
Aug  9 23:33:19 fran6-cr10 dbus-daemon[620]: [system] Successfully activated service 'org.freedesktop.timedate1'
Aug  9 23:33:20 fran6-cr10 systemd[1]: Started Time & Date Service.
Aug  9 23:33:21 fran6-cr10 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Finished Wait until snapd is fully seeded.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Reached target Multi-User System.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Reached target Graphical Interface.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Starting Record Runlevel Change in UTMP...
Aug  9 23:33:26 fran6-cr10 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Finished Record Runlevel Change in UTMP.
Aug  9 23:33:26 fran6-cr10 systemd[1]: Startup finished in 6.532s (kernel) + 1min 4.710s (userspace) = 1min 11.242s.
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + output=VGA1
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + x=1680
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + y=1050
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + freq=59.95
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + '[' 4 -ne 4 ']'
Aug  9 23:33:28 fran6-cr10 lightdm[1033]: ++ cvt 1680 1050 59.95
Aug  9 23:33:28 fran6-cr10 lightdm[1034]: ++ grep -v '^#'
Aug  9 23:33:28 fran6-cr10 lightdm[1035]: ++ cut '-d ' -f3-
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + modename=1680x1050
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:28 fran6-cr10 lightdm[1036]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:28 fran6-cr10 lightdm[1036]: Try 'xrandr --help' for more information.
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:28 fran6-cr10 lightdm[1037]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:28 fran6-cr10 lightdm[1031]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:28 fran6-cr10 lightdm[1038]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:28 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:28 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:28 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Aug  9 23:33:28 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:28 fran6-cr10 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug  9 23:33:28 fran6-cr10 systemd[1]: gpu-manager.service: Deactivated successfully.
Aug  9 23:33:28 fran6-cr10 systemd[1]: Finished Detect the available GPUs and deal with any system changes.
Aug  9 23:33:28 fran6-cr10 systemd[1]: Starting Light Display Manager...
Aug  9 23:33:28 fran6-cr10 lightdm[1085]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Aug  9 23:33:28 fran6-cr10 systemd[1]: Started Light Display Manager.
Aug  9 23:33:28 fran6-cr10 acpid: client 793[0:0] has disconnected
Aug  9 23:33:28 fran6-cr10 acpid: client connected from 1091[0:0]
Aug  9 23:33:28 fran6-cr10 acpid: 1 client rule loaded
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + output=VGA1
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + x=1680
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + y=1050
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + freq=59.95
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + '[' 4 -ne 4 ']'
Aug  9 23:33:29 fran6-cr10 lightdm[1101]: ++ cvt 1680 1050 59.95
Aug  9 23:33:29 fran6-cr10 lightdm[1102]: ++ grep -v '^#'
Aug  9 23:33:29 fran6-cr10 lightdm[1103]: ++ cut '-d ' -f3-
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + modename=1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:29 fran6-cr10 lightdm[1104]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:29 fran6-cr10 lightdm[1104]: Try 'xrandr --help' for more information.
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1105]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:29 fran6-cr10 lightdm[1105]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:29 fran6-cr10 lightdm[1099]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1106]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:29 fran6-cr10 lightdm[1106]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:29 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:29 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:29 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Aug  9 23:33:29 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:29 fran6-cr10 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug  9 23:33:29 fran6-cr10 systemd[1]: gpu-manager.service: Deactivated successfully.
Aug  9 23:33:29 fran6-cr10 systemd[1]: Finished Detect the available GPUs and deal with any system changes.
Aug  9 23:33:29 fran6-cr10 systemd[1]: Starting Light Display Manager...
Aug  9 23:33:29 fran6-cr10 lightdm[1150]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Aug  9 23:33:29 fran6-cr10 systemd[1]: Started Light Display Manager.
Aug  9 23:33:29 fran6-cr10 acpid: client 1091[0:0] has disconnected
Aug  9 23:33:29 fran6-cr10 acpid: client connected from 1156[0:0]
Aug  9 23:33:29 fran6-cr10 acpid: 1 client rule loaded
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + output=VGA1
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + x=1680
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + y=1050
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + freq=59.95
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + '[' 4 -ne 4 ']'
Aug  9 23:33:29 fran6-cr10 lightdm[1166]: ++ cvt 1680 1050 59.95
Aug  9 23:33:29 fran6-cr10 lightdm[1167]: ++ grep -v '^#'
Aug  9 23:33:29 fran6-cr10 lightdm[1168]: ++ cut '-d ' -f3-
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + modename=1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:29 fran6-cr10 lightdm[1169]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:29 fran6-cr10 lightdm[1169]: Try 'xrandr --help' for more information.
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1170]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:29 fran6-cr10 lightdm[1170]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:29 fran6-cr10 lightdm[1164]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:29 fran6-cr10 lightdm[1171]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:29 fran6-cr10 lightdm[1171]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Aug  9 23:33:30 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:30 fran6-cr10 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug  9 23:33:30 fran6-cr10 systemd[1]: gpu-manager.service: Deactivated successfully.
Aug  9 23:33:30 fran6-cr10 systemd[1]: Finished Detect the available GPUs and deal with any system changes.
Aug  9 23:33:30 fran6-cr10 systemd[1]: Starting Light Display Manager...
Aug  9 23:33:30 fran6-cr10 lightdm[1211]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Aug  9 23:33:30 fran6-cr10 systemd[1]: Started Light Display Manager.
Aug  9 23:33:30 fran6-cr10 acpid: client 1156[0:0] has disconnected
Aug  9 23:33:30 fran6-cr10 acpid: client connected from 1217[0:0]
Aug  9 23:33:30 fran6-cr10 acpid: 1 client rule loaded
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + output=VGA1
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + x=1680
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + y=1050
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + freq=59.95
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + '[' 4 -ne 4 ']'
Aug  9 23:33:30 fran6-cr10 lightdm[1229]: ++ cvt 1680 1050 59.95
Aug  9 23:33:30 fran6-cr10 lightdm[1230]: ++ grep -v '^#'
Aug  9 23:33:30 fran6-cr10 lightdm[1231]: ++ cut '-d ' -f3-
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + modename=1680x1050
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:30 fran6-cr10 lightdm[1232]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:30 fran6-cr10 lightdm[1232]: Try 'xrandr --help' for more information.
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:30 fran6-cr10 lightdm[1233]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:30 fran6-cr10 lightdm[1233]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:30 fran6-cr10 lightdm[1227]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:30 fran6-cr10 lightdm[1234]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:30 fran6-cr10 lightdm[1234]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:30 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Aug  9 23:33:30 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug  9 23:33:31 fran6-cr10 systemd[1]: gpu-manager.service: Deactivated successfully.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Finished Detect the available GPUs and deal with any system changes.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Starting Light Display Manager...
Aug  9 23:33:31 fran6-cr10 lightdm[1282]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Aug  9 23:33:31 fran6-cr10 systemd[1]: Started Light Display Manager.
Aug  9 23:33:31 fran6-cr10 acpid: client 1217[0:0] has disconnected
Aug  9 23:33:31 fran6-cr10 acpid: client connected from 1288[0:0]
Aug  9 23:33:31 fran6-cr10 acpid: 1 client rule loaded
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + output=VGA1
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + x=1680
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + y=1050
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + freq=59.95
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + '[' 4 -ne 4 ']'
Aug  9 23:33:31 fran6-cr10 lightdm[1326]: ++ cvt 1680 1050 59.95
Aug  9 23:33:31 fran6-cr10 lightdm[1327]: ++ grep -v '^#'
Aug  9 23:33:31 fran6-cr10 lightdm[1328]: ++ cut '-d ' -f3-
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + modename=1680x1050
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:31 fran6-cr10 lightdm[1329]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:31 fran6-cr10 lightdm[1329]: Try 'xrandr --help' for more information.
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:31 fran6-cr10 lightdm[1330]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:31 fran6-cr10 lightdm[1330]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:31 fran6-cr10 lightdm[1324]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:31 fran6-cr10 lightdm[1331]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:31 fran6-cr10 lightdm[1331]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:31 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:31 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:31 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug  9 23:33:31 fran6-cr10 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Aug  9 23:33:31 fran6-cr10 systemd[1]: gpu-manager.service: Deactivated successfully.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Finished Detect the available GPUs and deal with any system changes.
Aug  9 23:33:31 fran6-cr10 systemd[1]: Starting Light Display Manager...
Aug  9 23:33:31 fran6-cr10 lightdm[1383]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Aug  9 23:33:31 fran6-cr10 systemd[1]: Started Light Display Manager.
Aug  9 23:33:31 fran6-cr10 acpid: client 1288[0:0] has disconnected
Aug  9 23:33:31 fran6-cr10 acpid: client connected from 1390[0:0]
Aug  9 23:33:31 fran6-cr10 acpid: 1 client rule loaded
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + output=VGA1
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + x=1680
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + y=1050
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + freq=59.95
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + '[' 4 -ne 4 ']'
Aug  9 23:33:32 fran6-cr10 lightdm[1400]: ++ cvt 1680 1050 59.95
Aug  9 23:33:32 fran6-cr10 lightdm[1401]: ++ grep -v '^#'
Aug  9 23:33:32 fran6-cr10 lightdm[1402]: ++ cut '-d ' -f3-
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + mode=' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + modename=1680x1050
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + xrandr --newmode 1680x1050 ' 146.00  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync'
Aug  9 23:33:32 fran6-cr10 lightdm[1403]: xrandr: failed to parse '1680x1050' as a mode specification
Aug  9 23:33:32 fran6-cr10 lightdm[1403]: Try 'xrandr --help' for more information.
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + xrandr --addmode VGA1 1680x1050
Aug  9 23:33:32 fran6-cr10 lightdm[1404]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:32 fran6-cr10 lightdm[1404]: xrandr: cannot find mode "1680x1050"
Aug  9 23:33:32 fran6-cr10 lightdm[1398]: + xrandr --output VGA1 --mode 1680x1050
Aug  9 23:33:32 fran6-cr10 lightdm[1405]: xrandr: Output VGA1 is not disconnected but has no modes
Aug  9 23:33:32 fran6-cr10 lightdm[1405]: xrandr: cannot find mode 1680x1050
Aug  9 23:33:32 fran6-cr10 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug  9 23:33:32 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:32 fran6-cr10 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 6.
Aug  9 23:33:32 fran6-cr10 systemd[1]: Stopped Light Display Manager.
Aug  9 23:33:32 fran6-cr10 systemd[1]: gpu-manager.service: Start request repeated too quickly.
Aug  9 23:33:32 fran6-cr10 systemd[1]: gpu-manager.service: Failed with result 'start-limit-hit'.
Aug  9 23:33:32 fran6-cr10 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
Aug  9 23:33:32 fran6-cr10 systemd[1]: lightdm.service: Start request repeated too quickly.
Aug  9 23:33:32 fran6-cr10 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug  9 23:33:32 fran6-cr10 systemd[1]: Failed to start Light Display Manager.
Aug  9 23:33:41 fran6-cr10 systemd[1]: Created slice User Slice of UID 1000.
Aug  9 23:33:41 fran6-cr10 systemd[1]: Starting User Runtime Directory /run/user/1000...
Aug  9 23:33:41 fran6-cr10 systemd[1]: Finished User Runtime Directory /run/user/1000.
Aug  9 23:33:41 fran6-cr10 systemd[1]: Starting User Manager for UID 1000...
Aug  9 23:33:41 fran6-cr10 systemd[1494]: Queued start job for default target Main User Target.
Aug  9 23:33:42 fran6-cr10 systemd[1494]: Created slice User Application Slice.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Created slice User Core Session Slice.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Started Pending report trigger for Ubuntu Report.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Reached target Paths.
Aug  9 23:33:43 fran6-cr10 dbus-daemon[620]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.48' (uid=1000 pid=1502 comm="/usr/bin/pipewire " label="unconfined")
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Reached target Timers.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Starting D-Bus User Message Bus Socket...
Aug  9 23:33:43 fran6-cr10 dbus-daemon[620]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on GnuPG network certificate management daemon.
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Successfully called chroot.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Successfully dropped privileges.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Successfully limited resources.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Canary thread running.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Watchdog thread running.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on PipeWire Multimedia System Socket.
Aug  9 23:33:43 fran6-cr10 rtkit-daemon[1535]: Running.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on debconf communication socket.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on Sound System.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on REST API socket for snapd user session agent.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on Speech Dispatcher Socket.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Listening on D-Bus User Message Bus Socket.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Reached target Sockets.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Reached target Basic System.
Aug  9 23:33:43 fran6-cr10 systemd[1]: Started User Manager for UID 1000.
Aug  9 23:33:43 fran6-cr10 systemd[1]: Started Session c1 of User fran6.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Started PipeWire Multimedia Service.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Started PipeWire Media Session Manager.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Starting Sound Service...
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Aug  9 23:33:43 fran6-cr10 systemd[1494]: Started D-Bus User Message Bus.
Aug  9 23:33:43 fran6-cr10 systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Aug  9 23:33:43 fran6-cr10 systemd[1]: Started RealtimeKit Scheduling Policy Service.
Aug  9 23:33:44 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:44 fran6-cr10 pipewire[1502]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Aug  9 23:33:44 fran6-cr10 pipewire[1502]: mod.rt: could not set nice-level to -11: Permission non accordée
Aug  9 23:33:44 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:44 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:44 fran6-cr10 pipewire-media-session[1503]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Aug  9 23:33:44 fran6-cr10 pipewire-media-session[1503]: mod.rt: could not make thread 1538 realtime using RTKit: Permission non accordée
Aug  9 23:33:45 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] AppArmor D-Bus mediation is enabled
Aug  9 23:33:45 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.1' (uid=1000 pid=1505 comm="/usr/bin/snap run snapd-desktop-integration " label="unconfined")
Aug  9 23:33:45 fran6-cr10 systemd[1494]: Starting flatpak document portal service...
Aug  9 23:33:45 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:45 fran6-cr10 pipewire[1502]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Aug  9 23:33:45 fran6-cr10 pipewire[1502]: mod.rt: could not make thread 1540 realtime using RTKit: Permission non accordée
Aug  9 23:33:46 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.4' (uid=1000 pid=1539 comm="/usr/libexec/xdg-document-portal " label="unconfined")
Aug  9 23:33:46 fran6-cr10 systemd[1494]: Starting sandboxed app permission store...
Aug  9 23:33:46 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Aug  9 23:33:46 fran6-cr10 systemd[1494]: Started sandboxed app permission store.
Aug  9 23:33:46 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.freedesktop.portal.Documents'
Aug  9 23:33:46 fran6-cr10 systemd[1494]: Started flatpak document portal service.
Aug  9 23:33:46 fran6-cr10 kernel: [   91.071895] audit: type=1400 audit(1691616826.514:66): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19457/usr/lib/snapd/snap-confine" pid=1505 comm="snap-confine" capability=12  capname="net_admin"
Aug  9 23:33:46 fran6-cr10 kernel: [   91.071916] audit: type=1400 audit(1691616826.514:67): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19457/usr/lib/snapd/snap-confine" pid=1505 comm="snap-confine" capability=38  capname="perfmon"
Aug  9 23:33:46 fran6-cr10 systemd[1]: blueman-mechanism.service: Deactivated successfully.
Aug  9 23:33:46 fran6-cr10 systemd[1]: tmp-snap.rootfs_BfkhCG.mount: Deactivated successfully.
Aug  9 23:33:49 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:49 fran6-cr10 rtkit-daemon[1535]: message repeated 4 times: [ Supervising 0 threads of 0 processes of 1 users.]
Aug  9 23:33:50 fran6-cr10 systemd[1]: systemd-timedated.service: Deactivated successfully.
Aug  9 23:33:50 fran6-cr10 systemd[1494]: Started Sound Service.
Aug  9 23:33:50 fran6-cr10 systemd[1494]: Reached target Main User Target.
Aug  9 23:33:50 fran6-cr10 systemd[1494]: Startup finished in 8.834s.
Aug  9 23:33:50 fran6-cr10 pulseaudio[1504]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
Aug  9 23:33:50 fran6-cr10 kernel: [   94.702224] Bluetooth: RFCOMM TTY layer initialized
Aug  9 23:33:50 fran6-cr10 kernel: [   94.702244] Bluetooth: RFCOMM socket layer initialized
Aug  9 23:33:50 fran6-cr10 kernel: [   94.702258] Bluetooth: RFCOMM ver 1.11
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSink/sbc
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSource/sbc
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Failed to add UUID: Failed (0x03)
Aug  9 23:33:50 fran6-cr10 kernel: [   94.708253] Bluetooth: hci0: Opcode 0x c24 failed: -32
Aug  9 23:33:50 fran6-cr10 kernel: [   94.709241] Bluetooth: hci0: Opcode 0x c24 failed: -32
Aug  9 23:33:50 fran6-cr10 bluetoothd[618]: Failed to add UUID: Failed (0x03)
Aug  9 23:33:53 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 1 users.
Aug  9 23:33:54 fran6-cr10 rtkit-daemon[1535]: message repeated 20 times: [ Supervising 0 threads of 0 processes of 1 users.]
Aug  9 23:33:54 fran6-cr10 dbus-daemon[1730]: [session uid=1000 pid=1728] AppArmor D-Bus mediation is enabled
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: src/profile.c:register_profile() :1.68 tried to register 00001108-0000-1000-8000-00805f9b34fb which is already registered
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: src/profile.c:register_profile() :1.68 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug  9 23:33:54 fran6-cr10 bluetoothd[618]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug  9 23:34:01 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.11' (uid=1000 pid=1632 comm="x-session-manager " label="unconfined")
Aug  9 23:34:01 fran6-cr10 systemd[1]: Started Run anacron jobs.
Aug  9 23:34:01 fran6-cr10 anacron[1988]: Anacron 2.3 started on 2023-08-09
Aug  9 23:34:01 fran6-cr10 anacron[1988]: Normal exit (0 jobs run)
Aug  9 23:34:01 fran6-cr10 systemd[1]: anacron.service: Deactivated successfully.
Aug  9 23:34:01 fran6-cr10 systemd[1494]: Starting Virtual filesystem service...
Aug  9 23:34:01 fran6-cr10 snapd-desktop-i[1974]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Aug  9 23:34:01 fran6-cr10 snapd-desktop-i[1974]: Failed to do gtk init. Waiting for a new session with desktop capabilities.
Aug  9 23:34:01 fran6-cr10 snapd-desktop-i[1974]: Checking session /org/freedesktop/login1/session/c1...
Aug  9 23:34:01 fran6-cr10 snapd-desktop-i[1974]: Is a desktop session! Forcing a reload.
Aug  9 23:34:01 fran6-cr10 snapd-desktop-i[1974]: Loop exited. Forcing reload.
Aug  9 23:34:02 fran6-cr10 systemd[1494]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 2.448s CPU time.
Aug  9 23:34:02 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.Daemon'
Aug  9 23:34:02 fran6-cr10 systemd[1494]: Started Virtual filesystem service.
Aug  9 23:34:02 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.14' (uid=1000 pid=1632 comm="x-session-manager " label="unconfined")
Aug  9 23:34:02 fran6-cr10 systemd[1494]: Starting Accessibility services bus...
Aug  9 23:34:02 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.a11y.Bus'
Aug  9 23:34:02 fran6-cr10 systemd[1494]: Started Accessibility services bus.
Aug  9 23:34:04 fran6-cr10 systemd[1494]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 1.
Aug  9 23:34:04 fran6-cr10 systemd[1494]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Aug  9 23:34:04 fran6-cr10 systemd[1494]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 2.448s CPU time.
Aug  9 23:34:04 fran6-cr10 systemd[1494]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Aug  9 23:34:04 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.11' (uid=1000 pid=1632 comm="x-session-manager " label="unconfined")
Aug  9 23:34:04 fran6-cr10 systemd[1494]: Starting User preferences database...
Aug  9 23:34:04 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'ca.desrt.dconf'
Aug  9 23:34:04 fran6-cr10 systemd[1494]: Started User preferences database.
Aug  9 23:34:04 fran6-cr10 kernel: [  109.142077] audit: type=1400 audit(1691616844.582:68): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19457/usr/lib/snapd/snap-confine" pid=2094 comm="snap-confine" capability=12  capname="net_admin"
Aug  9 23:34:04 fran6-cr10 kernel: [  109.142093] audit: type=1400 audit(1691616844.582:69): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19457/usr/lib/snapd/snap-confine" pid=2094 comm="snap-confine" capability=38  capname="perfmon"
Aug  9 23:34:04 fran6-cr10 snapd-desktop-i[2177]: Failed to load module "appmenu-gtk-module"
Aug  9 23:34:04 fran6-cr10 snapd-desktop-i[2177]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Aug  9 23:34:04 fran6-cr10 x-session-manager[1632]: WARNING: Unable to find provider '' of required component 'dock'
Aug  9 23:34:05 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.20' (uid=1000 pid=2177 comm="/snap/snapd-desktop-integration/83/usr/bin/snapd-d" label="snap.snapd-desktop-integration.snapd-desktop-integration (enforce)")
Aug  9 23:34:05 fran6-cr10 at-spi-bus-launcher[2035]: dbus-daemon[2035]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1632 comm="x-session-manager " label="unconfined")
Aug  9 23:34:05 fran6-cr10 systemd[1494]: Starting Portal service...
Aug  9 23:34:05 fran6-cr10 at-spi-bus-launcher[2035]: dbus-daemon[2035]: Successfully activated service 'org.a11y.atspi.Registry'
Aug  9 23:34:05 fran6-cr10 at-spi-bus-launcher[2254]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug  9 23:34:05 fran6-cr10 systemd[1]: Started Session c2 of User fran6.
Aug  9 23:34:05 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.24' (uid=1000 pid=2255 comm="/usr/libexec/xdg-desktop-portal " label="unconfined")
Aug  9 23:34:05 fran6-cr10 systemd[1494]: Starting Portal service (GTK/GNOME implementation)...
Aug  9 23:34:06 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Aug  9 23:34:06 fran6-cr10 systemd[1494]: Started Portal service (GTK/GNOME implementation).
Aug  9 23:34:07 fran6-cr10 rtkit-daemon[1535]: Supervising 0 threads of 0 processes of 0 users.
Aug  9 23:34:07 fran6-cr10 rtkit-daemon[1535]: message repeated 2 times: [ Supervising 0 threads of 0 processes of 0 users.]
Aug  9 23:34:07 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.freedesktop.portal.Desktop'
Aug  9 23:34:07 fran6-cr10 systemd[1494]: Started Portal service.
Aug  9 23:34:07 fran6-cr10 snapd-desktop-i[2177]: New theme: gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
Aug  9 23:34:07 fran6-cr10 snapd-desktop-i[2177]: All available theme snaps installed
Aug  9 23:34:09 fran6-cr10 dbus-daemon[620]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.96' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:09 fran6-cr10 systemd[1]: Starting Hostname Service...
Aug  9 23:34:09 fran6-cr10 dbus-daemon[620]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug  9 23:34:09 fran6-cr10 systemd[1]: Started Hostname Service.
Aug  9 23:34:09 fran6-cr10 snapd-desktop-i[2177]: New theme: gtk=Yaru-dark icon=Yaru-dark cursor=Yaru, sound=Yaru
Aug  9 23:34:09 fran6-cr10 snapd-desktop-i[2177]: All available theme snaps installed
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.22' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Starting Virtual filesystem service - disk device monitor...
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Started Virtual filesystem service - disk device monitor.
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.22' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Starting Virtual filesystem service - Apple File Conduit monitor...
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Started Virtual filesystem service - Apple File Conduit monitor.
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.22' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.22' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Starting Virtual filesystem service - digital camera monitor...
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Started Virtual filesystem service - digital camera monitor.
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.22' (uid=1000 pid=2229 comm="/usr/bin/mate-settings-daemon " label="unconfined")
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Aug  9 23:34:10 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Aug  9 23:34:10 fran6-cr10 systemd[1494]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.panel.applet.BriskMenuFactory' requested by ':1.29' (uid=1000 pid=2588 comm="mate-panel " label="unconfined")
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.panel.applet.WnckletFactory' requested by ':1.29' (uid=1000 pid=2588 comm="mate-panel " label="unconfined")
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.panel.applet.IndicatorAppletCompleteFactory' requested by ':1.29' (uid=1000 pid=2588 comm="mate-panel " label="unconfined")
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.panel.applet.NotificationAreaAppletFactory' requested by ':1.29' (uid=1000 pid=2588 comm="mate-panel " label="unconfined")
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.panel.applet.DriveMountAppletFactory' requested by ':1.29' (uid=1000 pid=2588 comm="mate-panel " label="unconfined")
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.panel.applet.NotificationAreaAppletFactory'
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.panel.applet.DriveMountAppletFactory'
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.panel.applet.IndicatorAppletCompleteFactory'
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.panel.applet.BriskMenuFactory'
Aug  9 23:34:11 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.panel.applet.WnckletFactory'
Aug  9 23:34:12 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.41' (uid=1000 pid=2664 comm="/usr/lib/mate-indicator-applet/mate-indicator-appl" label="unconfined")
Aug  9 23:34:12 fran6-cr10 systemd[1494]: Starting Virtual filesystem metadata service...
Aug  9 23:34:12 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gtk.vfs.Metadata'
Aug  9 23:34:12 fran6-cr10 systemd[1494]: Started Virtual filesystem metadata service.
Aug  9 23:34:14 fran6-cr10 spice-vdagent[2798]: vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
Aug  9 23:34:14 fran6-cr10 systemd[1494]: Started snap.ubuntu-mate-welcome.ubuntu-mate-welcome.d139f6fd-5d7f-4dd2-90ac-03e9a76e7da8.scope.
Aug  9 23:34:14 fran6-cr10 NetworkManager[621]: <info>  [1691616854.4108] agent-manager: agent[b41b35a5bfa5a068,:1.107/org.freedesktop.nm-applet/1000]: agent registered
Aug  9 23:34:15 fran6-cr10 kernel: [  120.419779] traps: mate-power-mana[2790] trap int3 ip:7f6ac6dc1cef sp:7ffc7b467110 error:0 in libglib-2.0.so.0.7200.4[7f6ac6d82000+8f000]
Aug  9 23:34:16 fran6-cr10 notification-ar[2666]: GDBus.Error:org.freedesktop.DBus.GLib.ErrorError: Method invoked for RegisterStatusNotifierHost returned FALSE but did not set error
Aug  9 23:34:20 fran6-cr10 dbus-daemon[620]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.116' (uid=1000 pid=2719 comm="/usr/libexec/ayatana-indicator-datetime/ayatana-in" label="unconfined")
Aug  9 23:34:20 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.68' (uid=1000 pid=2719 comm="/usr/libexec/ayatana-indicator-datetime/ayatana-in" label="unconfined")
Aug  9 23:34:20 fran6-cr10 systemd[1]: Starting Time & Date Service...
Aug  9 23:34:20 fran6-cr10 systemd[1494]: Starting Evolution source registry...
Aug  9 23:34:20 fran6-cr10 dbus-daemon[620]: [system] Successfully activated service 'org.freedesktop.timedate1'
Aug  9 23:34:20 fran6-cr10 systemd[1]: Started Time & Date Service.
Aug  9 23:34:21 fran6-cr10 dbus-daemon[620]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.104' (uid=1000 pid=2697 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined")
Aug  9 23:34:21 fran6-cr10 systemd[1]: Starting Bluetooth management mechanism...
Aug  9 23:34:21 fran6-cr10 dbus-daemon[620]: [system] Successfully activated service 'org.blueman.Mechanism'
Aug  9 23:34:21 fran6-cr10 systemd[1]: Started Bluetooth management mechanism.
Aug  9 23:34:21 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.45' (uid=1000 pid=2697 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined")
Aug  9 23:34:21 fran6-cr10 systemd[1494]: Starting Bluetooth OBEX service...
Aug  9 23:34:22 fran6-cr10 obexd[2949]: OBEX daemon 5.64
Aug  9 23:34:22 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.bluez.obex'
Aug  9 23:34:22 fran6-cr10 systemd[1494]: Started Bluetooth OBEX service.
Aug  9 23:34:23 fran6-cr10 brisk-menu[2658]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
Aug  9 23:34:23 fran6-cr10 brisk-menu[2658]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
Aug  9 23:34:23 fran6-cr10 brisk-menu[2658]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
Aug  9 23:34:23 fran6-cr10 brisk-menu[2658]: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
Aug  9 23:34:23 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating service name='org.mate.ScreenSaver' requested by ':1.37' (uid=1000 pid=2658 comm="/usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu " label="unconfined")
Aug  9 23:34:25 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.mate.ScreenSaver'
Aug  9 23:34:30 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
Aug  9 23:34:30 fran6-cr10 systemd[1494]: Started Evolution source registry.
Aug  9 23:34:30 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.68' (uid=1000 pid=2719 comm="/usr/libexec/ayatana-indicator-datetime/ayatana-in" label="unconfined")
Aug  9 23:34:30 fran6-cr10 systemd[1494]: Starting Evolution calendar service...
Aug  9 23:34:31 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
Aug  9 23:34:31 fran6-cr10 systemd[1494]: Started Evolution calendar service.
Aug  9 23:34:32 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.78' (uid=1000 pid=2989 comm="/usr/libexec/evolution-calendar-factory " label="unconfined")
Aug  9 23:34:32 fran6-cr10 systemd[1494]: Starting Evolution address book service...
Aug  9 23:34:32 fran6-cr10 dbus-daemon[1534]: [session uid=1000 pid=1534] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
Aug  9 23:34:32 fran6-cr10 systemd[1494]: Started Evolution address book service.
Aug  9 23:34:39 fran6-cr10 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Aug  9 23:34:50 fran6-cr10 systemd[1]: systemd-timedated.service: Deactivated successfully.
Aug  9 23:34:52 fran6-cr10 systemd[1]: blueman-mechanism.service: Deactivated successfully.
Aug  9 23:35:27 fran6-cr10 wnck-applet[2662]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
grep -E 'Stopping D-Bus|Started Availability' /var/log/syslog.1 
grep: /var/log/syslog.1: Aucun fichier ou dossier de ce type
sed -n '/Stopping D-Bus/,/Started Availability/p' /var/log/syslog.1 
sed: impossible de lire /var/log/syslog.1: Aucun fichier ou dossier de ce type

Edit : L'information ci-dessus est tronqué de manière trop significative pour être utile, je suppose.
J'aurai bien mis en pièce-jointe le fichier texte de 42Mo mais je ne sais pas encore comment. De toutes manières, sera-t-il seuelemtn pertinent ?

Dernière modification par fran6co (Le 16/08/2023, à 13:24)

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Bonjour,

Pour ajouter toi-même les balises code à ton précédent message #1 :        Merci         

• Cliquer sur le lien « Modifier » en bas à droite du message

• Sélectionner le texte

• Cliquer sur le <> de l'éditeur de message

Montre la carte graphique, en te servant du Retour utilisable de commande :

lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"

uname -a

xrandr

dpkg -l | grep -v ^ii

et :

echo $XDG_SESSION_TYPE

pour voir si c'est Wayland ou x11.

Dernière modification par xubu1957 (Le 10/08/2023, à 11:32)

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Bonjour et merci pour votre message.

J'ai tenté de mofifier mon premier message mais me suis rendu compte que le contenu du terminal est fortement tronqué. 311000 lignes de promt à coller entre deux Code /code... le forum ne semble pas supporter.

voici la réponse à vos demandes :

fran6@fran6-cr10:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller])
	Kernel driver in use: i915
	Kernel modules: i915
fran6@fran6-cr10:~$ 

fran6@fran6-cr10:~$ uname -a
Linux fran6-cr10 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
fran6@fran6-cr10:~$ 

fran6@fran6-cr10:~$ xrandr
Screen 0: minimum 640 x 480, current 1680 x 1027, maximum 16384 x 16384
nxoutput0 connected primary 1680x1027+0+0 427mm x 261mm
   800x600       60.00 +
   640x480       60.00  
   800x480       60.00  
   1024x600      60.00  
   1024x768      60.00  
   1152x864      60.00  
   1280x720      60.00  
   1280x800      60.00  
   1280x1024     60.00  
   1360x768      60.00  
   1366x768      60.00  
   1440x900      60.00  
   1600x900      60.00  
   1600x1200     60.00  
   1680x1050     60.00  
   1920x1080     60.00  
   1920x1200     60.00  
   1680x1027     60.00* 
fran6@fran6-cr10:~$

fran6@fran6-cr10:~$ dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                      Version                                 Architecture Description
+++-========================================-=======================================-============-================================================================================
fran6@fran6-cr10:~$ 

fran6@fran6-cr10:~$ echo $XDG_SESSION_TYPE
x11
fran6@fran6-cr10:~$ 

Sinon, pour information, j'ai commencé à configurer le système et lorsqu'il a bien fonctionné, je lui ai ôté claier, souris et écran. Je l'utilise avec Nomachine.
J'ai rencontré des difficultés d'affichage puis de résolution que j'ai fini par corriger et c'est à ce moment-là que l'extinction a fini par ne plus fonctionner. Je crois en effet qu'il y a un lien depuis le début mais je ne sais pas où intervenir vu le nombre de forums qui en parlent sur des systèmes plus vieux et dont les commandes ne semblent pas fonctionner ici.

Merci pour votre attention.

Cordialement,

Fran6

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Donne aussi la liste des anomalies de démarrage :

journalctl --no-pager -b -p err

et :

ls -l /var/crash

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

fran6@fran6-cr10:~$ journalctl --no-pager -b -p err
août 10 12:56:13 fran6-cr10 kernel: Bluetooth: hci0: Opcode 0x c39 failed: -32
août 10 12:57:09 fran6-cr10 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
août 10 12:57:09 fran6-cr10 systemd[1]: Failed to start Light Display Manager.
fran6@fran6-cr10:~$ 

fran6@fran6-cr10:~$ ls -l /var/crash
total 28428
-rw-r----- 1 fran6    whoopsie   111335 août   9 21:28 _usr_bin_blueman-manager.1000.crash
-rw-r--r-- 1 fran6    whoopsie        0 août   9 21:28 _usr_bin_blueman-manager.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   9 21:37 _usr_bin_blueman-manager.1000.uploaded
-rw-r----- 1 fran6    whoopsie    85900 août   9 22:05 _usr_bin_blueman-tray.1000.crash
-rw-r--r-- 1 fran6    whoopsie        0 août   9 22:05 _usr_bin_blueman-tray.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   9 22:05 _usr_bin_blueman-tray.1000.uploaded
-rw-r----- 1 fran6    whoopsie 17257854 août   8 00:35 _usr_bin_caja.1000.crash
-rw-rw-r-- 1 fran6    whoopsie        0 août   8 00:35 _usr_bin_caja.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   8 00:35 _usr_bin_caja.1000.uploaded
-rw-r----- 1 fran6    whoopsie  3017391 août   8 21:14 _usr_bin_marco.1000.crash
-rw-rw-r-- 1 fran6    whoopsie        0 août   8 21:14 _usr_bin_marco.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   8 21:14 _usr_bin_marco.1000.uploaded
-rw-r----- 1 fran6    whoopsie  1717397 août   9 22:41 _usr_bin_mate-power-manager.1000.crash
-rw-r--r-- 1 fran6    whoopsie        0 août   9 22:41 _usr_bin_mate-power-manager.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   9 22:41 _usr_bin_mate-power-manager.1000.uploaded
-rw-r----- 1 fran6    whoopsie  4224796 août   8 21:13 _usr_bin_mate-settings-daemon.1000.crash
-rw-rw-r-- 1 fran6    whoopsie        0 août   8 21:13 _usr_bin_mate-settings-daemon.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   8 21:13 _usr_bin_mate-settings-daemon.1000.uploaded
-rw-r----- 1 fran6    whoopsie  2651875 août   8 21:31 _usr_lib_mate-panel_wnck-applet.1000.crash
-rw-r--r-- 1 fran6    whoopsie        0 août   8 21:31 _usr_lib_mate-panel_wnck-applet.1000.upload
-rw------- 1 whoopsie whoopsie       37 août   8 21:31 _usr_lib_mate-panel_wnck-applet.1000.uploaded
fran6@fran6-cr10:~$ 

ah, d'accord, il s'agirait donc bien d'un problème avec LightDM

Je me rappelle avoir bricolé dans les fichiers Lightdm .conf.d et una utre avec les mêmes extensions... je me demande même si j'en ai pas créé un avec un tuto... Ça vient peut-être de là...

Dernière modification par fran6co (Le 10/08/2023, à 12:02)

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Je ne saurais pas aider plus !   ¯∖_(ツ)_/¯

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

oui, je crois avoir créé ça :

50-display-setup-script.conf

[Seat:*]
display-setup-script=/etc/lightdm/add-and-set-resolution.sh VGA1 1680 1050 59.95

Je viens de le vider de son contenu car je n'ai pas les droits pour le supprimer.

Dernière modification par fran6co (Le 10/08/2023, à 12:06)

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Je ne saurais pas aider plus !   ¯∖_(ツ)_/¯

Bah, ce n'est pas grave, tu m'as orienté dans mes recherches, je vais encore chercher ou attendre que quelqu'un rebondisse sur tes interventions. En tous cas, merci pour ton aide.

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Montre :

cat /etc/lightdm/lightdm.conf.d

inspiré depuis [MATE] Non prise en compte de ma configuration LightDM

La Doc lightdm.

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Montre :

cat /etc/lightdm/lightdm.conf.d

inspiré depuis [MATE] Non prise en compte de ma configuration LightDM

La Doc lightdm.

Ah pardon, je n'avais pas vu ton commentaire. Je viens de réussir à supprimer mon fichier que j'avais créé. je viens de faire un redémarrage avec sudo reboot now et là j'attends que ça revienne sur le bureau...
Je fais quand-même ta manip ou tu préfères que je relance les commandes précédentes concernantles erreurs de démarrage ?
merci pour ton suivi.

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Bon, apparemment, ce fichier 50-display-setup-script.conf est lié au problème de redémarrage.
Le système répond correctement aux commandes graphiques d'extinction et de redémarrage.
Cependant, je retrouve le problème qu'était censé régler ce fichier .conf :

Le système est de nouveau extrêmement lent sans écran de branché sur la prise VGA et la résolution est pauvre. J'ai tenté à un moment avec une carte pièce détachée d'un viel écran qui a fini à la poubelle et cela avait solutionné la lenteur. Je n'ai toutefois pas l'envie de laisser traîner un câble VGA avec un circuit imprimé non alimenté derrière le PC.

Du coup, je ne sais pas trop quoi faire... je recrée 50monitors.blablabla.conf ou pas ?

Dernière modification par fran6co (Le 10/08/2023, à 12:35)

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Je dois signaler que le système m'indique un problème dans une fenêtre à l'ouverture du bureau :

Impossible d'appliquer la configuration enregistrée pour les écrans. La taille virtuelle demandée n'est pas adaptée à la taille disponible : demande=(1,1), minimum=(8,8), maximum=(32767,32767)

Ça le faisait également avant de vous contacter alors que le système était devenu plus réactif avec le fichier .conf que je viens de supprimer.

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Montre :

cat /etc/lightdm/lightdm.conf.d

inspiré depuis [MATE] Non prise en compte de ma configuration LightDM

La Doc lightdm.

Ah pardon, je n'avais pas vu ton commentaire. Je viens de réussir à supprimer mon fichier que j'avais créé. je viens de faire un redémarrage avec sudo reboot now et là j'attends que ça revienne sur le bureau...
Je fais quand-même ta manip ou tu préfères que je relance les commandes précédentes concernantles erreurs de démarrage ?
merci pour ton suivi.

Voici la réponse :

fran6@fran6-cr10:~$ cat /etc/lightdm/lightdm.conf.d
cat: /etc/lightdm/lightdm.conf.d: est un dossier
fran6@fran6-cr10:~$ 

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Fournis :

systemd-analyze time

systemd-analyze blame --no-pager

systemd-analyze critical-chain

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Fournis :

systemd-analyze time

systemd-analyze blame --no-pager

systemd-analyze critical-chain

fran6@fran6-cr10:~$ systemd-analyze time
Startup finished in 6.717s (kernel) + 1min 14.846s (userspace) = 1min 21.564s 
graphical.target reached after 1min 14.813s in userspace
fran6@fran6-cr10:~$

fran6@fran6-cr10:~$ systemd-analyze blame --no-pager
31.182s snapd.service
24.684s udisks2.service
23.374s systemd-journal-flush.service
16.567s apport-autoreport.service
16.313s networkd-dispatcher.service
15.826s ModemManager.service
13.654s accounts-daemon.service
13.479s dev-loop24.device
13.273s NetworkManager-wait-online.service
13.222s dev-loop15.device
13.073s dev-loop12.device
12.871s dev-loop13.device
12.827s dev-loop16.device
12.565s dev-loop10.device
12.563s dev-loop23.device
12.537s dev-loop9.device
12.133s dev-sda5.device
11.808s dev-loop11.device
11.719s dev-loop8.device
11.679s dev-loop22.device
11.654s dev-loop7.device
11.506s dev-loop17.device
11.419s dev-loop18.device
11.080s dev-loop6.device
10.033s snapd.seeded.service
 9.758s dev-loop1.device
 9.264s dev-loop4.device
 9.255s dev-loop2.device
 9.186s dev-loop21.device
 9.184s dev-loop20.device
 8.794s dev-loop19.device
 8.574s avahi-daemon.service
 8.569s bluetooth.service
 8.440s NetworkManager.service
 8.420s polkit.service
 8.243s dev-loop5.device
 8.241s dev-loop14.device
 7.118s cups.service
 6.575s thermald.service
 6.515s wpa_supplicant.service
 6.512s systemd-logind.service
 5.919s gpu-manager.service
 5.778s dev-loop3.device
 4.379s lightdm.service
 4.362s snapd.apparmor.service
 3.853s rsyslog.service
 3.776s dev-loop0.device
 3.710s grub-common.service
 3.479s systemd-resolved.service
 3.469s systemd-fsck@dev-disk-by\x2duuid-12F8\x2dB098.service
 3.432s systemd-udevd.service
 3.266s apport.service
 2.972s e2scrub_reap.service
 2.898s apparmor.service
 2.484s snap-bare-5.mount
 2.404s snap-blender-3822.mount
 2.305s snap-core-15511.mount
 2.202s networking.service
 2.181s snap-core18-2785.mount
 2.105s snap-core20-1822.mount
 2.042s snap-core20-1974.mount
 1.950s snap-core22-858.mount
 1.870s snap-firefox-2356.mount
 1.811s snap-firefox-2987.mount
 1.707s snap-gimp-393.mount
 1.626s lm-sensors.service
 1.623s snap-gnome\x2d3\x2d38\x2d2004-119.mount
 1.606s snap-gnome\x2d3\x2d38\x2d2004-143.mount
 1.472s snap-gnome\x2d42\x2d2204-120.mount
 1.437s systemd-tmpfiles-setup.service
 1.424s snap-gnome\x2d42\x2d2204-126.mount
 1.293s snap-gtk2\x2dcommon\x2dthemes-13.mount
 1.284s systemd-modules-load.service
 1.237s grub-initrd-fallback.service
 1.209s systemd-udev-trigger.service
 1.165s snap-gtk\x2dcommon\x2dthemes-1535.mount
 1.099s keyboard-setup.service
 1.095s systemd-random-seed.service
 1.069s snap-prusa\x2dslicer-87.mount
  999ms systemd-tmpfiles-setup-dev.service
  979ms systemd-sysusers.service
  950ms snap-snapd-18357.mount
  903ms setvtrgb.service
  886ms snap-snapd-19457.mount
  822ms snap-snapd\x2ddesktop\x2dintegration-49.mount
  746ms snap-snapd\x2ddesktop\x2dintegration-83.mount
  685ms systemd-sysctl.service
  599ms snap-software\x2dboutique-57.mount
  578ms swapfile.swap
  536ms systemd-journald.service
  536ms openvpn.service
  518ms user@1000.service
  483ms snap-ubuntu\x2dmate\x2dwelcome-714.mount
  461ms upower.service
  439ms plymouth-read-write.service
  423ms snap-ubuntu\x2dmate\x2dwelcome-720.mount
  412ms boot-efi.mount
  380ms update-notifier-download.service
  371ms systemd-binfmt.service
  361ms systemd-timesyncd.service
  356ms snap-vlc-3078.mount
  280ms systemd-user-sessions.service
  279ms dev-hugepages.mount
  277ms dev-mqueue.mount
  275ms sys-kernel-debug.mount
  273ms sys-kernel-tracing.mount
  269ms console-setup.service
  260ms kmod-static-nodes.service
  256ms modprobe@configfs.service
  255ms modprobe@drm.service
  252ms ifupdown-pre.service
  251ms modprobe@fuse.service
  217ms blueman-mechanism.service
  206ms ufw.service
  183ms kerneloops.service
  165ms systemd-update-utmp.service
  160ms systemd-remount-fs.service
  126ms proc-sys-fs-binfmt_misc.mount
  101ms ubuntu-advantage-desktop-daemon.service
   89ms rtkit-daemon.service
   87ms systemd-tmpfiles-clean.service
   52ms var-snap-firefox-common-host\x2dhunspell.mount
   48ms modprobe@chromeos_pstore.service
   23ms user-runtime-dir@1000.service
   20ms snapd.socket
   19ms dev-disk-by\x2duuid-fe1f3a35\x2dca0e\x2d43b5\x2dbcb8\x2ddd46548e7099.sw…
   11ms systemd-update-utmp-runlevel.service
   10ms modprobe@efi_pstore.service
    9ms modprobe@pstore_blk.service
    5ms modprobe@pstore_zone.service
    5ms sys-kernel-config.mount
    4ms plymouth-quit-wait.service
    4ms modprobe@ramoops.service
    3ms sys-fs-fuse-connections.mount
fran6@fran6-cr10:~$

fran6@fran6-cr10:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 14.813s
└─multi-user.target @1min 14.812s
  └─snapd.seeded.service @1min 4.778s +10.033s
    └─snapd.service @33.569s +31.182s
      └─basic.target @31.975s
        └─sockets.target @31.974s
          └─snapd.socket @31.953s +20ms
            └─sysinit.target @31.795s
              └─snapd.apparmor.service @27.432s +4.362s
                └─apparmor.service @24.505s +2.898s
                  └─local-fs.target @24.486s
                    └─boot-efi.mount @24.073s +412ms
                      └─systemd-fsck@dev-disk-by\x2duuid-12F8\x2dB098.service @20.537s +3.469s
                        └─dev-disk-by\x2duuid-12F8\x2dB098.device @20.519s
fran6@fran6-cr10:~$ 

Dernière modification par fran6co (Le 10/08/2023, à 12:55)

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Montre :

snap list

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

fran6@fran6-cr10:~$ snap list
Nom                        Version           Révision  Suivi            Éditeur             Notes
bare                       1.0               5         latest/stable    canonical✓          base
blender                    3.6.1             3822      latest/stable    blenderfoundation✓  classic
core                       16-2.59.5         15511     latest/stable    canonical✓          core
core18                     20230530          2785      latest/stable    canonical✓          base
core20                     20230622          1974      latest/stable    canonical✓          base
core22                     20230725          858       latest/stable    canonical✓          base
firefox                    116.0.2-1         2987      latest/stable/…  mozilla✓            -
gimp                       2.10.30           393       latest/stable    snapcrafters✪       -
gnome-3-38-2004            0+git.efb213a     143       latest/stable/…  canonical✓          -
gnome-42-2204              0+git.ff35a85     126       latest/stable    canonical✓          -
gtk-common-themes          0.1-81-g442e511   1535      latest/stable/…  canonical✓          -
gtk2-common-themes         0.1               13        latest/stable    canonical✓          -
prusa-slicer               2.6.0+snap4       87        latest/stable    ivo-cavalcante      -
snapd                      2.59.5            19457     latest/stable    canonical✓          snapd
snapd-desktop-integration  0.9               83        latest/stable/…  canonical✓          -
software-boutique          0+git.0fdcecc     57        latest/stable/…  flexiondotorg       classic
ubuntu-mate-welcome        22.04.0-a59036a6  720       latest/stable/…  flexiondotorg       classic
vlc                        3.0.18            3078      latest/stable    videolan✓           -
fran6@fran6-cr10:~$ 

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Montre :

cat /etc/lightdm/lightdm.conf.d

inspiré depuis [MATE] Non prise en compte de ma configuration LightDM

La Doc lightdm.

Je viens de finir de parcourir le sujet auquel tu te référais, je vois que le problème était différent. en tous cas merci d'avoir cherché avec moi

Dernière modification par fran6co (Le 10/08/2023, à 13:19)

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

J'aperçois cette cdommande dans la doc sur LightDM vers la fin de la pageau point 8.1, je teste ?

sudo apt-get install --reinstall lightdm

Dernière modification par fran6co (Le 10/08/2023, à 13:22)

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Pour info, Xrandr donne ça à présent :

fran6@fran6-cr10:~$ xrandr
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
VGA1 disconnected primary (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
fran6@fran6-cr10:~$ 

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Je lis :

Les différentes fenêtres de connexion
Selon la variante d'Ubuntu que vous utilisez, votre écran de connexion par défaut est généralement soit :

LightDM pour Ubuntu Unity, Lubuntu, Xubuntu, Ubuntu Budgie et Ubuntu MATE jusqu’à la 20.04 ;
GDM (GNOME Display Manager) pour Ubuntu GNOME et Ubuntu (à partir de la version 17.10) ;
SDDM (Simple Desktop Display Manager) pour les versions 16.04 et supérieures de Kubuntu ;
Artica pour Ubuntu MATE à partir de la 22.04,...

dans la Doc fenetre_de_connexion.

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Là, je suis perdu, je ne connaissais pas LightDM avant lundi mais le dernier là ???

Je vais potasser le lien que tu m'as envoyé. Merci.

xubu1957

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Fournis :

echo; lsb_release -d ; echo $XDG_CURRENT_DESKTOP ; echo; ls -lt /usr/share/xsessions | awk '{print $6,$7,$8,$9}'

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

fran6@fran6-cr10:~$ echo; lsb_release -d ; echo $XDG_CURRENT_DESKTOP ; echo; ls -lt /usr/share/xsessions | awk '{print $6,$7,$8,$9}'

Description:	Ubuntu 22.04.3 LTS
MATE

   
janv. 26 2022 mate.desktop
fran6@fran6-cr10:~$ 

Oui, j'étais en train de fouiller dans l'interface graphique, je me demande donc, s'il ne vaudrait pas mieux tenter d'installer une connexion alternative. Qu'en penses-tu ?

fran6co

Re : Ubuntu Mate Extinction non fonctionnelle - [RÉSOLU]

Je ne vois aucune référence à Artica dans mon Ubuntu. Je suis en train de parcourir le lien justement, peut-être trouverais-je un moyen de savoir s'il est bien présent ici...