Debian User Forums

Using a graphical editor with sudo, gksu{,do} or su-to-root runs the whole application with root privileges for the entire time it is open, that's why it's such a bad idea. Any bugs in the program or the underlying graphics stack will be exposed ...

Who the heck thought that was a good idea? It looks like I'll be dumping LightDM soon and going back to using xinit . Quite a few people aren't going to be able to do this as X without a display manager requires a modesetting video driver. root has to launch the driver if the kernel can't. GDM star...

Lol ... this thread, as pretty much every gnu/Linux forum thread ... EVER, has jumped the topic track and headed off into let's talk about anything/everything territory. :D Also as usual I contributed more than my share of off-topicness too. :D So shall continue, I speculate and wonder, with X runni...

wizard10000 wrote:Are you running X using a display manager that's not GDM? If so, X is running under the root account.

Who the heck thought that was a good idea? It looks like I'll be dumping LightDM soon and going back to using xinit.

Phil

... and the simple fix of chown'ing it back. Another reason newbish folks may want to keep a root account around. Obviously I've elected to keep using gksu, thing will likely remain working fine for the life of Buster if I want to use it and for now I do. Mentioned in previous posts, I've used the ...

... invoke root (via gvfs) to save the file. Keep having to ask myself, what the hades am I missing here ?!?!? Using a graphical editor with sudo, gksu{,do} or su-to-root runs the whole application with root privileges for the entire time it is open, that's why it's such a bad idea. Any bugs in ...

anticapitalista wrote:

wizard10000 wrote:
... If so, X is running under the root account. This is the reason I quit using display managers

Why is that so 'wrong' now in buster, but was perfectly acceptable in all previous Debian releases?

It was never acceptable, rootless X is a major improvement.

Bulkley wrote:BTW, I use Openbox with Tint2 and keep this thing as simple as possible.

Same. openbox just works

Are you running X using a display manager that's not GDM? If so, X is running under the root account. This is the reason I quit using display managers :) I don't use a display manager. I log in with sx (alias for startx). That's one more thing I haven't been able to do with Buster. BTW, I use Openb...

wizard10000 wrote:
... If so, X is running under the root account. This is the reason I quit using display managers

Why is that so 'wrong' now in buster, but was perfectly acceptable in all previous Debian releases?

Bulkley wrote:Not me. I don't even use sudo. I still use su (although I have added the -) when I need to use access root.

Are you running X using a display manager that's not GDM? If so, X is running under the root account. This is the reason I quit using display managers

^ Nn worries definitely see where you're coming from fellow nixer. The gnu/Nix gawds punished me for being an overly sensitive ahole, the project I'd thought had succeeded, while works is not right. So it's back to the drawing board. Dratz ! Running on coffee fumes here.

Apology accepted.
Over the years we've had possibly hundreds of posts where people have added the wrong repos and hacked things they shouldn't have hacked. It's very hard to support and best not to encourage it.

Public apology, sorry Sunrat, have no idea why I read what you'd said and interpreted it so harshly. What you'd typed was nowhere near as big a reprimand as I was taking it to be and so ended up lashing out. Sorry fellow nixer ... Had just gotten done successfully following a tute to do something I ...

What about using su-to-root instead of gksu , like this?: su-to-root -X -c <application> Nope. chris@BOSSDESK:~$ su-to-root -X -c dolphin kdesu(13194)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /build/kde4libs-5CvfXW/kde4libs-4.14.38/kdesu/process.cpp ...