Bug 282678

Summary: easy way to disable beagle completely during installation
Product: [openSUSE] openSUSE 10.3 Reporter: Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component: InstallationAssignee: Gary Ekker <gekker>
Status: RESOLVED FEATURE QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P5 - None CC: aj, deanjo, forgotten_RlXLgpWK5h, kevin.dupuy, meissner, neiskam, richard.bos, vaclavik
Version: Alpha 4plus   
Target Milestone: ---   
Hardware: Other   
OS: Other   
See Also: https://fate.suse.com/303367
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 341832    

Description Forgotten User --EoyBps8f 2007-06-10 16:48:05 UTC
Even when started with nice beagle (including the cron-job) can lead to serious performance issues on older hardware because of its CPU, RAM and harddisk usage, the latter two not being handled by nice AFAIK.

Even if it is only at the beginning, this "beginning" is the time a user measures the performance and snappyness of his new installation and obviously this "beginning" is not a fixed time-period but much longer on older hardware with less RAM and slower harddisks.

Advanced users might know how to enter the package-management and disable it, most do not and should not have to. A simple checkbox with a line of explanation that on older hardware and for those who do not need a desktop-search beagle can be disabled completely would suffice.

I am not sure whether strigi will replace beagle for those that install KDE4 and whether strigi is as performance-hungry as beagle is, yet if so a more general checkbox would be the better solution that disables either of the two, depending which desktop is installed.
Comment 1 Forgotten User RlXLgpWK5h 2007-06-10 18:04:03 UTC
I also want to state, that in my eyes this is currently one of the biggest flaws in openSUSE installation. On slower computers beagle simply cannot be used, it even takes long to remove it graphically, beacause it is hogging up resources all the time. And I have a fast computer, and I do not want a tool which works in the background all the time. I knew where my files are and how to remove them. So, I do not want beagle, but it is really not an easy task to remove it, beacause you must know what you want to remove first... Would be cool, if there is one more dialog box during the installation, which asks you wether you want beagle or not on your computer..

Just my 2cents
Comment 2 Juraj VáclavíÂk 2007-06-13 06:08:40 UTC
I prefer to set default instalafion WITHOUT beagle/kerry, independent of other sw selection. It dramatically reduced the efficiency of PC and I do not know any user what uses this feature (I maintain about 10 desktop PC with Linux and about 60 PC with Windows). I think, that speed of start of new installed PC is very important for acceptance by new users.
Comment 3 Andreas Jaeger 2007-07-02 16:58:08 UTC
Gary, could you evaluate and drive this, please?
Comment 4 Dean Hilkewich 2007-09-06 22:23:17 UTC
Agreed having beagle on default is VERY annoying.
Comment 5 Kevin Dupuy 2007-09-21 03:14:04 UTC
Perhaps "Desktop Search" should be made as a pattern, so one click and it's off, but Beagle SHOULD definatly be included in the default installation of openSUSE. Too few distros include such a useful feature. Many folks don't use it because they don't know it's there, or it works.

PS: I have a cheap Acer with 1.7 G Processor and 512 MB memory and Beagle doesn't slow me down at all...
Comment 6 Nikolay Paskov 2007-09-26 16:21:16 UTC
We are not discussing here to remove beagle at all but having an option to disable it from the very beginning. It will be really very useful.
Comment 7 Juraj VáclavíÂk 2007-09-27 05:54:48 UTC
I think, that "Desktop Search" as a pattern is a very good suggestion. I would be very satisfied by it.
Comment 8 Joe Shaw 2007-09-27 21:14:51 UTC
(In reply to comment #0 from Sven Burmeister)
> Even if it is only at the beginning, this "beginning" is the time a user
> measures the performance and snappyness of his new installation and obviously
> this "beginning" is not a fixed time-period but much longer on older hardware
> with less RAM and slower harddisks.

This to me is more of a problem with the way cron jobs are handled in SUSE than necessarily a Beagle thing[*].  The fact that daily cron jobs are run 15 minutes after the initial install is not a very good idea, IMO, because of the reason you gave: it's when the user measures the performance and snappiness of the installation.

[*] (Not that I disagree with you about not installing Beagle on slower machines.  Desktop search is probably untenable there in any case.)

> I am not sure whether strigi will replace beagle for those that install KDE4
> and whether strigi is as performance-hungry as beagle is, yet if so a more
> general checkbox would be the better solution that disables either of the two,
> depending which desktop is installed.

The bottom line of desktop search is the same, regardless of which system you use: it has to parse and extract information from essentially every single file on your system, or at least your home directory.  This has extremely high overhead in terms of the disk (there's no getting around having to read the bytes off the disk) and in CPU usage (all those file formats have to be parsed).

There are obviously tradeoffs to be made and in the end Strigi might be better suited to the task, but my suspicion is that if a system can't reasonably handle Beagle, Strigi probably won't fare much better.  Conditional install based on system resources just makes sense.
Comment 9 Gary Ekker 2007-10-01 19:19:24 UTC
I will move this to fate Code11.
Comment 10 Richard Bos 2007-10-09 18:54:40 UTC
Perhaps the installation can created the flag file:
/var/spool/cron/lastrun/cron.daily during installation.  If this will be
done the cron.daily scripts won't be executed untill next day.

If it can be done, it's a simple solution :)
Comment 11 Gary Ekker 2008-01-18 20:54:05 UTC
Moved to the feature tracking tool for 11.0.
Comment 12 Bugzilla Account Maintenance 2008-09-02 18:07:48 UTC
Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."
Comment 13 JP Rosevear 2008-09-11 21:16:46 UTC
Fix resolution.