Re: [Evolution] camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8187 AND other CRITICAL messages






Last evening, I received a "bad" e-mail from a trusted client.  Each
time I clicked on the e-mail, evolution closed.  

It's one of the problems of using a development release.  If you insist
on using a 3.13 version, then the best thing you can do is, as Andre
says, to get stack traces and so on of the crashed Evo so that the
developers can put things right before it is released.

 I deleted the "bad" e-mail, I started evolution from the CLI.
Evolution started but gave the following message:


camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8187


Even though I deleted the"bad" e-mail and emptied Trash, it still get the camel-WARNING.  For example:


john john-Vostro-3500:~$ evolution


(evolution:15595): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error 
-8187


(evolution:15595): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:2462: signal 
'changed::antialiasing' is invalid for instance '0x7ff170762cc0' of type 'WebKitWebSettings'


** (evolution:15595): CRITICAL **: WebKitDOMNode* webkit_dom_node_get_first_child(WebKitDOMNode*): 
assertion 'WEBKIT_DOM_IS_NODE(self)' failed


** (evolution:15595): CRITICAL **: WebKitDOMNode* webkit_dom_node_get_first_child(WebKitDOMNode*): 
assertion 'WEBKIT_DOM_IS_NODE(self)' failed


** (evolution:15595): CRITICAL **: WebKitDOMNode* webkit_dom_node_insert_before(WebKitDOMNode*, 
WebKitDOMNode*, WebKitDOMNode*, GError**): assertion 'WEBKIT_DOM_IS_NODE(self)' failed


** (evolution:15595): CRITICAL **: WebKitDOMNode* webkit_dom_node_get_first_child(WebKitDOMNode*): 
assertion 'WEBKIT_DOM_IS_NODE(self)' failed


** (evolution:15595): CRITICAL **: WebKitDOMNode* webkit_dom_node_insert_before(WebKitDOMNode*, 
WebKitDOMNode*, WebKitDOMNode*, GError**): assertion 'WEBKIT_DOM_IS_NODE(self)' failed


I find it quite strange that you choose to blame the crash when
displaying a message on the Camel WARNING message rather than all the
CRITICAL WebKit messages 

P.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]