Skip to main content

Screen Sharing with Adobe Connect on Linux

One of my final annoyances as a full-time Linux user is the inability to share my desktop when I'm in Adobe Connect sessions. (Aside: you CAN do screen sharing from Linux quite well with Yugma. Free conference call line too.)

Although this isn't a real solution for screen sharing on Linux, it at least gets you there without having to use a completely different machine. These steps are for Ubuntu 9.04 but I'm assuming most of the other distros have VNC built in as well.

  1. Launch a Windows VM and install TightVNC
  2. Enable desktop sharing on Ubuntu (System -> Preferences -> Remote Desktop)
  3. Using the IP address or hostname that is displayed in the desktop sharing dialog once things are enabled, connect to your Ubuntu host using TightVNC from the Windows VM.
  4. From an Adobe Connect room, click "Share My Desktop" and select TightVNC as the application you want to share

I know, I know, people were probably groaning with step 1, but compared to having to switch completely over to my Mac just to share my desktop in a Connect meeting this is a better solution. I figured it would work but didn't get around to trying it until today. You may have some resolution issues to contend with but it gets you there.

I'd love to see Adobe actually enable screen sharing in Connect from Linux, but I'm not holding my breath.

Comments

stevenerat said…
About 4 years ago I blogged about how to use Crossover Office to run Windows apps on Linux. Connect, previously Breeze, ran fine even as a presenter in MSIE 6 on Fedora (newer versions of MSIE were not available at the time). Don't know if its still possible, but worth consideration.http://www.talkingtree.com/blog/index.cfm/2005/3/2/CrossOverOffice
Matthew Woodward said…
Interesting--I wouldn't have thought to try that. Guess I just assumed there was no way it would work! Probably worth a shot. Thanks!

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…