SUMMARY STEPS TO REPRODUCE 1.Turn off NFS server. 2.Place entries for NFS shares in /etc/fstab (using systemd automount options) on NFS client computer. 3.Start KDE Partition Manager program on NFS client computer. OBSERVED RESULT The program remains in the disk scanning phase for up to 30 minutes. The main program does not start until many cycles of attempting to mount the missing NFS shares is complete. If the NFS server is up, or the NFS entries are removed from /etc/fstab the program starts normally. EXPECTED RESULT The program should only be in the initial disk scanning phase for a very brief period, and then the program should quickly start. SOFTWARE VERSIONS (available in About System) KDE Plasma Version:5.14.2 KDE Frameworks Version:5.51.0 Qt Version:5.11.2 ADDITIONAL INFORMATION I started running journalctl -f just before starting KDE Partition Manager. It became quickly apparent why the program was not starting as attempt after attempt was being made to mount the missing shares on the NFS server that was down. I only posted this issue hours ago on the Manjaro forum and I already had another very competent user confirm exactly the same symptoms and result. Link to Manjaro forum thread: https://forum.manjaro.org/t/kde-partition-manager-long-start-time-confirmed-bug/63698 Journal output from the time KDE Partition Manager was started: $ journalctl -f -- Logs begin at Sun 2018-10-28 07:25:33 MST. -- Oct 31 15:37:58 htpc1 systemd[643]: Starting Mark boot as successful... Oct 31 15:37:58 htpc1 systemd[643]: Started Mark boot as successful. Oct 31 15:42:29 htpc1 plasmashell[811]: trying to show an empty dialog Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Applet "Application Menu" loaded after 0 msec Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Increasing score for "Application Menu" to 97 Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:32 htpc1 plasmashell[811]: trying to show an empty dialog Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:34 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35494, resource id: 33554565, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:42:34 htpc1 kdesu[1366]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 15:42:35 htpc1 kdesud[1370]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 15:42:35 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:37 htpc1 plasmashell[811]: KActivitiesStats( 0x55e9ae5db4a0 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:org.kde.partitionmanager.desktop" score: 13.2286 last: 1541025754 first: 1538808294 Oct 31 15:42:50 htpc1 su[1375]: (to root) htpc on pts/5 Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session opened for user root by (uid=1000) Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session closed for user root Oct 31 15:42:50 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 38305, resource id: 65011729, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:42:50 htpc1 su[1378]: (to root) htpc on pts/5 Oct 31 15:42:50 htpc1 su[1378]: pam_unix(su:session): session opened for user root by (uid=1000) Oct 31 15:42:51 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:42:51 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:42:51 htpc1 kernel: FS-Cache: Loaded Oct 31 15:42:51 htpc1 kernel: FS-Cache: Netfs 'nfs' registered for caching Oct 31 15:42:51 htpc1 kernel: Key type dns_resolver registered Oct 31 15:42:52 htpc1 kernel: NFS: Registering the id_resolver key type Oct 31 15:42:52 htpc1 kernel: Key type id_resolver registered Oct 31 15:42:52 htpc1 kernel: Key type id_legacy registered Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4833, resource id: 54525969, major code: 142 (Unknown), minor code: 3 Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4864, resource id: 69206022, major code: 142 (Unknown), minor code: 3 Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4907, resource id: 69206119, major code: 142 (Unknown), minor code: 3 Oct 31 15:42:57 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5022, resource id: 54525969, major code: 142 (Unknown), minor code: 3 Oct 31 15:42:59 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40252, resource id: 54525969, major code: 15 (QueryTree), minor code: 0 Oct 31 15:43:53 htpc1 mount[1480]: mount.nfs: Connection timed out Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:43:53 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:43:53 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:44:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5180, resource id: 69206119, major code: 142 (Unknown), minor code: 3 Oct 31 15:44:19 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5371, resource id: 69206022, major code: 142 (Unknown), minor code: 3 Oct 31 15:44:24 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44245, resource id: 2097152, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:44:24 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44252, resource id: 2097153, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:44:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP] Oct 31 15:44:55 htpc1 mount[1505]: mount.nfs: Connection timed out Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:44:55 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:44:55 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:45:47 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined Oct 31 15:45:56 htpc1 mount[1678]: mount.nfs: Connection timed out Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:45:56 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:45:56 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:46:57 htpc1 mount[1683]: mount.nfs: Connection timed out Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:46:57 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:46:57 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:47:10 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined Oct 31 15:47:58 htpc1 mount[1687]: mount.nfs: Connection timed out Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:47:58 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:47:58 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:49:00 htpc1 mount[1693]: mount.nfs: Connection timed out Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:49:00 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:49:00 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:50:03 htpc1 mount[1702]: mount.nfs: Connection timed out Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:50:03 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:50:03 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:50:21 htpc1 systemd[1]: Starting Cleanup of Temporary Directories... Oct 31 15:50:21 htpc1 systemd[1]: Started Cleanup of Temporary Directories. Oct 31 15:50:21 htpc1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 31 15:50:21 htpc1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 31 15:50:21 htpc1 kernel: audit: type=1130 audit(1541026221.574:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 31 15:50:21 htpc1 kernel: audit: type=1131 audit(1541026221.574:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 31 15:51:05 htpc1 mount[1709]: mount.nfs: Connection timed out Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:51:05 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:51:05 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:52:09 htpc1 mount[1716]: mount.nfs: Connection timed out Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:52:09 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:52:09 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:53:10 htpc1 mount[1719]: mount.nfs: Connection timed out Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:53:10 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:53:10 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:54:12 htpc1 mount[1727]: mount.nfs: Connection timed out Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:54:12 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:54:12 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:54:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP] Oct 31 15:55:14 htpc1 mount[1735]: mount.nfs: Connection timed out Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:55:14 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:55:14 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:56:15 htpc1 mount[1747]: mount.nfs: Connection timed out Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:56:15 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:56:15 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:57:19 htpc1 mount[1754]: mount.nfs: Connection timed out Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:57:19 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:57:19 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:57:52 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined Oct 31 15:58:24 htpc1 mount[1761]: mount.nfs: Connection timed out Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 15:58:24 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:58:24 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 15:59:26 htpc1 mount[1765]: mount.nfs: Connection timed out Oct 31 15:59:26 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 15:59:26 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 15:59:26 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 15:59:27 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:59:27 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 16:00:28 htpc1 mount[1775]: mount.nfs: Connection timed out Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 16:00:28 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:00:28 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 16:01:01 htpc1 CROND[1789]: (root) CMD (run-parts /etc/cron.hourly) Oct 31 16:01:18 htpc1 kcmshell5[1793]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 16:01:29 htpc1 mount[1785]: mount.nfs: Connection timed out Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 16:01:29 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:01:29 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 16:02:30 htpc1 mount[1798]: mount.nfs: Connection timed out Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 16:02:30 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:02:30 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 16:03:38 htpc1 mount[1801]: mount.nfs: Connection timed out Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 16:03:38 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:03:38 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 16:04:12 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined Oct 31 16:04:39 htpc1 mount[1806]: mount.nfs: Connection timed out Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 16:04:39 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:04:39 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 16:04:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP] Oct 31 16:05:50 htpc1 mount[1812]: mount.nfs: Connection timed out Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 16:05:50 htpc1 systemd[1]: Failed to mount /media/nfs/4tb. Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:05:50 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 16:06:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 8048, resource id: 69206119, major code: 142 (Unknown), minor code: 3 Oct 31 16:06:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 8079, resource id: 2097169, major code: 142 (Unknown), minor code: 3 Oct 31 16:06:13 htpc1 kcmshell5[1822]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 16:06:13 htpc1 kcmshell5[1822]: kcmshell5 with modules ' "org.kde.kcmshell_kcm_kdeconnect" ' is already running. Oct 31 16:06:29 htpc1 kdeconnectd[830]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders Oct 31 16:06:29 htpc1 kdeconnectd[830]: kdeconnect.core: Broadcasting identity packet Oct 31 16:06:51 htpc1 mount[1819]: mount.nfs: Connection timed out Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32 Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'. Oct 31 16:06:51 htpc1 systemd[1]: Failed to mount /media/nfs/3tb. Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner) Oct 31 16:06:51 htpc1 systemd[1]: Mounting /media/nfs/4tb... Oct 31 16:07:52 htpc1 mount[1826]: mount.nfs: Connection timed out Oct 31 16:07:52 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32 Oct 31 16:07:52 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'. Oct 31 16:07:52 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Can anybody retest this bug with KPM from git? There were a lot of changes which might affect it (libparted backend was replaced with sfdisk). fstab is not used at by KPM during the scan (but maybe some of the tools like libparted could have used it...). KPM only checks whether partition is mounted during the scan, it shouldn't try to mount it.
Thank you for your attention on this matter. I installed kpmcore-git and partitionmanager-git. The newer version ran fine without the NFS entries in fstab. Unfortunately, when the NFS entries were returned to fstab the exact same delays were experienced when starting Partition Manager. I can't thank you enough for your rapid response. KDE definitely has a hard working team of developers in place. Please let me know if there are any further diagnostics you would like run.
(In reply to Dal Monico from comment #2) > I installed kpmcore-git and partitionmanager-git. The newer version ran fine > without the NFS entries in fstab. Unfortunately, when the NFS entries were > returned to fstab the exact same delays were experienced when starting > Partition Manager. > Sorry to ask again but can you please double check that it's running sfdisk backend? You can go to Setings->Configure->Advanced and it should show. Or if you enable log in Settings->Panels Shown->Log output. Anyway, I have some idea how we can debug this a bit. But it would be much better if you are actually able to compile kpmcore and partition manager from git. I can help you with that if you are unsure. My idea is to print all commands that are executed to standard output, so that you can see which commands are run (if you run partitionmanager from the terminal). Then we can see what is outputed just before it starts automounting, so that we know which command triggers systemd automount. Then depending on our findings we can thing how to avoid that. So, do you think you'll be able to help me with that? (I have no NFS setup here, so it would be hard for me to solve this without help)
Sorry I did not see your message until just now. I checked and it was indeed running the fsdisk backend. I am going to see if I can get KPM to start properly with a systemd mount unit. I will get back to you with the results. I will try my best to work with you on this issue. I greatly appreciate your efforts to improve KPM.
Well I'm happy to report good news. I found a solution for this by writing a systemd mount unit. I only just now wrote the unit and tested it out briefly. It seems absolutely problem free in my limited testing so far. KDE Partition Manager starts up immediately now. There is no delay when booting with the server offline using systemd to mount the NFS share. NFS share mount unit: ``` /etc/systemd/system/media-nfs-3tb.mount ``` ``` # /etc/systemd/system/media-nfs-3tb.mount # sudo systemctl enable media-nfs-3tb.mount # sudo systemctl start media-nfs-3tb.mount # sudo systemctl daemon-reload # sudo systemctl status media-nfs-3tb.mount # sudo systemctl is-enabled media-nfs-3tb.mount [Unit] Description=Mount 3tb NFS Share Documentation=man systemd.unit man systemd.mount man systemd.special After=remote-fs-pre.target After=network.target Wants=network.target After=network-online.target Wants=network-online.target After=NetworkManager-wait-online.service Wants=NetworkManager-wait-online.service Conflicts=umount.target Before=umount.target DefaultDependencies=no [Mount] Where=/media/nfs/3tb What=192.168.0.102:/srv/nfs/3tb Type=nfs Options=noauto,noatime,nodiratime,x-systemd.automount,x-gvfs-hide,timeo=14,x-systemd.idle-timeout=1min [Install] WantedBy=multi-user.target ``` NFS Automount Unit: ``` /etc/systemd/system/media-nfs-3tb.automount ``` ``` # /etc/systemd/system/media-nfs-3tb.automount # sudo systemctl enable media-nfs-3tb.automount # sudo systemctl start media-nfs-3tb.automount # sudo systemctl daemon-reload # sudo systemctl status media-nfs-3tb.automount # sudo systemctl is-enabled media-nfs-3tb.automount [Unit] Documentation=man systemd.unit man systemd.mount man systemd.special Description=Automount 3tb NFS Share Before=remote-fs.target [Automount] Where=/media/nfs/3tb TimeoutIdleSec=1min ``` I'm sure I probably listed far more services and targets than necessary in the unit. I wanted to make sure that the mount wasn't attempted till much later in the boot process so that the program wouldn't hang. If you do not use ```NetworkManager-wait-online.service``` then remove it's entry (or substitute the service you use in it's place). If you feel this is only a workaround and not a fix, then let me know if you need me to perform further steps. Thank you so much for your quick assistence.
Glad to hear that you found a workaround. I'll lower the importance of the bug since you have a workaround it's a fairly rare setup. In principle it would be good to investigate it a bit more and find what was causing that slow down before. It might be quicker if you can at some point (but maybe not this weekend) join IRC on Freenode #partitionmanager or #calamares channel.
This may be kernel related. There was a similar report just made on the Manjaro forum regarding gparted. The user reported the same long start time on kernels above 4.17. I can't shut down to test different kernels presently as I'm in the middle of an operation on my server that will require it being up for at least 12 hours. https://forum.manjaro.org/t/gparted-scanning-all-devices-in-4-19/64170
(In reply to Dal Monico from comment #7) > This may be kernel related. There was a similar report just made on the > Manjaro forum regarding gparted. The user reported the same long start time > on kernels above 4.17. I can't shut down to test different kernels presently > as I'm in the middle of an operation on my server that will require it being > up for at least 12 hours. > > https://forum.manjaro.org/t/gparted-scanning-all-devices-in-4-19/64170 Indeed, could be something in the kernel. We might still be able to pinpoint what causes it. GParted uses libparted for a lot of jobs just as KPM 3.3. On the other hand you saw the same problem in kpmcore-git/partitionmanager-git. And this version does not use any libraries and just calls various linux command line programs. I'll try to write a small patch that outputs commands that are being executed to terminal. It's probably a good idea to just include it by default and hide it behind some shell variable. e.g. "KPMCORE_DEBUG=1 partitionmanager" would enable more verbose output. After that you can ask maintainer of kpmcore-git/partitionmanager-git packages to rebuild those. Then you wouldn't need to compile it yourself.
It took me a long time to complete the operations with my server so I just got a chance to test the different kernel theory. I was using kernel 4.18, so it was possible older kernels did not display this behavior. To test, I disabled my mount and automount units I'd created for my NFS shares and disconnected from the server. Then I re-enabled my NFS shares in FSTAB, and rebooted into kernel 4.14. Sadly, the old kernel produced exactly the same behaviour with KPM for me as with the newer kernel. So, the kernel being a factor for this behaviour with KPM seems disproved. Perhaps that may be a factor with the gparted symptoms, but the person who reported the gparted issue has not provided the logs I requested to determine the cause. My computer is almost 10 years old, so compiling on it is not great (and I would rather avoid it). Generally, I try to avoid installing packages outside of my package manager entirely if at all possible. Please advise as to what you think would be best at this point.
(In reply to Dal Monico from comment #9) > My computer is almost 10 years old, so compiling on it is not great (and I > would rather avoid it). Generally, I try to avoid installing packages > outside of my package manager entirely if at all possible. Yeah, I try to avoid that too. Although, on Gentoo it's much easier to apply patches :), I can apply patches inside my package manager. > > Please advise as to what you think would be best at this point. See my previous comment, I will write a patch and we'll try to ask kpmcore-git package maintainer to recompile.
I've now pushed change that prints commands to terminal if KPMCORE_DEBUG shell variable is set. Sof if you run KPMCORE_DEBUG=y partitionmanager, you'll see what commands are being run and maybe you'll spot the command that takes a long time. Just need to get some packager to build a binary for you...
Thank you
(In reply to Dal Monico from comment #12) > Thank you Do you want to debug this further now that KPM 4.0 is released? Or should I close this as won't fix?
Without knowing which command exactly causes long executable, there isn't much I can do... Running KPMCORE_DEBUG=y partitionmanager can output commands which are executed to stdout.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!