I am using xubuntu 18.04, but this question should preferably be applicable to all linux installations having both desktop managers "xfce" and "fluxbox". So I have started with xubuntu (i.e. ubuntu with xfce) but I have also apt install fluxbox as well. In "Xfce" I use xfce4-settings-manager to select a theme, the result for "Adwaita-dark" theme is shown below, for the "x-terminal-emulator" application: However, when I switch to "fluxbox": As you can see the window's menubar, as well as the preferences window do not obey the selected theme. This is a problem in "nautilus" file manager as well, but not for other applications (such as "Thunar" file manager, which works correctly) Does it perhaps not follow "gtk-2.0" styles ? For that I have set gtk-3.0 in "~/.config/gtk-3.0/settings.ini" [Settings] gtk-theme-name = Adwaita-dark gtk-icon-theme-name = SimplyGrey gtk-fallback-icon-theme = gnome gtk-font-name = Sans 10 # next option is applicable only if selected theme supports it gtk-application-prefer-dark-theme = true I have also setup QT to use GTK+ styles, but the issue persists. What am I missing here ?

I want to map the Ctrl+Alt+4 to take a screenshot of a selected area. Right now I can do that from a terminal using gnome-screenshot -a. I have tried putting: Control Mod1 4 :ExecCommand gnome-screenshot -a` in my ~/.fluxbox/keys but that does not work -- probably because of the space before -a. Is there a way to map those key combination to take a screenshot of a selected area?

I'm trying to setup Fluxbox to look nice on my machine as I familiar with it and find it functional. One thing stoping me from moving to it fulltime, while seemingly trivial, is that it looks *ugly*. I have a 1680x1050 screen and fluxbox does not seem to have even basic anti-alliasing. Menus and corners of windows look jagged and, well, not nice. What can I do to make Fluxbox look nicer? e.g. include anti-alliasing, maybe get transparency working....

This is my question: how to configure the Fluxbox slit side panel (taskbar which contains dockable apps) for avoiding to auto-hide?

I am running Fluxbox 1.3.7 and polybar 3.5.7 Whenever I maximize a window, polybar is overlapping the top of the window. Is it possible to make windows treat polybar as a border? in other words, is it possible to get maximized windows to leave room for polybar? I have tried override-redirect = true which simply makes the bar unmovable, but does not prevent it from overlapping maximized windows. Also I don't believe the wm-restack option is applicable here as that only supports i3 and bspwm Thanks.

I'm running fluxbox without any DE. For some reason I lost the ability to raise the desktop and window frame context menus with the right mouse button. I found that fluxbox did not place a "fluxbox" file into /user/share/menu/ as it should. Creating it by hand did not help. The other files there look OK as do the files in ~/.fluxbox, including the menu file. I ran # update-menus with no effect Perhaps unrelated, but the menu problem coincided with a problem configuring the nvidia-persistenced package. The package is installed but only partially configured. When I reinstall it I get this: Setting up nvidia-persistenced (460.32.03-1) ... Starting NVIDIA Persistence Daemon nvidia-persistenced failed to initialize. Check syslog for more details. invoke-rc.d: initscript nvidia-persistenced, action "start" failed. dpkg: error processing package nvidia-persistenced (--configure): installed nvidia-persistenced package post-installation script subprocess retu> There's no report of an error in syslog.

On **FreeBSD 13**, I installed **Fluxbox** and added two menu entries to the *Fluxbox menu*: [exec] (Lazarus IDE) {lazarus} [exec] (Set Resolution) {xrandr -s 1680x1050} Both of these show up on the *Fluxbox menu*, but do nothing when clicked. I have tried giving the full path of the program too: [exec] (Lazarus IDE) {/usr/local/bin/lazarus} That also doesn't work. The commands however work fine through Xterm in Fluxbox. What am I doing wrong here? --- **Update**: When I run lazarus from the terminal, I noticed the output states: TLazarusManager.Run starting /home/s/.lazarus/bin/lazarus ... But even that path doesn't execute from FluxBox menu.

I recently installed OpenBSD on my sparc64 workstation and I wanted to use fluxbox for my desktop environment. When I install it and try to start it it gives a error saying "couldn't connect to xserver passing null display" I looked online an saw something about editing the .xsession file but it is not there I only have the root user because I didn't set up any other users but I did reinstall it once and added a user with but the file still wasn't there. I want to make fluxbox start automatically after logging in. I am very new to UNIX so please help. Edit: I actually also wanted to try icewm but it gives the error "cant open display: . X must be running and $DISPLAY set."

This issue is driving me crazy. I have no clue why it sometimes happens. Its totally feeling intermittent. I have a /etc/rc.local shell script that fires off on startup. I am using Ubuntu x64 19.10... For what its worth, I run this off a cloud droplet via Digital Ocean. Long story short... My script has at the beginning something like this...

echo "Starting virtual display session..."
export DISPLAY=:0
Xvfb :0 -screen 0 640x360x16 & 
DISPLAY=:0.0 fluxbox &
sleep 1
x11vnc -display :0.0 -usepw -forever -bg

All of this works most of the time.... However the fluxbox sometimes just will not load. I will end up with a X display session but no window manager. When I run ps aux | grep fluxbox I see nada. The issue is that it only happens sometimes. I can reboot the system and most of the time it will load, but on occasion it just totally does not start process. UPDATE: I can see the following error happen when this seems to occur:

Error: Couldn't connect to XServer:0.0

Why is this happening if I am setting the export of the display and also setting the display when I start the fluxbox process? Does anyone have any idea? Note: I only have the virtual frame buffer via xvfb and it always runs on DISPLAY=:0 Thank you! 🙏

I am setting up a Debian 10 with fluxbox window manager. One of the components I need is miniconda, I've installed everything from the initial bash (no desktop) and everything works fine. Miniconda installation alters the /.bashrc file, appending the following lines to its contents: # >>> conda initialize >>> # !! Contents within this block are managed by 'conda init' !! __conda_setup="$('/opt/miniconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)" if [ $? -eq 0 ]; then eval "$__conda_setup" else if [ -f "/opt/miniconda3/etc/profile.d/conda.sh" ]; then . "/opt/miniconda3/etc/profile.d/conda.sh" else export PATH="/opt/miniconda3/bin:$PATH" fi fi unset __conda_setup # type_conda_out.txt conda is a function conda () { if [ "$#" -lt 1 ]; then "$CONDA_EXE" $_CE_M $_CE_CONDA; else \local cmd="$1"; shift; case "$cmd" in activate | deactivate) __conda_activate "$cmd" "$@" ;; install | update | upgrade | remove | uninstall) CONDA_INTERNAL_OLDPATH="${PATH}"; __add_sys_prefix_to_path; "$CONDA_EXE" $_CE_M $_CE_CONDA "$cmd" "$@"; \local t1=$?; PATH="${CONDA_INTERNAL_OLDPATH}"; if [ $t1 = 0 ]; then __conda_reactivate; else return $t1; fi ;; *) CONDA_INTERNAL_OLDPATH="${PATH}"; __add_sys_prefix_to_path; "$CONDA_EXE" $_CE_M $_CE_CONDA "$cmd" "$@"; \local t1=$?; PATH="${CONDA_INTERNAL_OLDPATH}"; return $t1 ;; esac; fi } root@Zumbi:~# /opt/miniconda3/bin/conda shell.bash hook > hook_out.txt export CONDA_EXE='/opt/miniconda3/bin/conda' export _CE_M='' export _CE_CONDA='' export CONDA_PYTHON_EXE='/opt/miniconda3/bin/python' # Copyright (C) 2012 Anaconda, Inc # SPDX-License-Identifier: BSD-3-Clause __add_sys_prefix_to_path() { # In dev-mode CONDA_EXE is python.exe and on Windows # it is in a different relative location to condabin. if [ -n "${_CE_CONDA}" ] && [ -n "${WINDIR+x}" ]; then SYSP=$(\dirname "${CONDA_EXE}") else SYSP=$(\dirname "${CONDA_EXE}") SYSP=$(\dirname "${SYSP}") fi if [ -n "${WINDIR+x}" ]; then PATH="${SYSP}/bin:${PATH}" PATH="${SYSP}/Scripts:${PATH}" PATH="${SYSP}/Library/bin:${PATH}" PATH="${SYSP}/Library/usr/bin:${PATH}" PATH="${SYSP}/Library/mingw-w64/bin:${PATH}" PATH="${SYSP}:${PATH}" else PATH="${SYSP}/bin:${PATH}" fi \export PATH } __conda_hashr() { if [ -n "${ZSH_VERSION:+x}" ]; then \rehash elif [ -n "${POSH_VERSION:+x}" ]; then : # pass else \hash -r fi } __conda_activate() { if [ -n "${CONDA_PS1_BACKUP:+x}" ]; then # Handle transition from shell activated with conda = 4.4. See issue #6173. PS1="$CONDA_PS1_BACKUP" \unset CONDA_PS1_BACKUP fi \local cmd="$1" shift \local ask_conda CONDA_INTERNAL_OLDPATH="${PATH}" __add_sys_prefix_to_path ask_conda="$(PS1="$PS1" "$CONDA_EXE" $_CE_M $_CE_CONDA shell.posix "$cmd" "$@")" || \return $? rc=$? PATH="${CONDA_INTERNAL_OLDPATH}" \eval "$ask_conda" if [ $rc != 0 ]; then \export PATH fi __conda_hashr } __conda_reactivate() { \local ask_conda CONDA_INTERNAL_OLDPATH="${PATH}" __add_sys_prefix_to_path ask_conda="$(PS1="$PS1" "$CONDA_EXE" $_CE_M $_CE_CONDA shell.posix reactivate)" || \return $? PATH="${CONDA_INTERNAL_OLDPATH}" \eval "$ask_conda" __conda_hashr } conda() { if [ "$#" -lt 1 ]; then "$CONDA_EXE" $_CE_M $_CE_CONDA else \local cmd="$1" shift case "$cmd" in activate|deactivate) __conda_activate "$cmd" "$@" ;; install|update|upgrade|remove|uninstall) CONDA_INTERNAL_OLDPATH="${PATH}" __add_sys_prefix_to_path "$CONDA_EXE" $_CE_M $_CE_CONDA "$cmd" "$@" \local t1=$? PATH="${CONDA_INTERNAL_OLDPATH}" if [ $t1 = 0 ]; then __conda_reactivate else return $t1 fi ;; *) CONDA_INTERNAL_OLDPATH="${PATH}" __add_sys_prefix_to_path "$CONDA_EXE" $_CE_M $_CE_CONDA "$cmd" "$@" \local t1=$? PATH="${CONDA_INTERNAL_OLDPATH}" return $t1 ;; esac fi } if [ -z "${CONDA_SHLVL+x}" ]; then \export CONDA_SHLVL=0 # In dev-mode CONDA_EXE is python.exe and on Windows # it is in a different relative location to condabin. if [ -n "${_CE_CONDA+x}" ] && [ -n "${WINDIR+x}" ]; then PATH="$(\dirname "$CONDA_EXE")/condabin${PATH:+":${PATH}"}" else PATH="$(\dirname "$(\dirname "$CONDA_EXE")")/condabin${PATH:+":${PATH}"}" fi \export PATH # We're not allowing PS1 to be unbound. It must at least be set. # However, we're not exporting it, which can cause problems when starting a second shell # via a first shell (i.e. starting zsh from bash). if [ -z "${PS1+x}" ]; then PS1= fi fi root@Zumbi:~# type -f conda bash: type: conda: not found ``` ===EDIT 2=== Only now, while editing FB's menu, I could see how xterm is called: it is done by a wrapper: x-terminal-emulator -T "Bash" -e /bin/bash --login and the --login option, as explained in bash documentation , > Make bash act as if it had been invoked as a login shell So it explains why bash was not getting $PATH. Using fbrun xterm results in a bash with the default, initialized system $PATH as expected.

I have no idea about this. The first time it happened was that I installed wine. But now if I rm -r .fluxbox/ It returns; However I need all my configuration files, so I simply cp old-fluxbox/xxx .fluxbox/ It's gone!
I only copied the keys, menu and startup.
I am really really confused.
Digression: I switched to KDE, but after adding a wetget to the panel the desktop crashed. : )

I use fluxbox as my window manager. All of my other applications, besides the Zoom video conference application has window decorations, and they can be toggled on/off with the appropriate fluxbox key binding/command. Zoom does not. I has space above it for window decorations, and when I toggle them on/off this space disappears and comes back, but it never has the window decorations in it. How can I fix this? In a related question, https://unix.stackexchange.com/questions/502964/how-to-force-enable-window-decorations-on-application , @Lars Kotthoff says this is a problem related to the fact that "fluxbox doesn't have a compositor." What is a compositor? How can one be used to solve this problem? (I don't need anything to be transparent, or have a drop shadow, which seems to be the primary function of a compositor, from what I've learned trying this so far.) As requested, some versions: $ fluxbox --version Fluxbox 1.3.7-gentoo-r4 : (c) 2001-2015 Fluxbox Team $ uname -a Linux kirk 4.19.44-gentoo #5 SMP PREEMPT Thu Mar 19 12:31:30 EDT 2020 x86_64 Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux $ eselect profile show Current /etc/portage/make.profile symlink: default/linux/amd64/17.0/desktop

I recently needed to join a "Zoom" meeting from my Debian workstation on which I use Fluxbox for my window manager. The Zoom application starts in the upper left corner of my display with no titlebar or window decorations, so I cannot move it or otherwise manipulate it as I would with other windows. (I can perform some actions by right-clicking on Zoom in the toolbar, but options there are limited). The Zoom application doesn't provide any inline help nor did it come with a readme or man page, at least that I have been able to find. Is there a way to instruct Fluxbox to force window decorations on this window, either before or after starting the tool?

I'm running Debian 10 with fluxbox. I have an application where the window layer keeps changing to "Above dock", despite me checking "Remember..." "Layer". This layer change seems to happen randomly. How do I prevent this from happening? Pop ups created by the application launch with the "Normal" layer, so they are unclickable until I find them...certainly a very annoying issue. This *only* happens with this one application. Two more questions as asides: Do other window managers have this layer feature, or is it only fluxbox? What can control the window layer? Is it the window manager only, the application only, or both the window manager and application?

I am trying to install fluxbox in debian 8 with xdm. Problem is when i try to login with my username it shows X "Can't connect display: :0. But when I tried as root is shows fluxbox correctly. I tried lightdm but facing same problem. After installing debian Installed "sudo" as root then change my user as root. Then I instead xorg + fluxbox + xdm. Can anyone tell me what I did wrong? Why everything ok with root and not login with my username?

I'm having difficulty installing things like tmux app manager and fluxbox styles. In both cases i attempt to tar into their directories ~/.tmux/plugins/tpm & ~/.fluxbox/styles like this sudo tar -xjf trinity.tar.bz2 ~/.fluxbox/styles however I get an error stating that /styles is not a directory. Same with /tpm. They are indeed there, but they are not directories. I'm very confused. Where do I unpack my tar files?

I'm new to FreeBSD 9.1 and I wanted to install a desktop GUI environment. I first tried Gnome 2 since I am familiar with it. I appended the following lines to the /etc/rc.conf file: hald_enable="YES" dbus_enable="YES" gnome_enable="YES" gdm_enable="YES" When typing startx for the first time, my mouse, keyboard and everything else worked fine. However, after restarting my PC, the mouse didn't work anymore. Keyboard worked fine. I searched around for solutions and people said that adding the following line to the /etc/rc.conf file mouse_enable="YES" or moused_enable="YES" worked for them. However, this didn't work for me. I then tried switching to Fluxbox just to check if that works. I appended the following lines to the /etc/rc.conf file: hald_enable="YES" dbus_enable="YES" Again, when typing startx for the first time, my mouse and keyboard worked fine. However, after restarting my PC again the mouse worked just before starting X (in text mode). However, after starting X it doesn't work at all. Keyboard works fine. Does anyone have an idea what might be causing this kind of behavior and how to fix it?

In Manjaro Fluxbox there is no keyboard layout switch in the panel/toolbar tray. How do I add that?

I added this line to my ~/.fluxbox/keys file: Mod1 Shift :ToggleCmd {Exec setxkbmap fr} {Exec setxkbmap us} But it doesn't work.

I use Slax Linux as a Live Linux on a USB drive and I have a problem with multiple monitor configuration. My computer has two screens, this is the output of xrandr: Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 16384 x 16384 DVI-I-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1600x1200 60.00 1280x1024 75.02 60.02 1280x960 60.00 1152x864 75.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08 DVI-I-2 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) When Slax is started, it looks like this: (50% scale) Which is perfect, except, to get the mouse on the left screen, I have to move it out of the right of the right screen. So I want to switch the screens. First I tried: xrandr --output DVI-I-1 --auto --output DVI-I-2 --auto --left-of DVI-I-1 Now the mouse moves the right way, but the screens look like this: If I do instead: xrandr --output DVI-I-1 --off --output DVI-I-2 --off xrandr --output DVI-I-1 --auto --output DVI-I-2 --auto --left-of DVI-I-1 It seems to work at first, my screens looks like the first picture and the mouse moves okay. But when I click on the four squares to start a program, the screens look like this: How can I switch the screens and get FluxBox (version 1.3.5) to work normally? Note that I'll be using this installation on different computers, so I don't want any permanent configuration, just a few lines of code that I can run after startup when I'm using this particular computer. Editing of configuration files is allowed though, Slax uses a temporary file system and changes will be lost on reboot anyway.