Bug 1317220 - Unhandled error while saving file on gedit
Unhandled error while saving file on gedit
Product: Fedora
Classification: Fedora
Component: gedit (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-03-12 21:27 EST by BK Sarthak Das
Modified: 2016-12-20 14:25 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 14:25:16 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Final error screen (38.98 KB, image/png)
2016-03-12 21:27 EST, BK Sarthak Das
no flags Details

  None (edit)
Description BK Sarthak Das 2016-03-12 21:27:31 EST
Created attachment 1135773 [details]
Final error screen

Description of problem: When saving a file through gedit, a GDBus.Error is thrown because the focus of the cursor goes from entering the file name to searching, causing to show this error. 

Version-Release number of selected component (if applicable): gedit 3.18.3

How reproducible: Open new file on gedit and save it at some place other than default location. while renaming the file, it'll give error.

Steps to Reproduce:
1. Open gedit GUI
2. Write something on the unsaved file
3. Hit save
4. Once the save dialog appears, do not type anything, rather goto a different location from what it initially opened with. 
5. For example, if Documents was default save location, goto Desktop and start typing, without focusing the cursor the Name textbox.

Actual results: A popup will appear saying "Could not send the search request" GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: unknown tokenizer: TrackerTokenizer

Expected results: The alert box should say "No such files in the location" or maybe the cursor should focus on the filename textbox by default to avoid this.

Additional info:
Comment 1 Fedora End Of Life 2016-11-24 11:03:28 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2016-12-20 14:25:16 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.