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 545606 - crash in Evolution Mail and Calendar: Entering a due date on a...
crash in Evolution Mail and Calendar: Entering a due date on a...
Status: RESOLVED DUPLICATE of bug 544187
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-07-30 22:36 UTC by paul.freitas
Modified: 2008-07-31 04:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description paul.freitas 2008-07-30 22:36:38 UTC 
What were you doing when the application crashed?
Entering a due date on a task.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 122585088 vsize: 122585088 resident: 41791488 share: 18530304 rss: 41791488 rss_rlim: 4294967295
CPU usage: start_time: 1216937717 rtime: 10132 utime: 9585 stime: 547 cutime:3 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65e5740 (LWP 3414)]
[New Thread 0xb26e5b90 (LWP 13022)]
[New Thread 0xb3cffb90 (LWP 13020)]
[New Thread 0xb52ffb90 (LWP 3681)]
(no debugging symbols found)
0xb7eed424 in __kernel_vsyscall ()

+ Trace 204224

Thread 1 (Thread 0xb65e5740 (LWP 3414))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #10 <signal handler called>
  • #11 e_cal_menu_target_new_select
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #12 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #13 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #19 ??
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
  • #21 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (177730 sec old) ---------------------
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:29888): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-07-31 04:20:25 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.


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