Created attachment 943181 [details] Tracker log Description of problem: Tracker logged loads of my private documents into journal. That includes my notes with sensitive data, my travel tickets and Mastodon concert tickets I would prefer not to share, and books on Christian ethics I won't want anyone to know I'm reading. Version-Release number of selected component (if applicable): tracker How reproducible: No idea. Actual results: Attached (very sensitive stuff ommitted).
Running Fedora 21 TC2+updates, this dumping of tracker crap into the journal is taking place ... for the same documents. Something is broken. I see no reason forthis to be happening.
Could you please send me one of the files that is triggering this? These are caused by a bug in on of tracker's extractors that is being hit by a file on your disk.
Created attachment 964593 [details] output of journactl -b
Created attachment 964594 [details] first pdf file that gets written to the log
Created attachment 964595 [details] another file that got written to the log
I've attached my journal and a couple of the source pdf files, I hope that helps and I haven't inadvertently disclosed something embarrassing in there. NOTE: whatever is causing tracker a problem is not the main issue, the main issue is the giant spew of data into the log.
Created attachment 964680 [details] change g_warning to g_debug
(In reply to zachw from comment #6) > NOTE: whatever is causing tracker a problem is not the main issue, the main > issue is the giant spew of data into the log. Please follow/join the discussion in the upstream bug.
What version of tracker are you using? I have tracker-1.2.4-3.fc21.x86_64 and neither of those two files are causing anything to be written to the logs.
Same as you (1.2.4-3.fc21), also I went from fedora 20 to 21 beta via fedup.
*** Bug 1176675 has been marked as a duplicate of this bug. ***
*** Bug 1176678 has been marked as a duplicate of this bug. ***
*** Bug 1180824 has been marked as a duplicate of this bug. ***
tracker-1.2.5-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/tracker-1.2.5-2.fc21
tracker-1.2.5-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
*** Bug 1212511 has been marked as a duplicate of this bug. ***
Aug 22 13:46:30 philip-pc gnome-session: (tracker-extract:4241): Tracker-WARNING **: Call to gst_discoverer_discover_uri(file:///home/philip/Downloads/q2/Install/Data/baseq2/players/male/claymore_i.pcx) failed: Could not determine type of stream. Aug 22 13:46:30 philip-pc gnome-session: (tracker-extract:4241): Tracker-WARNING **: Call to gst_discoverer_discover_uri(file:///home/philip/Downloads/q2/Install/Data/baseq2/players/male/claymore.pcx) failed: Could not determine type of stream. Aug 22 13:46:30 philip-pc gnome-session: (tracker-extract:4241): Tracker-WARNING **: Call to gst_discoverer_discover_uri(file:///home/philip/Downloads/q2/Install/Data/baseq2/players/male/cipher_i.pcx) failed: Could not determine type of stream. Aug 22 13:46:30 philip-pc gnome-session: (tracker-extract:4241): Tracker-WARNING **: Call to gst_discoverer_discover_uri(file:///home/philip/Downloads/q2/Install/Data/baseq2/players/male/cipher.pcx) failed: Could not determine type of stream. Failing to discover the type of a random game data file: tracker.x86_64 v1.4.1-1.fc22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.