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 554751 - crash in Evolution Mail and Calendar: usando las tareas de evo...
crash in Evolution Mail and Calendar: usando las tareas de evo...
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-02 18:09 UTC by marodok
Modified: 2008-10-03 05:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description marodok 2008-10-02 18:09:51 UTC
What were you doing when the application crashed?
usando las tareas de evolution


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

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 100237312 vsize: 100237312 resident: 32702464 share: 20660224 rss: 32702464 rss_rlim: 4294967295
CPU usage: start_time: 1222970608 rtime: 509 utime: 475 stime: 34 cutime:2 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 0xb66bd720 (LWP 6645)]
[New Thread 0xb3e5fb90 (LWP 6731)]
[New Thread 0xb2b8db90 (LWP 6680)]
[New Thread 0xb4e6bb90 (LWP 6674)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb66bd720 (LWP 6645))

  • #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 g_type_value_table_peek
    from /usr/lib/libgobject-2.0.so.0
  • #11 <signal handler called>
  • #12 e_cal_menu_target_new_select
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #13 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #14 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgobject-2.0.so.0
  • #22 ??
  • #23 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (15 sec old) ---------------------
Tasks
(evolution:6481): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed
(evolution:6481): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6645): DEBUG: mailto URL command: evolution %s
** (evolution:6645): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:6645): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed
(evolution:6645): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2008-10-03 05:03:47 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 ***