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 517589 - crash in Tasks: changing prefrences in E...
crash in Tasks: changing prefrences in E...
Status: RESOLVED DUPLICATE of bug 489872
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-20 01:54 UTC by brustb
Modified: 2008-02-20 07:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description brustb 2008-02-20 01:54:42 UTC
Version: 2.10

What were you doing when the application crashed?
changing prefrences in Evolution


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.14-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 142966784 vsize: 142966784 resident: 54312960 share: 35213312 rss: 54312960 rss_rlim: 4294967295
CPU usage: start_time: 1203461437 rtime: 5456 utime: 5008 stime: 448 cutime:1344 cstime: 91 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 -1208698128 (LWP 2953)]
[New Thread -1273414768 (LWP 11001)]
[New Thread -1231062128 (LWP 3035)]
[New Thread -1262531696 (LWP 3034)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()
  • #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 ??
    from /usr/lib/libpango-1.0.so.0
  • #10 g_slist_foreach
    from /lib/libglib-2.0.so.0
  • #11 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/libpango-1.0.so.0
  • #13 ??
    from /usr/lib/libpango-1.0.so.0
  • #14 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_socket_add_id
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 bonobo_socket_add_id
    from /usr/lib/libbonoboui-2.so.0
  • #39 bonobo_control_frame_get_remote_window
    from /usr/lib/libbonoboui-2.so.0
  • #40 ??
    from /usr/lib/libbonoboui-2.so.0
  • #41 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #42 ??
    from /lib/libgobject-2.0.so.0
  • #43 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #44 ??
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #46 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #47 gtk_widget_realize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #54 ??
    from /lib/libgobject-2.0.so.0
  • #55 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #56 ??
    from /lib/libgobject-2.0.so.0
  • #57 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #58 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #59 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgtk-x11-2.0.so.0


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/liblber-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
Cannot access memory at address 0xbf9ee328
/usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
Couldn't get registers: No such process.
Quitting: Can't detach LWP 3034: No such process
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-20 07:00:02 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 489872 ***