64-bit Arch and KDE 4.2 on ext4

I wrote my this post last Sunday, but completely forgot to actually publish it.  In any case, I’ve been running x86-64 Arch on an ext4 partition with KDE 4.2.3 since. It has been interesting, to say the least.

  • Arch: I must say I’m not really happy with the way Arch users have to hack around hal, PoliciKit and Xorg to get their keyboard working these days. Apparently, Xorg input hotplugging is in a case of flux these days, and the solution is to add some fairly complex lines in multiple config files. It works, but trial and error is not much fun when your mouse and keyboard refuse to do anything and you can’t get out of X.
    Otherwise, no problems whatsoever. Arch remains my favourite distribution by far.
  • ext4: I’ve been installing Ubuntus, Mintses and Arches using ext4 filesystems on laptops and desktops galore, and never had a problem. They only thing that’s very noticable is the speed boost. Moving on.
  • x86-64: A first for me. Can’t really comment on any speed difference. The system is very snappy, but that can be because of a number of reasons. In any case, I haven’t encountered any problems, not even with flash, with works very well in 64-bit these days. Only one footnote: Arch doesn’t provide a 64-bit wine package. Installing the 32-bit version is possible from AUR, the user repository, but also installs 32-bit libraries. Again, it works.
  • KDE 4.2.3: Ah, here’s the really interesting one. I’ve been enthousiastic about KDE4 before, but I haven’t really installed it as my day-to-day-desktop. Usually I install it, look around, tweak some stuff, and then run back to Openbox. Not this time, I vowed. I promised myself to use KDE at least a week. What’s more, I wouldn’t use my favourite GTK-apps, but I’d stick to the defaults provided by KDE as much as possible.
    Well, we’re half way, and I can’t say there haven’t been any difficult moments. Figuring out how to add custom keyboard shortcuts was one. Struggling with Konqueror, Kopete and Amarok were others, and I still don’t know if the latest k3b (alpha) is actually capable of burning anything. Configuration issues aside, I also hit a couple of crashes and lockups, which definitely doesn’t happen as much in GNOME or my own Openbox. Konqueror dissappeared on me sometimes, some Plasmoids made Plasma crash entirely, caused weird skipping issues in Amarok, or simply didn’t work as intended, and Juk frequently planted itself handling my 5000+ mp3 collection. I have been able to work around almost all of these issues, but it’s apparent KDE4 is still rather young and wobbly on it’s feet.
    And while I succeeded (I still use KDE), I’ve also failed (I installed GTK-apps). I’ve said something like this before, but I still think that the main problem KDE has is the fact that its applications simply aren’t as good or as many as the GTK ones. I had to trade Kopete for Pidgin, Konqueror for Firefox, and Koffice for OpenOffice, not because I didn’t “like” them (I don’t, but that didn’t stop me using them), but because of bugs and crashes forced me to do so. I plan to go into this with a series of posts, comparing Qt and GTK software in different areas. The first one should be about Kopete, Pidgin, and Emesene, but I’ve never been good with writing series (I hate deadlines 😉 ).
    In the end, what’s important is that after compromising a bit, I still use KDE. It’s possible that I switch back to Openbox after the week is over (for example, if K3b really can’t burn yet), but I don’t plan to. I like my desktop very much the way it is now, and I’ve been able to impress my co-workers with the following screenshots. KDE makes your peers like you! Try it out now!

    Arch and KDE 4.2

    Arch and KDE 4.2

    Alt-Tab in KDE 4.2

    Alt-Tab in KDE 4.2

    San

Advertisements

7 Responses to 64-bit Arch and KDE 4.2 on ext4

  1. flammenwurfer says:

    I try to stick with qt apps if at all possible but it doesn’t always work out that way.

    I’ve been trying to use Arora (web browser). It’s a qt browser that I like, but there are a few things I don’t like about it (attaching files in gmail doesn’t work and is kind of a deal breaker) so I’m not sure if I’ll stick with it or not.

    Like you’ve noticed the KDE 4 version of K3B is all screwed up and last I checked wasn’t being worked on very quickly. I have the KDE 3 version installed for now.

    I’m sticking with KDE 4 for 2 reasons. It’s very good looking. It’s becoming faster, more stable, and more flexible with every release. I guess that’s more like 4 reasons, haha.

  2. Sam Weston says:

    Great post. I need to get around trying KDE again. Just a note, that afaik the is no 64 bit wine at this point in time. It’s still under heavy development: http://wiki.winehq.org/Wine64

    That would probably be why arch has to 64-bit wine package 😛

  3. lefty.crupps says:

    My KDE 4.2.2 on Debian 32bit doesn’t seem to have the stability issues that you have, not even close. I expect that its either a 64bit issue or (more likely) the Arch packages are in need of some stabilization.

    I’ve not yet tried the newest K3b so I cannot comment on that, but the rest work fine for me. The only ‘GTk apps’ that I generally use are Firefox (and Iceweasel, as I have both), OpenOffice.org, and Handbrake. And I think only Handbrake is a true GTk app, but I may be wrong. Kopete is much better than Pidgin for me.

  4. […] 64-bit Arch and KDE 4.2 on ext4 I wrote my this post last Sunday, but completely forgot to actually publish it. In any case, I’ve been running x86-64 Arch on an ext4 partition with KDE 4.2.3 since. It has been interesting, to say the least. […]

  5. […] just say that and not back it up. In fact, I’m not even sure if I’m right! Because I’m using KDE 4.2 at the moment, I thought this would be an ideal time to really test some Qt and GTK applications […]

  6. […] have changed the background to the one I also used in KDE, and figured Clearlooks (Openbox and GTK theme), and GNOME-brave (from GNOME-colors) go very well […]

  7. […] My earliest posts complained about issues with the nVidia driver, crashing plasmoids, KDE simply failing to start,  Kwin effects leaving artefacts, and systray icons that look […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: