(In reply to comment #0)
> ACTUAL OUTCOME:
> says download fails
> 

Could you include the actual error message with exact steps to reproduce?
Thanks.

I have tried several way of downloading installing with the same result.  This
is the easiest way to reproduce it.
1. go to tableteer.nokia.com/tableteer/os2008
2. click on camera  ( or any other application, except  bomerman will install
fine)
3. click install the camera app
4. it opens a 2 new windows and prompts to download camera.install size.34kB
5. click open (or save and run later yields same result)
6. it opens app man
7. it downloads 5kB
8. refreshes app list
9. it prompts install app camera 3.4 .2MB
10. click ok
11. download fashes up for 185kB, closes
12. then messages "Downloadng camera failed"

This happens everytime with any application except bomerman.  Thank you for
your reply, I am shipping back to nokia for the 2nd time today and am
requesting a new device.

(In reply to comment #1)
> (In reply to comment #0)
> > ACTUAL OUTCOME:
> > says download fails
> > 
> 
> Could you include the actual error message with exact steps to reproduce?
> Thanks.
>

ran apt-get update in xterm, I got "E: Could not open lock file
/var/lib/apt/lists/lock-open (13 permission denied)"

Otherwise, exact same steps/results. I tried several packages from several
repositories. N810 with OS2008 50-2.

I found a workaround thanks to this thread on ITT.com:
http://www.internettablettalk.com/forums/showthread.php?t=15902

Basically, somehow the internal memory got corrupted. The workaround solution
is to power the tablet off, connect it to your PC via USB and turn it back on.
You should now be able to format the internal memory card on your PC, reinstall
the firmware, and have it all fixed.

Comment 5 Ryan Abel 2008-05-18 14:08:15 UTC

Application manager needs to fail more gracefully when encountering a corrupted
internal card.

Comment 6 Marius Vollmer 2008-06-03 16:49:37 UTC

(In reply to comment #5)
> Application manager needs to fail more gracefully when encountering a corrupted
> internal card.

Yes.  Some improvements are coming up.  Package checksums are checked again
after downloading all packages, and memory cards that can not be written to
will not be used for downloading packages.

Comment 7 Eero Tamminen 2008-07-08 09:45:57 UTC

(In reply to comment #4)
> Basically, somehow the internal memory got corrupted. The workaround solution
> is to power the tablet off, connect it to your PC via USB and turn it back on.
> You should now be able to format the internal memory card on your PC

Formatting is a bit extreme.

If the card is not badly corrupted, it should be enough just to
correct it from the PC (Windows, OSX and Linux should all provide
a tool for this).  Even the device might be able to do it (from
File manager), but this might not be always be possible because
it can require more free memory than is available.

Comment 8 Ryan Abel 2008-07-08 14:59:31 UTC

(In reply to comment #7)
> (In reply to comment #4)
> > Basically, somehow the internal memory got corrupted. The workaround solution
> > is to power the tablet off, connect it to your PC via USB and turn it back on.
> > You should now be able to format the internal memory card on your PC
> 
> Formatting is a bit extreme.
> 

Well, in the case of the N810, formatting is necessary, as the partition table
is oversized and must be recreated.

Comment 9 Eero Tamminen 2008-08-20 11:20:25 UTC

> Well, in the case of the N810, formatting is necessary, as the partition
> table is oversized and must be recreated.

This should concern only a small batch of early devices.  There are
many ways in which user can him/herself corrupt FAT file systems
(it's a bit shame that this fragile MicroSoft creation is still
so popular that all memory cards need to use it)...

Comment 10 Andre Klapper 2008-10-08 14:50:15 UTC

(Removing deprecated "Future" Target Milestone.)

Comment 11 Andre Klapper 2008-10-08 16:40:19 UTC

(In reply to comment #6)
> Package checksums are checked again
> after downloading all packages, and memory cards that can not be written to
> will not be used for downloading packages.

Marius, will this be done for Fremantle or for Diablo SSU updates?

Comment 12 Marius Vollmer 2008-10-08 17:10:45 UTC

(In reply to comment #11)
> (In reply to comment #6)
> > Package checksums are checked again
> > after downloading all packages, and memory cards that can not be written to
> > will not be used for downloading packages.
> 
> Marius, will this be done for Fremantle or for Diablo SSU updates?

These changes are in hildon-application-manager 2.1.13, released 2008-06-03, so
you should have them in Diablo already.

Comment 13 Eero Tamminen 2008-10-08 18:13:15 UTC

> These changes are in hildon-application-manager 2.1.13, released 2008-06-03, so
you should have them in Diablo already.

Should this be marked as fixed?  It doesn't exactly fix the reported issue, but
should now at least detect the situation and give a sensible error message
about the problem, right?

Comment 14 Andre Klapper 2008-10-09 16:32:22 UTC

(In reply to comment #13)
> > These changes are in hildon-application-manager 2.1.13, released 2008-06-03, so
> you should have them in Diablo already.
> 
> Should this be marked as fixed?  It doesn't exactly fix the reported issue, but
> should now at least detect the situation and give a sensible error message
> about the problem, right?

That was exactly my reasoning for asking Marius here - yes, I agree.