Author Topic: [SOLVED] LMCE within VMPlayer - Orbiter ocasionaly turns black / non responsive  (Read 756 times)

Avner

  • Veteran
  • ***
  • Posts: 76
    • View Profile
Hello,

I am trying to set up LinuxMce as a guest inside Windows Vista host using vmware player.
I did the following:
* Downloaded and installed LinuxMCE-8.10-final
* Followed the instructions in: http://wiki.linuxmce.org/index.php/Installing_0810 (section Internet Instalation):
Code: [Select]
  Edited the file /etc/apt/sources.list to point to the new location for interpid packages.
   sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
   apt-get update
   sudo apt-get dist-upgrade
   apt-get install medibuntu-keyring
   wget -c http://deb.linuxmce.org/ubuntu/new-installer-latest.tar.gz
   tar xvf new-installer-latest.tar.gz
   cd new-installer
   ./pre-install-from-repo.sh
   ./mce-install.sh
   ./post-install.sh
   reboot

I had to resort to vmware player version 4.0.1 as the newer version 4.0.2 had problems to install VmwareTools

The problem I'm having is:
* Orbiter stops responding after a short while and shows as black rectangle
* In addition, the aother two windows: pluto-xine-playback-window and picture-viewer are always black

Any of the following actions did not resolve the problem:
* Quick regenration of Orbiter
* Full regenration of Orbiter
* Restart Router
* reboot

After reboot lmce automatically detects and runs the a list of scripts such as:
Code: [Select]
99_WaveTrend_RFID.sh
99_VidikronTV.sh
99_Runco_VX2c.sh
99_RuncoTV.sh
99_PioneerPlasma.sh
99_PLCBUS_1141.sh
88_InsteonPLM.sh
85_PioneerKuro.sh
80_GatewayPlasma.sh
60_ApexAlarmPanel.sh
40_Oppo.sh
40_Mitsubishi_Plasma.sh
30_JVC.sh
20_kwikwai.sh
20_rain8net.sh
20_YamahaReceiver.sh
20_SharpTV.sh
20_PioneerReceiver.sh
20_OnkyoReceiver.sh
20_OleviaTV_ATI.sh
20_NAD_Receiver.sh
20_MarantzReceiver.sh
20_LG_TV.sh
20_DenonReceiver.sh
Spawn_serialports_18826.log

Looking in the log files I noticed the following errors in /var/log/pluto/DCERouter.log:

Code: [Select]
...
05 02/12/12 14:01:35.011 [33;1mThe target device 20 (routed to 20) has not registered. [0m <0xb669ab90>
...
05 02/12/12 13:58:17.237 [33;1mThe target device 21 (routed to 21) has not registered. [0m <0xb669ab90>
...
05 02/12/12 13:58:32.166 [33;1mThe target device 30 (routed to 30) has not registered. [0m <0xb669ab90>
...

I don't know what triggers the above scripts and how to stop them from running automatically after reboot.
I think they are related to the problem as they invoke commands to device 20, which is the source of the problem in a similar problem in http://forum.linuxmce.org/index.php?topic=10694.0


Regards,
Avner
« Last Edit: February 18, 2012, 08:29:37 am by Avner »
Asus P5GD2-X, Intel i915P/G, Pentium 4 3.2 GHz, 2.5GB, nvidia Geforce 8800, Hauppauge WinTV-HVR-1850

Avner

  • Veteran
  • ***
  • Posts: 76
    • View Profile
I read a bit more about the plug and play Plug-in. When it detects a new device it attempt to determine what device template is on the path
(http://wiki.linuxmce.org/index.php/Plug%26play). So assuming that there is a new device that is not recognized the plug and play Plug-in would launch multiple scripts for all possible device templates. Assuming that this is a transitory process the list of Spawn_PNP Detection scripts could probably be ignored.

I haven't touched the orbiter for a day. After a day it still appears black. The latest log information from DCERouter.log and the list of Span processes that are in the system are attached below.
Could this information explain the condition for the black non responsive orbiter?
Note that the system load is low (observed in top) and other OS components (e.g. konsole terminal in KDE desktop) are responsive.


Thanks,
Avner

------------------------------

Latest log information from DCERouter.log:

Code: [Select]
05 02/14/12 7:48:26.350 Router::RemoveAndDeleteSocket 0x8f40bd8 -1003 <0x71949b90>
05 02/14/12 17:29:13.030 void ClientSocket::Disconnect() on this socket: 0x8f40c18 (m_Socket: 156) <0xa61ccb90>
07 02/14/12 17:29:13.033 Received Message from 12 (Event Plug-in / Bedroom (Master)) to -1001 (unknown / ), type 2 id 52 Event:Sunset, retry none, parameters: <0xa61ccb90>
05 02/14/12 17:29:13.035 Socket::ReceiveData 0x8f41b08 failed, bytes left 0 start: 3030000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 157 Incoming_Conn Socket 157 127.0.0.1 <0x71949b90>
05 02/14/12 17:29:13.035 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 157 127.0.0.1 <0x71949b90>
05 02/14/12 17:29:13.035 TCPIP: Closing connection to -1003 (Router Dev #0) 0x8f41b08 m_Socket: -1 <0x71949b90>
05 02/14/12 17:29:13.035 Router::RemoveAndDeleteSocket 0x8f41b08 -1003 <0x71949b90>

------------------------------

The list of Span processes that are in the system

Code: [Select]
dcerouter_1025897:~# ps aux | grep -i spawn
root     15376  0.0  0.0   3132  1200 ?        Ss   Feb12   0:01 SCREEN -d -m -h 3000 -S SimplePhone_22 /bin/bash -x Spawn_Device.sh 22 127.0.0.1 SimplePhone
root     15378  0.0  0.0   2876  1448 pts/18   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 22 127.0.0.1 SimplePhone
root     15379  0.0  0.0   3132  1204 ?        Ss   Feb12   0:00 SCREEN -d -m -h 3000 -S Xine_Player_23 /bin/bash -x Spawn_Device.sh 23 127.0.0.1 Xine_Player
root     15382  0.0  0.0   2876  1448 pts/19   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 23 127.0.0.1 Xine_Player
root     15384  0.0  0.0   3132  1200 ?        Ss   Feb12   0:00 SCREEN -d -m -h 3000 -S LaunchPhoto_Screen_Saver.sh_25 /bin/bash -x Spawn_Device.sh 25 127.0.0.1 LaunchPhoto_Screen_Saver.sh
root     15388  0.0  0.0   2880  1448 pts/20   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 25 127.0.0.1 LaunchPhoto_Screen_Saver.sh
root     15394  0.0  0.0   3132  1204 ?        Ss   Feb12   0:00 SCREEN -d -m -h 3000 -S MPlayer_Player_26 /bin/bash -x Spawn_Device.sh 26 127.0.0.1 MPlayer_Player
root     15397  0.0  0.0   2876  1448 pts/21   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 26 127.0.0.1 MPlayer_Player
root     15398  0.0  0.0   3132  1208 ?        Ss   Feb12   0:00 SCREEN -d -m -h 3000 -S Picture_Viewer_27 /bin/bash -x Spawn_Device.sh 27 127.0.0.1 Picture_Viewer
root     15405  0.0  0.0   2880  1448 pts/22   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 27 127.0.0.1 Picture_Viewer
root     15413  0.0  0.0   3132  1204 ?        Ss   Feb12   0:00 SCREEN -d -m -h 3000 -S MythTV_Player_41 /bin/bash -x Spawn_Device.sh 41 127.0.0.1 MythTV_Player
root     15415  0.0  0.0   2876  1448 pts/23   Ss+  Feb12   0:00 /bin/bash -x Spawn_Device.sh 41 127.0.0.1 MythTV_Player
root     15528  0.0  0.0   3000   992 ?        Ss   Feb12   0:00 SCREEN -d -m -S DCERouter /usr/pluto/bin/Spawn_DCERouter.sh
root     15529  0.0  0.0   2856  1428 pts/9    Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_DCERouter.sh
root     16035  0.0  0.0   3000   992 ?        Ss   Feb12   0:00 /usr/bin/SCREEN -d -m -S App_Server15 /usr/pluto/bin/Spawn_Device.sh 15 localhost App_Server
root     16036  0.0  0.0   2876  1448 pts/11   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 15 localhost App_Server
root     16157  0.0  0.0   3000   996 ?        Ss   Feb12   0:00 /usr/bin/SCREEN -d -m -S HAL16 /usr/pluto/bin/Spawn_Device.sh 16 localhost HAL
root     16158  0.0  0.0   2876  1448 pts/13   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 16 localhost HAL
root     16281  0.0  0.0   3000   996 ?        Ss   Feb12   0:00 /usr/bin/SCREEN -d -m -S Disk_Drive29 /usr/pluto/bin/Spawn_Device.sh 29 localhost Disk_Drive
root     16282  0.0  0.0   2876  1448 pts/14   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 29 localhost Disk_Drive
root     16782  0.0  0.0   3000  1000 ?        Ss   Feb12   0:00 /usr/bin/SCREEN -d -m -S External_Media_Identifier30 /usr/pluto/bin/Spawn_Device.sh 30 localhost External_Media_Identifier
root     16783  0.0  0.0   2876  1444 pts/15   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 30 localhost External_Media_Identifier
root     16875  0.0  0.0   3000   996 ?        Ss   Feb12   0:00 /usr/bin/SCREEN -d -m -S Disk_Drive31 /usr/pluto/bin/Spawn_Device.sh 31 localhost Disk_Drive
root     16876  0.0  0.0   2876  1444 pts/16   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 31 localhost Disk_Drive
root     17167  0.0  0.0   3000   992 ?        Ss   Feb12   0:11 /usr/bin/SCREEN -d -m -S OnScreen_Orbiter21 /usr/pluto/bin/Spawn_Device.sh 21 localhost LaunchOrbiter.sh
root     17168  0.0  0.0   2876  1452 pts/17   Ss+  Feb12   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 21 localhost LaunchOrbiter.sh
Asus P5GD2-X, Intel i915P/G, Pentium 4 3.2 GHz, 2.5GB, nvidia Geforce 8800, Hauppauge WinTV-HVR-1850

Avner

  • Veteran
  • ***
  • Posts: 76
    • View Profile
I found an ugly solution but it works for me.
Occasionally, when Orbiter becomes non responsive (completely black or simply does not show up) I open a console (either from a KDE session or from e.g. tty2) and apply
Code: [Select]
sudo killall -9 OrbiterA new orbiter is kicked in after few seconds.
When X is lost (e.g. after moving to tty2 (Alt-Cntrl-F2) and closing the VM), X can be restored by going to e.g. tty2 and typing:
Code: [Select]
sudo su -
/usr/pluto/bin/Start_X_Wrapper.sh
The orbiter regenerates (progress green line at the bottom of the screen) and orbiter shows up

Hopefuly this will help the next person who tackles this problem.
Avner
Asus P5GD2-X, Intel i915P/G, Pentium 4 3.2 GHz, 2.5GB, nvidia Geforce 8800, Hauppauge WinTV-HVR-1850