I switched to Mint 22 Cinnamon Edition from Windows 10 a few weeks ago and, while I’ve solved 95% of the problems I’ve come across so far, I’m bashing my head against the final few that are really bogging me down. Most of these exist with the file manager (Nemo):
No recursive search in Open/Save dialog
No bookmarks in Open/Save dialog (and I have searched around for solutions a hell of a lot, and I always end up at some variation of A-Folder-I’m-Supposed-To-Edit-The-Contents-Of-Doesn’t-Exist or This-Entire-App-Doesn’t-Exist, so no solutions have worked):
I have tried saving to bookmarks from within the open/save dialog (as some websites have suggested) and it applies to the actual app of Nemo (hence ~/.config/gtk3.0/bookmarks) but still doesn’t propagate to the open/save dialog. Some sites have suggested there is a ~/.gtk-bookmarks, there isn’t. some have suggested modifying settings to to with QT5 that I can’t find, and one suggestion of there being a /usr/bin/qt5ct/* to tweak doesn’t exist either.
Date Created and Permissions seem to be entirely unavailable while in network shares (SMB - tho will probably be moving to a different kind of sharing solution soon), breaking my workflows and making management difficult
A distinct lack of “Copy the path of ” , and the lack of “Open with elevated privileges”
Inadherence to SMB Server-Side Copy, making copying files to/fro the same network share impossibly slow (Windows managed this fine, somehow)
I have tried installing Dolphin but it has felt even more abrasive to use workflow-wise than Nemo and doesn’t “gel” with me.
I have also tried Nautilus and while the UX/UI is far cleaner than Dolphin, it doesn’t appear to respect individual folder view preferences (i.e. list/“Details” in one folder and grid in another), so I can’t use it either. I also don’t know how I’d make either work as the file open/save dialog regardless.
I would also love to be able to auto-mount the network shares at startup and I have given this a go using the fstab but I’ve gone wrong somewhere and it hasn’t worked yet. Any pointers there would be nice - my setup currently doesn’t have entries for the shares in the fstab at all and I kinda don’t want them to turn up under /mnt/ but if that is the only option then I’ll take it.
If any of y’all have any ideas as to how to remedy even some of these points I’d be very grateful haha
Did you look into Nautilus extensions?
And for the automount to work, there’s a flag to wait until the network is online or else it will fail.
You can mount the drives wherever if you don’t want them behind /mnt, locations are just formalities.
Well, I just had a look, and it seems like the only way to get individual folder views on Nautilus is really hacky and not an ideal solution at all. Secondly - I was aware of this particular flag for post-network-up-mounting but that was not the issue - it seemed to half-mount to /mnt/ but was empty (perhaps something was incorrect credentials-wise, IDK) so I’ll try again at some point.
Oh that’s disappointing, I was sure there would have been an extension for that.
I remember in the file manager from lxde you could set custom layouts for each folder as well (apart from Dolphin), maybe give that a shot.
I’ll say, I definitely don’t want it unmounting after idle time, since I’m gonna be using my computer periodically throughout the day and accessing certain datasets periodically as well - that might introduce some faff. But I’ll definitely look into it - this sounds the nicest so far.
The warning stems from a mint setup thing. Somewhere mint is meant to set the $OPTION variable as part of starting the service.
Open a terminal window, run cd /net/<machine>; ls. The output should show the nfs shares of said machine.
Validate with a showmount -e <machine> which queries and prints available nfs shares.
Yeah seems like it’s an NFS-only thing from what I can tell… there is no such thing as even /net/ to begin with and the showmount states “unable to receive”, leading me to that conclusion
I guess autofs is not configured to work “automagically” in mint.
(On Fedora) The software is configured using the “/etc/auto.master” file. There are two shell scripts (need to be executable) that look up nfs/cifs shares and mount them on access (/etc/auto.net, /etc/auto.smb; documentation in script).
They are enabled in the auto.master file using lines like
/net -hosts
/cifs /etc/auto.smb --timeout=60
So, there you have it, if you want to go down that rabbit hole. But I guess you chose Mint so you didn’t have to.
Well, down the rabbit hole I have been going. I’m getting sooooomewhere but I believe I’m hitting this:
There’s no /etc/creds at all but there is /etc/credstore and /etc/credstore.encrypted, neither of which have anything in them (and yes I have turned on view hidden files). So I am wondering if there is a way to either:
Find out where the creds are stored and point it there
Find out the format or syntax of whatever $key should be and make there be an /etc/creds/$key
Hard-plumb in the creds directly in the file somehow (acknowledging the security risk)
First hint is found in man smbclient:
A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the -A for more details.
I think you’ll create the folder /etc/creds and add files in there. One for each server. Not quite sure about the format of these files.
I think the man page says
You have to read the articles carefully - the first one seems to refer to an older version of the auto.smb script with different locations.
The second is mint specific (yay) but describes how to hard code specific shares - not the use of the auto mount (that I prefer).
Yooo. Thanks. The second link worked flawlessly. (at least for now, until I change to a non-SMB service in a few weeks). I’m fine with the hard-coded shares since there are only a couple that need to persist like that that I use daily and I can go and manually mount the rest like I used to as and when I need to - the main buggerance is sorted, at least, and magically my bookmarks problem along with it, so that’s cool (maybe bookmarks struggled with network locations). Thanks again
