Bonsoir,

voici mon deuxième "problème" (enfin je crois bien) depuis mon installation de fedora 18. En fait, le démarrage en lui-même est très rapide, beaucoup plus que sous fedora 17, et avec un ssd+hdd j'obtiens :
Jun 8 21:52:50 PC3 systemd[1]: Startup finished in 1.290s (kernel) + 2.371s (initrd) + 8.121s (userspace) = 11.783s.

Par contre, une fois le démarrage effectué, le sysytème met pratiquement 1 minute pour afficher le bureau et me donner la main (en soit, c'est pas si grave, mais je suis étonnée, j'ai l'impression que ça n'a jamais été aussi lent). Voilà la suite du cat /var/log/messages après la ligne startup finished. Je n'arrive pas à traduire et à trouver la raison de cette lenteur...
Jun  8 21:52:50 PC3 systemd[1]: Startup finished in 1.290s (kernel) + 2.371s (initrd) + 8.121s (userspace) = 11.783s.
Jun  8 21:52:50 PC3 colord: Profile added: icc-3e2a948f375571589326b4c473540b10
Jun  8 21:52:50 PC3 systemd[1]: Stopping Sendmail Mail Transport Client...
Jun  8 21:52:50 PC3 systemd[1]: Stopping Sendmail Mail Transport Agent...
Jun  8 21:52:50 PC3 systemd[1]: Starting Sendmail Mail Transport Agent...
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.239+0000: 1283: info : libvirt version: 0.10.2.5, package: 1.fc18 (Fedora Project, 2013-05-19-23:05:52, buildvm-18.phx2.fedoraproject.org)
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.239+0000: 1283: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so not accessible
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.254+0000: 1283: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so not accessible
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.269+0000: 1283: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.272+0000: 1283: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible
Jun  8 21:52:50 PC3 systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Jun  8 21:52:50 PC3 systemd[1]: Started Sendmail Mail Transport Agent.
Jun  8 21:52:50 PC3 systemd[1]: Starting Sendmail Mail Transport Client...
Jun  8 21:52:50 PC3 goa[1426]: goa-daemon version 3.6.3 starting [main.c:112, main()]
Jun  8 21:52:50 PC3 systemd[1]: Started Sendmail Mail Transport Client.
Jun  8 21:52:50 PC3 libvirtd[1283]: 2013-06-08 19:52:50.987+0000: 1383: error : virNWFilterSnoopLeaseFileRefresh:1903 : open("/var/run/libvirt/network/nwfilter.ltmp"): Aucun fichier ou dossier de ce type
Jun  8 21:52:51 PC3 gcr-prompter[1459]: Gtk: Theme directory scalable/status of theme Snow Sabre black has no size field
Jun  8 21:52:52 PC3 kernel: [   14.185668] cgroup: libvirtd (1383) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  8 21:52:52 PC3 kernel: [   14.185675] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
Jun  8 21:52:52 PC3 kernel: [   14.185761] cgroup: libvirtd (1383) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  8 21:52:52 PC3 kernel: [   14.185854] cgroup: libvirtd (1383) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  8 21:52:53 PC3 /usr/sbin/irqbalance: WARNING: MSI interrupts found in /proc/interrupts
Jun  8 21:52:53 PC3 /usr/sbin/irqbalance: But none found in sysfs, you need to update your kernel
Jun  8 21:52:53 PC3 /usr/sbin/irqbalance: Until then, IRQs will be improperly classified
Jun  8 21:52:56 PC3 chronyd[501]: Selected source 88.190.17.126
Jun  8 21:52:56 PC3 chronyd[501]: System clock wrong by 12.812384 seconds, adjustment started
Jun  8 21:52:59 PC3 kernel: [   21.611775] nouveau  [  PTHERM][0000:02:00.0] temperature (92 C) went below the 'downclock' threshold
Jun  8 21:52:59 PC3 systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  8 21:53:00 PC3 systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  8 21:53:08 PC3 NetworkManager[565]: <info> (em1): IP6 addrconf timed out or failed.
Jun  8 21:53:08 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun  8 21:53:08 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun  8 21:53:08 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun  8 21:53:15 PC3 gnome-session[711]: WARNING: Detected that screensaver has left the bus
Jun  8 21:54:07 PC3 dbus-daemon[445]: dbus[445]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  8 21:54:07 PC3 dbus[445]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  8 21:54:07 PC3 dbus-daemon[445]: dbus[445]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  8 21:54:07 PC3 dbus[445]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  8 21:54:07 PC3 dbus-daemon[445]: Launching FprintObject
Jun  8 21:54:07 PC3 dbus-daemon[445]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jun  8 21:54:07 PC3 dbus-daemon[445]: ** Message: entering main loop
Est-ce que quelque chose parait anormal ? Ou peut-être que je deviens parano...
Merci à nouveau !!
Bonjour,

Perso j'ai désactivé Sendmail, je trouvais qu'au démarrage ça ralentissait un peu le bouzin, et je n'en ai pas l'utilité.

Sinon, chez moi je ne trouve pas que Fedora 18 boote plus vite que Fedora 17.

Dans mon portable j'ai un SSD, et ça démarre à toute allure passées les commandes BIOS, et l'affichage de KDE est très rapide également, plus rapide que dans mon desktop qui démarre sur un WD Black Caviar.

Pas normal que tu attendes donc une minute au milieu des processus de démarrage, tu auras noté que tu as quelques messages d'erreur, notamment celui-ci :
Jun  8 21:53:15 PC3 gnome-session[711]: WARNING: Detected that screensaver has left the bus
qui a l'air de faire perdre du temps pour les processus de démarrage suivants, le système doit certainement re-créer un ou des fichiers, tu as déjà de la chance que ça passe et que ta session s'ouvre.

II faudrait éplucher tous les var/log , pas seulement var/log/messages pour trouver éventuellement d'autres infos.

(edit : ) Déjà, un coup de Google pour diagnostiquer ce que signifie la ligne citée, c'est peut-être une piste...?

Si ça tombe, à la prochaine Màj de kernel tu n'auras plus ce souci.
Si il y a un problème avec ton "screensaver" (économiseur d'écran) essaye d'en changer pour voir si cela améliore ton démarrage.
chepioq wrote:Si il y a un problème avec ton "screensaver" (économiseur d'écran) essaye d'en changer pour voir si cela améliore ton démarrage.
Je ne comprends pas... je n'ai pas de screensaver. Je croyais d'ailleurs qu'il n'y en avait plus par défaut.

@paradise : une recherche google m'amène vers des tas de posts qui n'ont pas l'air d'être vraiment lié à mon problème. Je vais tout de même continuer à chercher de ce coté là. Merci !
Un nouveau test après avoir changé le fond d'écarn -puisque j'avais pas de screensaver)...
Jun  9 12:00:37 PC3 systemd[1]: Startup finished in 1.290s (kernel) + 2.379s (initrd) + 8.455s (userspace) = 12.126s.
Jun  9 12:00:37 PC3 systemd[1]: Started LSB: Starts and stops login and scanning of iSCSI devices..
Jun  9 12:00:37 PC3 dbus-daemon[446]: Starting iscsi (via systemctl):  [  OK  ]
Jun  9 12:00:37 PC3 systemd[1]: Stopping Sendmail Mail Transport Client...
Jun  9 12:00:37 PC3 systemd[1]: Stopping Sendmail Mail Transport Agent...
Jun  9 12:00:37 PC3 systemd[1]: Starting Sendmail Mail Transport Agent...
Jun  9 12:00:37 PC3 libvirtd[1191]: 2013-06-09 10:00:37.612+0000: 1191: info : libvirt version: 0.10.2.5, package: 1.fc18 (Fedora Project, 2013-05-19-23:05:52, buildvm-18.phx2.fedoraproject.org)
Jun  9 12:00:37 PC3 libvirtd[1191]: 2013-06-09 10:00:37.612+0000: 1191: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so not accessible
Jun  9 12:00:37 PC3 libvirtd[1191]: 2013-06-09 10:00:37.618+0000: 1191: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so not accessible
Jun  9 12:00:37 PC3 libvirtd[1191]: 2013-06-09 10:00:37.627+0000: 1191: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Jun  9 12:00:37 PC3 libvirtd[1191]: 2013-06-09 10:00:37.628+0000: 1191: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible
Jun  9 12:00:37 PC3 systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Jun  9 12:00:37 PC3 systemd[1]: Started Sendmail Mail Transport Agent.
Jun  9 12:00:37 PC3 systemd[1]: Starting Sendmail Mail Transport Client...
Jun  9 12:00:37 PC3 colord: Device added: xrandr-Samsung Electric Company-SyncMaster-H4JXA05895
Jun  9 12:00:37 PC3 colord: Profile added: icc-3e2a948f375571589326b4c473540b10
Jun  9 12:00:38 PC3 systemd[1]: Started Sendmail Mail Transport Client.
Jun  9 12:00:38 PC3 goa[1426]: goa-daemon version 3.6.3 starting [main.c:112, main()]
Jun  9 12:00:38 PC3 libvirtd[1191]: 2013-06-09 10:00:38.833+0000: 1373: error : virNWFilterSnoopLeaseFileRefresh:1903 : open("/var/run/libvirt/network/nwfilter.ltmp"): Aucun fichier ou dossier de ce type
Jun  9 12:00:39 PC3 gcr-prompter[1448]: Gtk: Theme directory scalable/status of theme Snow Sabre black has no size field
Jun  9 12:00:40 PC3 kernel: [   15.270318] cgroup: libvirtd (1373) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 12:00:40 PC3 kernel: [   15.270325] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
Jun  9 12:00:40 PC3 kernel: [   15.270416] cgroup: libvirtd (1373) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 12:00:40 PC3 kernel: [   15.270508] cgroup: libvirtd (1373) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 12:00:41 PC3 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/20-chrony' took too long; killing it.
Jun  9 12:00:41 PC3 NetworkManager[565]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/20-chrony' timed out.
Jun  9 12:00:42 PC3 /usr/sbin/irqbalance: WARNING: MSI interrupts found in /proc/interrupts
Jun  9 12:00:42 PC3 /usr/sbin/irqbalance: But none found in sysfs, you need to update your kernel
Jun  9 12:00:42 PC3 /usr/sbin/irqbalance: Until then, IRQs will be improperly classified
Jun  9 12:00:47 PC3 systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  9 12:00:47 PC3 systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  9 12:00:48 PC3 chronyd[501]: Selected source 91.121.60.158
Jun  9 12:00:48 PC3 chronyd[501]: System clock wrong by 15.067480 seconds, adjustment started
Jun  9 12:00:55 PC3 NetworkManager[565]: <info> (em1): IP6 addrconf timed out or failed.
Jun  9 12:00:55 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun  9 12:00:55 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun  9 12:00:55 PC3 NetworkManager[565]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun  9 12:01:34 PC3 dbus-daemon[446]: dbus[446]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 12:01:34 PC3 dbus[446]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 12:01:34 PC3 dbus-daemon[446]: dbus[446]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 12:01:34 PC3 dbus[446]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 12:01:34 PC3 dbus-daemon[446]: Launching FprintObject
Jun  9 12:01:34 PC3 dbus-daemon[446]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jun  9 12:01:34 PC3 dbus-daemon[446]: ** Message: entering main loop
Il n'y a pas de problème de screensaver pourtant le "démarrage" (afficahge du bureau) est toujours aussi lent. NetworkManager semble prendre du temps. Je signale aussi que c'est mon pc fixe et que je n'utilise qu'une connection filaire dessus.

et #dmesg au démarrage : 
[    2.431673] [drm] Initialized nouveau 1.1.0 20120801 for 0000:02:00.0 on minor 0
[    2.622857] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    2.648932] scsi 6:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
[    2.649653] scsi 6:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
[    2.650252] scsi 6:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
[    2.650749] scsi 6:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
[    2.651092] sd 6:0:0:0: Attached scsi generic sg3 type 0
[    2.651269] sd 6:0:0:1: Attached scsi generic sg4 type 0
[    2.651492] sd 6:0:0:2: Attached scsi generic sg5 type 0
[    2.651669] sd 6:0:0:3: Attached scsi generic sg6 type 0
[    2.658041] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[    2.664054] sd 6:0:0:1: [sdd] Attached SCSI removable disk
[    2.664785] sd 6:0:0:2: [sde] Attached SCSI removable disk
[    2.665524] sd 6:0:0:3: [sdf] Attached SCSI removable disk
[    2.695641] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: discard
[    2.758814] nouveau  [  PTHERM][0000:02:00.0] temperature (92 C) went below the 'downclock' threshold
[    2.780379] systemd-journald[50]: Received SIGTERM
[    2.827051] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.846261] ata6.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
[    2.846268] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    2.857976] type=1404 audit(1370779039.079:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
[    2.865243] ata6.00: configured for UDMA/133
[    2.865436] scsi 5:0:0:0: Direct-Access     ATA      SAMSUNG HD103SJ  1AJ1 PQ: 0 ANSI: 5
[    2.865632] sd 5:0:0:0: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    2.865644] sd 5:0:0:0: Attached scsi generic sg7 type 0
[    2.865724] sd 5:0:0:0: [sdg] Write Protect is off
[    2.865728] sd 5:0:0:0: [sdg] Mode Sense: 00 3a 00 00
[    2.865773] sd 5:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.881102]  sdg: unknown partition table
[    2.881365] sd 5:0:0:0: [sdg] Attached SCSI disk
[    2.913196] SELinux: 2048 avtab hash slots, 97658 rules.
[    2.929867] SELinux: 2048 avtab hash slots, 97658 rules.
[    3.471563] SELinux:  9 users, 15 roles, 4399 types, 246 bools, 1 sens, 1024 cats
[    3.471569] SELinux:  83 classes, 97658 rules
[    3.477099] SELinux:  Permission attach_queue in class tun_socket not defined in policy.
[    3.477104] SELinux: the above unknown classes and permissions will be allowed
[    3.477116] SELinux:  Completing initialization.
[    3.477117] SELinux:  Setting up existing superblocks.
[    3.477133] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[    3.477140] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[    3.477155] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
[    3.477166] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[    3.477177] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[    3.477210] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs
[    3.478046] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[    3.478052] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[    3.479742] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[    3.479753] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
[    3.479758] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[    3.479784] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs
[    3.479792] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
[    3.479801] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[    3.479823] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[    3.480505] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts
[    3.480510] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[    3.480528] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[    3.480622] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[    3.480660] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480666] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
[    3.480669] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480679] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480711] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480722] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480727] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480732] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480737] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480752] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[    3.480768] SELinux: initialized (dev sda2, type ext4), uses xattr
[    3.498837] type=1403 audit(1370779039.720:3): policy loaded auid=4294967295 ses=4294967295
[    3.506432] systemd[1]: Successfully loaded SELinux policy in 650.757ms.
[    3.603462] systemd[1]: Relabelled /dev and /run in 70.975ms.
[    3.728944] systemd-readahead[256]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day.
[    3.735476] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[    3.770695] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs
[    3.773727] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[    3.800336] EXT4-fs (sda2): re-mounted. Opts: discard
[    3.854133] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts
[    3.879375] systemd-udevd[264]: starting version 201
[    3.949614] kvm: Nested Virtualization enabled
[    3.961810] tun: Universal TUN/TAP device driver, 1.6
[    3.961817] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    4.045279] parport_pc 00:05: reported by Plug and Play ACPI
[    4.045332] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[    4.070548] i2c i2c-10: nForce2 SMBus adapter at 0x600
[    4.070572] i2c i2c-11: nForce2 SMBus adapter at 0x700
[    4.157213] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[    4.157469] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
[    4.157480] forcedeth 0000:00:07.0: setting latency timer to 64
[    4.212936] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 18
[    4.240853] MCE: In-kernel MCE decoding enabled.
[    4.247033] EDAC MC: Ver: 3.0.0
[    4.250924] AMD64 EDAC driver v3.4.0
[    4.322349] microcode: AMD CPU family 0xf not supported
[    4.328525] powernow-k8: fid 0x14 (2800 MHz), vid 0x9
[    4.328531] powernow-k8: fid 0x12 (2600 MHz), vid 0xb
[    4.328533] powernow-k8: fid 0x10 (2400 MHz), vid 0xd
[    4.328534] powernow-k8: fid 0xe (2200 MHz), vid 0xf
[    4.328535] powernow-k8: fid 0xc (2000 MHz), vid 0x11
[    4.328537] powernow-k8: fid 0x2 (1000 MHz), vid 0x12
[    4.328585] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 5400+ (2 cpu cores) (version 2.20.00)
[    4.415803] Adding 2064380k swap on /dev/sda3.  Priority:-1 extents:1 across:2064380k SS
[    4.417551] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    4.417572] SELinux: initialized (dev sda1, type ext4), uses xattr
[    4.453581] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: discard
[    4.453600] SELinux: initialized (dev sda5, type ext4), uses xattr
[    4.567299] EXT4-fs (sdg): mounted filesystem with ordered data mode. Opts: (null)
[    4.567330] SELinux: initialized (dev sdg, type ext4), uses xattr
[    4.601062] ppdev: user-space parallel port driver
[    4.678599] forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x1374 @ 1, addr 00:1f:c6:a7:3d:3d
[    4.678606] forcedeth 0000:00:07.0: highdma pwrctl mgmt gbit lnktim msi desc-v3
[    4.684620] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 22
[    4.684631] hda_intel: Disabling MSI
[    4.684665] snd_hda_intel 0000:00:05.0: setting latency timer to 64
[    4.695603] ALSA sound/pci/hda/hda_intel.c:1724 0000:00:05.0: Enable delay in RIRB handling
[    4.720195] systemd-udevd[305]: renamed network interface eth0 to em1
[    4.736861] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[    4.736937] SELinux: initialized (dev sdb1, type ext4), uses xattr
[    5.373331] hda_codec: AD1988: BIOS auto-probing.
[    5.397038] ALSA sound/pci/hda/hda_auto_parser.c:335 autoconfig: line_outs=1 (0x12/0x0/0x0/0x0/0x0) type:line
[    5.397050] ALSA sound/pci/hda/hda_auto_parser.c:339    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    5.397056] ALSA sound/pci/hda/hda_auto_parser.c:343    hp_outs=1 (0x11/0x0/0x0/0x0/0x0)
[    5.397061] ALSA sound/pci/hda/hda_auto_parser.c:344    mono: mono_out=0x0
[    5.397065] ALSA sound/pci/hda/hda_auto_parser.c:347    dig-out=0x1b/0x0
[    5.397069] ALSA sound/pci/hda/hda_auto_parser.c:348    inputs:
[    5.397076] ALSA sound/pci/hda/hda_auto_parser.c:352      Front Mic=0x14
[    5.397081] ALSA sound/pci/hda/hda_auto_parser.c:352      Rear Mic=0x17
[    5.397086] ALSA sound/pci/hda/hda_auto_parser.c:352      Line=0x15
[    5.397090] ALSA sound/pci/hda/hda_auto_parser.c:352      CD=0x18
[    5.958275] input: HDA NVidia Line as /devices/pci0000:00/0000:00:05.0/sound/card1/input4
[    5.958754] input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:05.0/sound/card1/input5
[    5.958964] input: HDA NVidia Line Out as /devices/pci0000:00/0000:00:05.0/sound/card1/input6
[    5.960977] EDAC amd64: DRAM ECC enabled.
[    5.960996] EDAC amd64: K8 revF or later detected (node 0).
[    5.961078] EDAC MC: DCT0 chip selects:
[    5.961083] EDAC amd64: MC: 0:     0MB 1:     0MB
[    5.961087] EDAC amd64: MC: 2:   512MB 3:     0MB
[    5.961091] EDAC amd64: MC: 4:   512MB 5:   512MB
[    5.961095] EDAC amd64: MC: 6:   512MB 7:     0MB
[    5.961142] EDAC amd64: CS2: Unbuffered DDR2 RAM
[    5.961145] EDAC amd64: CS4: Unbuffered DDR2 RAM
[    5.961148] EDAC amd64: CS5: Unbuffered DDR2 RAM
[    5.961151] EDAC amd64: CS6: Unbuffered DDR2 RAM
[    5.961517] EDAC MC0: Giving out device to 'amd64_edac' 'K8': DEV 0000:00:18.2
[    5.961638] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV '0000:00:18.2' (POLLED)
[    5.965269] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
[    6.801857] systemd[1]: Unit rngd.service entered failed state.
[    7.266652] Loading iSCSI transport class v2.0-870.
[    7.288689] iscsi: registered transport (tcp)
[    7.354463] iscsi: registered transport (iser)
[    7.367212] libcxgbi:libcxgbi_init_module: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
[    7.367221] libcxgbi:ddp_setup_host_page_size: system PAGE 4096, ddp idx 0.
[    7.380550] Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010)
[    7.381416] iscsi: registered transport (cxgb3i)
[    7.398956] Chelsio T4 iSCSI Driver cxgb4i v0.9.1 (Aug. 2010)
[    7.400335] iscsi: registered transport (cxgb4i)
[    7.419533] cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.16 (Dec 05, 2012)
[    7.428229] Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.2.2 (Apr 25, 2012)
[    7.428977] iscsi: registered transport (bnx2i)
[    7.449988] iscsi: registered transport (be2iscsi)
[    7.449996] In beiscsi_module_init, tt=ffffffffa0519000
[    7.650601] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    7.682149] Ebtables v2.0 registered
[    7.837622] Bluetooth: Core ver 2.16
[    7.837798] NET: Registered protocol family 31
[    7.837800] Bluetooth: HCI device and connection manager initialized
[    7.837816] Bluetooth: HCI socket layer initialized
[    7.837819] Bluetooth: L2CAP socket layer initialized
[    7.837827] Bluetooth: SCO socket layer initialized
[    7.840387] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[    7.840436] forcedeth 0000:00:07.0 em1: MSI enabled
[    7.857333] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.857340] Bluetooth: BNEP filters: protocol multicast
[    7.857356] Bluetooth: BNEP socket layer initialized
[    7.919746] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    8.729142] fuse init (API version 7.21)
[    8.757512] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[    8.766228] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
[    9.726227] ALSA sound/core/pcm_lib.c:352 BUG: pcmC0D0c:0, pos = 5461, buffer size = 5461, period size = 2730
[   14.586940] cgroup: libvirtd (1326) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[   14.586947] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
[   14.589973] cgroup: libvirtd (1326) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[   14.591762] cgroup: libvirtd (1326) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Quels autres fichiers de /var/log dois-je regarder ?
Merci !
Que renvoie la commande : 
systemd-analyze blame
Effectivement, il y a un problème au niveau de IPV6 :
Jun  9 12:00:55 PC3 NetworkManager[565]: <info> (em1): IP6 addrconf timed out or failed.
Du coup, le système perd du temps à re-créer les fichiers.

Que donne la commande :
journalctl | grep p37p1
en changeant bien sûr "p37p1" par le nom de ta connection ?
Je pense que tu as la gestion de IPV6 en "automatique", et si ton réseau ne gère pas IPV6, le temps imparti est écoulé : "timed out".

Tu peux éditer NetworkManager par la commande 
nm-connection-editor
puis tu édites ta connexion dans les paramètres IPV6 en cochant l'onglet Methode : "ignorer" au lieu de "automatique", ça devrait marcher au reboot.
@chepioq : Je pense que le problème se situe "après" car tout se passe bien et va à la "bonne vitesse" jusqu'à la fin du boot et le 
Jun  9 12:00:37 PC3 systemd[1]: Startup finished in 1.290s (kernel) + 2.379s (initrd) + 8.455s (userspace) = 12.126s.
La commande donne : (aucune valeur ne me parait anormalement élevée...) 
# systemd-analyze blame
          3.333s NetworkManager-wait-online.service
          1.966s systemd-udev-settle.service
          1.343s abrt-uefioops.service
           979ms firewalld.service
           813ms iscsid.service
           513ms gdm.service
           459ms chronyd.service
           451ms backup.mount
           436ms accounts-daemon.service
           424ms sm-client.service
           356ms systemd-logind.service
           325ms lm_sensors.service
           314ms rtkit-daemon.service
           312ms avahi-daemon.service
           308ms fedora-storage-init.service
           308ms restorecond.service
           224ms iscsi.service
           220ms abrt-ccpp.service
           220ms systemd-udev-trigger.service
           217ms mcelog.service
           192ms fedora-loadmodules.service
           174ms systemd-fsck@dev-disk-by\x2duuid-d5052c2f\x2de15b\x2d4fad\x2d8102\x2d4f61f1b2897e.service
           153ms systemd-udevd.service
           149ms systemd-fsck@dev-disk-by\x2duuid-3b5d3626\x2d6060\x2d48fe\x2daa27\x2d16e0593db6ca.service
           131ms ksmtuned.service
           129ms plymouth-start.service
           127ms NetworkManager.service
           122ms abrt-vmcore.service
           121ms systemd-tmpfiles-setup.service
           117ms systemd-vconsole-setup.service
           117ms polkit.service
           106ms colord.service
           104ms udisks2.service
            97ms fedora-storage-init-late.service
            94ms irqbalance.service
            86ms alsa-restore.service
            86ms fedora-readonly.service
            77ms systemd-modules-load.service
            76ms home-balustre-Guitare.mount
            74ms sshd.service
            66ms dev-hugepages.mount
            63ms home-balustre-Vid\xc3\xa9os.mount
            62ms sys-kernel-debug.mount
            61ms lvm2-monitor.service
            60ms bluetooth.service
            60ms dev-mqueue.mount
            53ms systemd-remount-fs.service
            48ms systemd-fsck@dev-disk-by\x2duuid-4defcb5f\x2d9e4a\x2d46a6\x2db9a2\x2dc1ccb52d1faf.service
            45ms systemd-sysctl.service
            45ms tmp.mount
            42ms ksm.service
            42ms systemd-readahead-replay.service
            40ms systemd-readahead-collect.service
            39ms home-balustre-Images.mount
            35ms systemd-journal-flush.service
            34ms systemd-update-utmp-runlevel.service
            32ms systemd-user-sessions.service
            32ms data.mount
            32ms home.mount
            24ms upower.service
            22ms rpcbind.service
            19ms home-balustre-Musique.mount
            18ms auditd.service
            17ms systemd-readahead-done.service
            14ms boot.mount
            11ms dev-disk-by\x2duuid-b5653d1b\x2d9be6\x2d428f\x2db488\x2de6c2db7cf2c5.swap
             9ms systemd-random-seed-load.service
             6ms sys-kernel-config.mount
             3ms home-balustre-Documents.mount

@paradise : voilà donc une piste... Voici le retour de la commande : 
# journalctl | grep em1
juin 09 18:42:24 PC3.home systemd-udevd[320]: renamed network interface eth0 to em1
juin 09 18:42:27 PC3.home NetworkManager[560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-em1 ...
juin 09 18:42:27 PC3.home NetworkManager[560]: ifcfg-rh:     read connection 'em1'
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): carrier is OFF
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): new Ethernet device (driver: 'forcedeth' ifindex: 2)
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): exported as /org/freedesktop/NetworkManager/Devices/0
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): bringing up device.
juin 09 18:42:27 PC3.home kernel: forcedeth 0000:00:07.0 em1: MSI enabled
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): carrier now ON (device state 20)
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): preparing device.
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): deactivating device (reason 'managed') [2]
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Auto-activating connection 'em1'.
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) starting connection 'em1'
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) scheduled...
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) started...
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 2 of 5 (Device Configure) scheduled...
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) complete.
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 2 of 5 (Device Configure) starting...
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> (em1): device state change: prepare -> config (reason 'none') [40 50 0]
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 2 of 5 (Device Configure) successful.
juin 09 18:42:27 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 2 of 5 (Device Configure) complete.
juin 09 18:42:29 PC3.home avahi-daemon[440]: Registering new address record for fe80::21f:c6ff:fea7:3d3d on em1.*.
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) scheduled.
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) started...
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> (em1): device state change: config -> ip-config (reason 'none') [50 70 0]
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Beginning DHCPv4 transaction (timeout in 45 seconds)
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Beginning IP6 addrconf.
juin 09 18:42:29 PC3.home avahi-daemon[440]: Withdrawing address record for fe80::21f:c6ff:fea7:3d3d on em1.
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) complete.
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> (em1): DHCPv4 state changed nbi -> preinit
juin 09 18:42:29 PC3.home dhclient[1037]: Listening on LPF/em1/00:1f:c6:a7:3d:3d
juin 09 18:42:29 PC3.home dhclient[1037]: Sending on   LPF/em1/00:1f:c6:a7:3d:3d
juin 09 18:42:29 PC3.home dhclient[1037]: DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x10f0404b)
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> (em1): DHCPv4 state changed preinit -> reboot
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
juin 09 18:42:29 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) started...
juin 09 18:42:29 PC3.home avahi-daemon[440]: Joining mDNS multicast group on interface em1.IPv4 with address 192.168.1.13.
juin 09 18:42:29 PC3.home avahi-daemon[440]: New relevant interface em1.IPv4 for mDNS.
juin 09 18:42:29 PC3.home avahi-daemon[440]: Registering new address record for 192.168.1.13 on em1.IPv4.
juin 09 18:42:30 PC3.home NetworkManager[560]: <info> (em1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
juin 09 18:42:30 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) complete.
juin 09 18:42:30 PC3.home NetworkManager[560]: <info> (em1): device state change: secondaries -> activated (reason 'none') [90 100 0]
juin 09 18:42:30 PC3.home avahi-daemon[440]: Registering new address record for fe80::21f:c6ff:fea7:3d3d on em1.*.
juin 09 18:42:30 PC3.home NetworkManager[560]: <info> Policy set 'em1' (em1) as default for IPv4 routing and DNS.
juin 09 18:42:30 PC3.home NetworkManager[560]: <info> Activation (em1) successful, device activated.
juin 09 18:42:50 PC3.home NetworkManager[560]: <info> (em1): IP6 addrconf timed out or failed.
juin 09 18:42:50 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
juin 09 18:42:50 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) started...
juin 09 18:42:50 PC3.home NetworkManager[560]: <info> Activation (em1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
OK, fais ce que je te propose dans mon post suivant, je pense que c'est la soluce.
paradise wrote:Je pense que tu as la gestion de IPV6 en "automatique", et si ton réseau ne gère pas IPV6, le temps imparti est écoulé : "timed out".

Tu peux éditer NetworkManager par la commande 
nm-connection-editor
puis tu édites ta connexion dans les paramètres IPV6 en cochant l'onglet Methode : "ignorer" au lieu de "automatique", ça devrait marcher au reboot.
Ok, modif effectuée... Alors, j'ai toujours environ 45 secondes entre la fin du boot et l'affichage de mon bureau (je reste soit sur une page noire, soit sur le fond d'écran vierge).
Voilà le nouveau "résultat" de cat /var/log/messages 
Jun  9 19:04:42 PC3 systemd[1]: Startup finished in 1.281s (kernel) + 1.922s (initrd) + 8.464s (userspace) = 11.668s.
Jun  9 19:04:42 PC3 colord: Profile added: icc-d7f2d36728de6b2a785375de2042960d
Jun  9 19:04:42 PC3 colord: Profile added: icc-31c4c5beb7945179ea588bcee4252a05
Jun  9 19:04:42 PC3 colord: Profile added: icc-ee266733c701509eebc0d089f44ff3d3
Jun  9 19:04:42 PC3 colord: Profile added: icc-57a2e6077c521cec2dc37094ac0064cc
Jun  9 19:04:42 PC3 colord: Profile added: icc-38aad8400d23c0dee96027ba8db2e2b9
Jun  9 19:04:42 PC3 colord: Profile added: icc-e850597cefed059fa223c17fdef9d8c8
Jun  9 19:04:42 PC3 colord: Profile added: icc-99901730bc39e5f9941416f1900a8eee
Jun  9 19:04:43 PC3 colord: Profile added: icc-5f58d42ead7269afadf867e5f1cea4f0
Jun  9 19:04:43 PC3 dbus-daemon[443]: dbus[443]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun  9 19:04:43 PC3 dbus[443]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun  9 19:04:43 PC3 colord: Profile added: icc-27aa672c5d8449cd1f3ad755224992b3
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.076+0000: 1167: info : libvirt version: 0.10.2.5, package: 1.fc18 (Fedora Project, 2013-05-19-23:05:52, buildvm-18.phx2.fedoraproject.org)
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.076+0000: 1167: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so not accessible
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.084+0000: 1167: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so not accessible
Jun  9 19:04:43 PC3 colord: Profile added: DCP-7060D-Gray..
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.098+0000: 1167: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Jun  9 19:04:43 PC3 colord[1189]: (colord:1189): Cd-WARNING **: failed to get session [pid 1217]: Erreur inconnue -2
Jun  9 19:04:43 PC3 colord: Device added: cups-DCP-7060D
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.127+0000: 1167: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible
Jun  9 19:04:43 PC3 colord: Profile added: DCP7065DN-Gray..
Jun  9 19:04:43 PC3 colord[1189]: (colord:1189): Cd-WARNING **: failed to get session [pid 1217]: Erreur inconnue -2
Jun  9 19:04:43 PC3 colord: Device added: cups-DCP7065DN
Jun  9 19:04:43 PC3 systemd[1]: Started LSB: Starts and stops login and scanning of iSCSI devices..
Jun  9 19:04:43 PC3 dbus-daemon[443]: Starting iscsi (via systemctl):  [  OK  ]
Jun  9 19:04:43 PC3 dbus-daemon[443]: Failed to issue method call: Unit sendmail.service is masked.
Jun  9 19:04:43 PC3 libvirtd[1167]: 2013-06-09 17:04:43.733+0000: 1300: error : virNWFilterSnoopLeaseFileRefresh:1903 : open("/var/run/libvirt/network/nwfilter.ltmp"): Aucun fichier ou dossier de ce type
Jun  9 19:04:43 PC3 colord: Device added: xrandr-Samsung Electric Company-SyncMaster-H4JXA05895
Jun  9 19:04:44 PC3 colord: Profile added: icc-3e2a948f375571589326b4c473540b10
Jun  9 19:04:45 PC3 kernel: [   14.259303] cgroup: libvirtd (1300) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:04:45 PC3 kernel: [   14.259309] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
Jun  9 19:04:45 PC3 kernel: [   14.259392] cgroup: libvirtd (1300) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:04:45 PC3 kernel: [   14.259481] cgroup: libvirtd (1300) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:04:46 PC3 goa[1446]: goa-daemon version 3.6.3 starting [main.c:112, main()]
Jun  9 19:04:47 PC3 /usr/sbin/irqbalance: WARNING: MSI interrupts found in /proc/interrupts
Jun  9 19:04:47 PC3 /usr/sbin/irqbalance: But none found in sysfs, you need to update your kernel
Jun  9 19:04:47 PC3 /usr/sbin/irqbalance: Until then, IRQs will be improperly classified
Jun  9 19:04:47 PC3 gcr-prompter[1482]: Gtk: Theme directory scalable/status of theme Snow Sabre black has no size field
Jun  9 19:04:48 PC3 chronyd[494]: Selected source 94.23.167.40
Jun  9 19:04:52 PC3 systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  9 19:04:52 PC3 systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  9 19:05:11 PC3 gnome-session[767]: WARNING: Detected that screensaver has left the bus
Jun  9 19:05:25 PC3 dbus-daemon[443]: dbus[443]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 19:05:25 PC3 dbus[443]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 19:05:25 PC3 dbus-daemon[443]: dbus[443]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 19:05:25 PC3 dbus[443]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 19:05:25 PC3 dbus-daemon[443]: Launching FprintObject
Jun  9 19:05:25 PC3 dbus-daemon[443]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jun  9 19:05:25 PC3 dbus-daemon[443]: ** Message: entering main loop
Le "screensaver" est de retour... Par ailleurs, je démarre sur un ssd, est-ce que j'ai besoin de readahead ?
Déjà, tu n'as plus les warnings dus à IP6...?

Ce qui me tracasse, ce sont les erreurs de libvirtd, les 2 "Starting Stop" de systemd concernant Read-Ahead Data, et enfin "WARNING: Detected that screensaver has left the bus".

Ça fait beaucoup, je trouve...
paradise wrote:Déjà, tu n'as plus les warnings dus à IP6...?

Ce qui me tracasse, ce sont les erreurs de libvirtd, les 2 "Starting Stop" de systemd concernant Read-Ahead Data, et enfin "WARNING: Detected that screensaver has left the bus".

Ça fait beaucoup, je trouve...
Oui, c'est cool pour l'IP6 🙂 !!
En plus, le problème vient d'être réglé... Alors, d'une part, j'ai fait finalement un 
# yum remove gnome-screensaver
...
Jje crois que le problème venait (entre autre) de la connection automatique et de la gestion du trousseau de clé, mot de passe... Donc j'ai remis la connection auto mais en enlevant le mot de passe du trousseau, et maintenant ça fonctionne à nouveau !

Pour info, voici tout de même le dernier //var/log/messages avec toujours un tas d'erreurs... 
Jun  9 19:31:31 PC3 systemd[1]: Startup finished in 1.281s (kernel) + 1.927s (initrd) + 8.065s (userspace) = 11.274s.
Jun  9 19:31:31 PC3 libvirtd[1151]: 2013-06-09 17:31:31.648+0000: 1218: error : virNWFilterSnoopLeaseFileRefresh:1903 : open("/var/run/libvirt/network/nwfilter.ltmp"): Aucun fichier ou dossier de ce type
Jun  9 19:31:31 PC3 dbus-daemon[439]: dbus[439]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Jun  9 19:31:31 PC3 dbus[439]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Jun  9 19:31:31 PC3 systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jun  9 19:31:31 PC3 dbus-daemon[439]: dbus[439]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jun  9 19:31:31 PC3 dbus[439]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jun  9 19:31:31 PC3 colord: Using config file /etc/colord.conf
Jun  9 19:31:31 PC3 colord: Using mapping database file /var/lib/colord/mapping.db
Jun  9 19:31:31 PC3 colord: Using device database file /var/lib/colord/storage.db
Jun  9 19:31:31 PC3 colord: loaded plugin libcd_plugin_camera.so
Jun  9 19:31:31 PC3 colord: loaded plugin libcd_plugin_scanner.so
Jun  9 19:31:31 PC3 colord: Daemon ready for requests
Jun  9 19:31:31 PC3 dbus-daemon[439]: dbus[439]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jun  9 19:31:31 PC3 dbus[439]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jun  9 19:31:31 PC3 systemd[1]: Started Manage, Install and Generate Color Profiles.
Jun  9 19:31:31 PC3 colord: Profile added: icc-e9dd9b440c82e1862c5c36c857bccb6f
Jun  9 19:31:31 PC3 systemd[1]: Starting CUPS Printing Service...
Jun  9 19:31:31 PC3 systemd[1]: Started CUPS Printing Service.
Jun  9 19:31:31 PC3 colord: Profile added: icc-c21ab8389855a2219cd46309335e0107
Jun  9 19:31:31 PC3 colord: Profile added: icc-6a7cc41a0076b2e1b18ae502271e2ad5
Jun  9 19:31:31 PC3 colord: Profile added: icc-0b49e4b7462d9c0be4ca2ca33a84bfd8
Jun  9 19:31:31 PC3 colord: Profile added: icc-17e4d60642125da094742f5b9e119ef4
Jun  9 19:31:31 PC3 colord: Profile added: icc-e76730df92b29124615047c43dab02df
Jun  9 19:31:31 PC3 dbus-daemon[439]: dbus[439]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun  9 19:31:31 PC3 colord: Profile added: icc-d7f2d36728de6b2a785375de2042960d
Jun  9 19:31:31 PC3 dbus[439]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun  9 19:31:31 PC3 colord: Profile added: icc-31c4c5beb7945179ea588bcee4252a05
Jun  9 19:31:32 PC3 colord: Profile added: icc-ee266733c701509eebc0d089f44ff3d3
Jun  9 19:31:32 PC3 colord: Profile added: icc-57a2e6077c521cec2dc37094ac0064cc
Jun  9 19:31:32 PC3 colord: Profile added: icc-38aad8400d23c0dee96027ba8db2e2b9
Jun  9 19:31:32 PC3 colord: Profile added: icc-e850597cefed059fa223c17fdef9d8c8
Jun  9 19:31:32 PC3 colord: Profile added: icc-99901730bc39e5f9941416f1900a8eee
Jun  9 19:31:32 PC3 colord: Profile added: icc-5f58d42ead7269afadf867e5f1cea4f0
Jun  9 19:31:32 PC3 colord: Profile added: icc-27aa672c5d8449cd1f3ad755224992b3
Jun  9 19:31:32 PC3 colord: Profile added: DCP-7060D-Gray..
Jun  9 19:31:32 PC3 colord[1249]: (colord:1249): Cd-WARNING **: failed to get session [pid 1258]: Erreur inconnue -2
Jun  9 19:31:32 PC3 colord: Device added: cups-DCP-7060D
Jun  9 19:31:32 PC3 colord: Profile added: DCP7065DN-Gray..
Jun  9 19:31:32 PC3 colord[1249]: (colord:1249): Cd-WARNING **: failed to get session [pid 1258]: Erreur inconnue -2
Jun  9 19:31:32 PC3 colord: Device added: cups-DCP7065DN
Jun  9 19:31:32 PC3 colord: Device added: xrandr-Samsung Electric Company-SyncMaster-H4JXA05895
Jun  9 19:31:32 PC3 colord: Profile added: icc-3e2a948f375571589326b4c473540b10
Jun  9 19:31:33 PC3 kernel: [   13.456707] cgroup: libvirtd (1218) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:31:33 PC3 kernel: [   13.456714] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
Jun  9 19:31:33 PC3 kernel: [   13.456853] cgroup: libvirtd (1218) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:31:33 PC3 kernel: [   13.456958] cgroup: libvirtd (1218) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
Jun  9 19:31:36 PC3 /usr/sbin/irqbalance: WARNING: MSI interrupts found in /proc/interrupts
Jun  9 19:31:36 PC3 /usr/sbin/irqbalance: But none found in sysfs, you need to update your kernel
Jun  9 19:31:36 PC3 /usr/sbin/irqbalance: Until then, IRQs will be improperly classified
Jun  9 19:31:36 PC3 chronyd[487]: Selected source 88.191.120.99
Jun  9 19:31:36 PC3 goa[1456]: goa-daemon version 3.6.3 starting [main.c:112, main()]
Jun  9 19:31:41 PC3 systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  9 19:31:41 PC3 systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  9 19:31:56 PC3 dbus-daemon[439]: dbus[439]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 19:31:56 PC3 dbus[439]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Jun  9 19:31:56 PC3 dbus-daemon[439]: dbus[439]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 19:31:56 PC3 dbus[439]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun  9 19:31:56 PC3 dbus-daemon[439]: Launching FprintObject
Jun  9 19:31:56 PC3 dbus-daemon[439]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jun  9 19:31:56 PC3 dbus-daemon[439]: ** Message: entering main loop
Si tu désactives ton screensaver, ça change quelque chose pour ton souci ?
Bon, content pour toi que ce soit réglé !

Dans ton dernier rapport de /var/log/messages, je ne vois plus d'erreurs, souvent il peut y avoir de faux messages d'erreurs qui n'en sont pas vraiment, en tout cas je ne vois plus rien d'anormal.

Je pense que tu peux marquer ton sujet en Résolu ?
paradise wrote:Bon, content pour toi que ce soit réglé !

Dans ton dernier rapport de /var/log/messages, je ne vois plus d'erreurs, souvent il peut y avoir de faux messages d'erreurs qui n'en sont pas vraiment, en tout cas je ne vois plus rien d'anormal.

Je pense que tu peux marquer ton sujet en Résolu ?
Parfait alors ! Merci pour ton aide 😉
Oui, tu avais deux soucis : la gestion de l'IPV6 et le screensaver qui foutait le boxon.

Pour le screensaver, il s'agit d'un bogue, ça doit pouvoir se régler en cherchant avec Google.

edit : bogue peut-être réglé avec la dernière Màj qui comporte (x)screensaver, justement.
balustre wrote:@chepioq : Je pense que le problème se situe "après" car tout se passe bien et va à la "bonne vitesse" jusqu'à la fin du boot et le 
Jun  9 12:00:37 PC3 systemd[1]: Startup finished in 1.290s (kernel) + 2.379s (initrd) + 8.455s (userspace) = 12.126s.
La commande donne : (aucune valeur ne me parait anormalement élevée...) 
# systemd-analyze blame
          3.333s NetworkManager-wait-online.service
          1.966s systemd-udev-settle.service
          1.343s abrt-uefioops.service
           979ms firewalld.service
           813ms iscsid.service
           513ms gdm.service
           459ms chronyd.service
           451ms backup.mount
           436ms accounts-daemon.service
           424ms sm-client.service
           356ms systemd-logind.service
           325ms lm_sensors.service
           314ms rtkit-daemon.service
           312ms avahi-daemon.service
           308ms fedora-storage-init.service
           308ms restorecond.service
           224ms iscsi.service
           220ms abrt-ccpp.service
           220ms systemd-udev-trigger.service
           217ms mcelog.service
           192ms fedora-loadmodules.service
           174ms systemd-fsck@dev-disk-by\x2duuid-d5052c2f\x2de15b\x2d4fad\x2d8102\x2d4f61f1b2897e.service
           153ms systemd-udevd.service
           149ms systemd-fsck@dev-disk-by\x2duuid-3b5d3626\x2d6060\x2d48fe\x2daa27\x2d16e0593db6ca.service
           131ms ksmtuned.service
           129ms plymouth-start.service
           127ms NetworkManager.service
           122ms abrt-vmcore.service
           121ms systemd-tmpfiles-setup.service
           117ms systemd-vconsole-setup.service
           117ms polkit.service
           106ms colord.service
           104ms udisks2.service
            97ms fedora-storage-init-late.service
            94ms irqbalance.service
            86ms alsa-restore.service
            86ms fedora-readonly.service
            77ms systemd-modules-load.service
            76ms home-balustre-Guitare.mount
            74ms sshd.service
            66ms dev-hugepages.mount
            63ms home-balustre-Vid\xc3\xa9os.mount
            62ms sys-kernel-debug.mount
            61ms lvm2-monitor.service
            60ms bluetooth.service
            60ms dev-mqueue.mount
            53ms systemd-remount-fs.service
            48ms systemd-fsck@dev-disk-by\x2duuid-4defcb5f\x2d9e4a\x2d46a6\x2db9a2\x2dc1ccb52d1faf.service
            45ms systemd-sysctl.service
            45ms tmp.mount
            42ms ksm.service
            42ms systemd-readahead-replay.service
            40ms systemd-readahead-collect.service
            39ms home-balustre-Images.mount
            35ms systemd-journal-flush.service
            34ms systemd-update-utmp-runlevel.service
            32ms systemd-user-sessions.service
            32ms data.mount
            32ms home.mount
            24ms upower.service
            22ms rpcbind.service
            19ms home-balustre-Musique.mount
            18ms auditd.service
            17ms systemd-readahead-done.service
            14ms boot.mount
            11ms dev-disk-by\x2duuid-b5653d1b\x2d9be6\x2d428f\x2db488\x2de6c2db7cf2c5.swap
             9ms systemd-random-seed-load.service
             6ms sys-kernel-config.mount
             3ms home-balustre-Documents.mount
Personnellement j'ai ceci : 
[dominique@host ~]$ systemd-analyze time
Startup finished in 1.193s (kernel) + 600ms (initrd) + 1.302s (userspace) = 3.096s
[dominique@host ~]$ systemd-analyze blame
           823ms akmods.service
           675ms akmods-shutdown.service
           159ms plymouth-start.service
           113ms systemd-fsck@dev-disk-by\x2duuid-3aacf37e\x2d185b\x2d4c32\x2db435\x2dd3bf277c72d9.service
           107ms systemd-fsck@dev-disk-by\x2duuid-1f02b994\x2d9220\x2d4a5e\x2dac58\x2d7fa83a28e43c.service
            84ms NetworkManager.service
            53ms chronyd.service
            42ms systemd-udev-trigger.service
            40ms avahi-daemon.service
            39ms systemd-vconsole-setup.service
            37ms rtkit-daemon.service
            32ms mcelog.service
            30ms systemd-binfmt.service
            29ms systemd-logind.service
            26ms lm_sensors.service
            25ms udisks2.service
            24ms systemd-modules-load.service
            20ms systemd-sysctl.service
            19ms sys-kernel-debug.mount
            18ms dev-mqueue.mount
            17ms proc-sys-fs-binfmt_misc.mount
            17ms dev-hugepages.mount
            16ms systemd-udevd.service
            14ms alsa-restore.service
            14ms tmp.mount
            14ms colord.service
            13ms gpm.service
            12ms irqbalance.service
            12ms polkit.service
            12ms dev-disk-by\x2duuid-b70abe30\x2d94cc\x2d4886\x2da85b\x2dc1418d7f02b5.swap
            10ms home.mount
            10ms systemd-tmpfiles-setup.service
             6ms systemd-readahead-replay.service
             6ms systemd-readahead-collect.service
             5ms systemd-random-seed-load.service
             5ms systemd-journal-flush.service
             4ms boot.mount
             4ms systemd-user-sessions.service
             4ms upower.service
             3ms systemd-readahead-done.service
             3ms systemd-remount-fs.service
             2ms systemd-update-utmp-runlevel.service
             2ms sys-kernel-config.mount
             1ms auditd.service
NetworkManager-wait-online.service je l'ai viré et cela fonctionne sans soucis
J'ai aussi désinstallé abrt avec yum, je préfère faire mes rapport de bogues directement sur le bugzilla

J'ai aussi arrêté firewalld, vu que mon routeur à un pare feu performant et paramètrable.

Si tu n'utilises pas le bluetooth, tu peut aussi désactiver bluetooth.service

De même si tu n'est pas en lvm, tu peux désactiver lvm2-monitor.service.

J'ai aussi désactivé (mais avec l'option "mask") fedora-storage-init.service, fedora-loadmodules.service, fedora-storage-init-late.service et fedora-readonly.service, vu que ces services sont déjà lancé par le kernel et sont donc des doublons (c'est pas moi qui le dit, voir ici, paragraphe 6 : http://freedesktop.org/wiki/Software/systemd/Optimizations/ ).