GNOME Bugzilla – Bug 684425
Do not pass NULL text to gtk_entry_set_text()
Last modified: 2014-04-11 09:06:09 UTC
Here's what I see when starting evolution without any evolution data in $HOME: [stef@stef-rawhide ~]$ rm -r ./.cache/evolution/ [stef@stef-rawhide ~]$ rm -r ./.config/evolution/ [stef@stef-rawhide ~]$ rm -r ./.gnome2/accels/evolution [stef@stef-rawhide ~]$ evolution (evolution:2462): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (evolution:2462): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (evolution:2462): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed This is with: Name : evolution Arch : x86_64 Version : 3.5.91 Release : 1.fc18
Also present with evolution from git master.
This could be fixed with the trivial patch in bug #58777. I've decided stop trying to constantly work around it and can live with the warnings.
*** This bug has been marked as a duplicate of bug 58777 ***
I'm reopening this, but #58777 had been rejected by gtk+ developers.
*** Bug 727952 has been marked as a duplicate of this bug. ***
Created commit 3bd387b in evo master (3.13.1+) [1] Created commit 616f177 in ews master (3.13.1+) [2] Created commit c25954c in ema master (3.13.1+) [3] Created commit eb61b07 in evo evolution-3-12 (3.12.1+) Created commit 88e9c96 in ews evolution-ews-3-12 (3.12.1+) Created commit ce892b7 in ema evolution-mapi-3-12 (3.12.1+) The stable branch commits (3.12.1+) in ews and ema contain their own copy of added evo functions, just for a simpler backward compatibility. They master versions use evo-provided functions. [1] https://git.gnome.org/browse/evolution/commit/?id=3bd387b [2] https://git.gnome.org/browse/evolution-ews/commit/?id=616f177 [3] https://git.gnome.org/browse/evolution-mapi/commit/?id=c25954c