Hide Forgot
Description of problem: I have imported some notes from Gnote into Bijiben. When I type the search term "fialkow", I see two notes with matching names in a drop-down menu. However, when I click on one of those notes, the application prints an error message 'No Notes Found'. Version-Release number of selected component (if applicable): bijiben-3.10.1-1.fc20.x86_64 How reproducible: Happens every time Steps to Reproduce: 1. Import notes from Gnote. 2. Type 'fialkow'. 3. Select one of the notes in the drop-down menu. Actual results: The application displays the message 'No Notes Found'. Expected results: The application should display the note with the title that was selected by the user.
3 explanation: - there is no note with fialkow title/content, but your report highly suggest this is not the case - the note indexing specifically during import failed - or, the query has issues with these notes. If you don't have to scroll thousands of items, can you find "manually" the relevant notes and edit it? Some output might be useful here. It might also be useful to lookup for other notes that were imported at the same time. Thanks for this! With a bit of luck there is some fix to backport from current version.
I can confirm that: 1) One of the notes that came up in the search for "fialkow" had a title of "Fialkow New Laptop" 2) I was able to find this note in the list. 3) After editing this note, I was able to select it in the search list and it was found and displayed properly. I had no messages in Bijiben and then I imported all of the messages from Gnote. I find that some of the imported messages can be found from the search results but others cannot be found (without editing them first).
bijiben was updated to 3.10.2-1.fc20.x86_64 on my computer this morning, so I did some testing. This problem seems to persist with the new version. I decided to run bijiben from the terminal command line and see what happens when I do the import. I found messages like the following in the output after attempting to import notes from Gnote. The first of these messages seems to be a normal exception and the rest seem to indicate a successful import. ** (bijiben:4313): WARNING **: Could not import /home/agajania/.local/share/gnote/7b763532-bc2f-46ea-b496-515604fc7e0b.note - Aborting import for template note ** Message: Updating ressource <Messages 11/4/2013> urn:uuid:d40649f9-f139-52e6-d55c-8e6842362d48 ** Message: Updating ressource <rhevm-test install notes - July 2013> urn:uuid:f52a2e9d-246f-13d4-1e56-2eb9effbbdaa ** Message: Updating ressource <Messages - June 29, 2012> urn:uuid:94186b1d-163f-0dd1-f4e1-71ac549d6a48 . . . However, eventually, I started to see many messages like the following. Perhaps the import procedure is not closing files so there are problems if you have too many notes to import. ** (bijiben:4313): WARNING **: dup: Too many open files : query=|||INSERT OR REPLACE { <urn:uuid:e53a4093-7bb0-88d2-198b-93fdc3937266> a nfo:Note , nie:DataObject ; nie:url '/home/agajania/.local/share/bijiben/faaacebe-4cc6-4a48-8c22-446f8049c775.note' ; nie:contentLastModified '2009-08-20T21:42:27Z' ; nie:contentCreated '1970-01-01T00:00:00Z' ; nie:title 'New Note 127' ; nie:plainTextContent 'New Note 127 1.5 1.5 .25 ' ; nie:dataSource 'local:local' ;nie:generator 'Bijiben' . }|||
Thanks for this report. I need to check, but the issue might be : all notes creates threads and are imported at the same time (thus, a queue is needed).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.