Comment 16 for bug 1377719

Hi Andrew. I did find something of note.

First, I re-ran your test, and had no problems (i.e., after running as
user, Bleachbit would run OK as admin, repeatedly, in fact). That test was:
1. Reboot Kubuntu
2. Start BleachBit as a normal use, but do not clean anything yet
3. Clean only "_System_ - Temporary Files" (If you do not want to
uncheck other boxes, please note you can right click on this option to
clean just the one option.)
4. Copy the list of files that were deleted, and save the list in a text
file.
5. Close BleachBit
6. Run "kdesudo bleachbit"
If #6 fails, would you please send me a list of files (step #4)?

And #6 did NOT fail -- it ran OK.

- - - - -
Then, I re-booted the PC
- - - - -

Then I did the 6-step test again, but this time the ONLY file I chose to
clean (as a normal user) was _*KDE*_-temporary files (I did not clean
any other files on this test run.)

It cleaned as follows (I'm no expert, but xauth does not look good!):

Delete 4.1kB /home/mike/.kde/tmp-mike-desktop14/xauth-1000-_0

Disk space recovered: 4.1kB
Files deleted: 1

Then, I closed Bleachbit and tried to run Bleachbit as admin, and it
failed to open, with this message:

No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning:
could not open display
   warnings.warn(str(e), _gtk.Warning)
Could not open X display

=> Thus, it looks like cleaning *KDE*-temporary files is causing the
problem?

--Mike

On 11/07/2014 04:01 PM, Andrew Ziem wrote:
> Hi Mike. Do you think rebooting Kubuntu (just once) helped resolve any
> issues caused by the older version? Do you agree the new version is
> fixed?
>