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 457231 - crash in Tasks: browsing junk
crash in Tasks: browsing junk
Status: RESOLVED DUPLICATE of bug 469626
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 458187 462134 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-15 23:10 UTC by jyu
Modified: 2007-09-04 18:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jyu 2007-07-15 23:10:44 UTC 
What were you doing when the application crashed?
browsing junk


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 553734144 vsize: 553734144 resident: 42000384 share: 21061632 rss: 42000384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184540717 rtime: 844 utime: 661 stime: 183 cutime:43 cstime: 70 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 46912496402016 (LWP 29332)]
[New Thread 1126455632 (LWP 29668)]
[New Thread 1115965776 (LWP 29667)]
[New Thread 1105475920 (LWP 29388)]
[New Thread 1105209680 (LWP 29370)]
(no debugging symbols found)
0x000000338a60d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 148253

Thread 1 (Thread 46912496402016 (LWP 29332))

  • #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_free1
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #9 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #18 ??
    from /lib64/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #21 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (86 sec old) ---------------------
(evolution:29332): camel-WARNING **: Could not create key entry for word 'shed': Interrupted system call
(evolution:29332): camel-WARNING **: Could not create key entry for word 'deadly': Interrupted system call
(evolution:29332): camel-WARNING **: Could not create key entry for word 'tandoori': Interrupted system call
(evolution:29332): camel-WARNING **: Could not create key entry for word 'sugars': Interrupted system call
(evolution:29332): camel-WARNING **: Could not create key entry for word 'examples': Interrupted system call
--------------------------------------------------
Comment 1 palfrey 2007-07-19 15:12:53 UTC 
*** Bug 458187 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-08-01 11:39:17 UTC 
*** Bug 462134 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Mueller 2007-09-04 18:22:51 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 469626 ***