Fluxbox for a newbie

[jessejazza]

I have looked at a few fluxbox clips on Youtube. I am thinking i would like to use it rather than MX-23.2_386 XFCE in future. I'm very much a DIY/customising sort of person.

I installed Fluxbox to my MX-23.2_386 XFCE installation to find that there is quite a few files to edit in the .fluxbox directory. As a newbie i thought i don't want to install the MX-23.2_386 Fluxbox version just yet as i need to use the computer each day [only got 1 PC].

So to shorten the learning curve [or need for tinkering] and still keep XFCE for everyday use - i thought i might be able to copy the .fluxbox files from the MX23.2_386 Fluxbox iso DVD and install them in my .fluxbox directory on the current XFCE installation. I found when the fluxbox DVD was running and i tried to access the .fluxbox directory it asked for root [i put in 'ROOT'] which it didn't like.

Was this a daft idea? What is the easiest way of learning Fluxbox whilst still needing to use the PC.

[FullScale4Me]

In 'MX Package Installer' select the 'Enabled Repos' tab.

Check 'Also Install "Recommended" Packages'.

Select and install the package 'mx-fluxbox'. (metapackage)

Logout.

At the top of the screen, there is a desktop switcher to go between the two. Only present when logged out.



Fluxbox uses its bits as well as some from several lightweight distros. Finding and using logout within Fluxbox looks slightly different than Xfce.

EDIT

Well, that didn't give a fully working Fluxbox installation. Trying to launch Settings Manager. From the white wrench/spanner nothing, From the Orange/Red Icon it gave an error;

Code: Select all

Failed to run custom-toolbox /etc/custom-toolbox/mxfb-settings.list. Error 2:

Running MX Tweaks 'Reset ALL mx-fluxbox settings' made no change even after logging out and reboot. Ditto for the other two reset options adjacent to it.

I picked the (metapackage) but I'm not sure if it was the right thing to do in this case. What else is needed?

Code: Select all

System:
  Kernel: 6.1.0-18-686-pae [6.1.76-1] arch: i686 bits: 32 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-686-pae root=UUID=<filter> ro quiet splash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.2_386 Libretto
    January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required>
    Chassis: Oracle Corporation type: 1 serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> BIOS: innotek GmbH
    v: VirtualBox date: 12/01/2006
CPU:
  Info: model: Intel Core i7-7700 bits: 32 type: MCP arch: Kaby Lake gen: core 7 built: 2018
    process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9 microcode: N/A
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 3598 min/max: N/A cores: 1: 3598 2: 3598 bogomips: 14390
  Flags: avx avx2 ht nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Unknown: Dependent on hypervisor status
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT Host state unknown
  Type: retbleed status: Vulnerable
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Unknown: Dependent on hypervisor status
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
    empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vmware
    unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx display-ID: :0 screens: 1
  Screen-1: 0 s-res: 800x600 s-dpi: 96 s-size: 211x158mm (8.31x6.22") s-diag: 264mm (10.38")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 800x600 hz: 60 size: N/A modes: max: 800x600
    min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0
    chip-ID: 8086:2415 class-ID: 0401
  API: ALSA v: k6.1.0-18-686-pae status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 bus-ID: 00:03.0
    chip-ID: 8086:100e class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
    modules: i2c_piix4 port: N/A bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives:
  Local Storage: total: 20 GiB used: 8.93 GiB (44.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 20 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1.0 scheme: MBR
Partition:
  ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 8.93 GiB (45.8%) fs: ext4 dev: /dev/sda1
    maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2074 libs: 1048 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 151 Uptime: 1m wakeups: 33 Memory: 3.88 GiB used: 654.6 MiB (16.5%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

FYI - this post in this thread was my effort to help the OP of the thread and learn something as a benefit.

If this ends up being outside the scope of the intent of the metapackage (above) this VBox VM isn't needed beyond helping the OP.

[siamhie]

Open MX Package Manager and at the bottom of the first tab (Popular Applications) is the category Window Managers. Install fluxbox from there.
To switch between desktops, log out and click on the icon at the top center of the screen to select the desktop.

[FullScale4Me]

Thanks, siamhie.

I see my personal solution in my Torrent folder - MX-23.2_fluxbox_386.iso.

Not sure if the package: mx-fluxbox-data-pi is supposed to show on a 32 bit X86 MX Linux instance.

Below is what MXPI sees for 'fluxbox' - highlighted is what I used as my 1st install attempt.

[siamhie]

Not sure if the package: mx-fluxbox-data-pi is supposed to show on a 32 bit X86 MX Linux instance.

@FullScale4Me Does fluxbox show up in your window manager section under popular applications?

[FullScale4Me]

Yes, I've found it and all is good.

It's still doesn't clear up why there is two metapackages.

[siamhie]

Yes, I've found it and all is good.

It's still doesn't clear up why there is two metapackages.

Maybe @Jerry3904 can clear that up for you.

[Jerry3904]

I'm on the road today, will check tonight

[Jerry3904]

Yes, I've found it and all is good.

It's still doesn't clear up why there is two metapackages.

The -pi package is used for Raspberry Pi installations, and maybe only older ones, not sure but @dolphin_oracle set it up and can explain better.

[dolphin_oracle]

that mx-fluxbox-data-pi package is an old one, and likely doesn't have the current default fluxbox configuration contained. however nothing in it is architecture dependent and so shows up on all architectures, not just the pi.