FS#57975 - [gnome-documents] Gnome documents non-functional after 3.28 update

Attached to Project: Arch Linux
Opened by Lucian H (psychi) - Monday, 26 March 2018, 17:35 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 31 January 2019, 18:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Gnome documents will open, but only shows a spinning progress wheel after the 3.28 update so is essentially non-functional. I also get no documents results in Gnome shell. Looking at the logs, there are a load of errors:

JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: libgdprivate-1.0.so: cannot open shared object file: No such file or directory
Failed to load shared library 'libgdprivate-1.0.so' referenced by the typelib: libgdprivate-1.0.so: cannot open shared object file: No such file or directory

I've tried resetting my tracker database but it didn't make any difference.

Searching on google I found this: https://bugs.launchpad.net/ubuntu/+sour … bug/960179 which suggests that the issue here may be a packaging problem - gnome-documents hasn't been properly rebuilt against the latest version of evince?
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 31 January 2019, 18:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.30.1
Comment by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 14:32 GMT
Sounds more like a missing rpath, even though your link is bad so I have no idea what it said.
Comment by Lucian H (psychi) - Thursday, 29 March 2018, 17:03 GMT
Sorry about the link. Correct link is here: https://bugs.launchpad.net/ubuntu/+source/gnome-documents/+bug/960179 . The error message is the same but I'm no expert on this stuff so it might be irrelevant.
Comment by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 17:06 GMT
No, that is a very different error message. Totally unrelated.
Comment by Jan de Groot (JGC) - Saturday, 31 March 2018, 13:26 GMT
Can't reproduce with 3.28.0-1.
Comment by jozef riha (jose1711) - Saturday, 31 March 2018, 22:15 GMT
i am on 3.28.0-1 and also affected. same symptoms and whole load of errors like:

apr 01 00:12:07 myhost gnome-documents[10367]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_create_collection_icon: (null)
Comment by Lucian H (psychi) - Sunday, 01 April 2018, 07:29 GMT
Ok, so I've removed gnome-documents and evince, cleared my pacman cache and reinstalled them. I no longer get the errors about libgdprivate - not sure what was going on there. gnome-documents is still non-functional and both it and gnome shell are generally spewing loads of javascript errors all over the place even with all extensions disabled. 'tracker search' works so it looks like this is probably a JS issue in gnome-documents and/or gnome-shell. I guess I need to raise upstream. Sorry.
Comment by jozef riha (jose1711) - Monday, 02 April 2018, 18:35 GMT
fyi i reported https://bugzilla.gnome.org/show_bug.cgi?id=794866. please consider extending this bug report before raising a new one.
Comment by Stanislav T (stas-t) - Monday, 09 April 2018, 16:14 GMT
I can confirm a bug. Also I have an update: gnome-documents starts well for me from the terminal:

$ killall gnome-documents
$ gnome-documents

But after I exit it with Ctrl+Q then - after a delay while tracker-extract was still doing its job - I'm getting a core dump.

   gnome-documents-coredump.txt (3.1 KiB)
Comment by mattia (nTia89) - Sunday, 15 April 2018, 14:20 GMT
gnome-documents works for me, without any error...
Since it is the first time I use that application, could be a problem related with GNOME cache/.config files from a previous version?
Comment by Lucian H (psychi) - Sunday, 15 April 2018, 18:39 GMT
It's certainly possible that there's some old cruft lying around that's breaking it. There are certainly a *lot* of javascript errors flying around in many different apps/contexts and lots of things not working. I'm guessing that 3.28 wasn't this broken for the developers! That said, I don't see any obvious candidates under ~/.config or ~/.cache that might be responsible. Are there some standard things that I can try deleting to get rid of saved state for GNOME?
Comment by Stanislav T (stas-t) - Sunday, 15 April 2018, 20:09 GMT
Another thing that I've discovered: after indexing finishes - "tracker search --documents A_STRING" returns me results I expect to see while Gnome search returns me no documents for the same string. So I doubt that it's tracker related.

@mattia: Can you confirm that after you close your gnome-documents it doesn't produce a coredump?
Comment by mattia (nTia89) - Monday, 16 April 2018, 23:12 GMT
no, gnome-documents works as expected but in truth I get this segfault when I close it...
dmesg: gnome-documents[29372]: segfault at 8e28 ip 00007fa2fe0527b0 sp 00007fffa65e25f8 error 4 in libmozjs-52.so[7fa2fdcdc000+9e4000]

probably gnome-documents just needs to be rebuild due to js52 update?
Comment by Stanislav T (stas-t) - Tuesday, 17 April 2018, 10:13 GMT
@mattia: I've rebuilt and re-installed gnome-documents - and I see the same behavior:
- when I "killall gnome-documents" and start it as a gnome app - it shows no documents
- when I "killall gnome-documents" and start it from Alt+F2, "gnome-documents", Enter - it shows documents but crashes on exit
Comment by Stanislav T (stas-t) - Friday, 18 May 2018, 13:44 GMT
I discovered that there are two completely different shared objects on my system: /usr/lib/libgd.so from gd package and /usr/lib/gnome-documents/libgd.so from gnome-documents package. Can it be the case that gnome-documents process picks the wrong libgd.so and that causes the problem?
Comment by Christopher Davis (brainblasted) - Thursday, 31 January 2019, 18:09 GMT
This was an upstream issue that I fixed with 3.30.1. Could I request this be closed?

Loading...