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 721024 - Clicking a note produces critical messages on console
Clicking a note produces critical messages on console
Status: RESOLVED OBSOLETE
Product: bijiben
Classification: Applications
Component: general
3.11.x
Other Linux
: Normal major
: ---
Assigned To: Bijiben maintainer(s)
Bijiben maintainer(s)
Depends on: 699249
Blocks:
 
 
Reported: 2013-12-24 21:56 UTC by Baptiste Mille-Mathias
Modified: 2018-01-07 10:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Baptiste Mille-Mathias 2013-12-24 21:56:14 UTC 
I have a new note opened, and when I click on it, each time I have this kind of critical messages

** (bijiben:32708): CRITICAL **: WebKitDOMNode* webkit_dom_range_get_start_container(WebKitDOMRange*, GError**): assertion 'WEBKIT_DOM_IS_RANGE(self)' failed

** (bijiben:32708): CRITICAL **: gushort webkit_dom_node_get_node_type(WebKitDOMNode*): assertion 'WEBKIT_DOM_IS_NODE(self)' failed

** (bijiben:32708): CRITICAL **: WebKitDOMNode* webkit_dom_range_get_end_container(WebKitDOMRange*, GError**): assertion 'WEBKIT_DOM_IS_RANGE(self)' failed

** (bijiben:32708): CRITICAL **: gushort webkit_dom_node_get_node_type(WebKitDOMNode*): assertion 'WEBKIT_DOM_IS_NODE(self)' failed

** (bijiben:32708): CRITICAL **: WebKitDOMDocumentFragment* webkit_dom_range_clone_contents(WebKitDOMRange*, GError**): assertion 'WEBKIT_DOM_IS_RANGE(self)' failed

build from git today
Comment 1 Pierre-Yves Luyten 2014-03-01 22:41:10 UTC 
And focus fails. But i'm not sure solving 699249 would remove warnings.
Comment 2 Mohammed Sadiq 2018-01-07 10:14:39 UTC 
This seems no longer found. Please re-open in case the issue persists.

Thanks