Re: Application manager broken
 

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 :)

Re: Application manager broken
 

(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.

Re: Application manager broken
 

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.

Re: Application manager broken
 

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.

Re: Application manager broken
 

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.

Re: Application manager broken
 

Glad you got straightened out.

Re: Application manager broken
 

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.

Re: Application manager broken
 

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.

Re: Application manager broken
 

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 :)

Re: Application manager broken
 

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.

Re: Application manager broken
 

That last one is entirely unhelpful .. it provides no details or information. The first one, half the people in the thread magically "fixed".

That middle one is actually a good thread. They are on to something at the end regarding installing and then uninstalling an app.

NDI - Did you flash 1.1 or OTA update?

ETA: The OP of the second thread posted in the first thread as now "fixed". SO whatever this problem is, it isn't consistent and seems more related to the repositories than App Manager itself.. although I'm not sure how or why.

Re: Application manager broken
 

I don't have those problems because I have a different setup.

I have the beast on the internet with NIC1 and it does PPPoE to the internet, also 10.* IP in the city WAN. The second card, NIC2, is set up using Windows' ICS (basically NAT). This internal LAN serves me (gateway), my secondary PC(and NAS) and the printer along with a WRouter. The WRouter is assigned an 192.168.137.* IP and gets out through me.

As a result, my beast is the only one responsible for Internet activity, as for the phone, it queries the router and the router asks me. I reply all requests from cache or make the query myself outside.

That's why my DNS command from the CLI cached repositories and all other devices have the local IP to use.

When not cached, my PC tries to resolve repositories on its own and fails several times (usually) before they finally resolve and it all works. Why DNS fails so often I can't tell.

I'm considering adding them to etc\hosts. That should cut a lot of problems until I have to manually do this again.

As for egoshin's issue, I have little clue, or supposition why someone would choose to hide the update to wifi info. That makes NO sense. I would understand fmtx or similar, but some of those apps have nothing to show for themselves.

It must be a bug. I hate to suggest this, but could this be a fs issue? Maybe a bad flash or a busted up cluster that messed up a file? You could end up with a reflash and fresh install of all apps. I imagine that would fix everything. But it's my device :P

Edit: OTA for me both 1.01 and 1.1 because I'm on W7x64 and I didn't want to risk incompatibility. Save for the inability to play MPEG1 files (I'm sure it's silly, some library got left behind) no issues here.

Oh, and the standard stuff is known to not work, like xvid in osso-player.

Re: Application manager broken
 

At least the first problem was caused by corrupted Release file in repositories. It should be fixed by now, but since Akamai caching seems to cause problems every now and then it's possible that the server serving you isn't up to date.

What do these files look like when you open them with web browser?

http://repository.maemo.org/extras/d...mantle/Release
http://repository.maemo.org/extras-t...mantle/Release
http://repository.maemo.org/extras-d...mantle/Release

They should look something like this:

Architectures: armel i386 all
Components: free non-free
Date: Wed, 20 Jan 2010 20:53:11 UTC
Label: Extras
Origin: maemo
Suite: fremantle
Version: 2.0
MD5Sum:
d41d8cd98f00b204e9800998ecf8427e 0 free/binary-all/Packages
7b106d3d1528f3224efc46888424fc11 29 free/binary-all/Packages.gz
3ad59e5df9489cd5a6b6c36786d404bb 81 free/binary-all/Release
bb8379d9be4884520ab6b2491a51c849 839659 free/binary-armel/Packages
5add5ff8ac9afc39388adef4215d9687 422870 free/binary-armel/Packages.bz2
---file clipped---

Re: Application manager broken
 

I agree fully that these specific apps he's asking about should not be hidden.. but I do not think they are being hidden by design.. there is a problem somewhere needs addressing. Whether a bug in the firmware or a problem in the network or repo's.

However, I do not agree that ALL hiding of apps should be removed. I seem to be having the same philosophical discussion in several threads right now.. this is rather.. redundant.

Re: Application manager broken
 

Baseline:
Architectures: armel i386 all
Components: free non-free
Date: Wed, 20 Jan 2010 20:53:11 UTC
Label: Extras
Origin: maemo
Suite: fremantle
Version: 2.0
MD5Sum:
d41d8cd98f00b204e9800998ecf8427e 0 free/binary-all/Packages
7b106d3d1528f3224efc46888424fc11 29 free/binary-all/Packages.gz
3ad59e5df9489cd5a6b6c36786d404bb 81 free/binary-all/Release

Re: Application manager broken
 

First one was clearly caused by this https://bugs.maemo.org/show_bug.cgi?id=8286

Other ones look the same too, but the repositories should be fixed by now.

Re: Application manager broken
 

Well.. at least I know my troubleshooting skills aren't failing me.

And his information appears to be missing certain key signatures.

ETA: Most notably,
bb8379d9be4884520ab6b2491a51c849 839659 free/binary-armel/Packages
5add5ff8ac9afc39388adef4215d9687 422870 free/binary-armel/Packages.bz2

Re: Application manager broken
 

Are you referring ot ndi's post? I don't think that he posted to whole file. At least I didn't :)

Re: Application manager broken
 

Ah.. ok then :D.

ETA: You've got this.. you evidently have more information than me at this point. I'll go sit in a corner now :)

Re: Application manager broken
 

That bug was fixed 2010-01-20 10:26:52 GMT+3. He's still having issues.

Also, happy 1000th post :P

Re: Application manager broken
 

Ok, you want full.

Architectures: armel i386 all
Components: free non-free
Date: Wed, 20 Jan 2010 20:53:11 UTC
Label: Extras
Origin: maemo
Suite: fremantle
Version: 2.0
MD5Sum:
d41d8cd98f00b204e9800998ecf8427e 0 free/binary-all/Packages
7b106d3d1528f3224efc46888424fc11 29 free/binary-all/Packages.gz
3ad59e5df9489cd5a6b6c36786d404bb 81 free/binary-all/Release
bb8379d9be4884520ab6b2491a51c849 839659 free/binary-armel/Packages
5add5ff8ac9afc39388adef4215d9687 422870 free/binary-armel/Packages.bz2
57440afa282ef506407b905974b98874 407478 free/binary-armel/Packages.gz
907a65daa765305266fdcf297876ecec 83 free/binary-armel/Release
e2e7fc4a032121edb7c3def8e2ad0393 837509 free/binary-i386/Packages
60d01118521b7beeb429eab54c159201 422572 free/binary-i386/Packages.bz2
2b08a21a6c3707f9d2f84f165da71a16 407106 free/binary-i386/Packages.gz
c009409264db49e84fe41f16a95df774 82 free/binary-i386/Release
a0b8b43e2edda93c1e407887778f4148 159612 free/source/Sources
fc3d6fd9e538743220ae2a0e9fc7af63 47043 free/source/Sources.bz2
9eeed2c1be735c3df1ecc501cefdebde 50239 free/source/Sources.gz
d41d8cd98f00b204e9800998ecf8427e 0 non-free/binary-all/Packages
7b106d3d1528f3224efc46888424fc11 29 non-free/binary-all/Packages.gz
d5ee2cbdc7004eb87a0ced62c3aae1b8 85 non-free/binary-all/Release
f2c01b84da6804130f1402f0902d9f72 48305 non-free/binary-armel/Packages
c926ebf7c36d71828a502af6f637cd12 25392 non-free/binary-armel/Packages.bz2
e4f37bd50a847ff943e1f050e3bdc5a7 21612 non-free/binary-armel/Packages.gz
fa37996871d28c18b8c9256c0ab90bf7 87 non-free/binary-armel/Release
d41d8cd98f00b204e9800998ecf8427e 0 non-free/binary-i386/Packages
4059d198768f9f8dc9372dc1c54bc3c3 14 non-free/binary-i386/Packages.bz2
0fe6769024c1aa5a9011c18e08e152a0 29 non-free/binary-i386/Packages.gz
37334e5012bed712af985b36d72b445d 86 non-free/binary-i386/Release
d41d8cd98f00b204e9800998ecf8427e 0 non-free/source/Sources
4059d198768f9f8dc9372dc1c54bc3c3 14 non-free/source/Sources.bz2
4a4dd3598707603b3f76a2378a4504aa 20 non-free/source/Sources.gz


Then the SHA1 and then other stuff. If you want full, I'd better zip and upload?

Re: Application manager broken
 

First two are OK (I don't have extras-testing, BTW).

But last one is a garbage -

System error
error: Error during compilation of /var/www/dhandler:
syntax error at /var/www/dhandler line 95, near "!=="
Global symbol "$subr" requires explicit package name at /var/www/dhandler line 114.
Global symbol "$subr" requires explicit package name at /var/www/dhandler line 114.
Global symbol "$subr" requires explicit package name at /var/www/dhandler line 120.
syntax error at /var/www/dhandler line 133, near "} elsif"
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 134.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 136.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 138.
Global symbol "$a_uri" requires explicit package name at /var/www/dhandler line 140.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 141.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 142.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 143.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 145.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 147.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 149.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 152.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 153.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 154.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 155.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 156.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 156.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 157.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 159.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 160.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 161.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 162.
Global symbol "$uri" requires explicit package name at /var/www/dhandler line 166.
Global symbol "%settings" requires explicit package name at /var/www/dhandler line 170.
Global symbol "$a_uri" requires explicit package name at /var/www/dhandler line 170.
syntax error at /var/www/dhandler line 173, near "}"
/var/www/dhandler has too many errors.
context:
...
91: # debug log
92: # $m->comp('log.comp', s=>"$settings{root}/$uri, subr->status:" . $subr->status . ":". $subr->content_type);
93: $settings{debug} && $m->comp('log.comp', s=> "Last-Modified: $lastmodified / $uri" );
94:
95: if ($subr->status !== 200 || $subr->status !== 401) {
96: $m->comp('log.comp', s=>"****: $settings{root}/$uri, subr->status:" . $subr->status . ":". $subr->content_type);
97: return 404;
98: }
99:
...
110: } elsif ($uri =~ '(Packages|Packages\.gz|Packages\.bz2|Sources|Sour ces\.gz|Sources\.bz2|Release|Release\.gpg)$') {
111: $r->headers_out->add('Cache-Control' => 'no-cache, no-store');
112: }
113:
114: $r->content_type($subr->content_type) if $subr->content_type;
115: # no need to send headers, the previous line does it all
116: # $r->send_http_header;
117:
118: return 200 if $r->header_only;
119:

... but apt-get works...

EDIT line numbers 95, 114, 120 133-136 etc are in red color.

Re: Application manager broken
 

This one is broken for me:
It starts with
and so apt-get update fails with a BADSIG error. :(

Re: Application manager broken
 

It's always possible that some akamai servers are not updated. If people in the other threads are not manually refreshing their application manager they could still be affected since AM refreshesh itself once per day.

Re: Application manager broken
 

Error near !==? I think we are getting nearer :P

Re: Application manager broken
 

Actually extras-devel is garbage for me too. I think that this is your problem. Enable extras-testing so HAM will work at least mostly

Re: Application manager broken
 

You puzzled me.

How the freq of AM refreshing have deal with it? It is matter of time or page configuration (Time-To-Live).

I never had a problem with akamai caching - it caches only cacheable pages and only until it is expired. (Yes, I suspect there is a minimum live time, but that is minutes)

And the main question - why apt-get works?

EDIT: it is definitely works because I just checked the existence of gstreamer0.10-mkv - it was put just yesterday at night.

Re: Application manager broken
 

Attached extras-devel snapshot.

Warning1: First line manually edited

Warning2: Line ends are Windows so I can visually check against the browser. Can convert if needed.

Re: Application manager broken
 

I don't think it is needed. I never enabled extras-testing and it worked.

And that are separate repositories.

Re: Application manager broken
 

I think he means other people are affected even if they didn't hit update manually, since it does it by itself.

And, most likely because the AM never uses apt-get but uses the apt libraries and rewrote some of the code - code that is different enough to crash - maybe some off GET request or some parameters like including the software version.

Is TCPDump available? :)

Re: Application manager broken
 

Because extras-devel is broken for HAM, nothing in there shows up. If you enable extras-testing you will get more apps until extras-devel is fixed. Wasn't more apps what you wanted for?

Re: Application manager broken
 

You puzzle me too - the text which I posted was from browser and has nothing with apt-get.

Moreover, I just used

wget ...(3rd file URL)...

And looked into Release file - it is WRONG.

Re: Application manager broken
 

HAM won't show the apps until it downloads (refreshesh) new (fixed) files from repositories. Since HAM downloads Relese and other files only once a day it could take one day until fix is visible to users

Re: Application manager broken
 

apt-get downloads the same file....

Re: Application manager broken
 

Actually, I have two issues here now:

1. What is going on (I may wait until it is fixed if somebody works on it).

2. I need some packages from extras-devel, and I can get it via apt-get. And my issue (2) is - why I can get it via apt-get? (
gstreamer0.10-mkv)

Re: Application manager broken
 

How it gets the yesterday night submission which never exists before yesterday? (Please take into account that issue is at least a couple of days).

Re: Application manager broken
 

Extras-devel is broken (I reported it, hopefully it's fixed tomorrow)

Re: Application manager broken
 

I have no idea what you mean

Re: Application manager broken
 

apt-get update's the repository when you tell it to. AM gets it once a day. I'm not sure if refreshing in HAM actually "refreshes" the files.

Egoshin: apt-cache search gstreamer

Anything that shows up should be installable.

ETA: I guess unless they are from extras-devel.. which mikkov says is broken :D.

Re: Application manager broken
 

I don't know why, but that was funny. Puzzled 2 - the sequel. (it's 3:15 AM here in Romania. And I work tomorrow).

Precisely. Browser gets it wrong, HAM gets it wrong, but apparently apt-get gets it right.

It stands to reason that since HAM fails, it's wrong. It also stands to reason that apt-get gets it right, so I'm guessing that something HAM does trigger the bug.

Beyond this point, I simply speculated that HAM adds something or removes something from the request that breaks the server. Furthermore, since it's not identical, it's safe to assume HAM is not a front end for apt-get, but simply uses apt libraries and has its own GET method.

It's also possible that though different both HAM and apt-get issue valid if different requests but the US server cored/is bad/does localized processing if it's unique.