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 518471 - crash in Tasks: setting Calendars to wor...
crash in Tasks: setting Calendars to wor...
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-24 19:38 UTC by M Bernard Richards
Modified: 2008-02-28 06:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description M Bernard Richards 2008-02-24 19:38:08 UTC 
Version: 2.10

What were you doing when the application crashed?
setting Calendars to work offline


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 112721920 vsize: 112721920 resident: 44769280 share: 29671424 rss: 44769280 rss_rlim: 4294967295
CPU usage: start_time: 1203874250 rtime: 1129 utime: 1044 stime: 85 cutime:0 cstime: 0 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 -1208138016 (LWP 3350)]
[New Thread -1310737520 (LWP 16535)]
[New Thread -1246069872 (LWP 3360)]
[New Thread -1234187376 (LWP 3358)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 190330

Thread 2 (Thread -1310737520 (LWP 16535))

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


----------- .xsession-errors (7 sec old) ---------------------
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
** 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: checking rw on /dev/pilot
** 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
Xlib: unexpected async reply (sequence 0x22f58)!
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-28 06:46:56 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 334966 ***