RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1610873 - JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Summary: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip...
Keywords:
Status: CLOSED DUPLICATE of bug 1690935
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-documents
Version: 7.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Debarshi Ray
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-01 14:27 UTC by Martin Krajnak
Modified: 2019-04-10 09:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-10 09:22:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-documents/issues/12 0 None None None 2019-01-18 17:15:21 UTC

Description Martin Krajnak 2018-08-01 14:27:44 UTC 
Description of problem:
There are several errors in journalctl which I believe are comming from gnome-documents search provider

Version-Release number of selected component (if applicable):
gnome-documents-3.28.1-1.el7

How reproducible:
always

Steps to Reproduce:
1.Open terminal and execute journalctl -f
2.Search in gnome-shell for "gnome-documents"

Actual results:
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com dbus[769]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-shell[14711]: Wrong number of result metas returned by search provider org.gnome.Documents.desktop: expected 2 but got 0
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-shell[14711]: Wrong number of result metas returned by search provider org.gnome.Documents.desktop: expected 2 but got 0
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:14 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-documents[3210]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate gd_filename_strip_extension: (null)
Aug 01 10:20:39 hp-moonshot-03-c10.lab.eng.rdu.redhat.com dbus[769]: [system] Failed to activate service 'org.bluez': timed out
Aug 01 10:20:39 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-shell[14711]: Received error from DBus search provider org.gnome.Documents.desktop during GetResultMetas: Gio.IOErrorEnum: Timeout was reached
Aug 01 10:20:39 hp-moonshot-03-c10.lab.eng.rdu.redhat.com gnome-shell[14711]: Wrong number of result metas returned by search provider org.gnome.Documents.desktop: expected 2 but got 0

Expected results:
there should be no errors

Additional info:
tested on aarch64 and x86_64
Comment 2 Martin Krajnak 2018-08-02 10:28:25 UTC 
By the way these messages are generated periodically so it clearly is something wrong with the search provider.

Aug 02 12:27:13 t470s gnome-shell[11024]: Received error from DBus search provider org.gnome.Documents.desktop during GetResultMetas: Gio.IOErrorEnum: Timeout was reached
Aug 02 12:27:13 t470s gnome-shell[11024]: Wrong number of result metas returned by search provider org.gnome.Documents.desktop: expected 5 but got 0
Comment 3 Oliver Ilian 2018-09-21 10:33:14 UTC 
is there any update on this. I am seeing this now as well on a test machine.
Comment 4 Martin Krajnak 2019-04-09 12:58:36 UTC 
I am getting also a lot of these why searching for documents:

Apr 09 14:56:00 localhost.localdomain gnome-documents[7383]: JS ERROR: TypeError: job.has_results is not a function
                                                             EvinceView<._onSearchJobUpdated@resource:///org/gnome/Documents/js/evinceview.js:527:26
                                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                                             main@resource:///org/gnome/Documents/js/main.js:48:12
                                                             run@resource:///org/gnome/gjs/modules/package.js:225:12
                                                             @/usr/bin/gnome-documents:6:1
Apr 09 14:56:00 localhost.localdomain gnome-documents[7383]: JS ERROR: TypeError: job.has_results is not a function
                                                             EvinceView<._onSearchJobUpdated@resource:///org/gnome/Documents/js/evinceview.js:527:26
                                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                                             main@resource:///org/gnome/Documents/js/main.js:48:12
                                                             run@resource:///org/gnome/gjs/modules/package.js:225:12
                                                             @/usr/bin/gnome-documents:6:1
Apr 09 14:56:00 localhost.localdomain gnome-documents[7383]: JS ERROR: TypeError: job.has_results is not a function
                                                             EvinceView<._onSearchJobUpdated@resource:///org/gnome/Documents/js/evinceview.js:527:26
                                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                                             main@resource:///org/gnome/Documents/js/main.js:48:12
                                                             run@resource:///org/gnome/gjs/modules/package.js:225:12
                                                             @/usr/bin/gnome-documents:6:1

gnome-documents-3.28.2-2.el7.x86_64
gnome-documents-libs-3.28.2-2.el7.x86_64
Comment 5 Debarshi Ray 2019-04-10 09:21:55 UTC 
This is very likely a duplicate of bug 1690935, which is fixed for RHEL 7.7.
Comment 6 Debarshi Ray 2019-04-10 09:22:46 UTC 

*** This bug has been marked as a duplicate of bug 1690935 ***
Note You need to log in before you can comment on or make changes to this bug.