|
davegravy
|
 |
« on: July 06, 2010, 05:15:52 pm » |
|
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one. The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached) The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user). Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help. 05 07/06/10 12:08:34.506 [33;1mGot a reload command from 0 [0m <0xb3d8bb90>
05 07/06/10 12:08:37.982 [33;1mDropping all sockets...[0m <0xb4f286f0>
05 07/06/10 12:08:37.982 [33;1mDone dropping sockets
Logged
|
|
|
|
|
totallymaxed
|
 |
« Reply #1 on: July 06, 2010, 06:02:12 pm » |
|
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one. The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached) The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user). Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help. 05 07/06/10 12:08:34.506 [33;1mGot a reload command from 0 [0m <0xb3d8bb90>
05 07/06/10 12:08:37.982 [33;1mDropping all sockets...[0m <0xb4f286f0>
05 07/06/10 12:08:37.982 [33;1mDone dropping sockets
Posts: 183
Linux and LinuxMCE witchdoctor
|
|
« Reply #2 on: July 06, 2010, 06:25:57 pm » |
|
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one.
The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached)
The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user).
Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help.
Personally I don't like this message: "Could not find text object: 670". Try a full regen (not a quick one). The "device kills connection immediately" symptom is actually alright, since the web page connects, does its thing and disconnects. Once a second you should see a "ANYNEWS?" message in the logs, because the web page checks for updates every second, and if you don't, it means the Proxy_Orbiter lacks a change (but this change would only prevent automatic refreshes from working, the rest of the web orbiter should work just fine regardless). |
|
|
|
|
Logged
|
|
|
|
uplink
Administrator
Guru
Posts: 183
Linux and LinuxMCE witchdoctor
|
|
« Reply #3 on: July 06, 2010, 06:30:10 pm » |
|
I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)
Actually, I didn't upload the beach ball cursor to LinuxMCE  You still get SuperTux. I'll put it in LinuxMCE SVN now, but leave it disabled until a switch is made for selecting one or the other (some people like SuperTux  ). |
|
|
|
|
Logged
|
|
|
|
uplink
Administrator
Guru
Posts: 183
Linux and LinuxMCE witchdoctor
|
|
« Reply #4 on: July 06, 2010, 06:43:09 pm » |
|
Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.
|
|
|
|
|
Logged
|
|
|
|
|
davegravy
|
|
« Reply #5 on: July 06, 2010, 07:17:47 pm » |
|
Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.
Tried Chrome and the behaviour is a bit different (though still broken). Instead of the SuperTux persisting after the first button-push, it disappears after a couple seconds and is replaced by a blank (black) screen. The only exception to this is the "Active Calls" button which yields the attached image. |
|
|
|
|
Logged
|
|
|
|
uplink
Administrator
Guru
Posts: 183
Linux and LinuxMCE witchdoctor
|
|
« Reply #6 on: July 06, 2010, 07:47:08 pm » |
|
OK, that rules in a Javascript issue with Internet Explorer. I don't have it, so I never tested it. The other screens seem to be botched regens.
SuperTux appears before an AJAX request is sent with a command and to load the resulting image, and then it disappears. Somewhere the AJAX request dies on Internet Explorer.
|
|
|
|
|
Logged
|
|
|
|
|
totallymaxed
|
|
« Reply #7 on: July 06, 2010, 08:34:04 pm » |
|
I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)
Actually, I didn't upload the beach ball cursor to LinuxMCE You still get SuperTux. I'll put it in LinuxMCE SVN now, but leave it disabled until a switch is made for selecting one or the other (some people like SuperTux ). Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor. Andrew |
|
|
|
|
Logged
|
|
|
|
|
posde
|
|
« Reply #8 on: July 06, 2010, 10:57:06 pm » |
|
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.
SSHHHH, don't tell them. They will replace it with a waving Windows flag |
|
|
|
|
Logged
|
|
|
|
|
totallymaxed
|
|
« Reply #9 on: July 06, 2010, 11:44:19 pm » |
|
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.
SSHHHH, don't tell them. They will replace it with a waving Windows flag :-) |
|
|
|
|
Logged
|
|
|
|
uplink
Administrator
Guru
Posts: 183
Linux and LinuxMCE witchdoctor
|
|
« Reply #10 on: July 07, 2010, 12:07:28 am » |
|
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.
SSHHHH, don't tell them. They will replace it with a waving Windows flag Or an Apple... err... apple |
|
|
|
|
Logged
|
|
|
|
|
Riggs
|
|
« Reply #11 on: July 07, 2010, 02:44:08 am » |
|
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation
However if i click on any of may cams there is no picture at all
|
|
|
|
|
Logged
|
Dell XPS Gen5 P4 3.2Ghz 64 x2, 3Gbs Ram, GeForce 8600GT 1Gb VRam, Creative Audigy 2 ZS, LinuxMCE 10.04 32bit,, 2 Eth Cards, Comcast business 25Mbs/5Mbs. Zwave, X10, Vera 3.
|
|
|
|
fastie81
|
|
« Reply #12 on: July 07, 2010, 07:25:55 am » |
|
hey
Where did you get the documentation?
I have been looking on the Wiki and nothing..
Please let me know.
Fastie
|
|
|
|
|
Logged
|
|
|
|
|
Kooma
|
|
« Reply #13 on: July 07, 2010, 07:32:15 am » |
|
|
|
|
|
|
Logged
|
|
|
|
|
totallymaxed
|
|
« Reply #14 on: July 07, 2010, 08:14:21 am » |
|
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation
However if i click on any of may cams there is no picture at all
Are you using motion cams? ie are you using the motion package to do motion detection on your cams? Andrew |
|
|
|
|
Logged
|
|
|
|
|
