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 471153 - crash in Evolution: Lendo email (read email)
crash in Evolution: Lendo email (read email)
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-08-28 14:49 UTC by Andre Dias
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Andre Dias 2007-08-28 14:49:10 UTC 
What were you doing when the application crashed?
Lendo email (read email)


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-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 261046272 vsize: 261046272 resident: 58474496 share: 22585344 rss: 58474496 rss_rlim: 4294967295
CPU usage: start_time: 1188226182 rtime: 20939 utime: 17813 stime: 3126 cutime:71312 cstime: 3561 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 -1236830496 (LWP 13929)]
[New Thread -1458619488 (LWP 14466)]
[New Thread -1361445984 (LWP 13995)]
[New Thread -1352660064 (LWP 13993)]
[New Thread -1344267360 (LWP 13992)]
[New Thread -1335850080 (LWP 13987)]
[New Thread -1327457376 (LWP 13986)]
[New Thread -1299747936 (LWP 13964)]
[New Thread -1281512544 (LWP 13963)]
[New Thread -1289905248 (LWP 13962)]
[New Thread -1273119840 (LWP 13957)]
[New Thread -1264727136 (LWP 13956)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 158546

Thread 1 (Thread -1236830496 (LWP 13929))

  • #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 (108 sec old) ---------------------
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x1e00077
QInputContext: cannot create input context for non-toplevel widgets
QInputContext: cannot create input context for non-toplevel widgets
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x3a2302a
(evolution:13929): gtkhtml-WARNING **: Arquivo ou diretório não encontrado
(evolution:13929): gtkhtml-WARNING **: Arquivo ou diretório não encontrado
(evolution:13929): gtkhtml-WARNING **: Arquivo ou diretório não encontrado
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-09 18:01:03 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 ***