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 337719 - Debian: Crash when writing/reading message
Debian: Crash when writing/reading message
Status: RESOLVED DUPLICATE of bug 336767
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-04-08 15:55 UTC by shoktai
Modified: 2006-04-13 10:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description shoktai 2006-04-08 15:55:27 UTC
Distribution: Debian testing/unstable
Package: Evolution
Severity: enhancement
Version: GNOME2.12.3 unspecified
Gnome-Distributor: Debian
Synopsis: Crash when writing message
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:

Evolutin stops when i am writing messages
Steps to reproduce the crash:
1. Open Evolution
2. Write/read a message
3. Wait for the crash

Expected Results:

Application stops
How often does this happen?
Very often

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230563104 (LWP 16137)]
[New Thread -1285985360 (LWP 16149)]
[New Thread -1285723216 (LWP 16147)]
[New Thread -1276437584 (LWP 16145)]
[New Thread -1268048976 (LWP 16144)]
[New Thread -1259660368 (LWP 16143)]
[New Thread -1248855120 (LWP 16141)]
[New Thread -1238938704 (LWP 16139)]
(no debugging symbols found)
0xb751d221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1230563104 (LWP 16137))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 es_menu_hook_get_type
  • #3 <signal handler called>
  • #4 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #5 g_signal_handlers_destroy
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_interface_list_properties
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #8 gdk_window_end_paint
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gdk_window_clear_area_e
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-04-08 15:55 -------

Comment 1 André Klapper 2006-04-08 19:33:35 UTC
Hi shoktai,
this could be a known Debian issue, due to the glib update. Please see
bug 336767 for more information. A fast workaround is to start Evolution with
this env variable set, until fixed packages are available:

$ G_SLICE=always-malloc evolution

Also, please check that Evo and its friends (evolution, e-d-s,
evolution-plugins, libsoup, gtkhtml, etc.) are the latest version available,
and do have matching version numbers (including the debian package version).

Setting to NEEDINFO.


(thanks to guenther for copy&paste)

Comment 2 shoktai 2006-04-08 20:08:35 UTC
Thanks for the quick answer.
I have added recently to my /etc/environment file

G_SLICE=always-malloc

i will try with 

G_SLICE=always-malloc evolution
Comment 3 André Klapper 2006-04-09 11:33:17 UTC
ok, please update (or close) after trying. thanks in advance :-)
Comment 4 shoktai 2006-04-10 19:03:53 UTC
My /etc/environment file contains 
G_SLICE=always-malloc evolution
but the problem remains the same.

evolution --version
Gnome evolution-2.4 2.4.2.1

When i launch evolution --debug i get 
adding hook target 'source'

(evolution:8948): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution:8948): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed
Comment 5 André Klapper 2006-04-11 11:37:35 UTC
that terminal output is normal. :-)

what versions of evolution-data-server, gtkhtml, libgtkhtml, and evolution-plugins are you using?
Comment 6 Christian Kirbach 2006-04-11 13:20:59 UTC
unique trace
Comment 7 shoktai 2006-04-11 17:08:04 UTC
Sorry for the lack of details but i am not yet into debbuging, just let me know if you need any other infos:
ii  evolution                         2.4.2.1-1                         The groupware suite
ii  evolution-data-server             1.4.2.1-1                         evolution database backend server
ii  evolution-plugins                 2.4.2.1-1                         All bundled plugins for Evolution
ii  gtkhtml                           1.1.10-9                          HTML rendering/editing library - bonobo component binary.
ii  gtkhtml3.8                        3.8.1-1                           HTML rendering/editing library - bonobo component binary
ii  libgtkhtml-data                   1.1.10-9                          HTML rendering/editing library - data files.
ii  libgtkhtml1.1-3                   1.1.10-9                          HTML rendering/editing library - runtime files.
ii  libgtkhtml3.8-15                  3.8.1-1                           HTML rendering/editing library - runtime files
Comment 8 André Klapper 2006-04-11 19:18:14 UTC
ok, your packages look good.

i still wonder if it's evo at all - the stacktrace does not have any evolution traces in the threads where a signal handler is called. anyway, not your problem. :-)
Comment 9 shoktai 2006-04-11 19:29:51 UTC
Yes, i guess, i'd love to understand what means your sentence ;) 

I also have that when trying to launch evolution from the console:
*** glibc detected *** double free or corruption (out): 0x0814d5b0 ***
Comment 10 André Klapper 2006-04-12 10:26:12 UTC
errmm.... funny man! ;-)
you've actually read bug 336797 and the sentence about "*** glibc detected ***"? :-)
ok, this IS a duplicate of bug 336797, but i'm going to close this only after you've managed to get evolution running without problems. :-)
so please try out the workarounds described in bug 336797, and read
http://mail.gnome.org/archives/evolution-list/2006-April/msg00009.html

thanks in advance. :-)
Comment 11 shoktai 2006-04-12 19:03:01 UTC
"Wow, look at him go. You're the real Lord of the Dance, Homer"
Evolution rocks again.

Thanks so much. 
Comment 12 André Klapper 2006-04-13 10:12:59 UTC
i interpret this as a "fixed". no problem, you're welcome. ;-)

*** This bug has been marked as a duplicate of 336797 ***
Comment 13 André Klapper 2006-04-13 10:17:05 UTC
damn, wrong one. sorry for the noise.
Comment 14 André Klapper 2006-04-13 10:17:51 UTC

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