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 504821 - crash in Evolution: envoyer/recevoir
crash in Evolution: envoyer/recevoir
Status: RESOLVED DUPLICATE of bug 426496
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-21 09:21 UTC by airalis
Modified: 2007-12-21 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description airalis 2007-12-21 09:21:38 UTC
What were you doing when the application crashed?
envoyer/recevoir


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Orange
Icon Theme: gnome

Memory status: size: 97337344 vsize: 97337344 resident: 26152960 share: 17801216 rss: 26152960 rss_rlim: 4294967295
CPU usage: start_time: 1198228847 rtime: 214 utime: 198 stime: 16 cutime:500 cstime: 40 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237219616 (LWP 6898)]
[New Thread -1298142304 (LWP 6985)]
[New Thread -1279673440 (LWP 6948)]
[New Thread -1271280736 (LWP 6947)]
[New Thread -1252852832 (LWP 6917)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237219616 (LWP 6898))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtkhtml-3.14.so.19
  • #6 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 html_object_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #8 html_engine_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #9 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (26 sec old) ---------------------
in emp_apps_open_in
in emp_apps_open_in
index:0
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6742): DEBUG: mailto URL command: evolution %s
** (evolution:6742): DEBUG: mailto URL program: evolution
(evolution:6742): e-data-server-DEBUG: Loading categories from "/home/netb/.evolution/categories.xml"
(evolution:6742): e-data-server-DEBUG: Loaded 29 categories
(evolution:6742): libebook-WARNING **: invalid escape, passing it through
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6898): DEBUG: mailto URL command: evolution %s
** (evolution:6898): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 André Klapper 2007-12-21 10:44:11 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 426496 ***