My system does not work as expected. Have looked into hardware problems and memory, but did not find anything up to now Did a new install and although in the begin it worked quit well I had some system freezes. Started to look into journalctl and found quit a lot failed results. e.g. failed to start Flush Journal to Persistent Storage. No idea what that means but it does not sound good. Failed to start login service and cups scheduler where some others. I have copied some pieces of the end of the journalctl. What is wrong with computer or its software. Why a whole bunch of failures and where to start working on the system. ----------------------------------- Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Starting recovery (logdev: internal) Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Metadata corruption detected at __write_verify+0xd0/0xe0 [xfs], xfs_dir3_leaf1 block 0xea5a00 Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Unmount and run xfs_repair Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): First 64 bytes of corrupted metadata buffer: Nov 25 12:22:16 linux-c8ur kernel: ffff96e8ff161000: 00 00 00 00 00 00 00 00 3d f1 00 00 df bc 03 ec ........=....... Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161010: 00 00 00 00 00 ea 5a 00 00 00 07 9c 00 00 20 c5 ......Z....... . Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161020: 57 d3 e4 b0 b3 94 44 28 92 6c d5 8d 3c 0f cb 6a W.....D(.l..<..j Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161030: 00 00 00 00 01 00 00 60 00 96 00 05 00 00 00 00 .......`........ Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): xfs_do_force_shutdown(0x8) called from line 1322 of file ../fs/xfs/xfs_buf.c. Return address = 0xffffffffc0832d55 Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): Corruption of in-memory data detected. Shutting down filesystem Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): Please umount the filesystem and rectify the problem(s) Nov 25 12:22:18 linux-c8ur kernel: XFS (sda5): log mount/recovery failed: error -117 Nov 25 12:22:18 linux-c8ur kernel: XFS (sda5): log mount failed Nov 28 06:30:30 linux-c8ur mtp-probe[7085]: bus: 2, device: 104 was not an MTP device Nov 28 06:30:31 linux-c8ur systemd-logind[7079]: Failed to enable subscription: Connection timed out Nov 28 06:30:31 linux-c8ur dbus[1026]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Nov 28 06:30:31 linux-c8ur systemd-logind[7079]: Failed to fully start up daemon: Connection timed out Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 28 06:30:31 linux-c8ur systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has failed. -- -- The result is failed. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Unit entered failed state. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Nov 28 06:30:31 linux-c8ur systemd[1]: Stopped Login Service. -- Subject: Unit systemd-logind.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has finished shutting down. Nov 28 06:30:31 linux-c8ur systemd[1]: Starting Login Service... -- Subject: Unit systemd-logind.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has begun starting up. Nov 28 06:30:56 linux-c8ur systemd-logind[7090]: Failed to enable subscription: Connection timed out Nov 28 06:30:56 linux-c8ur systemd-logind[7090]: Failed to fully start up daemon: Connection timed out Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 28 06:30:56 linux-c8ur systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has failed. -- -- The result is failed. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Unit entered failed state. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Failed to get journal fields: Bad message -- opensuse:tumbleweed:20161123 Qt: 5.7.0 KDE Frameworks: 5.28.0 kf5-config: 1.0 KDE Plasma: 5.8.3 Kernel: 4.8.9-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org