GNOME Bugzilla – Bug 601430
Crash in html_engine_is_selection_active at htmlselection.c line 355
Last modified: 2013-08-23 18:04:49 UTC
What were you doing when the application crashed? Creating an event from a message Steps to reproduce: - message preview not shown in main view (not sure if this is relevant) - right-click message from list - select 'Create Event' - crash Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 866205696 vsize: 866205696 resident: 88981504 share: 28594176 rss: 88981504 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257869715 rtime: 4579 utime: 4130 stime: 449 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fafcd927910 (LWP 24547)] [New Thread 0x7fafd20da910 (LWP 24403)] [New Thread 0x7fafd18d9910 (LWP 24402)] [New Thread 0x7fafe50c8910 (LWP 23153)] [New Thread 0x7fafd2ade910 (LWP 23152)] [New Thread 0x7fafdb74a910 (LWP 22866)] [New Thread 0x7fafdc353910 (LWP 22865)] [New Thread 0x7fafde7fc910 (LWP 22861)] [New Thread 0x7fafdeffd910 (LWP 22860)] [New Thread 0x7fafdf7fe910 (LWP 22859)] [New Thread 0x7fafdffff910 (LWP 22858)] [New Thread 0x7fafe618c910 (LWP 22854)] [New Thread 0x7fafe698d910 (LWP 22853)] 0x00007faffbb1052d in __libc_waitpid (pid=24548, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 218987
Thread 1 (Thread 0x7fb000baf7f0 (LWP 22848))
Inferior 1 [process 22848] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ----------- .xsession-errors (1259318 sec old) --------------------- (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3002): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
Just tried several more times. 100% reproducible here. Whether or not the message preview is enabled or not makes no difference (just thought it might have been relevant since there were functions in the trace related to the html engine). It crashes with it enabled or disabled In my steps above, I obviously forgot to mention a step -- choosing the destination calendar. In this case I chose the "Personal" calendar "On this computer".
Closing as OBSOLETE since the stack trace is too old to be useful now. Reopen the bug and update the version field if this crash still occurs in Evolution 3.8 or later.