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 360284 - crash in Evolution: Delete spam and try to s...
crash in Evolution: Delete spam and try to s...
Status: RESOLVED DUPLICATE of bug 360237
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-06 22:02 UTC by Markus Ortel
Modified: 2006-10-10 19:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Markus Ortel 2006-10-06 22:02:39 UTC
What were you doing when the application crashed?
Delete spam and try to swith to the trash folder


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 210714624 vsize: 0 resident: 210714624 share: 0 rss: 48152576 rss_rlim: 0
CPU usage: start_time: 1160161122 rtime: 0 utime: 5071 stime: 0 cutime:4939 cstime: 0 timeout: 132 it_real_value: 0 frequency: 1403

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232922960 (LWP 6643)]
[New Thread -1312826464 (LWP 15868)]
[New Thread -1336271968 (LWP 6688)]
[New Thread -1327879264 (LWP 6687)]
[New Thread -1304433760 (LWP 6684)]
[New Thread -1296041056 (LWP 6681)]
[New Thread -1259758688 (LWP 6679)]
[New Thread -1286562912 (LWP 6675)]
[New Thread -1277903968 (LWP 6652)]
[New Thread -1251365984 (LWP 6649)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-10-06 22:45:58 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Markus Ortel 2006-10-09 18:22:02 UTC
Hope that might help:

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 194969600 vsize: 0 resident: 194969600 share: 0 rss: 37916672 rss_rlim: 0
CPU usage: start_time: 1160417005 rtime: 0 utime: 1599 stime: 0 cutime:1559 cstime: 0 timeout: 40 it_real_value: 0 frequency: 1122

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232795984 (LWP 5069)]
[New Thread -1307178080 (LWP 5188)]
[New Thread -1290392672 (LWP 5186)]
[New Thread -1298785376 (LWP 5155)]
[New Thread -1345221728 (LWP 5152)]
[New Thread -1353614432 (LWP 5151)]
[New Thread -1259639904 (LWP 5150)]
[New Thread -1269687392 (LWP 5147)]
[New Thread -1269421152 (LWP 5086)]
[New Thread -1251247200 (LWP 5077)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232795984 (LWP 5069))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 __kernel_vsyscall
  • #6 __lll_mutex_unlock_wake
    from /lib/tls/i686/cmov/libpthread.so.0
  • #7 _L_mutex_unlock_269
    from /lib/tls/i686/cmov/libpthread.so.0
  • #8 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 pthread_mutex_unlock
    from /lib/tls/i686/cmov/libc.so.6
  • #13 pthread_mutex_unlock
    from /lib/tls/i686/cmov/libc.so.6
  • #14 e_thread_put
    at e-msgport.c line 1148
  • #15 ml_regen_timeout
    at message-list.c line 3923
  • #16 emfb_search_search_activated
    at em-folder-browser.c line 1132
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 emit_search_activated
    at e-search-bar.c line 161
  • #23 scopeitem_activated_cb
    at e-search-bar.c line 428
  • #24 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #25 IA__g_closure_invoke
    at gclosure.c line 490
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #28 IA__g_signal_emit
    at gsignal.c line 2243
  • #29 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_menu_shell_append
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 g_type_class_meta_marshal
    at gclosure.c line 567
  • #35 IA__g_closure_invoke
    at gclosure.c line 490
  • #36 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #37 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #38 IA__g_signal_emit
    at gsignal.c line 2243
  • #39 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #43 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #44 g_main_context_iterate
    at gmain.c line 2677
  • #45 IA__g_main_loop_run
    at gmain.c line 2881
  • #46 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #47 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 3 Markus Ortel 2006-10-09 18:32:51 UTC
Oh, my dear! Sorry, duplicate of

360570
360308
359957
359774

:)

Regards,
Markus
Comment 4 Karsten Bräckelmann 2006-10-10 19:45:16 UTC
Actually, I believe this to be a duplicate of bug 360237 and its friends, err... duplicates. ;)  Thanks for the good stacktrace, Markus.


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