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 443732 - crash in Tasks: change of inbox for dire...
crash in Tasks: change of inbox for dire...
Status: RESOLVED DUPLICATE of bug 444866
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 443885 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-03 22:35 UTC by juan_sr
Modified: 2007-07-04 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description juan_sr 2007-06-03 22:35:09 UTC
What were you doing when the application crashed?
change of inbox for directory of query in Evolution


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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 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: 603111424 vsize: 603111424 resident: 39612416 share: 21192704 rss: 39612416 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180909656 rtime: 420 utime: 358 stime: 62 cutime:36 cstime: 31 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 46912496455264 (LWP 3512)]
[New Thread 1084229968 (LWP 3666)]
[New Thread 1115965776 (LWP 3535)]
[New Thread 1105209680 (LWP 3532)]
(no debugging symbols found)
0x00000033bea0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496455264 (LWP 3512))

  • #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 g_slist_remove
    from /lib64/libglib-2.0.so.0
  • #8 html_image_factory_unregister
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #9 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #10 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #15 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #17 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #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/libgtk-x11-2.0.so.0
  • #24 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #33 g_value_unset
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #36 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #37 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #38 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #39 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #40 html_engine_parse
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #41 gtk_html_begin_full
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #42 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #43 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #44 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #45 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #46 ??
    from /lib64/libglib-2.0.so.0
  • #47 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #48 ??
    from /lib64/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #50 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #51 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (13 sec old) ---------------------
  Minor opcode:  6
  Resource id:  0x1406533
(evolution:3512): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution:3512): 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:3512): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f0490'
(evolution:3512): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f0890'
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------
Comment 1 André Klapper 2007-06-10 23:48:05 UTC
*** Bug 443885 has been marked as a duplicate of this bug. ***
Comment 2 Karsten Bräckelmann 2007-07-04 00:49:41 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?

Please, particularly have a look at bug 444866 comment 16.


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