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 455158 - crash in Tasks: checking email, but i ca...
crash in Tasks: checking email, but i ca...
Status: RESOLVED DUPLICATE of bug 405646
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 458058 458073 459214 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-09 13:29 UTC by bohari.japar
Modified: 2007-08-01 15:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bohari.japar 2007-07-09 13:29:38 UTC 
What were you doing when the application crashed?
checking email, but i cant see any


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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: OSX

Memory status: size: 111124480 vsize: 111124480 resident: 32133120 share: 20332544 rss: 32133120 rss_rlim: 4294967295
CPU usage: start_time: 1183987566 rtime: 262 utime: 245 stime: 17 cutime:0 cstime: 4 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208359200 (LWP 4668)]
[New Thread -1250563184 (LWP 4759)]
[New Thread -1239671920 (LWP 4688)]
(no debugging symbols found)
0x007e1402 in __kernel_vsyscall ()

+ Trace 146727

Thread 3 (Thread -1239671920 (LWP 4688))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/i686/nosegneg/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/nosegneg/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/i686/nosegneg/libpthread.so.0
  • #10 start_thread
    from /lib/i686/nosegneg/libpthread.so.0
  • #11 clone
    from /lib/i686/nosegneg/libc.so.6 


----------- .xsession-errors (13 sec old) ---------------------
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
** Message: Unable to load host id information, assuming unset
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
DEBUG: Inbox/ (mbox:/root/.evolution/mail/local#Inbox/)
--------------------------------------------------
Comment 1 palfrey 2007-07-19 15:11:09 UTC 
*** Bug 458058 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-07-19 15:11:36 UTC 
*** Bug 458073 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-07-22 09:56:17 UTC 
*** Bug 459214 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-08-01 15:03:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 405646 ***