pkexec is a cli usage of polkit = systemd's version of sudo
nah, you have homework to do.
pkexec is a cli usage of polkit = systemd's version of sudo
nah, you have homework to do.
Yes i know, and i have learned a lot since 2018 when I for the first time in my life installed Linux Mint on a lapoptp... But it's only three years and not active ones.. mostly just daily using and only fixing when broken..
No choice!
Some.... just some .... i will say a lot of assembly required. hahaha
Perhaps, though if you actually used it I suspect you'd discover otherwise quite quickly.
Much of your points are valid, it is another user - but don't conflate poor implementations with 'proper use'. A GUI is a finished interface, something linux lacks. It is also not 'required' and arguably fat.steve_v wrote: ↑2021-07-30 05:14 It sounds very much to me like you're working through GUI file managers one at a time, running each of them through sudo, and then just moving on to the next one as they get screwed up.
I could be wrong, and if I am then I apologise. I do recall you telling somebody else to run their GUI file manager as root though, so I have to assume you've been doing the same...
If sudo was meant for running large GUI applications with elevated permissions, it would say that in the manual. It doesn't. Sudo is for running a command as another user, and it does exactly what it says on the tin.
It is not UNIX’s job to stop you from shooting your foot. If you so choose to do so, then it is UNIX’s job to deliver Mr. Bullet to Mr. Foot in the most efficient way it knows.
Indeed. I've tried before with this one, and it got nowhere. It just kind of rotates in place and pokes at random things.
Sure. One of the reasons things like pkgexec exist in the first place is because sudo is not suitable for those use cases.
Don't conflate established multi-user design with faux-permissions... Or shiny GUIs with progress for that matter.
GNU/Linux has a utensil for every occasion, just like the UNIX systems and philosophy it was derived from. Many of them are so well polished they haven't changed significantly in decades... They're just not mouse-driven GUI-focused utensils, and for some reason I'll probably never understand, that gets some people all knotty.
Ya, I didn't say that! Elsewhere I've mentioned I have sudo-less systems...
Move disk from server 1 to server 2 and now Sue(1005) can freely access Bob's(1005) files. The permissions are to organize within a given system, nothing more. I say faux since many conflate permissions with security.
Amen.
What is the problem of testing things when terminal commands didn't work????
I only right-click and open as administrator if I have to make planned changes where I must have root privileges.. and only then.steve_v wrote: ↑2021-07-30 05:14 In one of our previous interactions, I'm pretty sure I mentioned that running GUI applications (including file managers) as root (or sudo) can and does cause strange borkage, because it louses up permissions on configuration and / or temporary files in your home directory... Or better yet, scatters configuration files between your home directory and roots home directory depending on who you ran it as last.
This simply is not how desktop GNU/Linux works, and if you keep doing it, you will have problems. Using sudo does not just give you elevated permissions, it makes you a completely different user for that shell.
eh, what?....seriously.... now you're just making yourself look stupid.steve_v wrote: ↑2021-07-30 05:14 IOW, "sudo make me a sandwich" will probably result in a sandwich that belongs to root... So you'll need to "sudo eat sandwich" as well.
When "make" puts the cheese back in the fridge, that might well become root's cheese. If it washes the knife, guess what? That's root's knife now as well. If it saved the sandwich recipe, it saved it to root's recipe book, not yours...
See where this is going? That's why we don't run complex applications through sudo.
I tried a new account, and it didn't work either... But the solution was a GUI named Timeshift
As you can see, I have been a member for almost four months now. and I have never used Debian before April 7thsteve_v wrote: ↑2021-07-30 05:14 It sounds very much to me like you're working through GUI file managers one at a time, running each of them through sudo, and then just moving on to the next one as they get screwed up.
I could be wrong, and if I am then I apologise. I do recall you telling somebody else to run their GUI file manager as root though, so I have to assume you've been doing the same...
The only reason I tested foxit reader, is that I'm installing Linux Mint 20.2 on my mothers laptop and I am trying to install as many programs as possible as she had on her Win7 computer.. so she gets an easy switch how to use her computer with a Linux-engine instead of a win-engine.steve_v wrote: ↑2021-07-30 05:14 Then there's that mention of foxit reader... the old "don't break Debian" bit that's been around forever likely applies, as does the well-established advice against installing things (especially proprietary things) from the web rather than the repos.
There are at least six perfectly good FOSS PDF readers available without even opening a web browser, and every time you install some random software with a random executable installer, you risk screwing up your system.
Let me guess, foxit comes as a '.run' file? That there is short for "run away".
Windows: Install random crap from the web, run a virus scan or use third-party uninstall tools when things go sideways.
GNU/Linux: Install software from the distribution repositories (or make your own packages), enjoy things not going sideways because the package manager tracks installed files properly.
I don't know if it is to all you others disadvantage if I don't like the terminal.. Because I won't ever protest if you all help me trying different commands in the terminal. On the contrary, I'm glad you all are helping me by writing out the commands, so I can copy and paste it into the terminal.steve_v wrote: ↑2021-07-30 05:14 Perhaps, though if you actually used it I suspect you'd discover otherwise quite quickly.
OTOH, it most certainly is to everyone else's advantage, because trying to help somebody fix their system without resorting to CLI commands (and therefore relying on a bunch of pictures or long-winded descriptions of where buttons are etc.) is exceedingly painful.
Thank you for your answertrinidad wrote: ↑2021-07-30 20:39 I would stop while you were ahead and do some common sense things first. If you're dual booting, boot up and log into Windows. Once logged in hold the left shift key down and don't release it until the computer goes off completely going through the process of logging out and shutting down normally. Don't release it until done. This clears hibernated pre-loaded RAM and completely unmounts disks on Windows as Halvor spoke of. Afterwards boot into your Debian system. Turn off smartmon if it is set to run after boot. Test your ability to create folders. If you still cannot create folders run gparted to check the tags and flags on your partitions. You have XFCE installed so just use Thunar and get it working right first.
Two questions: 1) Is this UEFI? 2) Did you install smartmon to Debian or did you install to Windows?
TC