Tag: GNU+Linux

Posts tagged with GNU+Linux, GNU/Linux or GNU-Linux relate to the GNU operating system, managed primarily through the Free Software Foundation, and the Linux kernel, managed by the Linux Foundation.  GNU/Linux is the basis of most free software operating systems in use today.

Posted on
by

Here’s the deal:

1)You have no time and you want to try the latest Fedora release because it looks pretty darn good.
2) You accept the default disk partitioning scheme which the kind people at Red Hat / Fedora project set up for you, because they only have your best interests at heart, right?
3) While using this cutting-edge release, something nasty happens like, ooh, perhaps a sound driver locks up the entire system and you have to hard-reset the machine (that is, switch it off by the power switch because nothing responds to input).

What next? If, like me (on one occassion) you try to boot up the machine and get no further than the recovery console, you’d feel a bit aggravated. But there is an alternative – do a disk check. You may have read my verbose coverage for How to do a disk check in Linux before. This takes it one step further – how to check your logical volume when it’s encrypted and formatted using the latest ext4 filesystem.

Instead of the method used before, this time I booted from a Live CD. You can find one to download at the Fedora project. Ensure that this CD matches the release of the version you are trying to recover. In this case, that’s Fedora 10.
Once you have booted the offending machine up with the Live CD, open up a terminal by pointing to Applications > System Tools > Terminal. Once in the terminal window, just type:

# su

…to become the root user. This is essential to using all the disk tools.
You may be tempted to check for volume groups first:

# vgscan

.. but this would return nothing.
What’s happening here is that the Volume Group, located on that partition, is itself encrypted. Once unlocked, you can then gain access to both of the Logical Volumes – the swap volume and the root (/) volume.
To unlock the encrypted Volume Group, first you need to establish which partition it resides on:

# fdisk /dev/sda
The number of cylinders for this disk is set to 12161.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Hit p to print the partitions on your primary disk:

Command (m for help): p
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb07eb07e
Device     Boot  Start End    Blocks   Id System
/dev/sda1    *       1 5377 43190721 7 HPFS/NTFS
/dev/sda2         5378 5402    200812+ 83 Linux
/dev/sda3         5403 12161 54291667+ 8e Linux LVM

So the partiton of type “Linux LVM” (Logical Volume Managed) is the baby we’re after.
To unlock the encrypted Volume Group, use the following:

# cryptsetup luksOpen /dev/sda3 mydisk


This sets up the encryption/decryption kernel subroutines to allow access to device /dev/sda3, mapped to a device node called “mydisk” in /dev/mapper/ . We’ll not actually need to use this device node, but it could be handy to know if you needed to perform further diagnostics.
You will be prompted to enter the encryption key which is stored in one of eight “slots” on the disk. If the key you enter matches a key in any slot, your disk will become unlocked. Assuming that it is, you can then scan once again for Volume Groups:

# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2


Now we’re getting somewhere. Let’s activate the VG and display the LVs (Logical Volumes) it contains:

# vgchange -a y
2 logical volume(s) in volume group "VolGroup00" now active
# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID RE7t2h-nIy9-dWZ9-xt26-Fgq4-gFd8-34E3f2
LV Write Access read/write
LV Status available
# open 0
LV Size 47.81 GB
Current LE 1530
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID B7XJzD-9sS0-3iHx-AWBE-W9qN-TvRb-vCdYZF
LV Write Access read/write
LV Status available
# open 0
LV Size 3.91 GB
Current LE 125
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

We can deduce from the sizes of these two volumes that the first of the two is the root (/) volume, and the second is the swap volume.
As the purpose is to FIX the filesystem on it, which may have become corrupt through the hard-reset performed earlier, we do not want to mount this volume. Instead, as we now have a device node for this activated volume, at /dev/VolGroup00/LogVol00, we can simply perform a disk check straight on it.
To check which extn file system checking tools are on the system, you can tab-complete at the command line:

# fsck. (hit tab)
fsck.cramfs fsck.ext3 fsck.ext4dev fsck.vfat
fsck.ext2 fsck.ext4 fsck.msdos


As this was formatted an ext4 volume, that’s what we use:

# fsck.ext4 /dev/VolGroup00/LogVol00
esfsck 1.41.3 (12-Oct-2008)
/dev/VolGroup00/LogVol00: recovering journal
Clearing orphaned inode 730 (uid=0, gid=500, mode=0100600, size 2263160)
Clearing orphaned inode 187182 (uid=500, gid=500, mode=0100600, size 4096)
... and so on until ...
/dev/VolGroup00/LogVol00: clean, 190926/3137536 files, 2016683/12533760 blocks

Now there are two more steps to perform: de-activate the volume group, and lock the encryption of the drive.

# vgchange -a n
0 logical volume(s) in volume group "VolGroup00" now active
# cryptsetup luksClose mydisk

The second command returns nothing, which means it did not error (the disk is now encrypted and not writable-to without unlocking again).
I hope that helps someone with a sense for adventure but not enough time on their hands for when things go somewhat awry!

Posted on
by

We’re all used to doing a disk check in Windows XP.  It’s easy.  Just double-click on “My Computer”, then select the drive you want to run the check on.  Right-click, Properties, Tools tab, then select “Check Now…” in the Error-checking section.  In almost every instance you’ll be told that the check will be done upon the next reboot.  Easy.

So how does one go about it on Linux?  Well… as you may have guessed, it’s not quite so straightforward.  Linux, by default, does actually have an intelligent disk-checking system already in place. By all accounts, you generally needn’t worry.  But if you have a reason to believe your disk may be slowly dying, and nothing is reporting in the SMART status of your drive, perhaps it’s worth checking the file system instead.

That’s where File System Check comes in (duh!).  Like all Linux tools, it’s painfully abbreviated to simply “fsck”.  Terse, to say the least.  Now the warning:

DO NOT.  I REPEAT, DO NOT EVER EVER EVER RUN THIS COMMAND WHILE YOUR DRIVE IS MOUNTED (I.E. IN USE).  I TAKE NO RESPONSIBILITY FOR ANY LOSS OF DATA THAT YOU MAY CAUSE BY FOLLOWING THESE INSTRUCTIONS.

To unmount your root (/) volume, follow these easy steps:

  1. Boot from a Live CD. Your root volume will not be mounted by default.
  2. Open a terminal and type:# dmesg | grep sda If you see output relating to your “SCSI” device, then this will identify that your hard disk, in all likelihood, contains your root partition. For example, amongst other output, I see this:
    sd 2:0:0:0: [sda] Assuming drive cache: write through
    sda: sda1 sda2
    sd 2:0:0:0: [sda] Attached SCSI disk

  3. In the example above, we see that SCSI disk 2 (2:0:0:0:) the Linux kernel registers it as the first logical drive (“sda”) in the system.  We can also see it has only 2 partitions, sda1 and sda2.  If this is the only physical drive in the machine, we should strongly suspect that it uses one partition as /boot (formatted with ext4) and the other as a Logical Volume containing both root (/) and swap. Furthermore, it’s foregone conculsion that the smallest partition will be /boot and the larger one will contain our swap and / partitions, so let’s proceed with accessing them.
  4. So, how do we access a “Logical Volume” within an equally mystical “Volume Group”?  Luckily, Linux LVM comes with a plethora of useful tools to make the job easy.

    # /sbin/vgscan
    Reading all physical volumes. This may take a while...
    Found volume group "VolGroup00" using metadata type lvm2     Great. We have identified the volume group.  But before we can identify the logical volumes it contains, we need access it.
    # /sbin/vgchange -a y
    2 logical volume(s) in volume group "VolGroup00" now active
    Here, the -a flag indicates that we want to change the “active” status of the volume group, and the y means “yes”.
    # /sbin/lvdisplay
    --- Logical volume ---
    LV Name                /dev/VolGroup00/LogVol00
    VG Name                VolGroup00
    LV UUID                DG2WxJ-sKa5-20mg-NtjW-CsPW-t99V-Egqlja
    LV Write Access        read/write
    LV Status              available
    # open                 0
    LV Size                7.25 GB
    Current LE             232
    Segments               1
    Allocation             inherit
    Read ahead sectors     auto
    - currently set to     256
    Block device           253:2
    --- Logical volume ---
    LV Name                /dev/VolGroup00/LogVol01
    VG Name                VolGroup00
    LV UUID                HqKozT-16PQ-HUaT-Yyc7-lMCO-007m-Xcc2c8
    LV Write Access        read/write
    LV Status              available
    # open                 1
    LV Size                512.00 MB
    Current LE             16
    Segments               1
    Allocation             inherit
    Read ahead sectors     auto
    - currently set to     256
    Block device           253:3
    We can now see two partitions contained within the volume group. The first partition, although small by today’s standards, looks a lot larger than the second.  We can also see that each logical volume has a device node (/dev/VolGroup00/LogVol01, for example).

    As we want to perform the disk check without the parition being mounted, we do not issue any mount command here.  However, if you wanted to double-check that this is the partition to check, mount it and have a quick look around.  The following step is only offered to help in this case – skip this if you wish to perform a disk check.

    # mkdir /tmp/lv0

    For me, the first logical volume (the 7.5GB one) would be the one to test.
    # mount -t ext4 /dev/VolGroup00/LogVol00 /tmp/lv0
    # cd /tmp/lv0
    # ls
    bin  boot  dev  etc  home  lib  lib64  lost+found  media  mnt  opt  proc  root  sbin  selinux  srv  sys  tmp  usr  var

    Ok, that looks like the root partition, so let’s get out of it and unmount it before running the file system check on it.
    # cd /
    # umount /tmp/lv0

  5. An alternative to the above steps, if you have already booted into your main system, is to investigate /etc/fstab to see which is your / volume.  All you do is open a terminal and issue: # cat /etc/fstab On my CentOS 5 system, I see this:

    /dev/VolGroup00/LogVol00 /                      ext4    defaults        1 1
    LABEL=/boot1            /boot                   ext4    defaults        1 2
    tmpfs                   /dev/shm                tmpfs   defaults        0 0
    devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
    sysfs                   /sys                    sysfs   defaults        0 0
    proc                    /proc                   proc    defaults        0 0
    LABEL=SWAP-sdb1         swap                    swap    defaults        0 0

    So, /dev/VolGroup00/LogVol00 is my root volume.

So, now that that’s out of the way, what next?  Well, assuming you now know which is your root partition, the most sensible thing to do would be to boot from a Live CD of some distribution (Ubuntu, Fedora, etc) if you haven’t done so, and then perform the disk check from that.

Once in the LiveCD desktop, we’ll need to fire up a Terminal window.
If you know your filesystem type, e.g. if it’s Ext4, which is the default on the most common distributions, you can run a modified version of the fsck command specifically for that file system.  Here’s what I run for a thorough disk check:


# fsck.ext4 -c -D -f -P -v /dev/VolGroup00/LogVol00
Alternatively, if your partition structure is slightly older and only contains physical paritions (not Logical Volumes), it may just be a case of finding the partition directly – by checking /etc/fstab on the system when running. In that case, your command may look more like this (when / is unmounted!!):
# fsck.ext4 -c -D -f -P -v /dev/sda2


Here’s what the flags do:
-c  – forces a bad block scan.  Although bad blocks are remapped dynamically by the file system, if the file system or its journal are corrupt, this may not work correctly.
-D  – performs a directory check and optimisation.  Doesn’t hurt, and can speed up directory listings of a large number of files.
-f  – forces the check itself to actually run.  As mentioned previously, the file system maintains itself quite well, and if you don’t force the check, fsck may look at the last check interval and decide a check is not required.
-P  – perform all file system fixes automatically.  This is usually a safe flag, but if your file system is potentially very corrupt, this may not be advisable.  In this situation, contact an expert – or restore your back-up… ;-)
-v   – verbose output. See what’s going on.
/dev/VolGroup00/LogVol00 or /dev/sda2 – this is the partition I want to perform the disk check on.

This little guide doesn’t explain how to perform a check on an encrypted logical volume… That one’s coming. :-)

Updated from post originally put here: http://onecool1.wordpress.com/2008/09/19/how-to-do-a-disk-check-in-linux/

Posted on
by

Fedora 16 is here.  With all GNU/Linux distributions, newer versions generally mean better hardware support, usability and so on.  Unfortunately, for users of netbooks, laptops and basically any hardware that contains Realtek’s 8192e wireless chip, things can still be problematic.

I posted, previously, a rather kludgy solution to fixing this in Fedora 14.  Then 15 came along, and the fix I was using then no longer worked.  This is because my previous solution installed the Linux kernel staging drivers for a kernel version very similar to that running in Fedora 14 (but actually built for Ubuntu).

Now that we are 2 versions of Fedora down the road (12 months, then), is the situation better for the humble RTL8192e_PCI ?  Sadly, no.  The main problem is that the 8192e driver is still in the Linux driver staging tree rather than in the main code line.  In the respected opinion of the Linux kernel developers and testers, this means the code isn’t good enough to be enabled by default.  Quite when it will be “ready” to hit the trunk, I’m not sure. 

In the meantime, this means you have to install the kernel’s development modules (staging drivers).

This is quite simple in Fedora:

  1. Enable the RPMFusion repository by following instructions here:
    http://rpmfusion.org/Configuration
  2. Then, as root, install the kmod-staging package:
    # yum install kmod-staging

Posted on
by

This problem has been reported for other systems – Jayway covers 64-bit Ubuntu, which is where I derived most of the info I needed (thanks guys!).

If you are developing Android apps using Eclipse, especially on 64-bit Fedora 16, then you too may have come across the error message:

Failed to get the adb version: Cannot run program "/home/[user]/[path]/android/[sdk]/tools/adb": java.io.IOException: error=2, No such file or directory

I did.

To fix it, you need to install 32-bit compatibility libraries.  On Ubuntu (and probably Debian) you can use the getlibs tools.  For Fedora users, it requires installing a few bits and pieces.  Easily accomplished with this:

su -
yum install libstdc++.i686 ncurses-libs.i686
 compat-libstdc++-33.i686

Yum will pull in the necessary dependencies.

Restart Eclipse and the error should disappear.

Posted on
by
ThinkPad T420.  Shiny and new.

It is with incredible reserve that I discuss my new Lenovo ThinkPad T420, such is my excitement.  As a natural born geek, software developer and sysadmin, there is something about a ThinkPad which is “just right”.

The lure of a ThinkPad is unquestionable.  It’s the promise of your best bit of code ever.  It’s the idea that it’ll be with you for years; your faithful companion.  It’s the reassurance of industry-leading build quality and top-spec engineering, using high quality components.  But it’s more than that too.  It’s an identity, a bit like that of Apple users – but thankfully in more self-respecting way.  You have a ThinkPad, you join an elite.  It’s everything you want.

You want this so badly that it comes as a bit of a surprise when all is not quite what it seems.

Branded accessories – one of those indulgences.

Better the devil?

As Lenovo only offer such spiffing hardware bundled with a throwaway operating system, you must suffer the wasted hours and ridiculous horseplay that ensues from such choices being made for you.  We are all too familiar with this scenario… so, I’ll continue!

Here is my experience, abridged:

  • Unbox, connect battery, plug in power, switch on.  It switches itself off.  And then back on – phew! 
  • Windows 7 starts up and completes its install process.  You are prompted to answer a few questions along the way:

  • Do you wish to use Norton to protect your PC?  I choose No.  
  • It prompts again: “Are you really, really sure you don’t want to use Norton???”.  I really, really confirm that yes, I don’t want to use Norton, thanks all the same.  
  • Further into the installer, you are prompted to accept the Windows EULA (end user licence agreement).  At the same point, you are also prompted to accept the Lenovo warranty terms.  You cannot proceed if you choose only one.  I imagine that this is another Microsoft “initiative”, a bit like Restricted Boot, which attempts to force people (through fear, usually) into sticking with Windows.
  • Finally, it finishes setting up Win7 and loads up the desktop.  On the offchance that there is a warranty issue, I decide to make a backup using Windows Backup.  Unbelievably, the Windows partition (C drive) contains 26.39GB of data.  WHAT??!!  This is a freshly installed operating system.  How on earth can it consist of so much… bloat?!  There is also a system partition (1.6GB, of which 900MB or so is used) and a Lenovo recovery partition (17GB, of which 9GB is used).  So, I have 36GB of disk space used up for a fresh install of Win7, plus some Lenovo utilities and Google Chrome (installed by default – the only good software choice made by Lenovo so far).   Hesitantly, I begin the backup process to Verbatim DVD+R discs.
  • 3 hours later, now on the 4th disc, the back-up process fails.  The error given is unspecific.  I now have a collection of 4 shiny new drinks coasters.
  • I dig into the Lenovo software and find that I can install “Rescue and Recovery” software, presumably from the Lenovo recovery partition into Win7.  I install it, which takes about 4-5 mins on this core i7 2640 machine.
  • Oh, wait a sec, what’s that?  Some pop-up just appeared above the clock in the right hand corner.  Something about Norton doing something, was that?  Oh, it’s gone.  So, despite being really, really clear that I did NOT want Norton installed on my machine, er, there it is.  Installed on my machine.  Poor Lenovo, poor.  And it gets better.
    • Creating recovery media fails.  Classic.
  • I fire up R and R and find the option: Create Recovery Media.  This looks more promising.  I fire it up, stick in a DVD+R (still have 6 left, hopefully that’s enough..).  It starts off, “extracting files”.  And then stops, and fails.  Apparently, in this instance, I may be able to expect Lenovo to ship me out some recovery CDs.







    • Not to be

    So far, any reasonable, sane person would not feel very confident using Win7 on this machine.  The dream probably wouldn’t be shattered, but clearly the software configuration is dysfunctional, ignoring user preferences and showing some worrying reliability issues out of the box.

    Luckily, being part of an elite means that you don’t follow the masses.  The throwaway software, bundled with the machine, is designed for people who don’t, won’t or can’t think.  It’s also designed for those who blythely accept it, probably “because it’s safer”.  Well, luckily for Windows users it must be a lot safer now that Norton is installed, regardless of your wishes!  Phew!

    To be

    Fedora 16 live CD, running on this T420.

    The alternative, as always, is to not accept what you are given.  Instead, seek a better solution that you can feel confident in.  For this ThinkPad T420, the better solution is GNU/Linux, Fedora 16 flavour.

    Here is how easy Fedora is:

    • You download a live CD, burn it to disc and restart the computer.
    • The CD boots up into a “live desktop” (this doesn’t affect any data on the hard drive).
    • From the live desktop, you run software (e.g. Firefox) as if it were installed on your computer.  On the ThinkPad, all hardware is automatically recognised and usable immediately.
    • From the live desktop, you have the option to install this software to your hard disc.  How refreshing: choice.

    But don’t take my word for it, try it yourself.

    If, that is, you have the mind to.

    Posted on
    by
    Tux, as originally drawn by Larry Ewing 
    Tux – your faithful free-software friend

    It might seem a long way off, but Saturday 5 April 2014 represents your best, last opportunity to ditch that ageing Windows XP and upgrade to a modern, capable, free and secure operating system: GNU/Linux.

    Microsoft are dropping support of Windows XP on Tuesday 8 April 2014.  After then, the numerous security issues that XP will face will go un-patched.  Anti-virus vendors, firewall software writers… basically everyone in the proprietary software world will no longer support Windows XP.

    In the meantime, Microsoft is doing its best to urge businesses to migrate to a newer version of Windows(1).  Note that the term used is “migrate”, not “upgrade”.

    It is claimed(2) that Windows 7 has overtaken XP as the most widely used Microsoft desktop operating system.  Whether this is credible or not, Microsoft is not one to pass up an opportunity to tell companies on XP not to wait for Windows 8(3).

    This is perhaps the best advice they have given:  there are so many freely available secure operating systems available right now, which will run eficiently on current PC hardware, that there really is little point waiting for anything.  There is, of course, an enormouse number of free applications to run on them too, of which here is a highlight.

    Of course, you would wait until Saturday 5 April 2014 to update your computer software but, actually, why wait at all?  You can install Linux alongside Windows to dip your toes in before committing fully.  All you need to do is visit one of these and follow the installation documentation:

    Don’t worry – Microsoft is far more afraid of you getting your feet wet than you are.   If you have any questions, there are loads of resources available to help.  Try a Linux User Group (usalug.com / lug.org.uk), or maybe start on a forum (www.linuxforums.org, www.linuxquestions.org, www.linux.com/community/forums).  Of course, as a business user you may want to opt for enterprise support.  You can find that here: Red Hat Enterprise Linux – and here: Ubuntu for Business.

    Choosing to upgrade from a proprietary operating system to a free operating system can seem hazardous, but rest assured – you are not the first to try!  Millions have gone before you, and millions will come after.  With open source software, there is strength in numbers and these numbers increase daily.

    Come and join in – and try not to have a lot of fun! 😉

    Enhanced by Zemanta

    Posted on
    by

    I recently upgraded to Fedora 15 on my netbook (a Samsung N130).  For a while I used Ubuntu 10.04 (nice and quick, reliable wireless, good battery), then 10.10 (bit slower, still reliable, reasonable battery) and then 11.04 (sadly a bit more sappy towards the battery and – subjectively- more laggy too).

    But saying that, I like Ubuntu 11.04 in many ways.  I think Unity is good, despite much antipathy towards it elsewhere on t’internet, and the intregration of social networking, media player, messaging and so on makes for a pretty swish experience.  One problem that started plaguing it on my netbook, however, was that wireless became increasingly unreliable.  Sometimes I’d have to reboot multiple times to get a conneciton to my Access Point.  Connecting to wireless when coming out of standby never worked, period.  

    The netbook contains a Realtek RTL8192e wireless chip – a problem in Linux due to Realtek not really pushing development as proactively as possible into the Linux kernel.

    So, what to do?

    If you’re reading this then you’re probably thinking you have two options:
    1) Struggle for an eternity to get the native Linux driver working properly, or
    2) Install ndis-wrapper, download the Windows driver binaries and use that instead.

    There were the options I felt I had after reading this fedoraforum thread  (F15, RTL8192 and Staging Drivers) and this thread too (F14 RTL8192E Staging Driver).

    I almost swayed completely to option 2), but as if by magic I managed to get option 1) working.  This was mainly thanks to this ubuntu forum post.  In the post is a link to a download with the native linux RTL8192e driver files (I have taken the liberty of copying this archive and uploading here, in case that link stops working).

    Here’s what I did:

    In a terminal, type (as root)

    # yum groupinstall “Development Tools” -y

    Then, as your normal user:

    # wget http://www.dirk-hoeschen.de/temp/rtl819Xe.tar.gz
      (or my link, above)
    # tar xfz rtl819Xe.tar.gz
    # cd rtl819Xe

    Then, again as root:
    # ./install.sh
    (this step compiles the driver and loads the resultant kernel module)

    Because Linux loads drivers (modules) dynamically, the device is brought up immediately.

    My wireless card was then recognised and visible in Network Manager.  My access point was recognised and easy to connect to.  I have noticed that negotiation times are a bit longer than before, but I can confirm that after a little testing I can now put my netbook into standby, then awaken it and hey presto! my wireless reconnects automatically.  This is not a fringe use case; I for one am very glad this works as it should now.

    Unlike the ubuntu post, I didn’t download the latest sources to compile.  I just went with the files in the archive. If you have difficulties, it may be worth investigating this – YMMV.

    Although Fedora 15 was a pain to start off with, due to this issue, I found that once sorted it’s now becoming a real joy to use.  The extended battery life is really something to behold too – I’m getting a 20-30% increase in operating time now (up to 4 hours instead of 3 on Ubuntu 11.04).

    Hope this helps someone out there.  If not, you may still want to follow some ndis-wrapper instructions – this might be a better alternative for you.

    Good luck!

    Posted on
    by

    Thunderbird and Firefox are GTK+ apps.  GTK+ is a windowing toolkit that GNU/Linux application developers tend to use when creating software on the GNOME Desktop Environment.

    If you decide to switch to an alternative desktop environment, such as KDE, the default settings for GNOME/GTK applications may be ignored.  This is because KDE uses the Qt windowing toolkit instead.

    To fix this, you need to do it tell KDE to pick up the GTK settings and apply them to your GTK apps.

    In Fedora/CentOS, this is simple:

    # yum install qtcurve-gtk2.x86_64

    Then in KDE, point to Kicker (the application menu) > system settings > Application Appearance > GTK+ Appearance

    Change the Widget Style (dropdown) from Redmond to qtCurve.

    More information for Ubuntu users is here:

    Posted on
    by

    Ok, so I check my email first thing on Wed 16 Feb to find a message from a close friend.

    “What’s that email all about then mate?”, he asks.  “No idea – which email?” I reply.

    Turns out, it was this email (I have removed private email addresses, etc):

    Join me on Ecademy

    Connect to the right people
    Market your business
    Grow revenue

    photo Steve Dowe
    @dot.com>
    		Upgrade to PowerNetworker
    7 day FREE Trial
    ps. Join today and receive a free trial PowerNetworker subscription>

    This email was sent to
    To avoid receiving these emails in the future go to
    http://www.ecademy.com/blockinvites.php?e=
    The Ecademy Limited. Registered in England and Wales. Company Registration:3651083 VAT:718037736    @dotcom>    @domain.com>

    So, from a contact list I’d imported probably 2 years ago, since which I’d downgraded from a PowerNetworker to a Free member, suddenly is sent a whole load of invites to people I’ve not spoken to.  This is not good.

    Now, before the critics chime in, yes I know that the terms of importing the contact list are that ecademy will send out invites on my behalf.  This is not an issue – I agreed to that…2+ years ago.  A lot changes in that time.

    Miffed as I was that this had happened, I considered blogging about it and finally let it lie … until the same message was again dispatched, early this morning (24 Feb), to the 180-odd contacts who had not yet responded or read their email.  This, in my book, is tantamount to spamming.  “Oh, you didn’t buy my product?  Here, try again…”.  Ad infinitum.  This, a happy member does not make (especially since finding out that a customer of mine has received 3!).

    So, sorry to all the contacts past and present who have endured these messages.  At least I was able to obtain the list of contact data back out of ecademy so that I could message everyone separately and invite them personally to LinkedIn.

    Let me just say, however, that despite this I have otherwise been happy using ecademy.  Support has been good and the web site is useful in connecting people.  But this method of increasing memberships is a little too covert for my liking, and the time is coming for one or more new platforms in business/social networking, with open, user-controlled features and content.

    In the meantime, I await with interest, the outcome of my correspondance with ecademy’s support team:

    Sent 24 Feb 2011

    Hello,

    I wish to close my account.

    Can you also promise that the details of people who are in my contact list, but who are not members of ecademy, will be removed from your database?

    I look forward to hearing from you.

    Many thanks,
    Steve

    Update – 24 Deb 2011

    Well, an automaton can do that for me too! I quote:

    Delete Your Account

    Deleting an account is a major step. Once the account has been deleted, you will not be able to re-join using the same email address. All your records, contacts, posts, comments and messages will also be deleted. Deleted records cannot be recovered.

    This process is irreversible.
    Are you absolutely sure you want to do this?
    As an alternative, Click on ‘No. Just hide my profile’ to hide your profile and turn off all email messages, leaving your account intact.
    If you definitely want to be permanently removed from Ecademy, type in your password, check the confirmation box and choose the ‘Yes. Please delete my account’ button below.