Re: Application manager broken
 

This gives me more to work with. When on WiFI it looks like a DNS problem.. try using the google DNS servers described in a thread where someone in ireland was getting similar responses.

Again in this thread with almost identical readouts to yours with wifi. But, this may lead to being a problem in how the new firmware uses DNS entries.

Try adding 8.8.8.8 and 8.8.4.4 to your /etc/resolv.conf and see if that fixes your wifi problems.

For the 3G - what exactly is the error?

Re: Application manager broken
 

In theory, yes. But I've also wondered this myself on how Maemo is going to handle dependencies. For example, say someone ports a CLI app that does something useful (pianobar, for example, for pandora radio) and then someone else creates a GUI front-end for it.. if the GUI frontend gets votes *before* pianobar itself gets votes.. would the GUI wind up in extras before pianobar can? How is this prevented?

Definitely a topic for a different thread though..

Re: Application manager broken
 

Didn't he say no error, it's just very very slow?

Also, my wifi actually NATs to my PC, second NIC. The PC resolves repository.maemo.org just fine. I did notice, though, that doing a DNS on the name THEN tapping update makes it update in like 5 seconds, which is odd. It usually takes like 20 or so.

--

++ [ 0:43:37.79] [Ndi] D:\Admin\Projects\LANMap>dns repository.maemo.org
[DNS] lookup on "repository.maemo.org" resolved. Host : a515.g.akamai.net
IP list:
81.196.26.177
81.196.26.154

The format's a little odd, it's a custom W7

Re: Application manager broken
 

GUI wouldn't be allowed to enter Extras before pianobar is there as long as GUI is packaged properly (has pianobar as a dependency)

Re: Application manager broken
 

Very good information to have.. thank you.

Re: Application manager broken
 

I'll have a go at changing the DNS settings after the terminal thing is done. Since my last post it is only 33% now so it'll probably take an hour or so.

And the 3G error (I'll confirm this when this thing is done as well) is something along the lines of:

I'll try and refresh the sources over 3G and it'll say "sources were only partially refeshed, click details for a detailed report" or something, and in the details part for the packages that didn't refresh it says "Proxy CONNECT aborted" (I'm pretty sure - again, I'll double check soon).

Re: Application manager broken
 

And that's all fine.. but the people experiencing this application manager problem appear to have DNS servers that are returning bad ip addresses for the maemo.org repositories. Most notably: 1.0.0.0.

As the other guy said in a link I posted - pre-1.1 he was able to manually edit his advanced settings and set his DNS servers to google's.. and they worked. But *after* the 1.1 update, it appears the advanced settings are not taking effect; or are at least being ignored.. and instead the other /var/run/resolv.conf.wlan0 is being used with the DHCP DNS servers, not the manually added ones.

This would "appear" to be a bug introduced in 1.1 that the Advanced Settings->DNS is not working (would need testing). This does not solve the problem of people unable to get to repositories because of bad DNS servers - but unfortunately theres not much we can do about it. We have to somehow force the Google DNS servers to be used instead, in these cases. Not difficult: If the Advanced Settings worked.. since they aren't appearing to - you have to do it by hand.

Re: Application manager broken
 

So, by changing my DNS settings, technically everything should work fine over WiFi, and I just won't be able to download things over 3G from the repos that don't work because of the "Proxy CONNECT aborted" error?

I can live with that I guess.

EDIT: Terminal thing is done:

Reading package lists... Done
W: Failed to fetch http://repository.maemo.org/extras/d...le/Release.gpg Could not connect to repository.maemo.org:80 (1.0.0.0), connection timed out

(Then there are a lot more "failed to fetch" errors, all because they timed out)

W: Some index files failed to download, they have been ignored, or old ones used instead.
W: You may want to run apt-get update to correct these problems

:(

Re: Application manager broken
 

Do any https sites work in the browser? The app manager is only doing standard http/https downloads.

Re: Application manager broken
 

You are lucky! You are not censored!