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 479895 - crash in Tasks: adding a folder to the "...
crash in Tasks: adding a folder to the "...
Status: RESOLVED DUPLICATE of bug 449996
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 480977 485304 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-24 17:26 UTC by oxenreid
Modified: 2008-02-25 06:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description oxenreid 2007-09-24 17:26:34 UTC
Version: 2.10

What were you doing when the application crashed?
adding a folder to the "on this computer".

Children,  When are you going to relase a stable version of this applicaiton?   It used to be more stable than this.  I am a consultant and I count on being able to use my laptop and this program to connect to client systems and to manage may e-mail and to sell the idea that you can use my services to free yourself from microsoft office.  If this crashes every other second it does not make a good impression.  

I even upgraded from the previous "demi-stable" release to this one via a upgrade on Fedora 7.  I completely re-did my configuration with out copying anything from the old folder.  Needless to say this is very painfull and now it still keeps crashing like NT4.0 

BTW, I also find it a pain in the ass to contact you to complain about these issues and how I might participate in getting these crashes  fixed.    Cripes I can't even open a gizmoproject e-mail containg a voice mail with out a crash.  


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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 213278720 vsize: 213278720 resident: 68427776 share: 49467392 rss: 68427776 rss_rlim: 4294967295
CPU usage: start_time: 1190650208 rtime: 4461 utime: 4090 stime: 371 cutime:0 cstime: 0 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 -1208358160 (LWP 4007)]
[New Thread -1421509744 (LWP 5069)]
[New Thread -1296491632 (LWP 4449)]
[New Thread -1287652464 (LWP 4130)]
[New Thread -1265005680 (LWP 4026)]
[New Thread -1210459248 (LWP 4022)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208358160 (LWP 4007))

  • #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/libpango-1.0.so.0
  • #11 ??
    from /usr/lib/libpango-1.0.so.0
  • #12 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-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 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_container_forall
    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 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 gtk_container_forall
    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 gtk_widget_unparent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #48 ??
    from /lib/libgobject-2.0.so.0
  • #49 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #50 ??
    from /lib/libgobject-2.0.so.0
  • #51 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #52 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #53 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #56 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #63 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #64 ??
    from /lib/libgobject-2.0.so.0
  • #65 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #66 ??
    from /lib/libgobject-2.0.so.0
  • #67 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #68 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #69 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #70 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #71 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #72 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #73 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #74 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #75 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #76 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #77 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #78 ??
    from /lib/libglib-2.0.so.0
  • #79 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #80 ??
    from /lib/libglib-2.0.so.0
  • #81 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #82 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #83 main
  • #0 __kernel_vsyscall

Comment 1 Suman Manjunath 2007-11-30 18:26:55 UTC
*** Bug 480977 has been marked as a duplicate of this bug. ***
Comment 2 Suman Manjunath 2007-11-30 19:03:57 UTC
*** Bug 485304 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Mueller 2008-02-25 06:02:57 UTC
Dear Reporter. Please note that 2.10 is cosidered old. Sure we are sorry that Evolution crashes so often for you. If you want to help fixing those issues, please get us bugreports with nice stacktraces. You can find more information here: http://live.gnome.org/GettingTraces

Anyway, this bug looks like bug 449996 to me, hence marking it as such.

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