10-23-2020, 09:05 PM
(02-23-2020, 03:14 PM)az2020 link Wrote: One thing I'm not liking is KDE "wallet." Every time I boot, kwallet asks me for a password just to connect to my own wifi from my own computer (which I logged into with my own username and password). That doesn't seem well thought out.I've got a feeling it serves a very good purpose and in the future we're all going to be using wallets. But, right now, I'm not liking it.
Issues discussed here are probably more specific to distro default config than KDE...
kWallet is a secret keeper, which can be secured with a password not necessarily identical with linux user password. If the login system assume that it is identical when it isn't, and try to open the wallet with the linux user password, you get error message on every login for failing to open the wallet.
Wallets store not only trivialities like wifi passwords, but also encryption keys to more important stuffs like Chrome browser data, that includes saved online passwords. Linux give us the possibility to have multi wallet with multi password, but the default behavior (asking wallet password every login) might feel inconvenient.
On my daily driver, I set my default wallet password identical to linux user login password, and configure the login system to open the wallet when logging in (using linux user password as wallet password). This is configured in /etc/pam.d folder.
If the operating system is configured for simplicity, then assuming that the wallet password and user password will be the same is very sensible, but to my experience hopping distro so far, most distro does not do this by default.
Other issues discussed, ie waiting for NFS to cleanly unmount before shutting down, is probably also related with the distro's default configuration, hidden in places like samba config, systemd services config, timeout settings etc. These are things (Jerry's bread and butter?) which casual users would never configure themselves (not many windows user know how to use msconfig, not all linux users ever enter /etc folder)
Kubuntu's default might be carried over from Ubuntu's use case as server, it should must wait for services within it to really gracefully exit before OS shut down (SQL database corruption is a bad bad bad thing), while in GUI systems, a simple confirmation is all it takes to gracefully exit all GUI program.
I'm sure that the fine tuning of LL can also be carried over into KDE, to ensure an experience more attuned to what users expect. I just want to say that resolving these issues are perfectly doable with KDE.
PS: I was just trying out LL, and I think it is a distro I can use immediately after installation, instead of needing-customization-to-be-usable. I'll use LL as my OS-in-flashdrive that I use for backup purposes. (I use openSUSE tumbleweed KDE for daily driver).