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 588637 - Crash on saving recurring event in calendar
Crash on saving recurring event in calendar
Status: RESOLVED DUPLICATE of bug 579779
Product: evolution
Classification: Applications
Component: Calendar
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-07-15 10:55 UTC by Ben
Modified: 2009-07-15 14:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Ben 2009-07-15 10:55:59 UTC
Steps to reproduce:
1. Open an existing appointment in calender
2. Go to recurrence options
3. Set to recur every week forever
4. [close] [save]


Stack trace:
http://projects.gnome.org/evolution/bugs.shtml
'Debugging Evolution's Chrashes (Getting a backtrace)'



[dafoot@fatbeast ~]$ gdb evolution
GNU gdb (GDB) Fedora (6.8.50.20090302-33.fc11)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Missing separate debuginfos, use: debuginfo-install evolution-2.26.2-1.fc11.x86_64
(gdb) run
Starting program: /usr/bin/evolution
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffea596910 (LWP 14587)]
[Thread 0x7fffea596910 (LWP 14587) exited]
(evolution:14580): e-data-server-DEBUG: Loading categories from "/home/dafoot/.evolution/categories.xml"
(evolution:14580): e-data-server-DEBUG: Loaded 32 categories
[New Thread 0x7fffe84a2910 (LWP 14589)]
[New Thread 0x7fffea596910 (LWP 14594)]
[New Thread 0x7fffe3fff910 (LWP 14595)]
[New Thread 0x7fffe35fe910 (LWP 14596)]
[Thread 0x7fffe35fe910 (LWP 14596) exited]
[New Thread 0x7fffe35fe910 (LWP 14604)]
[Thread 0x7fffe35fe910 (LWP 14604) exited]
[New Thread 0x7fffe35fe910 (LWP 14605)]
[New Thread 0x7fffe2bfd910 (LWP 14606)]
[Thread 0x7fffe2bfd910 (LWP 14606) exited]
[New Thread 0x7fffe2bfd910 (LWP 14607)]
[Thread 0x7fffe2bfd910 (LWP 14607) exited]
[Thread 0x7fffe35fe910 (LWP 14605) exited]
[Thread 0x7fffe3fff910 (LWP 14595) exited]
[Thread 0x7fffea596910 (LWP 14594) exited]
[New Thread 0x7fffea596910 (LWP 14608)]
[New Thread 0x7fffe3fff910 (LWP 14610)]
[Thread 0x7fffea596910 (LWP 14608) exited]
[Thread 0x7fffe3fff910 (LWP 14610) exited]
[New Thread 0x7fffe3fff910 (LWP 14614)]
[New Thread 0x7fffea596910 (LWP 14615)]
[Thread 0x7fffe3fff910 (LWP 14614) exited]
[Thread 0x7fffea596910 (LWP 14615) exited]
[New Thread 0x7fffea596910 (LWP 14616)]
[New Thread 0x7fffe3fff910 (LWP 14621)]
[New Thread 0x7fffe35fe910 (LWP 14622)]
[New Thread 0x7fffe2bfd910 (LWP 14623)]
[Thread 0x7fffe3fff910 (LWP 14621) exited]
[Thread 0x7fffe35fe910 (LWP 14622) exited]
[Thread 0x7fffe2bfd910 (LWP 14623) exited]
[New Thread 0x7fffe2bfd910 (LWP 14626)]
[Thread 0x7fffe2bfd910 (LWP 14626) exited]

(evolution:14580): calendar-gui-CRITICAL **: simple_recur_to_comp: assertion `GTK_BIN (priv->special)->child != NULL' failed
[New Thread 0x7fffe2bfd910 (LWP 14628)]

"evolutionDebug.txt" 157L, 7883C



Other information:
Comment 1 palfrey 2009-07-15 14:20:38 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 579779 ***