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 465828 - crash in Tasks: Copying from a pop accou...
crash in Tasks: Copying from a pop accou...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 473164 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-12 01:11 UTC by rohare
Modified: 2007-11-30 17:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rohare 2007-08-12 01:11:27 UTC
Version: 2.10

What were you doing when the application crashed?
Copying from a pop account to my local IMAP inbox.


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.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 680587264 vsize: 680587264 resident: 87162880 share: 41951232 rss: 87162880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186845430 rtime: 1946 utime: 1792 stime: 154 cutime:26 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496365712 (LWP 28345)]
[New Thread 1147435344 (LWP 30414)]
[New Thread 1157925200 (LWP 30413)]
[New Thread 1136945488 (LWP 29177)]
[New Thread 1126455632 (LWP 28387)]
[New Thread 1094719824 (LWP 28382)]
(no debugging symbols found)
0x00000038cc80d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496365712 (LWP 28345))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 pango_attr_list_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #12 ??
    from /lib64/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #17 bonobo_ui_engine_prune_widget_info
    from /usr/lib64/libbonoboui-2.so.0
  • #18 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #19 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #20 ??
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #24 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #25 bonobo_ui_xml_rm
    from /usr/lib64/libbonoboui-2.so.0
  • #26 bonobo_ui_engine_xml_rm
    from /usr/lib64/libbonoboui-2.so.0
  • #27 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #28 Bonobo_UIContainer_removeNode
    from /usr/lib64/libbonobo-2.so.0
  • #29 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #30 ??
    from /usr/lib64/evolution/2.10/libmenus.so.0
  • #31 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #33 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #34 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #35 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #36 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #37 ??
    from /lib64/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #39 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #40 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (161 sec old) ---------------------
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x17e5580'
(evolution:28345): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x1cfa4b0'
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x17e5180'
(gnome-terminal:20824): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(evolution:28345): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x1cfacb0'
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x1cfb0b0'
--------------------------------------------------
Comment 1 palfrey 2007-09-03 16:56:05 UTC
*** Bug 473164 has been marked as a duplicate of this bug. ***
Comment 2 Suman Manjunath 2007-11-30 17:57:45 UTC
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0x1cfacb0'
(evolution:28345): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0x1cfb0b0'

This is bug #447591, which is fixed now.

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