Bonjour, j'ai Ubuntu 18.04 sur un Thinkpad P70 Lenovo en dual boot Windows 10.
Windows démarre très vite, Ubuntu met plusieurs dizaines de secondes... J'ai 10 Go de swap, 32 Go de ram, donc ça devrait aller...
Voici les analyses systemd
Code:systemd-analyze blame 30.189s NetworkManager-wait-online.service 8.042s snapd.service 6.943s gpu-manager.service 6.807s keyboard-setup.service 6.684s dev-sdb2.device 6.409s networkd-dispatcher.service 4.512s snap-gnome\x2d3\x2d26\x2d1604-78.mount 4.273s snap-gnome\x2dsystem\x2dmonitor-81.mount 4.246s snap-gnome\x2dlogs-45.mount 4.055s snap-gnome\x2d3\x2d26\x2d1604-74.mount 3.743s tor@default.service 3.563s snap-gnome\x2dcharacters-254.mount 3.549s snap-gnome\x2dsystem\x2dmonitor-77.mount 3.489s snap-opera-34.mount 3.445s NetworkManager.service 3.069s snap-core18-782.mount 3.044s systemd-journal-flush.service 2.977s snap-gnome\x2d3\x2d28\x2d1804-31.mount 2.828s snap-gnome\x2d3\x2d28\x2d1804-40.mount 2.690s snap-gnome\x2dcharacters-258.mount 2.680s ModemManager.service 2.640s snap-whatsdesk-17.mount 2.456s snap-gnome\x2dcalculator-352.mount lines 1-23...skipping... 30.189s NetworkManager-wait-online.service 8.042s snapd.service 6.943s gpu-manager.service 6.807s keyboard-setup.service 6.684s dev-sdb2.device 6.409s networkd-dispatcher.service 4.512s snap-gnome\x2d3\x2d26\x2d1604-78.mount 4.273s snap-gnome\x2dsystem\x2dmonitor-81.mount 4.246s snap-gnome\x2dlogs-45.mount 4.055s snap-gnome\x2d3\x2d26\x2d1604-74.mount 3.743s tor@default.service 3.563s snap-gnome\x2dcharacters-254.mount 3.549s snap-gnome\x2dsystem\x2dmonitor-77.mount 3.489s snap-opera-34.mount 3.445s NetworkManager.service 3.069s snap-core18-782.mount 3.044s systemd-journal-flush.service 2.977s snap-gnome\x2d3\x2d28\x2d1804-31.mount 2.828s snap-gnome\x2d3\x2d28\x2d1804-40.mount 2.690s snap-gnome\x2dcharacters-258.mount 2.680s ModemManager.service 2.640s snap-whatsdesk-17.mount 2.456s snap-gnome\x2dcalculator-352.mount 2.432s snap-gnome\x2dcharacters-206.mount 2.416s snap-gnome\x2dcalculator-406.mount 2.325s systemd-fsck@dev-disk-by\x2duuid-14984518\x2d2661\x2d461a\x2d840e\x2de485956c774f.service 2.294s apparmor.service 2.194s snap-core-6818.mount 1.939s accounts-daemon.service 1.910s udisks2.service 1.850s snap-gnome\x2d3\x2d26\x2d1604-82.mount 1.847s grub-common.service 1.840s snap-vlc-770.mount 1.721s snap-telegram\x2ddesktop-715.mount 1.707s systemd-fsck@dev-disk-by\x2duuid-F02C\x2dC0B2.service 1.691s snap-gnome\x2dsystem\x2dmonitor-70.mount 1.672s snap-core18-941.mount 1.648s snap-shotcut-43.mount 1.580s thermald.service 1.561s wpa_supplicant.service 1.520s apport.service 1.297s plymouth-read-write.service 1.269s snap-shotcut-41.mount 1.203s snap-whatsdesk-15.mount 1.141s snap-chromium\x2dffmpeg-9.mount 1.124s bolt.service 1.089s networking.service 1.065s snap-opera-33.mount 1.037s systemd-udevd.service 1.026s snap-opera-35.mount 1.007s snap-shotcut-45.mount 998ms bluetooth.service 995ms snap-chromium\x2dffmpeg-11.mount 988ms tor.serviceMerci de votre aideCode:systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @49.937s └─multi-user.target @49.937s └─kerneloops.service @49.930s +7ms └─network-online.target @49.928s └─network.target @19.731s └─NetworkManager.service @16.285s +3.445s └─dbus.service @15.467s └─basic.target @15.418s └─sockets.target @15.417s └─snapd.socket @15.413s +2ms └─sysinit.target @15.361s └─apparmor.service @13.048s +2.294s └─local-fs.target @13.042s └─run-user-1000-gvfs.mount @36.150s └─run-user-1000.mount @24.854s └─local-fs-pre.target @9.567s └─keyboard-setup.service @2.759s +6.807s └─systemd-journald.socket @2.699s └─system.slice @2.698s └─-.slice @2.674s
-----