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 477670 - crash in Tasks: checking the junk folder
crash in Tasks: checking the junk folder
Status: RESOLVED DUPLICATE of bug 469626
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-17 06:48 UTC by mckinlay
Modified: 2007-09-20 18:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mckinlay 2007-09-17 06:48:25 UTC
Version: 2.10

What were you doing when the application crashed?
checking the junk folder


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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 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: 609804288 vsize: 609804288 resident: 51965952 share: 32272384 rss: 51965952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190011534 rtime: 533 utime: 502 stime: 31 cutime:630 cstime: 51 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 46912496357520 (LWP 4816)]
[New Thread 1084229968 (LWP 4924)]
[New Thread 1136679248 (LWP 4923)]
[New Thread 1094986064 (LWP 4884)]
[New Thread 1094719824 (LWP 4826)]
(no debugging symbols found)
0x000000322380d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496357520 (LWP 4816))

  • #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_free1
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #9 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #18 ??
    from /lib64/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #21 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (10 sec old) ---------------------
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
(evolution:4816): 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?)
BBDB spinning up...
(evolution:4816): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8dead0'
(evolution:4816): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8de4d0'
report junk?? Watch the pounds disappear
report junk?? Software
report junk?? Don't be the "little guy" in the club
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-20 18:05: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 469626 ***