Results 1 to 3 of 3

Thread: Bleach bit deepscan

  1. #1
    Join Date
    Jan 2016

    Bleach bit deepscan

    I'm running a deepscan with bleach bit but even though I know this takes a long time no indication appears on screen to say how long it will take or if it's still running successfully. It's tempting to abandon it after several hours but could still be working ? Would the community oblige and give me the low down on this. Thank you Terry

  2. #2
    Join Date
    Feb 2010
    Obscurial Springs
    Ubuntu Budgie Development Release

    Re: Bleach bit deepscan

    Hello and Welcome

    I've never had BB take more than a minute to finish the deepscan portion and a progress bar should appear next to active . I see no problem canceling the process if it's been hours. I exclude some actions under system that I'm not comfortable with including memory and free disk space. The later could take a very long time.
    Attached Images Attached Images
    “Start where you are. Use what you have. Do what you can".

    Ubuntu Documentation Search: Popular Pages
    Ubuntu: Security Basics
    Ubuntu: Flavors

  3. #3
    Join Date
    Sep 2011

    Re: Bleach bit deepscan

    It can easily take several hours if you have it set to wipe free space on a large partition.

    The deep scan per se alone, no, not in my experience at least.

    If you did the wipe free space option and didn't mean to, or have changed your mind, you can kill it but it will leave a huge set of files behind that will take hours and hours to rm. It might even be easier in that case to copy your good data off that partition to somewhere else and then reformat it. If you decide to rm it instead it will bog down your system. I've been doing this off and on for quite a few hours now (days? sure seems like) now and even niced 19 it bogs down my system terribly.

    If you didn't have that option set something has probably gone wrong unless you have a very unusual setup.

    However, Bleachbit WILL often appear to have hung in the gui when it actually IS working. I always run it by starting it in a terminal so that I can tell the diference between the gui looking jammed or even blank even though it is chugging right along underneath and an actual hang. Also, it can tell you exactly WHAT is taking so long. You can also run it ENTIRELY in a terminal without the overhead of the gui at all, but that is another subject.
    Last edited by Dreamer Fithp Apprentice; January 28th, 2016 at 02:29 AM.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts