Tag Info

Hot answers tagged

14

Here are some points you could start with: Have a look at the packages installed on your system with pacman -Q and remove the ones you don't need. A good start may be to append the -t switch: Restrict or filter output to packages not required by any currently installed package. Clean the package cache of pacman with pacman -Sc Always use pacman ...


7

Openbox will give the functionality you are looking for to windows whose _OB_APP_TYPE property is set to "desktop" (You can use obxprop to check the properties of a window). So we need to set the _OB_APP_TYPE for your terminator window to "desktop" so that this will happen. Reading through the openbox source code, in client.c I could see that _OB_APP_TYPE ...


6

There's probably hundreds of equally valid answers for this, but I use gmrun: It has miscellaneous useful features: You can run a command in a terminal using Ctrl+Enter It keeps a history of commands, so you can just keep hitting Up to cycle through them, or search through them with the standard shell mechanisms, Ctrl+R and !. It also has ...


6

Edit ~/.config/openbox/lxde-rc.xml with your favorite text editor and then, within the existing <keyboard> element, add the following lines: <keybind key="Print"> <action name="Execute"> <command>scrot</command> </action> </keybind> Use the openbox --reconfigure command to use the new settings. ...


5

The simplest is slock, the suckless screen locker. You could combine this with xautolock if you wanted to automate it after a period of inactivity. If you want something more "featurefull" you could install xscreensaver. Of course, gnome-screensaver is an option as well...


5

On LXDE ~/.config/openbox/lxde-rc.xml config is used instead. To check how openbox was started you can do: $ ps ax | grep openbox 2109 ? S 0:29 openbox --config-file /home/marcin/.config/openbox/lxde-rc.xml


4

Personally I use gnome-do for that kind of stuff. Yeah it's mono and some people don't like that, but if you enter a command. it runs it and when it's about running GUI applications it's a really quick way to trigger them. Since gnome-do has so many plugins, many of the actions I'd usually run via alt+F2 (like quickly mounting something) I can just do via ...


4

I had some success using bashrun. It's simple, has many features, and is very customizable. a few screenshots:


4

Alt+Space, x is the default shortcut for maximize/unmaximize in most window managers. Does that work? Or maybe it's Alt+F6 and Alt+F7 as suggested in the Actions Documentation. If not, you can add a binding using the information in the Openbox Bindings Documentation, but it sounds like you can only set shortcuts for all windows, not just for one program. ...


4

If you are talking about icons in your panel (like tint2, for example), then you can use xseticon (there is a PKGBUILD in AUR). You can set an icon for an application like so: xseticon -id "$WINDOWID" path/to/icon.png


4

Are you actually asking about having 'desktop icons', because it seems to be the situation. I'll go with the assumption that you want 'desktop' style icons, and still use the *box style right click menu. Yes it is possible, and some good guides already exist. Although Fluxbox is different from Openbox, the minimal environment is similar. The are quality ...


4

I think you would be better off just removing libnotify and notify-send from the equation, given your stated requirements they do not provide any additional flexibility of functionality. If you are looking for a minimal status bar, conky has a comprehensive amount of functionality, all of which can be updated in real time (depending upon how resource ...


4

That's not the right way to initiate a x session with openbox, Perhaps you meant to put that line in ~/.xinitrc, and execute startx instead. Remember that an X app can't be run outside the Xorg environment.


4

I have used arandr, this utility allows to save a script configuring your two screens. (I know there is also the utilityxrandr but I have not used it.) I have added this script to my startup in fluxbox (I don't know where to put it for openbox) so each time a session is started, my two monitors get configured. I don't understand what you mean with desktop ...


4

Yes, Gnome and KDE provide some of their own keyboard shortcuts in addition to the ones provided by their respective WMs. However, this may not mean what you think. The fact that Fn + UpArrow produces the keysym XF86AudioRaiseVolume is mainly due to your laptop's keyboard. You can verify this by using xev again (in the Openbox environment); It should have ...


4

First, Openbox depends on Xorg so it needs to and will be installed as a dependency. Second, you can set up your machine to boot only into a shell which is the standard for a minimal Debian install. Then you can run startx (if Xorg isinstalled) in that console and this command will start your X11. To start an Openbox session with startx you have to edit ...


4

After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.


4

The main practical implementation is that descendants of the window manager will inherit the environment variables of the window manager. This is helpful for dealing with cryptographic key agents such as gpg-agent or ssh-agent where the login manager starts up the agents so the window manager and its descendants inherit the SSH_AGENT_PID and SSH_AUTH_SOCK ...


4

xset --help usage: xset [-display host:dpy] option ... To control Energy Star (DPMS) features: -dpms Energy Star features off +dpms Energy Star features on dpms [standby [suspend [off]]] force standby force suspend force off force on (also implicitly enables DPMS features) ...


3

I have implemented this function by using wmctrl. The relevant part in rc.xml of openbox: <keybind key="A-space"> <action name="execute"> <execute>wmctrl-switch-by-application</execute> </action> </keybind> below is the code in wmctrl-switch-by-application: # taken from: http://www.st0ne.at/?q=node/58 # get ...


3

Almost certainly feh is loading the background, then something else is resetting the X background during the rest of the startup process. I suspect this has to do with the fact that you are firing up the gnome-settings-daemon. This starts a whopping chain of things that will include setting the background and other desktop settings like font rendering. You ...


3

KDE apps are written using Qt, so you need to use a Qt configuration tool (package qt4-qtconfig in Debian/Ubuntu)


3

(I assume you mean after a certain amount of time with no activity) slock doesn't have that capability built-in; you have to use another tool that watches X and tracks how long there's been no activity. For example, using xautolock with a delay of 15 minutes: $ xautolock -time 15 -locker slock


3

You can find key binding definitions here, And window actions here. An example here to set Ctrl + Shift + A for toggling window maxmize state: edit your ~/.config/openbox/rc.xml, put in these lines: <keybind key="C-S-a"> <action name="ToggleMaximize"> </action> </keybind>


3

As warl0ck noted, LXDE uses openbox as the WM, so you may just have a problem in your configuration settings. Hopefully these LXDE file locations should get you back on course: The config files of LXPanel are stored in ~/.config/lxpanel/. Under LXDE, we use a different profile name - LXDE. So it's in ~/.config/lxpanel/LXDE. In this way, if you changed the ...


3

It looks like a badly configured X server. Try the following: Boot normally. When you are at the login screen hit Ctrl+Alt+F2 (or any other F1-6 key) to drop to a CLI login screen. Login as root and stop the Display Manager. If you are using gdm: service gdm stop Generate a default xorg.conf file and copy it to /etc/X11: Xorg -configure cp xorg.conf.new ...


3

Apparently, it was the entry in ~/.config/openbox/lxde-rc.xml. Logging out and back in wasn't enough for some reason, but I rebooted and now my F11 key is back in action.


3

As far as I can tell, adding these lines to ~/.config/openbox/autostart should work. Unfortunately, I don't have openbox installed so I can't check. However, I can tell you why it does not work with ~/.xinitrc. ~/.xinitrc is only read when you are launching X manually from a tty using startx or xinit (see here). When you log in from a graphical loigin ...



Only top voted, non community-wiki answers of a minimum length are eligible