GNOME Bugzilla – Bug 584733
Cannot create new account
Last modified: 2013-09-13 01:05:51 UTC
Just realized that I cannot create a new mail account in evolution master. I guess merge of commit 6d70e07 didn't go well. On the first look, the "current = g_strdup ("imap");" is leaking, as the previous allocation came on the stack. Also, I see couple warnings on evo console during continuation of "preselected" IMAP account creation, like: > Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed though I cannot finish the first page, as the "forward" button isn't available. When closing the druid and opening other account edit dialog, and changing in there the account type I see couple of: > Gtk-CRITICAL **: gtk_entry_set_text: assertion `GTK_IS_ENTRY (entry)' failed Thus something is really wrong now. Srag?
Blocker.
Taken. Lemme look at it right away.
fixed in master.
No, not fixed, I'm sorry. Edit->Preferences->Mail Accounts->Add Email: a@b Forward (preselected IMAP) Server: type anything, Forward still disabled In server, choosing all the text, hit Del, the text is deselected, but still there, not deleted.
New patch pushed. it was a freed-memory referenced issue. Fixed. Thanks to valgrind and Milan.
OK, I tried my simple steps and seems to be fixed. I also noticed one little thing, before you enter anything to the server address the "Forward" button is disabled, when you type something in there, the "Forward" button is enabled, but deleting the server entry content doesn't disable the "Forward" button, thus you are able to create an account with empty server names for both receiving and sending. I do not believe you introduced it, thus I'm closing this as fixed. Just if you can, and you'll recall, please look at this. Thanks in advance.
is http://bugzilla.gnome.org/show_bug.cgi?id=576086 a duplicate of this ?
(In reply to comment #7) > is http://bugzilla.gnome.org/show_bug.cgi?id=576086 a duplicate of this ? Seems to be a different one, as he is able to configure an account, but not finish a wizard fully.
*** Bug 584898 has been marked as a duplicate of this bug. ***