Mandriva is not negotiating a patent deal with Microsoft

Several sites are spreading unfounded rumours that Mandriva will be the next one signing a patent deal with Microsoft, after Novell, Xandros and Linspire. Adamw, a Mandriva employee answered to the rumours on the Mandriva Cooker IRC channel today:

09:32 < AdamW> sander85: there are no plans to do a deal with microsoft,
and that comes from the top (fb)

(fb is probably François Bancilhon, Mandriva’s CEO).

Can we please stop spreading pointless rumours, and get back to real work and news please?

Update: Official statement

Bug fixing progress

Since a few days, the bug triaging process is in full force. The purpose is to review all old, unconfirmed bugs, and verify if they are still valid. And of course, making sure those valid bugs are fixed. I have the impression that it’s really a great success. Lots of Bugzilla e-mails are arriving in my mailbox, and looking at changelog mailing list, several old bugs are finally getting fixed.

I started to concentrate on bugs in Kaffeine and KMplayer. I think Kaffeine is now as stable as is possible now. That means: far from perfect, but I think all remaining problems should now be handled by its upstream authors. Already since some time, Kaffeine has XCB support, which should make it a lot more stable when viewing embedded videos in the Konqueror web browser. And since this weekend, Kaffeine correctly disables the screen saver when you are viewing a full screen video, and won’t copy the whole media file you open from media:/ URIs to your home directory. I proposed an update for Mandriva 2007.0 and 2007.1 Spring to fix the last two issues. Fixing the first one, is unfortunately a lot more difficult for older Mandriva versions, because it requires a more recent version of xine, and depends on libxcb, which is in contribs…

KMplayer was actually in a much better state. The only real serious issue, is that KMplayer does not add itself to KDEs service menus which appear when you insert a DVD disk. This is rather serious as KMplayer is Mandriva’s default video player, and thus user’s don’t get an option to actually play the movie when they insert a DVD disk. This should not be too difficult to fix though, so let’s hope we’ll have a fix soon.

I also reviewed Kopete bugs. About all of them are fixed in current Cooker, possibly we’ll also have udpated packages for 2007.0 and 2007.1 Spring implementing a higher framerate for MSN webcam support, fixing decryption of gpg encrypted messages (2007.1 only) and fixing errors when chatting on conference.jabber.org (2007.0 only).

For my own use (and pleasure), I also recompile a lot of Cooker packages for 2007.1. While recompiling a more recent version of libxml, I had problems with python crashing. After a lot of trying to find out what causes it, I found out that python-reportlab as shipped in both 2007.1 and Cooker makes python crash. Python-reportlab is a dependency of the hplip printer drivers, so if you don’t have these installed, you’ll probably never notice this problem. Ia also makes certain hplip utilities crash in 2007.1 and Cooker. Compiling a more recent version of python-reportlab, fixed all problems, so I hope we will see this as an update for 2007.1 soon.

Next on the bug review list, will be cd burning applications. Thanks to the article I wrote on this blog about audio cd burning applications, I already tested some of them, which always helps in reviewing bugs.

If you always wanted to get involved in free software development, this is actually a great opportunity to join the Mandriva bug reviewing effort! You don’t really need to have development skills, just some willingness to compare different bugs, to try to reproduce them, and to look them up in other bug trackers. Often those bugs are really already fixed, it’s just that someone has to confirm they actually are, or provide the good patch or solution which has been created by the upstream developers. If you are interested, do not hesitate to contact us on the bugteam mailing list!

Disk encryption in Mandriva

Last weekend, I bough an external USB hard drive to finally start regularly making back-ups of my computers at home. For security reasons, I wanted to store back-ups on an encrypted partition, because one never knows what may happen. Using an encrypted partition was not too hard, but still some bugs prevented it from being newbie proof.

For the encrypted partition, I chose to use LUKS. It seems to be some kind of standard, widely supported (by Hal for example), and it has some graphical utilities available which should make it a no-brainer.

First problem, I’m using x86_64, and apparently luks-tools only exists for i586 in Mandriva. I filed a bug, and a new luks-tools package for x86_64 should already appear very shortly on a Cooker mirror near you. If you have luks-tools installed, it should be as simply as running gnome-luks-format to set up an existing partition.

So I did it at the console. Of course, make sure you have the package cryptsetup installed, otherwise you won’t have the necessary utilities. First we’ll add a header to the partition, indicating that this is a LUKS encrypted partition, and which encryption type we are using:

cryptsetup -c aes-cbc-essiv:sha256 luksFormat /dev/sdb1

(as I already mentioned with gnome-luks-format, you should create the partition first, for example with diskdrake or cfdisk).
Once the header is in place, we’ll open the encrypted partition:

cryptsetup luksOpen /dev/sdb1 encbackup

Encback is a name you can freely replace by your own choice of course. Once you have done this, your encrypted partition will be mapped to /dev/mapper/encback. You can use this like any normal partition for example to create an ext3 file system on it:

mkfs.ext3 /dev/mapper/encback

Then we can mount it:

mount /dev/mapper/encback /media/encrypted-backup

And we’re ready to go. To close the encrypted device after I have umount it, I run

cryptsetup luksClose encback

When you plug in the USB disk, hall will automatically detect you have a LUKS encrypted partition. A dialog will appear, where you can enter your passphrase, and after that it is mounted automatically. At least, that’s the theory. Unfortunately, this was not working, probably because of bug #30015. Let’s hope this gets fixed soon! Also note that KDE does not seem to support this at all, so even then this is Gnome only. For now I have created two small scripts, which will run cryptsetup and mount or umount, so I don’t have to retype these commands by hand each time.

I opened another bug to request LUKS support in diskdrake. Disk encryption is becoming more and more common these days with all those portable storage media, so Mandriva’s default partition tool should have this support built in. I guess it should not be too hard to implement this.

Some nice documentation which helped me a lot during this exploration, can be found in Red Hat Magazine.

Update 22 May 2007: I updated the howto to use aes-cbc-essiv:sha256 instead of aes-cbc-plain. Reader David Crick pointed me to the fact that aes-cbc-plain is vulnerable to a cryptography weakness, which is called the “watermarking attack”. Thanks!

More community = less employees…

Last Thursday, at least four Mandriva employees received the news that their contract will be stopped next month. All of them are people who are very active in the Mandriva community, and sometimes maintainer of important packages (such as Apache). There has not been much more explanation about this decision. This gives the news last week that Mandriva wants more involvement of the community (read: people who are not payed) another dimension to me… :-(

Oh well, we’ll have to wait to see if this will impact development much. But it’s never a good sign that people have to leave a company.

Update 21 May 2007: It seems that the list referred to in the above posting in not completely correct. Currently a lot of rumours are going around, even on Mandriva’s official IRC channels, and even between current Mandriva employees. Probably more than four people are losing their job, but it seems not even Mandriva employees themselves know exactly who is concerned. The communication clearly has been catastrophic, and this is severely damaging Mandriva’s image :-(

Update 22 May 2007:To get a more complete picture of the problems, please also read Dvalin’s blog post.

Mandriva – The Next Generation

Mandriva 2007 Spring was already a very nice distribution with a lots of improvements and changes in style from the previous versions. severely improved graphical themes, the public availability of non-free packages, getting update notifications on the desktop without Mandriva subscription, and a generally more polished system.

For the next version of Mandriva, the bar is again set a lot higher than before. Last week, two interesting announcements were made:

  • David Barth announced that some internal re-organization was done at Mandriva, and that the community will be more actively involved in the development of the next Mandriva version. What this means in practice, and how this will work out, remains to be seen, but I have the feeling that this is a confirmation of something we have seen already in 2007.1: Mandriva really cares about the community now, and makes use of the community’s remarks to improve the distribution.
  • Anne Nicolas, who will follow-up development of next Mandriva’s versions from now on, announced that an effort will be done to get Mandriva’s bugzilla cleaned up and to improve the workflow of bug reports, which should result in a more bug free distribution. All new bug reports will first be checked by a team, which will verify the validity of the report, and which will collect all necessary information for the developers to be able to analyze and fix the bug. If developers receive more high quality reports, this will hopefully result in quicker and more bug fixing. Statistics about the bug fixing progress will be collected, in order to pinpoint problematic parts of the distribution, so this can be acted upon.

This is all great news. Mandriva shows that it is not wanting to be yet another ordinary nice Linux distribution, but that it has the ambition to be a real leader. Interesting times are coming!

Mandriva work this week

This week I was contacting the mailing lists for various upstream projects to find fixes for some problems.

First there was the problem that F-Spot does not automatically handle the upgrade from sqlite2 to sqlite3. In the past, F-spot used sqlite2 as its database, today it uses sqlite3 by default, but you can still continue to use your sqlite2 database. That is, if sqlite2 libraries are installed on your system. And one can imagine that in the future, distributions will stop shipping sqlite2, because it is not maintained anymore and because sqlite3 is far superior. It is possible to upgrade from sqlite2 to sqlite3 by upgrading the db at the command line, but we really cannot expect normal users to do this, do we?

In Pan, I had the problem that new headers were not appearing in a newsgroup, until I killed the “get new headers”-task by hand. I found out it was caused by a news server I had configured in Pan, which was not reachable. I filed a bug.

I experienced a crash in ogginfo when some wrongly encoded characters are found in the Vorbis tag, for which I found a patch with Google. I filed a bug but I’ll need to investigate if the tag is really invalid: Easytag shows it correctly without any problem.

Another problem I experienced already some time ago, but which I never really investigated, was that Amarok did not add files on a read-only Samba share to its library. Thanks to Debian changelog mailing list, I discovered today that there was a patch for libtag fixing this. This is a real serendipity!

I did again some testing with Kaffeine. I contact its mailing list for the problem that it copied everything to ~/tmp when using system:/ URI in Konqueror. I found a fix now, but I’m still not impressed by Kaffeine’s stability. For now, you’re better of continuing to use kmplayer.

I contacted Mandriva’s web discuss mailing list (which does not seem to be archived unfortunately) for a new structure of the End user documentation on the Mandriva wiki and posted a proposed for some documentation about the tmb kernel. I’m a bit disappointed by the reactions: like this we won’t succeed in creating a very active wiki community with lots of useful user documentation. I’ll try to implement a proposal in my sandbox this weekend: practical work is often better than theoretical discussion

Mandriva 2007 Spring released, looking forward to 2008

Now that Mandriva 2007 Spring has been released and the corrupted Mandriva Cooker subversion repository has been fixed, development for Mandriva 2008 has started now.

Some things which I have on my wishlist for Mandriva 2008:

  • New kernel, Linux 2.6.22 or later which I hope will give us these things: CFQ IO scheduler as default (since Linux 2.6.18), better task scheduler, probably CFS, better wireless drivers (bcm43xx is stable in 2.6.20, but it’s not in Mandriva’s 2.6.17, finally good Ralink drivers: complete documentation exists, but drivers are still not production quality)
  • Mandriva still uses OSS drivers for some sound cards which are perfectly supported with Alsa (for example for some Intel ICH2 810 AC97 cards, which was not fixed in 2007.1 as far as I know). This is annoying as OSS does not have sound mixing, and can cause applications complain about occupied /dev/dsp and it also causes missing sound in Flash. Fedora even does not ship OSS anymore for some time already. A maximum of cards should be switched to Alsa now early in Cooker development , so that things get tested.
  • slocate is still being installed by default by rpmsrate instead of the much performance friendlier mlocate (already in 2007.1 Main). We should make the switch now in rpmsrate so it’s the default in 2008.
  • Almost a year ago, I proposed a new program menu structure for Mandriva. According to Gnome and menu maintainer Frédéric Crozat, it would be implemented for 2008. Let’s hope this becomes true, as it will make the menu at the same time friendly for new users, and more practical for power users. Unfortunately, I lost the complete original document (what a shame!). If somebody still has it somewhere, I would be grateful if you could send it to me!
  • Drop esound, and use Pulseaudio instead. Pulseaudio is a more modern and actively maintained sound server. There was some discussion about it some time ago, and I still hope Pulseaudio will not be forced on all users (personally I prefer not to use a sound server, and let all the mixing be done by Alsa. For this reason, I still hope more and more applications will use GStreamer, as GStreamer makes it easy to choose your preferred output method, such as Alsa or Pulseaudio for all applications. But Pulseaudio should certainly replace esound in main.
  • Test new Kaffeine: In Mandriva 2007.0, Kaffeine was replaced by kmplayer as the default video player in KDE, because Kaffeine was unstable paying embedded videos in Konqueror. Now that both Xine and Kaffeine support XCB, this problem should be fixed. We should test if it is indeed stable now, and if Kaffeine plays supports all kinds of embedded videos in web pages like kmplayer. If this is the case, we should consider moving back to Kaffeine, as its interface is a bit better than KMplayer’s.
  • Mandriva’s net_applet and mdkonline system tray utilities still poll too much, which causes unnecessary CPU usage, and which also eats battery life on laptops. These applications should be scrutinized a bit more, so they are completely idle most of the time.
  • Up to date printing support: Unfortunately printing support did not really advance in Mandriva 2007 Spring. The drivers are mostly still the same as in 2007.0, and some newer printer models supported by newer versions of hpijs and other models which appeared on linuxprinting.org, are not support in 2007 Spring. Mandriva 2008 should really have up to date printing support, like was always the case in previous versions.
  • Cleaning up the repositories: the Main repository now contains a lot of programs which are not used by a lot of people (things like flphoto, uucp, uw-imapd, xpdf,…). On the other hand, some very interesting packages are in Contribs (Transmission, dovecot,…). The contents of both repositories should be looked at, in order to clean up, and put packages in the appropriate repository.
  • We need a simple application installation program: rpmdrake has improved a lot in 2007.0 and now in 2007.1 Spring. Still it is too complex for new users. Suppose a user wanting to search a DTP application. He should easily find Scribus. Well, Scribus does not even appear in the Publishing category in rpmdrake. Instead, these category contains mostly technnical console programs not suitable for beginners. We should have something like Ubuntu’s gnome-app-install which only shows userfriendly graphical applications.
  • More and easier to find documentation: Mandriva already comes with a lot of documentation, but the included handbooks are difficult to find (being hidden in More Applications). They should be in a more obvious place. On the other hand, we should make sure more documentation becomes available in different languages on the wiki, and the wiki should be easy to find (include a link on the desktop?). This way, users will know where to look for help.
  • Related to the menu structure and the reorganization of the repositories, we should constantly be evaluating which applications should be in the default installation and which not. We had such discussion shortly before 2007.1 Spring went out, but this was a bit too little too late. We should make sure we start with this process before the first beta is released, so we have more time to evaluate and stress test programs.

Currently I already started by taking a quick look at the contents of the main repository. Maybe other people are interested in participating in this effort, so that it can happen a bit more organized?

Struggling with Linux’ OOM killer when building RPMs

Last two weeks, I have created a lot of updated packages for Mandriva 2007.1. I packaged Gnome 2.18.1, and also updated subversion snaphots of kdepim and kdegraphics. Kdepim, because it has received a lot of bug fixing love the last two months, and kdegraphics, because it contains kpdf using new xpdf code, which should be compatible with PDF 1.6 and 1.7 specifications. In kdepim, they also removed the kitchensynk tool, which offered synchronization options with external devices. Apparently it was too buggy to be really useful. I have the impression that Kmail is indeed also more stable than in 3.5.6. I could not reproduce yet the hangs I sometimes experienced with 3.5.6.

Compiling kdepim on an AMD64 system, seems to require a huge amount of memory (much more than on x86 32 bit). 1 GB of RAM and about 250 MB of swap did not prevent g++ eating up all of my memory (even when no other services were active!). Unfortunately, this made Linux become completely unstable: the hard drive started thrashing the whole time, and the system was completely unresponsive. I could only stop it by doing a hard reset. I am clearly not the only one hating this stupid Linux behaviour.

In the Mandriva Cooker channel (irc.freenode.org, -cooker), couriousous suggested to execute

# echo 2 > /proc/sys/vm/overcommit_memory

The default value is 0: when an application asks more memory than is available, Linux will still try to allocate it, even if chances exist that it won’t be available. This seems to be done because some applications ask more memory than what they will really use. If in the end, no more memory or swap is availed, Linux’ OOM killer will kill some (random) processes to free up memory. By setting overcommit_memory to 2, the allocation of too much memory will fail immediately. The application can then react itself to the fact that not enough memory is available. The result was that instead of bringing my system to death, the g++ compiler just exited with the message that I was out of memory. Much nicer! I found a complete technical explanation about memory allocation in Linux on the web. To make this setting default, I put vm.overcommit_memory = 2 in my /etc/sysctl.conf. I do not understand why it is not the default value, making a system unresponsive for several (tens of) minutes does not seem very friendly…

Update 16 april 2007: It seems like this setting has severe problems as well. On my system with 384 MB RAM, which I use as server and desktop, several applications randomly crashed because they did not get the memory they wanted (Evolution, Tilda,…). Changing the setting back to 0, made these applications work correctly again. I suppose playing with the overcommit_ratio value as explained in the article which I mentioned above, can improve this behaviour. But anyway, it sucks that such things are so difficult to get right. This should really be working nicely out of the box

Anyway, in the end I got kdepim compiled on AMD64 by adding some more swap. From now on, I’ll be creating bigger swap partitions is Linux, it can realy be useful, even when you think you have enough memory…

I also built a freetype 2.3.4 RPM for Mandriva. Font rendering on my flat panel is now much nicer comparing with freetype 2.3.1 which is included in Mandriva 2007.1! Not that it was ugly before, but it’s a nice surprise to still see such big improvements, especially from a minor update.

OpenSolaris, ForeSight Linux, Mandriva 2007.1

Today I received the OpenSolaris Starter Kit package in my letter box! To promote OpenSolaris, Sun decided to start a free delivery program of the OS. The kit contains two DVDs: the first one contains live versions of OpenSolaris distributions Belenix, Schillix and Nexenta, while the second CD contains Sun’s own Solaris Express Community Edition. I thought to try it out quickly in VMWare, but apparently it needs 768 MB of Ram! Ouch, that’s huge, just for installing an OS! I’ll try to test out the live distributions maybe this weekend.

Today I also downloaded Foresight Linux. It seems to be a nice Gnome based distribution. I would like to try it out soon. I hope it won’t be a disappointment like Frugalware recently.

Another thing I would really need to do is write an extensive Mandriva 2007.1 final review. Yes, it is not yet officially announced, but the final 2007.1 tree is already available. It seems ISO images are currently distributed to early Bittorrent seeders, so maybe already tomorrow we can expect the official announcement.

Seems like I planned to do a lot this weekend. And I’m pretty sure I will never finish all these plans, because it’s becoming very hot again in Belgium, and then I like not to spend too much time on my computer :-) Forecasts said temperature would rise to 27 degrees during the next days. And that in April in Belgium?! I mean, fifteen years ago we used to say it was already very hot if it was 27 degrees in summer time… After one of the hottest summer ever last year (maximum of 37 degrees), an unusual hot winter (breaking several day and month records), now an extremely hot Spring… Global warming is clearly not an inconvenient threat for the future, it is already reality. Time to wake up those world leaders who still think it’s not necessary to do something.

Mandriva 2007.1: KDE vs. Gnome

Mandriva 2007.1 RC3 is out since this weekend, so we are really near the final release now. If you have some spare time, and some bandwidth, please grab one of the ISO images or start a network install via FTP with the boot.iso and report your findings!

After all the Gnome testing I did for Mandriva 2007.1, I thought it was time to do some ultimate testing with KDE. Actually, I’m very deceived: where Mandriva 2007.1 is very polished, the default KDE install is terrible. Really, not just bad, but plain terrible. Here’s an overview.

  • Image viewers:: Finally, it seems kuickshow has been removed from the default KDE installation. There is still gwenview, kview and showfoto (digikam) though. KView is really superfluous. GWenview does all what KView does, and more. Why keep it?
  • VoIP applications: It seems the marketing team has decided that VoIP will be the killer application for 2007.1. Great, but why does KDE need 3 VoIP applications?! There is KPhone, OpenWengo and Ekiga. Ekiga is without doubt the best Gnome VoIP application, but it really does not belong in KDE. OpenWengo is there, probably because of some agreement between Mandriva and the Wengo company. It seems like the best free (as in free speech) KDE VoIP application for now, as it’s actively developed. KPhone is not a dead project, but still I have rarely heard of it, and I’m wondering if there are really enough people using it. I never saw somebody on the cooker mailing list reporting about it or opening a bug report, which gives me the impression that this application is not very well tested in Mandriva. Why not just go with Wengophone? Wengophone can connect to any SIP service, so that does not seem to be a valid reason.

    Update 02 april 2007: The default VoIP application choice has changed today: KPhone is no longer installed by default in KDE, neither is Ekiga (excellent!). Skype was added for powerpack installs. Although I think Skype + Wengophone is still too much for Powerpack, the current situation is a huge improvement.
  • IRC and other network applications: Mandriva now installs all of kdenetwork by default. This includes the unmaintained and feature-lacking IRC client ksirc, as the program ksig. ksig seems to be a manager of signatures for your e-mail client. But: it does not seem to work together with KMail, KDE’s own e-mail client, as KMail seems to do its own signature management. I do not know a lot of people who are using so many different signatures that they need a seperate management application, and if it does not work together with KDE’s own mail client, I do not see why this is interesting to have. On the other hand, Konversation is also installed by default (while it still has not been moved to Main repository, which is also a problem). Konversation, contrarely to ksirc, and Kopete (which is also installed by default) is a great IRC client. So now we have two (actually even three counting Kopete) applications which can do IRC: again too much duplication.

    Update 02 april 2007: Today, first Konversation was removed (strange decision), now it has been added back. We are back at square one here. Actually the real problem here is not rpmsrate, it is task-kde which is the culprit, because it requires the kdenetwork metapackage, which installs ksirc and ksig by default, although they do not have high enough priority in rpmsrate. And Konversation still has not been moved to main :-(
  • Office suites: Mandriva 2007.1 installs two complete office suites in KDE. There’s the obligatory OpenOffice.org, but in 2007.1 we also see the complete KOffice suite now. That means two word processors, two spreadsheet applications, two presentation packages, etc… And that while KOffice are not very good in importing MS Office documents, and generally have a less extensive feature set. In 2007.0 there was the much better choice to install OpenOffice.org by default, and only a few of the KOffice applications which do not overlap too much with OpenOffice.org, like Krita, Kivio and Kexi.

    Update 02 april 2007: All of KOffice will not be installed anymore from now on. This issue has been fixed.
  • New kicker lay-out: The new kicker lay-out is very unhandy. The height of the panel has been reduced, so that there’s only one line available for open windows in the task list. Unfortunately a lot of space is wasted with four virtual desktops in the kicker bar. Together with 4 application icons and 4 items active by default in the system tray, this leaves way too less space for open windows. Already starting from three open windows on a 1024×768 monitor, the task list becomes too crowded to be pleasant. When changing the height of the panel back to the normal size, the Mandriva button becomes too big, that it’s not very beautiful anymore. Already several people asked on the cooker list how they can change the icon back to the previous one: it’s clear that this question will come back only more the moment Mandriva 2007.1 is released. A graphical configuration option was not possible for this release, due to a lack of time. A huge mistake if you ask me.
  • Fax programs: Actually this is also a problem present in the default Gnome installation, but in Gnome, this problem is not really visible, as it seems there are not graphical Gnome fax programs installed. In KDE this is worse: kdeprintfax, kfaxviewer and kfaw clutter the Office menu. This is especially visible when you use Discovery menus. As not a lot of people are using their computer as a fax today (most people don’t even have the hardware, either because they don’t have a modem, either because most modems are softmodems which do not work in Linux), this should not be installed by default.

    Update 02 april 2007: KFax will not be installed anymore from now on. Still there is kdeprintfax in default installation, which is still to much in my opinion.
  • Default digicam application: When you plug in a digital camera, you get a window asking what you want to do. The first and by default selected action is “Open in a new window”. Unfortunately this option does not work: it only shows you an empty Konqueror window. You have to manually choose the second option to open it in Digikam. But if you’ve never started Digikam before, even this option does not work flawlessly: digikam is opened, and asks where you want to create your picture collection, but it does not start the import dialog, like it does correctly the second time.
  • KDE file chooser opens in .mdk-folders: By default all KDE applications open and save their documents in /home/username/.mdk-folders/Documents. This is highly confusing, as this directory is not visible in for example Konqueror. There is actually the /home/username/Documents link to that directory. This is the name which should be shown in the KDE file chooser to not confuse users. This problem has already been reported months ago, but has been ignored

    Update 02 april 2007: This issue is currently under investigation by the Mandriva developers. Let’s hope for a fix soon.
  • Default settings in smb4k: KDE includes smb4k, a network browser for the SMB protocol, which enables users to easily connect to Windows shares. This is a fantastic application but unfortunately its default settings are not ideal: first of all, it still mounts the shares with the smbfs file system, which is obsolete now. It should be configured to use the actively maintained CIFS instead. And then I had charset problems. Connecting from a Mandriva 2007.1 system to another Mandriva 2007.1 system, both using UTF-8 locales, all special characters were lost. I had to manually configure smb4k to also use the UTF-8 file system.
  • Too much Gnome applications: We talked about Ekiga being installed by default in KDE, but that’s not all. There is also Gnucash (KMyMoney apparently is a good alternative), gnome-media (just to have a simple sound recorder, but how many people really use that?) and all of Gnome’s accessibility applications like Orca and Dasher. I can understand that one or two Gnome applications could be useful in KDE too, here it seems Mandriva is really exaggerating. For example Gnome does not include any KDE application by default (and one QT application: Scribus).
  • Klamav: Mandriva still includes the Klamav on-demand anti-virus program in KDE. This is really useless. Not only does it integrate bad with the back-end clamav (as Klamav does not use the virus databases downloaded by Clamav’s Freshclam, futhermore such an application is not very useful in a Linux desktop. Clamav is great for virus scanning on your mail gateway, but an anti-virus application for Linux itself is not necessary for now.

    Update 02 april 2007: Klamav will not be installed by default anymore.

Personally I use both KDE and Gnome, and always encouraged people to test the two, and see what they like better (if they really have any preference). Both have their advantages and disadvantages. But for now, I’ll be recommending Gnome to new Mandriva users. Mandriva’s KDE install is currently too bad to be recommended to new users. Mandriva’s Gnome installation on the other hand, is not perfect, but already very polished.