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 465023 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431459
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-09 12:20 UTC by siddiqui
Modified: 2007-08-23 11:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description siddiqui 2007-08-09 12:20:44 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:21:43 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: 589398016 vsize: 589398016 resident: 46039040 share: 32399360 rss: 46039040 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186681761 rtime: 192 utime: 175 stime: 17 cutime:2 cstime: 6 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 46912629597760 (LWP 3975)]
[New Thread 1084229968 (LWP 4054)]
[New Thread 1105209680 (LWP 4046)]
(no debugging symbols found)
0x00002aaaacdc197f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912629597760 (LWP 3975))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #6 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #7 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (47 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340d4b6 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--- Hash table keys for warning below:
--> file:///home/siddiqui
(nautilus:3945): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Writing new pickle
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3975): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3975): DEBUG: mailto URL program: evolution
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 palfrey 2007-08-09 16:37:18 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Mart Raudsepp 2007-08-23 11:54:39 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 431459 ***