Well that didn't go well. Every attempted install failed. (And there are four all up). However I should point out that I didn't follow the procedure to the letter and tried the update to a working Akamaru during the first round.
Anyway, I've decided to move to a dock which is a little less fiddly to install. So I killed the kiba-dock downloads folder (and installation - I hope) with one line of code:
sudo rm -r kiba-dock
Note - if you want to kill a nested folder you have to navigate there first with cd.
Wednesday, May 12, 2010
Tuesday, May 11, 2010
Cairo dock anyone?
The best docks for Ubuntu.
Latest deb packages for Cairo Dock.
But there's no need to follow that link, because you can download and install Cairo-dock via synaptic.
Latest deb packages for Cairo Dock.
But there's no need to follow that link, because you can download and install Cairo-dock via synaptic.
putting the physics back into kiba-dock
I've just installed kiba-dock using the instructions from my install of Hardy Heron. Unfortunately the sensational elastic snooker-ball effects weren't in evidence. To fix this, I'm going to follow the different install procedure I found at HOW TO: Install Kiba-Dock in the Ubuntu forums.
First of all, remove all existing kiba- and akamaru programs via synaptic (and delete their folders).
The next step is to install the build dependencies with this code:
* sudo aptitude remove automake1.4
* sudo apt-get install fakeroot automake1.9 build-essential libpango1.0-dev libgtk2.0-dev libgconf2-dev libglitz-glx1-dev librsvg2-dev libglade2-dev libxcomposite-dev subversion libtool libgtop2-dev python-gtk2-dev libgnome-menu-dev libgnomeui-dev libgnomevfs2-dev intltool libxml2-dev libglitz1-dev libcairo2 libdbus-1-dev libgtop2-7 libgnomevfs2-0 libgnomeui-0 librsvg2-2 python-feedparser libasound2-dev libsdl1.2-dev libdbus-glib-1-dev libgstreamer-plugins-base0.10-dev libgstreamer0.10-dev libgstreamer0.10-0 pidgin-dev libpurple-dev
Then make the directory into which kiba-dock will be installed:
* mkdir kiba-dock
* cd kiba-dock
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/akamaru/ akamaru
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-dock/ kiba-dock
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-plugins/ kiba-plugins
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-dbus-plugins/ kiba-dbus-plugins
For the physics, you need this code:
* svn update -r 602 *
Next enter the following code, typing each line at a time:
cd akamaru/
./autogen.sh --prefix=/usr --exec-prefix=/usr
sudo make install
cd ..
cd kiba-dock/
./autogen.sh
sudo make install
cd ..
cd kiba-plugins/
./autogen.sh
sudo make install
cd ..
cd kiba-dbus-plugins/
./autogen.sh
sudo make install
cd ..
Now all you have to do is type 'kiba-dock' into a terminal.
To start kiba-dock on login, go to System -> Preferences -> Sessions and click 'add new' under the start-up tab.
Name = Kiba-Dock
Command = kiba-dock
First of all, remove all existing kiba- and akamaru programs via synaptic (and delete their folders).
The next step is to install the build dependencies with this code:
* sudo aptitude remove automake1.4
* sudo apt-get install fakeroot automake1.9 build-essential libpango1.0-dev libgtk2.0-dev libgconf2-dev libglitz-glx1-dev librsvg2-dev libglade2-dev libxcomposite-dev subversion libtool libgtop2-dev python-gtk2-dev libgnome-menu-dev libgnomeui-dev libgnomevfs2-dev intltool libxml2-dev libglitz1-dev libcairo2 libdbus-1-dev libgtop2-7 libgnomevfs2-0 libgnomeui-0 librsvg2-2 python-feedparser libasound2-dev libsdl1.2-dev libdbus-glib-1-dev libgstreamer-plugins-base0.10-dev libgstreamer0.10-dev libgstreamer0.10-0 pidgin-dev libpurple-dev
Then make the directory into which kiba-dock will be installed:
* mkdir kiba-dock
* cd kiba-dock
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/akamaru/ akamaru
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-dock/ kiba-dock
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-plugins/ kiba-plugins
* svn co https://kibadock.svn.sourceforge.net/svnroot/kibadock/trunk/kiba-dbus-plugins/ kiba-dbus-plugins
For the physics, you need this code:
* svn update -r 602 *
Next enter the following code, typing each line at a time:
cd akamaru/
./autogen.sh --prefix=/usr --exec-prefix=/usr
sudo make install
cd ..
cd kiba-dock/
./autogen.sh
sudo make install
cd ..
cd kiba-plugins/
./autogen.sh
sudo make install
cd ..
cd kiba-dbus-plugins/
./autogen.sh
sudo make install
cd ..
Now all you have to do is type 'kiba-dock' into a terminal.
To start kiba-dock on login, go to System -> Preferences -> Sessions and click 'add new' under the start-up tab.
Name = Kiba-Dock
Command = kiba-dock
show me the splash screen
A small thing that irked me was the absence of splash screen (aka Plymouth) on boot-up. I put the advice from two entries in the Ubuntu forums together and came up with this solution:
* type the following lines separately into a terminal, pressing 'enter' after each:
sudo bash
xxxx (password)
echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
update-initramfs -u
He presto! Splash screen.
Unfortunately there is still a slight delay before the splash graphic displays, and the boot-up process is slightly longer. But I'll live with that.
* type the following lines separately into a terminal, pressing 'enter' after each:
sudo bash
xxxx (password)
echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
update-initramfs -u
He presto! Splash screen.
Unfortunately there is still a slight delay before the splash graphic displays, and the boot-up process is slightly longer. But I'll live with that.
Mounting Windows Partitions in Ubuntu
I found the following details at: Mounting Windows Partitions in Ubuntu.
1. install ntfs-config;
2. go to System > Administration > NTFS Configuration Tool to launch it;
3. when asked "type what directory you want the drive to appear in", /media/Windows is a good choice;
4. The window hiding behind that one allows you to enable write support for the device, too;
1. install ntfs-config;
2. go to System > Administration > NTFS Configuration Tool to launch it;
3. when asked "type what directory you want the drive to appear in", /media/Windows is a good choice;
4. The window hiding behind that one allows you to enable write support for the device, too;
Monday, May 10, 2010
solving the media maze
If you click an mp3 file in Lucid (or just import one into your Rythmbox library), you will be prompted to download the necessary codec. The same will not happen for a wma file. For that you need to go to the Medibuntu site. There you will find a link to Lucid packages, and from there to the Windows 32-bit codecs.
Manually download the deb file and install it. (Enabling Medibuntu as a repository in Synaptic will provide updates, but I don't see the need for that.)
Manually download the deb file and install it. (Enabling Medibuntu as a repository in Synaptic will provide updates, but I don't see the need for that.)
Sunday, May 9, 2010
Ubucleaner
With the passage of time, an Ubuntu system can become a little clogged. Ubucleaner is a shell script which lets you clean your Ubuntu system by removing the following:
apt cache
Config file for Uninstalled .deb packages
Unused Kernels
APT Cache
APT is the package management tool which is used to install/upgrade and remove packages in your Ubuntu system. If you use it often then it’s cache consumes a lot of space. By removing the apt cache you get plenty of free space.
Config Files For Uninstalled .Deb packages
Suppose you downloaded a package for any software and it did not work. Many users forget to delete such packages. The Ubucleaner takes care of such packages and throws them out of the system.
Unused Kernel
There could be more than one kernel present in your system at the same time. But only one will be functional. This script gets rid of all unused kernels to free up system space and keep your system neat and clean.
How To Use The Ubucleaner
Its very simple, open the terminal and run the following two commands sequentially:
wget http://www.opendesktop.org/CONTENT/content-files/71529-ubucleaner.sh
sudo chmod +x 71529-ubucleaner.sh
Now run the script with the following command and it will take care of all the things mentioned above: sh 71529-ubucleaner.sh
More details.
apt cache
Config file for Uninstalled .deb packages
Unused Kernels
APT Cache
APT is the package management tool which is used to install/upgrade and remove packages in your Ubuntu system. If you use it often then it’s cache consumes a lot of space. By removing the apt cache you get plenty of free space.
Config Files For Uninstalled .Deb packages
Suppose you downloaded a package for any software and it did not work. Many users forget to delete such packages. The Ubucleaner takes care of such packages and throws them out of the system.
Unused Kernel
There could be more than one kernel present in your system at the same time. But only one will be functional. This script gets rid of all unused kernels to free up system space and keep your system neat and clean.
How To Use The Ubucleaner
Its very simple, open the terminal and run the following two commands sequentially:
wget http://www.opendesktop.org/CONTENT/content-files/71529-ubucleaner.sh
sudo chmod +x 71529-ubucleaner.sh
Now run the script with the following command and it will take care of all the things mentioned above: sh 71529-ubucleaner.sh
More details.
Removing Entries from Grub 2
Entries should be removed by editing or removing files in the /etc/grub.d folder. The /boot/grub/grub.cfg file is read-only and should not normally require editing.
Too Many Kernels? Kernels removed via Synaptic or with "apt-get remove" will automatically update grub.cfg and no user action is required.
* To find current kernel, in a terminal type: uname -r
* In Synaptic, type linux-image-2 in the search window at the upper right;
* The results should show every available and installed kernel. A green box on the left indicates that the package is installed. The only linux-image you want installed is the latest one. Uninstall the old kernels from the list by clicking their boxes and selecting "Mark for Removal".
* or Right click and select "Mark for Complete Removal" and then press the Apply main menu button;
The kernels will be removed from your system and from the Grub menu. Note -many users keep one previous kernel on the machine which previously ran without problems.
If you don't want to see the "Memtest86+" entries, run this command:
Code: sudo chmod -x /etc/grub.d/20_memtest86+
Run the update-grub command to allow the changes to be incorporated in grub.cfg
Too Many Kernels? Kernels removed via Synaptic or with "apt-get remove" will automatically update grub.cfg and no user action is required.
* To find current kernel, in a terminal type: uname -r
* In Synaptic, type linux-image-2 in the search window at the upper right;
* The results should show every available and installed kernel. A green box on the left indicates that the package is installed. The only linux-image you want installed is the latest one. Uninstall the old kernels from the list by clicking their boxes and selecting "Mark for Removal".
* or Right click and select "Mark for Complete Removal" and then press the Apply main menu button;
The kernels will be removed from your system and from the Grub menu. Note -many users keep one previous kernel on the machine which previously ran without problems.
If you don't want to see the "Memtest86+" entries, run this command:
Code: sudo chmod -x /etc/grub.d/20_memtest86+
Run the update-grub command to allow the changes to be incorporated in grub.cfg
Saturday, May 8, 2010
startupmanager to edit GRUB
At last a gui with which to edit Grub. Look for 'startupmanager' in Synaptic. btw - forget quick search - that won't find it.
Then go to System/Admin/StartUp-Manager
Then go to System/Admin/StartUp-Manager
Wifi card driver fiasco with Lucid Lynx
This did not work as it should have. Ubuntu has shot itself in the foot with the release of 10.04. Thousands of users of one of the most popular laptops on the market will find themselves unable to connect to the Internet on installing Ubuntu, and without any guidelines on how to proceed.
The issue affects wireless connections from the Dell Inspiron 15. What's really strange about this mess is that the scenario was obviously anticipated by the Ubuntu team and steps have been taken to hold the user's hand through the process of establishing a wireless connection via a proprietary driver, but - and here's the rub - this hand-holding only occurs when running Ubuntu 10.04 from the CD.
So, when I first ran Lucid Lynx from the CD, a flag appeared on my desktop telling me that proprietary drivers were available. (It should have been even more to the point - drivers were required for certain hardware devices to work and that I should click here to enable them.) As no wireless networks were visible, I quickly surmised that this flag could help sort that out so I clicked and in the ensuing window, enabled both the drivers listed. Now, since I wasn't connected to a network at the time, I can only conclude that Ubuntu downloaded those drivers form the CD. In any case, within a minute or so, my home wifi network appeared in the dropdown list beneath the wifi icon (in my top menu) and I was able to connect.
Now fast forward to the following evening when I decided to take the plunge and install Ubuntu 10.04 on my hard disk. After installation and logging in, no flag appeared. And of course - there was a red exclamation mark over my wifi icon and no networks listed. Miffed, bothered and bewildered, I tinkered around for a while until I found the Hardware drivers icon under System/Admin. But the ensuing window was empty and devoid of any advice. What was I supposed to do. I needed Synaptic but I didn't have an Internet connection.
To cut a long story short, after an hour or so of anguish - googling dead-ends in Windows, and on the point of just giving up on Ubuntu and formatting the partition, I pulled the Ethernet lead from the router out of the back of the desktop computer and stuck it in my laptop. Now at last I had an Internet connection and after clicking the hardware drivers icon again, Ubuntu presented me with a longish list of updates that I should download. I agreed and lo and behold, when the updates had finished, that missing flag popped up. Yes I cried, yes, enable those 2 proprietary drivers. (I had no idea which, if either, was appropriate.) And at last, after rebooting, I pulled out the Ethernet cable, the wireless icon showed itself and my home wifi network appeared in the list beneath it.
But look, it should not have been this way...
By the way, its the Broadcom STA driver that did the trick.
And what should have happened on logging in the first time? I should have seen a flag advising me that my wifi card would not work without enabling a proprietary driver and that to proceed, I should insert the CD to install that driver.
The issue affects wireless connections from the Dell Inspiron 15. What's really strange about this mess is that the scenario was obviously anticipated by the Ubuntu team and steps have been taken to hold the user's hand through the process of establishing a wireless connection via a proprietary driver, but - and here's the rub - this hand-holding only occurs when running Ubuntu 10.04 from the CD.
So, when I first ran Lucid Lynx from the CD, a flag appeared on my desktop telling me that proprietary drivers were available. (It should have been even more to the point - drivers were required for certain hardware devices to work and that I should click here to enable them.) As no wireless networks were visible, I quickly surmised that this flag could help sort that out so I clicked and in the ensuing window, enabled both the drivers listed. Now, since I wasn't connected to a network at the time, I can only conclude that Ubuntu downloaded those drivers form the CD. In any case, within a minute or so, my home wifi network appeared in the dropdown list beneath the wifi icon (in my top menu) and I was able to connect.
Now fast forward to the following evening when I decided to take the plunge and install Ubuntu 10.04 on my hard disk. After installation and logging in, no flag appeared. And of course - there was a red exclamation mark over my wifi icon and no networks listed. Miffed, bothered and bewildered, I tinkered around for a while until I found the Hardware drivers icon under System/Admin. But the ensuing window was empty and devoid of any advice. What was I supposed to do. I needed Synaptic but I didn't have an Internet connection.
To cut a long story short, after an hour or so of anguish - googling dead-ends in Windows, and on the point of just giving up on Ubuntu and formatting the partition, I pulled the Ethernet lead from the router out of the back of the desktop computer and stuck it in my laptop. Now at last I had an Internet connection and after clicking the hardware drivers icon again, Ubuntu presented me with a longish list of updates that I should download. I agreed and lo and behold, when the updates had finished, that missing flag popped up. Yes I cried, yes, enable those 2 proprietary drivers. (I had no idea which, if either, was appropriate.) And at last, after rebooting, I pulled out the Ethernet cable, the wireless icon showed itself and my home wifi network appeared in the list beneath it.
But look, it should not have been this way...
By the way, its the Broadcom STA driver that did the trick.
And what should have happened on logging in the first time? I should have seen a flag advising me that my wifi card would not work without enabling a proprietary driver and that to proceed, I should insert the CD to install that driver.
Subscribe to:
Posts (Atom)