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 641618 - Evolution calendar does not show birthdays for contacts
Evolution calendar does not show birthdays for contacts
Status: RESOLVED DUPLICATE of bug 636334
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-02-05 17:24 UTC by Thomas Frenzel
Modified: 2011-02-06 01:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas Frenzel 2011-02-05 17:24:01 UTC
Evolution calendar does not show birthdays of my local contacts, regardless of the birthdays/anniversaries calendar source being checked or unchecked. Please note that most of my contacts have birthdays assigned to them and those where shown at some time in the past, but I do not know when exactly the problem appeared. I already tried to create a fresh profile by doing the following before reimporting my contacts from a *.vcf file:

evolution --force-shutdown
rm -rf .gconf/apps/evolution
rm -rf .evolution
rm -rf .config/evolution
rm -rf .local/share/evolution
killall gconfd-2
evolution

Regarding to the bug described above this had no effect. Any suggestions how to debug this? I already missed a birthday because of that :'(

The following messages are shown, when starting evolution from the console, but I have no idea whether they are related to the problem:
$ evolution

(evolution:8873): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `(s)'

(evolution:8873): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed
Comment 1 Akhil Laddha 2011-02-06 01:21:14 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 636334 ***