Tag Archives: kde4

Steps in the KDE development direction

I embarked on a simple investigation today:  get kdevelop setup on one of my machines so I could start learning how to develop under KDE.  The first lesson was to get my environment right (Kubuntu 64-bit 10.04):

525  export KDEDIR=/usr
527  export KDEDIRS=/usr
535  export LD_LIBRARY_PATH=/usr/lib/kde4:/usr/lib/qt4:$LD_LIBRARY_LIB
537  export LD_LIBRARY_PATH=/usr/lib/kde4:/usr/lib/qt4:/usr/include/KDE:$LD_LIBRARY_LIB
539  export KDE4_INCLUDES=/usr/include/KDE

Then came the actual coding which, once the above was done, was quite easy.  I followed the tutorial here and modified it slightly to add a custom “No” button.  Simple small step, but progress nonetheless!

KDE 4.4 Upgrade and Debug Package Problems

I find it funny the day after I make a glowing comment about support in FOSS projects, I run into a snag that is not documented anywhere.

I filed a bug on it, but was able to resolve it myself.  Trying to look at this from a newbie or non-technical point of view, I’m not sure how I would have reached the same conclusion.  I happen to know that all *-dbg packages are “debug” packages and are therefore implicitly optional.  Removing them was a reasonable step, and it happened to fix it.

However, as a normal end-user, I am not likely to have known about this.  In fact, when seeking help, I may have been asked to install these packages to gather more information about a problem.

This is not a good problem to have during an upgrade process.  But I did draw this problem down upon myself by installing packages from the backports.  However, I seem to recall this same issue when performing a supported upgrade from the previous version of the distribution (Kubuntu 9.04) to the current version (Kubuntu 9.10).

krdc, Windows XP, and bb4win

I am retrying krdc.  There appears to have been a number of nice feature changes including the ability to grab all keys which means all of my keyboard shortcuts in bb4win now work.  However, I notice a few oddities that I need to follow-up with at some point.

  1. If I have my auto-hiding panel at the top of the screen in KDE, it interferes with the krdc icon-bar restoring when I move my cursor to the top of the screen
  2. My mouse cursors don’t appear normally
  3. bbLeanSkin’s feature of edge-snapping does not work
  4. AltKey (non-bb4win) does not work — so my alt-RMB and alt-LMB mouse functionality does not work and I miss it.
  5. GoToMeeting ends up interfering with a lot of the cursor events when I am remoted in — which could just be a krdc issue

I am attempting this setup to determine if this works or if maybe a 4-port KVM might be a better option than my previously thought up crazy scenario.

Time, Money and Technology

It seems to be about time for an entry that targets the intent of this blog.  One of the problems with technology is that it usually requires time or money.  I have had little extra of either lately (beyond getting my netbook), so I think I need to establish my next set of events.

I have Kubuntu 9.04 with KDE 4.3.1 running stably on my netbook.  As noted, I needed to reinstall due to partition corruption.  I have not had any trouble since, so I suspect one of two things:  ext4 or suspending while Amarok was playing.  Thus far,  I have really enjoyed my netbook.  There is expected slowness with some things, but this is a writing and surfing machine, not something intended for enormous power.  It is a fun little machine with excellent portability.  I look forward to the day that more powerful computers are this size!

As noted, there was a suspend problem with my netbook.  Since I suspect some things that are reproducible in a VM,  I intend to give that a try at my earliest opportunity.  I think the steps to replicate the problem should be pretty straight forward.

At some point I would like to start doing some development for KDE.  In the spirit of open source, it is because some things are broken that I want fixed.  I still cannot connect to wireless networks that have their SSIDs hidden.  That is very annoying.  I might also try to pitch in on Amarok, but what I really need is time (there’s that time thing again).

Lastly, and this needs to wait until I am at “my other home” again, I need to figure out some things with DSL.  I have to say I am pretty impressed with DSL — I really had no idea how it actually worked and that it used the telephone lines instead of a dedicated line!  I found some things that my VPN connection times out on, so I need to sort that out.  That also includes hopefully getting the Cisco VPN working under Linux (Kubuntu) again.

I think that sums up my technology plans at this point.  We’ll see how that sorts out against the real world.

Static IP Configuration

I finally figured out how to get my static IP addresses set through the system configuration files.  I had to resort to this because KDE4 doesn’t have the nice networking interface that KDE3 did — they are still working on that.

There are two key files that come into play:  (1) /etc/resolv.conf and (2) /etc/network/interfaces.


me@machine:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain home
search home
nameserver x.x.x.1

This file is pretty simple.  It is the list of domain name servers that help resolve things like http://www.cnn.com into an IP address.  I had to find these values from my router, and thankfully it was picking them up automatically from my new ISP.  I also added my router (x.x.x.1) to the file so it would resolve the names of the machines locally on my network.  I still need to use {machine-name}.local as the syntax, but it works (e.g., ping machine.local).


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static

auto eth1
iface eth1 inet static

This file was trickier.  It started out like this:

me@machine:~/junk/config-files/etc/network$ more interfaces-20090809-1
auto lo
iface lo inet loopback

That’s not a lot of information to work with, so a fair amount of searching was required to figure out how to get what I wanted.  All of that information is pretty simple, and helped me understand how some of this works. I don’t think I really need to use the “network” and “broadcast” attributes, but I chose to mostly out of a copy-and-paste coincidence

The final step was a reboot, because just restarting networking didn’t work (sudo /etc/init.d/networking restart).  There must be something cached that needs to be flushed to get this to work while the machine is running.  Something else for me to noodle out another day.

While this was fun for curiosity, the primary motivation for doing this was to hopefully fix my VMware networking problem. I’ll have to test that out later tonight or early tomorrow.

KDE 4 screen edge actions

I have just recently upgraded to Kubuntu 9.04 64-bit.  It has KDE 4.2.2. in it and it has its ups and downs.  One of the great ups is the screen edge actions.  By default, the upper-left corner shows a “summary” of all the windows you have open on all desktops.  Just move the mouse up there and suddenly you see miniature versions of all your windows.

For crazy people (like me) who have too many windows open, this is a great feature.  Just click on a window, and it becomes in-focus / maximized (if not previously).