Hide Forgot
Earlier today I upgraded my F23 installation to F25. Shortly after resolving the usual nvidia driver issues and finally logging into GNOME, I noticed that bijiben was no longer in my "Favorites" sidebar. I tried starting it and after 6-7 crashes it finally appeared, but none of my 98 notes was there. The notes themselves still existed in .local/share/bijiben, but bijiben just came up empty. I tried searching, got no results and when I returned to the main screen there was this "you have no notes" or something similar message in the main window. I tried logging out and back in, restarting gnome-shell that seems to take care of a few minor glitches and even rebooting, but still no notes (when bijiben decided not to crash that is). Finally, I wrote a new note, returned to the main screen and it was the only one there. I closed bijiben, restarted it, and now all my notes are back (though they don't want to get organized into notebooks, never did). If a user doesn't know about the internals of the program, i.e. where the actual xml notes are stored, they might perceive it as data loss. Also, when the notes are opened, they lack their background color, which makes it quite hard to read when using the dark theme and the fonts are black. I upgraded directly to bijiben-3.21.2-2.fc25.x86_64. Was the removal of the launcher from the sidebar intentional, or was that also a bug? Is there a plugin for gnote that allows importing notes from bijiben? I could not find one. The following appeared in my journal when I finally managed to get bijiben started: Nov 11 04:10:28 <hostname> org.gnome.bijiben.desktop[18667]: [xcb] Unknown request in queue while dequeuing Nov 11 04:10:28 <hostname> org.gnome.bijiben.desktop[18667]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 11 04:10:28 <hostname> org.gnome.bijiben.desktop[18667]: [xcb] Aborting, sorry about that. Nov 11 04:10:28 <hostname> org.gnome.bijiben.desktop[18667]: bijiben: xcb_io.c:165: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed. Nov 11 04:10:28 <hostname> audit[18667]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=18667 comm="bijiben" exe="/usr/bin/bijiben" sig=6 Nov 11 04:10:28 <hostname> abrt-hook-ccpp[20342]: Process 18667 (bijiben) of user 1000 killed by SIGABRT - dumping core Nov 11 04:10:44 <hostname> bijiben[20600]: tracker-backend.vala:211: Falling back to bus backend, the direct backend failed to initialize: Locale mismatch, cannot use direct connection Nov 11 04:10:44 <hostname> bijiben[20600]: Loading account account_1463640553_0 Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed Nov 11 04:10:44 <hostname> bijiben[20600]: biji_item_add_notebook: assertion 'BIJI_IS_ITEM (coll)' failed
Apparently it wasn't a one-off fix. Every time I start bijiben, I have to deal with a blank screen. I need to open and close it a few times or create a new note and move back and forth between grid and list views before I get my notes back.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.