I must say, I appreciate the attention to make things not only simpler but less breakable lately. First we had APT being patched to stop users removing essential packages, now the KDE Discover software manager gets a similar upgrade.
Developer Nate Graham has written up another great "This week in KDE" blog post, going over changes and improvements coming to the next release of Plasma and the various applications. One small change really caught my eye though! Discover now has a new way to ensure you keep a working system, with an updated mechanism to detect important packages getting removed and give you a friendly warning on it free of too much technical jargon.
Picture Source - Nate Graham
Graham's comment underneath "Hopefully this is Linus-Sebastian-proof", heh. I hope many more application developers are looking at the way Discover and APT are evolving to ensure things are a bit more idiot-proof.
Another change to make things look a bit friendlier in Discover is that previously, if you had issues upgrading, it would instantly shove a load of technical details in your face. To normal consumers, that's clearly not going to do much to help and could probably scare them away. Now, instead, it will provide a very clear and friendly message, with the option to get more details to report the issue.
Picture Source - Nate Graham
Plenty more upgrades to Plasma are in the works too, like the newer KWin Overview effect gaining the ability to display search results from KRunner, which brings it another step closer to the GNOME Activities Overview feature, which I did always find thoroughly useful.
There's plenty more fixes in the full post.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: denyasisThanks for the info! I think we can certainly find arguments on what we would call a safety net or not, especially for a distro aiming for a more advanced (or adventurous) user.
Yeah, I would not advise a new user to use OpenSuse. There are just enough rough edges, even at my skill level, that I run into hiccups. I'll say my installs are non standard and I've tweaked a lot, so it could be user error.
PolKit is an enigma to me, especially since Suse seems to modify it, so it's not entirely the same as upstream and thier documentation is inconsistent. Steam tries to modify network settings on start, invoking a polkit rule. Depending on the DE, KDE just works, XFCE asks for the admin password, Enlightenment spams the password dialog, locking up the environment.
Maybe I should get this influencer guy to try it on OpenSuse? Lol
Hmm i know NetworkManager has a polkit - policy. Maybe thats the one get used, i can't be sure cause i use systemd networkd. Dropped all the "fluff" for my none moveable pc. But i also don't see a reason why steam should change network settings -> maybe it's just using NetworkManager to detect if it is in online or offline mode or for some other "security" features ?
Additional Information after a small google search -> https://githubmemory.com/repo/ValveSoftware/steam-for-linux/issues/7856 << my guess sounds about right.
Additional Information (2nd) -> "If using systemd-networkd for network management, install lib32-systemd in order for Steam to be able to connect to its servers" from the arch wiki ;)
If i see it right -> it not only ask network manager for the network status but also needs networkmanager and most likely related polkit stuff to be in 32bit ....
Last edited by Glog78 on 21 November 2021 at 2:58 am UTC
1 Likes, Who?
gradyvuckovic Nov 21, 2021
These are exactly the kinds of positive UX changes we need more of in the world of Linux and which I am glad to see the Linus Linux Challenge has resulted in.
As a rule, any time a user asks a piece of software to do anything, whether it be simply starting or closing the application, or asking it to perform any kind of task, there should be clear communication of the outcome.
For example, an action that refreshes a view in a user interface:
- If the action was successful (refreshing a view), hint at that visually by flashing the display area.
- If the action was unsuccessful, present a message box with a description of exactly what went wrong.
- If the action takes longer than 400ms, present a loading indicator on the view.
The number one thing that causes UX problems, is 'lack of communication'. If you don't know what's happening, or what went wrong, trying to fix the problem is that much harder.
A simple thing like an error message saying "Error: This action cannot be completed as it would remove the following software which is critical to the system's operation:", does not take that much effort for a developer to implement, but makes a massive positive difference for users.
New users aren't 'idiots' (necessarily, I mean in some cases..), they are just new. It's not their fault if they are left confused because the software didn't fully explain itself.
This should be a minimum UX standard that should be implemented across all DEs for all 'failable' actions.
Kudos to the distros for taking onboard the feedback of the Linux Challenge and making great changes as a result. Hopefully we see more of this.
Last edited by gradyvuckovic on 21 November 2021 at 3:16 am UTC
As a rule, any time a user asks a piece of software to do anything, whether it be simply starting or closing the application, or asking it to perform any kind of task, there should be clear communication of the outcome.
For example, an action that refreshes a view in a user interface:
- If the action was successful (refreshing a view), hint at that visually by flashing the display area.
- If the action was unsuccessful, present a message box with a description of exactly what went wrong.
- If the action takes longer than 400ms, present a loading indicator on the view.
The number one thing that causes UX problems, is 'lack of communication'. If you don't know what's happening, or what went wrong, trying to fix the problem is that much harder.
A simple thing like an error message saying "Error: This action cannot be completed as it would remove the following software which is critical to the system's operation:", does not take that much effort for a developer to implement, but makes a massive positive difference for users.
New users aren't 'idiots' (necessarily, I mean in some cases..), they are just new. It's not their fault if they are left confused because the software didn't fully explain itself.
This should be a minimum UX standard that should be implemented across all DEs for all 'failable' actions.
Kudos to the distros for taking onboard the feedback of the Linux Challenge and making great changes as a result. Hopefully we see more of this.
Last edited by gradyvuckovic on 21 November 2021 at 3:16 am UTC
9 Likes, Who?
Something to think -> is a good example which did come up denyasis (for other reasons)
If someone removes Network Manager -> is this package essential with systemd networkd still being around or not ?
Just a question :)
Question 2 to make it hard -> if one distribution says it is essential and the other says it isn't -> what would you as an developer of a not distribution package choose as an answer ?
Question 3 to make it completly lost -> what if the user wants to exchange network manager against wicd ?
Last edited by Glog78 on 21 November 2021 at 3:29 am UTC
If someone removes Network Manager -> is this package essential with systemd networkd still being around or not ?
Just a question :)
Question 2 to make it hard -> if one distribution says it is essential and the other says it isn't -> what would you as an developer of a not distribution package choose as an answer ?
Question 3 to make it completly lost -> what if the user wants to exchange network manager against wicd ?
Last edited by Glog78 on 21 November 2021 at 3:29 am UTC
0 Likes
Quoting: BeamboomQuoting: NezchanI'll be damned. I've been using Linux since RedHat 5.2, but today I learned I'm not a real Linux user.
... Is that what you got out of my comments? How? If you don't mind me asking?
Quoting: NezchanAnd yeah, I raised my hand when you asked who hadn't bricked their system because they were fucking around under the hood. Another shared experience I don't share I guess. I'm a fraud.
You've been around since RedHat 5.2 and you've not screwed up your system even ONCE?! Wow! Again, not sure why you believe that makes you a "fraud", but I can't help bu thinking you're a rare breed :D
Hell, from what I recall I used my entire 2-3 first YEARS breaking my system. Tweaking like a madman, installing packages east and west, trying to force packages not compiled for my distro to work, digging and punching through config files and file property settings and thinking I got the hang of things.
Essentially doing everything I never experienced Windows giving me the opportunity to do.
Zero times. There have been a couple of updates over the years that have more or less bricked things, and there have been times I've had to do a fresh install because of some fuckup or another introduced when upgrading to a new version of whatever it happened to be. But nothing because I've been fucking around under the hood because I absolutely avoid fucking around under the hood if I can at all avoid it.
I don't want to tinker. I don't want to tweak. I don't want to have to use command line if I can get away with it, although that's sometimes not possible. I just want to use my computer like a normal person on an OS I feel comfortable with. All the stuff you list there sounds beyond unpleasant.
3 Likes, Who?
Quoting: BeamboomQuoting: AussieEeveeThere is a tiny little warning blended in with all the other white noise on the screen, and blaming Linus is just silly.
TINY? lol - dude, there was NO "white noise". There's FIRST an explicit warnings, very clearly put, AND info on what exact packages are about to be installed (for you to make up your own mind), then ANOTHER very explicit warning AND you're required to type a bloody SENTENCE to get through with it.
If that ain't clear enough then you're not really mature to use a system that gives you full control. You're supposed to READ what the system tells you. Read, and comprehend.
With great powers comes great responsibilities - and that goes for the package managers too. Most definitely.
But if you're after a OS that completely PADS you inside a fuzzy box where you can do nothing to harm you - well then Linux is not, was never and hopefully never will be your right choice.
this is bullshit.
it dont have to be black and white.
maybe the person want to have an desktop enviroment like KDE or gnome without all the issues that came with linux.
maybe they want to give a new life to an older hardware.
maybe they arent fluent in english and couldnt understand the whole sentence.
people shouldnt be forced to chose between all the benefits of linux or having to deal with something like windows.
this mindset is what prevent linux from geting more marketshare and as result, prevent us from having more games and softwares that support our system, until the day we can no longer do our work or live our lives because linux became unberable due to it weak ecosystem, and its not economically viable to use, or its too much headeach, too much games/softwares we have to give up.
Quoting: BeamboomI use Linux because it's NOT the padded regime of Windows and MacOS. There will always be a trade-off between security and efficiency.
that is why we have many distros, there is no way in hell that all of then have to cattter to linux elistists like you.
want to use some hard to use distro? there will always be an option for you, but no, you want exclusivity, you want to be one of the only ones who CAN use linux.
i bet you didnt started by compiling your own kernel and installing the user interface from scratch.
just give newbies an option, if they want to go deeper they can use arch or something, but Pop!OS isnt designed for that audience.
Last edited by elmapul on 21 November 2021 at 8:34 am UTC
1 Likes, Who?
Quoting: Beamboom. We became wiser, and better at reading and better at understanding, even RESPECTING the system.
that is, the ones who survived, the ones who didnt go back to windows.
hell.
Quoting: BeamboomThey buy the TV with the features they want.
i use VLC because it has the features that i want AND it is open source.
i used firefox long before i knew the term open source.
and then i started respecting floss software and dontributing to it (donation, translation, bug report etc) because i believed in this cause, i saw for my self that it could produce good softwares so i wanted to support it.
i may be the exception, but if it werent for exceptions like me, we would never have something like linux to begin with.
you dont have to chose between opensource and features if you can have both, but we cant unless we increase our marketshare.
Quoting: Beamboombetween those VERY clear warnings were a listing of what exact packages we talk about.
of course, an newbie user know what xorg is.
Quoting: Beamboomhas experienced on our Linux system during our first year for DECADES now.if i suffer you have to suffer too!
bullshit. if you really think like that, why are you using modern computers? go back to "paper file system", tech evolve to make our lifes easier, i bet you have an monitor instead of an printer to read those comments right?
Quoting: Glog78A mac os or windows user don't understand containers and container based security and he don't want to understand why a program don't follow the theme he has set or why he needs a special driver version or or or ...
speaking of themes, one of the reasons why i started using linux was the freedom to customize, freedom is that, being able to make the system work and feel like you want.
removing theme customization like gnome is doing, or puting programs in a sandbox where they cant see the theme that the system is using to adapt (use it thenselves) feel so backward...
Quoting: GuestQuoting: Glog78i won't try if a sudo rm -rf /* is catched on my distribution , cause i am 90% sure it isn't and i am to lazy to do so at least it works perfectly fine without a warning on subdirs ;)
Ha! It's not caught on my system! I pause and triple check every time I use the rm command with elevated permissions.
Reminds me of this: https://www.pcworld.com/article/431317/scary-steam-for-linux-bug-erases-all-the-personal-files-on-your-pc.html
hell the redhat CEO deleted an entire serve worth of information by accident.
Quoting: eridanired123Quoting: Liam DaweQuoting: BeamboomIt's a real shame to see such elitist nonsense being posted here. It's techno jargon in the errors, crammed around lots of overloading info that even "power users" screw up on. There is a reason why the term "sane defaults" even exists. Unless we want Linux on the desktop to continue to be gated by zealots and remain irrelevant, we have to appeal to users who don't have the time and patience to relearn every single thing and study all error messages, just to stop their system breaking.Quoting: AussieEeveeThere is a tiny little warning blended in with all the other white noise on the screen, and blaming Linus is just silly.
TINY? lol - dude, there's TWO explicit warnings, very clearly put, AND info on what exact packages are about to be installed, AND you're asked to type a bloody SENTENCE to get through with it.
If that ain't clear enough then you're not really mature to use a system that gives you full control.
With great powers comes great responsibilities - and that goes for the package managers too. Most definitely.
But if you're after a OS that completely PADS you inside a fuzzy box where you can do nothing to harm you - well then Linux is not, was never and hopefully never will be your right choice.
Nah, this time I strongly believe you are wrong, Liam.
The text was clearly indicating that they were ESSENTIAL packages, if a person doesn't understand a term, in this case what “essential” means, then that person should look that term in a dictionary.
YES, Mr. Sebastian was affected by a flaw in the Linux system that should be fixed (and it is not about APT at all), but also, YES, the youtuber has responsibility in what happened too.
you need to high light the ESSENTIAL part in eye catch color, otherwise the user will just ignore the text wall.
or do you really think any one read the terms of service of anything?
Quoting: Purple Library GuyI don't think you have much of a picture of what the Linux desktop can be like for straightforward users to use.
he is too used to the problems of linux to see that it can evolve.
its almost like we didnt had ANDROID and a lot of smarth devices like tvs, digital cameras etc running linux and being easy to use at the same time.
sure, those are too dumbed down systems that you cant break but you cant do much, unless you have an way to root your device or know how to hack your camera, but come on! we can have an midle term!
Last edited by elmapul on 21 November 2021 at 8:33 am UTC
3 Likes, Who?
i will glue togheter my comments because there are an entire page of then.
0 Likes
Wait..
Why is this whole comment sections basically a continuation of the previous thread, instead of discussing the actual topic which has nothing to do with the CLI and is a GUI only move to prevent new users from bricking their DE, which I would say is very objectively a good move.
If someone thinks that this was a bad move from KDE, I would love to hear their arguments.
Last edited by Rooster on 21 November 2021 at 9:53 am UTC
Why is this whole comment sections basically a continuation of the previous thread, instead of discussing the actual topic which has nothing to do with the CLI and is a GUI only move to prevent new users from bricking their DE, which I would say is very objectively a good move.
If someone thinks that this was a bad move from KDE, I would love to hear their arguments.
Last edited by Rooster on 21 November 2021 at 9:53 am UTC
5 Likes, Who?
Quoting: Glog78Quoting: denyasisQuoting: Glog78Since i use arch on my machine , there is no real default "net"
Really? I'm not familiar with arch, I've used the wiki a ton... it's So helpful!!
But I'd be really surprised if you have to backup all your custom confs in /etc because pacman overwrites them on every update. Or that a DE doesn't use PolKit (or equivalent) without some sort of base default rules package.
I feel it would be a little weird to have no system safe guards, even coming from upstream.
*I could be totally wrong about Arch and if so, I'd gladly share a frosty beverage of your choice if you could enlighten me on the rules.d local override process for Polkit. Trying to fix an issue with Steam and the network.
** Oh, I missed that part in your post. If you count OpenSuse as "mainstream". It has full system snapshot by default, courtesy of BTRFS. Reboot, pick the old snapshot in GRUB and good to go! (Ok... you need a terminal command to finish the rollback, you know, altering the file system and all).
There are safe guards (like pacman usually by default don't overwrite configs but put them next to the existing file) Which is good and bad *lol* ... imagine a config not working because of a missing parameter after a reboot because you didn't checked for the new config template (hadn't had this since years but i had this a few times) *ups* << usually they are not leaving the system in an "unusable" state but i would probably define unusable different than a "newbie" :) -> imagine dns not working anymore after an systemd update or since i boot directly from efi into the kernel i once used an "outdated" way to write the root partition into efi ... lets say thanks god i always have a "normal" bootloader ready ...
With default i mean there is no default net which you can be sure to be find on every arch installation. I for example can boot my X even without polkit (init 2 -> startx /usr/bin/xterm ;) ). There are however packages with files under /usr/share/polkit-1/rules.d and /usr/share/polkit-1/actions. There is no special rule for steam (if that helps) The last issue i had with steam and network i fixed by setting up a local dns proxy and re-enabling ipv6 -> had a ipv4 only config before.
OpenSuse i would call as mainstream but when was the last time someone adviced OpenSuse somewhere for a beginner? Even during 7 pages of this discussion you and me are probably the only two who talk about OpenSuse / Suse so far. Being able to do so on the terminal is a step forward. But i guess we are far from "newbie" friendly even at this point.
i saw something even worse, not being able to login because some file was encoded with the wrong encoding.
(eg: it was UTF 8 when it should be UTF16 or the opposite)
imagine reading an file searching for errors in the code of the config file, only to realize... there is NONE, but you know that this is the file wich is causing problem...
then you change the encoding and puff! it work again!
an newbie would NEVER figure that out.
0 Likes
Quoting: Glog78OpenSuse i would call as mainstream but when was the last time someone adviced OpenSuse somewhere for a beginner? Even during 7 pages of this discussion you and me are probably the only two who talk about OpenSuse / Suse so far. Being able to do so on the terminal is a step forward. But i guess we are far from "newbie" friendly even at this point.
Strange. You request safety features like snapshots, being able to boot those and roll back, and yet say the distro that implements all that by default is not for new users....
0 Likes
Patreon
PayPal
See more from me