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 474256 - crash in Tasks: closed preferences dialo...
crash in Tasks: closed preferences dialo...
Status: RESOLVED DUPLICATE of bug 444924
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-06 14:55 UTC by dont
Modified: 2007-09-06 15:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dont 2007-09-06 14:55:01 UTC 
Version: 2.10

What were you doing when the application crashed?
closed preferences dialog


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 125591552 vsize: 125591552 resident: 45682688 share: 29999104 rss: 45682688 rss_rlim: 4294967295
CPU usage: start_time: 1189060387 rtime: 2189 utime: 1987 stime: 202 cutime:9 cstime: 28 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 -1208768800 (LWP 12204)]
[New Thread -1228239984 (LWP 12265)]
[New Thread -1267180656 (LWP 12262)]
[New Thread -1217356912 (LWP 12227)]
(no debugging symbols found)
0x005a3402 in __kernel_vsyscall ()

+ Trace 160904

Thread 1 (Thread -1208768800 (LWP 12204))

  • #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_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_hash_table_foreach
    from /lib/libglib-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 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-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 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #25 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/evolution/2.10/libemiscwidgets.so.0
  • #28 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #37 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #38 ??
    from /lib/libgobject-2.0.so.0
  • #39 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #40 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #41 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
    from /lib/libgobject-2.0.so.0
  • #46 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #47 ??
    from /lib/libgobject-2.0.so.0
  • #48 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #49 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #54 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #55 ??
    from /lib/libglib-2.0.so.0
  • #56 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #57 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #58 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (31958 sec old) ---------------------
If you can reproduce the crash, please notify the developers
by reporting a bug at:
http://developer.pidgin.im/newticket/
Please make sure to specify what you were doing at the time
and post the backtrace from the core file.  If you do not know
how to get the backtrace, please read the instructions at
http://developer.pidgin.im/wiki/GetABacktrace
If you need further assistance, please IM either SeanEgn or 
LSchiere (via AIM).  Contact information for Sean and Luke 
on other protocols is at
http://developer.pidgin.im/wiki/DeveloperPages
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
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-06 15:01:47 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 444924 ***