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 476717 - crash in Evolution: creating rule
crash in Evolution: creating rule
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-13 21:12 UTC by frkdavid2
Modified: 2007-09-13 21:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description frkdavid2 2007-09-13 21:12:12 UTC
What were you doing when the application crashed?
creating rule


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nuvola
Icon Theme: Wasp

Memory status: size: 152502272 vsize: 152502272 resident: 35639296 share: 22433792 rss: 35639296 rss_rlim: 4294967295
CPU usage: start_time: 1189715223 rtime: 4077 utime: 3966 stime: 111 cutime:1091 cstime: 100 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237326112 (LWP 9593)]
[New Thread -1332741216 (LWP 10160)]
[New Thread -1316443232 (LWP 9641)]
[New Thread -1308050528 (LWP 9640)]
[New Thread -1299657824 (LWP 9639)]
[New Thread -1267221600 (LWP 9638)]
[New Thread -1276171360 (LWP 9615)]
[New Thread -1258792032 (LWP 9612)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237326112 (LWP 9593))

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


----------- .xsession-errors ---------------------
(evolution:9593): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb624eb40(0x89a3390)
(evolution:9593): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb624eb40(0x89a3390)
(evolution:9593): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb624eb40(0x89a3390)
DEBUG: Inbox/Spip_Nantes (mbox:/home/frank/.evolution/mail/local#Inbox/Spip_Nantes)
subcell_view 0x858def0 deleted before the a11y object 0x8569ac8
subcell_view 0x858def0 deleted before the a11y object 0x8569b20
subcell_view 0x858def0 deleted before the a11y object 0x8569e20
subcell_view 0x858def0 deleted before the a11y object 0x86a9e68
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Pascal Terjan 2007-09-13 21:49:38 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 ***