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 434524 - crash in Evolution: Deleting messages.
crash in Evolution: Deleting messages.
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-04-30 08:10 UTC by lca
Modified: 2007-05-18 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lca 2007-04-30 08:10:49 UTC
What were you doing when the application crashed?
Deleting messages.


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-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 155873280 vsize: 155873280 resident: 33996800 share: 18886656 rss: 33996800 rss_rlim: 4294967295
CPU usage: start_time: 1177685708 rtime: 1805 utime: 1565 stime: 240 cutime:0 cstime: 0 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 -1237555488 (LWP 4071)]
[New Thread -1328370784 (LWP 4117)]
[New Thread -1311454304 (LWP 4098)]
[New Thread -1282004064 (LWP 4097)]
[New Thread -1263662176 (LWP 4085)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237555488 (LWP 4071))

  • #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 ---------------------
beryl: Couldn't bind redirected window 0x1800121 to texture
beryl: pixmap 0x16000c8 can't be bound to texture
beryl: Couldn't bind redirected window 0x18000f0 to texture
beryl: pixmap 0x1641b97 can't be bound to texture
beryl: Couldn't bind redirected window 0x3a170e3 to texture
beryl: pixmap 0x1600bbb can't be bound to texture
beryl: Couldn't bind redirected window 0x38026c9 to texture
beryl: pixmap 0x1600bbd can't be bound to texture
beryl: Couldn't bind redirected window 0x38026c6 to texture
beryl: pixmap 0x1600b74 can't be bound to texture
beryl: Couldn't bind redirected window 0x3802272 to texture
beryl: pixmap 0x16000cc can't be bound to texture
beryl: Couldn't bind redirected window 0x1800121 to texture
beryl: pixmap 0x16000c8 can't be bound to texture
beryl: Couldn't bind redirected window 0x18000f0 to texture
--------------------------------------------------
Comment 1 palfrey 2007-04-30 13:51:59 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 palfrey 2007-05-18 11:09:35 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 426496 ***