[opensuse] Baloo: Excessive Disk I/O
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, and it's even more ridiculous that the KDE dev who designed this piece of crap won't put in a feature to shut this piece of malware off. The next thing that's pissing me off is that when downloading torrents, Baloo goes completely nuts and sucks 25% of one core when the torrents are going and causes an extreme amount of disk I/O. How was this even released, because it's completely awful and I want it gone. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Apr 27, 2014 at 7:32 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, and it's even more ridiculous that the KDE dev who designed this piece of crap won't put in a feature to shut this piece of malware off. The next thing that's pissing me off is that when downloading torrents, Baloo goes completely nuts and sucks 25% of one core when the torrents are going and causes an extreme amount of disk I/O. How was this even released, because it's completely awful and I want it gone.
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded. I allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running. If BOINC is causing you issues with Baloo... isn't the "solution" then to exclude the BOINC directory? Or exclude everything in /home and Baloo has nothing to do? Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc and editing/adding this line Indexing-Enabled=false Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me. C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Correction below: On Sun, Apr 27, 2014 at 7:51 AM, C <smaug42@opensuse.org> wrote:
On Sun, Apr 27, 2014 at 7:32 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, and it's even more ridiculous that the KDE dev who designed this piece of crap won't put in a feature to shut this piece of malware off. The next thing that's pissing me off is that when downloading torrents, Baloo goes completely nuts and sucks 25% of one core when the torrents are going and causes an extreme amount of disk I/O. How was this even released, because it's completely awful and I want it gone.
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded. I allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running.
If BOINC is causing you issues with Baloo... isn't the "solution" then to exclude the BOINC directory? Or exclude everything in /home and Baloo has nothing to do?
Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended
Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc
That should be: $HOME/.kde4/share/config/baloofilerc
and editing/adding this line Indexing-Enabled=false
Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me.
C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The point is, that not everybody who uses Linux desktops know to exclude a directory that is written to constantly, and causes Baloo to eat up the system's resources. Does Windows do this? No, it doesn't. Here we have a situation where a "feature" is foisted upon users, and users have to dig into a configuration file to turn it off, and the dev know better than the users and they are _not_ going to put in a GUI switch to turn Baloo off because that's what they want, and what they want matters and that's the end of the story. There is no doubt that Baloo causes high disk I/O on my system and high CPU consumption with multiple torrents running. I killed it in KSysGuard and immediately my system returned to normal. Just because you haven't noticed something does not mean that it does not exist. On Sat, Apr 26, 2014 at 10:51 PM, C <smaug42@opensuse.org> wrote:
On Sun, Apr 27, 2014 at 7:32 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, and it's even more ridiculous that the KDE dev who designed this piece of crap won't put in a feature to shut this piece of malware off. The next thing that's pissing me off is that when downloading torrents, Baloo goes completely nuts and sucks 25% of one core when the torrents are going and causes an extreme amount of disk I/O. How was this even released, because it's completely awful and I want it gone.
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded. I allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running.
If BOINC is causing you issues with Baloo... isn't the "solution" then to exclude the BOINC directory? Or exclude everything in /home and Baloo has nothing to do?
Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended
Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc
and editing/adding this line Indexing-Enabled=false
Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me.
C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Apr 27, 2014 at 8:04 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
The point is, that not everybody who uses Linux desktops know to exclude a directory that is written to constantly, and causes Baloo to eat up the system's resources. Does Windows do this? No, it doesn't. Here we have a situation where a "feature" is foisted upon users, and users have to dig into a configuration file to turn it off, and the dev know better than the users and they are _not_ going to put in a GUI switch to turn Baloo off because that's what they want, and what they want matters and that's the end of the story. There is no doubt that Baloo causes high disk I/O on my system and high CPU consumption with multiple torrents running. I killed it in KSysGuard and immediately my system returned to normal. Just because you haven't noticed something does not mean that it does not exist.
Chill a litte. I wasn't defending Baloo. :-P Did you even read what I wrote?
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded.
This is why I hadn't seen any disk I/O. For whatever reason, after upgrading my home was excluded by default. I didnt' exclude it, so post upgrade, Baloo wasn't doing anything.
allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running.
This was my observations after enabling.
Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended
Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc
and editing/adding this line Indexing-Enabled=false
This is currently "how you disable". It's a new "feature" that, like any... needs some rethinking and rework. I've disabled it using the "false" setting and deleted the multi-gig sql index file in $HOME/.local/config If you go read the blog posts by the developer leads (such as this one: http://vhanda.in/blog/2014/04/desktop-search-configuration/ ) you can see that they went about this wrong... they were surprised at the backlash etc etc. Basically they didn't realize that there were users that don't actually.. you know... need Desktop Search capability.
Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me.
As you can see... I'm on your side here. I don't use search. I don't want search. It's wasted on me. I'll try it, but it's more work for me to search for things than to just go to where I stored it (I'm OCD about keeping my data organized so finding things is easy... for me). C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, and it's even more ridiculous that the KDE dev who designed this piece of crap won't put in a feature to shut this piece of malware off. The next thing that's pissing me off is that when downloading torrents, Baloo goes completely nuts and sucks 25% of one core when the torrents are going and causes an extreme amount of disk I/O. How was this even released, because it's completely awful and I want it gone.
This will prevent baloo from running automatically. open up a konsole window: $ su password: #type the rooot password here # F=`which baloo` # mv $F $F.moved # exit $ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-27 02:26 (GMT-0400) Dirk Gently composed:
This will prevent baloo from running automatically.
open up a konsole window:
$ su password: #type the rooot password here # F=`which baloo` # mv $F $F.moved # exit $
As will the documented: in: ~/.kde/share/config/baloofilerc change "Indexing-Enabled=true" to "Indexing-Enabled=false" If baloofilerc doesn't exist, or Indexing-Enabled, does not exist, create. It's not hard. I looked it up before doing any upgrading from from pre-4.13. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/04/14 07:26, Dirk Gently wrote:
This will prevent baloo from running automatically.
open up a konsole window:
$ su password: #type the rooot password here # F=`which baloo` # mv $F $F.moved # exit $
DON'T do this - it will stop baloo from running _until_the_next_update_ Instead, use Felix's method of editing the personal config file in your home directory - because of course, that's the *correct* way to configure things. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Can anyone else confirm if they are having the same issues as I am? I do use search, and I know how to disable it or find the info to disable it, I just want to se On Sat, Apr 26, 2014 at 11:21 PM, C <smaug42@opensuse.org> wrote:
On Sun, Apr 27, 2014 at 8:04 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
The point is, that not everybody who uses Linux desktops know to exclude a directory that is written to constantly, and causes Baloo to eat up the system's resources. Does Windows do this? No, it doesn't. Here we have a situation where a "feature" is foisted upon users, and users have to dig into a configuration file to turn it off, and the dev know better than the users and they are _not_ going to put in a GUI switch to turn Baloo off because that's what they want, and what they want matters and that's the end of the story. There is no doubt that Baloo causes high disk I/O on my system and high CPU consumption with multiple torrents running. I killed it in KSysGuard and immediately my system returned to normal. Just because you haven't noticed something does not mean that it does not exist.
Chill a litte. I wasn't defending Baloo. :-P
Did you even read what I wrote?
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded.
This is why I hadn't seen any disk I/O. For whatever reason, after upgrading my home was excluded by default. I didnt' exclude it, so post upgrade, Baloo wasn't doing anything.
allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running.
This was my observations after enabling.
Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended
Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc
and editing/adding this line Indexing-Enabled=false
This is currently "how you disable". It's a new "feature" that, like any... needs some rethinking and rework. I've disabled it using the "false" setting and deleted the multi-gig sql index file in $HOME/.local/config
If you go read the blog posts by the developer leads (such as this one: http://vhanda.in/blog/2014/04/desktop-search-configuration/ ) you can see that they went about this wrong... they were surprised at the backlash etc etc. Basically they didn't realize that there were users that don't actually.. you know... need Desktop Search capability.
Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me.
As you can see... I'm on your side here. I don't use search. I don't want search. It's wasted on me. I'll try it, but it's more work for me to search for things than to just go to where I stored it (I'm OCD about keeping my data organized so finding things is easy... for me).
C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Ne 27. dubna 2014 00:25:37, Lars Kruczynski napsal(a):
Can anyone else confirm if they are having the same issues as I am?
I also have huge disk usage, even Baloo now (after initial reindexing) doesn't use much CPU. It causes terrible lags, so that the computer (powerful one) is practically unusable. When I pause all baloo processes, computer runs perfectly... :-/ I'm thinking if I remove it completely or let it run only when I'm not in the front of it and hoping it gets better... :-/ V, -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On Saturday 26 of April 2014 22:32:14 Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, (BIIIP)
Hi Lars, you can remove baloo-file, baloo-pim and baloo-tools packages, that will stop baloo from doing anything, as it's binaries are in these packages. Cheers, Hrvoje
Thank you, but it seems the developer is already getting a lot of backlash over baloo, one thing being that there isn't an enable or disable switch. I want file indexing, but baloo isn't working like it should; I have just read a lot of comments from people who are experiencing the same problems with heavy disk I/O and high CPU utilization, and the developer also mentioned there is a bug in baloo_file_cleaner, which explains the infinite loop it was stuck in yesterday. Here is the quote: "There seems to be a bug within the baloo_file_cleaner that was not caught during the many phases of testing. Please feel free to kill the cleaner process. With regard to security, it was this *baloo_file_cleaner* process that was making sure that the file is no longer stored in the index." http://vhanda.in/blog/2014/04/desktop-search-configuration/ Some of the comments are quite funny, like this one: "Baloo is just the worst piece of software I have EVER seen." or "I DON'T WANT FUCKING INDEXING OF MY CONTENTS!!!! At this time I simply remove all the fucking akonadi/baloo/nepomuk/other shit out of my system. Next time I remove all the KDE Environment. Nice try!" I have to say, that for a non-beta release of KDE...it's quite perplexing that baloo made it through all the betas and ended up like it is now. If I can catch it doing buggy things within minutes of using it, it makes one start wondering if they really tried it very much with large 1-3 TB drives 100% full of files, and running torrents, BOINC, etc. On Sun, Apr 27, 2014 at 4:46 AM, šumski <hrvoje.senjan@gmail.com> wrote:
On Saturday 26 of April 2014 22:32:14 Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, (BIIIP)
Hi Lars, you can remove baloo-file, baloo-pim and baloo-tools packages, that will stop baloo from doing anything, as it's binaries are in these packages.
Cheers, Hrvoje -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/27/2014 04:57 AM, Lars Kruczynski wrote:
I have to say, that for a non-beta release of KDE...it's quite perplexing that baloo made it through all the betas and ended up like it is now. If I can catch it doing buggy things within minutes of using it, it makes one start wondering if they really tried it very much with large 1-3 TB drives 100% full of files, and running torrents, BOINC, etc.
What are these betas you were referring to? I've been keeping up with the KDE4 channel and I never saw a single instance of any betas available that included Baloo. Also, It would be nice if we could read the manual, (what manual!!!???), but not a shred of documentation came with baloo. If you look into baloofilerc you will see that you can exclude file types, and directories from indexing. It seems that excluding huge binary files like iso files and entire directories that are in use by bittorrent would be the solution to your problem. Remember there was a word of warning about the fact that it indexes your entire home directory unless you put in exclusions. In my case I excluded directories that contained my Virtual Machine disk image files. That criticism notwithstanding, I am NOT seeing any huge disk IO or cpu loading issues, even as I recompile entire subsystems with many many files. I think your issue is one of tuning. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be. On Sun, Apr 27, 2014 at 4:46 AM, šumski <hrvoje.senjan@gmail.com> wrote:
On Saturday 26 of April 2014 22:32:14 Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, (BIIIP)
Hi Lars, you can remove baloo-file, baloo-pim and baloo-tools packages, that will stop baloo from doing anything, as it's binaries are in these packages.
Cheers, Hrvoje -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dolphin will not open when breaking the packages; I just tried it. So, I think the suggestion to remove baloo isn't a good one, unless there is a different way to do it. On Sun, Apr 27, 2014 at 5:29 PM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
On Sun, Apr 27, 2014 at 4:46 AM, šumski <hrvoje.senjan@gmail.com> wrote:
On Saturday 26 of April 2014 22:32:14 Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, (BIIIP)
Hi Lars, you can remove baloo-file, baloo-pim and baloo-tools packages, that will stop baloo from doing anything, as it's binaries are in these packages.
Cheers, Hrvoje -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 27 of April 2014 17:40:49 Lars Kruczynski wrote:
Dolphin will not open when breaking the packages; I just tried it. So, I think the suggestion to remove baloo isn't a good one, unless there is a different way to do it.
Can you paste commands used, and zypper output when you tried it? Note that you *cannot* remove libbaloofiles4, etc, but only packages i listed. Also make sure you have the latest packages from KDE:Current Cheers, Hrvoje
On 4/27/2014 5:29 PM, Lars Kruczynski wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
See this Page where the arrogant developer talks about how he is forcging this thing down everyone's throat: http://vhanda.in/blog/2014/04/desktop-search-configuration/ Also notice this one hint he gives about shutting it off..
There is no explicit “Enable/Disable” button any more. We would like to promote the use of searching and feel that Baloo should never get in the users way. However, we are smart about it and IF you add your HOME directory to the list of “excluded folders”, Baloo will switch itself off since it no longer has anything to index.
-- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
What is wrong with simply editing: $HOME/.kde4/share/config/baloofilerc changing this line: Indexing-Enabled=false That turns it off. That does NOT break your RPM database. That does not cause any drama. It just works. C. On Mon, Apr 28, 2014 at 2:40 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
Dolphin will not open when breaking the packages; I just tried it. So, I think the suggestion to remove baloo isn't a good one, unless there is a different way to do it.
On Sun, Apr 27, 2014 at 5:29 PM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
On Sun, Apr 27, 2014 at 4:46 AM, šumski <hrvoje.senjan@gmail.com> wrote:
On Saturday 26 of April 2014 22:32:14 Lars Kruczynski wrote:
I'm not impressed with Baloo at all, in fact it's really slowing my computer down and KDE 4.13 so far has been a drag all because of Baloo. When running BOINC, Baloo constantly wants to index everything BOINC writes to the disk which is frequent. Yes, I can exclude the BOINC directory, but there's no GUI option for a new user to shut off Baloo which is ridiculous, (BIIIP)
Hi Lars, you can remove baloo-file, baloo-pim and baloo-tools packages, that will stop baloo from doing anything, as it's binaries are in these packages.
Cheers, Hrvoje --
-- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Ne 27. dubna 2014 14:02:10, John Andersen napsal(a):
On 04/27/2014 04:57 AM, Lars Kruczynski wrote:
I have to say, that for a non-beta release of KDE...it's quite perplexing that baloo made it through all the betas and ended up like it is now. If I can catch it doing buggy things within minutes of using it, it makes one start wondering if they really tried it very much with large 1-3 TB drives 100% full of files, and running torrents, BOINC, etc.
What are these betas you were referring to? I've been keeping up with the KDE4 channel and I never saw a single instance of any betas available that included Baloo.
Also, It would be nice if we could read the manual, (what manual!!!???), but not a shred of documentation came with baloo.
If you look into baloofilerc you will see that you can exclude file types, and directories from indexing. It seems that excluding huge binary files like iso files and entire directories that are in use by bittorrent would be the solution to your problem.
Remember there was a word of warning about the fact that it indexes your entire home directory unless you put in exclusions. In my case I excluded directories that contained my Virtual Machine disk image files.
That criticism notwithstanding, I am NOT seeing any huge disk IO or cpu loading issues, even as I recompile entire subsystems with many many files.
I think your issue is one of tuning.
For me, this is big regression. Latest Nepomuk from 4.12 worked by order of magnitude better. Recently, Nepomuk was indexing comparable amount of data (new install) and it was faster and not consuming so much resources. Baloo can make computer equipped by i7 CPU running 8x3.2 GHz and 16 GB RAM completely unusable! I know, that over 680 GB is much, but still, background service should never ever cause continuous lags. Software doing that is simply a crap. I wish indexing and things like autocompletion from address books in KMail (it required Nepomuk, so I think now it requires Baloo) etc., but what can I do? Let the computer run for whole week and not touch it in hope, that Baloo will finish its work? It's just a joke. Well written file indexer is supposed to work unnoticed on background. This is not well written software. Also, how can I check how much files are already indexed? Nepomuk showed amount of files, as well as percent of PIM data. Why does it came without better GUI? Seriously, I like KDE and I don't want only to complain, but why are KDE devs all the time breaking something? I don't understand the logic, when finally one get well working software and when it is OK, it is replaced by... ehm... sort of think like that... Similar with KMail and KOrganizer. They have much better features then Thunderbird or Evolution (in my humble opinion), but sometimes there are problems with Akonadi and unpleasant bugs. It is breaking the trust. Finally, I hope there will be soon some fix for Baloo... I need the computer for work, so I'm keeping it off... All the best, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
John Andersen wrote:
On 4/27/2014 5:29 PM, Lars Kruczynski wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
See this Page where the arrogant developer talks about how he is forcging this thing down everyone's throat:
I really liked this one: "Please trust the developers to keep sensible defaults." :-) -- Per Jessen, Zürich (8.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2014 04:27 AM, Per Jessen wrote:
John Andersen wrote:
On 4/27/2014 5:29 PM, Lars Kruczynski wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
See this Page where the arrogant developer talks about how he is forcging this thing down everyone's throat:
I really liked this one:
"Please trust the developers to keep sensible defaults."
Indeed. The change from "index only what I tell you" to "index everything except what I tell you" is a perfect example of how the developers know better because they have this device the NSA gave them which scans the users' deep consciousness and determines what they really need despite what they say they want, so as to determine what is really, really best for them. No matter what they say they think they want. These devices have been available to governments and various governmental departments and political leaders for some while now (probably since the beginning of the century at least), and it seems that either they or their OpenSource equivalent are now becoming commercially available I have a suspicion that these devices were actually developed by Google based on a failed prototype from Microsoft, but that's probably off topic for this forum. -- Faith may be defined briefly as an illogical belief in the occurrence of the improbable...A man full of faith is simply one who has lost (or never had) the capacity for clear and realistic thought. He is not a mere ass: he is actually ill. -- H. L. Mencken -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In prior version of KDE, Nepomuk's indexing feature was disabled by default, so I never used it. Just for testing purposes, I once tried switching indexing on through the Nepomuk GUI and a process or two started, yet my hard drive didn't seem to be doing anything. Either Nepomuk was broken, or it was unobtrusively indexing my files and didn't hog system resources. It's hard for me to compare Baloo to Nepomuk when, from my impression, Nepomuk wasn't doing anything even when the indexing feature was turned on. Baloo is a whole different story, and I had to turn it off because it was giving me performance problems. I didn't like that by default it's switched on, so the second you log into KDE it starts indexing. I hadn't kept up with any of the changes that were coming with KDE 4.13, and trusted that it would be an improvement over 4.11.4. Therefore, when I was having all types of performance issues related to disk I/O and CPU utilization, it took me time to track down how to finagle with Baloo and stop it. I was surprised that the GUI offers barely any options, and that it's opt-out and not opt-in. I looked around the internet some, and I found a funny post on the Kubuntu forum: "After a few days baloo settled down on my system but on my wife's laptop baloo kept going and going for days making it really difficult to do anything. I found a message that ~/.kde/share/config/baloofilerc has a line in it under [Basic Settings] Indexing-Enabled=true I changed that to Indexing-Enabled=false and the laptop was useable again, but lost a few search items. It's nice when it works but hell when it hogs the system." I love the beginning where he says: "After a few days", and keep in mind that the 2.5" hard drive on his wife's laptop isn't exactly an icon for longevity. I can only imagine the wear and tear the first iteration of Baloo is doing to SSD's. Baloo shouldn't start automatically the first time a user logs into KDE, but I hate when OS's ask you questions through a dialogue box when you just want to get stuff done. I don't have an answer to how this should be done correctly, but I want to reaffirm that Baloo should _not_ start indexing anything without the user's permission. They're already talking about allowing it to be uninstalled by having the Baloo package be split. I want this, because I want to uninstall it. And if my supposition is correct, I don't think I'll ever be installing it again -- not that I don't think it can become better. I just don't need it. On Mon, Apr 28, 2014 at 4:10 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
On 04/28/2014 04:27 AM, Per Jessen wrote:
John Andersen wrote:
On 4/27/2014 5:29 PM, Lars Kruczynski wrote:
That method brings up dependency warnings of wanting to downgrade dolphin and gwenview. I just want it completely gone, should I choose break? Will there be an option in the future to not install Baloo at all? Because there should be.
See this Page where the arrogant developer talks about how he is forcging this thing down everyone's throat:
I really liked this one:
"Please trust the developers to keep sensible defaults."
Indeed. The change from "index only what I tell you" to "index everything except what I tell you" is a perfect example of how the developers know better because they have this device the NSA gave them which scans the users' deep consciousness and determines what they really need despite what they say they want, so as to determine what is really, really best for them. No matter what they say they think they want.
These devices have been available to governments and various governmental departments and political leaders for some while now (probably since the beginning of the century at least), and it seems that either they or their OpenSource equivalent are now becoming commercially available
I have a suspicion that these devices were actually developed by Google based on a failed prototype from Microsoft, but that's probably off topic for this forum.
-- Faith may be defined briefly as an illogical belief in the occurrence of the improbable...A man full of faith is simply one who has lost (or never had) the capacity for clear and realistic thought. He is not a mere ass: he is actually ill. -- H. L. Mencken -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 28 Apr 2014, Sam M wrote: [..]
get stuff done. I don't have an answer to how this should be done correctly, but I want to reaffirm that Baloo should _not_ start indexing anything without the user's permission. They're already talking about allowing it to be uninstalled by having the Baloo package be split. I want this, because I want to uninstall it.
Full ACK. I'm boggling at the arrogance of those developers. But you can uninstall it, you don't have to believe the political deps: 13.1/w.KDE 4.13.0: $ rpm -qa '*baloo*' '*nepomuk*' '*akonadi*' '*strigi*' '*redland*' \ *soprano*' kdebase4-runtime | sort baloo-core-4.13.0-3.2.x86_64 kdebase4-runtime-4.13.0-3.1.x86_64 libakonadi4-4.13.0-3.1.x86_64 libakonadiprotocolinternals1-1.12.1-2.1.x86_64 libbaloofiles4-4.13.0-3.2.x86_64 libbaloowidgets4-4.13.0-2.1.x86_64 libsoprano4-2.9.3-3.2.1.x86_64 libstrigi0-0.7.8-8.49.x86_64 nepomuk-core-4.13.0-3.1.x86_64 soprano-backend-redland-2.9.3-3.2.1.x86_64 That is all that you really need. All other deps are "political" deps. Features (the search) will not work. But the programs will run. Same with pulseaudio BTW ;) Taboos: # zypper ll | egrep 'baloo|akonadi|strigi|nepomuk|soprano|redland' |\ grep -v python 101 | strigi | package | (any) 165 | akonadi-runtime | package | (any) 169 | plasma-addons-akonadi | package | (any) 250 | soprano | package | (any) 362 | baloo-tools | package | (any) 363 | kdenetwork-strigi-analyzers | package | (any) 366 | baloo-file | package | (any) 367 | baloo-kioslaves | package | (any) I think I "broke" some packages (dolphin etc.) too. Don't be shy to do the same. 12.1/w.KDE 4.8.5: $ rpm -qa '*baloo*' '*nepomuk*' '*akonadi*' '*strigi*' '*redland*' \ *soprano*' kdebase4-runtime kdebase4-runtime-4.8.5-382.18.x86_64 libakonadi4-4.8.5-291.4.x86_64 libakonadiprotocolinternals1-1.7.2-121.4.x86_64 libredland0-1.0.14-7.1.3.x86_64 libsoprano4-2.8.0-122.5.x86_64 libstrigi0-0.7.7-74.5.x86_64 HTH, -dnh -- Du vergisst die Kunden, die sich Windows-"Lösungen" andrehen lassen. Die kaufen auch Scheiße in Dosen incl. Wartungsvertrag. -- Holger Marzen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2014 08:37 PM, David Haller wrote:
Hello,
On Mon, 28 Apr 2014, Sam M wrote: [..]
get stuff done. I don't have an answer to how this should be done correctly, but I want to reaffirm that Baloo should _not_ start indexing anything without the user's permission. They're already talking about allowing it to be uninstalled by having the Baloo package be split. I want this, because I want to uninstall it.
Full ACK. I'm boggling at the arrogance of those developers. But you can uninstall it, you don't have to believe the political deps:
13.1/w.KDE 4.13.0:
$ rpm -qa '*baloo*' '*nepomuk*' '*akonadi*' '*strigi*' '*redland*' \ *soprano*' kdebase4-runtime | sort baloo-core-4.13.0-3.2.x86_64 kdebase4-runtime-4.13.0-3.1.x86_64 libakonadi4-4.13.0-3.1.x86_64 libakonadiprotocolinternals1-1.12.1-2.1.x86_64 libbaloofiles4-4.13.0-3.2.x86_64 libbaloowidgets4-4.13.0-2.1.x86_64 libsoprano4-2.9.3-3.2.1.x86_64 libstrigi0-0.7.8-8.49.x86_64 nepomuk-core-4.13.0-3.1.x86_64 soprano-backend-redland-2.9.3-3.2.1.x86_64
That is all that you really need. All other deps are "political" deps. Features (the search) will not work. But the programs will run. Same with pulseaudio BTW ;) Taboos:
# zypper ll | egrep 'baloo|akonadi|strigi|nepomuk|soprano|redland' |\ grep -v python 101 | strigi | package | (any) 165 | akonadi-runtime | package | (any) 169 | plasma-addons-akonadi | package | (any) 250 | soprano | package | (any) 362 | baloo-tools | package | (any) 363 | kdenetwork-strigi-analyzers | package | (any) 366 | baloo-file | package | (any) 367 | baloo-kioslaves | package | (any)
I think I "broke" some packages (dolphin etc.) too. Don't be shy to do the same.
12.1/w.KDE 4.8.5:
$ rpm -qa '*baloo*' '*nepomuk*' '*akonadi*' '*strigi*' '*redland*' \ *soprano*' kdebase4-runtime kdebase4-runtime-4.8.5-382.18.x86_64 libakonadi4-4.8.5-291.4.x86_64 libakonadiprotocolinternals1-1.7.2-121.4.x86_64 libredland0-1.0.14-7.1.3.x86_64 libsoprano4-2.8.0-122.5.x86_64 libstrigi0-0.7.7-74.5.x86_64
HTH, -dnh
In case you go for uninstall, consider deleting the files created by baloo. They might be several Gb size. On my system they are in ~/.local/share/baloo/file. HTH ~rmš~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 12 May 2014, Radule Šoškic wrote:
13.1/w.KDE 4.13.0:
$ rpm -qa '*baloo*' '*nepomuk*' '*akonadi*' '*strigi*' '*redland*' \ *soprano*' kdebase4-runtime | sort baloo-core-4.13.0-3.2.x86_64 kdebase4-runtime-4.13.0-3.1.x86_64 libakonadi4-4.13.0-3.1.x86_64 libakonadiprotocolinternals1-1.12.1-2.1.x86_64 libbaloofiles4-4.13.0-3.2.x86_64 libbaloowidgets4-4.13.0-2.1.x86_64 libsoprano4-2.9.3-3.2.1.x86_64 libstrigi0-0.7.8-8.49.x86_64 nepomuk-core-4.13.0-3.1.x86_64 soprano-backend-redland-2.9.3-3.2.1.x86_64 [..] In case you go for uninstall, consider deleting the files created by baloo. They might be several Gb size.
On my system they are in ~/.local/share/baloo/file.
Good point. If you allowed baloo to be installed in the first case ;) $ ls -l ~/.local/share/baloo ls: cannot access ~/.local/share/baloo: No such file or directory (nothing under ~/.config nor ~/.kde4 as well ;) Speaking of stuff like that I still have acroread and flash installed, but I have ~/.macromedia and ~/.adobe completely readonly (after I once set the prefs). So no flash-cookies etc. -dnh -- Debian is like Suse with yast turned off, just better. :) -- Goswin Brederlow -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (13)
-
Anton Aylward -
C -
David Haller -
Dirk Gently -
Dylan -
Felix Miata -
John Andersen -
Lars Kruczynski -
Per Jessen -
Radule Šoškić -
Sam M -
Vojtěch Zeisek -
šumski