Shop Mobile More Submit  Join Login
I use Clonezilla for frequent partition backups.  This is my menu entry for booting the iso from Grub. (My iso is located on sdb7 so adjust accordingly)

menuentry "ISO Clonezilla live" {
set isofile="/clonezilla-live-2.1.0-7-amd64.iso"
loopback loop (hd1,7)$isofile
linux (loop)/live/vmlinuz boot=live live-config nolocales edd=on nomodeset ocs_live_run=\"ocs-live-general\" ocs_live_extra_param=\"\" ocs_live_keymap=\"\" ocs_live_batch=\"no\" ocs_lang=\"\" vga=788 ip=frommedia nosplash toram=filesystem.squashfs findiso=$isofile
initrd (loop)/live/initrd.img
Ok, I showed how to create a custom.xml to incorporate a wallpaper slideshow on Gnome (should also work on gnome derivatives, Unity & Cinnamon but not tested here) in my previous journal entry.

Some people prefer a static background they can select from Appearances.  I found a script for that on Ubuntu forums, the name & link are noted in the script.  It is annotated with instructions.

It works great, hope you find a use for it.


#Script author: Freecore…
#November 7th, 2012, 04:42 PM
#Actually, you don't have to add manually your 80 wallpapers. I wrote a script to do that (I have a lot of wallpapers I #wanted to add to the appearance menu too :smile:).

#This is the script:


# Freecore

# This script creates an xml file that you can
# put on /usr/share/gnome-background-properties (if you want wallpapers entrys to ALL users, requires administrator rights)
# or in /home/userA/.local/share/gnome-background-properties (if you want it only for userA).

# Instructions
# (Realize that the script it's supposed to be runned like this: sh namescript FOLDER/OF/PICTURES/DIRECTION/).
# Don't forget the last "/".
# This script creates a file named my-wallpapers.xml.
# The file will have the xml code that Ubuntu (Gnome) identifies when it search for backgrounds.
# ATTENTION: The file generated will NOT include hidden folders NOR sub-folders pictures.
# ATTENTION: The file will include xml code for EACH file, so only put pictures in that folder.


echo '<?xml version="1.0" encoding="UTF-8"?>' >> "$xmlFile"
echo '' >> "$xmlFile"
echo '<wallpapers>' >> "$xmlFile"

# For each file in the folder ingresed by the user, it wll create an xml entry.
for img in "$1"*; do

# We'll declare a variable with the entire name of the image (extention included). It will be used to declare the next variable.

# We'll declare a variable with the name without the extention. It will be the name in the appearance menu
Name=$(echo "$CompleteName" | cut -d "." -f 1)

echo " <wallpaper>" >> "$xmlFile"
echo " <name>$Name</name>" >> "$xmlFile"
echo " <filename>$img</filename>" >> "$xmlFile"
echo " <options>zoom</options>" >> "$xmlFile"
echo " <pcolor>#000000</pcolor>" >> "$xmlFile"
echo " <scolor>#000000</scolor>" >> "$xmlFile"
echo " <shade_type>solid</shade_type>" >> "$xmlFile"
echo " </wallpaper>" >> "$xmlFile"


echo '</wallpapers>' >> "$xmlFile"

echo "The file has been created with the pictures in $1"

#All you have to do is put it in a .sh text file and run it in a terminal with something like
#sh your/pictures/folder/ be aware of the last "/". And it's done!

#If you want the wallpapers to be able only in your appearance menu you can put the xml file in your local folder (./#local/share...) as I mentioned in the script.

#You can manage to convert the script to a Slideshow creator too with some little changes.

#I hope it'll help some people. :cool:
**** 29 November 2012 *****
Ran into a bug since I originally shared this:  If you use the link from the slideshow.xml for easy access by apps like gdm3setup make sure you either have it in a different folder than the images, or remove it before running the nautilus script. If you don't it will be added to the custom.xml and will not display that 'image' correctly.

My solution was to place them in /usr/share/GDM so I no longer have to worry about it.

I use a nautilus script that I found via Webupd8… to create a wallpaper slideshow, but the problem is that to add one that's already been created is a PITA, at least to me.

That sent me on a quest to figure out how to add my custom wallpapers so they would show up in System Settings > Backgrounds so that I could create custom collections and easily select them.  I looked at numerous pages similar to this one… and this is what I ended up with.

My /usr/share/gnome-background-properties/custom.xml looks like this:

<?xml version="1.0" encoding="UTF-8"?>

<wallpaper deleted="false">

<name>Custom Backgrounds</name>


So, after the nautilus script creates the slideshow.xml (whatever name you told it to use) you insert the path & filename info where indicated.  (Using a script is optional, you can use the the gnome-backgrounds.xml for a guide, or just add your images to it).

I use the system path because I use the same script as my GDM theme, which seems to require root access.

Now, when you open up System Settings > Backgrounds your new custom.xml file will show up as an image just like the other backgrounds that were installed with your system.

Note: This essentially just a knockoff of the adwaita.xml, the one that provides the time of day changes in the blue striped wallpaper

* Bonus, now, to use the same xml via an application like gdm3setup, which will only look for images, you create a link to the slideshow.xml (in my case /usr/share/backgrounds/custom/custom.xml) and give it a .jpg extension, mine is simply /usr/share/backgrounds/custom/custom.jpg).  Now you can navigate to that folder with gdm3setup and it will show up as a legitimate selection.  Of course you can mix & match, but if you like a smooth transition from the login screen to the desktop, you will have the dynamic wallpaper making a seamless transition.

I don't know if anyone even bothers to read these journal entries, but I can also explain how to add transparency to the login screen (get  rid of that solid gray look between the gdm wallpaper theme & the desktop wallpaper).

Anyway, if you have questions or problems feel free to ask, I'll do my best.  I know this works on Archlinux (and derivatives) and should work with any distro that has /usr/share/gnome-background-properties, which should include Ubuntu.
  • Listening to: The Lacs - 190proof
  • Drinking: Massive quantities of strong black coffee
Hi folks, as you probably realize by now, I am not an Ubuntu user, but I still have roots to it.  This is probably an aspect I have overlooked in every one of my themes, but this is a fix via CraazyT & nowerries.

--------  Quote  ------------------

~nowerries Mar 12, 2012
Hey just read the thread and thought you might like my fix for USC on dark colored themes.

"Only bug I have noticed so far is fonts unreadable in Ubunut Software Center the fix for this is to in terminal type...

sudo gedit /usr/share/software-center/ui/gtk3/css/softwarecenter.css

.... and change the color value of @define-color super-light-aubergine to what ever color you want to define background."

Updated: 01-07-2013

Ok, think we've got this figured out.  Some dark themes have always been a problem with the text entry boxes in Firefox, &/or invisible text cursors, I think this will cure it.

#### Firefox text fix goes inside the theme name/gtk-2.0/gtkrc (or an app fix in the gtk-2.0/styles) This should work with all problematic dark themes in Firefox #########

style "ff" {
text[NORMAL] = "#000"
base[NORMAL] = "#FFF"
class "GtkInvisible" style "ff"
widget "GtkInvisible" style "ff"

style "fff" {
text[NORMAL] = "#000"
base[NORMAL] = "#FFF"
class "GtkEntry" style "fff"
widget "GtkEntry" style "fff"

style "custom" {
GtkWidget::cursor-color = "#000"
GtkWidget::secondary-cursor-color = "#FF0000"
widget_class "*" style "custom"

###### End of Firefox fix ##########

I don't know what the secondary cursor is, but you'll have a red one with this.
May also work in ~/.gtkrc but that hasn't been thoroughly tested.  Biggest problem for me is that my system has so many modifications it's sometimes difficult to know where one "fix" ends & another begins.

Anyway, if this is a problem for you, & the method works please help me to disseminate it. (spread the word) :)

If it is proven that it works in the ~/.gtkrc that would be the best method because it would affect all your themes globally.