KDE 4.3 and Konqueror's Neglect

KDE 4.3 Ain't So Stable (Yet)
KDE 4.3 was released yesterday. My advice to anyone considering trying it out right now: DON'T UPGRADE! If you are going to use it, do a fresh install, unless you know how to juggle config files. Edit: I did an upgrade of KDE 4.3 on my brother's laptop, and it went smooth as silk. KDE 4.3 works flawlessly for his computer, yet mine still had/has some issues. So your mileage may vary.

While any of you that know me are aware I am an avid Linux fan (though this is really about KDE, not Linux per se), the following post has some bad new to report.

KDE 4.3 is supposed to be a stabilizing release, focusing mostly on bug fixes (over 10,000 completed) and some feature updates. That may be, but I'm afraid my experience so far has been anything but stable.

1st: I installed KDE 4.3 from the apt-repositories. Then I restarted KDE/X-Windows. KDE proceeded to start, but never showed me my desktop, just a blank workspace. Obviously KDE 4.3 did not smoothly upgrade from KDE 4.2.4.

2nd: After 30 minutes of doing a fairly straightforward but advanced detection and fix, I was able to isolate a group of the problem files and repopulate my KDE configuration files. Things progressed smoothly until I encountered the next major bug: Exiting KDE.

KDE 4.3 will NOT, under any circumstances, Shut down the computer, Restart the computer, or Log out. It simply will not do it, no matter how many times you try. Luckily I know the manual shutdown command, but that's a pretty heinous error.

3rd: Konsole. The transparency in KDE Konsole is... wait for it.... even more broken than before. I have trouble believing my eyes on this one. I'm pretty shocked it did not get fixed. Even the WORKAROUND for the bug, that has been there for over a year, no longer works now. I guess this just gives me more impetus to get back to writing my own alternative virtual terminal, because God-Damn-it, we need one fucking badly.

4th: EDIT. I fixed the problem. It was a setting configuration, though it was really damned hard to find.

5th: Be forewarned this has some rather ranting moments, so I apologize.

Konqueror is without a doubt the best file manager I know of currently. But it has been pretty broken since KDE 4.0.

Even by KDE 4.3, it still have issues, plus some new bugs. For me, the most apparent bug in KDE4 Konqueror is the utterly awful way Images are handled within it (opening, previewing, mouse previewing). Since one of my primary hobbies is collecting images, this has been a constant colossal pain in my side. I keep waiting for that be fixed but it has been 18 months now. That's pretty f**king unacceptable. (Can you tell I'm mad?)

On a less rage filled thought, Konqueror is in serious need of being updated from QT3 to QT4. Namely it needs the standard QT4 navigation bar, and god-damn-it would be nice to have meta/information panels like Dolphin does. Actually, even though I don't use Dolphin because of its imposed limitations, I like several things in it.

But there is good news. At least, partially. The KDE team has been planning to add these exact updates for a while now. It would just be nice if they actually did it.

Cursory Review of KDE 4.3
Konqueror:

• Konqueror Gestures are back. I did miss these, but ironically now I don't so much need them if I have my new mouse with 5+ buttons.
• Better Ark integration (with more menu support too).

Ark:

• Support for more formats and a few small bug fixes.
  

Gwenview (changed from version 2.2.4 to 2.3.0):

• Bug Fixes: God Almighty I hope the bugs are really fixed. They were simply AWFUL at points (way too frequently) and they should been fixed a long time ago. Really, they should have been. No excuse. Should have been done months ago.
• Plugins: In case you did not know (like most KDE 4 users), you have to install the kiki-plugins package to enable the plugins for Gwenview. As far as I can tell, nothing has changed since the prior version.
  It is still missing the most important plugin for me: Find Duplicates Images.
  
• Sidebar: Better hiding and restoration interface.
• Thumbnail Bar: Now it can be vertical, which I prefer. Nice.
• On a personal note, though Gwenview is still missing a few features I consider crucial, I really do like all the new features that have been added.
  

Conclusion
I sometimes ask myself, "Should you try using KDE 3.5 again?" The answer is mostly no. The biggest problems (that I know of) for KDE 4 has been Gwenview and Konqueror, which are two programs I use constantly, and they are usable, just not fully-functioning. If I look beyond that, KDE 4 is a great system. I can live with the small little lack of eyecandy in Konsole. Even in KDE 4.2.4, when Plasma would crash, it would do so very gracefully and almost immediately restore itself with no noticeable ill-effects.

Firefox 3.5 is finally out!

So Firefox 3.5 was finally released officially yesterday. Any of you Slashdot readers probably knew about it just slightly before I did!

If you are running Ubuntu, as every good person should, Firefox-3.5 is not in the official repositories yet. But do not despair! You can add the PPA Ubuntu Mozilla Security repository to your system and download FF35 immediately.

For full details, see here: https://launchpad.net/~ubuntu-mozilla-security/+archive/ppa

For the quick 6-step process, do the following:
(All from command line.)

1. sudo echo "deb http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu jaunty main" | sudo tee -a /etc/apt/sources.list
2. gpg --keyserver keyserver.ubuntu.com --recv-keys B9F1C432AE74AE63
3. gpg --armor --export B9F1C432AE74AE63 | sudo apt-key add -
   
4. sudo apt-get update
5. sudo apt-get install firefox-3.5
6. firefox-3.5 & # Or just start firefox-3.5 from the Run Dialog
   

You will still have firefox-3.0 on the system and in fact, it will still be the default application if you ever simply ran the command 'firefox.'

I probably will be running some speed tests here soon, and if I do, I will post the resulting comparison between the two browser versions.

Ubuntu makes Draw Tablet installation easy as could be

So I own a Wacom Cintiq 12WX draw tablet. Yes, it is a very expensive toy and I use it in Linux.

Prior to switching to Ubuntu 9.04 Jaunty, the process involved with getting my tablet to work was somewhat involved.

1. Plug in the device
2. Throw some generic config lines into /etc/X11/xorg.conf to enable the input devices
3. Compile the latest Linux Wacom Project drivers myself and load them into my kernel
4. Change my nvidia settings to accommodate my new display
5. Restart KDE
6. Enable the input device in The Gimp
   

Oh yeah: I also needed to make sure I had the darn thing plugged (usb and vga/dvi) in properly. (I have missed it a few times among all my other cables).

Not a lot of work and the compilation is pretty simple.

But now with Ubuntu 9.04 Jaunty, my job is much simpler:

1. Plug in the device
2. Change my nvidia settings to accommodate my new display
3. Restart KDE
4. Enable the input device in The Gimp

Let me tell you, it does not get much easier than this. I mean, plug it in and go!

I am having a minor configuration issue with simultaneously using my tablet input and my mouse to work on the same drawing area. It seems that somewhere along the way, the tablet input takes precedence and disables using the mouse to affect the Gimp Drawing area. I'm looking for a solution and I will post it when I know it.

Logitech diNovo Edge bluetooth connectivity issues

Sort of like USB support years ago, BlueTooth still has some bugs under Linux. Currently I'm referencing just connectivity issues. From what I can tell, this particular issue has been around in Linux since July 2007 at least according to some bug reports.

I use the Logitech diNovo Edge. This keyboard is awesome and I love it. When the dongle is not initialized as a bluetooth device - ie in bios, boot, install etc it simply emulates a usb keyboard / mouse and works (without any fancy features) perfectly. Hence, it works in text mode great. This happens during during System Startup, BIOS access or during the actually Linux console startup sequence.

However, as soon as it is initialized as a bluetooth device it forces you to use bluetooth pairing to work (this applies to Windows too). So, as you can imagine, by the time I reach KDE the keyboard doesn't work.

A solutions I have found to this problem (Source http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497):

Edit with sudo (text-editor) /etc/default/bluetooth

Then look for the line that says:
HID2HCI_ENABLED=1

and change it to this:
HID2HCI_ENABLED=0

Linux Promotional Rant - Windows Recovery versus Windows

Overview
I saw this quote in an Ubuntu Forum thread and I felt like making my own reply.

Quote source from http://social.msdn.microsoft.com/forums/en-US/hottechnology/thread/b998ea87-1857-4bd1-ba38-a202c4ce6b97/

A post by jgalley:

"You are doing an automatic upgrade of your OS and in the middle of the application of the patches the power fails and your system crashes hard. What OS do you want to be running? From my experience if it is Linux then you are about to see firsthand why Ubuntu is free and Vista costs 400 bucks.

If I have to rebuild my worstation and development environment even once then the actual cost of Ubuntu is more that the cost of Vista. In fact, for every extra time my Ubuntu system crashes hard and fails to boot I could have purchased a new Vista system from Dell, thrown my old system in the trash and still come out ahead.

Linux is the best, if what you like to do is rebuild and reinstall operating systems or endlessly search the internet for cryptic instuctions on how to edit /etc files to make some piece of hardware or software sort of work."

Yeah, I know anything from the Microsoft forums is pretty much flamebait, but let's go with this.

This entire speech totally belies the fact that in my experience a Windows Machine tends to bug-out after a sudden power loss, while nothing so palty even shakes a Linux system.

Right off, this guy is not being specific with his arguments. Let's get specific.

Harddrive Hardware Failure
When dealing with hardware failure due to spontaneous power loss, then RAID systems and backups are all you have to deal with. Shockingly those have very little, if anything, to do with the Operating System. The same goes for any other hardware you have die from the experience.

Harddrive Filesystem Failure
When dealing with software file-system problems due to spontaneous power loss, then there is no contest. Linux journaling File-Systems just win.

I occasionally see print claiming that NTFS is a journaling file-system like EXT3/4. To be bluntly honest, I don't know if I would believe ithad journaling even if I saw the source-code myself, because NTFS sure as fuck doesn't act like it has journaling.

At least not journaling like I have enjoyed with Linux file-systems. Of course, that assumes one is using NTFS, which is a fair assumption now days, but again this poster did not mention that. For all we know, there are Fat32 systems involved and let me tell you from experience, doing scandisks on huge Fat32 formated Harddisks takes hours.

Maybe it has been a few years, or maybe Vista has something magically under the hood, but no NTFS file-system I have even heard of makes serious recoveries as quickly and thoroughly as a Linux journaling file-system.

Fixing A Broken OS
What about when the OS is broken and won't boot properly. Of course, exactly *how* broken has an significant impact. Misconfigured files? Broken drivers? Broken kernal? The poster does not mention the specific methods of restoration.

He might mean throwing in some vendor provided disc and hoping its magic works. I would not know, Linux does not need these things. But since he's not specific, let's assume he means doing some manual work on a recovery console. In fact, this is very likely exactly what he means.

I need to stop here for a second and point out something: Is this n00b actually claiming it is easier to do something in the console/command-line in *Windows* than in Linux? ...? The next question of course is WTF? Yeah, let's move on. Alright, so it is safe to say it is going to be easier to do work on the console/command-line in Linux than Windows any day of the decade.

But what kind of work you ask? Well, whatever work you need to do to restore your system. Let's hope you know enough about the clearly documented and well designed Windows system architecture. Let's also hope that you can do all your recover from a console text environment and nothing requires a graphical session. At this point alone, Linux recovery is more certain than Windows, because in Linux literally anything that can be done from a graphical session can be done from a console, while the same is certainly not always true for Windows.

As for what exact work is to be done, I don't know since each situation varies but I'd like to see him edit his registry through a console Microsoft Console and call that "easy." Meanwhile I will just be using my Vim editor to modify human-readable-flat-text-configuration-files and browsing the Internet from command-line via eLinks for further help.

In Linux, one can completely recompile/reinstall anything needed without a graphical session. Debian Software Packages and shell-scripts for the win. That does not happen with all the numerous variety of Windows installer programs.

Using a boot disk, with some careful work, one can even do recompilation/reinstall for a non-booted system. I would like to see any Windows machine compile from command line as easily as Linux. Hell, I would like to see Windows compile ANYTHING as readily as Linux tends to.

Instructions
The poster mentions "Cryptic instructions." Well, I won't say Linux is easy to use as a Fisher Price toy, but few powerful tools are. Since turnabout is fair play, if he wants to talk cryptic, then let's go all the way and discuss poor instructions. This, of course, leads to Microsoft Help Files/Manuals.

I certainly will not claim every Linux/BSD Man-page ever written in the world is great and has all the information needed. But in my experience, easily 90% of the time, man-pages will give provide most if not all ones needs. I have yet to even hear of a single good Microsoft Help file. (And I have talked with career technical writers on the subject).

Of course, this side-steps the point about the architectures and system designs themselves.

Full OS Reinstall
Now, if the poster is talking about a full OS reinstall, I can fucking-money-back-guarantee-you Ubuntu Linux will be fully installed and have completed any updates with all my software installed well before Windows has the 2nd Service pack installed (if even the 1st), let alone all other personal programs and virus/firewall software.

And that does not even address the issue of live-booting. :P

Development Environment
The guy mentions rebuilding his development environment. ... I am going to assume that means installing Visual Studio, or something of the like, and a train load of additional software libraries.

I got news for the poster, in Linux that is as easy as a few mouse clicks with my package manager, or a single Shell-script execution to send commands to apt-get. In a word: Owned.

Further Laughs
This guy identifies himself as a ripened idiot by going on further to state: "In fact, for every extra time my Ubuntu system crashes hard and fails to boot I could have purchased a new Vista system from Dell, thrown my old system in the trash and still come out ahead."

Even from my longest recovery time, my time has never been equal to the couple thousand dollars to build my new powerful desktop, and certainly was not worth the recovery of my irreplaceable data files. Maybe this guy takes his computer to the Geek Squad and has to wait two weeks for recovery? (Yeah, I know they don't do Linux, but you get my point).

Lastly, what sort of piece of shit computer is he running that is worth less than $400 + New Deskstop that he casually throws away?

Shear Idiocy -- Economics of Morons
"If I have to rebuild my worstation and development environment even once then the actual cost of Ubuntu is more that the cost of Vista."

I really have to address this one. So, "free" is somehow going to become more than $400 through just one occasion? Are you fucking kidding me?

Beyond the fact that the poster is utterly failing to take into account the 10 to 1 ratio of Windows system breakdowns versus Linux, he arbitrarily states that any recovery with Linux will be more than $400. The logical converse of this argument is that any recovery with Vista will be automatically less. (And that does not even address repeated recovery costs, which Linux most definitely trumps Windows on because of better system longevity).

Is he claiming that any recovery done with Vista will be less costly (time and money and effort invested) over Linux? Really? Seriously? ...I actually think this person is claiming exactly that. Well, he's completely wrong.

Situations vary and thus recoveries do. In the 1 out of 10 situations where Linux has a problem like Windows, the situations is going to be specific and relate to the knowledge of the person doing the recovery. I am not going to claim Linux recoveries always cost less than Windows recovery because making such a blanket statement about all situation is foolishness, and the same goes for Windows over Linux.

I will just say this: Linux recoveries happen less frequently... and chances are, you can find the "cryptic" instructions online, and you will be able to access your configuration files through console easily and recompile/reinstall any software necessary. Windows can't claim that people. It just can't.

Move from VMWare to VirtualBox

If you use Virtual Machine software, in particular VMWare, this will be of interest to you. If you use Ubuntu, I suggestion you consider using VirtualBox for your VM needs and here is why. Please note, this is only talking about non-VMWare Fusion products.

I have been using VMWare for about 2 and 1/2 years now, but just recently I have decided to move to using VirtualBox.

The Reasons I Left VMWare

1. Apt-get Availability: VMWare is not available in the Ubuntu apt repositories and I have never found any other Ubuntu/Debian repos to use. It was once available via 3rd party repos from Ubuntu, but not for well over a year and a 1/2.
   
2. Compiling: Because there are no easily available apt-repositories packages, I have been compiling VMWare myself for a while. I don't mind compiling (in fact, I think it is a great and powerful feature of Linux) but because VMWare has close ties with the kernel, occasionally I would have to recompile VMWare after a kernel or kernel module update from Ubuntu. In general, the compiling was not a major annoyance but it was not convenient.
   
3. Compiling Problems: In Ubuntu Jaunty 9.04, I have not been able to compile VMWare 1.x no matter what I try. I attempted to use verrsion 2.x, but that didn't work out well.
   
4. Future VMWare Versions: I successfully compiled and ran VMWare 2.x but it radically fails to meet my needs for a Virtual Machine program. Furthermore, it fails (perhaps even spectacularly) to meet some of my most basic preferences for a program in general. I personally found its interface ridiculously slow, featureless, and extremely unusable.
   

Reasons I Moved to VirtualBox

1. Competitors: VirtualBox is the major competitor to VMWare.
   
2. Features: VirtualBox actually has a few features that VMWare does not have, such as dynamic virtual harddrive expansion and shrinking and not require full diskspace pre-allocation. VirtualBox also supports limited 3D Acceleration (both OpenGL and Direct3D), with more in development. (This feature VMWare completely lacks). I have yet to find any features missing in VirtualBox from VMWare.
3. Integration: Though my recent usage experience has not been excessive, the integration of VirtualBox into my host Linux system has been better and smoother than VMWare. In particular:
   
   • Using VMWare I had network issues when running KDE4 in a VM. VirtualBox has no such issues.
   • After installing the Guest Additions, my mouse can travel smoothly between my VirtualBox guest VM display and my desktop without being stuck/limited to the display area. (Vbox specifically informs you of this capability actually post-installation).
   • Guided steps with the GUI for sharing files between the host machine and guest VM. VMWare required mounting via commandline which worked but was somewhat buggy.
     
4. Availability: VirtualBox is available right through the Ubuntu apt-repositories. If I want a more up-to-date version, I can easily find apt-repo at PPA launchpad. (This sort of community is yet another reason why Ubuntu is so great).
5. Portability: Just like VMWare, Virtualbox runs on every major OS out there.
6. Cost: VirtualBox is free as you get. While VMWare never cost me anything to run, there may have come a day when I was faced with paying for their products. I won't have to worry about that with VirtualBox.
7. Performance: Though I have not thoroughly tested the performance, from my own experience and the reviews I have read online, VBox does not perform (process tasks as quickly) as VMWare but it certainly is not casually noticable. I know VBox is continuing to push for improvements in this area.
   

Summary
I have been using VirtualBox for about 2 weeks now and it is exceeding my needs. VBox meets my needs in a more convenient way than VMWare did before, especially after installing the Guest Additions. Though VBox has a different interface from VMWare, I think I actually prefer the organization concept and designs of the VirtualBox system over VMWare's organization, particularly with shared resources. Overall, I think it is a better piece of software.

Yet more support for Linux from NVidia and ATI

This was news to me. It makes me very happy to see this. Long story short, Nvidia and ATI/AMD are providing programming API's to allow software in the *nix world (Linux, BSD, Solaris, etc) to utilize GPUs on their hardware. Specifically,VDPAU from Nvidia and XvBA from ATI/AMD are the systems for the X Windows System. They are equivalent of the Microsoft's DirectX Video Acceleration (DxVA) API for Windows^.

Those links will give you more information if you are interested. There are several other programs I personally know of, most notable Avidemux's latest development branches, which are working to make use of this new programming API and technology. It makes me pleased to see these systems coming into place in the *nix world, breaking down yet another barrier between competing Operating Systems.

Even though the protocols from Nvidia and ATI are still limited in what they can do, I have little doubt the capabilities will be extended and based on stirrings in the Windows world, I am sure of it.