After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 767567 - Crashes when importing from Tomboy
Crashes when importing from Tomboy
Status: RESOLVED DUPLICATE of bug 783471
Product: bijiben
Classification: Applications
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Bijiben maintainer(s)
Bijiben maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-06-12 17:28 UTC by Sam Morris
Modified: 2018-02-06 23:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Morris 2016-06-12 17:28:45 UTC 
The first time I ran bijiben it crashed with the following backtrace. This is repeatable if I try to import notes from Tomboy on subsequent runs, though I see other crashes in about 3 out of 4 attempts to get it to show the main window. I assume these crashes are unrelated and I'll report them separately.

Core was generated by `bijiben'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 236329

  • #0 biji_manager_note_new_full
    at biji-manager.c line 880
  • #0 biji_manager_note_new_full
    at biji-manager.c line 880
  • #1 instanciate_note
    at provider/biji-import-provider.c line 117
  • #2 go_through_notes_cb
    at provider/biji-import-provider.c line 168
  • #3 ??
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #4 ??
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #5 ??
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #6 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #7 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #8 g_main_context_iteration
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #9 g_application_run
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #10 main
    at bjb-main.c line 37 






Comment 1


Isaque Galdino





          2018-02-06 23:20:11 UTC
        




*** This bug has been marked as a duplicate of bug 783471 ***