Voor KDE-ontwikkeling gebruik ik een aparte gebruiker. Maar als je su - kde-devel uitvoert en daarna een X11-toepassing oproept, dan krijg je vervelende foutmeldingen als:

of

Hier is een aantal oplossingen voor.

For KDE development, I work with a separate user. However, when you invoke su - kde-devel and run an X11 application, you'll get nasty errors like:

or

There are several solutions for this.

It's not that obvious to obtain the window title when you only have the process ID (PID) of the process showing that window. xprop(1) and xwininfo(1) didn't work for me, because these were interactive commands. Finally I found the wmctrl(1) tool, which should work fine with most major window managers (KWin for example).

The following command obtains the window title of the process with PID 1234 and having a window managed by your window manager:

Unfortunately, X.org does not work out of the box when installing it inside VirtualBox on a Gentoo guest machine.

The VESA driver didn't really work when starting X, it spitted out the following line:

Well, maybe the VirtualBox Guest Additions will help out. They installed without a glitch on the Gentoo guest, but when starting X I got a similar error as above, only VESA replaced with some VirtualBox stuff.

It's been a real pain to enable graphics hardware acceleration on my 3.5 year old IBM Thinkpad T42, containing an ATI Radeon 9600 (Mobility). The binary drivers by ATI are just plain crap, causing insane instability to the system (kernel panics everywhere). I called it a day and continued working without acceleration. But applications like Google Earth are a real pain to use like this, so something inside me shouted to get this right.