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 470472 - crash in Tasks: préférences
crash in Tasks: préférences
Status: RESOLVED DUPLICATE of bug 405646
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-26 17:02 UTC by jpbaurens
Modified: 2007-10-07 18:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jpbaurens 2007-08-26 17:02:15 UTC 
Version: 2.10

What were you doing when the application crashed?
préférences


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: 111370240 vsize: 111370240 resident: 43552768 share: 31625216 rss: 43552768 rss_rlim: 4294967295
CPU usage: start_time: 1188146880 rtime: 2043 utime: 1841 stime: 202 cutime:9 cstime: 16 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 -1208841488 (LWP 3082)]
[New Thread -1250477168 (LWP 3191)]
[New Thread -1219617904 (LWP 3116)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 158020

Thread 3 (Thread -1219617904 (LWP 3116))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6 


----------- .xsession-errors (113 sec old) ---------------------
(evolution:3082): e-dateedit.c-WARNING **: time_text:17:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:07:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:17:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:17:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:18:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:07:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:18:00
(evolution:3082): e-dateedit.c-WARNING **: time_text:18:00
--------------------------------------------------
Comment 1 Suman Manjunath 2007-08-27 05:22:29 UTC 
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 more useful description to this bug.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you please get us a stack trace with debugging symbols [1]? 

Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks!

[1] debugging symbols are obtained by installing debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Tobias Mueller 2007-10-07 18:19:47 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 405646 ***