bizdelnick

joined 1 year ago
[–] bizdelnick@lemmy.ml 8 points 7 months ago

Sysadmin GUI tools are designed to be secure by isolating GUI from privileged process. That is not true for a random GUI app.

[–] bizdelnick@lemmy.ml 7 points 7 months ago (1 children)

Nope. Running GUI as root in the same X server as unprivileged apps is insecure because each of them can take control over privileged window. IDK if this issue has been addressed in Wayland, but anyway there are no wayland-only distros nowadays.

[–] bizdelnick@lemmy.ml 9 points 7 months ago

Don't do this. I'm unsure if this works in any distro, but if it does, this is unsecure.

[–] bizdelnick@lemmy.ml 0 points 7 months ago

Don't do this. I'm unsure if this works in any distro, but if it does, this is unsecure.

[–] bizdelnick@lemmy.ml 2 points 7 months ago (2 children)

I have no idea what you are talking about. The answer to your question is: this is impossible and this is done for purpose. Don't try to work in linux like in windows.

[–] bizdelnick@lemmy.ml 11 points 7 months ago (1 children)

Use bash-completion, it is much faster than clicking menus.

every distro I’ve tried has a strong sense that if you’re using the GUI you don’t need or deserve admin controls

GUI tools are not suited to be run as root in general. Few ones that are have special measures taken to prevent gaining privileges by another process, e. g. run a background non-GUI process as root and GUI communicating with it as an ordinary user. Such tools (package managers, system tweakers etc.) are usually configured to get required privileges via polkit (e. g. pkexec synaptic to run GUI package manager in Debian). Don't use sudo to run GUI programs!

[–] bizdelnick@lemmy.ml 10 points 7 months ago (26 children)

You don't need to run any GUI programs as root.

[–] bizdelnick@lemmy.ml 81 points 7 months ago (4 children)

Don't search tasks for a tool. Search a tool for your tasks.

[–] bizdelnick@lemmy.ml 2 points 7 months ago (1 children)

Everything seems ok. It is unlikely that the disk itself is dying. Maybe the problem is a bad cable or bus controller. Or something is wrong with the filesystem.

[–] bizdelnick@lemmy.ml 6 points 7 months ago

It's not GTK, it's tk.

[–] bizdelnick@lemmy.ml 2 points 7 months ago* (last edited 7 months ago) (3 children)

Check its SMART: smartctl -a /dev/sdb.

view more: ‹ prev next ›