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 466765 - crash in Tasks: opening browser
crash in Tasks: opening browser
Status: RESOLVED DUPLICATE of bug 463568
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 479629 497286 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-14 21:20 UTC by rjohnston
Modified: 2007-11-16 13:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rjohnston 2007-08-14 21:20:09 UTC
Version: 2.10

What were you doing when the application crashed?
opening browser


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 170037248 vsize: 170037248 resident: 65527808 share: 46518272 rss: 65527808 rss_rlim: 4294967295
CPU usage: start_time: 1187122451 rtime: 2928 utime: 2718 stime: 210 cutime:2 cstime: 8 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 -1208252704 (LWP 4108)]
[New Thread -1374725232 (LWP 5975)]
[New Thread -1301099632 (LWP 5934)]
[New Thread -1244558448 (LWP 4404)]
[New Thread -1266685040 (LWP 4402)]
[New Thread -1233421424 (LWP 4145)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208252704 (LWP 4108))

  • #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 /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_widget_region_intersect
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 gtk_container_propagate_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_container_forall
    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 ??
    from /usr/lib/libgtk-x11-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 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #24 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #26 ??
    from /lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-09-21 13:19:51 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

*** This bug has been marked as a duplicate of 463568 ***
Comment 2 palfrey 2007-09-24 15:52:44 UTC
*** Bug 479629 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-11-16 13:30:48 UTC
*** Bug 497286 has been marked as a duplicate of this bug. ***