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 480272 - crash in Evolution: Changing pref..
crash in Evolution: Changing pref..
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-09-25 15:55 UTC by noway
Modified: 2007-10-03 00:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description noway 2007-09-25 15:55:04 UTC
What were you doing when the application crashed?
Changing pref..


Distribution: SUSE LINUX 10.1 (i586)
Gnome Release: 2.18.1 2007-09-13 (SUSE)
BugBuddy Version: 2.18.1

System: Linux 2.6.16.53-0.8-smp #1 SMP Fri Aug 31 13:07:27 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Industrial

Memory status: size: 340234240 vsize: 340234240 resident: 46149632 share: 21803008 rss: 67952640 rss_rlim: 4294967295
CPU usage: start_time: 1190734275 rtime: 7248 utime: 4318 stime: 2930 cutime:62 cstime: 202 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234221392 (LWP 11200)]
[New Thread -1523725408 (LWP 11495)]
[New Thread -1515197536 (LWP 11494)]
[New Thread -1506804832 (LWP 11493)]
[New Thread -1496499296 (LWP 11310)]
[New Thread -1488106592 (LWP 11309)]
[New Thread -1479713888 (LWP 11306)]
[New Thread -1363571808 (LWP 11288)]
[New Thread -1354785888 (LWP 11287)]
[New Thread -1346393184 (LWP 11280)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1234221392 (LWP 11200))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    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 html_cluev_type_init
    from /usr/lib/libgtkhtml-3.14.so.19
  • #6 html_cluev_type_init
    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 html_engine_redraw_selection
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_check
    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 ---------------------
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Network sensor: can not find eth1
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 00:35:51 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 ***