1 |
On Monday, August 24, 2015 11:31:04 AM Francisco Ares wrote: |
2 |
> 2015-08-24 10:13 GMT-03:00 Francisco Ares <frares@×××××.com>: |
3 |
> |
4 |
> > |
5 |
> > |
6 |
> > 2015-08-24 9:14 GMT-03:00 Francisco Ares <frares@×××××.com>: |
7 |
> > |
8 |
> >> Thanks, Dale, for your point of view. |
9 |
> >> |
10 |
> >> But since I'm not the only user (my wife is forced to use it, too ;-) |
11 |
> >> )and I am the only one that knows how to use a command line session, for |
12 |
> >> instance, I still want to try to make this semantic desktop thing to |
13 |
work. |
14 |
> >> |
15 |
> >> Thanks, again, and |
16 |
> >> Best Regards |
17 |
> >> Francisco |
18 |
> >> |
19 |
> >> 2015-08-21 22:36 GMT-03:00 Dale <rdalek1967@×××××.com>: |
20 |
> >> |
21 |
> >>> Fernando Rodriguez wrote: |
22 |
> >>> > On Friday, August 21, 2015 6:27:36 PM Dale wrote: |
23 |
> >>> >> Francisco Ares wrote: |
24 |
> >>> >>> Hi, |
25 |
> >>> >>> |
26 |
> >>> >>> In fact, I can only suppose there's something related to changing |
27 |
> >>> from |
28 |
> >>> >>> nepomuk to baloo: |
29 |
> >>> >>> |
30 |
> >>> >>> Now, every time I log in, a window pops up asking for root password. |
31 |
> >>> >>> The window title is "PolicyKit - KDE" and pressing the button |
32 |
> >>> >>> "Details", it shows: |
33 |
> >>> >>> |
34 |
> >>> >>> Action: Folder Watch Limit |
35 |
> >>> >>> polkit.subject-pid: 5254 |
36 |
> >>> >>> polkit.caller-pid: 6699 |
37 |
> >>> >>> |
38 |
> >>> >>> Looking for those PIDs: |
39 |
> >>> >>> |
40 |
> >>> >>> ~ $ ps -A | grep 5254 |
41 |
> >>> >>> 5254 ? 00:00:07 baloo_file |
42 |
> >>> >>> |
43 |
> >>> >>> and PID 6699 doesn't show up any more, probably the process has |
44 |
> >>> >>> already ended. |
45 |
> >>> >>> |
46 |
> >>> >>> Did I miss something? How do I set up Baloo? Looking on the net, I |
47 |
> >>> >>> only found how to set up a file ~/.kde4/share/config/nepomukserverrc |
48 |
> >>> >>> (that was nonexistent, which seemed strange), is there something |
49 |
else |
50 |
> >>> >>> regarding the database it might be willing to use? |
51 |
> >>> >>> |
52 |
> >>> >>> Thank you all. |
53 |
> >>> >>> Francisco |
54 |
> >>> >>> |
55 |
> >>> >> |
56 |
> >>> >> Reading your posts, it seems you don't really want this "feature" of |
57 |
> >>> >> KDE. Why not disable the thing? I have this in make.conf: |
58 |
> >>> >> |
59 |
> >>> >> -nepomuk -semantic-desktop |
60 |
> >>> >> |
61 |
> >>> >> So far, that has disabled the whole desktop search thingy, that I |
62 |
also |
63 |
> >>> >> found to be a pest and never needed. |
64 |
> >>> >> |
65 |
> >>> >> Just a thought, in case you wasn't aware. |
66 |
> >>> >> |
67 |
> >>> >> Dale |
68 |
> >>> >> |
69 |
> >>> >> :-) :-) |
70 |
> >>> > Do you use kmail? I disabled nepomuk at one point and I wasn't able to |
71 |
> >>> access |
72 |
> >>> > my contacts on kmail. I think it's the same with baloo. And from what |
73 |
> >>> I've |
74 |
> >>> > read the plan is for more applications to use it so you may miss |
75 |
> >>> important |
76 |
> >>> > features. They recommend just disabling file indexing or adding your |
77 |
> >>> home |
78 |
> >>> > directory to the exclusion list on system settings, But after doing |
79 |
> >>> that I |
80 |
> >>> > still got that popup a few times until I okay'd it. |
81 |
> >>> > |
82 |
> >>> |
83 |
> >>> |
84 |
> >>> I used to use Kmail until all this mess started. I think the last I |
85 |
> >>> used Kmail was back in KDE3. When I saw all this mess coming, I |
86 |
> >>> switched to Seamonkey. Seamonkey does all my email stuff and I'm happy |
87 |
> >>> with it. I do wish the sound notification thingy would work tho. Maybe |
88 |
> >>> I just need to sit down one day and try to figure out why it doesn't |
89 |
> >>> work. Sound works everywhere else. Still, it does what I really need |
90 |
> >>> without to much bloat. |
91 |
> >>> |
92 |
> >>> I installed KDE with the kde-meta. It basically installs everything but |
93 |
> >>> the kitchen sink. To be honest tho, I could likely install it in a |
94 |
> >>> better way that leaves out TONS of stuff I never use. This file indexer |
95 |
> >>> thingy is one of the ones I have never had a need for. If I want to |
96 |
> >>> find some file, locate, find and etc works for those rare occasions. It |
97 |
> >>> is rare since I'm fairly well organized with my stuff. Well, computer |
98 |
> >>> files at least. My closet and shop is a different matter tho. lol |
99 |
> >>> |
100 |
> >>> My point was that this can be disabled IF it is not needed. If it is |
101 |
> >>> needed, then fixing it is the solution. If it is not, disable it and |
102 |
> >>> shove the problem into the trash can. ;-) |
103 |
> >>> |
104 |
> >>> Dale |
105 |
> >>> |
106 |
> >>> :-) :-) |
107 |
> >>> |
108 |
> >>> |
109 |
> >>> |
110 |
> >> |
111 |
> > Thanks to all that have posted. |
112 |
> > |
113 |
> > I tried a "clean start": I've deleted all related (at least all that I |
114 |
> > could find) files used by baloo (just kept some backup copies in a ZIP |
115 |
> > file, just in case). |
116 |
> > |
117 |
> > As expected, all of them are back, and also that popup window, requiring |
118 |
> > root password. |
119 |
> > |
120 |
> > I guess, now, I am (we are) looking on the wrong place, perhaps this is a |
121 |
> > global setting, not a user one. |
122 |
> > |
123 |
> > Going to check this out. |
124 |
> > |
125 |
> > Thanks again, and |
126 |
> > Best Regards |
127 |
> > Francisco |
128 |
> > |
129 |
> |
130 |
> |
131 |
> Found this: |
132 |
> |
133 |
> ~ # cat /etc/dbus-1/system.d/org.kde.baloo.filewatch.conf |
134 |
> <!DOCTYPE busconfig PUBLIC |
135 |
> "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" |
136 |
> "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> |
137 |
> <busconfig> |
138 |
> |
139 |
> <!-- Only user root can own the foo helper --> |
140 |
> <policy user="root"> |
141 |
> <allow own="org.kde.baloo.filewatch"/> |
142 |
> </policy> |
143 |
> |
144 |
> </busconfig> |
145 |
> |
146 |
> |
147 |
> Looks like there might be something related to what I am facing, isn't it? |
148 |
> |
149 |
> Googling the file name, I got this: |
150 |
> |
151 |
> https://bugs.kde.org/show_bug.cgi?id=339465 |
152 |
> |
153 |
https://www.reddit.com/r/kde/comments/2ibdf7/what_is_baloo_file_watch_and_why_does_it_need/ |
154 |
> http://www.linuxquestions.org/questions/slackware-14/kde-4-13-3-%5Balien%5D-annoying-kde-polkit-and-wallet-prompts-4175517244/ |
155 |
> |
156 |
> So, got back to the first and (as it seems) proper solution, but with no |
157 |
> effects, for now. |
158 |
> |
159 |
> Perhaps I'll just wait and see future upgrades on baloo. Meanwhile I will |
160 |
> try to filter more directories not to be indexed, and/or increasing the |
161 |
> limit on "/etc/sysctl.d/97-kde-baloo-filewatch-inotify.conf" by hand. |
162 |
> |
163 |
> Thanks! |
164 |
> Francisco |
165 |
|
166 |
I'm not following this thread closely, but if the problem is that you keep |
167 |
being prompted after updating the file or granting baloo permission to update |
168 |
it. It may be that you don't have the sysctl init script set to run on boot |
169 |
(if you're using openrc). So run: |
170 |
|
171 |
rc-update add sysctl boot |
172 |
|
173 |
-- |
174 |
Fernando Rodriguez |