https://bugs.kde.org/show_bug.cgi?id=405247
skierpage <skierp...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INTENTIONAL |---
Ever confirmed|0 |1
--- Comment #4 from skierpage <skierp...@gmail.com> ---
(In reply to Nate Graham from comment #3)
> The problem with writing the file it's currently indexing to some log
> somewhere is that this would be a huge privacy violation and we'd be storing
> a lot of potentially sensitive and personally-identifiable information in
> that log file.
1) That seems more an issue for user permissions and logging/journalctl. User
log files including Baloo logs should only be readable by other users with
admin rights. journalctl output already contains warnings that expose paths
like 'baloo_file[1540]: File moved to path which now no longer exists -
"/home/spage/OMG/my/secrets"'
FWIW in Fedora 29 I tried to view journal files as an unprivileged user (`sudo
-u openvpn journalctl`), and got
Hint: You are currently not seeing messages from other users and the
system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
2) If logging failing files is really a privacy issue, then it could be under
the control of a BALOO_LOG_FAILING_PATHS environment variable.
> `balooctl monitor` already does show you which file it's working on; is
> there a reason why that's not sufficient?
I had problems getting this to work. When I boot Linux, baloo starts reindexing
on startup, reaches a problem file, and crashes. If I'm lucky my desktop is up
and I get a DrKonqi crash notice, but nothing tells me what file had the
problem. Also `balooctl monitor` reports the file indexing but not the crash. I
filed this bug because it was hard for me to figure out what was crashing baloo
indexing in bug 405017. The only reason I was able to identify the file is I
had "only" added 50 new pictures and I guessed that one of my PANO files might
have caused the problem.
We all want Baloo to be more reliable, and making it easy to find out what file
causes it problems will surely help. Cheers, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
