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 487766 - crash in Evolution: I was scrolling down the...
crash in Evolution: I was scrolling down the...
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-10-18 04:28 UTC by michael
Modified: 2007-10-18 23:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description michael 2007-10-18 04:28:30 UTC
What were you doing when the application crashed?
I was scrolling down the list of messages in my inbox using the arrow keys; I opened one message, closed it, and continued scrolling.


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

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Flat-Blue

Memory status: size: 504487936 vsize: 504487936 resident: 47357952 share: 20283392 rss: 47357952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192681485 rtime: 2247 utime: 2167 stime: 80 cutime:2 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ad9bca13860 (LWP 5072)]
[New Thread 0x43046950 (LWP 5139)]
[New Thread 0x42845950 (LWP 5129)]
[New Thread 0x42804950 (LWP 5128)]
[New Thread 0x42003950 (LWP 5126)]
[New Thread 0x41802950 (LWP 5103)]
[New Thread 0x41001950 (LWP 5102)]
[New Thread 0x40800950 (LWP 5101)]
(no debugging symbols found)
0x00002ad9b4a04c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2ad9bca13860 (LWP 5072))

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


----------- .xsession-errors (162 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0

(gnome-terminal:4008): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (602686112) is greater than comparison timestamp (2975426443).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x300001e (Terminal) appears to be one of the offending windows with a timestamp of 602686112.  Working around...

(firestarter:4745): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Firewall started
evolution-shell-Message: Killing old version of evolution-data-server...
--------------------------------------------------
Comment 1 André Klapper 2007-10-18 23:20:12 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 ***