2015-08-24 15:57 GMT-03:00 Fernando Rodriguez < frodriguez.develo...@outlook.com>:
> On Monday, August 24, 2015 11:31:04 AM Francisco Ares wrote: > > 2015-08-24 10:13 GMT-03:00 Francisco Ares <fra...@gmail.com>: > > > > > > > > > > > 2015-08-24 9:14 GMT-03:00 Francisco Ares <fra...@gmail.com>: > > > > > >> Thanks, Dale, for your point of view. > > >> > > >> But since I'm not the only user (my wife is forced to use it, too ;-) > > >> )and I am the only one that knows how to use a command line session, > for > > >> instance, I still want to try to make this semantic desktop thing to > work. > > >> > > >> Thanks, again, and > > >> Best Regards > > >> Francisco > > >> > > >> 2015-08-21 22:36 GMT-03:00 Dale <rdalek1...@gmail.com>: > > >> > > >>> Fernando Rodriguez wrote: > > >>> > On Friday, August 21, 2015 6:27:36 PM Dale wrote: > > >>> >> Francisco Ares wrote: > > >>> >>> Hi, > > >>> >>> > > >>> >>> In fact, I can only suppose there's something related to changing > > >>> from > > >>> >>> nepomuk to baloo: > > >>> >>> > > >>> >>> Now, every time I log in, a window pops up asking for root > password. > > >>> >>> The window title is "PolicyKit - KDE" and pressing the button > > >>> >>> "Details", it shows: > > >>> >>> > > >>> >>> Action: Folder Watch Limit > > >>> >>> polkit.subject-pid: 5254 > > >>> >>> polkit.caller-pid: 6699 > > >>> >>> > > >>> >>> Looking for those PIDs: > > >>> >>> > > >>> >>> ~ $ ps -A | grep 5254 > > >>> >>> 5254 ? 00:00:07 baloo_file > > >>> >>> > > >>> >>> and PID 6699 doesn't show up any more, probably the process has > > >>> >>> already ended. > > >>> >>> > > >>> >>> Did I miss something? How do I set up Baloo? Looking on the net, > I > > >>> >>> only found how to set up a file > ~/.kde4/share/config/nepomukserverrc > > >>> >>> (that was nonexistent, which seemed strange), is there something > else > > >>> >>> regarding the database it might be willing to use? > > >>> >>> > > >>> >>> Thank you all. > > >>> >>> Francisco > > >>> >>> > > >>> >> > > >>> >> Reading your posts, it seems you don't really want this "feature" > of > > >>> >> KDE. Why not disable the thing? I have this in make.conf: > > >>> >> > > >>> >> -nepomuk -semantic-desktop > > >>> >> > > >>> >> So far, that has disabled the whole desktop search thingy, that I > also > > >>> >> found to be a pest and never needed. > > >>> >> > > >>> >> Just a thought, in case you wasn't aware. > > >>> >> > > >>> >> Dale > > >>> >> > > >>> >> :-) :-) > > >>> > Do you use kmail? I disabled nepomuk at one point and I wasn't > able to > > >>> access > > >>> > my contacts on kmail. I think it's the same with baloo. And from > what > > >>> I've > > >>> > read the plan is for more applications to use it so you may miss > > >>> important > > >>> > features. They recommend just disabling file indexing or adding > your > > >>> home > > >>> > directory to the exclusion list on system settings, But after doing > > >>> that I > > >>> > still got that popup a few times until I okay'd it. > > >>> > > > >>> > > >>> > > >>> I used to use Kmail until all this mess started. I think the last I > > >>> used Kmail was back in KDE3. When I saw all this mess coming, I > > >>> switched to Seamonkey. Seamonkey does all my email stuff and I'm > happy > > >>> with it. I do wish the sound notification thingy would work tho. > Maybe > > >>> I just need to sit down one day and try to figure out why it doesn't > > >>> work. Sound works everywhere else. Still, it does what I really > need > > >>> without to much bloat. > > >>> > > >>> I installed KDE with the kde-meta. It basically installs everything > but > > >>> the kitchen sink. To be honest tho, I could likely install it in a > > >>> better way that leaves out TONS of stuff I never use. This file > indexer > > >>> thingy is one of the ones I have never had a need for. If I want to > > >>> find some file, locate, find and etc works for those rare > occasions. It > > >>> is rare since I'm fairly well organized with my stuff. Well, > computer > > >>> files at least. My closet and shop is a different matter tho. lol > > >>> > > >>> My point was that this can be disabled IF it is not needed. If it is > > >>> needed, then fixing it is the solution. If it is not, disable it and > > >>> shove the problem into the trash can. ;-) > > >>> > > >>> Dale > > >>> > > >>> :-) :-) > > >>> > > >>> > > >>> > > >> > > > Thanks to all that have posted. > > > > > > I tried a "clean start": I've deleted all related (at least all that I > > > could find) files used by baloo (just kept some backup copies in a ZIP > > > file, just in case). > > > > > > As expected, all of them are back, and also that popup window, > requiring > > > root password. > > > > > > I guess, now, I am (we are) looking on the wrong place, perhaps this > is a > > > global setting, not a user one. > > > > > > Going to check this out. > > > > > > Thanks again, and > > > Best Regards > > > Francisco > > > > > > > > > Found this: > > > > ~ # cat /etc/dbus-1/system.d/org.kde.baloo.filewatch.conf > > <!DOCTYPE busconfig PUBLIC > > "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" > > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> > > <busconfig> > > > > <!-- Only user root can own the foo helper --> > > <policy user="root"> > > <allow own="org.kde.baloo.filewatch"/> > > </policy> > > > > </busconfig> > > > > > > Looks like there might be something related to what I am facing, isn't > it? > > > > Googling the file name, I got this: > > > > https://bugs.kde.org/show_bug.cgi?id=339465 > > > > https://www.reddit.com/r/kde/comments/2ibdf7/what_is_baloo_file_watch_and_why_does_it_need/ > > > http://www.linuxquestions.org/questions/slackware-14/kde-4-13-3-%5Balien%5D-annoying-kde-polkit-and-wallet-prompts-4175517244/ > > > > So, got back to the first and (as it seems) proper solution, but with no > > effects, for now. > > > > Perhaps I'll just wait and see future upgrades on baloo. Meanwhile I > will > > try to filter more directories not to be indexed, and/or increasing the > > limit on "/etc/sysctl.d/97-kde-baloo-filewatch-inotify.conf" by hand. > > > > Thanks! > > Francisco > > I'm not following this thread closely, but if the problem is that you keep > being prompted after updating the file or granting baloo permission to > update > it. It may be that you don't have the sysctl init script set to run on boot > (if you're using openrc). So run: > > rc-update add sysctl boot > > -- > Fernando Rodriguez > > Hi, Fernando. Thanks for your advice, but this is not the case. The sysctl init script is already in "boot" level. But I've solved this issue by doubling the value on this file: ~ # cat /etc/sysctl.d/97-kde-baloo-filewatch-inotify.conf fs.inotify.max_user_watches = 1048575 Now there's just the feeling that whatever way the developers found to automatically set this value is not correctly detecting the needs of what it should be for each situation. Probably I'm keeping buffers unoccupied, some day I'll try to reduce this value... perhaps ;-) Many thanks for all who has taken the time to bother with my issue! Best regards, Francisco
