Nokia N800 orbiter reloads itself after selecting TV

[purps]

When I select TV (doesn't seem to do it with any other button presses), my N800 orbiter craps out, as if it is reloading. Sometimes it won't crap out, but then it will usually do it later when selecting a channel.

I've been battling with this for a while now over various snapshots installs/upgrades, so it's nothing that I've done I don't think. None of my other orbiters (web orbiters and onscreen orbiters) have this problem.

Any clues as to what may be causing these issues? I've tried reloading/regenning/rebooting, removing and reinstalling, and as I said this is over various installs as well, so I have no idea what to try next.

Cheers,
Matt.

EDIT: It is now officially unusable, it does it every single time. Once it reloads (TV still on), I press the "now playing" scenario on the home page, and it flakes out again.

[purps]

This is an extract from the general info log when the orbiter fails, does it give any clues?

Code: [Select]

08 09/03/11 22:41:18.794 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:18.794   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5177.png <0x59eefb90>
08 09/03/11 22:41:18.962 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:18.962   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5174.png <0x59eefb90>
08 09/03/11 22:41:19.125 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.125   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5171.png <0x59eefb90>
08 09/03/11 22:41:19.231 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.231   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5168.png <0x59eefb90>
08 09/03/11 22:41:19.359 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.359   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5165.png <0x59eefb90>
08 09/03/11 22:41:19.506 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.506   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5162.png <0x59eefb90>
08 09/03/11 22:41:19.628 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.628   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5159.png <0x59eefb90>
08 09/03/11 22:41:19.743 Received Message from 40 (Nokia N800 Living Room / Living Room) to 4 (General Info Plug-in / Cupboard), type 1 id 71 Command:Request File, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.743   Parameter 13(Filename): orbiter/C40/5672.0.0.5660.5156.png <0x59eefb90>
08 09/03/11 22:41:19.909 Received Message from 40 (Nokia N800 Living Room / Living Room) to 9 (Orbiter Plug-in / Cupboard), type 1 id 255 Command:Orbiter Registered, retry none, parameters: <0x59eefb90>
08 09/03/11 22:41:19.909   Parameter 8(On/Off): 0 <0x59eefb90>
08 09/03/11 22:41:19.909   Parameter 17(PK_Users): 0 <0x59eefb90>
08 09/03/11 22:41:19.909   Parameter 45(PK_EntertainArea):  <0x59eefb90>
08 09/03/11 22:41:19.909   Parameter 57(PK_Room): 0 <0x59eefb90>
05 09/03/11 22:41:21.449 Socket::ReceiveData 0x8f9c2fa0 failed, bytes left 0 start: 321000000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 96 Incoming_Conn Socket 96 192.168.80.150EVENT 40 T=8 Event #40 <0x596eeb90>
05 09/03/11 22:41:21.449 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 96 192.168.80.150EVENT 40 T=8 Event #40 <0x596eeb90>
05 09/03/11 22:41:21.449 TCPIP: Closing connection to 40 (Router Dev #0) 0x8f9c2fa0 m_Socket: -1 <0x596eeb90>
05 09/03/11 22:41:21.449 Router::RemoveAndDeleteSocket 0x8f9c2fa0 40 <0x596eeb90>
05 09/03/11 22:41:21.449 Socket::ReceiveData 0x585009b8 failed, bytes left 0 start: 322250000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 202 Incoming_Conn Socket 202 192.168.80.150EVENT 40 T=8 Event #40 <0x59eefb90>
05 09/03/11 22:41:21.449 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 202 192.168.80.150EVENT 40 T=8 Event #40 <0x59eefb90>
05 09/03/11 22:41:21.449 TCPIP: Closing connection to 40 (Router Dev #0) 0x585009b8 m_Socket: -1 <0x59eefb90>
05 09/03/11 22:41:21.449 Router::RemoveAndDeleteSocket 0x585009b8 40 <0x59eefb90>

[phenigma]

Someone can correct me if I am wrong but... This is because the new TV screens require a rebuild of the orbiter to work properly and that hasn't been done on the Maemo builds since the TV screens were added almost 2 years ago now (I think).

Here is an updated Maemo n800/n810 orbiter, with dependencies, that you can try out to see if it fixes your issues, you can always revert to the old version if you have problems:

http://www.4shared.com/file/Yla70F_X/lmceorbiter-diablo-0810tar.html

On your n800 you will need to get to the command prompt, get root access and un-tar the archive and install the .deb files with dpkg.

Code: [Select]

mkdir work
cd work
tar xvf ../lmceorbiter-diablo-0810.tar.gz
dpkg -i *.deb

You may need to do an 'apt-get -f install'

If you can't access the DL link I can post it elsewhere. 

The only bug I can see is that it is not automatically restarting if it crashes, I havn't even looked into that yet but I think that niteman must have newer source than what is currently is svn.

I have a new n900 build as well, if anyone is having the same issues, just havn't tested it yet.

J.

[coley]

There was a new N900 install built and there is an install.fremantle available on svn reflecting its new home http://deb.linuxmce.org/maemo.
Maybe you can arrange with posde to get your new deb uploaded to the diablo distro dir and the appropriate install file updated.

-Coley.

[phenigma]

Thanks Coley, I wasn't aware of the n900 build hosted by the community, I'll check it out.

If the screens work for purps then I'll talk to posde, I'm not using lmce for television currently.  I'd also like to see if niteman has a more recent source for the maemo wrapper than is in the lmce svn.

J.

[purps]

Someone can correct me if I am wrong but... This is because the new TV screens require a rebuild of the orbiter to work properly and that hasn't been done on the Maemo builds since the TV screens were added almost 2 years ago now (I think).

Here is an updated Maemo n800/n810 orbiter, with dependencies, that you can try out to see if it fixes your issues, you can always revert to the old version if you have problems:

http://www.4shared.com/file/Yla70F_X/lmceorbiter-diablo-0810tar.html

On your n800 you will need to get to the command prompt, get root access and un-tar the archive and install the .deb files with dpkg.

Code: [Select]

mkdir work
cd work
tar xvf ../lmceorbiter-diablo-0810.tar.gz
dpkg -i *.deb

You may need to do an 'apt-get -f install'

If you can't access the DL link I can post it elsewhere. 

The only bug I can see is that it is not automatically restarting if it crashes, I havn't even looked into that yet but I think that niteman must have newer source than what is currently is svn.

I have a new n900 build as well, if anyone is having the same issues, just havn't tested it yet.

J.

Thanks for the reply.

Silly question number 1: How do I actually launch it once the debs are installed? Am I supposed to be launching an installer, or the app itself at this stage?

Cheers,
Matt.

[phenigma]

Not silly at all!  Great question.

It launches from the same icon you currently use to launch the diablo orbiter in maemo.  I use the same icon to launch this build as the 0710 lmceorbiter that I have always used.  It's built from the source that is in svn at svn.linuxmce.org with a few updates for new dependencies and fixes for building.

The installer .deb deals deals only with the installation, installing the fonts that orbiter requires and the orbiter package itself.  The installer is a simply a repackaged version of the one niteman created, hosted at http://diapub.com/~michael/repository/dists/diablo/free/binary-armel/, but it is updated to depend on this newer build.  After the .debs are installed you should have an icon available for lmceorbiter, the same as you do now.

J.

[purps]

Not silly at all!  Great question.

It launches from the same icon you currently use to launch the diablo orbiter in maemo.  I use the same icon to launch this build as the 0710 lmceorbiter that I have always used.  It's built from the source that is in svn at svn.linuxmce.org with a few updates for new dependencies and fixes for building.

The installer .deb deals deals only with the installation, installing the fonts that orbiter requires and the orbiter package itself.  The installer is a simply a repackaged version of the one niteman created, hosted at http://diapub.com/~michael/repository/dists/diablo/free/binary-armel/, but it is updated to depend on this newer build.  After the .debs are installed you should have an icon available for lmceorbiter, the same as you do now.

J.

Sorry, I should have mentioned in my last post, there is no icon, hence my struggle. It should be in "Extras" right? That's where the last one was anyway. The launch icon from before disappeared when I uninstalled the previous orbiter software.

Oh poopies, was I supposed to install the debs with the original orbiter in place?

Cheers,
Matt.

[phenigma]

Either way, the new .debs will replace the old version when you install it.  The new .debs are the same as the old, just new orbiter build.   

You should be able to add the icon through the regular menu editing on the n800, the icon is added to it.  Otherwise you should be able to launch it from the command line with /usr/bin/linuxmceorbiter, but the icon should be installed with the new .debs just like the old one.

J.

[purps]

Right-o. It turns out my initial silly question was a bit premature - I didn't appreciate there had been an installation problem during the very quick look I had at this last night (hence no icon, duh).

The installation of the debs falls over when it comes to the unmet dependency of mysql-common (wrong version), leaving "libmysqlclient15off", "lmceorbiter-os2008" and "lmce-orbiter-installer" unconfigured. Doing an apt-get -f install just removes these three things.

Am I right in saying I need to get that mysql-common sorted out before I can proceed?

Cheers,
Matt.

EDIT: I tried to install the deb from here http://maemo.org/packages/package_instance/view/diablo_extras-devel_free_armel/mysql-common/5.0.32-7etch6maemo1/ but I got the following...

Code: [Select]

/home/user # dpkg -i mysql-common_5.0.32-7etch6maemo1_all.deb

(Reading database ... 14620 files and directories currently installed.)
Preparing to replace mysql-common 4.0.24-10sarge2 (using mysql-common_5.0.32-7etch6maemo1_all.deb) ...
/var/lib/dpkg/tmp.ci/preinst: line 33: syntax error: Bad substitution
dpkg: error processing mysql-common_5.0.32-7etch6maemo1_all.deb (--install):
 subprocess pre-installation script returned error exit status 2
dpkg (subprocess): unable to execute new post-removal script: No such file or directory
dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
 mysql-common_5.0.32-7etch6maemo1_all.deb


[phenigma]

There is a problem with the extras-devel build of mysql common.  It depends on bash, but the package doesn't know that... and bash is not installed by default on the n800.  I have removed the bash requirements of the install/remove scripts and have a rebuild of mysql-common without the errors from the maemo repository...

Looks like I forgot to include it in the tarball...  I apologize profusely for that.  Here is a link to just the mysql-common .deb:

http://www.4shared.com/file/mAZpWRHW/mysql-common_5032-7etch6maemo1.html Included in the original tarball now.

That should fix you up.  Again I am sorry for missing that .deb in the archive.

J.

[purps]

Firstly, absolutely no apology necessary, your help is very much appreciated.

Secondly, and this is REALLY embarrassing, but my computer-illiterate girlfriend came home and just "clicked on the icon and it loaded" and she was using it when I got home. The last time I looked at it (last night), I was staring blankly at the error above, and that was where I left it - I assume that my attempt in installing mysql-common_5.0.32-7etch6maemo1_all did something positive? I dunno.

Anyway, it seems to be working well, no problems with TV yet, and I'm not expecting any, it all seems more responsive. I will uninstall it though and try these new debs. Thanks again, very kind of you to help with this.

Cheers,
Matt.

[purps]

I can confirm that installing all the debs together in one go works as it should. I did not have to run apt-get -f install, but maybe that was because I have already done it once before? In fact I have another N800 which is stock, I can always try it on that.

Everything still seems to be working as it should, I can't tell you what a relief it is to have this working properly again.

Can I help in any way to get this documented?

Cheers,
Matt.

[phenigma]

I noticed that it is a little more responsive as well.  I'm really glad it is working for you.

Ideally this would go into the repository.  I'll see about submitting a complete tarball to svn.

J.

[purps]

Tried it on my other N800, and it installed fine with that extra deb. Proper job.

I see what you mean about it not automatically restarting upon a crash though, that's a bit of a bummer.

Cheers,
Matt.