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 478804 - crash in Tasks: fgn
crash in Tasks: fgn
Status: RESOLVED DUPLICATE of bug 442949
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-21 01:01 UTC by abhrodeepsaha
Modified: 2007-10-07 09:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description abhrodeepsaha 2007-09-21 01:01:26 UTC
What were you doing when the application crashed?
fgn 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 137564160 vsize: 137564160 resident: 33607680 share: 21397504 rss: 33607680 rss_rlim: 4294967295
CPU usage: start_time: 1190355944 rtime: 521 utime: 465 stime: 56 cutime:0 cstime: 4 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208727840 (LWP 4178)]
[New Thread -1236214896 (LWP 4196)]
(no debugging symbols found)
0x007d6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208727840 (LWP 4178))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 free
    from /lib/i686/nosegneg/libc.so.6
  • #6 g_free
    from /lib/libglib-2.0.so.0
  • #7 pango_font_description_free
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_context_set_font_description
    from /usr/lib/libpango-1.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-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_container_forall
    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 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_widget_reset_rc_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (18 sec old) ---------------------
(evolution:4178): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:4178): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a42008'
(evolution:4178): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a42128'
(evolution:4178): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
--------------------------------------------------
Comment 1 Susana 2007-10-07 09:47:00 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 442949 ***