![]() |
Re: [N900] Yes, another hildon-home bug thread...
Quote:
Quote:
But I could not identify any of them to cause an infinite block ... Nevertheless I had a bit of confusion in DCEW config. I had a command on desktop, which did not belong there. And DCEW named it as "IP", but could not locate the command (when checking the executed commands of all my widgets). But, again, this was one of the standard commands. |
Re: [N900] Yes, another hildon-home bug thread...
And thanks to all of you trying to help/identify this phenomenon !!
|
Re: [N900] Yes, another hildon-home bug thread...
Quote:
Normal applications, contacts, links, etc. still work even with this "hanging". How did you recover? Reboot? |
Re: [N900] Yes, another hildon-home bug thread...
Besides contacts and shortcuts, I have:
- 8 instances of ConnectNow widget - 2 QBW snippet widgets - 1 Personal IP Monitor widget On other desktops: - 1 Calendar Home widget - 4 Internet Radio Player widgets Yes i did a reboot. |
Re: [N900] Yes, another hildon-home bug thread...
New information!
It seems like wget is the culprit here (or Maemo itself). I had that command [code] [code] under suspicion, but no proove. But now I am sure: I chnged WLAN connectivity and at the same time fired that command in x-term. One time it did hang completely, there was no output. And the command did not end. This is the reason why h-h cannot end that command, as nothing is writte to stdout and it does not return. There was no running instance of wget anymore neither of awk, so I do not understand that situation very well. But that prooves that it is not a bug of h-h, but a bug inside Maemo itself (or really wget?) caused by "bad" (better: not perfect) implementation of dcew (as I would have done same way, relying on output/ending of a simple command line). Any ideas/suggestions? I still have that command line Quote:
P.S.: a second call in a second x-term terminated immediately with no ouput and after connecting agaian it terminetd after 2 seconds with correct IP shown |
Re: [N900] Yes, another hildon-home bug thread...
@peterleinchen,
Can I assume that you don't have the real wget installed, but are using busybox wget? If so, busybox wget doesn't support, among others, the -t and -T options, but inconveniently chooses not to mention that fact. Probably busybox wget is either buggy, or waits indefinetly for a reply, or both. Try to install the real wget and make sure wget is not the same as busybox wget. Hopefully this will solve your problem! |
Re: [N900] Yes, another hildon-home bug thread...
Hi reinob,
thanks for your input. Of course I am using bb-power, but also have lots of "real" programs installed ;) Quote:
Open for any other input :) --edit But -possibly- maybe it is really busybox-power's fault (/bin/sh). So I post here output of Quote:
??? |
Re: [N900] Yes, another hildon-home bug thread...
Anybody ou there experiencing the same problem, please give some feedback!
Are you using busybox-power or stock busybox shell? I would like to give iDont (big THX for looking into it to him) an all-clear in case anybody experienced this with stock sh, too. Once again: the command Code:
wget -t 2 -T 3 -q -O - checkip.dyndns.com | awk -F ": " '{print $2}' | awk -F "</" '{print $1}' I do not think it was caused by wget or awk as both programs did not have an instance running anymore. Unfortunately my shell is now gone, as I had an umexpected reboot ... |
Re: [N900] Yes, another hildon-home bug thread...
Quote:
Code:
sh: wget: not found |
Re: [N900] Yes, another hildon-home bug thread...
Quote:
There is no wget in stock sh, but wget is available from the repo and listed as dependency in a lot of apps. And, to be sure, you did not suffer from h-h getting stalled? At least this bug (no output from sh command, hereby h-h getting stalled) does not need to be caused by wget, but could be from stock (bb-power) sh or Maemo system itself. |
All times are GMT. The time now is 17:15. |
vBulletin® Version 3.8.8