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 480451 - crash in Evolution: Opened Preferences windo...
crash in Evolution: Opened Preferences windo...
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-26 03:50 UTC by bob
Modified: 2007-10-03 00:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bob 2007-09-26 03:50:03 UTC 
What were you doing when the application crashed?
Opened Preferences window


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.18.1 2007-09-13 (SUSE)
BugBuddy Version: 2.18.1

System: Linux 2.6.22.5-23-default #1 SMP 2007/09/18 05:23:45 UTC i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Industrial

Memory status: size: 283561984 vsize: 283561984 resident: 13623296 share: 24821760 rss: 38445056 rss_rlim: 901647360
CPU usage: start_time: 1190778356 rtime: 635 utime: 603 stime: 32 cutime:7 cstime: 2 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 -1235798336 (LWP 7008)]
[New Thread -1486181488 (LWP 7098)]
[New Thread -1374020720 (LWP 7069)]
[New Thread -1365628016 (LWP 7068)]
[New Thread -1355326576 (LWP 7028)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 165534

Thread 1 (Thread -1235798336 (LWP 7008))

  • #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 ---------------------
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution-2.10:7008): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
(evolution-2.10:7008): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 00:35:37 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 ***