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 463526 - crash in Tasks: Chaning font sizes
crash in Tasks: Chaning font sizes
Status: RESOLVED DUPLICATE of bug 426496
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-04 22:16 UTC by finnzi
Modified: 2007-08-11 00:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description finnzi 2007-08-04 22:16:10 UTC 
Version: 2.10

What were you doing when the application crashed?
Chaning font sizes


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 172916736 vsize: 172916736 resident: 82014208 share: 40714240 rss: 82014208 rss_rlim: 4294967295
CPU usage: start_time: 1186263958 rtime: 2763 utime: 2312 stime: 451 cutime:2 cstime: 5 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208682784 (LWP 3261)]
[New Thread -1251783792 (LWP 3471)]
[New Thread -1264075888 (LWP 3385)]
[New Thread -1238705264 (LWP 3384)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 152849

Thread 1 (Thread -1208682784 (LWP 3261))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #6 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 ??
    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_refresh_fonts
    from /usr/lib/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib/libgconf-2.so.4
  • #13 gconf_listeners_notify
    from /usr/lib/libgconf-2.so.4
  • #14 ??
    from /usr/lib/libgconf-2.so.4
  • #15 ??
    from /usr/lib/libgconf-2.so.4
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------
Comment 1 Tobias Mueller 2007-08-11 00:10:47 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 ***