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 576086 - "forward" button does not work in setup assistant
"forward" button does not work in setup assistant
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[timezone]
Depends on:
Blocks:
 
 
Reported: 2009-03-20 14:32 UTC by webograph
Modified: 2009-08-18 07:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description webograph 2009-03-20 14:32:29 UTC
Please describe the problem:
when starting the first time, the setup assistant ignores the "forward" button in the timezone selection.

Steps to reproduce:
1. boot a live image
2. start evolution
3. go through the dialog (i used li@v.e as email address and none, sendmail as mail servers)
4. select or don't select a time zone
5. click forward

Actual results:
nothing happens; error message on stdout/stderr:

(evolution:3369): GnomeUI-CRITICAL **: gnome_druid_set_page: assertion `GNOME_IS_DRUID_PAGE (page)' failed

Expected results:
the druid to finish (or not even to ask my timezone)

Does this happen every time?
yes

Other information:
this was tested using the gnome live image from [1] in virtualbox.

[1] http://downloads.foresightlinux.org/gnome-live/2.26.0/gnome-2.26-x86.hdd.gz
Comment 1 Milan Crha 2009-06-17 08:50:09 UTC
I cannot reproduce this with compiled official sources [1][2] of neither 2.26.0 nor 2.26.2

[1] http://projects.gnome.org/evolution/download.shtml
[2] http://ftp.gnome.org/pub/GNOME/sources/evolution/2.26/
Comment 2 Akhil Laddha 2009-08-18 07:36:31 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.3 or later), please reopen. thanks in advance.