After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 665210 - gnome-documents - unable to present local docs
gnome-documents - unable to present local docs
Status: RESOLVED INCOMPLETE
Product: tracker
Classification: Core
Component: Extractor
0.12.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-extractor
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2011-11-30 15:16 UTC by Adam
Modified: 2012-09-23 21:15 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Adam 2011-11-30 15:16:44 UTC
The application doesn't show local documents. It shows documents saved in my google account only. Local documents are saved in default Documents folder in home directory. I've tried reinstall the app, check and update my xdg-user-dirs, restart tracker-control but nothings changed.

I found that in file ~/.local/share/tracker/tracker-extract.log after every restart of tracker control (tracker-control -rs) is added more than 3500 lines of warnings and calls. Maybe it's useful for resolving the problem. First 15 lines are these:
-------------------------------------------
30 lis 2011, 15:21:11: Tracker-Warning **: Call to gstdiscovererdiscover_uri() failed: Stream has no data.

30 lis 2011, 15:21:12: Tracker-Warning **: Cannot read from FD... could not extract text

30 lis 2011, 15:21:21: Tracker-Warning **: Could not get pixbuf from GdkPixbufLoader when setting album art

30 lis 2011, 15:21:21: Tracker-Warning **: Could not get pixbuf from GdkPixbufLoader when setting album art

30 lis 2011, 15:21:21: Tracker-Warning **: Could not get pixbuf from GdkPixbufLoader when setting album art .....
-------------------------------------------

and it continues repeating these three lines:
-------------------------------------------
30 lis 2011, 15:21:30: GLib-GIO-Critical **: gfilenewforpath: assertion `path != NULL' failed

30 lis 2011, 15:21:30: GLib-GIO-Critical **: gfileread: assertion `GISFILE (file)' failed

30 lis 2011, 15:21:30: GLib-GObject-Critical **: gobjectunref: assertion `GISOBJECT (object)' failed .....
-------------------------------------------

I've got Fedora 16 updated.
Comment 1 Cosimo Cecchi 2012-03-08 00:07:40 UTC
-> tracker

Hi, sorry it took long to answer.
It looks like Tracker's indexer is getting stuck on a file; do you have any way of identifying that file?
Comment 2 Martyn Russell 2012-03-08 11:59:31 UTC
(In reply to comment #1)
> -> tracker
> 
> Hi, sorry it took long to answer.
> It looks like Tracker's indexer is getting stuck on a file; do you have any way
> of identifying that file?

Hello Cosimo, you have to run with verbosity at a higher level. You can do this if you follow the wiki on how to do that.

You will have to reindex specific files or everything to get these errors to show up again with the file information around them though.

  http://live.gnome.org/Tracker/Documentation/Debugging
Comment 3 Cosimo Cecchi 2012-03-08 20:42:21 UTC
(In reply to comment #2)

> Hello Cosimo, you have to run with verbosity at a higher level. You can do this
> if you follow the wiki on how to do that.
> 
> You will have to reindex specific files or everything to get these errors to
> show up again with the file information around them though.
> 
>   http://live.gnome.org/Tracker/Documentation/Debugging

Perfect, thanks Martyn.

Adam, can you follow these instructions and retrieve the culprit file if this is still an issue?
Comment 4 Tobias Mueller 2012-09-23 21:15:36 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!