No Gravatar

Well KDE4.1 is available, and it is a sweet. For a lot of people, this will be the switchover point, the rest of you – KDE4.2 should do it :)

I would like to suggest looking at Bruce Byfields excellent review for a good idea of who should be switching yet.

I, I’m sold. Despite the slowness of my NVidia card natively, I can work just fine using XGL. However, I also found that XGL conversely made my KDE3 installation almost unusably slow (ditto KDE3 apps I still use – even though inside KDE4 I can hack-launch them to run on the native screen with a few tweaks).
So I split out XGL to only run for KDE4 for now. To do so I rm’d /etc/X11/xsession.d/98xserver-xgl_start-server
then created a new script in /usr/bin called startkde4-xgl with the following content:

#!/bin/bash
GL_START=/usr/share/xserver-xgl/Xgl-session
XGL_DISPLAY=:1
XGL_OPTS=”-nolisten tcp -fullscreen -br +xinerama”

$XGL_START $XGL_DISPLAY $XGL_OPTS –execute /usr/lib/kde4/bin/startkde

Gave it execute permissions and added a session file for it in /usr/share/xsessions.
Please note: These instructions arethe short-version and they are for kubuntu, other distros handle XGL in very different ways.

Either way, it’s great to finally have KDE4.1 final installed – now to go PLAY !

 
No Gravatar

By now, most people know that KDE4 and later are severely hampered on NVidia hardware due to problems with the driver. This appears to be a problem with XRender feature primarily, though there are other things as well. I have in the past tried every single piece of the many pieces of advice out there – and none of them had any measurable effect for me. It all worked – it was just utterly, unusably slow.
News I saw today confirms the same problem is hitting the upcoming Gnome 2.6 and even the firefox browser.

Today, as I was reading more sites about it, I saw a possible hint that sounded worth a try – and I tried it – and it’s working perfectly – so I thought I would share it.
Switch to XGL. Unlike the AIGL favored by most distributions now, XGL does not make composition and render feature available through extensions (which is where NVidia seems to do an epic fail) – the actual X server is implemented directly in OpenGL – and then makes these features function by actually doing them in it’s existing OpenGL setup (yes I know this is an oversimplification but it covers the core reason why this seems to work).

On kubuntu hardy, getting xgl is as simple as: sudo apt-get install xserver-xgl
You need to reboot afterward as there is a bootscript that handles the switchover.

However, once I did that – KDE was a LOT faster. For a test, I enabled desktop effects – at first, nothing happened. Then I looked in the advanced settings and found it was set to use OpenGL – since my X-server is now already using OpenGL to render, this apparently does not work. So for a test, I threw it over to XRender – and suddenly they were working.
Frame rates were high – much higher than they had been under the Xorg server with XRender, the effects worked stably and without issues – there was no visual problems at all – and the desktop remained perfectly fast and responsive. In fact the only problem was the actual effects HAPPENED slow. This I am disinclined to blame on either XGL or XRender – I suspect this is simply a case of “don’t run desktop effects on a box with only 512MB of physical ram” – the card and display was handling it perfectly fine, the computer was just taking long to do this extra stuff (which I believe are done with lower priority to save resources for the more important applications).

I am pretty sure they are actually usable anyway – I will play more with them in the next day or two.

*Note: XGL is not considered stable, and being basically a fork is not a nice way of doing things. I have also heard reports of various shortcomings in it, some things that should work but just don’t. I haven’t used it long enough yet to find any – but you have been warned. It seems to make KDE4 usable – and right now, that is my highest priority, it may not be yours.

**Note: I do not suggest letting this blog be a suggestion to buy NVidia, I will never again – ATI has a FREE driver now, without problems and that works very well according to people – I can now get a card that meets my needs without a non-free driver, so I won’t be buying another NVidia and deal with nasty surprises like this again. I had no choice before – if you have one – choose free software. This entry is an attempt to help those who, like me, at a time when there was no other sufficient choice available were forced to buy an NVidia card and cannot upgrade at this time, to allow you to at least deal with the situation of the problems NVidia’s proprietary driver has with current software releases until the time you CAN upgrade.

 
No Gravatar

Last night I finished the code for kde3to4 version 0.0.2. This release will mark a major leap ahead in the race from a newly implemented idea to a genuinely solid and useful program.

The first major change is that it now uses kioclient rather than shell cp as it’s backend for copying files and directories. This is a major improvement over the previous one for many reasons. Kioclient is graphical and has things like progressbars working out of the box. Overwrite’s are handled sanely in the way users are already used to and error handling is well implemented.
It basically makes the entire user experience a huge deal better than it used to be. I highly recommend it (or for KDE3 apps it’s parent utilities integrated in kfmclient).

An even more important change is the new all_apps plugin which uses a fairly standard formula to try and migrate any and all apps it finds. This one is still very experimental and marked as such, but it should work very well since the vast majority of apps will play happily with the formula it uses. For the rest it contains a double-level of protection to reduce the risk of breakage.

1) It deliberately ignores any program for which an existing script exists. In other words, it gives precedence to specialized plugins rather than it’s own formulaic approach.
2) It has an internal blacklist of programs to ignore.

This gives quite a bit of power to the protection scheme. Amarok for example is safe to migrate for 1.x versions, but 2.x is not compatible with 1.x settings. A migration tool for amarok is on their TODO list but not finished. So what I did was to blacklist amarok in the all_apps plugin, and provide an amarok1.x plugin that you can use if you are not using amarok2 yet. When amarok2 has a safe way to import amarok1 settings, we can build another plugin for upgraders and handle each edge-case.

This morning I sent a mail to the kde-devel mailing list asking developers to let me know about apps that should be pointedly ignored by all_apps or provide plugins/documentation where specialized plugins could work instead. It got me some very useful feedback. At time of writing this post (less than an hour after the mail) the blacklist has been updated to include mailody and kdevelop. In the former case because it is completely incompatible (I will look at the possibility of a specialized plugin when I have time) and in the latter because the settings are so vastly different that an import makes no sense.
I also have specific confirmation from Boudewijn that krita should work perfectly with this setup.

All in all, kde3to4 is coming along very nicely and I have solid hopes that it may be included with KDE4.2 (a point where many people have already indicated they will switch and thus a point where it’s usefulness will likely peak).

——-
UPDATE: The new release is now available from the application page (link in the menu on the left)

 
No Gravatar

After some discussion on KDE-Devel this week, I began designing and coding a wizard for migrating application settings from KDE3 to KDE4. It requires that you have your old KDE3 .kde directory somewhere backed up, or that KDE4 uses a different location (this is the case on kubuntu) but other than that it makes migrating just a little bit easier as you no longer need to go and reconfigure all the apps you use every day.
The idea is that things like bookmarks, kopete accounts etc. should just follow you.

The program is written in pure bash with a kdialog frontend,and is designed in a very modular way so anybody (hopefully some of the application developers themselves) can write modules to migrate various apps which will tie into the wizard at large without any difficulty.
There is a howto for writing plugin scripts included with the package, which is released under the GPL version 3.
More info and downloads are on the program page.

 
No Gravatar

Yesterday I sent a mail to the KDE development mailing list indicating my personal top-3 wish-list items for KDE4.1. Aaron responded positively – indicating that one thing I indicated was already on the TODO list and another was in planning but needed time because of a QT shortcoming.

I mentioned a fourth one though, but added that this may be a kubuntu packaging issue. The problem that a default install from the Kubuntu PPA repo of 4.1RC1 does not install folderview – despite the latter having become an absolute cornerstone of KDE4.1. Perhaps I had a bad choice of words because I mentioned that it ‘could be a kubuntu packaging mistake’.
Aaron agreed that it was.

Johnathan Riddle then replied wanting to know what the mistake was – especially since it apparently mentions on the kubuntu RC1 site that folderview is in a sepperate package (when I installed RC1 it didn’t, but I haven’t gone to check so it may well have been updated since then).
Either way, I replied again – stating that I wasn’t trying to diss kubuntu, just trying to find out who to report it to. Aaron and me both stated that folderview should be a default install, Aaron even went so far as to say that it should be in KDEbase !
This didn’t happen, since the kubuntu guys felt that adding just one plasmoid to kdebase would be inconsistent, but they did update the dependencies so that folderview will henceforth be a default install (and the first kubuntu update to 4.1RC1 was already out today).
In short, like I always said – one of the most crucial end-user features of FOSS is that if you see a problem and you take care to politely explain what the problem is, the developers will make a genuine effort to make sure your problem is resolved… and people think proprietary software have MORE reliable support ? Ever seen a proprietory company give a damn about a feature-request or bug-report ? Let alone discuss it rationally and come to a solid solution in just 1 day !

Kudos to Johnathan and the other Kubuntu packagers for their effort and thanks to Aaron for replying and considering my ideas calmly and where solutions do not yet exist – at least respecting my views. To all the KDE4 flamers: THIS is the difference if you are just a bit POLITE and stop acting like gimme-gimme two year olds.

Anyway – no ranting tonight – I’m posting good news after all.

Finally, I promised a special announcement and here it is: In an effort to honor the memory of my departed friend Uwe I have volunteered to continue his work as the KDE press contact for Africa, ahead of the 4.1 release, I expect this to involve some real work soon. The community at large agreed so I am now a genuine KDE contributor. The contacts site should be updated soon, and this blog will be joining planet.kde.org as some of the early steps in this process.

 
No Gravatar

Friday afternoon saw the tragic and very premature passing away of my dear friend Uwe Thiem. This article, and this one gives more detail on Uwe’s massive contribution to FOSS, particularly KDE.
I would like to talk a little more about Uwe the person though, as I knew him. It says a lot about how passionate Uwe was about KDE that his final article about KDE was published on the same day he died. Since joining the project in it’s very early days, Uwe was active quite literally until his dying day.
He was a man of incredible intelligence who loved playing with language (and had mastered several), both human and computer. He was passionate and straightforward. I remember him once giving a rant about people who use the word ‘gender’ when they mean to ask somebody’s sex out of misplaced sensibilities (since that is entirely wrong). But he gave the rant, like all his rants, with a glint in his eye. Uwe had a sense of humor that any geek would be proud off. He was a celebrated coder and system administrator with a unique perspective on usability and friendliness for somebody so technically skilled.
It was his one true passion: ease of use, integration, consistency.
Knowing him was an education and I am a better person for having had him as a friend.

Go well my friend, you will be missed.

PS. I have done something special to honor the memory of my departed friend, but this is not the time or place to announce it so it will be a separate blog post in the near future.

 
No Gravatar

I have a challenge for the geeks reading this. Make this program crash.

First some background. Part of our server loadbalancing works by opening connections to the machines in question, if the connection opens, it assumes it’s all good, if it fails – it implements the failover setups.
One problem is that one of our services keeps accepting connections even if it’s already half-dead – making the test less than adequate. So we came up with the idea of writing a small daemon that listens on another port, the loadbalancer can check that. This new daemon will just accept the connection, then drop it straight away. Simple design see. It should also be basically crashproof – if it’s not there, that means ‘server is definitely dead’.

So I got to write the daemon. It is called alived. It runs as it’s own unprivileged user on port 10432 and should be completely secure since all connections are dropped right after being accepted.
However, we are concerned how it will hold up under load – so I was asked to give people the chance to try and crash it. Unfortunately I only have a debian/ubuntu package available at the moment, but that should cover a lot of people anyway, and the package is completely alien-safe for other cases.

So my challenge is, please install it, try to make it crash. Anything you can come up with – and if you do, post in the comments and let me know how you did it.
Sound like fun ?

Get the package here.

Socialist Libertarian

FSF

© 2012 The Blog From Hell Suffusion theme by Sayontan Sinha