KDE 4.3.1 !

"About" dialog

"About" dialog

Helio striked once again 🙂 We now have official KDE versions before they are even announced (yes this link is broken at the time I’m writing, but it’s my guess for the announcement page) on kde website.

Many many thanks !

My biggest problem being now that I can’t tell (because I don’t know) the new features/bugfixes on this blog… 🙂


My first bug

Yes ! I’m not a maintainer, but yesterday was the first time I got a bug assigned to me for the stable 2008 Spring ! I still don’t understand why as I didn’t upload the package to Mandriva and was not the last one to make a modification in this package, according to the changelog.

Whatever, I’m glad it has been solved in less than a day and this is thanks to the reporter which actually gave the solution in the bug report and Adam which uploaded the package and made some clever modifications to the SPEC.

The only thing needed was a rebuilt from the svn repository which fixed the compilation problem. The package is now in the official update repository.

Enabling metacity compositing manager

I’ve just switched for a few days to GNOME and I remembered a discussion about activating metacity compositing manager. I haven’t found the information I was looking for on the Internet, but Olivier told me his “Jus de cuisson” mentioned a discussion thread back in January.

I eventually found the discussion thread, but what was stated was wrong (well, it was probably true when the message was sent, but not anymore) : the compositing manager is not enabled by default.

The compositing manager doesn’t give you as much effects and eye-candies as compiz, but it’s enough for a daily and professional usage. Here’s the list of things enabled with the compositing manager of metacity (quote from Frederic Crozat):

-Composited managed desktop (some applications might use it, like transparent applications such as gnome-terminal and probably others)
-brand new alt-TAB with screenshot of applications and highlight of to-be-focused app
-nice shadow around windows (now, you can have an idea on the initial design of Ia Ora window theme 🙂
-NO openGL required !!

So, here’s how you can enable it (should work with any distro using a recent enough metacity) :
gconftool-2 --type bool --set /apps/metacity/general/compositing_manager true
To disable compositor :
gconftool-2 --type bool --set /apps/metacity/general/compositing_manager false


Just a very small note about one website I’ve just discovered and one I already knew.

Expérimental X11 intel driver

Just a small post to tell you that I’ve recently switched to the experimental X11 driver called “intel” on my Mandriva Linux 2007 Spring system. This X11 driver, usable with most of the intel graphic cards, is improved and is shipped in the 2007 Spring edition. In order to use it, it is necessary to update your xorg server (which, as a bonus, gives you access to randr extensions 1.2) and to do some manual operations which are explained here in a very straight-forward way :


I really appreciate this driver instead of the previous one (i810) for several reasons :

  • I don’t have this “blurred” appearance I had before, probably due to an incorrect refresh rate
  • I can now hotplug my television to my linux box, but unfortunately, the picture is black and white (even after several tries with xrandr, I can’t get the color)…
  • It is now possible to change resolution dynamically. It was possible before with krandrtray, but now Xorg has a good support for it
  • The awful 915resolution service isn’t useful anymore at every boot. It was used to launch a program hacking the BIOS in order to have the X11 driver correctly guessing the resolution. But, well, it’s really a hackish solution, as you’d admit.

However, I still have two little problems with it, but they don’t bother me, personally :

  • Beryl, compiz & compiz-fusion (yes, it is now available in 2007 Spring if you activate backports) don’t work : back to my favorite KDE theme : Serenity)
  • Logging out is enough to see X crashing (but it doesn’t crash when I’m inside the session, even when displaying at the same time a filem, a 3D application and flash sites)

That’s it.

KDE 4.0 Beta 1 is available for Mandriva 2007.1

Warning : Beta1 isn’t as stable as you might expect and beta2 will probably give a better overview of KDE4. So you’d better install it on a test/virtual machine. (Thanks to Daniel Beck)

Yes !

  • urpmi.addmedia kde4 <KDE_MIRROR>/pub/kde/unstable/3.92.0/Mandriva/2007.1/i586/media/4.0
  • Update Mandriva Linux your favorite way
  • You’re done

I can’t test it because I first need to clean my drive and get a lot of free space 😦 But If I manage to install it, be sure it’s gonna be on this blog !

(For you information, KDE 4.0 Beta 1 = KDE 3.92.0)

Using kernel 2.6.22 with Mandriva 2007.1 – part 1

I’ve just installed kernel- (coming from cooker) on my faithful system running Mandriva 2007.1.

To install it, I had to use the --nodeps switch and install it with rpm (using urpmi and –allow-nodeps may have lead to the same result) because of a conflict with drakxtools-backend < 10.4.140. The conflict is probably here due to MCC not handling something (modular ide ?), but I won’t use MCC to handle the kernel anyway.

I wanted to try the coretemp module included with 2.6.22 and well, it works but actually isn’t very useful to me at the moment.

I also hope 2.6.22 will solve the scheduler problem I have with virtualbox and my previous -tmb kernel, but I haven’t tested it yet.

Now comes the difficult part : wireless. I know the module name for my card is now iwl3945 (this module now uses the new wireless kernel stack and doesn’t require the ipw3945d daemon anymore) and 2007.1 doesn’t detect nor know anything about this module. So back to the old way of configuring the wireless network : no more GUI 🙂 I first had to install another cooker RPM : iwlwifi-3945-ucode-2.14.4-1mdv2008.0 containing the microcode for the wireless card which gets loaded by the module when it gets loaded itself. The driver loaded successfully but I ended up with two interfaces : eth2 and wlan0_rename… udev is responsible for this but the last time I modified udev network configuration I ended up with a completely unusable system, so I’ll have a look when I know more about udev and its scripts.

So this last difficulty brought me back to my old -tmb kernel (well, not so old : 2.6.21) because I need a wireless connection at home and at work. I’ll make a new post once my wireless network card has been configured successfully !