My NFS mounts have failed. I have not been making any changes to these which have been working well until a recent sudo zypper dup which upgraded my Plasma desktop to Plasma 6.
This upgrade has crashed my system but after sorting this out I find that Dolphin does not show the mount points on my home directory. If I go to console then the mount points are still show but the NFS connection is not working.
I looked at mounting manually and this is the result:-
Mar 21 14:28:03 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 21 14:28:03 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 21 14:28:33 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:auth): pam_kwallet5: pam_sm_authenticate
Mar 21 14:28:33 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:auth): pam_kwallet5: Refusing to do anything for the root user
Mar 21 14:28:38 HP-Z640-1 sudo[16225]: alastair : TTY=pts/1 ; PWD=/home/alastair ; USER=root ; COMMAND=/usr/bin/systemctl daemon-reload
Mar 21 14:28:38 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 14:28:38 HP-Z640-1 sudo[16225]: pam_unix(sudo:session): session opened for user root(uid=0) by alastair(uid=1000)
Mar 21 14:28:38 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Mar 21 14:28:38 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
Mar 21 14:28:39 HP-Z640-1 sudo[16225]: pam_unix(sudo:session): session closed for user root
Mar 21 14:28:39 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session
Mar 21 14:28:39 HP-Z640-1 sudo[16225]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 14:29:24 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 21 14:29:26 HP-Z640-1 kioworker[16147]: kf.kio.core: An error occurred during write. The worker terminates now.
Mar 21 14:30:11 HP-Z640-1 sudo[16371]: alastair : TTY=pts/1 ; PWD=/home/alastair ; USER=root ; COMMAND=/usr/bin/systemctl start home-alastair-NFS_from_ibmserv_134_alastair.mount
Mar 21 14:30:11 HP-Z640-1 sudo[16371]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 14:30:11 HP-Z640-1 sudo[16371]: pam_unix(sudo:session): session opened for user root(uid=0) by alastair(uid=1000)
Mar 21 14:30:11 HP-Z640-1 sudo[16371]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Mar 21 14:30:11 HP-Z640-1 sudo[16371]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
Mar 21 14:30:12 HP-Z640-1 sudo[16371]: pam_unix(sudo:session): session closed for user root
Mar 21 14:30:12 HP-Z640-1 sudo[16371]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session
Mar 21 14:30:12 HP-Z640-1 sudo[16371]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Any reason why the automounts are not working?
One thought I have disabled KWalletManager. Is that relevant.
Can I get rid of KWallet altogether. I really do not want all the KDE clutter.
Because you do not explain anything, I do not know how you configured your NFS (auto) mounting. Please show /etc/fstab and if you use good old automount then of course also /etc/auto.master .
And you also only say very vague “I looked at mounting manually”, but again we have no idea what you did.
alastair@HP-Z640-1:~> sudo systemctl start home-alastair-NFS_from_ibmserv_134_alastair.mount
[sudo] password for root:
Job failed. See "journalctl -xe" for details.
alastair@HP-Z640-1:~>
Then I ran:-
alastair@HP-Z640-1:~> journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
Mar 21 15:43:02 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:auth): pam_kwallet5: pam_sm_authenticate
Mar 21 15:43:02 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:auth): pam_kwallet5: Refusing to do anything for the root>
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: alastair : TTY=pts/1 ; PWD=/home/alastair ; USER=root ; COMMAND=/usr/bin/sy>
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_unix(sudo:session): session opened for user root(uid=0) by alastair(uid>
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_unix(sudo:session): session closed for user root
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:42 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("sudo")
Mar 21 15:44:42 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("system>
Mar 21 15:44:43 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:43 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:43 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:43 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:44 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:44:44 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
lines 2512-2537/2537 (END)
and with -q added:-
alastair@HP-Z640-1:/etc> journalctl -xeq
Mar 21 15:44:44 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:45:37 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:04 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:04 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:04 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:04 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:05 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:05 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:51:34 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("")
Mar 21 15:51:34 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("cd")
Mar 21 15:52:06 HP-Z640-1 pcloud[11202]: Update for linux-x64-prod-v1.14.5 is not available
Mar 21 15:53:10 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:53:10 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:53:11 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:53:11 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:53:43 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("")
Mar 21 15:53:43 HP-Z640-1 plasmashell[11044]: org.kde.klipper: Invalid or non-local url for preview: QUrl("cat")
Mar 21 15:55:00 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:55:00 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:55:00 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:55:00 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:55:01 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
Mar 21 15:55:01 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning b>
lines 2435-2460/2460 (END)
I also looked at /etc/fstab as you advised. I do not recognise the Clamav mount at all but will go back to the work I did on Clamav. This was for an old NAS box which does not upload virus signatures without help.
AFAK I am not using automount but here is the /etc/auto.master file:-
alastair@HP-Z640-1:/etc> cat auto.master
#
# Sample auto.master file
# This is a 'master' automounter map and it has the following format:
# mount-point [map-type[,format]:]map [options]
# For details of the format look at auto.master(5).
#
#/misc /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
# "nosuid" and "nodev" options unless the "suid" and "dev"
# options are explicitly given.
#
#/net -hosts
#
# Include /etc/auto.master.d/*.autofs
# To add an extra map using this mechanism you will need to add
# two configuration items - one /etc/auto.master.d/extra.autofs file
# (using the same line format as the auto.master file)
# and a separate mount map (e.g. /etc/auto.extra or an auto.extra NIS map)
# that is referred to by the extra.autofs file.
#
#+dir:/etc/auto.master.d
#
# If you have fedfs set up and the related binaries, either
# built as part of autofs or installed from another package,
# uncomment this line to use the fedfs program map to access
# your fedfs mounts.
#/nfs4 /usr/sbin/fedfs-map-nfs4 nobind
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
+auto.master
alastair@HP-Z640-1:/etc>
Your title says: “Mys system automounts have failed …”
Now you say:
Please make up your mind!
This is your only NFS entry in your /etc/fstab and it has somewhere the string CLAMAV in it, but you say also
Maybe your are confused by the difference between CLAMAV and Clamav?
I have no realy an idea about many of the statements you us above, but for a simple person like me, one checks if this one is mounted with the mount statement and in this case to filter the output
mount | grep CLAMAV
And when it is not there, I wouyld try to mount it:
mount /home/alastair/NFS_from_ibmserv_135_alastair
Please ignore the CLAMAV stuff. I have no idea why it is there in /etc/fstab and it certainly has nothing to do with the mount point /home/alastair/NFS_from_ibmserv_135_alastair. That mount point, one of the three I have which have disappeared, is only required when the backup server (192.168.169.135) is running, which it is NOT at present.
It is NOT used for anything to do with CLAMAV as far as I am aware. My CLAMAV database is run daily as a cron job on this system (192.168.169.137) and the files are uploaded manually to the NAS, at least until I can sort out running the updater in the NAS to use my database. AFAIK it is working fine:-
alastair@HP-Z640-1:~/applications/CLAMAV/CLAMAV_db> ls -l
total 230912
-rw-r--r-- 1 alastair alastair 0 Jan 27 17:51 bytecode-334.cdiff
-rw-r--r-- 1 alastair alastair 836 Feb 28 02:15 bytecode-335.cdiff
-rw-r--r-- 1 alastair alastair 289733 Feb 28 02:15 bytecode.cvd
-rw-r--r-- 1 alastair alastair 781 Feb 20 02:15 daily-27190.cdiff
-rw-r--r-- 1 alastair alastair 783 Feb 21 02:15 daily-27191.cdiff
-rw-r--r-- 1 alastair alastair 9719 Feb 22 02:15 daily-27192.cdiff
-rw-r--r-- 1 alastair alastair 1724 Feb 23 02:15 daily-27193.cdiff
-rw-r--r-- 1 alastair alastair 2183 Feb 24 02:15 daily-27194.cdiff
-rw-r--r-- 1 alastair alastair 1483 Feb 25 02:15 daily-27195.cdiff
-rw-r--r-- 1 alastair alastair 983 Feb 26 02:15 daily-27196.cdiff
-rw-r--r-- 1 alastair alastair 1256 Feb 27 02:15 daily-27197.cdiff
-rw-r--r-- 1 alastair alastair 3436 Feb 28 02:15 daily-27198.cdiff
-rw-r--r-- 1 alastair alastair 4427 Feb 29 02:15 daily-27199.cdiff
-rw-r--r-- 1 alastair alastair 4706 Mar 1 02:15 daily-27200.cdiff
-rw-r--r-- 1 alastair alastair 2171 Mar 2 02:15 daily-27201.cdiff
-rw-r--r-- 1 alastair alastair 1997 Mar 3 02:15 daily-27202.cdiff
-rw-r--r-- 1 alastair alastair 3999 Mar 4 02:15 daily-27203.cdiff
-rw-r--r-- 1 alastair alastair 2543 Mar 5 02:15 daily-27204.cdiff
-rw-r--r-- 1 alastair alastair 3303 Mar 6 02:15 daily-27205.cdiff
-rw-r--r-- 1 alastair alastair 5447 Mar 7 02:15 daily-27206.cdiff
-rw-r--r-- 1 alastair alastair 16605 Mar 8 02:15 daily-27207.cdiff
-rw-r--r-- 1 alastair alastair 11983 Mar 9 02:15 daily-27208.cdiff
-rw-r--r-- 1 alastair alastair 9314 Mar 10 02:15 daily-27209.cdiff
-rw-r--r-- 1 alastair alastair 8583 Mar 11 02:15 daily-27210.cdiff
-rw-r--r-- 1 alastair alastair 13997 Mar 12 02:15 daily-27211.cdiff
-rw-r--r-- 1 alastair alastair 13932 Mar 14 02:15 daily-27212.cdiff
-rw-r--r-- 1 alastair alastair 15660 Mar 14 02:15 daily-27213.cdiff
-rw-r--r-- 1 alastair alastair 17472 Mar 15 02:15 daily-27214.cdiff
-rw-r--r-- 1 alastair alastair 17185 Mar 17 02:15 daily-27215.cdiff
-rw-r--r-- 1 alastair alastair 15854 Mar 17 02:15 daily-27216.cdiff
-rw-r--r-- 1 alastair alastair 19164 Mar 18 02:15 daily-27217.cdiff
-rw-r--r-- 1 alastair alastair 14437 Mar 19 02:15 daily-27218.cdiff
-rw-r--r-- 1 alastair alastair 12027 Mar 20 02:15 daily-27219.cdiff
-rw-r--r-- 1 alastair alastair 18613 Mar 21 02:15 daily-27220.cdiff
-rw-r--r-- 1 alastair alastair 63059796 Mar 21 02:15 daily.cvd
-rw-r--r-- 1 alastair alastair 43 Mar 21 02:15 dns.txt
-rw-r--r-- 1 alastair alastair 2282177 Jan 27 17:50 main-62.cdiff
-rw-r--r-- 1 alastair alastair 170479789 Jan 27 17:51 main.cvd
alastair@HP-Z640-1:~/applications/CLAMAV/CLAMAV_db>
On the other had the server at 192.168.169.134 is running and serving the two mounts I have set up as shown here:-
I am understanding less and less about your problem definition.
I now understand that what is in the /etc/fstab is not to be mounted and that what is not in /etc/fstab is to be mounted. Go figure.
And then you swamp the post withe endless lists where I do not see any relation with a mount problem. And seemingly you tried to configure mounts in systemd. From man systemd.mount :
Mount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Mounts listed in /etc/fstab will be converted into native units dynamically at boot and when the configuration of the system manager is reloaded. In general, configuring mount points through /etc/fstab is the preferred approach
I did not knowingly create the rogue automount in /etc/fstab and will delete it.
I note your bold but I chose not to mount my system mounts through fstab. I configure my mounts using systemd and and these have worked well for a while without any problem and two of them have been in constant use since early February.
I have detailed what I have done and what used to work before the Plasma upgrade. I have not changed anything and you have, on several occasions told me to provide all the details.
I am not seeking your views on what I should have done, I have followed the man page you mention and believe what I have done is correct and used to work. Please could you help me find and solve to cause of the present problem.
You have detailed everything except what you have done about the problem.
You have provided no logs.
You have provided no troubleshooting information about mounting anything.
You haven’t even provided any indication that it was the Plasma upgrade as you assert.
You have posted a lot of unrelated and useless information while providing nothing of any use. Hell, it took you 3 of 4 posts to finally mention the actual impacted mount point.
Hi and thanks for the reply. What I have done is ask for help. I am sorry I do not have enough knowledge on where to start with fixing the problem and all I have been working on is trying to find the source. For this reason I have shown the commands I have used which have worked until I did the TW update which introduced Plasma 6.
I have had no trouble in mounting anything because I have had no errors to give me any clues that anything was wrong. The mounts concerned are systemd mounts which run automatically when run booted.
I have posted separately about the Plasma 6 problem and there is a bug report on this advised by others which explains the start of the problem I experience. I started this thread because, having posted my post about the Plasma problem I have been attempting to find out why the systemd mounts are not working. I cannot see where systemd mounts should fail because of a problem with Dolphin which is the app which failed after the Plasma update.
If you would like to suggest some command I might run to help diagnose the problem this would be appreciated.
I hope not as I am still trying to understand what is going wrong. Logs were mentioned earlier so I am posting her the log from my last boot. I really am not qualified to interpret this or even comment but I have put it in susepaste:-
Hi Dean,
Thanks for the reply. My last journalctl log (above) was over 3000 lines and sadly I had no idea what to look for as there had been so much going on at once here.
In searching for the cause of the problem I started from the Dolphin issue, went on to NFS and then systemd.mount. There was a lot of “red ink” which didn’t mean anything to me but I re-booted after (?) your post with a view to posting a newer boot log. I checked my Dolphin /home/alastair/ directory and the mounts are now back up!!!
I shall probably never know what really caused the problem as these mounts have been in use for over a month and losing them cost me dear. I am just relieved system is back up and running.
I didn’t see any error there rleating to your NFS mounts. I was about to suggest restarting the systemd mount unit for the mount concerned, but there is no point to doing that now.
systemctl status <name_of_mount>.mount systemctl restart <name_of_mount>.mount
Personal opinion - I always examine logs as the root user account:
alastair@HP-Z640-1:~> journalctl -b 0
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
I see these repeating in the logs.
(the part that is interesting is: “kconf_update/dolphin_detailsmodesettings.upd defined Version=5 but Version=6 was expected”
And it’s not just for Dolphin, but other KDE apps.
Mar 20 19:00:10 HP-Z640-1 kwin_x11[5012]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
Mar 20 19:00:10 HP-Z640-1 kded6[5010]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Mar 20 19:00:10 HP-Z640-1 kded6[5010]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Mar 20 19:00:10 HP-Z640-1 kconf_update[5137]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
Mar 20 19:00:10 HP-Z640-1 kconf_update[5137]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_detailsmodesettings.upd defined Version=5 but Version=6 was expected
Mar 20 19:00:10 HP-Z640-1 kconf_update[5137]: kf.config.kconf_update: /usr/share/kconf_update/kleopatra.upd defined Version=5 but Version=6 was expected
Mar 20 19:00:10 HP-Z640-1 kconf_update[5137]: kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected
Mar 20 19:00:10 HP-Z640-1 kconf_update[5137]: kf.config.kconf_update: /usr/share/kconf_update/okular.upd defined Version=5 but Version=6 was expected
Mar 20 19:00:10 HP-Z640-1 kded6[5010]:
Mar 20 19:00:10 HP-Z640-1 kded6[5010]: org.kde.plasma.dataengine.geolocation: gpsd not found
Mar 20 19:00:10 HP-Z640-1 kded6[5010]: "location"
Ma ...
and then we see more oddities:
Mar 20 19:03:03 HP-Z640-1 plasma-discover[7881]: Transaction error: "System management is locked by the application with pid 7182 (/usr/bin/ruby.ruby3.3).\nClose this application before trying again." PackageKit::Transaction(0x558b67505df0)
Mar 20 19:03:03 HP-Z640-1 plasma-discover[7881]: AppStreamIntegration: No distro component found for "org.opensuse.opensuse-tumbleweed"
Mar 20 19:03:07 HP-Z640-1 plasmashell[5189]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.worldclock",
… and more — this is related to NFS:
15:43:02 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:auth): pam_kwallet5: pam_sm_authenticate
Mar 21 15:43:02 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:auth): pam_kwallet5: Refusing to do anything for the root user
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: alastair : TTY=pts/1 ; PWD=/home/alastair ; USER=root ; COMMAND=/usr/bin/systemctl start home-alastair-NFS_from_ibmserv_134_alastair.mount
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_unix(sudo:session): session opened for user root(uid=0) by alastair(uid=1000)
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_unix(sudo:session): session closed for user root
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session
Mar 21 15:43:06 HP-Z640-1 sudo[17654]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 21 15:43:25 HP-Z640-1 plasmashell[11044]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 21
As you, I have NFS mounted remote units. I installed Plasma 6 in Tumbleweed, like you, and have no issues about my NFS units after reboot. However, muy units are not mounted using systemd, but in fstab file. Anyway, you should try these Options: rw,user,users,x-systemd.automount .
Hi Dean,
Many thanks. Unfortunately my first post had omitted my command line starting the system mount and only posted the error. The bug report has explained my Dolphin problem but not the system mounts. The post from aggie explains a bit more but, as you say, not much point of doing it now.
Thanks again.
Hi aggie,
Many thanks for your response which is very helpful as I would never have found this without knowing more about where to look.
I conclude that in the update of Plasma there were quite a few issues still to be resolved and it seems these are being addressed and will be over the coming days.
I do expect this in TW type of problem but I do need to understand a bit more about kwallet. I thought I had removed this from my system but it seems to re-appear and also is enabled. This for me is a real nuisance but it seems I am stuck with it.
Meanwhile many thanks for your reply which is appreciated.