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 465045 - crash in Tasks: Don
crash in Tasks: Don
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-08-09 14:00 UTC by Joao Rodrigues
Modified: 2007-09-24 19:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Joao Rodrigues 2007-08-09 14:00:24 UTC
Version: 2.10

What were you doing when the application crashed?
Don't know... I was in a diferente desktop when I got this report


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:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 116129792 vsize: 116129792 resident: 37236736 share: 30003200 rss: 37236736 rss_rlim: 4294967295
CPU usage: start_time: 1186664939 rtime: 468 utime: 422 stime: 46 cutime:2 cstime: 7 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 -1208617248 (LWP 18142)]
[New Thread -1253057648 (LWP 27409)]
[New Thread -1263547504 (LWP 18172)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208617248 (LWP 18142))

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


----------- .xsession-errors (404 sec old) ---------------------
/usr/bin/bittorrent:3785: GtkDeprecationWarning: gtk.threads_leave is deprecated, use gtk.gdk.threads_leave instead
  gtk.threads_leave()
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
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
Aviso do gestor de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x460005b (OpenOffice)
Aviso do gestor de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
calling convert '/tmp/.gnome_thumbnail.RBMHWT.QQ5GWT' +matte -thumbnail 128x128 png:'/tmp/.gnome_thumbnail.RBMHWT'
--- Hash table keys for warning below:
--> file:///home/gothicknight
(nautilus:20211): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Aviso do gestor de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c0005b (Sem nome1 )
Aviso do gestor de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 palfrey 2007-08-09 16:37:23 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 Tobias Mueller 2007-09-24 19:45:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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