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 455807 - crash in Evolution: i compose e-main for sen...
crash in Evolution: i compose e-main for sen...
Status: RESOLVED DUPLICATE of bug 450050
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-07-11 06:59 UTC by ccusche
Modified: 2007-07-11 12:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ccusche 2007-07-11 06:59:30 UTC
What were you doing when the application crashed?
i compose e-main for send


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-486 #1 Mon Jun 25 20:09:51 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 110710784 vsize: 110710784 resident: 34832384 share: 20402176 rss: 34832384 rss_rlim: 4294967295
CPU usage: start_time: 1184137375 rtime: 577 utime: 548 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232525632 (LWP 12199)]
[New Thread -1285440624 (LWP 12218)]
[New Thread -1284506736 (LWP 12214)]
[New Thread -1274934384 (LWP 12213)]
[New Thread -1266541680 (LWP 12212)]
[New Thread -1257731184 (LWP 12211)]
[New Thread -1248420976 (LWP 12205)]
[New Thread -1239831664 (LWP 12203)]
0xb7fad7f2 in ?? () from /lib/ld-linux.so.2

Thread 1 (Thread -1232525632 (LWP 12199))

  • #0 ??
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 427
  • #4 <signal handler called>
  • #5 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #6 html_cluev_type_init
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 html_cluev_type_init
    from /usr/lib/libgtkhtml-3.14.so.19
  • #8 html_object_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #9 html_engine_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 html_engine_redraw_selection
    from /usr/lib/libgtkhtml-3.14.so.19
  • #11 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 611
  • #0 ??
    from /lib/ld-linux.so.2


----------- .xsession-errors (5683 sec old) ---------------------
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
(/usr/lib/beagle/BeagleDaemon.exe:5391): libebook-WARNING **: invalid character found in attribute group/name
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-07-11 12:56:22 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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