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 727952 - gtk_entry_set_text: assertion 'text != NULL' failed
gtk_entry_set_text: assertion 'text != NULL' failed
Status: RESOLVED DUPLICATE of bug 684425
Product: evolution
Classification: Applications
Component: general
3.12.x (obsolete)
Other OpenBSD
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-04-10 10:29 UTC by Antoine Jacoutot
Modified: 2014-04-11 08:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
"OK" button is not active (51.09 KB, image/png)
2014-04-10 10:29 UTC, Antoine Jacoutot
Details

Description Antoine Jacoutot 2014-04-10 10:29:41 UTC
Created attachment 273972 [details]
"OK" button is not active

Hi.

When running evolution 3.12 I see a lot of:
(evolution:24280): Gtk-CRITICAL **: gtk_entry_set_text: assertion 'text != NULL' failed
(evolution:24280): Gtk-CRITICAL **: gtk_entry_set_text: assertion 'text != NULL' failed
(evolution:24280): Gtk-CRITICAL **: gtk_entry_set_text: assertion 'text != NULL' failed
<...>
on the console.

As a result, the interface is kinda of borked in the sense that some buttons are greyed out and some settings cannot be modified.

Screenshot showing the issue is attached.
Comment 1 Milan Crha 2014-04-11 05:43:50 UTC
(In reply to comment #0)
> As a result, the interface is kinda of borked in the sense that some buttons
> are greyed out and some settings cannot be modified.

Thanks for a bug report. The runtime critical warnings are not a reason for the OK button being disabled, it's a bug #58777. I just realized they rejected it.
It's bad.

Anyway, the OK button is most likely disabled because you've missing some information being set either on the Receiving Email or on the Sending Email pages, like user name or server address, or such. Could you verify that, please?
Comment 2 Antoine Jacoutot 2014-04-11 06:05:04 UTC
Hi Milan.

> Thanks for a bug report. The runtime critical warnings are not a reason for the
> OK button being disabled, it's a bug #58777. I just realized they rejected it.
> It's bad.

Oh... quite old :-)
 
> Anyway, the OK button is most likely disabled because you've missing some
> information being set either on the Receiving Email or on the Sending Email
> pages, like user name or server address, or such. Could you verify that,
> please?

Indeed you're right... the username field was missing in the smtp page. Not why the account setting wizards did...
But there are still some glitches, for e.g. in the "Sending Email" tab, I cannot change the Server Type (it is smtp now and wanted to move it to sendmail).

Also when setting a "Real folder for trash" and saving the preferences I am getting the following error:
No such interface 'org.gnome.evolution.dataserver.Source.Writable' on object at path /org/gnome/evolution/dataserver/SourceManager/Source_7

These are probably not related to the initial issue -- so let me know if you prefer I open a new ticket.
Comment 3 Milan Crha 2014-04-11 08:48:56 UTC
(In reply to comment #2)
> Indeed you're right... the username field was missing in the smtp page. Not why
> the account setting wizards did...

How did you configure the account, was it directly in evolution, or through GNOME Online Accounts? I guess it's the later, also due to the "No such interface" error message.

> But there are still some glitches, for e.g. in the "Sending Email" tab, I
> cannot change the Server Type (it is smtp now and wanted to move it to
> sendmail).

It's done intentionally, Matthew dropped support for changing Sending/Receiving types once you have it saved, which means you can decide when you are creating the new account, but not after it. It was doe to be consistent with calendar/book/... source editors, though it probably was not a good decision. There might also be some older bug reports with it, thus they can be possibly reopened and the decision rethought.

I'm closing this as a duplicate of bug #684425, which I just reopened. I agree with continuing in other bug reports with the sub-issues mentioned above.

*** This bug has been marked as a duplicate of bug 684425 ***
Comment 4 Antoine Jacoutot 2014-04-11 08:53:58 UTC
> How did you configure the account, was it directly in evolution, or through

It was directly from evolution (empty profile) with the first time wizard.

> It's done intentionally, Matthew dropped support for changing Sending/Receiving
> types once you have it saved, which means you can decide when you are creating
> the new account, but not after it. It was doe to be consistent with
> calendar/book/... source editors, though it probably was not a good decision.
> There might also be some older bug reports with it, thus they can be possibly
> reopened and the decision rethought.

Ah alright. OK that's good then :-)

> I'm closing this as a duplicate of bug #684425, which I just reopened. I agree
> with continuing in other bug reports with the sub-issues mentioned above.

Thanks Milan.