SLim Theme - Clearlooks openbox

Backgroung is poor, but is easy change.
Screenshot is in Brazilian Portuguese, but download link is in English.
Screen:
Download: http://www.speedyshare.com/607853852.html
UPDATE/UPDATE/UPDATE
Make new theme. More realist.
Screen:
Download: http://www.speedyshare.com/233588171.html
Last edited by kramerxiita (2008-09-13 15:14:45)

fflarex wrote:Very nice. I won't be using it myself, but I am nevertheless impressed. Are the buttons fake?
They're fake, slim doesn't support buttons....

Similar Messages

  • Slim Theme not loading shows dafault theme only.

    Hi I I installed slim and archlinux-slim-themes and did what the wiki said in regard to showing different themes.
    Path, X server and arguments (if needed)
    # Note: -xauth $authfile is automatically appended
    default_path /bin:/usr/bin:/usr/local/bin
    default_xserver /usr/bin/X
    xserver_arguments -nolisten tcp vt07
    # Commands for halt, login, etc.
    halt_cmd /sbin/shutdown -h now
    reboot_cmd /sbin/shutdown -r now
    console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
    #suspend_cmd /usr/sbin/suspend
    # Full path to the xauth binary
    xauth_path /usr/bin/xauth
    # Xauth file for server
    authfile /var/run/slim.auth
    # Activate numlock when slim starts. Valid values: on|off
    # numlock on
    # Hide the mouse cursor (note: does not work with some WMs).
    # Valid values: true|false
    # hidecursor false
    # This command is executed after a succesful login.
    # you can place the %session and %theme variables
    # to handle launching of specific commands in .xinitrc
    # depending of chosen session and slim theme
    # NOTE: if your system does not have bash you need
    # to adjust the command according to your preferred shell,
    # i.e. for freebsd use:
    # login_cmd exec /bin/sh - ~/.xinitrc %session
    login_cmd exec /bin/bash -login ~/.xinitrc %session
    # Commands executed when starting and exiting a session.
    # They can be used for registering a X11 session with
    # sessreg. You can use the %user variable
    # sessionstart_cmd some command
    # sessionstop_cmd some command
    # Start in daemon mode. Valid values: yes | no
    # Note that this can be overriden by the command line
    # options "-d" and "-nodaemon"
    # daemon yes
    # Set directory that contains the xsessions.
    # slim reads xsesion from this directory, and be able to select.
    sessiondir /usr/share/xsessions/
    # Executed when pressing F11 (requires imagemagick)
    screenshot_cmd import -window root /slim.png
    # welcome message. Available variables: %host, %domain
    welcome_msg Welcome to %host
    # Session message. Prepended to the session name when pressing F1
    # session_msg Session:
    # shutdown / reboot messages
    shutdown_msg The system is halting...
    reboot_msg The system is rebooting...
    # default user, leave blank or remove this line
    # for avoid pre-loading the username.
    #default_user simone
    # Focus the password field on start when default_user is set
    # Set to "yes" to enable this feature
    #focus_password no
    # Automatically login the default user (without entering
    # the password. Set to "yes" to enable this feature
    #auto_login no
    # current theme, use comma separated list to specify a set to
    # randomly choose from
    current_theme smoke-window
    # Lock file
    lockfile /var/lock/slim.lock
    # Log file
    logfile /var/log/slim.log
    The source for the theme is this: /usr/share/themes/Smoke/xfce-notify-4.0/gtkrc
    style "smoke-window"
    bg[NORMAL] = "#4d4d4d"
    XfceNotifyWindow::border-color = "#ffffff"
    XfceNotifyWindow::border-radius = 10.0
    XfceNotifyWindow::border-width-hover = 3.0
    class "XfceNotifyWindow" style "smoke-window"
    style "smoke-button"
    bg[NORMAL] = "#202020"
    bg[PRELIGHT] = "#404040"
    fg[NORMAL] = "#ffffff"
    fg[PRELIGHT] = "#ffffff"
    widget_class "XfceNotifyWindow.*.GtkButton*" style "smoke-button"
    style "smoke-text"
    fg[NORMAL] = "#ffffff"
    GtkWidget::link-color = "#a7a7a7"
    widget_class "XfceNotifyWindow.*.<GtkLabel>" style "smoke-text"
    style "smoke-summary"
    font_name = "Bold"
    widget "XfceNotifyWindow.*.summary" style "smoke-summary"
    I tryed on several different themes with the same method and still ugly ass default login screen
    This is my ~/xinitrc:
    # OPENBOX LOADER
    exec openbox-session
    # Start a D-Bus session
    # Source the below file only if you do not already use the default xinitrc skeleton.
    # Otherwise you will end up with multiple dbus sessions.
    source /etc/X11/xinit/xinitrc.d/30-dbus
    # Start GNOME Keyring
    eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
    # You probably need to do this too:
    export GPG_AGENT_INFO SSH_AUTH_SOCK
    I don't know whats missing I did everything the wiki told me still Slim only showing default theme. Please help. Thanks.

    I could be wrong but you seem to be confusing themes specific to slim with themes for gtk. The themes available for slim are in /usr/share/slim/themes.

  • [SOLVED] Slim not starting Openbox

    Hi :)
    I've run a search through this forum and all, and I can't seem to solve my problem...
    I've installed Arch on VirtualBox (so that I can try it out) and I installed Slim and Openbox.
    The problem is that when I log in, the screen flickers, and Slim comes back up, as if openbox wasn't executed at all
    Any of you guys has this setup? (slim and ob)
    If so, please tell me how you configured it...
    Thanks in advance
    Last edited by pedro-kun (2007-08-05 18:09:56)

    Here it is:
    # Path, X server and arguments (if needed)
    # Note: -xauth $authfile is automatically appended
    default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/bin
    default_xserver /usr/bin/X
    xserver_arguments -nolisten tcp vt07
    # Commands for halt, login, etc.
    halt_cmd /sbin/shutdown -h now
    reboot_cmd /sbin/shutdown -r now
    console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
    #suspend_cmd /usr/sbin/suspend
    # Full path to the xauth binary
    xauth_path /usr/bin/xauth
    # Xauth file for server
    authfile /var/run/slim.auth
    # Activate numlock when slim starts. Valid values: on|off
    # numlock on
    # Hide the mouse cursor (note: does not work with some WMs).
    # Valid values: true|false
    # hidecursor false
    # This command is executed after a succesful login.
    # you can place the %session and %theme variables
    # to handle launching of specific commands in .xinitrc
    # depending of chosen session and slim theme
    # NOTE: if your system does not have bash you need
    # to adjust the command according to your preferred shell,
    # i.e. for freebsd use:
    # login_cmd exec /bin/sh - ~/.xinitrc %session
    login_cmd exec /bin/bash -login ~/.xinitrc
    # Commands executed when starting and exiting a session.
    # They can be used for registering a X11 session with
    # sessreg. You can use the %user variable
    # sessionstart_cmd some command
    # sessionstop_cmd some command
    # Start in daemon mode. Valid values: yes | no
    # Note that this can overridden by the command line
    # option "-d"
    # daemon yes
    # Available sessions (first one is the default).
    # The current chosen session name is replaced in the login_cmd
    # above, so your login command can handle different sessions.
    # see the xinitrc.sample file shipped with slim sources
    # sessions xfce4,icewm,wmaker,blackbox
    # Executed when pressing F11 (requires imagemagick)
    screenshot_cmd import -window root /slim.png
    # welcome message. Available variables: %host, %domain
    welcome_msg Welcome to %host
    # shutdown / reboot messages
    shutdown_msg The system is halting...
    reboot_msg The system is rebooting...
    # default user, leave blank or remove this line
    # for avoid pre-loading the username.
    #default_user pedro
    # current theme, use comma separated list to specify a set to
    # randomly choose from
    current_theme default
    # Lock file
    lockfile /var/lock/slim.lock
    # Log file
    logfile /var/log/slim.log
    i got rid of the %session bit, and the sessions, because i'm gonna use only openbox. Either way, i don't think doing that has anything to do with the problem, because i think i tried it with the default slim.conf and it didn't work anyway.

  • Bash script: Rotate your wallpaper and SLiM theme at the same time

    EDIT;
    I've decided I should really thank Cerebral for his help with writing this script; this thank you should have been here from the get go.
    After writing:
    #!/usr/bin
    echo "Hello World!"
    I wrote a script to rotate my fluxbox background and SLiM theme at the same time, so I could have a contiuously changing background and still have a smooth transition from SLiM to fluxbox.  (It just looks so much cooler when both have matching backgrounds).  By the time you finish reading it, and configuring your box so it will work, you will probably have decided you could have writtin your own, better script to do the same thing.  But, on the off chance anybody finds use for it, here it is:
    (this should be obvious, but: don't run this script without at least reading the comments)
    #!/bin/bash
    #this is a script to rotate a number of backgrounds
    #to be shared by the fluxbox desktop and SLiM login manager.
    #it is the first meaningful script I've written. It may be
    #freely distributed and used with the understanding that you are
    #using it at your own risk.
    #Before running this script you need to check that your SLiM
    #themes are installed to the path /usr/share/slim/themes, which
    #is the defulat path for installation in Arch. Here are some
    #other things you need to set up:
    #1. create (if you don't have it) the directory /usr/share/wallpapers
    #2. create a wallpaper in /usr/share/wallpapers called 'dummy' by copying
    #you current wallpaper to that filename
    #3. set your window manager to display the wallpaper 'dummy', this works fine
    #using a style overlay in fluxbox, I haven't tested it with any other window
    #manager, but I don't see why this would cause a problem.
    #4. create a directory /usr/share/slim/themes/current, you can copy one of
    #your slim themes into that directory if you want. (this will prevent you
    #from seeing some error messages the first time you run the script)
    #5. define the names of the themes you want to rotate, in order for this
    #script to work, you must name them "themeNUMBER", where NUMBER is replaced
    #by an integer. Your themes must be numbered consecutively, start with 1
    # that is:
    #theme1 , theme2, theme3, etc. , theme305
    #If you don't number consecutively, this script will not run properly. You
    #must also define the total number of themes as "rotate_number"
    #6. Check if the script runs, if it does, you should change /etc/slim.conf to
    #use the theme "current"
    #7. This theme will now rotate your SLiM theme and wallpaper in such a way as
    #to make them match each other. Note that SLiM will not let you change themes
    #"on the fly", (as of July 6, 2008), so changes will not be apparent unless you
    #restart SLiM. I run the script before I run slim in my etc/rc.local local
    #script, so each time I reboot I get different wallpaper / login background.
    #Fred Drueck 2008
    #Define here all themes to be rotated and the total number of
    #themes to rotate:
    rotate_number=9
    theme1=/usr/share/slim/themes/default
    theme2=/usr/share/slim/themes/lake
    theme3=/usr/share/slim/themes/lunar
    theme4=/usr/share/slim/themes/flower2
    theme5=/usr/share/slim/themes/the-light
    theme6=/usr/share/slim/themes/mindlock
    theme7=/usr/share/slim/themes/parallel-dimensions
    theme8=/usr/share/slim/themes/wave
    theme9=/usr/share/slim/themes/fingerprint
    #check you are running this script as super-user:
    if [ $(id -u) != "0" ]; then
    echo "You must be the superuser to run this script" >&2
    exit 1
    fi
    echo "rotating themes"
    #figure out which theme is currently set, then name it as the variable
    #"last theme number", otherwise set last theme number as 0
    if [ -f /usr/share/slim/themes/current/current_theme_number ]
    then
    echo "checking current theme"
    cd /usr/share/slim/themes/current/
    eval last_theme_number=$(cat /usr/share/slim/themes/current/current_theme_number)
    echo $last_theme_number
    else
    echo "no theme is currently set, using theme 1"
    last_theme_number=0
    echo $1 > /usr/share/slim/themes/current/current_theme_number
    fi
    #set the new theme number
    eval new_theme_number=$(($(($last_theme_number % $rotate_number))+1))
    #select the new theme
    placeholder=theme
    eval new_theme=\$$placeholder$new_theme_number
    echo $new_theme
    #now clean out the "current" theme where I keep the current
    #theme for slim
    rm /usr/share/slim/themes/current/background*
    rm /usr/share/slim/themes/current/panel*
    rm /usr/share/slim/themes/current/slim.theme
    #the wildcards are there since the themes use jpg and png files
    cp $new_theme/background* /usr/share/slim/themes/current
    cp $new_theme/panel* /usr/share/slim/themes/current
    cp $new_theme/slim.theme /usr/share/slim/themes/current
    #increase the theme number, but first clear the old file
    rm /usr/share/slim/themes/current/current_theme_number
    echo $new_theme_number > /usr/share/slim/themes/current/current_theme_number
    #copy over the dummy wallpaper in "/usr/share/wallpapers" (with the theme
    #background file
    cp $new_theme/background* /usr/share/wallpapers/dummy
    exit 0
    Last edited by pseudonomous (2008-07-07 21:59:42)

    oh i forgot to mention... its rotating while moving. i.e. is doesn't have to stop rotate and then continue back to origin.

  • Looking for a theme of openbox in kde4

    sorry for my poor english,i didn't often post a thread in english
    some days ago i installed kde4 on my laptop and turn from openbox to kde4
    after try kwin for some days,i replace the kwin window manager with openbox,because  i've got used to openbox
    but one question:
    the theme of openbox doesn't suit the kde4's,i googled but didn't find a suitable  one.so is there a theme for openbox that can match the theme of kde4?
    Last edited by ggarlic (2009-12-13 12:40:16)

    box-look.org - openbox theme site
    PS: Or make one by yourself with Xyne's OBTheme. It's in AUR.
    Last edited by DonVla (2009-12-13 12:40:58)

  • SLiM themes

    i made up a few slim themes here if anyone else wants to try them out. i was going to submit them to the slim developers, but i didn't see any email address on their site. so i guess it's an "arch only" special.

    phrakture wrote:
    Wow, those are awesome - perhaps submit there here: http://developer.berlios.de/bugs/?group_id=2663
    Or possibly file a bug that there's no way to contact them?
    Aaron, can you please include them in slim-themes package meanwhile?

  • SLiM theme Burning-Arch

    Hi,
    I've made a slim theme.
    If you'd like to use it, it's in AUR.
    http://aur.archlinux.org/packages.php?ID=18455

    you're right
    no-problem, I can share it via dropbox   https://www.dropbox.com/s/k7gojpmdkmyg2 … 080.tar.gz
    PS: use this link only if original link doesn't work

  • Slim Theme Darch

    I created a new Slim theme for ArchLinux using the new logo and uploaded it to AUR with the name slim-theme-darch. I hope you like.

    gleidson wrote:
    dyscoria wrote:Looks like this gleidson dude just strolled in, hit us with arguably the best arch slim theme there is, then disappears into the crowd.
    Sorry but I am engaged to my college degree. I am a Computer Science student
    Apology refused dammit!
    I mean, thanks for the theme bud, good luck with your studies

  • [solved] Slim themes conflict with e2fsprogs

    I tried installing a couple of slim themes, and got a message saying...
    util-Linux-ng conflicts with e2fsprogs. Remove e2fsprogs?
    I am currently on my desktop trying to install arch on a old laptop.
    Last edited by Jboxer (2010-02-08 01:24:46)

    I have discovered e2fsprogs has to deal with Ext2 Filesystem Utilities, i have installed Ext4, therefore I might try to remove the programs that are dependent of e2fsprogs. I would like to receive some more suggestions before I do anything.
    Edit: It also is used for Ext4, so scratch that idea.
    Last edited by Jboxer (2010-02-07 22:43:20)

  • Dwm slim themes (8-pack)

    In keeping with my dwm wallpaper thread, I've released an 8-pack of SLIM login themes for dwm fans:
    EDIT: The files can now be found here: http://cinderwick.ca/projects/dwm-artwork-themes/
    Four styles are included, each with a light and dark scheme.  In addition to SLIM, you'll need the 'artwiz-fonts' package (available from the repositories) for proper viewing. A couple of previews are below:
    Cheers
    Last edited by thayer (2011-04-20 17:26:23)

    leo2501 wrote:
    Rydgel wrote:
    leo2501 wrote:where?
    Here.
    http://farm4.static.flickr.com/3215/298 … b9d361.jpg
    I'm going to sleep right now, I will edit and share this one if someone is interested.
    whats is the font? i REALLY like it, but maybe 1680x1050? i want to make a qingy one i will google for a guide or something
    @haxit: how do you do the one you did? where did you look for a guide? or is much easier than I think?
    What do you mean?
    Also can you please release that theme rydgel?
    Last edited by haxit (2008-10-30 21:48:38)

  • [SLiM] Theme Configuration

    My current theme (custom built): http://i.imgur.com/o5cAt0E.png
    My questions are:
    1. How can I use "Gohufont" instead of "Verdana", I tried to add "input_font Gohufont:size=12" but didn't work.
    2. Is there a way to hide the cursor ( | ) and only see the characters.
    - http://slim.berlios.de/themes_howto.php
    - https://wiki.archlinux.org/index.php/SLiM
    Thanks.
    Last edited by iJC (2013-10-12 18:42:27)

    cookies wrote:
    iJC wrote:1. How can I use "Gohufont" instead of "Verdana", I tried to add "input_font Gohufont:size=12" but didn't work.
    Hm, wrong font name maybe? Does your slim log complain about it somehow?
    2. Is there a way to hide the cursor ( | ) and only see the characters.
    You should be able to do that via your slim.conf.
    1. No, slim.log only says:
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    The font is installed at "/usr/share/fonts/misc/"
    gohufont-11.pcf.gz
    gohufont-14.pcf.gz
    gohufont-uni-11.pcf.gz
    gohufont-uni-14.pcf.gz
    2. There's only an option to hide the mouse cursor, not the " | " that appears when typing something...
    Last edited by iJC (2013-10-13 03:34:07)

  • Arch-tetra SLiM theme

    AUR
    Github
    Inspiration from here.
    Looks like Rydgel never shared his theme, so I made something similar.
    The original probably uses a non-free font called 'Ginza Medium' which I don't have acces to, so I used 'Tetra ITC Std Light' for the logo which is pretty close to the original.
    Requires the 'artwiz-fonts' package for the 'edges' font.
    EDIT: Rydgel did relese his theme here
    Last edited by Beini (2013-03-18 11:04:34)

    ill wrote:I like it a lot, is there any chance of a high res version with anti-aliasing?
    I just released 1.1 which should be more antialiased. As for high-res version, I'm not entirely sure what you need, the background already is just an 200x200 square which tiles so any resolution should be fine. You can also find the .xcf for the logo here
    Last edited by Beini (2013-03-18 10:02:08)

  • Setting new GTK2 theme in openbox? [SOLVED]

    I downloaded the theme pack from this thread:
    http://bbs.archlinux.org/viewtopic.php?id=74915
    post #23
    I was able to get part of the theme working (menu color and window decoration) but the actual GTK2 theme is being difficult. I have installed lxappearance, gtk-chtheme, and switch 2 trying all of them but none seem to want to do anything with the .theme file. Is there a way to do this manually or am I going about it the wrong way?
    Last edited by beatepix (2009-07-21 00:39:38)

    I use lxappearance. Copy the whole Simplicity folder to ~/.themes/, start lxappearance, and select it. It's that simple! (and there's step by step instructions in the readme file included with each of my desktops)

  • Openbox Theme from GTK theme [beta]

    Something like this surely exists, here is my version..
    Creates an Openbox Theme from your chosen GTK Theme ... ..in 1), 2), 3)...
    1) you need to launch your theme changing from a script like this (instead of calling your GTK switcher directly)
    #!/bin/bash
    # call your gtk theme switcher and as it quits create a matching openbox theme
    # command for gtk theme switcher
    lxappearance
    # path to auto openbox theme generator script
    ~/bin/auto-openbox-theme
    # launch obconf (so you can select the newly made theme)
    obconf
    exit
    2) For that to work you also need this next script in ~/bin/auto-openbox-theme and made executable
    #!/bin/bash
    # Looks for the current GTK theme and automatically creates a matching Openbox theme
    # The script fails on themes not following the Clearlooks convention..
    # ..future improvements will account for this - for now the script politely fails on such themes.
    # function used to see if script is generating empty results from GTK it can't handle yet
    function emptycheck {
    if [ -s $myfile ]
    then
    echo "$myfile has data."
    else
    echo "$myfile is empty."
    xmessage "Sorry this gtk is not handled yet. You should not select the generated Openbox Theme this time."
    exit
    fi
    # main script #
    # copy ~/.gtkrc-2.0 to a new file and remove all data except theme name line (!d = don't delete)
    sed /gtk-theme-name/!d ~/.gtkrc-2.0 > ~/.gtk-match-openbox-info
    # remove string before gtk theme name and return info to this file (-i)
    sed -i s/gtk-theme-name=// ~/.gtk-match-openbox-info
    # strip off all (/g) speach marks (\") and return info to this file (-i)
    sed -i s/\"//g ~/.gtk-match-openbox-info
    # place the theme name in a variable
    mygtktheme=$(cat ~/.gtk-match-openbox-info)
    # copy file called mygtktheme to a new file
    sed /gtk_color_scheme/!d ~/.themes/"$mygtktheme"/gtk-2.0/gtkrc > ~/.gtk-match-openbox-info
    # strip the line down to just colours
    sed -i s/gtk_color_scheme\ =\ \"// ~/.gtk-match-openbox-info
    sed -i s/gtk-color-scheme\ =\ \"// ~/.gtk-match-openbox-info
    sed -i s/fg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/bg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/base_color\:#// ~/.gtk-match-openbox-info
    sed -i s/text_color\:#// ~/.gtk-match-openbox-info
    sed -i s/selected_bg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/selected_fg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/tooltip_bg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/tooltip_fg_color\:#// ~/.gtk-match-openbox-info
    sed -i s/\"//g ~/.gtk-match-openbox-info
    # force \n to be a true line break so colours on individual lines
    sed -i s/\n/\\n/g ~/.gtk-match-openbox-info
    sed -i 's/\\//g' ~/.gtk-match-openbox-info
    # store some colours for use in Openbox theme
    # don't delete (!d) line number n and place it in a text file colournX
    # where X is used later to aid production of Openbox theme
    sed '1!d' ~/.gtk-match-openbox-info > /tmp/colour1V
    sed '2!d' ~/.gtk-match-openbox-info > /tmp/colour2W
    sed '3!d' ~/.gtk-match-openbox-info > /tmp/colour3X
    sed '4!d' ~/.gtk-match-openbox-info > /tmp/colour4Y
    sed '5!d' ~/.gtk-match-openbox-info > /tmp/colour5Z
    # check if we have empty data from unhandled GTK themes
    myfile="/tmp/colour1V"
    emptycheck
    myfile="/tmp/colour2W"
    emptycheck
    myfile="/tmp/colour3X"
    emptycheck
    myfile="/tmp/colour4Y"
    emptycheck
    myfile="/tmp/colour5Z"
    emptycheck
    # hold the above in varibles
    myV=$(cat /tmp/colour1V)
    myW=$(cat /tmp/colour2W)
    myX=$(cat /tmp/colour3X)
    myY=$(cat /tmp/colour4Y)
    myZ=$(cat /tmp/colour5Z)
    # make Openbox theme by replacing VWXYZ in template with colours
    sed s/VVVVVV/$myV/g ~/.themes/obthemetemplate/openbox-3/TEMPLATE > /tmp/obtheme
    sed -i s/WWWWWW/$myW/g /tmp/obtheme
    sed -i s/XXXXXX/$myX/g /tmp/obtheme
    sed -i s/YYYYYY/$myY/g /tmp/obtheme
    sed s/ZZZZZZ/$myZ/g /tmp/obtheme > ~/.themes/obthemetemplate/openbox-3/themerc
    # update rc.xml
    #urxvt -e /usr/bin/obconf
    3) AND you need this folder in your ~/.themes/ folder - download it, extract and copy to ~/.themes
    4) (optional but welcome) Post your fails, post your abusive and constructive criticism, and post your "hey why don't you use this 5million times better version here?"'s
    thanks, bye

    Works fine here. Thanks for the script, it's quite handy and I got at last a nice OB theme witch fits with the murrina chrome gtk theme

  • [SOLVED] SLiM background no longer persists with Openbox

    Hello,
    I've been using SLiM and Openbox in conjunction for a while now, and one of the features I really liked was how, after logging in, the slim theme would become the Openbox desktop background.
    (I didn't set up any configuration file to do this. It happens by default, and as far as I know it might be a bug.)
    Recently, I decided to try out some other login managers. Eventually, I decided to return to using SLiM.
    Now, however, after logging in, Openbox blanks the screen, replacing the SLiM theme with the default grey background.
    I don't know if one of the other login managers modified some configuration files, or if something completely different is happening.
    In short, I have two questions:
    Has anyone else experienced this behaviour between SLiM and Openbox? If so, can anyone confirm whether or not the persistent background is a bug or intentional?
    What files cause Openbox to blank the screen on startup? How could I disable this?
    Thanks in advance for your help/input, everyone.
    Last edited by Dekusola (2014-08-05 20:49:08)

    I'm pretty sure this behavior is a bug. I use SLIM and if you don't set the background after you log in, the SLIM background will persist including any prompts that might pop up (try pressing F1 to bring up the WM selection prompt and then log in to see what I mean).
    I use hsetroot from the AUR with Openbox to set the background at start up by putting it in ~/.config/openbox/autostart.
    There are also other similiar programs you can use to set the background with openbox like nitrogen, feh, to name a few. Take your pick.
    Here is the relevant section from the openbox wiki page https://wiki.archlinux.org/index.php/Op … d_programs

Maybe you are looking for