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 467904 - crash in Tasks: clicked on inbox
crash in Tasks: clicked on inbox
Status: RESOLVED DUPLICATE of bug 438276
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-18 08:47 UTC by j1
Modified: 2007-09-21 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description j1 2007-08-18 08:47:29 UTC
Version: 2.10

What were you doing when the application crashed?
clicked on 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 191946752 vsize: 191946752 resident: 85991424 share: 61136896 rss: 85991424 rss_rlim: 4294967295
CPU usage: start_time: 1187425777 rtime: 4666 utime: 4359 stime: 307 cutime:14 cstime: 9 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 -1208224032 (LWP 25833)]
[New Thread -1406653552 (LWP 26517)]
[New Thread -1258546288 (LWP 26352)]
[New Thread -1246581872 (LWP 25879)]
[New Thread -1246315632 (LWP 25852)]
(no debugging symbols found)
0x00154402 in __kernel_vsyscall ()

Thread 1 (Thread -1208224032 (LWP 25833))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 bonobo_ui_engine_update
    from /usr/lib/libbonoboui-2.so.0
  • #12 bonobo_ui_engine_xml_merge_tree
    from /usr/lib/libbonoboui-2.so.0
  • #13 ??
    from /usr/lib/libbonoboui-2.so.0
  • #14 _ORBIT_skel_small_Bonobo_UIContainer_setNode
    from /usr/lib/libbonobo-2.so.0
  • #15 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #16 Bonobo_UIContainer_setNode
    from /usr/lib/libbonobo-2.so.0
  • #17 ??
    from /usr/lib/libbonoboui-2.so.0
  • #18 bonobo_ui_component_set
    from /usr/lib/libbonoboui-2.so.0
  • #19 bonobo_ui_component_set_tree
    from /usr/lib/libbonoboui-2.so.0
  • #20 bonobo_ui_component_set_translate
    from /usr/lib/libbonoboui-2.so.0
  • #21 ??
    from /usr/lib/evolution/2.10/libmenus.so.0
  • #22 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #23 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #24 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #25 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #26 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #27 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #33 main
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-09-21 13:27:44 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 438276 ***