So at long last the first release in the KDE 4 series, KDE 4.0 has been released.
A couple of days after they tagged 4.0 I switched to using KDE 4 as my working desktop. (btw, isn’t it odd that the tag name is 4.0.0 if the release was called 4.0?)
It was remarkably more stable and usable than it had been just 4 or so weeks before when I had tried it last. I managed to fix a couple of JuK bugs (one very minor, another a crash) before 4.0.0 was tagged. Unfortunately I didn’t get time to do nearly enough testing so JuK as shipped with 4.0 has several bugs which are already fixed, including:
- Allow JuK to load the playlists and cache for KDE 3′s JuK (so you’ll need to wait for 4.0.1 to load your old collection. Sorry. :( )
- Correctly save the collection list after running JuK for the first time (so you’ll need to wait for 4.0.1 to save your new collection. Sorry. :( )
- JuK files in 4.0 will not be compatible with 4.0.1 due to the bug that prevented loading 3.5 data. But if JuK fails to load the files it will try again in a mode that should allow 4.0 files to load, so fret not.
- Some icons that used to show up had their names changed and I didn’t update JuK. Fixed in 4.0.1 and greater.
- I fixed a bug causing the Play Queue to show up twice on startup, and it was pretty random as to whether JuK would save whether you wanted the Play Queue shown or not on shutdown.
- The track announcement popup is pretty much completely hosed in JuK. I would disable it until 4.0.1, which has bugfixes for cover icon size, and track popup positioning.
- I fixed a bug where the list of playlist columns you wanted visible was not saved properly.
All of these issues are fixed in the 4.0 branch (what will be 4.0.1) and in trunk (4.1). There is still a bug where the History Playlist doesn’t have the extra “Time” column that it is supposed to have (and I’m not sure why it doesn’t). And of course JuK is still a little rough around the edges. But it is good enough for daily use I think even though the underlying code could probably still use some porting love on my part.
If you use kdesvn-build then it is possible to build the specific 4.0 release (using the tag 4.0.0 option pretty much everywhere) but I would recommend building the 4.0 branch instead if you’re going to be going to the trouble of using kdesvn-build. Especially since from what I under Gary L. Greene will be porting Konstruct to work with KDE 4 tarballs. Tarballs are mirrorable and put much much less load on our SVN servers. :)
Also I plan on pushing out the next kdesvn-build release at some point soon. kdesvn-build in /trunk supports downloading module updates while building which can be an impressive speedup. It introduces a few (minor) bugs which I may not have time to fix before I must release it or wait but I think the net benefits will be worth it.
Back to KDE 4 though, I wasn’t sure if I liked
kickoff KRunner (the new Alt-F2 Run Dialog) but when I went to try and launch System Settings, as soon as I typed “system” it noticed what I was trying to type and brought up an entry to launch that program. Very helpful.
(Incidentally the reason I was doing that was to test switching cursor themes. I heard that in KDE 4.0 it worked without requiring a reboot of the X Server, and it worked for me so that’s pretty cool.)
So congrats to all the developers, testers, translators, artists, bug wranglers, marketers (I guess we have those now ;) and everyone else who worked so hard to pull of the next major release of KDE. I’ll try to keep doing my part (time permitting unfortunately).