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 468771 - crash in Evolution Mail: composing email
crash in Evolution Mail: composing email
Status: RESOLVED DUPLICATE of bug 458322
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-08-21 08:50 UTC by maurizio.pierini
Modified: 2007-09-21 21:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description maurizio.pierini 2007-08-21 08:50:18 UTC
What were you doing when the application crashed?
composing email


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-powerpc #1 Sun Jul 29 13:58:06 CEST 2007 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ale-panther_gtk2
Icon Theme: OSX

Memory status: size: 127139840 vsize: 127139840 resident: 34390016 share: 22429696 rss: 34390016 rss_rlim: 4294967295
CPU usage: start_time: 1187594807 rtime: 1877 utime: 1783 stime: 94 cutime:4 cstime: 6 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 805675488 (LWP 7703)]
[New Thread 840148176 (LWP 8112)]
[New Thread 849294544 (LWP 8084)]
[New Thread 859174096 (LWP 7770)]
[New Thread 848536784 (LWP 7769)]
[New Thread 831759568 (LWP 7735)]
[New Thread 823370960 (LWP 7734)]
[New Thread 814982352 (LWP 7733)]
(no debugging symbols found)
0x0f1e2994 in ?? () from /lib/libpthread.so.0

Thread 1 (Thread 805675488 (LWP 7703))

  • #0 ??
    from /lib/libpthread.so.0
  • #1 ??
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_utf8_offset_to_pointer
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #7 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_bindings_activate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libbonoboui-2.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #37 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #38 ??
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #40 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #41 main
  • #0 ??
    from /lib/libpthread.so.0


----------- .xsession-errors (5711 sec old) ---------------------
** (nm-applet:4693): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.42" is not allowed to own the service "or
** (nm-applet:4693): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.42" is not allowed to own the service "or
** (nm-applet:4693): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.42" is not allowed to own the service "or
** (nm-applet:4693): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.42" is not allowed to own the service "or
** (nm-applet:4693): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.42" is not allowed to own the service "or
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Srinivasa Ragavan 2007-08-21 11:59: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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-09-21 21:22:45 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 458322 ***