Bug 290349

Summary: [wish] Add support to save results to eliminate re-scanning each time
Product: [Applications] filelight Reporter: Steve <robo116>
Component: generalAssignee: Martin Sandsmark <martin.sandsmark>
Status: REPORTED ---    
Severity: wishlist CC: audvare, karaluh, kde.lwzr1, markd, postix, yuri
Priority: NOR    
Version First Reported In: 1.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=489927
https://bugs.kde.org/show_bug.cgi?id=290890
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Session Errors 1-3-12
Error and Widget failure to auto update
Screenshot of bug report

Description Steve 2012-01-01 21:58:08 UTC 
Version:           1.0 (using KDE 4.7.3) 
OS:                Linux

I am suggesting to add some sort of method to allow the ability to save the FileLight scan results and review them later on.  Possibly adding a Save button (under the Scan menu) that will save the results to a local directory or a specified location.  You could incorporate the open dialog box to allow both a standard directory (to scan) as it is today, but add the support to open the configuration or results file.

Reproducible: Always

Steps to Reproduce:
Can't reproduce it if it doesn't exist


Expected Results:  
The same....unless we implement the new feature!

The addition to save a specific scan results or data isn't full appreciated in a standard PC configuration.  Usually a smaller HD that only takes a couple of minutes to scan.

However, larger RAID arrays, general Linux users (which have multiple HD's, with various distro's, OS's, etc installed) it would be very beneficial.  I ran FileLight on my PowerEdge RAID server which shares ~3TB of data in various directories and takes some time to scan (along with errors to get through as well when detecting certain folders on the share).  So for doing large directories such as this it allows me to refer back to the volume layout and see what is using so much data and where, and only re-initiate the scan when needed.

Can help out as needed to come up with ideas or general support if it would be beneficial
Comment 1 Steve 2012-01-04 04:28:49 UTC 
Created attachment 67423 [details]
Session Errors 1-3-12

Session Errors copied directly from terminal as login crashed
Comment 2 Steve 2012-01-04 04:31:58 UTC 
Created attachment 67424 [details]
Error and Widget failure to auto update

Screenshot of Error upon login
-Widget had trouble autoupdating (minor issue)
-Lancelot has issues
-Cannot Shutdown, Restart, Logoff, etc from menus.  Need to run from terminal to shutdown; or restart X
Comment 3 Steve 2012-01-04 04:33:28 UTC 
Created attachment 67425 [details]
Screenshot of bug report

Probably not of any use, but shows what failed and wants to send a bug report
-Couldn't collect any valuable data (or anything useful); so it won't let me submit otherwise I would try to link it to this.
Comment 4 Steve 2012-01-04 04:41:16 UTC 
Sorry, please ignore Comments 1, 2 & 3
Comment 5 Steve 2012-01-04 05:17:28 UTC 
Please review latest session log as there are multiple entries of various failures, dbus errors, etc.

I just don't know what i'm looking at :)
Comment 6 Mark Diekhans 2013-11-04 06:39:29 UTC 
Ideally scanning could optionally be done by a non-gui program that icould be run in a cron job.
The result of the scan then given to filelight to explore.

it's an amazing program!
Comment 7 karaluh 2013-11-20 13:09:27 UTC 
Saving results isn't going to help, cache is the answer. And there's nothing ideal in cron jobs, inotify might do the trick, but that's a separate issue.
Comment 8 Thibault Molleman 2021-01-04 07:25:23 UTC 
Filelight is such an amazing tool, yet it still lakes this basic functionality. Hopefully someone can implement this in the near future!
Comment 9 postix 2024-07-08 13:48:15 UTC 
*** Bug 395973 has been marked as a duplicate of this bug. ***