[Bug 261583] New: Bleachbit(as root) froze the desktop;I restarted and bleachbit(not as root) worked and then craxhed desktop.

ebbridge at gmail.com ebbridge at gmail.com
Thu Dec 30 00:19:31 GMT 2010


https://bugs.kde.org/show_bug.cgi?id=261583

           Summary: Bleachbit(as root) froze the desktop;I restarted and
                    bleachbit(not as root) worked and then craxhed
                    desktop.
           Product: kde
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: ebbridge at gmail.com


Version:           unspecified
OS:                Linux

My operating system is Ubuntu/Kubuntu 10.10,up to date as of this afternoon.
Having started with Ubuntu,I installed the Kubuntu plasma from Synaptic Package
Manager,and rebooted into KDE. The bleachbit(as root) cleaner(yes,I'm reporting
this to BB as well) asked me twice for the password. When the cleaner finally
came up,it froze the desktop and the mouse,with a vertical line where the arrow
normally is.<p>I disconnected and rebooted and ran the bleachbit (not as root)
which functioned perfectly. As soon as it stopped,I got a crash report.<p>It
prompted me to file a bug,which I attempted to do. It asked me to install some
bug reporting software,which I attempted to do,but would not do so,because it
said it had no authorization to install it,and would not prompt me for a
password.I went around in a circle with this three times.

Reproducible: Always

Steps to Reproduce:
I shut down and booted to Ubuntu. When I attempted to run bleachbit there,it
would not load the as root version,instead giving me the generic version.<p>I
went back into KDE,and again,it crashed;*but then reloaded and worked correctly
for a while,before crashing again.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list