https sites work in the browser.

Also, I changed my DNS settings to
Primary: 8.8.8.8
Secondary: 8.8.4.4

and I can now access the Apps from App Manager but like through 3G, only the "maemo.org" repo, the others give me the same error as the 3G error:
"Proxy CONNECT aborted"

EDIT: Don't worry, I closed the app, opened it again and refreshed, and all the repos work, over WiFi and 3G (the proxy error was caused because I had a proxy configured for http but not for https, so i just used the same settings for that as http)

Thanks for everything guys

(missed your Q, sorry) - I deleted files as you recommended. Actually, I did it twice, because there is another subdirectory there - partial and I deleted it too.

But it is created again.

Lucky as not in the US, yes. I'm beginning to actually look a bit fearful over the ocean there. Allowed legal wiretappings, remote microphone activation, swift arrests, security over security, FCC, disregarding international standards, RIAA, and the list goes on.

I am aware of the off-topic here, sorry, but I remember a few years ago some of my friends started to go over there to work (good people, sysadmins, engineers, architects, pilots, those people) and in the last year I've met over half of them back here. And all of them say that the people are nice over there.

Ok, enough of the off-topic. I posted because I wanted to say that I specifically ordered the EU non-localized phone because last time I had the EU+Region2 or somesuch nonsense that had arab-backed keyboard, and I never got an update from Nokia while everyone had fixed bugs.

No, I don't want it's new version at a moment. But I did that with another applications and it just disappears.

Morever, I may try to "Restore" package in Application Manager. It shows me my package ... but shadowed and impossible to select.

It's supposed to do that. The command simply reset all local caches.

Is that new? I never saw that. All my apps return to a normal state in the AM.

Glad you got straightened out.

Again, the primary problem - the censoring logic in application manager.

Why it is going crazy on one distribution (002) and works fine on another, that is just matter of luck - who is stricken and who is not, where is a trigger bug. But it shows that the whole idea - "hide stuff from user control" is BAD. User MAY want to hide something to simplify life and it is OK, but prevent him ... it causes the problem fix by another means, in this case - long story what and where is broken, apt-get/dpkg/rootsh usage and actually creates more problems.

I don't see how it creates *more* problems? In fact.. the real tools of the system are working fine.. apt-get see's the updates as available, rootsh gives you root, and dpkg installs what you tell it to.

Your problem is Nokia's App Manager is acting screwy.. whether this is actually a design flaw in AM post 1.1 or something specific with your device is still up in the air. Most of the "other problem" users I've seen were actually fixed by something totally unrelated. Take this thread for example.. the OP is fixed. It was a combination of DNS and bad proxy settings. Somehow I doubt that's your problem.

Your problem is so far fairly unique.. and rather intriguing.. but I'm not ready to claim bug in 1.1, or AM, and I certainly don't fault the "theory" of hiding mostly useless apps from users.

I've hit this 1.0.0.0 problem before.

In my case (and I suspect others here - try a search on 1.0.0.0 ) it's caused by a bad interaction between my adsl router and the resolver library.

Typically the browser isn't using the same resolver library that cmdline apps are (eg ping, apt-get, ..) so they can fail while the browser carries on working, adding to the mystery.

My particular router insists on handing out the dns address via dhcp, so on the N900 (still on PR1.0.1) I work around this by configuring a static IP on the N900 and setting the DNS addresses to openDNS nameservers manually - has worked fine for me since last November.

However, on my particular router, a fix is also possible by ssh-ing into the router and modifying its udhcpd.conf file. Inside that file there's a line like

opt dns 10.100.0.1

(that is the router's own ip address) which sends out the order over dhcp to use the router for dns queries. So I just change this to

opt dns 208.67.220.220 208.67.222.222

then

ps auxw | grep dhcp

to see what commandline the udhcp service is run with, then

killall udhcpd

and run it with the commandline I saw. In my case, this is:

/usr/sbin/udhcpd /var/tmp/udhcpd.conf

For extra fun, there's no editor (I could find) on the thing, so I had to edit by cat :-)

Also, the udhcpd.conf file is refreshed every time the router gets rebooted, so I've done it a couple of times now.

I mention this to suggest that it can be fixed on the router, but probably that's not for the fainthearted unless there's a web or gui config setting on the router for it

You sure? Look at this:

http://talk.maemo.org/showthread.php?t=41430

http://talk.maemo.org/showthread.php?t=41463

http://talk.maemo.org/showpost.php?p=485351&postcount=7

... and just browse forum 10mins.