Announcement

**claydoh** · Mar 09, 2019, 07:36 PM

Welcome!!

**oshunluvr** · Mar 10, 2019, 06:00 AM

Your path sounds a lot like many here. Obviously, we all prefer the Ubuntu ecosystem and Plasma 5 (aka KDE) too. I personally use Neon because I like the combo of a stable LTS base with the latest and greatest Plasma 5 on top.

Welcome to the forum.

**WWDERW** · Mar 10, 2019, 07:51 AM

My son still has the latest Neon on his little computer. 16.04 based Neon was alright on my computer, but after a fresh install of 18.04 Neon, I got a totally blank screen, right after I did the install, so I hadn't done any of the post install work and thus not committed to anything, so I just went to Kubuntu 18.04. Neon 18.04 works fine on my son's computer, so it must have been something on mine that caused it to wig out. Since it happened on my main production rig, spending too much time troubleshooting when I wasn't too far committed to the install anyway, I just loaded up Kubuntu.

Of course, it would have been far better if I hadn't done that during a work week as well. I really should do these fresh installs on a weekend (and even though I keep saying that, I still do it during the work week).

**oshunluvr** · Mar 10, 2019, 09:57 AM

The "black screen on installation" isn't unusual. If you search it you'll find lots of posts referencing lots of distros. It's usually a video issue that goes away when you get the proper driver installed and configured. I myself am running Neon on a desktop with an nvidia card and two Dell laptops with Intel built-in GPUs without problem. Well, except that Kscreen is still mostly useless for laptops when you switch monitor configurations often.

**WWDERW** · Mar 10, 2019, 02:10 PM

I have no doubt that it was something that could have been fixed. One thing that I have quickly come to love about Linux is that even if something that is/gets broken, more likely then not the user can get it working again. Unlike other platforms where they more then likely have to wait for an update, either thru the OS vendor or the software vendor. I was mainly on a time crunch and it was far quicker to go with something that I knew was going to work on my system then to try to troubleshoot.

Now, if I can only figure out why Kubuntu wont allow me to elevate and run the GUI version of Bleachbit after so many times (this seems to vary) between boots. My workround now is just to run a script for running Bleachbit via CLI and just elevate that when I need certain things cleaned. It's a minor thing (I have noticed on other programs (2 others right off the bat, not elevated though, just running as normal and those are games, SuperTux and TuxKart, both portable versions) and that work around seems to be good enough so far. I wonder if it has something to do with the PyGTK wrappers and not playing nice with a KDE based distro. Dunno, just spitballing.

**Snowhog** · Mar 10, 2019, 03:26 PM

As to Bleachbit running as root. See https://discourse.ubuntubudgie.org/t...ails-18-04/621

**oshunluvr** · Mar 10, 2019, 03:33 PM

Well, the Plasma developers have been struggling with security things for a little while. They locked down Dolphin from root and you would have thought they were stealing babies they way people reacted. Kate now will edit root owned files and ask you for sudo password when you try to save. Anyway, the point is it may be due to that. It seems like you should be able to either edit the Kmenu entry and add sudo to the command line (if that even works) or try "Run as a different user" - but I think that would require you to create a root password, which not everyone wants. Likely, the best solution would be to create a sudoers file for bleachbit and add sudo to the Exec line in the desktop file and in kmenu. Then you'd be root every time you launched it and wouldn't have to enter your password.

As usual with Linux, there's way more than one answer to the problem

**MoonRise** · Mar 10, 2019, 04:45 PM

Welcome to KFN!!

**WWDERW** · Mar 10, 2019, 05:24 PM

Originally posted by oshunluvr View Post

Well, the Plasma developers have been struggling with security things for a little while. They locked down Dolphin from root and you would have thought they were stealing babies they way people reacted. Kate now will edit root owned files and ask you for sudo password when you try to save.

Ironically, I actually wasn't fond of that as well. I had to find other ways around it (which I got pretty quick at and think were quicker then the other ways I was doing things).

Originally posted by oshunluvr View Post

Anyway, the point is it may be due to that. It seems like you should be able to either edit the Kmenu entry and add sudo to the command line (if that even works) or try "Run as a different user" - but I think that would require you to create a root password, which not everyone wants. Likely, the best solution would be to create a sudoers file for bleachbit and add sudo to the Exec line in the desktop file and in kmenu. Then you'd be root every time you launched it and wouldn't have to enter your password.

Attached is what I'm getting when I run it via CLI using Yakuake. If I'm reading the output correctly it seems to be a display issue more then a permissions one. It will run maybe once, twice, at most 3 times without rebooting graphically. That's when I just decided to script everything and run it CLI (I really didn't want to manually input all those cleaner commands every single time). And it works every time, just the inconsistency of the GUI use (and I am more of a GUI user).

Originally posted by oshunluvr View Post

As usual with Linux, there's way more than one answer to the problem

That's what I love about Linux. It actually made computing fun again. I grew up with computers (I grew up during the rise of the PC (a time when Macs were thought of as PCs as well (and I still think of them that way despite their marketing campaign). Outside of a couple of quirks (which all platforms have them), I prefer the KDE environment the most.

Originally posted by MoonRise View Post

Welcome to KFN!!

Thank you!

Attached Files

**notabug** · Mar 10, 2019, 10:31 PM

RE: WWDERW

Nice intro. Welcome to KFN.

**oshunluvr** · Mar 11, 2019, 06:25 AM

WWDERW, the actual problem you're encountering is that you're try to run a GUI program as root. The ability to do this is going away completely when X goes away. It's generally dangerous and usually unnecessary. The plan going forward is to have an application that needs root level access be program to have that within the application - like Kate - rather than requiring the whole program run as root.

In the mean time, try launching Bleachbit with either of these methods;

/etc/alternatives/kdesu bleachbit

or

sudo -i bleachbit

Either of these should allow you to run Bleachbit as root but without endangering your home folder.

Source thread: https://www.kubuntuforums.net/showth.../73471-Kdesudo

**WWDERW** · Mar 11, 2019, 08:22 AM

Originally posted by oshunluvr View Post

/etc/alternatives/kdesu bleachbit

or

sudo -i bleachbit

Neither worked.

The former said that it couldn't connect to X server and the latter gave me the same error that I attached earlier.

**Snowhog** · Mar 11, 2019, 09:43 AM

Did you see my post #7?

**WWDERW** · Mar 11, 2019, 10:41 AM

Originally posted by Snowhog View Post

Did you see my post #7?

Yes, editing the desktop file (root version) yielded the same results as the attachment that I posted.

The only reliable method that I have found is to use the bash script, which is fine for my use, I'm just wondering why the need in KDE and in the GTK based ones, it's not any problem. Only reason that I can think is that Bleachbit is a GTK based program. I might be off my rocker, but that's the only thing that I can think of.

Announcement

Just Joined Yesterday

Just Joined Yesterday

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment