Bug 1398646

Summary: bijiben prints critical messages on exit
Product: [Fedora] Fedora Reporter: Jiri Prajzner <jprajzne>
Component: bijibenAssignee: Pete Walter <walter.pete>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 29CC: py, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:31:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Prajzner 2016-11-25 13:16:16 UTC
Description of problem:
bijiben prints critical messages on exit

Version-Release number of selected component (if applicable):
bijiben --version
GNOME Notes 3.21.2

How reproducible:
always

Steps to Reproduce:
1. launch bijiben
2. quit bijiben
3.

Actual results:
(bijiben:15645): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(bijiben:15645): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:15645): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(bijiben:15645): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:15645): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(bijiben:15645): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

Expected results:
no error messages

Additional info:

Comment 1 Fedora End Of Life 2017-11-16 18:37:56 UTC
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.

Comment 2 Jiri Prajzner 2017-11-20 10:48:09 UTC
Still valid in F27

Comment 3 Ben Cotton 2018-11-27 18:07:58 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 4 Jiri Prajzner 2018-11-28 13:07:15 UTC
still present in f29.
closed with existing note opened:
GLib-CRITICAL **: 14:02:14.377: g_source_set_ready_time: assertion 'source->priv != NULL' failed

closed with non-saved new note:
GLib-GObject-WARNING **: 14:03:05.676: instance with invalid (NULL) class pointer

(bijiben:17457): GLib-GObject-CRITICAL **: 14:03:05.676: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:17457): GLib-GObject-WARNING **: 14:03:05.676: invalid (NULL) pointer instance

(bijiben:17457): GLib-GObject-CRITICAL **: 14:03:05.676: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:17457): GLib-GObject-WARNING **: 14:03:05.676: invalid (NULL) pointer instance

(bijiben:17457): GLib-GObject-CRITICAL **: 14:03:05.676: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:17457): GLib-GObject-WARNING **: 14:03:05.676: invalid (NULL) pointer instance

(bijiben:17457): GLib-GObject-CRITICAL **: 14:03:05.676: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(bijiben:17457): GLib-GObject-WARNING **: 14:03:05.676: invalid unclassed pointer in cast to 'GtkWidget'

(bijiben:17457): Gtk-CRITICAL **: 14:03:05.676: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed

(bijiben:17457): Gtk-WARNING **: 14:03:05.676: Child name 'main-view' not found in GtkStack

(bijiben:17457): GLib-GObject-WARNING **: 14:03:05.676: instance with invalid (NULL) class pointer

(bijiben:17457): GLib-GObject-CRITICAL **: 14:03:05.676: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

** (bijiben:17457): WARNING **: 14:03:05.691: local note delete failed, Error removing file /home/jprajzne/.local/share/bijiben/49c5faf9-d33f-42dd-8ebc-c131cf01646d.note: No such file or directory

(bijiben:17457): GLib-CRITICAL **: 14:03:05.692: g_source_set_ready_time: assertion 'source->priv != NULL' failed

Comment 5 Ben Cotton 2019-10-31 20:24:18 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 6 Jiri Prajzner 2019-11-06 12:31:23 UTC
seems fixed