[sweeper] [Bug 503792] New: KDE Sweeper does not clear the cache of Falkon browsers

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Mon May 5 12:33:16 BST 2025


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

            Bug ID: 503792
           Summary: KDE Sweeper does not clear the cache of Falkon
                    browsers
    Classification: Applications
           Product: sweeper
           Version: 25.04.0
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: kdmw.629 at tuta.io
  Target Milestone: ---

SUMMARY
KDE Sweeper has an option to Clean the cookies, history and temporary cache of
websites visited along with other options. However it does not clear the cache,
history and cookies of KDE Falkon browser. 

STEPS TO REPRODUCE
1.  Launch Falkon browser. Visit a few websites like google.com, yahoo.com,
outlook.com, gmail.com and log into a few sites.
2. Close the KDE Falkon browser 
3. Check the size of directory $HOME/.cache/falkon/ or $XDG_CONFIG_HOME/falkon
by running the following commands
     du -sm $HOME/.cache/falkon/
     du -sm $XDG_CONFIG_HOME/falkon
4. Launch KDE Sweeper application
5. Select all the options under the section "Web Browsing" 
6. Click on the "Clean Up" button. 

OBSERVED RESULT
The cache of the Falkon browser is not cleared. This can be checked by
rerunning the commands given in the step number 3 above. 

EXPECTED RESULT
The cache of the Falkon browser should be cleared and the size of the falkon
directory should go to zero or close to zero (1-2 MB). This can be checked by
running the commands given in the step number 3 above. 

SOFTWARE/OS VERSIONS
Windows: NA
macOS: NA
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.3.4
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
None.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list