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 467113 - crash in Tasks: accepted an appointment
crash in Tasks: accepted an appointment
Status: RESOLVED DUPLICATE of bug 460409
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-15 22:35 UTC by kobic.chen
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kobic.chen 2007-08-15 22:35:59 UTC
Version: 2.10

What were you doing when the application crashed?
accepted an appointment 


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 277848064 vsize: 277848064 resident: 103612416 share: 87461888 rss: 103612416 rss_rlim: 4294967295
CPU usage: start_time: 1187214257 rtime: 1311 utime: 1225 stime: 86 cutime:55 cstime: 19 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 -1208531232 (LWP 4542)]
[New Thread -1488266352 (LWP 8712)]
[New Thread -1425327216 (LWP 7065)]
[New Thread -1287193712 (LWP 4856)]
[New Thread -1276703856 (LWP 4582)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1488266352 (LWP 8712))

  • #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 (29 sec old) ---------------------
(evolution:4542): e-dateedit.c-WARNING **: time_text:09:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:08:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:08:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:17:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:08:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:17:00
(evolution:4542): e-dateedit.c-WARNING **: time_text:17:00
** Message: Response 1
** Message: Response 1
--------------------------------------------------
Comment 1 Suman Manjunath 2007-08-26 19:31:04 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 more useful description to this bug.

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

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 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 Suman Manjunath 2007-09-21 17:41:03 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 460409 ***