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 566901 - crash in Evolution Mail: Scrolling the calendar!
crash in Evolution Mail: Scrolling the calendar!
Status: RESOLVED DUPLICATE of bug 333224
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: 2009-01-07 14:14 UTC by dagi_x5
Modified: 2009-01-07 15:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description dagi_x5 2009-01-07 14:14:50 UTC 
What were you doing when the application crashed?
Scrolling the calendar!


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Mon Dec 15 17:25:36 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAquaIsh
Icon Theme: Kamel

Memory status: size: 523104256 vsize: 523104256 resident: 37949440 share: 21852160 rss: 37949440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231337455 rtime: 1073 utime: 915 stime: 158 cutime:6 cstime: 15 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 0x7f0c3a6f4700 (LWP 4055)]
[New Thread 0x44434950 (LWP 4158)]
[New Thread 0x41284950 (LWP 4127)]
[New Thread 0x41243950 (LWP 4088)]
(no debugging symbols found)
0x00007f0c35fd15ef in waitpid () from /lib/libpthread.so.0

+ Trace 211356

Thread 1 (Thread 0x7f0c3a6f4700 (LWP 4055))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 e_calendar_view_get_tooltips
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 ??
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (201 sec old) ---------------------
(nautilus:3421): Gtk-CRITICAL **: gtk_action_get_name: assertion `GTK_IS_ACTION (action)' failed
(nautilus:3421): Gtk-CRITICAL **: gtk_action_get_name: assertion `GTK_IS_ACTION (action)' failed
(nautilus:3421): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `name != NULL || type == GTK_UI_MANAGER_SEPARATOR' failed
(nautilus:3421): Gtk-CRITICAL **: gtk_action_get_name: assertion `GTK_IS_ACTION (action)' failed
(nautilus:3421): Gtk-CRITICAL **: gtk_action_get_name: assertion `GTK_IS_ACTION (action)' failed
(nautilus:3421): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `name != NULL || type == GTK_UI_MANAGER_SEPARATOR' failed
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4055): DEBUG: mailto URL command: evolution %s
** (evolution:4055): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 palfrey 2009-01-07 15:22:56 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 333224 ***