As I mentioned in my previous post, we’re looking for more wallpaper contributions to go into the next release of Fedora.  If you were saving your best work for last, or were saying “I’ll get to it soon” well now is the time.  The deadline for the wallpaper submissions is fast approaching, and August 9th will be here before you realize it.  So, take a look at my previous post for a refresher and lets see what’cha got!

What are supplemental wallpapers?

In addition to the standard wallpaper that the design team is working hard to design and finalize, we want to include some addition wallpapers for people to choose from.  We will still ship with the default GNOME upstream supplemental wallpapers but, we want to include some more from our community.

What we need

In order to us the image for the supplemental wallpapers we need some basic information

• URL of the image (ie. “where it’s at”)
• Title of the work in question
• Name of the author (their real name is preferable, but a nickname with a link to the profile on the page the image is from works as well)
• Contact information for the author, email if possible
• URL of the source page that the image was originally from
• The license of the photo (has to be compatible with the Fedora requirements)

In addition to this, what the image is of is important (see the wiki for the full requirements)

• Must not contain brand names or trademarks of any kind
• Must not contain material that is inappropriate, offensive, indecent, obscene, hateful, tortuous, defamatory, slanderous or libelous
• No religious, political, or nationalist imagery (including flags)
• No images of hats, particularly fedoras. (This is a matter of respect for our primary sponsor, Red Hat, Inc., and is not negotiable. Of course, passive appearance of hats, such as those upon heads in a crowd, may be allowed.)
• No version numbers. End users might prefer to continue to use an older theme, or use the latest theme in their older version of Fedora. To enable that choice, do not use any version numbers within the Fedora artwork.
• No text. Text should not be used in the backgrounds because the artwork is intended for a global audience and to be reused by derivative distributions.
• Should not contain images of people (contemporary, historical, or fictional)
• Should not contain images of pets, or captive or mistreated animals

How to submit

So, got that perfect image in mind for a supplemental wallpaper?  Great!  If the image meets all of the requirements then all you need to do is add it to the submissions section of the wiki and wait.  We will take submissions until 23:59 UTC on August 9th 2011 following that the design team will vote for the top 15 and they will be packaged up and included in the Fedora 16 release.

If you have any questions feel free to email me (pcon AT fedoraproject DOT org) or contact me (pcon) in #fedora-design on freenode

UDEV Rules

To start with, we need to set up static naming for the storage device that you want to make into backup disk.  Start by plugging in the disk.  (Now I’m not using Gnome or KDE so I’m not sure what their automounter will do.  So, you might have to find a way to exclude it from the automounter.  We need to find out the “model” of the drive.  My udev rules are pretty basic, and will work since most people don’t have more than one the same model of USB drive laying around that they would use.  You can always modify the udev rules to work for you.

udevadm info -a -p /sys/block/sdc | grep model

Here we are looking at the block device sdc (which is what the kernel named it since we don’t have any udev rules yet).  This could change depending on how many block devices you currently have.  Now we take this information, and feed it into a udev rule.  I created a file /etc/udev/rules.d/50-backup.rules The name isn’t really important, however, the number 50- is.  That is the order in which it runs.  We want that number to be less than 90 so that hal doesn’t run first.  Inside that file, we have the following:

KERNEL==”sd?1″, SUBSYSTEM==”block”, ATTRS{model}==”MODEL GOES HERE”, SYMLINK+=”backup”, RUN+=”/usr/local/bin/backup.sh”

Replace “MODEL GOES HERE” with the output from the udevadm command

The backup script

Now we udev running our script /usr/local/bin/backup.sh we need to make that script

#!/bin/bash

NOTIFYUSER="pcon"
MAINDIR="/home/pcon/"
BACKUPDIR="/mnt/backup"

su $NOTIFYUSER alt-notify-send backup "Waiting for things to settle" 0
sleep 5

su $NOTIFYUSER alt-notify-send backup "Starting backup" 0
echo "$(date) - Mounting /dev/backup to $BACKUPDIR" > /tmp/backup.log
mount /dev/backup $BACKUPDIR >> /tmp/backup.log 2>&1
echo "$(date) - Staring rsync of $MAINDIR to $BACKUPDIR" >> /tmp/backup.log
rsync -arvuz --inplace --delete $MAINDIR $BACKUPDIR >> /tmp/backup.log 2>&1
echo "$(date) - Mounting /dev/backup to $BACKUPDIR" >> /tmp/backup.log
umount $BACKUPDIR >> /tmp/backup.log 2>&1
su $NOTIFYUSER alt-notify-send backup "Backup completed" 0

We have a couple of things to setup here.  First we need to create /mnt/backup as root, and fill out the other variables in the top of the script.  Aslo, if we want notification in gnome, we need to make a notify-send work around.  Put the following in /usr/local/bin/alt-notify-send

#!/bin/sh
user=`whoami`
pids=`pgrep -u $user gnome-panel`
title=$1
text=$2
timeout=$3

if [ -z "$title" ]; then
    echo You need to give me a title >&2
    exit 1
fi
if [ -z "$text" ]; then
     text=$title
fi
if [ -z "$timeout" ]; then
     timeout=60000
fi

for pid in $pids; do
    # find DBUS session bus for this session
    DBUS_SESSION_BUS_ADDRESS=`grep -z DBUS_SESSION_BUS_ADDRESS \
    /proc/$pid/environ | sed -e 's/DBUS_SESSION_BUS_ADDRESS=//'`
    # use it
    DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS \
    notify-send -u low -t $timeout "$title" "$text"
done

Now chmod +x the two scripts, and everything should be good to go.  You can download the scripts used in this post below:

• 50-backup.rules
• backup.sh
• alt-notify-send (Taken from here)

In your .screenrc, make sure you have a place that will show messages.  If you start up screen and you see “New screen…” then you’ve got this.  Next add your script to your .screenrc

bind -k k5 exec /home/pcon/bin/build_script.sh

Now everything in your screen is ready to go.  Now, on to build_script.sh

#!/bin/bash

echo -n -e “\033^Starting Build\033\\”

# Do something here

echo -n -e “\033^Ending Build\033\\”

That’s it.  Now your screen will display “Starting Build” and “Ending Build” on your display.  If the stuff in between happens too fast, you may only see your last message.  The key thing is that your message has to start with “\033^”  and end with “\033\\” otherwise you’ll loose your cursor.  And you have to have the -e on the echo so that it will interpret the octal codes correctly.

1. libnotify is ugly
2. takes up diskspace if you don’t clear the queue
3. requires you to either have the script, or remember the ridiculously long command

Well, these are things of the past.  Thanks to mumbles!

First install mumbles from yum (or source) then install the irssi script.  Make sure you change the growl_server and growl_password then you are good to go.  The script has a dependency on Net::GrowlNotify in perl.

The script uses irssi config variables so you can use /SET growl_server or /SET growl_password to set your growl server/password without having to load/unload the script.

• Generic user with a generic password to hand to the person in charge
• Ability to play dvd stored locally.  (Called presentation_dvd)
• Ability to play any dvd inserted.
• Require no user input except to choose presentation_dvd or dvd

Preperation

To get ready, we need to do a couple of things

• Create a presenter user
• Install xine and xine-lib-extras-freeworld
• Copy our presentation_dvd to an iso
  

  dd if=/dev/dvd of=/home/presenter/presentation_dvd.iso

Xesssions

Xsessions are what defines your window manager.  It’s what tells X11 what to run when you say Session->Gnome or Session->fluxbox.  These files are stored in /usr/share/xsessions.

[Desktop Entry]
Encoding=UTF-8
Name=Presentation_DVD
Comment=Start the presentation DVD
Exec=/usr/local/bin/presentation_dvd
Terminal=False

[Window Manager]
SessionManaged=true

This is our file in /usr/share/xesssions/presentation_dvd.desktop We then create one in /usr/share/xesssions/dvd.desktop and replace presentation_dvd with dvd.

The Scripts

Our /usr/local/bin/presentation_dvd looks like this:

#!bin/bash
amixer set Master playback 100%
xine -f -g --no-splash dvd:/home/presenter/presentation_dvd.iso

This will turn the volume up to 100% and then start xine on the iso.  To exit, just right click and say exit.  This will take you back to the login screen.

Now to handle any dvd with the /usr/local/bin/dvd

#!/bin/bash
amixer set Master playback 100%
xine -f -g --no-splash dvd://

And the final touch, make them both executable

chmod a+x /usr/local/bin/dvd /usr/local/bin/presentation_dvd

NOTE:  The xine parameter is dash dash no dash splash.  The font I’m using doesn’t render two dashes well

Usage

From the login menu, choose your presenter user, and then choose the appropriate session at the bottom.  Then type in the password.  Like magic, everything should work.

Potential problems

If you don’t see your session in the list, you might have a typo in your xsession file

If one of the xine scripts don’t work, try logging into gnome and running the script from the command-line to see why.

In Fedora, you need to do the following as root before running any of the commands from the article

ln -s /usr/bin/gunzip /usr/bin/uncompress

Now.  To figure out how the server.cfg

At the end of your ~/.mailcap file, add the following

text/html; lynx -dump -width=78 -nolist %s | sed ‘s/^   //’; copiousoutput; needsterminal; nametemplate=%s.html

Then, in the ~/.muttrc add

auto_view text/x-vcard text/html text/enriched

And restart mutt.  This will use lynx to render the email.  You can substitute lynx for any text-based html browser you’d like.

set reverse_alias

Then set up the alias.  This can be added to your alias file, or straight into your .muttrc

alias fake_john john_doe2@example.com (Fake John Doe)

Now all mail that comes in from john_doe2@example.com will show up as from “Fake John Doe” but the headers will remain the same, and no one is the wiser.

That brings me to the real point.  If you haven’t gotten a chance to check out some of the apps that make desktop apps out of web apps, try them.

• I like fluid for OSX, it seems a little more full featured
• Then Prism is looking really promising for all platforms (yes, even linux)