Tag Archives: Ubuntu

Problems with Eclipse buttons in Ubuntu 9.10

Just found this post which deals with the exact same problem that I have been fighting with…

After upgrading to Ubuntu 9.10 (Karmic Koala) some buttons no longer work in Eclipse 3.5. Clicking has no effect but keyboard shortcuts still work.

Create a script to start eclipse with the following export…

#!/bin/sh
export GDK_NATIVE_WINDOWS=1
/opt/eclipse-3.5/eclipse

… and remember to change the path to where your eclipse is located.

Check http://www.norio.be/blog/2009/10/problems-eclipse-buttons-ubuntu-910 for a little more background on the problem.

VPN forbindelse til SDU i Ubuntu

Det er muligt at forbinde til SDU’s netværk i Ubuntu via VPN. Denne guide er skrevet med henblik pÃ¥ brug af Ubuntu 8.04 og Gnome.

Der er nogle generelle oplysninger pÃ¥ SDU’s hjemmeside inkl. en installationsguide og en link til en Cisco klient der kan downloades. Det ser dog ikke rigtig ud til at der er nogen klient at downloade, men klienten skal heller ikke bruges her. I installationsguiden stÃ¥r der at man skal bruge et gruppenavn og gruppepassword, og at det kan fÃ¥es ved henvendelse i Helpdesken. Jeg har modtaget mit direkte fra mit institut, sÃ¥ jeg har ikke prøvet helpdesken, men man skal bruge begge dele for at guiden virker.

I Ubuntu skal man have installeret pakkerne “network-manager-vpnc” og “vpnc”.
sudo apt-get install vpnc network-manager-vpnc
Derefter er det nødvendig at genstarte network-manager og den nemmeste løsning er simpelthen at genstarte computeren.

Nu kan man konfigurere VPN forbindelsen ved at venstre-klikke pÃ¥ NetworkManager ikonet i statusbaren og vælge “VPN-forbindelse” og “konfigurer VPN”.

  1. Vælg “Tilføj” og følg skærmene igennem.
  2. Vælg Cisco VPN-klient.
  3. Udfyld “Required” pÃ¥ det første faneblad. Mit gruppenavn er tekvpn, men det er afhængigt af hvilket fakultet man er tilknyttet.
  4. Under “Optional” udfyld dit brugernavn (inkl. domæne pÃ¥ formen: “domæne\brugernavn”) og vælg “Brug domæne til brugerverification”. Mit domæne er “tek” men det er naturligvis afhændigt af fakultetstilknytning.
  5. Sidst men ikke mindst skal man vælge “Enable weak single DES encryption”.

SÃ¥ er det muligt at logge ind ved igen at venste-klikke pÃ¥ NetworkManager ikonet i statusbaren og vælge “VPN-forbindelse” og klikke pÃ¥ den nyoprettede VPN forbindelse og udfylde gruppepasswordet og det almindelige password man bruger til at logge pÃ¥ domænet.

Det er OK at bemærke det ironiske i at man skal sætte flueben i “Enable weak single DES encryption” nÃ¥r der pÃ¥ SDU’s oplysningsside stÃ¥r “Benytter 3DES kryptering (168bit) og betragtes som den mest sikre protokol”…

First impressions: Hardy Heron (beta) and VMware Workstation 6.5 (also beta)

I just read a blog post on the Planet Gnome RSS feed by a guy who calls him self ChipX86 who said the new beta of VMware Workstation 6.5 was out. Being a major fan of Workstation since version 5.5 i decided it had to try it out immediately.

The new killer feature is obviously the Unity feature, which some might have seen in Fusion, which is VMware’s Workstation edition for MacOS X. Unity allows applications running in the guest operating system, to be accessed in the host operating system. So you could start Internet Explorer (if for example your workplace insists on using an intranet web-application that will only work in IE6… bastards), minimize the whole Windows OS, and enjoy your normal favorite flavor of Linux only slightly marred by the sight of IE6 running.

There’s lots of new stuff in version 6.5 as well, apart from just Unity. You can read them all at VMware’s documentation, but the most important ones are probably:

  • support for 3D acceleration in Windows XP – good when your developing code using Delta3D for your master thesis :-)
  • GUI for manipulating virtual network settings on Linux hosts

There’s plenty of other new stuff as well. The blog post has a pretty good walk-through of the best features of Unity.

Installation and Configuration

The download is the usual 200+ MB .tar.gz file. Un-packaging the file results in the expected vmware-install.pl script which must be run as super user. Starting the installation process the first message received was a warning that my existing Workstation 6.0 installation would be removed first. Not exactly unexpectedly but still kind of annoying. It would have been nice to have been able to keep a non-beta version installed along the beta.

Graphical installation... sort of.

The installation ran smooth, and soon asked for permission to run the vmware-config.pl script. I can’t remember when I last installed a version of VMware that didn’t require the infamous vmware-any-any patch to work on my machine, so I was actually expecting this would prove problematic. But to my surprise everything ran quietly and perfectly.

Starting Workstation after the installation gave another pleasant surprise, when the program informed me that I had to run is as super user, to load some modules into my running kernel. Much better that the “thinking-for-while-and-then-not-starting” thing that happened in version 6 when there was a problem with the modules. After aborting and restarting the program with sudo, I got a very handy graphical window showing the loading of the modules. Nice touch.

But all is not well… because right after that a new dialoge informed me that the program would be running in debug mode, which could not be turned off, and that debug mode would result in significant performance loss. To bad… it was probably to be expected, but I would actually have liked a warning before installation, especially since I had to un-install my Workstation version 6 first. I’m pretty sure the documentation says something about this some where, but a bit more prominent warning would have been nice.

Debug mode... blast!

Running Workstation 6.5 beta 1

I have just been running this new version for an hour or two, so it’s hard to come with a solid conclusion about Workstation 6.5 beta 1. Most stuff seem to be working. Programs, networking etc. I can definitely say that I didn’t get any performance improvement, but that was to be expected with all this debugging stuff. But to be fair, I didn’t really get a huge loss of performance, so I guess I’m going to have some more testing to get a qualified opinion on that.

Working as expected

So… what about Unity? Well, it works. Sort of… It’s definitely not perfect, but it can be used. Lots of times moving around the windows will result in them not getting updated/redrawn, and other strange things. But it will mostly work. I used Visual Studio, which is one of my primary reasons for using Workstation in the first place, with unity on my normal desktop for a while, and it worked fine. No real problems using the programs, and you get used to using your normal Linux productivity tools along side of the Windows apps really fast. It’s fantastic to finally be able to use Windows programs on multiple desktops, for example. That’s one the features is miss the most, when I’m finally using Windows.

Mmmm Unity

Using Unity

Unity seems to be working quite good, event though it seems to suck a lot of resources from the machine when running programs. I managed to crash it a couple of times, and at one time it actually took down Ubuntu with it. But it’s almost worth it, being able to use those few essential Windows apps, without seeing that nasty little Start button.

Rendering errors...

Further Testing

So that was just the very first and very few impression from using Workstation 6.5 beta 1 for about one and a half hour. I’ll probably give some more work tomorrow, where I need to do some .NET development, and see where it leads. I have another machine running Workstation as well, so should the need arise to use version 6.0, I’m going to be able to use that one. If you’re not so lucky, and you need a stable Workstation, you should probably wait a little while before going 6.5. But don’t miss out on trying Unity if you get the chance. I’m already looking forward to enabling some of my desktop effects, and seeing what Unity are going to do about that.