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 469731 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 475583
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-23 21:49 UTC by linxx506
Modified: 2007-10-02 09:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description linxx506 2007-08-23 21:49:17 UTC
Version: 2.10

What were you doing when the application crashed?



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:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 145342464 vsize: 145342464 resident: 55021568 share: 37081088 rss: 55021568 rss_rlim: 4294967295
CPU usage: start_time: 1187904599 rtime: 1031 utime: 979 stime: 52 cutime:1 cstime: 5 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 -1208187168 (LWP 8557)]
[New Thread -1317725296 (LWP 9195)]
[New Thread -1286276208 (LWP 9194)]
[New Thread -1296766064 (LWP 9193)]
[New Thread -1259099248 (LWP 8881)]
[New Thread -1269589104 (LWP 8596)]
[New Thread -1236780144 (LWP 8592)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208187168 (LWP 8557))

  • #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 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (287 sec old) ---------------------
(evolution:8557): e-data-server-DEBUG: Loading categories from "/home/grad/linx506/.evolution/categories.xml"
(evolution:8557): e-data-server-DEBUG: Loaded 29 categories
(evolution:8557): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:8557): 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?)
(evolution:8557): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x935c5a0'
(evolution:8557): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x935c6c0'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3403b55 specified for 0x3403d22 (Delete acc).
(evolution:8557): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:8557): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-08-26 18:49:41 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!

[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Suman Manjunath 2007-10-02 09:43:59 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 475583 ***