© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Hi there Laudeci,
also thank you to you.
The screenshots in this bug report were all after the fix.
Our last two messages must have crossed.
Sorry about that.
I can do sudo apt-get remove aptoncd, to make new screenshots of the previous thing? Or maybe an Strace? I will check the image tommorow to check if it is not corrupt. I made two images actually, the second one with no other applications running. The pattern is the same, two parallel lines for RAM and swap, and only one of my dual cores (CPU) is used, all is written away to the SATA Hitachi hard disk. In the previous version all was written away to the RAM. I had noticed this because I had to remove one of my two 2 GB memory chips, since the BIOS provided by Acer would not allow for 4 GB, as it was preinstalled with Vista 32-bit, although officially they advertised it could do that. After I removed one of the chips, some bugs disappeared, but the aptoncd thing just occured more rapidly, hence it had to be the RAM usage by aptoncd, but it is fixed now.
Thanks,
Thomas.