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 474715 - crash in Evolution Mail: scrolling through imap f...
crash in Evolution Mail: scrolling through imap f...
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-09-07 23:46 UTC by filip.sneppe
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description filip.sneppe 2007-09-07 23:46:54 UTC 
What were you doing when the application crashed?
scrolling through imap folder


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 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: 563331072 vsize: 563331072 resident: 354304000 share: 15925248 rss: 354304000 rss_rlim: 4294967295
CPU usage: start_time: 1189154035 rtime: 58410 utime: 55096 stime: 3314 cutime:4 cstime: 31 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232966992 (LWP 3375)]
[New Thread -1264604272 (LWP 3494)]
[New Thread -1308623984 (LWP 3466)]
[New Thread -1283794032 (LWP 3443)]
[New Thread -1298138224 (LWP 3437)]
[New Thread -1285555312 (LWP 3436)]
[New Thread -1273033840 (LWP 3434)]
[New Thread -1247818864 (LWP 3431)]
[New Thread -1238701168 (LWP 3427)]
0xb7f747f2 in ?? () from /lib/ld-linux.so.2

+ Trace 161218

Thread 1 (Thread -1232966992 (LWP 3375))

  • #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 (33512336 sec old) ---------------------
libadplug-2.0.so.0: cannot open shared object file: No such file or directory
Message: device: default
Message: alsa mixer timed out
Message: alsa mixer timed out
Message: alsa mixer timed out
Corrupt JPEG data: 25 extraneous bytes before marker 0xd9
Message: alsa mixer timed out
Message: alsa mixer timed out
Message: alsa mixer timed out
read(): Resource temporarily unavailable
(eog:6736): Eog-CRITICAL **: add_directory: assertion `info->type == GNOME_VFS_FILE_TYPE_DIRECTORY' failed
select(): Interrupted system call
select(): Interrupted system call
X connection to :0.0 broken (explicit kill or server shutdown).
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-09 17:36:45 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 450050 ***