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 470618 - crash in Tasks: While forwarding email m...
crash in Tasks: While forwarding email m...
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-27 07:14 UTC by petri.laine
Modified: 2008-01-25 15:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description petri.laine 2007-08-27 07:14:13 UTC
Version: 2.10

What were you doing when the application crashed?
While forwarding email message, I had the message attached in the new message window as I wanted it inlined. Then, when I was closing new message window buy clicking the 'x' -close button of the window, evolution entered into this error condition.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 646103040 vsize: 646103040 resident: 75399168 share: 57901056 rss: 75399168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188194297 rtime: 748 utime: 671 stime: 77 cutime:31 cstime: 18 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496414864 (LWP 3283)]
[New Thread 1136679248 (LWP 3714)]
[New Thread 1147435344 (LWP 3335)]
[New Thread 1115699536 (LWP 3330)]
0x0000003faf60d97f in __libc_waitpid (pid=3772, stat_loc=0x7fffb0213b0c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 1 (Thread 46912496414864 (LWP 3283))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 IA__g_utf8_offset_to_pointer
    at gutf8.c line 302
  • #4 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #5 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #6 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #7 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #13 do_focus_change
    at gtkwindow.c line 4782
  • #14 _gtk_window_set_has_toplevel_focus
    at gtkwindow.c line 7783
  • #15 gtk_window_focus_out_event
    at gtkwindow.c line 4816
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #20 IA__g_signal_emit
    at gsignal.c line 2243
  • #21 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #22 IA__gtk_main_do_event
    at gtkmain.c line 1595
  • #23 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #24 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #25 g_main_context_iterate
    at gmain.c line 2677
  • #26 IA__g_main_loop_run
    at gmain.c line 2881
  • #27 IA__gtk_dialog_run
    at gtkdialog.c line 996
  • #28 e_error_run
    at e-error.c line 625
  • #29 do_exit
    at e-msg-composer.c line 1696
  • #30 delete_event
    at e-msg-composer.c line 2904
  • #31 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #32 IA__g_closure_invoke
    at gclosure.c line 490
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #34 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #35 IA__g_signal_emit
    at gsignal.c line 2243
  • #36 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #37 IA__gtk_main_do_event
    at gtkmain.c line 1509
  • #38 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #39 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #40 g_main_context_iterate
    at gmain.c line 2677
  • #41 IA__g_main_loop_run
    at gmain.c line 2881
  • #42 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #43 main
    at main.c line 586


----------- .xsession-errors (34 sec old) ---------------------
localuser:lainepj being added to access control list
SESSION_MANAGER=local/pj.office.saunalahtigroup.fi:/tmp/.ICE-unix/3065
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3283): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3283): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
LoadPlugin: failed to initialize shared library /usr/lib/gcj-4.1.2/libgcjwebplugin.so [/usr/lib/gcj-4.1.2/libgcjwebplugin.so: wrong ELF class: ELFCLASS32]
(evolution:3283): e-data-server-DEBUG: Loading categories from "/home/lainepj/.evolution/categories.xml"
(evolution:3283): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------
Comment 1 André Klapper 2008-01-25 15:29:27 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 458670 ***