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 558698 - crash in Evolution Mail and Calendar: Changing the priority of...
crash in Evolution Mail and Calendar: Changing the priority of...
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-10-31 17:02 UTC by Don Pellegrino
Modified: 2008-10-31 20:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Don Pellegrino 2008-10-31 17:02:19 UTC 
What were you doing when the application crashed?
Changing the priority of a task.


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

System: Linux 2.6.26-1-686 #1 SMP Sat Oct 18 16:22:25 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 109748224 vsize: 109748224 resident: 49512448 share: 20099072 rss: 49512448 rss_rlim: 4294967295
CPU usage: start_time: 1225470243 rtime: 1671 utime: 1596 stime: 75 cutime:2 cstime: 4 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 0xb65806d0 (LWP 3586)]
[New Thread 0xb440eb90 (LWP 4158)]
[New Thread 0xb31c7b90 (LWP 3659)]
[New Thread 0xb5c4ab90 (LWP 3612)]
(no debugging symbols found)
0xb7fb2424 in __kernel_vsyscall ()

+ Trace 208979

Thread 1 (Thread 0xb65806d0 (LWP 3586))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #12 ??
  • #13 ??
  • #14 <signal handler called>
  • #15 e_cal_menu_target_new_select
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #16 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #17 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
  • #26 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Open_Tasks
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3805e82 (Octoshape ); these messages lack timestamps and therefore suck.
** Message: Error: This appears to be a text file
gstdecodebin.c(1657): type_found (): /play/decodebin0:
decodebin cannot decode plain text files
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3400021 (Music Play); these messages lack timestamps and therefore suck.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x8b specified for 0x1600867 ().
(rhythmbox:4659): Rhythmbox-CRITICAL **: new_playing_stream_idle_cb: assertion `entry != NULL' failed
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2a00021 (Benjamin B); these messages lack timestamps and therefore suck.
(evolution:3586): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed
(evolution:3586): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-10-31 20:15:37 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 544187 ***