Starting Studio on Linux?

[jpwegas]

Ok, I followed the instructions on the Linux FAQ here:

1. I'm running a GUI window manager (Gnome under Ubuntu 7.04) and logged in via the GUI.
2. I removed "-Djava.awt.headless=true" from the startsage script
3. I added the "force_headless_mode=true" to Sage.properties
4. /opt/sagetv/server/EULAstudio.txt exists

when I do "startsage" from a shell (in the GUI), the SageTV server process starts as normal, but I never see any EULA window or Studio window on the server.

What am I doing wrong?

Side note: I'd really love to be able to just use Studio directly on my Mac (server is Linux in the basement, but the main daily use machine is a Mac), but I suspect that would require a new server license for my Mac. Any chance of that changing? The files generated by Studio are only useful to a licensed server instance, right? So why does using Studio itself require a server license on the same machine? Is it simply that the server process and Studio are too tightly integrated? Just curious...

Thanks,

John

[_Demo_]

Did you run the sageclient.sh and tried pressing ctrl-shift-F12?

_Demo_

[jpwegas]

Actually, no. Forgive my newbie-ness - the FAQ entry didn't mention that you need to run the "client". (Isn't the "client" on Linux just Placeshifter?) From the wording of the FAQ I assumed that Studio was somehow spawned via the server startup script. I hadn't even installed the Linux client on that Linux box, since I normally don't use it as a Linux desktop or a Sage client.

When I get home tonight I will try again.

So if the Linux client is really Placeshifter, and I can spawn Studio from Placeshifter, I should be able to spawn Studio from the Placeshifter running on my Mac, right? That would be perfect.

Thanks for the clarification!

John

[Opus4]

Originally Posted by jpwegas

So if the Linux client is really Placeshifter, and I can spawn Studio from Placeshifter, I should be able to spawn Studio from the Placeshifter running on my Mac, right? That would be perfect.

In case you didn't know this: note that since Placeshifter is a remote client, it actually runs as part of the server application. When you open Studio in Placeshifter or in a media extender, Studio will actually open on the server.

- Andy

[bcjenkins]

So if you wanted ps to run local on a client, can you connect an x-windows session to your Mac and have it pop there?

B

[nielm]

Originally Posted by jpwegas

So if the Linux client is really Placeshifter, and I can spawn Studio from Placeshifter, I should be able to spawn Studio from the Placeshifter running on my Mac, right?

yes, but note that Studio will be running on the Linux server...

So why does using Studio itself require a server license on the same machine? Is it simply that the server process and Studio are too tightly integrated

Yes -- studio is part of the server.

[jpwegas]

Originally Posted by Opus4

In case you didn't know this: note that since Placeshifter is a remote client, it actually runs as part of the server application. When you open Studio in Placeshifter or in a media extender, Studio will actually open on the server.

- Andy

I understand that the Placeshifter is basically a "thin" client, so that most of the work is really being done on the server box by the SageTV server process.

But just to be clear, when you say "open on the server", you mean that the Studio will open a new window on the X11 display on the server, after I trigger it to start from a remote Placeshifter client?

That's even more confusing than I previously thought.

Thanks for the clarification.

John

[jpwegas]

Originally Posted by bcjenkins

So if you wanted ps to run local on a client, can you connect an x-windows session to your Mac and have it pop there?

B

Probably.

If I understand things correctly now, I can use PS to trigger Studio to start on the X11 display of the server box.

Whether I can use the X11 remote display to display the Studio window back on my Mac probably depends which X11 display the server process thinks it's attached to when it starts.

I will be playing around with this evening to see what the possibilities are.

Thanks,

John

[Opus4]

Originally Posted by jpwegas

But just to be clear, when you say "open on the server", you mean that the Studio will open a new window on the X11 display on the server, after I trigger it to start from a remote Placeshifter client?

I know next to nothing about "X11" other than that it is an X followed by two 1s. Anyway...

I believe you know this already, but: yes, Studio will certainly open on the server, if it is able to, instead of on a remote system where Placeshifter is running, as mentioned at the ends of Appendices M and N in the SageTV manual. The caveats there about how using service mode on Windows could affect whether it can open a Studio window would be similar to the fact that you had to take extra steps to enable the Linux server app to open Studio.

- Andy

[jpwegas]

So I installed Placeshifter on the Linux box and was able to start Studio. Thanks all for the clarifications on this matter!

I also tried connecting from my Mac (using X11 tunneling over ssh) to start the server and then trigger the Studio to start using the Placeshifter on the Mac.

It almost worked. The Studio window opens on the Mac, but it doesn't get any focus or allow any interactions. Picture attached below. The window is partly drawn but mostly blank. If I expand the window, the "drawn" portion gets bigger, but it's never more than 10% or so of the window.

I'm no X11 guru so I don't know what might be causing the problem. I can run other X11 programs over the same ssh tunnel and they appear fine on my Mac - I can interact with them as normal.

Has anyone else successfully displayed the Studio UI remotely over an ssh tunnel (on Mac or Linux)?

Thanks,

John

[ecoolman]

jpwegas, try exporting the following on your server box before starting sage placeshifter:

export AWT_TOOLKIT=MToolkit

Originally Posted by jpwegas

So I installed Placeshifter on the Linux box and was able to start Studio. Thanks all for the clarifications on this matter!

I also tried connecting from my Mac (using X11 tunneling over ssh) to start the server and then trigger the Studio to start using the Placeshifter on the Mac.

It almost worked. The Studio window opens on the Mac, but it doesn't get any focus or allow any interactions. Picture attached below. The window is partly drawn but mostly blank. If I expand the window, the "drawn" portion gets bigger, but it's never more than 10% or so of the window.

I'm no X11 guru so I don't know what might be causing the problem. I can run other X11 programs over the same ssh tunnel and they appear fine on my Mac - I can interact with them as normal.

Has anyone else successfully displayed the Studio UI remotely over an ssh tunnel (on Mac or Linux)?

Thanks,

John

[jpwegas]

Originally Posted by ecoolman

jpwegas, try exporting the following on your server box before starting sage placeshifter:

export AWT_TOOLKIT=MToolkit

Thanks, I'll try that this weekend.

John

[jreichen]

I'm digging up a very old thread here. Andy, I'm running 7.0.23 and the FAQ instructions don't work for me. I seem to remember this being an issue before v7 as well. It says to create an empty EULAstudio.txt file but it should already be there. The file is not already there, and creating an empty file doesn't work. Once I copied EULA.txt to EULAstudio.txt then it worked.

Also, java.awt.headless doesn't need to be removed from startsage (now startsagecore) anymore. The user can create a sagesettings file to control that. This will survive updates and upgrades.

HEADLESS=false

Thanks,
Jason

[Opus4]

Thanks -- that FAQ has been updated; let me know if there are any further issues with the instructions.

- Andy