Bug 1037892 - [ALL LANG] Run evolution first time from terminal produced Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed
Summary: [ALL LANG] Run evolution first time from terminal produced Gtk-CRITICAL **: g...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-04 02:27 UTC by Lijun Li
Modified: 2013-12-12 15:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-12 15:49:59 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 58777 0 None None None Never

Description Lijun Li 2013-12-04 02:27:46 UTC
Description of problem:
Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed

Version-Release number of selected component (if applicable):
evolution-3.8.5-9.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install latest rhel7 build.
2. Run evolution from terminal.

Actual results:
# evolution 

(evolution:7152): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed

(evolution:7152): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed

(evolution:7152): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed


Expected results:
Should have no such messages.

Additional info:

Comment 2 Matthew Barnes 2013-12-12 15:31:48 UTC
This is essentially:
https://bugzilla.gnome.org/show_bug.cgi?id=58777

Which GTK+ upstream refused for reasons I still don't understand.

The warning is harmless, so I've decided not to work around the flaw for every GtkEntry instance in Evolution.

Comment 3 RHEL Program Management 2013-12-12 15:49:59 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.