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 474305 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 444079
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-06 18:12 UTC by gioxsexy
Modified: 2007-10-03 03:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description gioxsexy 2007-09-06 18:12:36 UTC 
Version: 2.10

What were you doing when the application crashed?



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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 129126400 vsize: 129126400 resident: 49610752 share: 32772096 rss: 49610752 rss_rlim: 4294967295
CPU usage: start_time: 1189100951 rtime: 2005 utime: 1668 stime: 337 cutime:47 cstime: 40 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 -1208351008 (LWP 3911)]
[New Thread -1243546736 (LWP 4320)]
[New Thread -1229292656 (LWP 4135)]
[New Thread -1306485872 (LWP 4131)]
[New Thread -1285506160 (LWP 4000)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 160945

Thread 1 (Thread -1208351008 (LWP 3911))

  • #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 pango_layout_set_text
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/evolution/2.10/libemiscwidgets.so.0
  • #13 e_clipped_label_set_text
    from /usr/lib/evolution/2.10/libemiscwidgets.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #20 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (89 sec old) ---------------------
(evolution:3911): camel-WARNING **: Could not find key entry for word 'จากแอร': Illegal seek
(evolution:3911): camel-WARNING **: Could not find key entry for word 'างประเทศ': Illegal seek
(evolution:3911): camel-WARNING **: Could not find key entry for word 'องการยกเล': Illegal seek
(evolution:3911): camel-WARNING **: Could not find key entry for word 'จากแอร': Illegal seek
(evolution:3911): camel-WARNING **: Could not find key entry for word 'างประเทศ': Illegal seek
--------------------------------------------------
Comment 1 Luis Medinas 2007-09-07 18:17:33 UTC 
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
Comment 2 André Klapper 2007-10-03 03:40:21 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 444079 ***