I use terminal all the time so having it quickly accessible is crucial for me.
 
Would you like to see gnome-terminal icon by default in gnome-panel? Why?
 

 
I really hate Nautilus spatial mode, because it is not usable – it opens lots of windows that you need to close afterwards. I don’t get Fedora using spatial mode by default. First thing for me to do after installing Fedora is:
 
gconftool-2 --type boolean --set /apps/nautilus/preferences/always_use_browser true
 
Do you do the same or leave nautilus set to spatial mode?
 
UPDATE; I ashamed to admit that but I didn’t know about all the shortcuts and I’ve been using Gnome for years! I’ll have to try spatial mode again and report back ;) Thanks for all of your comments.
 
UPDATE 2: I switched to spatial mode ;)
 

If you have digital camera then you also have lots of digital photos on your disk drive. For you who want to better organise your photos here is one quick tip.
 

Cameras name photo files in non human friendly ways, for example last few photos I took have these filenames:

$ ls
pa198126.jpg pa198130.jpg pa198134.jpg pa198138.jpg pa198142.jpg pa198146.jpg pa198150.jpg pa198127.jpg pa198131.jpg pa198135.jpg pa198139.jpg pa198143.jpg pa198147.jpg pa198151.jpg pa198128.jpg pa198132.jpg pa198136.jpg pa198140.jpg pa198144.jpg pa198148.jpg pa198129.jpg pa198133.jpg pa198137.jpg pa198141.jpg pa198145.jpg

 Just from looking at the file names and not oppening these photos you can’t really get much information. If you wish to smartly bulk rename your photo files so that the file names have more meaning continue reading.
 

First we need to install jhead. If you are using Fedora use yum for installing jhead and for Debian (Ubuntu) based systems use apt-get:
 

yum install jhead
or
apt-get install jhead
 

To give these images a new name we will use date written by the camera to their exif tags. Exif tags contain a lot of useful information like date and time the shoots were taken, brand and model of the camera, shutter speed and other info.
 

We will use only the time info for now, but you can play with all the settings as you wish.
 

To rename the images with date and time when they were shoot we can use jhead with these parameters:
 

jhead -n%Y_%m_%d_%H%M%S p*.jpg
 

After that we have a much more human friendly image names:
 

$ ls
2008_10_19_161728a.jpg 2008_10_19_162047.jpg 2008_10_19_172113.jpg 2008_10_19_173315.jpg 2008_10_19_161728.jpg 2008_10_19_162100.jpg 2008_10_19_172124.jpg 2008_10_19_173330.jpg 2008_10_19_161830.jpg 2008_10_19_162204.jpg 2008_10_19_172137.jpg 2008_10_19_173349.jpg 2008_10_19_161840.jpg 2008_10_19_162218.jpg 2008_10_19_172141.jpg 2008_10_19_173806.jpg 2008_10_19_161949.jpg 2008_10_19_171956.jpg 2008_10_19_172231.jpg 2008_10_19_173816.jpg 2008_10_19_162000.jpg 2008_10_19_172009.jpg 2008_10_19_173256.jpg 2008_10_19_162034.jpg

 If you have some more examples how this approach can be enhanced even more please post it in the comments.
 
UPDATE:
 
I read a great article on linux.com about automated image processing. Highly recommended.
 

 
If you have bluetooth GPS dongle that you have laying around, or can borrow one from somebody, and like driving a bike or a car around then this is the guide for you.
 

You need to have bluetooth wireless chip already installed on your laptop. If you have a laptop or a desktop without bluetooth you can buy and use USB bluetooth dongle.
 

You can check if you have a bluetooth and that it is working correctly using this command:
hcitool dev

Then let’s make sure you have bluetooth service running:
service bluetooth status
 

if it is not running just start it with:
service bluetooth start
 

Turn on your bluetooth GPS dongle and find its bluetooth mac address with this command:
hcitool scan
Scanning ...
00:1E:EE:00:11:22 LG KU990
00:02:78:99:FF:00 SJ GPS
00:12:EE:55:00:FF Device01
 

If you find more than one bluetooth device you should know the name of your GPS dongle. My GPS dongle has a “GPS” in its name so it is easy to catch its mac address: 00:02:78:99:FF:00 (SJ GPS)
 

You need to install gpsd and setup bluetooth config files, so let’s first install gpsd:
su -
yum install gpsd gpsd-clients -y
 

Then you need to edit bluetooth config file so that gpsd connects automatically to GPS bluetooth dongle.

gedit / etc/bluetooth/rfcomm.conf
 

and add these lines:
 

rfcomm0 {
# Automatically bind the device at startup
bind yes;

# Description of the connection
comment "GPS Bluetooth dongle";
}
 

After reboot check if you have /dev/rfcomm0 device with:
ls -al /dev/rfcomm0
 

If after reboot (or you don’t wan’t to reboot) you still don’t have /dev/rfcomm0 then just issue this command:
rfcomm bind rfcomm0
 

Now start gpsd daemon:
gpsd /dev/rfcomm0
 

Now you can start having fun! :)
 

Install gps applications like tangogps, gpsdrive and gpsbabel.
yum install -y tangogps gpsdrive gpsbabel
 

Now just start tangogps and gpsdrive and enjoy…
 

I have read on glipper mailing list that the glipper maintainer has left the project so glipper is no longer maintained :(
 

Anybody with Python skills is welcome to joint the project and continue work on this small but essential and cool little project. I can’t imagine day-to-day work on Gnome desktop without this fabulous tool.

 
I can’t wait until somebody with Python skills comes along and makes this project shine again…

 
UPDATE:
Try parcellite – an alternative to glipper:

as root:
yum install parcellite
 

Thank you Martin for your comment regarding parcellite, and also thank you Christoph for fixing some glipper bugs, but it still has this issue with crashing on startup.

I’ve been trying for some time use Elisa media center on Fedora but it seams that Elisa is too elusive for Fedora. Current version on Elisa home page is 0.5.12 but if you install Elisa on Fedora 9 you will get much older 0.3.2, even bigger issue is that Elisa doesn’t work because of some broken dependencies.
 
You can look at Fedora Bugzilla; more specifically look at bugs #446051 and #429590.
 
So I guessed that there will be some “break my Fedora box” packages in F9 updates-testing repos, but unfortunately there were none :(
So I booted Fedora 10 beta – this is the bleeding edge Fedora so I thought there had to be new Elisa package in F10, but guess what? Fedora 10 also has old Elisa 0.3.2 which doesn’t work.
 
I also tried manually getting packages from freshrpms testing repo, I downloaded and saved all the rpm packages and tried to install them but there were some unmet dependencies :(
 
I tried installing pigment-python-0.3.8-1.fc9.i386.rpm but that packet needs libpigment-0.3.so.8, libpigment-gtk-0.3.so.8 and libpigment-imaging-0.3.so.8 but pigment-devel-0.3.9-1.fc9.i386.rpm packet provides only so.7 but no so.8 libraries…
 
I hope these issues will get sorted out as soon as possible. I’m willing to test Elisa packages and help that way so that working and updated Elisa gets into Fedora 10 repositories.
 
UPDATE:
I found out how you can install elisa on Fedora 9 thanks to thm on #fedora-devel irc channel, and it isn’t too hard.

First you need to setup freshrpms repository; just copy the code below, but you need to remove [ ] around etc because my blog has protection that prevents me to write that path.


su -
cat < /[etc]/yum.repos.d/freshrpms-testing-elisa.repo
[freshrpms-testing-elisa]
name=Freshrpms Testing (elisa)
baseurl=http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/testing/$releasever/elisa/$basearch
gpgkey=http://ftp.freshrpms.net/pub/freshrpms/RPM-GPG-KEY
enabled=1
EOF
 

and then just install elisa:
 

yum --enablerepo=freshrpms-testing-elisa install elisa

Links:

• Elisa home page
• Bugzilla bug #446051
• Bugzilla bug #429590
• Freshrpms testing repository