fluxbox-users — This list is for users of Fluxbox Window Manager.

[Fluxbox-users] [Spam]Re: sound volume control for use in fluxbox?

[Andrey G. G. <A.G...@in...>]

On Sun, 30 Nov 2025, Nable via Fluxbox-users wrote:
> I've also disabled the built-in window switcher in fluxbox (commented 
> corresponding lines in .fluxbox/keys) and replaced it with "alttab" 
> (https://sagb.github.io/alttab)
Thank you, but I always use ctrl-F1 ... ctrl-F4 for switching the virtual 
desktop, not a gui switcher.

Andrey

Re: [Fluxbox-users] sound volume control for use in fluxbox?

[Andrey G. G. <A.G...@in...>]

Thank you,

On Sun, 30 Nov 2025, Nable via Fluxbox-users wrote:
> I'm using "volumeicon" and "cbatticon" for this exact purpose (yep, I'm still using bare fluxbox on my main workstation).
Another person on this mailing list suggested me to use pnmixer for volume 
control. It also sits in the tray, and does exactly what's needed. So, I 
added it to my ~/.fluxbox/startup.

I'll try cbatticon.

> Btw, the third icon in my tray comes from "fbxkb", it indicates keyboard layout and allows to switch one on click. I've also disabled the built-in window switcher in fluxbox (commented corresponding lines in .fluxbox/keys) and replaced it with "alttab" (https://sagb.github.io/alttab)
As you may have guessed, I'm russian, and I need to switch my keyboard 
between the english mode and the russian one. But I do it in a more 
trivial way: my .xinitrc contains

setxkbmap -layout us,ru -option grp:caps_toggle,grp_led:caps

So, I press CapsLock to switch to russian; the CapsLog led is on when the 
keyboard is in the russian mode.

>> The only Lumina utility I sometimes used is for taking screenshots. What X program would you recommend for this purpose?
> I'm using scrot + maim, here's a part of my .fluxbox/keys config:
> # PrintScreen
> None Print :ExecCommand scrot
> Control Print :ExecCommand maim -s | xclip -selection clipboard -t image/png
> Shift Print :ExecCommand maim -i (xdotool getactivewindow) | xclip -selection clipboard -t image/png
I found screengrab for taking screenshots. I don't thing I need a special 
key binding for it, because I do it rarely. But if I'll need it, I'll do 
something sililar in my .fluxbox/keys.

Thank you once more,
Andrey

Re: [Fluxbox-users] sound volume control for use in fluxbox?

[Nable <nab...@go...>]

Hi Andrey,
> First of all, I need sound volume control (or a mixer, but a simple volume control would be sufficient). Ideally, this program should sit in the toolbar at the bottom of the screen; when I click it, it should show a slider to set the volume by my mouse.
>
> Second, I need a small gui program to display my battery status. Well, I can say
> acpi
> at the command line, but it would be nice to have something sitting in the toolbar and showing the battery status all the time.
>
> These two things existed ti Lumina in its panel. Now, in the bare fluxbox, I need some separate X programs for these purposes. What programs do you use?
I'm using "volumeicon" and "cbatticon" for this exact purpose (yep, I'm still using bare fluxbox on my main workstation).

Btw, the third icon in my tray comes from "fbxkb", it indicates keyboard layout and allows to switch one on click. I've also disabled the built-in window switcher in fluxbox (commented corresponding lines in .fluxbox/keys) and replaced it with "alttab" (https://sagb.github.io/alttab)

> The only Lumina utility I sometimes used is for taking screenshots. What X program would you recommend for this purpose?
I'm using scrot + maim, here's a part of my .fluxbox/keys config:
# PrintScreen
None Print :ExecCommand scrot
Control Print :ExecCommand maim -s | xclip -selection clipboard -t image/png
Shift Print :ExecCommand maim -i (xdotool getactivewindow) | xclip -selection clipboard -t image/png

I didn't have to compile anything, all these tools are available in Debian packages with the same names. I guess they should be available in your distro too.

Cheers, Nable

Re: [Fluxbox-users] sound volume control for use in fluxbox?

[Andrey G. G. <A.G...@in...>]

Dear Peter,

On Sat, 29 Nov 2025, Peter P. wrote:
> For monitoring volume and battery status I am using conky (see attached
> screenshot) and the respective lines in ~/.conkyrc are
> 	${if_mixer_mute}${color red}Muted: ${mixerbar}${color black}${else}volume: ${mixerbar}${endif}
> 	${battery} $alignr rem: ${battery_time}
Hm. conky seems too powerful and complex. But maybe it's OK.

> Taking screenshots is done with one of the many standalone programs
> available, in my case it is screengrab, which can be launched from
> fluxboxes menu or as a keyboard shortcut.
Yes. screengrab seems to be the right choice.

Thank you,
Andrey

Re: [Fluxbox-users] sound volume control for use in fluxbox?

[Jörg S. <ma...@js...>]

Am Sat, 29 Nov 2025 18:09:44 +0700 (+07)
schrieb "Andrey G. Grozin via Fluxbox-users"
<flu...@li...>:

> Hello *,
> 
> For years I used Lumina desktop environment (which uses fluxbox as
> its window manager). Now the distro I'm using (Gentoo) is about to
> remove Qt5, and hence Lumina (it has not been ported to Qt6). So, I
> had to decide what to use as my desktop.
> 
> I decided to use bare fluxbox. It provides > 90% of what I need for
> my everyday work. But I need some extra things, and I ask for your
> advice what X programs to install.
> 
> First of all, I need sound volume control (or a mixer, but a simple
> volume control would be sufficient). Ideally, this program should sit
> in the toolbar at the bottom of the screen; when I click it, it
> should show a slider to set the volume by my mouse.
> 
> Second, I need a small gui program to display my battery status.
> Well, I can say
> acpi
> at the command line, but it would be nice to have something sitting
> in the toolbar and showing the battery status all the time.
> 
> These two things existed ti Lumina in its panel. Now, in the bare
> fluxbox, I need some separate X programs for these purposes. What
> programs do you use?
> 
> The only Lumina utility I sometimes used is for taking screenshots.
> What X program would you recommend for this purpose?
> 
> Many thanks in advance,
> Andrey

Well, the panel isn`t Fluxbox strongest  part. I replaced it
with  Lemonbar. The Xfce4 panel would have everything you asked for.
Easy to replace Fluxbox panel with that. 
For volume control I use this line in the keys file
Mod4 l ;ToggleCmd  {exec pavucontrol} {exec killall pavucontrol}

I don't use battery control, but most panels have a build in function
for that, and as I said, it's easy to repllace Fluxbox panel with
another one

HTH
Joerg

Re: [Fluxbox-users] sound volume control for use in fluxbox?

[Peter P. <pet...@fa...>]

Hi Andrey,

do you have media/volume buttons on your keyboard? I map them to amixer
commands in ~/.fluxbox/keys like this:
	XF86AudioLowerVolume :ExecCommand amixer set Master 3dB- unmute
	XF86AudioRaiseVolume :ExecCommand amixer set Master 3dB+ unmute
	XF86AudioMute :ExecCommand amixer set Master toggle

For monitoring volume and battery status I am using conky (see attached
screenshot) and the respective lines in ~/.conkyrc are
	${if_mixer_mute}${color red}Muted: ${mixerbar}${color black}${else}volume: ${mixerbar}${endif}
	${battery} $alignr rem: ${battery_time}

Taking screenshots is done with one of the many standalone programs
available, in my case it is screengrab, which can be launched from
fluxboxes menu or as a keyboard shortcut.

cheers, P

* Andrey G. Grozin via Fluxbox-users <flu...@li...> [2025-11-29 12:25]:
> Hello *,
> 
> For years I used Lumina desktop environment (which uses fluxbox as its
> window manager). Now the distro I'm using (Gentoo) is about to remove Qt5,
> and hence Lumina (it has not been ported to Qt6). So, I had to decide what
> to use as my desktop.
> 
> I decided to use bare fluxbox. It provides > 90% of what I need for my
> everyday work. But I need some extra things, and I ask for your advice what
> X programs to install.
> 
> First of all, I need sound volume control (or a mixer, but a simple volume
> control would be sufficient). Ideally, this program should sit in the
> toolbar at the bottom of the screen; when I click it, it should show a
> slider to set the volume by my mouse.
> 
> Second, I need a small gui program to display my battery status. Well, I can
> say
> acpi
> at the command line, but it would be nice to have something sitting in the
> toolbar and showing the battery status all the time.
> 
> These two things existed ti Lumina in its panel. Now, in the bare fluxbox, I
> need some separate X programs for these purposes. What programs do you use?
> 
> The only Lumina utility I sometimes used is for taking screenshots. What X
> program would you recommend for this purpose?
> 
> Many thanks in advance,
> Andrey
> 
> 
> _______________________________________________
> Fluxbox-users mailing list
> Flu...@li...
> https://lists.sourceforge.net/lists/listinfo/fluxbox-users

[Fluxbox-users] sound volume control for use in fluxbox?

[Andrey G. G. <A.G...@in...>]

Hello *,

For years I used Lumina desktop environment (which uses fluxbox as its 
window manager). Now the distro I'm using (Gentoo) is about to remove Qt5, 
and hence Lumina (it has not been ported to Qt6). So, I had to decide what 
to use as my desktop.

I decided to use bare fluxbox. It provides > 90% of what I need for my 
everyday work. But I need some extra things, and I ask for your advice 
what X programs to install.

First of all, I need sound volume control (or a mixer, but a simple volume 
control would be sufficient). Ideally, this program should sit in the 
toolbar at the bottom of the screen; when I click it, it should show a 
slider to set the volume by my mouse.

Second, I need a small gui program to display my battery status. Well, I 
can say
acpi
at the command line, but it would be nice to have something sitting in the 
toolbar and showing the battery status all the time.

These two things existed ti Lumina in its panel. Now, in the bare fluxbox, 
I need some separate X programs for these purposes. What programs do you 
use?

The only Lumina utility I sometimes used is for taking screenshots. What X 
program would you recommend for this purpose?

Many thanks in advance,
Andrey

[Fluxbox-users] ToggleDecor, Firefox, Chrome, Zoom, and a lack of amusement

[Swift G. <sw...@ir...>]

I recently read the Bug threads on Firefox/Mozilla concerning the change 
they made to drop window decorations from Firefox. They basically hand 
wave off the terrible decision and implementation with "It's been this way 
on MacOS and Windows forever". Then they trash Fluxbox and act like it's 
the fault of the Window Manager somehow, when in fact, they are simply 
abusing privileged they probably should never have had (getting rid of my 
Decor). If you want to read the thread, I can dig it up. In fact, the last 
entry suggests that Mozilla won't support or change anything unless it's 
for GNOME.

I have had reasonable luck with using "ToggleDecor" bound to a keystroke 
but lately some applications still won't show the Fluxbox titlebar even 
after using this technique.

Can I just throw a suggestion for a new configuration directive/option to 
absolutely disable this functionality/feature from any application? Ie...

AlwaysForceDecor: True

Or something like that? I really really hate this behavior by these 
applications that seem to consider themselves "above" minding my window 
manager. Maybe this is a good idea in some situations, but I can't think 
of what those would be. Even if it resulted in ever "Save As" sub-dialog 
having it's own decor, I'd still find that a lot better than the current 
behavior of "We took your toolbar. Haha. 'Upgrade' to windows, bruh".

Thanks so much for maintaining Fluxbox. I've been a user for ... uhm, 
about 21 years? I switched from Blackbox.

Thanks,
   Swift

Re: [Fluxbox-users] How to run 'tail' command from menu script

[D.T. <ohn...@po...>]

I just noticed that the other user recommended uxterm, not urxvt.

urxvt is notoriously tricky with -e, iirc I always used 

urxvt -hold -e 'sh -c "tail /some/text/file"'

"read x" is literally the command you use instead of "$SHELL"
Effect: <Enter> closes the window

On Mon, 2024-02-12 at 16:49 -0700, Duke Normandin wrote:
> On Mon, 12 Feb 2024 22:51:10 +0000
> "D.T." <ohn...@po...> wrote:
> 
> > 2 additions wrt the trailing ;$SHELL:
> > 
> > - You can replace it with ;read x
> > - Remove it and invoke urxvt with the -hold option to keep the
> > terminal open
> 
> urxvt -hold -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
> -fullscreen -bg black -fg green -e "tail -20
> ~/notes/leftoff.txt"
> 
>  urxvt: unable to exec child.
> 
> I don't get what you mean by `read x'? x is the filename?

Re: [Fluxbox-users] How to run 'tail' command from menu script

[Duke N. <sid...@gm...>]

On Mon, 12 Feb 2024 22:51:10 +0000
"D.T." <ohn...@po...> wrote:

> 2 additions wrt the trailing ;$SHELL:
> 
> - You can replace it with ;read x
> - Remove it and invoke urxvt with the -hold option to keep the
> terminal open

urxvt -hold -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
-fullscreen -bg black -fg green -e "tail -20
~/notes/leftoff.txt"

 urxvt: unable to exec child.

I don't get what you mean by `read x'? x is the filename?
-- 
Duke
** Bottom-posting, text-only is the netiquette way! **

Re: [Fluxbox-users] How to run 'tail' command from menu script

[D.T. <ohn...@po...>]

2 additions wrt the trailing ;$SHELL:

- You can replace it with ;read x
- Remove it and invoke urxvt with the -hold option to keep the terminal
open


On Mon, 2024-02-12 at 13:38 -0700, Duke Normandin wrote:
> On Mon, 12 Feb 2024 15:04:46 -0500
> Andrew Nevai <an...@gm...> wrote:
> 
> > # The following doesn't work! I've tried quite a few permutations
> > # & combinations thereof, but I haven't lucked-in on the correct
> > # one.
> > #
> > # urxvt -e tail ~/notes/<filename.txt>
> > #
> > # Any help would be appreciated! TIA ...
> > # --
> > # Duke
> > 
> [snip]
> 
> > Maybe:
> > 
> > {uxterm -e "tail ~/notes/<filename.txt>; $SHELL"}
> 
> That did it! Thx a bunch ..

Re: [Fluxbox-users] How to run 'tail' command from menu script

[Duke N. <sid...@gm...>]

On Mon, 12 Feb 2024 15:04:46 -0500
Andrew Nevai <an...@gm...> wrote:

> # The following doesn't work! I've tried quite a few permutations
> # & combinations thereof, but I haven't lucked-in on the correct
> # one.
> #
> # urxvt -e tail ~/notes/<filename.txt>
> #
> # Any help would be appreciated! TIA ...
> # --
> # Duke
> 
[snip]

> Maybe:
> 
> {uxterm -e "tail ~/notes/<filename.txt>; $SHELL"}

That did it! Thx a bunch ..
-- 
Duke
** Bottom-posting, text-only is the netiquette way! **

Re: [Fluxbox-users] How to run 'tail' command from menu script

[Andrew N. <an...@gm...>]

# The following doesn't work! I've tried quite a few permutations &
# combinations thereof, but I haven't lucked-in on the correct one.
#
# urxvt -e tail ~/notes/<filename.txt>
#
# Any help would be appreciated! TIA ...
# --
# Duke
# ** Bottom-posting, text-only is the netiquette way! **
#
#
# _______________________________________________
# Fluxbox-users mailing list
# Flu...@li...
# https://lists.sourceforge.net/lists/listinfo/fluxbox-users

Maybe:

{uxterm -e "tail ~/notes/<filename.txt>; $SHELL"}

[Fluxbox-users] How to run 'tail' command from menu script

[Duke N. <sid...@gm...>]

The following doesn't work! I've tried quite a few permutations &
combinations thereof, but I haven't lucked-in on the correct one.

urxvt -e tail ~/notes/<filename.txt>

Any help would be appreciated! TIA ...
-- 
Duke
** Bottom-posting, text-only is the netiquette way! **

Re: [Fluxbox-users] Webpages of fluxbox.org

[riveravaldez <riv...@gm...>]

On 11/1/23, Peter <pet...@gm...> wrote:
> Hi,
>
> I have just upgraded to Debian 12, and found that Lyx won't run.  In fact,
> it freezes the system and the only recourse is reboot.  Its definitely
> Fluxbox, because I installed MATE and Lyx seems to run perfectly in it.
> Have there been any significant changes to Fluxbox in Debian 12?  And where
> should I communicate this to? I managed to get a long QT Debug copied, but
> not being a developer it doesn't mean anything to me but I can send it on to
> anyone who would find it useful.
>
> Peter

Hi, Peter, just another user here.

Maybe you can try first reporting to Fluxbox Debian's package
maintainer, check the right column ("Links for fluxbox") there:

https://packages.debian.org/bookworm/fluxbox

Hope it helps.

Best of luck and kind regards!

Re: [Fluxbox-users] Webpages of fluxbox.org

[Peter<pet...@gm...>]

Hi,

I have just upgraded to Debian 12, and found that Lyx won't run.  In fact, it freezes the system and the only recourse is reboot.  Its definitely Fluxbox, because I installed MATE and Lyx seems to run perfectly in it.  Have there been any significant changes to Fluxbox in Debian 12?  And where should I communicate this to? I managed to get a long QT Debug copied, but not being a developer it doesn't mean anything to me but I can send it on to anyone who would find it useful.

Peter

Re: [Fluxbox-users] Fluxbox disimprovements on dual monitors

[Matt B. <mb...@gm...>]

Hi Johnatan,

One possible workaround would be using a keyboard shortcut to move the
maximized window to the other monitor.  Something like the following:

## ~/.fluxbox/keys
# Windows+; -> move current window's to next monitor
Mod4 semicolon :SendToNextHead

Out of curiosity, are you dragging the window by the top window handle /
titlebar, or using an alt+left-mouse drag?  It sounds like you're saying
when your mouse hits the edge between the two monitors the virtual desktop
starts switching (on one monitor or both of them?)

It's possible that there's some difference in your old vs new
configurations, either in how Fluxbox was packaged/built, or how the X
server is configured.  ie xinerama etc, it's possible to have your 2
monitors set up as a single X virtual screen, or two separate screens... or
the relative positions of the monitors might have changed when upgrading.
Any of those might affect the behavior of the bug you're describing.  The
output of `xdpyinfo` might give some clue, but you probably don't have the
old setup available to compare.

Matt

On Fri, Jun 30, 2023 at 3:46 AM Johnatan Hallman via Fluxbox-users <
flu...@li...> wrote:

> Hello,
>
> It took me more than +1 year after Debian 9 being EOLed to finally switch
> to Debian 11 AntiX due to so many custom apps and so many issues.
>
> Regardless the security patches in the new system, when one upgrades
> he/she expects to get a "better" product not something utterly crap with
> bloatware features nobody asked for. Anyway if I wouldn't upgrade none of
> the latest browsers firefox/chrome would support the OS soon.
>
> My new setup is:
>
> Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox
>
> 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD
> Graphics 520] (rev 07)
>
> xorg-server 2:1.20.11-1.0nosystemd3 (https://www.debian.org/support)
> Current version of pixman: 0.40.0
>
>
> There are some extremely annoying issues compared to running Fluxbox on
> the exact same laptop but with the old system:
>
> With a 2 monitor setup moving maximized windows make it switch like crazy
> in between the virtual desktops, sometimes it ends up positioning the
> window outside the area then you have to kill the process and reopen it.
> This was not happening at all on the old system.
>
> Also this might not be related to Fluxbox but moving video players like
> VLC between the 2 screens makes the running video sluggish, this was also
> not present with the old Debian and old X.
>
>
>
> I wonder if Flux is still being developed... it would be nice to have a
> proper taskbar per monitor option. It can do taskbar on specific heads or
> on ALL but when you select ALL it just makes a huge taskbar and put the
> apps in order when you started. Having 2 taskbars on the 2 monitors would
> be better with each only displaying the corresponding apps.
>
>
>
>
>
>
> _______________________________________________
> Fluxbox-users mailing list
> Flu...@li...
> https://lists.sourceforge.net/lists/listinfo/fluxbox-users
>

[Fluxbox-users] Fluxbox disimprovements on dual monitors

[Johnatan H. <joh...@pr...>]

Hello,

It took me more than +1 year after Debian 9 being EOLed to finally switch to Debian 11 AntiX due to so many custom apps and so many issues.

Regardless the security patches in the new system, when one upgrades he/she expects to get a "better" product not something utterly crap with bloatware features nobody asked for. Anyway if I wouldn't upgrade none of the latest browsers firefox/chrome would support the OS soon.

My new setup is:

Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox 

00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)

xorg-server 2:1.20.11-1.0nosystemd3 (https://www.debian.org/support) 
Current version of pixman: 0.40.0


There are some extremely annoying issues compared to running Fluxbox on the exact same laptop but with the old system:

With a 2 monitor setup moving maximized windows make it switch like crazy in between the virtual desktops, sometimes it ends up positioning the window outside the area then you have to kill the process and reopen it. This was not happening at all on the old system.

Also this might not be related to Fluxbox but moving video players like VLC between the 2 screens makes the running video sluggish, this was also not present with the old Debian and old X.



I wonder if Flux is still being developed... it would be nice to have a proper taskbar per monitor option. It can do taskbar on specific heads or on ALL but when you select ALL it just makes a huge taskbar and put the apps in order when you started. Having 2 taskbars on the 2 monitors would be better with each only displaying the corresponding apps. 

Re: [Fluxbox-users] keys setting overridden by fluxbox-update_configs

[klu <kl...@gm...>]

The work-around I found out so far, is to "no-op" fluxbox-update_configs:

  ln -sf /usr/bin/true /usr/loca/bin/fluxbox-update_configs

On Sun, Nov 27, 2022 at 10:49 AM klu <kl...@gm...> wrote:
>
> My `~/.fluxbox/keys` file contains the following lines:
>
> [...]
> OnTitlebar Double Mouse1 :Maximize
> [...]
>
>
> However, it seems that fluxbox on startup and on exit, will prepend a
> few lines of configs, including below lines, to the beginning of my
> keys file:
>
> !mouse actions added by fluxbox-update_configs
> OnTitlebar Double Mouse1 :Shade
>
>
> This essentially overwrite my setting. I have no idea what triggered
> fluxbox-update_configs. And there's no mention of this tool in the
> manpage.
>
> Is there a way I can disable auto config saving?
>
>
> ---
>
> Fluxbox version: 1.3.7
> GIT Revision: unknown
> Compiled: Apr  7 2022 11:27:03
> Compiler: CLANG
> Compiler version: FreeBSD Clang 11.0.1
> (gi...@gi...:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
>
> Defaults:
> menu: /usr/local/share/fluxbox/menu
> windowmenu: /usr/local/share/fluxbox/windowmenu
> style: /usr/local/share/fluxbox/styles/bloe
> keys: /usr/local/share/fluxbox/keys
> init: /usr/local/share/fluxbox/init
> nls: /usr/local/share/fluxbox/nls
>
> Compiled options (- => disabled):
> BIDI
> -DEBUG
> EWMH
> -IMLIB2
> NLS
> REMEMBER
> RENDER
> SHAPE
> SLIT
> SYSTEMTRAY
> TOOLBAR
> RANDR
> XFT
> XINERAMA
> XMB
> XPM

[Fluxbox-users] keys setting overridden by fluxbox-update_configs

[klu <kl...@gm...>]

My `~/.fluxbox/keys` file contains the following lines:

[...]
OnTitlebar Double Mouse1 :Maximize
[...]


However, it seems that fluxbox on startup and on exit, will prepend a
few lines of configs, including below lines, to the beginning of my
keys file:

!mouse actions added by fluxbox-update_configs
OnTitlebar Double Mouse1 :Shade


This essentially overwrite my setting. I have no idea what triggered
fluxbox-update_configs. And there's no mention of this tool in the
manpage.

Is there a way I can disable auto config saving?


---

Fluxbox version: 1.3.7
GIT Revision: unknown
Compiled: Apr  7 2022 11:27:03
Compiler: CLANG
Compiler version: FreeBSD Clang 11.0.1
(gi...@gi...:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)

Defaults:
menu: /usr/local/share/fluxbox/menu
windowmenu: /usr/local/share/fluxbox/windowmenu
style: /usr/local/share/fluxbox/styles/bloe
keys: /usr/local/share/fluxbox/keys
init: /usr/local/share/fluxbox/init
nls: /usr/local/share/fluxbox/nls

Compiled options (- => disabled):
BIDI
-DEBUG
EWMH
-IMLIB2
NLS
REMEMBER
RENDER
SHAPE
SLIT
SYSTEMTRAY
TOOLBAR
RANDR
XFT
XINERAMA
XMB
XPM

[Fluxbox-users] building without toolbar, slit, neither tray (with lxqt and picom)

[Javier <je-vv@e.email>]

Hello !

Please CC me, for some weird reason my confirmation mail when subscribing to the ML doesn't work.

Hey, I've been using fluxbox-wm [1] from AUR (Artix/Arch), which is no more than fluxbox built with:

>     --disable-slit \
>     --disable-systray \
>     --disable-toolbar

In addition to the other configuration options stock fluxbox Arch sets...  I have to build fluxbox that way, since plain fluxbox has several issues running with lxqt and picom.

To start with, even while calling plain fluxbox with ** -no-toolbar -no-slit **, it so happens fluxbox starts effectively with no toolbar, but with an empty space as if it has a toolbar.  And one can sort of work around that by restarting fluxbox by calling the fluxbox ** Restart ** command, however it's like if fluxbox was setting a fullscreen wallpaper on the space excluding the lxqt panel, which is really weird to start with, since I set the overlay with background ** unset ** or ** none **.

Those issues are only present if not building fluxbox with ** --disable-slit --disable-systray --disable-toolbar **.  Whereas if building it with them, none of those issues show up.

However, I'm experiencing that after a while of having the screen both locked down, and auto turned off or turned off, when turning the screen back on, and unlocking, although fluxbox is still alive, the windows decorations are lost, so windows have already lost their titlebar for example.  The only way to recover them is to call the fluxbox ** Restart ** command.

So I tried moving from current commit SHA on the fluxbox-wm AUR package (e2cbd179ecb2ef2d76e0ad1fde84b44325305799) to the same commit SHA the Arch fluxbox package is using (1d19662c8975e881b4fa6465a8305be3ea5282ee).  Notice the commit stock Arch is using is just 6 commits behind head of master, while the fluxbox-wm from AUR (again same package, just to build without slit, toolbar and tray), is a bunch of commits behind.  When moving to the newer stock Arch fluxbox commit, the following linking error while building shows up:

> g++ -DHAVE_CONFIG_H -I.  -include ./config.h   -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS  -MT src/defaults.o -MD -MP -MF $depbase.Tpo -c -o src/defaults.o src/defaults.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> g++  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS   -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -o fluxbox src/fluxbox-AlphaMenu.o src/fluxbox-ArrowButton.o src/fluxbox-AttentionNoticeHandler.o src/fluxbox-CascadePlacement.o src/fluxbox-ClientMenu.o src/fluxbox-ClientPattern.o src/fluxbox-ColSmartPlacement.o src/fluxbox-CommandDialog.o src/fluxbox-ConfigMenu.o src/fluxbox-CurrentWindowCmd.o src/fluxbox-FbAtoms.o src/fluxbox-FbCommands.o src/fluxbox-FbMenu.o src/fluxbox-FbMenuParser.o src/fluxbox-FbRootWindow.o src/fluxbox-FbWinFrame.o src/fluxbox-FbWinFrameTheme.o src/fluxbox-FocusControl.o src/fluxbox-FocusableList.o src/fluxbox-HeadArea.o src/fluxbox-IconButton.o src/fluxbox-IconbarTheme.o src/fluxbox-Keys.o src/fluxbox-LayerMenu.o src/fluxbox-MenuCreator.o src/fluxbox-MinOverlapPlacement.o src/fluxbox-OSDWindow.o src/fluxbox-Resources.o src/fluxbox-RootCmdMenuItem.o src/fluxbox-RootTheme.o src/fluxbox-RowSmartPlacement.o src/fluxbox-Screen.o src/fluxbox-ScreenPlacement.o src/fluxbox-ScreenResource.o src/fluxbox-SendToMenu.o src/fluxbox-ShortcutManager.o src/fluxbox-StyleMenuItem.o src/fluxbox-TextDialog.o src/fluxbox-TooltipWindow.o src/fluxbox-UnderMousePlacement.o src/fluxbox-WinButton.o src/fluxbox-WinButtonTheme.o src/fluxbox-WinClient.o src/fluxbox-Window.o src/fluxbox-WindowCmd.o src/fluxbox-WindowState.o src/fluxbox-Workspace.o src/fluxbox-WorkspaceCmd.o src/fluxbox-WorkspaceMenu.o src/fluxbox-Xutil.o src/fluxbox-fluxbox.o src/fluxbox-main.o src/fluxbox-cli_cfiles.o src/fluxbox-cli_options.o src/fluxbox-cli_info.o src/fluxbox-Ewmh.o src/fluxbox-Remember.o   libFbTk.a src/defaults.o -lfontconfig -lfreetype  -lfreetype  -lfribidi  -lImlib2  -lXrandr  -lXext  -lXft  -lXinerama  -lXpm -lX11  -lXrender -lX11  -lX11   -lrt  -lm
> /usr/bin/ld: src/fluxbox-IconButton.o: warning: relocation against `_ZN11IconbarTool21s_iconifiedDecorationB5cxx11E' in read-only section `.text'
> /usr/bin/ld: src/fluxbox-IconButton.o: in function `IconButton::setupWindow()':
> IconButton.cc:(.text+0x132b): undefined reference to `IconbarTool::s_iconifiedDecoration[abi:cxx11]'
> /usr/bin/ld: IconButton.cc:(.text+0x133f): undefined reference to `IconbarTool::s_iconifiedDecoration[abi:cxx11]'
> /usr/bin/ld: IconButton.cc:(.text+0x1350): undefined reference to `IconbarTool::s_iconifiedDecoration[abi:cxx11]'
> /usr/bin/ld: warning: creating DT_TEXTREL in a PIE
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:2165: fluxbox] Error 1
> make[2]: Leaving directory '/home/general/.pkgs/src/others/fluxbox-wm/src/fluxbox'
> make[1]: *** [Makefile:4901: all-recursive] Error 1
> make[1]: Leaving directory '/home/general/.pkgs/src/others/fluxbox-wm/src/fluxbox'
> make: *** [Makefile:1760: all] Error 2
> ==> ERROR: A failure occurred in build().
>     Aborting...
> 

I then tried building with the head of master commit (9d8202f32338a3f08d3fa39057dc5eec5d97be4e), to see if that was somehow fixed, and I got exactly the same error.  So it seems building with ** --disable-slit --disable-systray --disable-toolbar ** is not working anymore after commit e2cbd179ecb2ef2d76e0ad1fde84b44325305799.  Please notice if I build the same fluxbox commit, but without those options, it builds just fine, but that's not what I'm looking for.  The fluxbox-wm AUR maintainer mentioned e2cbd179ecb2ef2d76e0ad1fde84b44325305799 is sort of the last commit which builds fine with those options [3]...

Has support to build recent fluxbox commits with ** --disable-slit --disable-systray --disable-toolbar ** being dropped?  It seems it's the only way I can get it working with lxqt and picom.

Please let me know, and remember to CC me, :)

Thanks !

-- 
Javier


[1]  https://aur.archlinux.org/packages/fluxbox-wm
[2]  https://archlinux.org/packages/extra/x86_64/fluxbox
[3]  https://aur.archlinux.org/packages/fluxbox-wm#comment-885519

Re: [Fluxbox-users] Windows created have weird dimensions on Debian with Fluxbox

[Peter P. <pet...@fa...>]

Matt,

* Matt Banack <mb...@gm...> [2022-06-14 23:12]:
> Hi Peter,
> 
> You can look into ~/.fluxbox/apps (`man fluxbox-apps`) to set default
> dimensions for a certain window.  Matching is done with xprop properties,
> ie name= and class=... run `xprop` from a terminal and point it at the
> window in question to confirm the prop values.  You'll want something like:
> 
> [app] (name=scide)
>   [Dimensions] {400 400}
>   [Position] (CENTER) {0% 0%}
> [end]

Thank you, If I tell the odd window to remeber its dimensions I get the
following entry
	[app] (name=SuperCollider) (class=SuperCollider)
  	  [Dimensions]  {0% 2%}
	[end]
created.
 
> It's possible scide is doing something odd to try to change its own window
> dimensions after it opens the window, in which case the apps solution may
> or may not work.  Best of luck :)

If I change this in this textfile to 
	[app] (name=SuperCollider) (class=SuperCollider)
  	  [Dimensions]  {100% 100%}
	[end]

the window is created the same (above, wrong) dimensions. What is important to
know that the problematic window is a subwindow of scide, namely "Show node tree"
and not the main scide IDE window.

What is puzzlig is that this is not a problem on openbox.

Thanks for your help Matt!
Peter

Re: [Fluxbox-users] Windows created have weird dimensions on Debian with Fluxbox

[Matt B. <mb...@gm...>]

Hi Peter,

You can look into ~/.fluxbox/apps (`man fluxbox-apps`) to set default
dimensions for a certain window.  Matching is done with xprop properties,
ie name= and class=... run `xprop` from a terminal and point it at the
window in question to confirm the prop values.  You'll want something like:

[app] (name=scide)
  [Dimensions] {400 400}
  [Position] (CENTER) {0% 0%}
[end]

It's possible scide is doing something odd to try to change its own window
dimensions after it opens the window, in which case the apps solution may
or may not work.  Best of luck :)

Matt

On Sat, Jun 11, 2022 at 12:36 AM Peter P. <pet...@fa...> wrote:

> Hi list,
>
> Windows created in the program "Supercollider" (Debian package
> supercollider, binary scide) are displayed only with their title bar, and
> this
> bar has very large horizontal dimensions, reaching beyond my desktop
> borders. The wmctl utility reports the dimensions 65535x65535 for this
> window:
>  $ wmctl -l -G
>  [...]
>  0x0100001d  0 60   100  65535 65535 zoot localhost Node Tree
> This happens to other windows of the same program too.
>
> I can only get to see this window's contents by maximizing it,
> which does not allow me to work at this programs main window at the same
> time.
>
> This does not happen with, say, openbox. There the window has the
> correct geometry of 400x400 there.
>  $ wmctl -l -G
>  [...]
>  0x00a00025  0 5    40   400  400  zoot localhost Node Tree
>
> I can resize the weird window in fluxbox with the same wmctl command
>  $ wmctrl -r localhost -e 0,0,0,400,400
> which makes it display normally. However, if I close and open it again
> it is back at 65535x65535.
>
> I'd be happy to learn about all possible sources for this problem,
> thank you so much!
> Peter
>
>
> _______________________________________________
> Fluxbox-users mailing list
> Flu...@li...
> https://lists.sourceforge.net/lists/listinfo/fluxbox-users
>

[Fluxbox-users] Windows created have weird dimensions on Debian with Fluxbox

[Peter P. <pet...@fa...>]

Hi list,

Windows created in the program "Supercollider" (Debian package
supercollider, binary scide) are displayed only with their title bar, and this
bar has very large horizontal dimensions, reaching beyond my desktop
borders. The wmctl utility reports the dimensions 65535x65535 for this
window:
 $ wmctl -l -G 
 [...]
 0x0100001d  0 60   100  65535 65535 zoot localhost Node Tree
This happens to other windows of the same program too.

I can only get to see this window's contents by maximizing it,
which does not allow me to work at this programs main window at the same time. 

This does not happen with, say, openbox. There the window has the
correct geometry of 400x400 there.
 $ wmctl -l -G 
 [...]
 0x00a00025  0 5    40   400  400  zoot localhost Node Tree

I can resize the weird window in fluxbox with the same wmctl command
 $ wmctrl -r localhost -e 0,0,0,400,400
which makes it display normally. However, if I close and open it again
it is back at 65535x65535.

I'd be happy to learn about all possible sources for this problem,
thank you so much!
Peter

[Fluxbox-users] losing window focus when switching desktops

[Peter P. <pet...@fa...>]

Hi list,

when I am using FB on my laptop with an external display mirroring the
internal one, and with the external display being slighly smaller,
window focus is lost when switching desktop.

Steps to reproduce:
Laptop display at 1366x768 
HDMI display at 1280x720
create a window (focussed)
switch to another desktop
switch back
window no longer focused.

or:
[...]
create two windows (one focussed)
switch to another desktop
switch back
the other one is focussed now.

This does not appear when the two display have identical display
resolution.

Is this a FB problem or about X?

Thank you for all hints!
Peter