LinuxMCE Forums

General => Installation issues => Topic started by: pigdog on September 06, 2009, 02:50:24 am

Title: Solved - This orbiter will be closed message.
Post by: pigdog on September 06, 2009, 02:50:24 am: Hi,

After everything seemed to update correctly I rebooted.

On startup I am getting an OK screen (after flicker screen view) that states

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

Then...grey screen of death. Cursor moves.

Did a <CTRL/ALT>F1 or F2 then back to F7 kinda got main menu back, left/right mouse clicks - no flicker screens.

Used main menu to kinda get to KDE desktop but was part successful then lost everything but OrbiterGL screen on status bar.

Managed to get console window working.

Played around going back to orbiter but things really screwed up trying quick reload.

Got,

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

...messages.

Did a Quick Regen this Orbiter. Things seemed to settle down.

Did complete cold boot. Power off PSU. Power up.

Same black OK screen...

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

...was generated.

Then grey screen of death. Did <Ctrl/ALT> F1 Hit return for login prompt.

<CTRL/ALT> F7 main menu screen "no flicker photo background".

Main menu> Advanced> Regen this Orbiter get "Stage 1 of 2" messages.

Flicker photo background appears.

Main Menu> KDE Desktop works O.K.

Webadmin via Konqueror works.

Haven't tried MD's yet.

Is it only me?
Title: Re: This orbiter will be closed message.
Post by: fido on September 06, 2009, 12:59:22 pm: The very same thing happened to me since updating my 0810 build a couple of days ago. I got the message

"An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed."

I had to reboot and thankfully it all worked again. It has happened to me at least twice now.

In addition and whether this is related or not i dont know, but each time any new device is detected, DCERouter dies and reloads. The device is added fine.....

Very strange.
Title: Re: This orbiter will be closed message.
Post by: maverick0815 on September 06, 2009, 01:20:34 pm: same happened here...
Title: Re: This orbiter will be closed message.
Post by: Itsik on September 07, 2009, 04:10:26 pm: yep, here as well ...
Title: Re: This orbiter will be closed message.
Post by: Marie.O on September 07, 2009, 05:11:01 pm: Did anyone open a trac ticket with some logs about this...
Title: Re: This orbiter will be closed message.
Post by: pigdog on September 08, 2009, 01:28:12 am: Hi posde,

I was considering doing a from scratch rebuild in order to determine if this was related to the alpha 2.30 snafu and/or 2.32/2.33 & 2.34 fixes.

If it returned I could grab logs, if gone it's then something residual.

Is there a way you'd rather proceed?

Cheers.

P.S. If you don't Regen this orbiter on the Core and you go to KDE Desktop the main menu image (sans flicker - not running) is superimposed over the KDE image.
Title: Re: This orbiter will be closed message.
Post by: rocketlynx on September 08, 2009, 03:37:10 am: I also have the same problem. I've had this recently, I think, since the Alpha-2.3x updates but it could have been a few updates before that.

It seems that the Core/Hybrid is confused and starts the Orbiter a second time on reboot and DCERouter reloads. If I knew where the script that loads the Core's OnScreenOrbiter was, I'd look to see if somehow it got a double entry.

Also, just checked, rebooted MDs and they seem to be OK!
Title: Re: This orbiter will be closed message.
Post by: maverick0815 on September 08, 2009, 03:46:38 pm: I did a clean install after this, and got no messages like that again
Title: Re: This orbiter will be closed message.
Post by: pigdog on September 08, 2009, 04:52:45 pm: Hi,

I did a re-install and this problem was corrected.

I will rename the title to Resolved.

Cheers.
Title: Re: This orbiter will be closed message.
Post by: rocketlynx on September 08, 2009, 06:20:46 pm: Quote from: pigdog on September 08, 2009, 04:52:45 pm
Hi,

I did a re-install and this problem was corrected.

I will rename the title to Resolved.

Cheers.

Ok, before I do a re-install, I have a question. Are you doing a backup and then a restore after the clean re-install? Also, I've done backus but never had to use them. What does the backup contain and what does it restore? Does it restore MDs or, do you restore the backup and then create the MDs? Or, do you stay away from the restore because it may re-corrupt the new installation.

What's the order?

Thanks,
Charles
Title: Re: Resolved - This orbiter will be closed message.
Post by: pigdog on September 08, 2009, 06:41:16 pm: Hi,

The script responsible for generating backups is /usr/pluto/bin/PlutoRestorePoint.sh

It looks like it does this...

-pluto_main database
-asterisk database
-files needed by the web admin
- floorplans, users, rooms, scenarios
-the pluto.conf config file

If you have media on your LinuxMCE HDD, or mythtv stuff, vdr, etc this stuff would probably be lost. You may be able to mod the script - I don't know.

I didn't do a backup/restore because I wasn't sure about corruption from original problem, cache-ng, etc., etc.

I'm rebuilding everything.
Title: Re: Resolved - This orbiter will be closed message.
Post by: felpouse on September 08, 2009, 08:04:53 pm: Hi all,

I've encountered the same issue. But actually for me make a reinstall is really difficult.
I tried this way. If u check the processes via ssh with ps -auxwf u'll finf the pid of OrbiterGL -d NN process that is involved on the UI interface.

If u kill it, the fist pid one that was started restart and u can have again the interface working perfectly.

It could be better to understand why this happened, because until yesterday I never have it .

Code: [Select]
05 09/08/09 19:54:49.117 Got a reload command from 0 <0xb434db90> 05 09/08/09 19:54:49.375 Orbiter reloading... <0xb434db90> 05 09/08/09 19:54:49.375 Orbiter quiting... <0xb434db90> 05 09/08/09 19:54:49.375 Got an on quit. Pushing an event into SDL <0xb434db90> 05 09/08/09 19:54:49.375 Got an on quit. Pushing an event into SDL <0xb434db90> 05 09/08/09 19:54:49.449 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=142847376, pDisplay_DataConnection=142869320 ->Closing <0xb0afdb90> 05 09/08/09 19:54:49.450 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=142847376, pDisplay_DataConnection=142869320 ->Closed <0xb0afdb90> 05 09/08/09 19:54:52.842 void ClientSocket::Disconnect() on this socket: 0x87809c0 (m_Socket: 16) <0xb62f66e0> Return code: 2 2 09/08/09 19:54:52 21 (spawning-device) Device requests restart... count=2/50 dev=21 Tue Sep 8 19:54:52 CEST 2009 Restart ========== NEW LOG SECTION ========== 1 09/08/09 19:55:00 21 (spawning-device) Starting... 2 1 09/08/09 19:55:00 21 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh 05 09/08/09 19:55:11.433 Replacement SDL window created! <0xb5a4cb90> 05 09/08/09 19:55:11.613 Using masked UI? NO <0xb5a4cb90> 05 09/08/09 19:55:13.305 Creating child 22 <0xb624e6e0> 05 09/08/09 19:55:13.315 Creating child 23 <0xb624e6e0> 05 09/08/09 19:55:13.345 Creating child 25 <0xb624e6e0> 05 09/08/09 19:55:13.411 Creating child 26 <0xb624e6e0> 05 09/08/09 19:55:13.463 Creating child 30 <0xb624e6e0> 05 09/08/09 19:55:13.470 Creating child 35 <0xb624e6e0> 05 09/08/09 19:55:14.040 VisibilityNotify! <0xb624e6e0> 05 09/08/09 19:55:14.040 EnterNotify! <0xb624e6e0> 05 09/08/09 19:55:14.040 FocusIn! <0xb624e6e0> 05 09/08/09 19:55:14.040 VisibilityNotify! <0xb624e6e0> 05 09/08/09 19:55:14.040 VisibilityNotify! <0xb624e6e0> 05 09/08/09 19:55:14.040 FocusOut! <0xb624e6e0> 05 09/08/09 19:55:14.040 FocusIn! <0xb624e6e0> 05 09/08/09 19:55:14.041 LeaveNotify! <0xb624e6e0> 05 09/08/09 19:55:14.041 EnterNotify! <0xb624e6e0> 05 09/08/09 19:55:14.205 FocusOut! <0xb624e6e0> == ATTEMPT FRESH START == 1 09/08/09 19:55:14 /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device) 11136 Dev: 21; Already Running list: 15,16,18,34,19,27,28,38,25,22,23,26,35,30, == FRESH START == 1 09/08/09 19:55:14 /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device) device: 21 ip: localhost cmd_line: LaunchOrbiter.sh 0 09/08/09 19:55:14 21 (spawning-device) Entering 21 ========== NEW LOG SECTION ========== 1 09/08/09 19:55:14 21 (spawning-device) Starting... 1 1 09/08/09 19:55:14 21 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh 05 09/08/09 19:55:14.872 Replacement SDL window created! <0xb5a1ab90> 05 09/08/09 19:55:15.073 Using masked UI? NO <0xb5a1ab90> 05 09/08/09 19:55:15.551 Creating child 22 <0xb62236e0> 05 09/08/09 19:55:15.591 Creating child 23 <0xb62236e0> 05 09/08/09 19:55:15.612 FocusOut! <0xb624e6e0> 05 09/08/09 19:55:15.612 LeaveNotify! <0xb624e6e0> 05 09/08/09 19:55:15.620 Creating child 25 <0xb62236e0> 05 09/08/09 19:55:15.742 Creating child 26 <0xb62236e0> 05 09/08/09 19:55:15.758 Creating child 30 <0xb62236e0> 05 09/08/09 19:55:15.789 Creating child 35 <0xb62236e0> 05 09/08/09 19:55:15.860 VisibilityNotify! <0xb624e6e0> 05 09/08/09 19:55:15.860 EnterNotify! <0xb624e6e0> 05 09/08/09 19:55:16.012 FocusIn! <0xb624e6e0> 05 09/08/09 19:55:16.052 FocusOut! <0xb624e6e0> 05 09/08/09 19:55:16.252 FocusIn! <0xb624e6e0> 05 09/08/09 19:55:16.423 LeaveNotify! <0xb624e6e0> 05 09/08/09 19:55:16.423 FocusOut! <0xb624e6e0> 05 09/08/09 19:55:16.423 VisibilityNotify! <0xb62236e0> 05 09/08/09 19:55:16.423 FocusIn! <0xb62236e0> 05 09/08/09 19:55:16.423 VisibilityNotify! <0xb62236e0> 05 09/08/09 19:55:16.423 VisibilityNotify! <0xb62236e0> 05 09/08/09 19:55:16.423 FocusOut! <0xb62236e0> 05 09/08/09 19:55:16.423 EnterNotify! <0xb62236e0> 05 09/08/09 19:55:16.423 FocusIn! <0xb62236e0> 05 09/08/09 19:55:16.684 FocusOut! <0xb624e6e0> 05 09/08/09 19:55:26.680 Orbiter quiting... <0xb43aab90> 05 09/08/09 19:55:26.681 Got an on quit. Pushing an event into SDL <0xb43aab90> 05 09/08/09 19:55:26.685 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=167276088, pDisplay_DataConnection=167278208 ->Closing <0xb09fdb90> 05 09/08/09 19:55:26.686 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=167276088, pDisplay_DataConnection=167278208 ->Closed <0xb09fdb90> 05 09/08/09 19:55:26.820 LeaveNotify! <0xb62236e0> 05 09/08/09 19:55:26.820 FocusOut! <0xb62236e0> 05 09/08/09 19:55:30.654 void ClientSocket::Disconnect() on this socket: 0x9e7f9c0 (m_Socket: 16) <0xb624e6e0> Return code: 0 2 09/08/09 19:55:30 21 (spawning-device) Shutting down... count=2/50 dev=21 Tue Sep 8 19:55:30 CEST 2009 Shutdown Return code: 137 3 09/08/09 19:56:45 21 (spawning-device) Device died... count=1/50 dev=21 Tue Sep 8 19:56:45 CEST 2009 died ========== NEW LOG SECTION ========== 1 09/08/09 19:56:55 21 (spawning-device) Starting... 2 1 09/08/09 19:56:55 21 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh 05 09/08/09 19:56:56.333 Replacement SDL window created! <0xb58ffb90> 05 09/08/09 19:56:56.470 will overwrite wm window id // void X11wrapper::Assign_WmWindow(Window) <0xb58ffb90> 05 09/08/09 19:56:56.474 Using masked UI? NO <0xb58ffb90> 05 09/08/09 19:56:57.088 Creating child 22 <0xb62a16e0> 05 09/08/09 19:56:57.149 Creating child 23 <0xb62a16e0> 05 09/08/09 19:56:57.200 Creating child 25 <0xb62a16e0> 05 09/08/09 19:56:57.222 Creating child 26 <0xb62a16e0> 05 09/08/09 19:56:57.269 Creating child 30 <0xb62a16e0> 05 09/08/09 19:56:57.301 Creating child 35 <0xb62a16e0> 05 09/08/09 19:57:01.158 VisibilityNotify! <0xb62a16e0> 05 09/08/09 19:57:01.158 EnterNotify! <0xb62a16e0> 05 09/08/09 19:57:01.293 FocusIn! <0xb62a16e0> 05 09/08/09 19:57:01.293 VisibilityNotify! <0xb62a16e0> 05 09/08/09 19:57:01.293 VisibilityNotify! <0xb62a16e0> 05 09/08/09 19:57:01.293 LeaveNotify! <0xb62a16e0> 05 09/08/09 19:57:01.294 EnterNotify! <0xb62a16e0> 05 09/08/09 19:57:01.294 FocusOut! <0xb62a16e0> 05 09/08/09 19:57:01.294 FocusIn! <0xb62a16e0> 05 09/08/09 19:57:01.294 FocusOut! <0xb62a16e0> 05 09/08/09 19:57:01.294 LeaveNotify! <0xb62a16e0> 05 09/08/09 19:57:01.294 VisibilityNotify! <0xb62a16e0> 05 09/08/09 19:57:01.294 EnterNotify! <0xb62a16e0> 05 09/08/09 19:57:01.294 FocusIn! <0xb62a16e0> 05 09/08/09 19:57:01.421 FocusOut! <0xb62a16e0>
If someone could give me some support we can try to investigate on it.
I suppose that could be related to a defunct process/script lauched that involved in a second start of the LaunchOrbiter.sh script and the error on the UI interface.

Best regards

Luke
Title: Re: Resolved - This orbiter will be closed message.
Post by: rocketlynx on September 10, 2009, 07:08:05 am: Quote from: felpouse on September 08, 2009, 08:04:53 pm
Hi all,

I've encountered the same issue. But actually for me make a reinstall is really difficult.
I tried this way. If u check the processes via ssh with ps -auxwf u'll finf the pid of OrbiterGL -d NN process that is involved on the UI interface.

If u kill it, the fist pid one that was started restart and u can have again the interface working perfectly.

It could be better to understand why this happened, because until yesterday I never have it .

If someone could give me some support we can try to investigate on it.
I suppose that could be related to a defunct process/script lauched that involved in a second start of the LaunchOrbiter.sh script and the error on the UI interface.

Best regards

Luke
This kill is only good for the current boot, correct? That is, when you reboot, since it hasn't been fixed, the same problem will return. I wonder if anyone who understands this strange situation could comment on where the problem is coming from and if there is a way to fix it short of a complete re-install. Also, since my Core/Hybrid is in a closet and I don't really use it as a Media Director, I'll try to live with it until a fix comes along.

Charles
Title: Re: Resolved - This orbiter will be closed message.
Post by: canukguy1974 on September 11, 2009, 12:50:56 am: I have the same problem. Is there away that we can revert the upgrade. I don't see how reinstalling it is away to resolve the issue. We need to find out why the handful of us have this issue and others don't. I deleted all the orbiters from web admin except Orbiter #20 the onscreen and I still get the same thing. When I check processes I notice that LaunchOrbiter.sh is listed like 10 times. I am still new to linuxmce so I am still guessing. I really don't want to re-install the whole system again. I have alot of media on this. When I do a re-install can I save my /home folder so I don't lose all my media and settings?

EDIT*******
this is the log for 20_LaunchOrbiter.sh.log
Code: [Select]
== ATTEMPT FRESH START == 1 09/07/09 22:52:10 /usr/pluto/bin/Spawn_Device.sh 20 (spawning-device) [1;00m27482 Dev: 20; Already Running list: 21,25,22,30,24,15,16,17,18,27,28,[1;00m == FRESH START == 1 09/07/09 22:52:10 /usr/pluto/bin/Spawn_Device.sh 20 (spawning-device) [1;00mdevice: 20 ip: localhost cmd_line: LaunchOrbiter.sh[1;00m 0 09/07/09 22:52:10 20 (spawning-device) [1;00mEntering 20[1;00m ========== NEW LOG SECTION ========== 1 09/07/09 22:52:10 20 (spawning-device) [1;00mStarting... 1[1;00m 1 09/07/09 22:52:10 20 (spawning-device) [1;00mFound /usr/pluto/bin/LaunchOrbiter.sh[1;00m 05 09/07/09 22:52:11.007 [33;1mReplacement SDL window created![0m <0xb5939b90> 05 09/07/09 22:52:11.168 [33;1mwill overwrite wm window id [0m[32m// void X11wrapper::Assign_WmWindow(Window)[0m[0m <0xb5939b90> 05 09/07/09 22:52:11.174 [33;1mUsing masked UI? NO[0m <0xb5939b90> 05 09/07/09 22:52:11.434 [33;1mCreating child 21[0m <0xb613b6e0> 05 09/07/09 22:52:11.445 [33;1mCreating child 22[0m <0xb613b6e0> 05 09/07/09 22:52:11.458 [33;1mCreating child 24[0m <0xb613b6e0> 05 09/07/09 22:52:11.471 [33;1mCreating child 25[0m <0xb613b6e0> 05 09/07/09 22:52:11.494 [33;1mCreating child 30[0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mVisibilityNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mEnterNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mFocusIn![0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mVisibilityNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mVisibilityNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.824 [33;1mLeaveNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.825 [33;1mFocusOut![0m <0xb613b6e0> 05 09/07/09 22:52:11.825 [33;1mEnterNotify![0m <0xb613b6e0> 05 09/07/09 22:52:11.825 [33;1mFocusIn![0m <0xb613b6e0> 05 09/07/09 22:52:13.187 [33;1merror_code==1 => ErrorText=='BadRequest (invalid request code or no such operation)' [0m[32m// bool X11wrapper::Mouse_Grab(Window, Window)[0m[0m <0xb62da6e0> 05 09/07/09 22:52:13.188 [33;1merror_code==1 => ErrorText=='BadRequest (invalid request code or no such operation)' [0m[32m// bool X11wrapper::Keyboard_Grab(Window)[0m[0m <0xb62da6e0> 05 09/07/09 22:52:13.190 [33;1mVisibilityNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.190 [33;1mEnterNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mFocusIn![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mVisibilityNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mVisibilityNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mFocusOut![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mLeaveNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mEnterNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.309 [33;1mLeaveNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mVisibilityNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mEnterNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mFocusIn![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mLeaveNotify![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mFocusOut![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mFocusOut![0m <0xb62da6e0> 05 09/07/09 22:52:13.310 [33;1mFocusIn![0m <0xb62da6e0> 05 09/07/09 22:52:13.591 [33;1mFocusOut![0m <0xb62da6e0> 05 09/07/09 22:52:22.271 [33;1mFocusIn![0m <0xb62da6e0> 05 09/07/09 22:52:22.435 [33;1mFocusOut![0m <0xb62da6e0> 05 09/07/09 22:52:22.563 [33;1mOrbiter quiting...[0m <0xb45e8b90> 05 09/07/09 22:52:22.564 [33;1mGot an on quit. Pushing an event into SDL[0m <0xb45e8b90> 05 09/07/09 22:52:22.583 [33;1mXRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=163633600, pDisplay_DataConnection=-1307217360 ->Closing[0m <0xb0ffdb90> 05 09/07/09 22:52:22.583 [33;1mXRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=163633600, pDisplay_DataConnection=-1307217360 ->Closed[0m <0xb0ffdb90> 05 09/07/09 22:52:22.659 [33;1mLeaveNotify![0m <0xb613b6e0> 05 09/07/09 22:52:22.659 [33;1mFocusOut![0m <0xb613b6e0> 05 09/07/09 22:52:26.795 [33;1mvoid ClientSocket::Disconnect() on this socket: 0x9823f00 (m_Socket: 16)[0m <0xb62da6e0> Return code: 0 2 09/07/09 22:52:26 20 (spawning-device) [1;33mShutting down... count=1/50 dev=20[1;00m Mon Sep 7 22:52:26 EDT 2009 Shutdown /code]
Title: Re: Resolved - This orbiter will be closed message.
Post by: pigdog on September 12, 2009, 12:01:43 am: Hi canukguy1974,

I thought it might be possible to downgrade ...

http://forum.linuxmce.org/index.php?topic=8639.0

... however, since I've rebuilt I've been fine and no re-occurrence

If your media is separate from your HDD that has your OS ie: on a NAS, partition, etc., you media will be fine.

If you have one big HDD with everything - don't do that!

Separated...

the OS may change but the media stays the same.

Queue the music.
Title: Not Resolved - This orbiter will be closed message.
Post by: infoteksec on September 15, 2009, 08:51:47 am: Saying this is RESOLVED is like saying "My car now works because I've bought another one" rather than repairing the tyre puncture.

LMCE is big, very big - Huge. I think quality control is taking second place to getting new features out. Since there are so many components, changes are being made asynchronously without proper testing.

Its not the first time that an ungrade has resulted in installations getting crippled. The upgrade should have been withdrawn promptly rather than let others suffer.

Peter
Title: Re: Resolved - This orbiter will be closed message.
Post by: tschak909 on September 15, 2009, 12:33:24 pm: ...

It's rather easy to say these things, when you're the user, and not the one developing the software.

I'm very tired of comments like these, especially when you refuse to take into account that _THESE CURRENT RELEASES ARE ALPHA_

Expect stuff to break,

When we can fix it, we will, but we have to keep moving forward.

Regression testing has been a huge issue, and was not implemented at Pluto at all, I have spent _YEARS_ figuring out how to graft on unit testing to the system to the system, and when I can, I will...

Until then,
Yes, stuff will break, these are the development versions, live with it, and stop complaining and help us debug the problem.

-Thom
Title: Re: Resolved - This orbiter will be closed message.
Post by: infoteksec on September 15, 2009, 01:16:52 pm: .... and I am in awe of the work that has been done.

Nevertheless, when you are told not to install the DVD of version 7.whatever and install the version based on 8.whatever instead you really are stuck with whatever gets dished out.

If releases are discovered to be a retrograde step you really should withdraw it and justify if only to yourself that the change is justified.

I'd love to help fix things -however, though I've been in software engineering for over 40-years having developed systems for some of the first 8-bit micros I have also worked in Release Engineering for DEC as was but have little experience in the Linux space.

Regards
Title: Re: Resolved - This orbiter will be closed message.
Post by: tschak909 on September 15, 2009, 02:42:35 pm: as an aside, i also go all the way back to the 8-bit micro space, my first personal computer being a TRS-80 Model I (although most of my code was for 6502 based micros, mostly the Atari 800)

-Thom
Title: Re: Resolved - This orbiter will be closed message.
Post by: rocketlynx on September 15, 2009, 06:39:53 pm: Quote from: tschak909 on September 15, 2009, 02:42:35 pm
as an aside, i also go all the way back to the 8-bit micro space, my first personal computer being a TRS-80 Model I (although most of my code was for 6502 based micros, mostly the Atari 800)

-Thom

I understand your pain and agree, It's Alpha!

Thom, I'm living with this for now rather than reinstalling because I don't use my core as an MD.

Can I stop/kill the MD on the Core/Hybrid after the core reboots which will also of course, kill the orbiter, with a command from the terminal?

Thanks,
Charles

P.S. Check your spam filter for a personal email I sent you about some plans I have for the WebDT 366 Orbiter.
Title: Re: Resolved - This orbiter will be closed message.
Post by: theteju on September 21, 2009, 02:17:01 pm: I have just installed fresh 8.10 and it was working fine until the update.
Now I am facing the same problem.
It took me a night to install the system, is there any other way to solve the problem rather than reinstalling ?
Title: Re: Resolved - This orbiter will be closed message.
Post by: Marie.O on September 21, 2009, 02:40:28 pm: Quote from: theteju on September 21, 2009, 02:17:01 pm
It took me a night to install the system, is there any other way to solve the problem rather than reinstalling ?

We are working on the problem. And the fix will work without you having to reinstall
Title: Re: Resolved - This orbiter will be closed message.
Post by: theteju on September 21, 2009, 07:46:49 pm: Thank you for your prompt reply. I guess i shall wait.
Title: Re: Resolved - This orbiter will be closed message.
Post by: rages on October 01, 2009, 04:23:29 pm: Hi,

I have the same problem, my installation is updated to the latest alpha, no news on this?

tnx for your work

Emanuele
Title: Re: Resolved - This orbiter will be closed message.
Post by: felpouse on October 01, 2009, 06:01:33 pm: Hi Emanuele,

actually I think they are still working on it.

Also me, I have the latest version installed, but sometime still happen.
The only think to do, is to kill the PID related to the orbiter and wait for the restart process and all will go well.

Regards

Luke
Title: Re: Resolved - This orbiter will be closed message.
Post by: pigdog on October 01, 2009, 08:36:16 pm: Hi,

A quick workaround is...

When you get the "Grey Screen" wait about 20-30 seconds, then press left mouse button, right mouse button, left mouse button.

The main menu will return. Then go to Advanced>Quick Regen this Orbiter.

The screens will be regenerated with flickr screens.

If dcerouter is regenerated the same thing (grey screen) will happen again.

It still happens if you update to alpha 2.36.

I did not have this problem on a clean install (from scratch).
Title: Re: Resolved - This orbiter will be closed message.
Post by: shakeel on October 05, 2009, 04:48:43 am: Pigdog's workaround works for me. I refuse to rebuild the system from scratch like some of the previous postings suggest. My music, DVDs, Games and other settings are all configured on this system and to rebuild would take days (I haven't separated my core from the media director yet). So even if it is a work around it is better than a rebuild. I love Linuxmce so please fix this issue when you have a chance. Keep up the good work. I think this issue started about a month ago for me with one of the updates.
Title: Re: Resolved - This orbiter will be closed message.
Post by: tschak909 on October 05, 2009, 04:54:32 am: The issue has been resolved in the latest updates. But it is worth noting that even if you did a reinstall, your media metadata is stored alongside your media files, and is separate from the core database, so these things would be preserved. You can also use the backup and restore feature to keep device settings.

-Thom
Title: Re: Resolved - This orbiter will be closed message.
Post by: rocketlynx on October 05, 2009, 05:38:36 am: Quote from: tschak909 on October 05, 2009, 04:54:32 am
The issue has been resolved in the latest updates. But it is worth noting that even if you did a reinstall, your media metadata is stored alongside your media files, and is separate from the core database, so these things would be preserved. You can also use the backup and restore feature to keep device settings.

-Thom

Thom, Which latest updates? Something coming after Alpha2.36? I'm on 2.36 and I still have the annoying problem on the Core.

Charles
Title: Re: Resolved - This orbiter will be closed message.
Post by: phenigma on October 05, 2009, 10:51:55 pm: I can confirm that this is still happening on Alpha 2.36.

Thom, the issue with m_bMediaRunning not being set false, unless the core is running (http://forum.linuxmce.org/index.php?topic=8881.msg60630#msg60630,) still exists. Nothing in SVN has changed which would rectify the issue. I don't have a build environment yet so I can not provide a direct patch. I intend to get on irc and request some assistance with the build environment but I've been away and havn't had a chance yet.

I believe that adding the line:

Code: [Select]
m_bMediaRunning = false;
to LM::LM() in LM.cpp [line 70-83] will fix the problem.

J.
Title: Re: Resolved - This orbiter will be closed message.
Post by: tschak909 on October 05, 2009, 11:11:02 pm: I have committed the line to svn. Let's see if this fixes it.

-Thom
Title: Re: Resolved - This orbiter will be closed message.
Post by: huh on October 06, 2009, 07:00:30 am: Thanks Thom- is there any way to apply this now? Or do I/we have to wait until the next alpha is released?
Title: Re: Resolved - This orbiter will be closed message.
Post by: rocketlynx on October 06, 2009, 04:50:04 pm: Quote from: phenigma on October 05, 2009, 10:51:55 pm
I can confirm that this is still happening on Alpha 2.36.

Thom, the issue with m_bMediaRunning not being set false, unless the core is running (http://forum.linuxmce.org/index.php?topic=8881.msg60630#msg60630,) still exists. Nothing in SVN has changed which would rectify the issue. I don't have a build environment yet so I can not provide a direct patch. I intend to get on irc and request some assistance with the build environment but I've been away and havn't had a chance yet.

I believe that adding the line:

Code: [Select]
m_bMediaRunning = false;
to LM::LM() in LM.cpp [line 70-83] will fix the problem.

J.

phenigma, Did you figure out how to get the update or when the fix will be available? I asked Thom also but I don't think he's online and I have the same problem too and I'm fully updated also.

Charles
Title: Re: Resolved - This orbiter will be closed message.
Post by: phenigma on October 07, 2009, 01:04:50 am: Quote from: rocketlynx on October 06, 2009, 04:50:04 pm
phenigma, Did you figure out how to get the update or when the fix will be available? I asked Thom also but I don't think he's online and I have the same problem too and I'm fully updated also.

If you have a build environment set up you could try to build the package and install it on your core using dpkg. Otherwise... I imagine it'll be in the next alpha build.

J.
Title: Re: Resolved - This orbiter will be closed message.
Post by: huh on October 14, 2009, 03:42:50 pm: Now that alpha 2.37 has been released, anyone try it that had the "orbiter already started" error?
Title: Re: Resolved - This orbiter will be closed message.
Post by: rperre on October 14, 2009, 05:02:02 pm: i had the same problem and yes it seemed to fix the problem with an upgarde

Richard
Title: Re: Resolved - This orbiter will be closed message.
Post by: rocketlynx on October 14, 2009, 06:26:46 pm: Quote from: huh on October 14, 2009, 03:42:50 pm
Now that alpha 2.37 has been released, anyone try it that had the "orbiter already started" error?

The answer to your question is YES, I have installed the 810-Alpha2.37 update and YES when I rebooted my Core the problem was gone.

Since this has been such a menace for most non-Linux people and newbies to LinuxMCE, I would like to thank whomever is responsible for the fix. I had decided not to reinstall my core simply because I have to many devices installed and working very well, so I've just lived with doing a quick regen of my core's orbiter #21 each time after a needed router reload to get it temporarily under control. Enough bandwidth wasted.

Thanks again,
Charles
Title: Re: Resolved - This orbiter will be closed message.
Post by: tschak909 on October 14, 2009, 06:34:05 pm: thank posde for the all important leg work on this one.

-Thom
Title: Re: Resolved - This orbiter will be closed message.
Post by: felpouse on October 14, 2009, 08:41:08 pm: Dear all,

I would like to tell you that, after the last updates applied to the core, all seems to be fixed.
I had tried to reboot the core, reload and regen all orbiters and so on and the problem actually never appeared.

This is a great goal. Would thanks all people that work on it.

BR

Luke
Title: Re: Resolved - This orbiter will be closed message.
Post by: pigdog on October 15, 2009, 02:22:10 am: Hi,

Sorry, started a new job, just tested on my Core and will change status from Resolved to Solved.

Thanks all.
Title: Re: Solved - This orbiter will be closed message.
Post by: rages on October 15, 2009, 06:57:36 pm: Hi,

Great work! my core is OK now.

TNX

Emanuele