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 483291 - crash in Tasks: CLosing an email
crash in Tasks: CLosing an email
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-04 10:07 UTC by wilvanantwerpen
Modified: 2008-02-20 06:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description wilvanantwerpen 2007-10-04 10:07:45 UTC
Version: 2.10

What were you doing when the application crashed?
CLosing an email


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Clearlooks

Memory status: size: 762523648 vsize: 762523648 resident: 160743424 share: 62656512 rss: 160743424 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191489445 rtime: 10021 utime: 9764 stime: 257 cutime:0 cstime: 1 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 46912496382096 (LWP 28198)]
[New Thread 1252067664 (LWP 28371)]
[New Thread 1074006352 (LWP 28308)]
[New Thread 1199618384 (LWP 28222)]
(no debugging symbols found)
0x000000357060d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496382096 (LWP 28198))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #8 ??
    from /lib64/libglib-2.0.so.0
  • #9 bonobo_ui_engine_dispose
    from /usr/lib64/libbonoboui-2.so.0
  • #10 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #11 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #12 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #14 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #15 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (90691 sec old) ---------------------
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:3004): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 wilvanantwerpen 2007-10-04 15:47:59 UTC
Hmm... i suggest to flag this one as NON reproducible as i have a strong suspicion that it happened because of http://bugzilla.gnome.org/show_bug.cgi?id=483282
Haven't seen the problem after rebooting the box.
Comment 2 Akhil Laddha 2008-02-20 06:45:11 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 447591 ***