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 659183 - evo 3.1.92: Calendar view does not show any event
evo 3.1.92: Calendar view does not show any event
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-09-15 20:08 UTC by Gert Kulyk
Modified: 2013-09-13 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot showing the issue (117.26 KB, image/png)
2011-09-16 20:32 UTC, Gert Kulyk 		Details

Description Gert Kulyk 2011-09-15 20:08:28 UTC 
Since I did a new git checkout today (evolution up to commit 	6ea72f4fe7cd9ed44660589bf13eb153007cb62e and e-d-s up to commit 	2e576d8cb05dfcc33d10fc23b4c7543b2205506f), the calendar component in Evolution seems to be broken. Neither previous edited events are showing up in calendar view, nor do newly edited ones (Gnome-Shell calendar component is showing the events, so it seems to be evolution specific).

Any hints how to debug this properly are appreciated.
Comment 1 Akhil Laddha 2011-09-16 04:39:52 UTC 
are you sure that e-calendar-factory is running because many times right version of e-calendar-factory doesn't get started. Please try to start manually from $PREFIX/libexec/e-calendar-factory after killing all other e-calendar-factory instances.
Comment 2 Milan Crha 2011-09-16 12:17:02 UTC 
I agree with Akhil, run evolution from console too and see any errors it might print you, on both consoles.
Comment 3 Gert Kulyk 2011-09-16 17:59:39 UTC 
I did so several times, even after rebooting the machine the calender does not show up anything. There are no old e-d-s instances running, the only error that is printed when starting evolution from console and working a bit with evo (which I did before reporting this), is " evolution-mail-CRITICAL **: mail_store_add: assertion `store_table != NULL' failed" which seems unrelated to this issue.
Comment 4 Gert Kulyk 2011-09-16 19:34:18 UTC 
For the record: I did today a clean jhbuild of e-d-s, gtkhtml and evolution, with the same result. The only additional configure switch was "--disable-static" CFLAGS were "-O2 -g". Checked out versions:

e-d-s:   3.1.92 up to commit 9220410d2a133406edfebe11125282f03ca534b0
gtkhtml: 4.1.92 up to commit 9220410d2a133406edfebe11125282f03ca534b0
evo:     3.1.92 up to commit b07e4936ee30e2f568224a8992194c9c94b80122

And before I forget it: I'm on i386.
Comment 5 Gert Kulyk 2011-09-16 19:36:26 UTC 
Sorry, gtkhtml is 4.1.92 up to commit b26fabf56be117e95945872f073678ae01bfe4e6
Comment 6 Gert Kulyk 2011-09-16 20:32:30 UTC 
Created attachment 196773 [details]
Screenshot showing the issue

Here a screenshot showing the issue.
Comment 7 Gert Kulyk 2011-09-16 22:48:14 UTC 
Sorry for the mess, I've found out that on a fresh account this does not happen. Seems like something broke my evolution-configuration.