Announcement

Collapse
No announcement yet.

Doing the deed!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    Originally posted by geoaraujo View Post
    I do think that for now baloo is way worse than nepomuk. I had excluded my home folder from being searched as suggested here at forums, nevertheless, recently fan gone crazy and temperature was near 90ºC! I've checked what process were running and I had eight (!) baloo file extractor processes running. Something is definetely not right.
    In general I think that baloo is an improvement over nepomuk, but unfortunately the developer seems to repeat some of the same mistakes that nepomuk suffered from in it's early days (the baloo config dialog is a usability nightmare...if it's not the worst I have seen, it comes as a close second ).

    If you want to disable baloo file indexing, edit .kde/share/config/baloofilerc
    Change "Indexing-Enabled" to "false"

    Comment


      #47
      I went to do this as you suggested, but tt seems that it was already disabled.

      My file reads
      Code:
      [Basic Settings]
      Indexing-Enabled=false
      
      [General]
      exclude filters=autom4te,*.rcore,CTestTestfile.cmake,*.o,*.omf,.hg,*.m4,*.orig,.obj,moc_*.cpp,conftest,.pch,.xsession-errors*,CMakeTmpQmake,*.tmp,qrc_*.cpp,po,.svn,.histfile.*,lzo,.bzr,.git,litmain.sh,cmake_install.cmake,CMakeFiles,*.pc,*.nvram,*.elc,*.la,.moc,CMakeCache.txt,confdefs.h,*.gmo,*.csproj,*.rej,config.status,lost+found,confstat,*.pyc,_darcs,CVS,.uic,*.part,libtool,*.aux,*.po,CMakeTmp,Makefile.am,*.lo,ui_*.h,*.loT,*~,*.moc,*.vm*,*.class,core-dumps
      exclude filters version=2
      exclude folders[$e]=$HOME/
      exclude mimetypes=
      first run=false
      folders[$e]=

      Comment


        #48
        Do you have your kde set to restore previous session on login (that might restore on login the baloo file extractor processes that were running at logout)?

        The setting is in SystemSettings>Startup&Shutdown>Session
        If so, you can try either of the following:
        1. Make sure baloo file extractor processes are not running when you log out next (kill them if you need to), this should prevent them from appearing on subsequent sessions (since you have indexing disabled)
        2. Change the session setting to "always start an empty session"
        Last edited by kubicle; Apr 15, 2014, 09:21 AM.

        Comment


          #49
          Originally posted by kubicle View Post
          Do you have your kde set to restore previous session on login (that might restore on login the baloo file extractor processes that were running at logout)?

          The setting is in SystemSettings>Startup&Shutdown>Session
          If so, you can try either of the following:
          1. Make sure baloo file extractor processes are not running when you log out next (kill them if you need to), this should prevent them from appearing on subsequent sessions (since you have indexing disabled)
          2. Change the session setting to "always start an empty session"
          I'll try that, thanks.

          Comment

          Working...
          X