Openbox (한국어)

From ArchWiki
Jump to: navigation, search

Template:Temporary i18n Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary text Template:Article summary end

오픈박스는 가볍고 설정을 자유롭게 할 수 있으며 광범위한 표준을 지원하는 윈도 매니저이다. 오픈박스 공식 웹사이트에 그 기능들이 설명되어 있다. 이 문서는 아치 리눅스에서 오픈박스를 설치하는 것에 대한 것이다.

설치

공식 저장소에 있는 오픈박스를 설치한다. 그 다음에 기본 설정 파일인 rc.xml, menu.xml, autostartenvironment~/.config/openbox로 복사한다.

Note: 루트 권한이 없는 보통 사용자로 이것을 실행한다.
$ mkdir -p ~/.config/openbox
$ cp /etc/xdg/openbox/{rc.xml,menu.xml,autostart,environment} ~/.config/openbox

이 파일 네 개가 오픈박스를 기본적으로 설정한다. 각 파일은 특정한 부분을 설정하는데 각 파일에 대한 설명은 다음과 같다.

rc.xml
이 파일이 기본 설정 파일이다. 키보드 단축키, 테마, 시각효과 등을 설정한다.
menu.xml
이 파일은 마우스 오르쪽 클릭 메뉴를 설정한다. 프로그램 실행기와 기타 빠른 실행을 설정한다. #Menus 부분을 참고하라.
autostart
오픈박스 실행 시에 openbox-session이 읽어 들인다. 오픈박스 실행 시에 시작하는 프로그램을 포함한다. 보통 환경 변수를 설정하거나 패널/독을 실행하거나 배경화면을 설정하거나 시작 스크립트를 실행하는 데에 사용된다. 오픈박스 위키를 참고하라.
environment
오픈박스 실행 시에 openbox-session이 읽어 들인다. 오픈박스에서 설정될 환경 변수를 포함한다. 여기에 설정된 어떤 변수라도 오픈박스 그 자체와 오픈박스 메뉴에서 실행하는 모두에 적용될 것이다.

Upgrading to Openbox 3.5

If you are upgrading to Openbox 3.5 or later from an earlier release, be aware of these changes:

  • There is a new config file called environment that you should copy from /etc/xdg/openbox to ~/.config/openbox.
  • The config file previously called autostart.sh is now just called autostart. You should rename yours to remove the .sh from the end of the name.
  • Some of the configuration grammar in rc.xml has changed. While Openbox appears to understand the old options, it would be wise to compare your configuration to the one in /etc/xdg/openbox and look for changes that affect you.

Openbox as a stand-alone WM

Openbox can be used as a stand-alone window manager (WM). This is usually simpler to install and configure than using Openbox with desktop environments. Running openbox alone may reduce your system's CPU and memory load.

To run Openbox as a stand-alone window manager, append the following to ~/.xinitrc:

exec openbox-session

You may also start Openbox from the command shell (aka: text prompt) using xinit:

$ xinit /usr/bin/openbox-session

If you used another window manager previously (such as Xfwm) and now Openbox will not start after logging out of X, try moving the autostart folder:

mv ~/.config/autostart ~/.config/autostart-bak

Using ConsoleKit, use this instead:

exec ck-launch-session openbox-session

If you also use PolicyKit and D-Bus (e.g. for automatically mounting drives in Nautilus/GNOME) use:

exec ck-launch-session dbus-launch openbox-session
Note: pyxdg is required for Openbox's xdg-autostart
Note: dbus-launch must be placed after ck-launch-session or you will experience mounting problems.

Openbox as a WM for desktop environments

Openbox can be used as a replacement window manager for full-fledged desktop environments. The method for deploying Openbox depends on the desktop environment.

GNOME 2.24 and 2.26

Create /usr/share/applications/openbox.desktop with the following lines:

[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=OpenBox
Exec=openbox
NoDisplay=true
# name of loadable control center module
X-GNOME-WMSettingsModule=openbox
# name we put on the WM spec check window
X-GNOME-WMName=OpenBox

In gconf, set /desktop/gnome/session/required_components/windowmanager to openbox:

$ gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox

Finally, choose the GNOME session from the GDM sessions menu.

GNOME 2.26 redux

If the previous guide for GNOME 2.24 fails:

If, when attempting to log into a "Gnome/Openbox" session -- and it consistently fails to start, try the following. This is one way of achieving your goal of using Openbox as the WM anytime you open a Gnome session:

  1. Log into your Gnome-only session (it should still be using Metacity as its window manager).
  2. Install Openbox if you have not done so already
  3. Navigate your menus to System → Preferences → Startup Applications (possibly named 'Session' in older Gnome versions)
  4. Open Startup Application, select '+ Add' and enter the text shown below. Omit the text after #.
  5. Click the 'Add' button for the data entry window. Make sure the checkbox beside your new entry is selected.
  6. Log out from your Gnome session and log back in
  7. You should now be running openbox as your window manager.
Name:    Openbox Windox Manager          # Can be changed
Command: openbox --replace               # Text should not be removed from this line, but possibly added to it
Comment: Replaces metacity with openbox  # Can be changed

This creates a startup list entry which is executed by Gnome each time the user's session is started.

GNOME 2.22 and prior

  1. If you use GDM, select the "GNOME/Openbox" login option
  2. If you use startx, add exec openbox-gnome-session to ~/.xinitrc
  3. From the shell:
$ xinit /usr/bin/openbox-gnome-session

KDE

  1. If you use KDM, select the "KDE/Openbox" login option.
  2. Open System Settings > Default Applications (in the Workspace Appearance and Behaviour section), and change the default window manager to Openbox (this will also avoid having to log out and log back in again).
  3. If you use startx, add exec openbox-kde-session to ~/.xinitrc
  4. From the shell:
$ xinit /usr/bin/openbox-kde-session

Xfce4

Log into a normal Xfce4 session. From your terminal, type:

$ killall xfwm4 ; openbox & exit

This kills xfwm4, runs Openbox, and closes the terminal. Log out, being sure to check the "Save session for future logins" box. On your next login, Xfce4 should use Openbox as its window manager.

Alternatively, you can chooose Settings -> Session and Startup from menu, go to the Application Autostart tab and add openbox --replace to the list of automatically started applications.

To enable exiting from a session using xfce4-session, edit ~/.config/openbox/menu.xml. If the file is not there, copy it from /etc/xdg/openbox/. Look for the following entry:

 <item label="Exit Openbox">
   <action name="Exit">
     <prompt>yes</prompt>
   </action>
 </item>

Change it to:

 <item label="Exit Openbox">
   <action name="Execute">
     <prompt>yes</prompt>
    <command>xfce4-session-logout</command>
   </action>
 </item>

Otherwise, choosing "Exit" from the root-menu causes Openbox to terminate its execution, leaving you with no window manager.

If you have a problem changing virtual desktops with the mouse wheel skipping over desktops, edit ~/.config/openbox/rc.xml. Move the mouse binds with... actions "DesktopPrevious" and "DesktopNext" from context Desktop to the context Root. Note that you may need to create a definition for the Root context as well.

When using the Openbox root-menu instead of Xfce's menu, you may exit the Xfdesktop with this terminal command:

$ xfdesktop --quit

Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities such as ROX for these functions.

(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)

Openbox for multihead users

While Openbox provides better than average multihead support on its own, a branch called Openbox Multihead is now available in the AUR that gives multihead users per-monitor desktops. This model is not commonly found in floating window managers, but exists mainly in tiling window managers. It is explained well on the Xmonad web site. Also, please see README.MULTIHEAD for a more comprehensive description of the new features and configuration options found in Openbox Multihead.

Openbox Multihead will function like normal Openbox when only a single head is available.

A downside to using Openbox Multihead is that it breaks the EWMH assumption that one and only one desktop is visible at any time. Thus, existing pagers will not work well with it. To remedy this, pager-multihead can be found in the AUR that is compatible with Openbox Multihead. Screenshots.

Finally, a new version of pytyle can also be found in the AUR that will work with Openbox Multihead.

Both pytyle3 and pager-multihead will work without Openbox Multihead if only one monitor is active.

Configuration

There are several options for configuring Openbox settings:

Manual configuration

To configure Openbox manually, edit the ~/.config/openbox/rc.xml file with a text editor. The file has explanatory comments throughout. See the Help:Configuration openbox wiki for more documentation on editing this file.

ObConf

ObConf is an Openbox configuration tool. It is used to set most common preferences such as themes, virtual desktops, window properties, and desktop margins. It can be installed with pacman:

# pacman -S obconf

ObConf cannot configure keyboard shortcuts and certain other features. For these features edit rc.xml manually. Alternatively, you can try obkeyAUR from the AUR.

Application customization

Openbox allows per-application customizations. This lets you define rules for a given program. For example:

  • Start your web browser on a specific virtual desktop.
  • Open your terminal program with no window decorations (window chrome).
  • Make your bit-torrent client open at a given screen position.

Per-application settings are defined in ~/.config/openbox/rc.xml. Instructions are in the file's comments. More details are found in the Help:Applications openbox wiki.

Menus

The default Openbox menu includes a variety of menu items to get you started. Many of these items launch applications you do not want, have not installed yet, or never intend to install. You will surely want to customize menu.xml at some point. There are a number of ways to do so.

Manual configuration of menus

You can edit ~/.config/openbox/menu.xml with a text editor. Many of the settings are self-explanatory. The article Help:Menus has extensive details.

Icons in menu

Since version 3.5.0 you can have icons next to your menu entries. To do that :

  1. add <showIcons>yes</showIcons> in the <menu> section of the rc.xml file
  2. edit the menu entries in menu.xml and add icons="<path>" like this :
<menu id="apps-menu" label="SomeApp" icon="/home/user/.icons/application.png">

then openbox --reconfigure or openbox --restart if you have troubles updating the menu :)

MenuMaker

MenuMaker creates XML menus for several window managers including Openbox. MenuMaker searchs your computer for executable programs and creates a menu file from the result. It can be configured to exclude certain application types (GNOME, KDE, etc) if you desire.

# pacman -S menumaker    #  Install MenuMaker from the repository

Once installed, generate a menu file (named menu.xml) by running the program.

$ mmaker -v OpenBox3     #  Will not overwrite an existing menu file.
$ mmaker -vf OpenBox3    #  Force option permits overwriting the menu file.
$ mmaker --help          #  See the full set of options for MenuMaker.

MenuMaker creates a comprehensive menu.xml. You may edit this file by hand or regenerate it after installing software.

Obmenu

Obmenu is a menu editor for Openbox. This GUI application is the best choice for those who dislike editing XML code. Obmenu is available in the community repository:

# pacman -S obmenu

Once installed, run obmenu then add and remove applications as desired.

Obm-xdg

obm-xdg is a command-line tool that comes with Obmenu. It generates a categorized sub-menu of installed GTK/GNOME applications.

To use obm-xdg with other menus, add the following line to ~/.config/openbox/menu.xml:

<menu execute="obm-xdg" id="xdg-menu" label="xdg"/>

Then add the following line under your 'root-menu' entry where you want to have the menu appear:

<menu id="xdg-menu"/>

Then run openbox --reconfigure to refresh the Openbox menu. You should now see a sub-menu labeled xdg in your menu.

To use obm-xdg by itself, create ~/.config/openbox/menu.xml and add these lines:

<openbox_menu>
 <menu execute="obm-xdg" id="root-menu" label="apps"/>
</openbox_menu>
Note: If you do not have GNOME installed, you need to install the package gnome-menus for obm-xdg.

openbox-menu

Openbox-menu uses menu-cache from the LXDE Project to create dynamic menus for Openbox.

Project homepage here: http://mimasgpc.free.fr/openbox-menu_en.html

AUR Package here: [1]

Python-based xdg menu script

This script is found in Fedora's Openbox package. You have only to put the script somewhere and create a menu entry.

Here is the head: latest script

Download from the above repository. Place the file into the directory you want.

Open menu.xml with your text editor and add the following entry. Of course, you can modify the label as you see fit.

<menu id="apps-menu" label="xdg-menu" execute="python2 <path>/xdg-menu"/>

Save the file and run openbox --reconfigure.

Note: If you do not have GNOME installed, you need to install the package gnome-menus for xdg-menu.

Openbox menu generator

Residing in the AUR as obmenugen-bin, Openbox menu generator creates the menu file from *.desktop files. Obmenugen provides a text file which filters (hides) menu items using basic regex.

$ obmenugen               # Create a menu file
$ openbox --reconfigure   # To see the menu you generated

Pipe menus

Like other window managers, Openbox allows for scripts to dynamically build menus (menus on-the-fly). Examples are system monitors, media player controls, or weather monitors. Pipe menu script examples are found in the Openbox:Pipemenus page at Openbox's site.

User Xyne created a pipe menu file browser and user brisbin33 created a pipe menu for scanning and connecting to wireless hot spots (using netcfg). Forum posts for these utilities are here: file browser and here: wifi.

User jnguyen created a pipe menu for managing removable devices using Udisks. The forum post is here: obdevicemenu.

Startup programs

Openbox supports running programs at startup. This is provided by command openbox-session.

Enabling autostart

There are two ways to enable autostart:

  1. When using startx or xinit to begin a session, edit ~/.xinitrc. Change the line that executes openbox to openbox-session.
  2. When using GDM or KDM, selecting an Openbox session automatically runs the autostart script.

Autostart script

Openbox provides a system-wide startup script which applies to all users and is located at /etc/xdg/openbox/autostart. A user may also create his own startup script to be executed after the system-wide script by creating the file ~/.config/openbox/autostart. This file is not provided by default and must be created by the user.

Further instructions are available in the Help:Autostart article at the official Openbox site.

Note: The autostart files used to be named autostart.sh prior to OpenBox 3.5.0. While these scripts will presently still work, users who are upgrading are advised to drop the .sh extension.

Autostart directory

Openbox also starts any *.desktop files in /etc/xdg/autostart - this happens regardless of whether a user startup script is present. nm-applet, for example, installs a file at this location, and may cause it to run twice for users with the usual (sleep 3 && /usr/bin/nm-applet --sm-disable) & in their startup script. There is a discussion on managing the effects of this at [2].

Themes and appearance

Template:Box YELLOW

Openbox themes

Themes control the appearance of windows, titlebars, and buttons. They also control menu appearance and on-screen display (OSD). Additional themes are available from the standard repositories.

# pacman -S openbox-themes

Cursors, icons, wallpaper

Please see Openbox Themes and Apps for information on these GUI customizations.

Recommended programs

Template:Box YELLOW

There is a list of Lightweight Applications in the wiki. Most of these work nicely with Openbox.

Tips and tricks

Aero snap behaviour

Windows 7 supports a unique window behaviour to snap windows when they are moved to the edge of the screen. This effect can also be achieved through an Openbox keybinding. More information here.

File associations

Because Openbox and the applications you use with it are not well-integrated you might run into the issues with your browser. Your browser may not know which program it is supposed to use for certain types of files.

A package in the AUR called gnome-defaults-list contains a list of file-types and programs specific to the Gnome desktop. The list is installed to /etc/gnome/defaults.list.

Open this file with your text-editor. Now you can replace a given application with the name of the program of your choosing. For example, totem <=> vlc or eog <=> mirage. Save the file to ~/.local/share/applications/defaults.list.

Another way of setting file associations is to install package perl-file-mimeinfo from the repository and invoke mimeopen like this:

mimeopen -d /path/to/file

You are asked which application to use when opening /path/to/file:

Please choose a default application for files of type text/plain
       1) notepad  (wine-extension-txt)
       2) Leafpad  (leafpad)
       3) OpenOffice.org Writer  (writer)
       4) gVim  (gvim)
       5) Other...

Your answer becomes the default handler for that type of file. Mimeopen is installed as /usr/bin/perlbin/vendor/mimetype.

Copy and paste

From a terminal Template:Keypress for copy and Template:Keypress for paste.

Also Template:Keypress for copy and mouse middle-click for paste (in terminals).

Other applications most likely use the conventional keyboard shortcuts for copy and paste.

Window transparency

The program transset-df (virtually the same as transset) is installed with pacman -S transset-df. With transset-df you can enable window-transparency on-the-fly.

For instance by placing the following in ~/.config/openbox/rc.xml you can have your mouse adjust window transparency by scrolling while hovering over the title bar (it is in the <mouse> section):

    <context name="Titlebar">
     . . .
     <mousebind button="Up" action="Click">
       <action name= "Execute" >
       <execute>transset-df -p .2 --inc  </execute>
       </action>
     </mousebind>
     <mousebind button="Down" action="Click">
       <action name= "Execute" >
       <execute>transset-df -p .2 --dec </execute>
       </action>
     </mousebind>
     . . .
   </context>

It appears to work only when no additional actions are defined within the action group.

Xprop values for applications

If you use per-application settings frequently, you might find this bash alias handy:

alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'

To use, run xp and click on the running program that you would like to define with per-app settings. The result displays only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:

[thayer@dublin:~] $ xp
WM_WINDOW_ROLE(STRING) = "roster"
WM_CLASS(STRING) = "gajim.py", "Gajim.py"
WM_CLASS(STRING) = "NAME", "CLASS"

Xprop for Firefox

For whatever reason, Firefox and like-minded equivalents ignore application rules (e.g. <desktop>) unless class="Firefox*" is used. This applies irrespective of whatever values xprop may report for the program's WM_CLASS.

Linking the menu to a button

Some people want to link the Openbox menu (or any menu) to an object. This is useful for creating a panel button to pop up a menu. Although Openbox does not provide this, a program called xdotool (available in community repo) simulates a keypress. Openbox can be configured to bind that keypress to the ShowMenu action.

After installing xdotool, add the following to the <keyboard> section of your rc.xml:

 <keybind key="A-C-q">
   <action name="ShowMenu">
     <menu>root-menu</menu>
   </action>
 </keybind>

Restart/reconfigure Openbox. The following command summons a menu at your cursor position. The command may given as-is, linked to an object, or placed in a script.

$ xdotool key ctrl+alt+q

Of course, change the key shortcut to your liking. Here is a snippet from a tint2 (a taskbar-like panel) configuration file which pops up a menu when the clock area is clicked. Each key combination is set to open a menu within openbox's rc.xml configuration file. The right‑click menu is different from the left‑click menu:

clock_rclick_command = xdotool key --clearmodifiers "ctrl+XF86PowerOff"
clock_lclick_command = xdotool key --clearmodifiers "alt+XF86PowerOff"

Urxvt in the background

With Openbox, running a terminal as desktop background is easy. You will not need devilspie here.

First you must enable transparency, open your .Xdefaults file (if it does not exist yet, create it in your home folder).

URxvt*transparent:true
URxvt*scrollBar:false
URxvt*geometry:124x24    #I do not use the whole screen, if you want a full screen term do not bother with this and see below.
URxvt*borderLess:true
URxvt*foreground:Black   #Font color. My wallpaper is White, you may wish to change this to White.

Then edit your .config/openbox/rc.xml file:

<application name="urxvt">
  <decor>no</decor>
  <focus>yes</focus>
  <position>
    <x>center</x>
    <y>20</y>
  </position>
  <layer>below</layer>
  <desktop>all</desktop>
  <maximized>true</maximized> #Only if you want a full size terminal.
</application>

The magic comes from the <layer>below</layer> line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.

Note: Instead of using <application name="URxvt">, you can use another name ("URxvt-bg" for example), and use the -name option when starting uxrvt. That way, only the urxvt terminals which you choose to name URxvt-bg would be captured and modified by the application rule in rc.xml. For example: urxvt -name URxvt-bg (case sensitive)

ToggleShowDesktop exception

Above method still minimizes Urxvt when using the ToggleShowDesktop command. A method for avoiding this is explained in this forum post. This involves editing Urxvt's source code.

Note: This method seems to have been broken in a recent update, now leading to a memory leak when the patched Urxvt is run.

The only working method at the moment seems to be the one outlined here. This makes ToggleShowDesktop a one-way action, not restoring the other desktop applications when ToggleShowDesktop is run for a second time. It also creates the opportunity to use a different terminal emulator than Urxvt, however.

Keyboard volume control

ALSA

If you use ALSA for sound, you can use the amixer program to adjust the volume of sound. You can use Openbox's keybindings to act like multimedia keys. (Alternatively, you can probably find out the names of your real multimedia keys and map them.) For example, in the <keyboard> section of rc.xml:

   <keybind key="W-Up">
     <action name="Execute">
       <command>amixer set Master 5%+</command>
     </action>
   </keybind>

This binds Windows key + Up arrow to increase your master ALSA volume by 5%. Corresponding binding for volume down:

   <keybind key="W-Down">
     <action name="Execute">
       <command>amixer set Master 5%-</command>
     </action>
   </keybind>

As another example you can also use the XF86Audio keybindings:

   <keybind key="XF86AudioRaiseVolume">
     <action name="Execute">
       <command>amixer set Master 5%+ unmute</command>
     </action>
   </keybind>
   <keybind key="XF86AudioLowerVolume">
     <action name="Execute">
       <command>amixer set Master 5%- unmute</command>
     </action>
   </keybind>
   <keybind key="XF86AudioMute">
     <action name="Execute">
       <command>amixer set Master toggle</command>
     </action>
   </keybind>

The above example should work for the majority of multimedia keyboards. It should enable to raise, lower and mute the Master control of your audio device by using the respective multimedia keyboard keys. Notice also that in this example:

  • The "Mute" key should unmute the Master control if it is already in mute mode.
  • The "Raise" and "Lower" keys should unmute the Master control if it is in mute mode.

Pulseaudio

If you are using pulseaudio with ALSA as a backend the above keybinding are slightly different as amixer must be told to use pulse.

  <keybind key="XF86AudioRaiseVolume">
     <action name="Execute">
       <command>amixer -D pulse set Master 5%+ unmute</command>
     </action>
   </keybind>
   <keybind key="XF86AudioLowerVolume">
     <action name="Execute">
       <command>amixer -D pulse set Master 5%- unmute</command>
     </action>
   </keybind>
   <keybind key="XF86AudioMute">
     <action name="Execute">
       <command>amixer set Master toggle</command>
     </action>
   </keybind>

This keybindings should work for most of the systems. Other examples can be found here.

Troubleshooting Openbox 3.5

X server crashes

Problems have been detected after upgrade to ver. 3.5, that the X server might crash in attempt to start openbox, ending with similar error message:

(metacity:25137): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process \
                   was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit \
                   status can't be returned. This is a bug in the program calling g_spawn_sync(); either do not request \
                   the exit status, or do not set the SIGCHLD action.
xinit: connection to X server lost
waiting for X server to shut down

In this particular case, some problem with metacity package has been identified as the cause of the X server crash issue. Removal of metacity & compiz-decorator-gtk packages solved the problem. Though, later was found, that even a simple reinstall of packages might have helped, as there is no problem after new installation of previously removed packages.

Also, plenty of similar cases have been found on the Internet, that not only metacity package might be causing the X server to crash. Thus, whatever else instead of metacity you get in the error output message, try to reinstall it (or remove if necessary) in an attempt to get rid of this X server crash.

Autostarting unwanted applications in 3.5

Unwanted applications do start with your Openbox session, though they are not listed in your ~/.config/openbox/autostart script?

Check the ~/.config/autostart/ directory, it might contain the residues from your previously used desktop environment (GNOME, KDE, etc.), and remove unwanted files.

SSH agent no longer starting

Whereas Openbox 3.4.x allowed launching an SSH agent from $XDG_CONFIG_HOME/openbox/autostart{,.sh}, with 3.5 that no longer seems to work. You need to put your code in $XDG_CONFIG_HOME/openbox/environment, e.g.:

SSHAGENT="/usr/bin/ssh-agent"
SSHAGENTARGS="-s"
if [ -z "$SSH_AUTH_SOCK" -a -x "$SSHAGENT" ]; then
        eval `$SSHAGENT $SSHAGENTARGS`
        trap "kill $SSH_AGENT_PID" 0
fi

Openbox not registering with D-Bus

Just like with SSH agent, lots of people used to have D-Bus code in $XDG_CONFIG_HOME/openbox/autostart{,.sh} - which no longer works (e.g. Thunar does not see any removable devices anymore).

The fix is to move the code to $XDG_CONFIG_HOME/openbox/environment:

if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
       eval `dbus-launch --sh-syntax --exit-with-session`
fi

Alternatively you can call openbox-session with dbus-launch in ~/.xinitrc.

See also