Page 1 of 1
MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 2:46 pm
by dolphin_oracle
Feedback for RC1 fluxbox isos go here.
https://mxlinux.org/blog/mx-21-release- ... -purposes/
Be sure to include proper system data, including the output of quick-system-info.
If posting nvidia-installer (ddm-mx) issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 6:24 pm
by Sigi
Repost from closed Beta-2: Please add LibreWolf & Telegram Desktop to Popular Applications.
May be, please think about to set default browser to LibreWolf instead of Firefox for security reasons and FOSS. THX!
https://www.youtube.com/watch?v=BMXrfmRSprM
https://www.youtube.com/watch?v=D_FqyhD1NlE
https://www.youtube.com/watch?v=8LVMkC82jpk&t=842s
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 6:33 pm
by dolphin_oracle
librewolf as default: not happening. telegram-desktop added to pop. apps... sounds good thanks for the suggestion.
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 6:39 pm
by Sigi
Just detected: MX 21-RC1 needs at least 10 GiB space for installation (VirtualBox with EFI enabled).
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 6:42 pm
by SwampRabbit
@dolphin_oracle we'll need to update Telegram first (the Bullseye version has issues) or get a routine to pull it from the actual site and install it that way
https://repology.org/project/telegram-desktop/versions
Honestly the flatpak might be the best way to go for installing this thing
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 6:43 pm
by SwampRabbit
Sigi wrote: Tue Oct 05, 2021 6:39 pm
Just detected: MX 21-RC1 needs at least 10 GiB space for installation (VirtualBox with EFI enabled).
I'm using 6.86GBs on a fresh MX-21 RC1 Xfce install, I doubt MX-FB needs more
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 05, 2021 11:51 pm
by siamhie
Sigi wrote: Tue Oct 05, 2021 6:39 pm
Just detected: MX 21-RC1 needs at least 10 GiB space for installation (VirtualBox with EFI enabled).
My stock Flux rc1 installed at 4.9 GB. VB is showing 114MB installed from synaptic.
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 1:16 am
by i_ri
hello dolphin_oracle
install. disk usage reports 5.2GB ; inxi 4.83 GiB
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0
Distro: MX-21_fluxbox_rc1_x64 Wildflower Oct 05 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <filter>
Chassis: Hewlett-Packard type: 3 serial: <filter>
Mobo: MSI model: IONA v: 1.0 serial: <filter> BIOS: American Megatrends v: 5.15
date: 06/25/2010
CPU: Topology: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP arch: Nehalem
family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 23410
Speed: 1502 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1923 2: 1914 3: 1963
4: 1747
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0042
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: d800 bus ID: 01:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 28.65 GiB used: 4.86 GiB (17.0%)
ID-1: /dev/sda type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
RAID: Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080
bus ID: 00:1f.2 chip ID: 8086.2822 rev: 06
Partition: ID-1: / raw size: 27.14 GiB size: 26.55 GiB (97.81%) used: 4.86 GiB (18.3%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 1.50 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
Info: Processes: 204 Uptime: 16m Memory: 7.64 GiB used: 1.27 GiB (16.7%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 5:59 am
by app4soft
gThumb fails in "Segmentation fault" as it was in MX21-beta2
scrot v1.5.x is outdated and buggy - need update to v1.6.x for MX21 release (already in `bullseye-backports`)
Also there are various glitches probably related to
compton, especially visible on
xfce4-terminal startup (I use old PC with integrated GPU)
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 6:20 am
by chrispop99
app4soft wrote: Wed Oct 06, 2021 5:59 am
gThumb fails in "Segmentation fault" as it was in MX21-beta2
I tested this on several different pieces of hardware when you posted about it in the Beta thread, but it doesn't happen for me.
Are you running live or installed?
Does it do it every time you attempt to view an image?
Does it do it if you open gThumb from the menu?
Can you run gThumb from the terminal to see if there are any clues in the output?
Chris
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 6:45 am
by app4soft
chrispop99 wrote: Wed Oct 06, 2021 6:20 am
Are you running live or installed?
Actually I'm running LiveUSB
chrispop99 wrote: Wed Oct 06, 2021 6:20 am
Does it do it every time you attempt to view an image?
Does it do it if you open gThumb from the menu?
Can you run gThumb from the terminal to see if there are any clues in the output?
gThumb fails in all cases. In terminal it shows only next:
NOTE: If force "software-gl" (`$ LIBGL_ALWAYS_SOFTWARE=1 gthumb`)
gThumb works, so probably issue related to Mesa drivers (GPU: ATI RS600 / Radeon 1250 Xpress)
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 10:53 am
by siamhie
Installation went fine (as did with the betas) but during setup when you select 'Custom install on existing partitions' the screen resembles a spreadsheet and not the polished look it had on b2.
Kudos for including this feature (show, hide, tab). I almost forgot about tabbed titlebars.
211006_074718.png
Code: Select all
[code]
System: Host: <filter> Kernel: 5.14.0-1mx-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1mx-amd64
root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0
Distro: MX-21_fluxbox_rc1_x64 Wildflower Oct 05 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUSTeK product: K30BF_M32BF_A_F_K31BF_6 v: N/A
serial: <filter>
Mobo: ASUSTeK model: K30BF_M32BF_A_F_K31BF_6 v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 0401 date: 04/29/2015
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 serial: <filter>
charge: 100% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: AMD A10-7800 Radeon R7 12 Compute Cores 4C+8G bits: 64
type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48) stepping: 1
microcode: 6003106 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27931
Speed: 1396 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1396
2: 2114 3: 2030 4: 1396
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:130f
Device-2: AMD Oland PRO [Radeon R7 240/340] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 01:00.0 chip ID: 1002:6613
Display: x11 server: X.Org 1.20.11 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.14.0-1mx-amd64 LLVM 11.0.1)
v: 4.5 Mesa 20.3.5 direct render: Yes
Audio: Device-1: AMD Kaveri HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:1308
Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0
Sound Server: ALSA v: k5.14.0-1mx-amd64
Network: Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave
driver: rtl8821ae v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8821
IF: wlan0 state: down mac: <filter>
Device-2: NetGear Nighthawk A7000 802.11ac Wireless Adapter AC1900 [Realtek 8814AU]
type: USB driver: 8814au bus ID: 2-2:2 chip ID: 0846:9054 serial: <filter>
IF: wlan1 state: up mac: <filter>
Drives: Local Storage: total: 1.36 TiB used: 549.15 GiB (39.3%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC43 scheme: MBR
ID-2: /dev/sdb vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT
Partition: ID-1: / raw size: 130.00 GiB size: 126.90 GiB (97.62%) used: 6.37 GiB (5.0%) fs: ext4
dev: /dev/sdb3
ID-2: /home raw size: 100.00 GiB size: 97.87 GiB (97.87%) used: 558.8 MiB (0.6%)
fs: ext4 dev: /dev/sdb4
ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sdb2
Sensors: System Temperatures: cpu: 3.1 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: radeon temp: N/A device: radeon temp: 30 C
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
Info: Processes: 192 Uptime: 42m Memory: 14.60 GiB used: 1.21 GiB (8.3%) Init: systemd
v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
[/code]
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 11:16 am
by Jerry3904
You saw the new borders app? I love playing with that and now run with no titlebar and orange (active)/green borders. Very snazzy
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 2:11 pm
by mihail_bc
not loading the system in fluxbox DE in virtualbox
after boot up menu, just before loading the desktop, screen turns black and remains so
dell latitude E5430
on hardd disk, still using MX 16 xfce, no issues so far!
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 2:23 pm
by siamhie
Jerry3904 wrote: Wed Oct 06, 2021 11:16 am
You saw the new borders app? I love playing with that and now run with no titlebar and orange (active)/green borders. Very snazzy
I watched your video on how to do that.
I'm not familiar with moving around Fluxbox with a keyboard. Might have to create a conky with all the key commands and try out the borderless approach.
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 2:26 pm
by SwampRabbit
siamhie wrote: Wed Oct 06, 2021 2:23 pm
I watched your video on how to do that.
I'm not familiar with moving around Fluxbox with a keyboard. Might have to create a conky with all the key commands and try out the borderless approach.
I actually remember seeing manyroads do a Conky like that in another thread... might be worth looking at
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 3:29 pm
by Sprinterdriver
Hi.
For both KDE and XFCE editions, the iso files match the sha checksums.
However, the Fluxbox ISO does not match the check sum:
Code: Select all
[sprinterdriver@localhost mx-beta]$ md5sum MX-21_fluxbox_rc1_x64.iso
26dd0013274df66d8219fd260c6fea63 MX-21_fluxbox_rc1_x64.iso
[sprinterdriver@localhost mx-beta]$ cat MX-21_fluxbox_rc1_x64.iso.md5
c99d8b90e95dd403869b5fc1556e7638 MX-21_fluxbox_rc1_x64.iso
I did download the iso file twice, and get checksum mismatch both times, both files have different checksum.
My third download attempt using Firefox and Downthemall extention was successfull.
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 4:12 pm
by siamhie
Sprinterdriver wrote: Wed Oct 06, 2021 3:29 pm
Hi.
For both KDE and XFCE editions, the iso files match the sha checksums.
However, the Fluxbox ISO does not match the check sum:
Code: Select all
[sprinterdriver@localhost mx-beta]$ md5sum MX-21_fluxbox_rc1_x64.iso
26dd0013274df66d8219fd260c6fea63 MX-21_fluxbox_rc1_x64.iso
[sprinterdriver@localhost mx-beta]$ cat MX-21_fluxbox_rc1_x64.iso.md5
c99d8b90e95dd403869b5fc1556e7638 MX-21_fluxbox_rc1_x64.iso
I did download the iso file twice, and get checksum mismatch both times, both files have different checksum.
My third download attempt using Firefox and Downthemall extention was successfull.
I downloaded once with just FF and everything checked out.
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 4:18 pm
by siamhie
SwampRabbit wrote: Wed Oct 06, 2021 2:26 pm
siamhie wrote: Wed Oct 06, 2021 2:23 pm
I watched your video on how to do that.
I'm not familiar with moving around Fluxbox with a keyboard. Might have to create a conky with all the key commands and try out the borderless approach.
I actually remember seeing manyroads do a Conky like that in another thread... might be worth looking at
I believe I found it (post #5)
viewtopic.php?p=616585#p616585
I also found, while searching the forums, his web page that has a key bindings conky.
https://eirenicon.org/knowledge-base/keybinding-conky/
I should be able to put together a key bindings conky for Fluxbox. Thanks
@manyroads 
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 5:41 pm
by manyroads
siamhie wrote: Wed Oct 06, 2021 4:18 pm
[...]
I should be able to put together a key bindings conky for Fluxbox. Thanks @manyroads
Please let me know if you run into problems.... I'm happy to help, if I am able.
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 06, 2021 10:02 pm
by siamhie
manyroads wrote: Wed Oct 06, 2021 5:41 pm
siamhie wrote: Wed Oct 06, 2021 4:18 pm
[...]
I should be able to put together a key bindings conky for Fluxbox. Thanks @manyroads
Please let me know if you run into problems.... I'm happy to help, if I am able.
@manyroads That would be great. I'll message you with an idea I have based on your key bindings conky you have on your web site.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 2:58 am
by m_pav
mihail_bc wrote: Wed Oct 06, 2021 2:11 pm
not loading the system in fluxbox DE in virtualbox
after boot up menu, just before loading the desktop, screen turns black and remains so
dell latitude E5430
Runs fine in VirtualBox on my 9yo Lenovo running MX21 beta2. Maybe it's the version of VirtualBox you're running on your MX16, or you may have insufficient virtual hardware provisioning.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 5:21 am
by kobaian
Tested on metal.
1. Installation process without any problems, but the tab where you choose the partition to install the system looks a little bit scary.
Of course it works exactly the same as earlier, but I think some newbies might feel a little bit uncomfortable looking at that.
2. I like the new default tint2, mx-comfort gtk-themes and fb-styles. The default look of the system is now much more consistent than in the beta version.
3. Fluxbox submenus are still not localized. :(
4. There is still a problem with the app file. Why after opening any Yad dialog I can still see the dimensions and the position saved? I have to remove them manually. Yad windows should be managed by Yad and not by Fluxbox to avoid a strange look of the dialog boxes. I don't know if I'm right, but I feel like Fluxbox want to save the position and dimension of almost every app that I open for the first time.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 10:29 am
by PPC
Wonderfull work, Jerry and the rest of the dev team!
I tested MXFB rc1, 32bits live version in Virtualbox
The good:
-MXfb looks polished, I never tested the 32bits version- it runs like a crazy horse- in the 64bits betas I tested, I had problems when trying to use firefox in my 1 gb of RAM virtual machine- not any more!
-I loved the current refault tint2 toolbar- thumbnails in the taskbar are a great touch, as is being able to close windows with a right click in the taskbar (that was also available in the previous beta)
-Localized fluxbox menu no longer have missing sections in the first menu layer!! YEAH! (but more on that below)
-No conky!- great for me, I don't use it (but some users may miss it, is that by design?)
-The default theme is gorgeous (a nice spin on the Numix style that was my default theme for a very long time)
What needs improvement:
-Hum... Only "recent files" and "exit" submenus are localized, all the rest still do show up in english
-"All apps" menu entry on the first layer is not localized. I'm assuming you also found no easy way to localize the debian categories that are generated in the all apps submenu... Anything I can do to try to help with that?
-The "start menu" available on the default toolbar should run a script (already available) to toggle xfce app launcher on and off, not to confuse users...
...and that's all- this OS is almost as perfect as possible!
My personal suggestions:
-On the toolbar- add date (in whatever format to the clock); add icons to the taskbar (my reasoning: it's way faster locating an icon than reading the title of the window); hide non used workspaces in the taskbar (my reasoning: try to open many windows and all that you'll see in the taskbar is the empty space before the window title, that can be desorianting)
- I love the default style but there's one thing that I find confusing: on the taskbar, the window with focus has a thicker blue upper border. Ok, when using a maximized window, with several apps running, the blue corners of the windows "touch" the top of the toolbar, making it more confusing finding the window with focus on the taskbar- we get, long the toolbar border, a succession of thincker and thinner blue upper boarders...) my suggestion? keep the top blue corner, but also make the background of the focused window title (and or icon) on the taskbar Blue, so it's easier to find (or make the focused border way larger)
- Horizontally align the desktop icons (I don't use desktop icons, but seeing them that way makes me glad I always turn idesk off :-) )
- I don't know if It's a VB problem, but I tried some styles that worked well on the beta2 and I get dark gray test on dark background, making the fluxbox menu almost impossible to read in those styles (It's perfect in the default style)
EDIT: -maybe add a "show desktop" button, on the default toolbar config- handy for people that want to access the dock, desktop icons or see a conky output.
I'm partial to the current tint2 config being used- because it looks so much like my own config, and the style looks so much with one of my default styles that, if not for the missing taskbar icons and the date on the clock, I can mistake it for my own default system!
The best praise I can give you if that I think that "normies", used to the mainstream OS, probably just look at the MXFB and think it's some kind of new "Windows 11" version, made to run on almost any available computer!
The style is gorgeous, the taskbar also, the wallpaper is beautiful- the OS runs on light resources (the 32 bits version, turning off the dock, icons and stuff from the systray runs on less than 200mb - so, yes, you can run MX linux on crappy old single core, 1 Gb computers, and still have enough RAM to have a couple of open tabs on firefox!
Great work, Team!
P.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 11:20 am
by siamhie
kobaian wrote: Thu Oct 07, 2021 5:21 am
Tested on metal.
1. Installation process without any problems, but the tab where you choose the partition to install the system looks a little bit scary.
Of course it works exactly the same as earlier, but I think some newbies might feel a little bit uncomfortable looking at that.
I selected 'Custom install on existing partitions' (resembles a spreadsheet). Is that the option you selected also?
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 12:11 pm
by Jerry3904
@PPC : alternative to making all those changes (which ain't gonna happen) is for the user to simply launch tint2 manager and select another toolbar. There's 10 or so available.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 2:28 pm
by Jerry3904
I'm in an airport between flights so only have time to pick up one topic: many of. the styles are unreadable.
To use the new default style, we needed to disable the style settings in the overlay file. What people see now is how the style was originally written.
BUT: to solve this we created a new app. Click menu > appearance > style, and in the top section (overlay) click "menu font." There you can toggle between native style font and the universal one that we used before by default.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 2:39 pm
by kobaian
siamhie wrote: Thu Oct 07, 2021 11:20 am
kobaian wrote: Thu Oct 07, 2021 5:21 am
Tested on metal.
1. Installation process without any problems, but the tab where you choose the partition to install the system looks a little bit scary.
Of course it works exactly the same as earlier, but I think some newbies might feel a little bit uncomfortable looking at that.
I selected 'Custom install on existing partitions' (resembles a spreadsheet). Is that the option you selected also?
Yes, that's right. I have to choose custom install, because I have a special partition for testing systems. MX19 with all my files, documents and pictures is still there on another partition. That's why I think It will be better to see something less scary while doing so important choice.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 2:51 pm
by Eadwine Rose
LOL You should see mine, 5 drives, all of them having at least 3 partitions.
Use the drop arrow on the left to collapse what you aren't going to use, that'll clear things up a bit and make it less scary.
(trust me, I lost my bleep when I saw the new installer for the first time and ran off having a panic attack
At least I can laugh about it now, and collapsing things is good!)
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 3:00 pm
by Jerry3904
The ability to use Shift as a modifier does not work desire what I thought I understood from this discussion:
viewtopic.php?f=143&t=66504
We need it to open mx-manual, since that key combo was written into the MXFB documentation on p. 1
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 3:16 pm
by dolphin_oracle
Jerry3904 wrote: Thu Oct 07, 2021 3:00 pm
The ability to use Shift as a modifier does not work desire what I thought I understood from this discussion:
viewtopic.php?f=143&t=66504
We need it to open mx-manual, since that key combo was written into the MXFB documentation on p. 1
sorry I'll adjust the live system.
for now, users can use "System Keyboard" app to change the keyboard toggle to something else or disable altogether.
that said, the current toggle should be "rcontrol+rshift" which I wouldnt' think would stop using shift as a modifier. however, I can't change that value via update, so if you updated from a beta you won't see the change. however, another user also reported a problem with selecting text that I'm sure is related to the keyboard toggle key combo.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 3:46 pm
by fehlix
Jerry3904 wrote: Thu Oct 07, 2021 3:00 pm
The ability to use Shift as a modifier does not work desire what I thought I understood from this discussion:
viewtopic.php?f=143&t=66504
We need it to open mx-manual, since that key combo was written into the MXFB documentation on p. 1
Shift+F1 opens here: MX Linux Users Manual v. 20210925
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 3:49 pm
by Jerry3904
Didn't work here on a fresh install.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 4:01 pm
by chrispop99
fehlix wrote: Thu Oct 07, 2021 3:46 pm
Jerry3904 wrote: Thu Oct 07, 2021 3:00 pm
The ability to use Shift as a modifier does not work desire what I thought I understood from this discussion:
viewtopic.php?f=143&t=66504
We need it to open mx-manual, since that key combo was written into the MXFB documentation on p. 1
Shift+F1 opens here: MX Linux Users Manual v. 20210925
Works here on both a 32- and 64-bit install.
Chris
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 4:04 pm
by Jerry3904
I'd love to be wrong
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 4:20 pm
by siamhie
kobaian wrote: Thu Oct 07, 2021 2:39 pm
Yes, that's right. I have to choose custom install, because I have a special partition for testing systems. MX19 with all my files, documents and pictures is still there on another partition. That's why I think It will be better to see something less scary while doing so important choice.
Eadwine Rose wrote: Thu Oct 07, 2021 2:51 pm
LOL You should see mine, 5 drives, all of them having at least 3 partitions.
Use the drop arrow on the left to collapse what you aren't going to use, that'll clear things up a bit and make it less scary.
(trust me, I lost my bleep when I saw the new installer for the first time and ran off having a panic attack
At least I can laugh about it now, and collapsing things is good!)
I brought it up (comment #12) that the screen looked better in b2. That one had a more polished look to it.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 4:25 pm
by siamhie
Jerry3904 wrote: Thu Oct 07, 2021 3:49 pm
Didn't work here on a fresh install.
Works for me when I installed rc1 yesterday. Here's the section from the keys file.
Code: Select all
###########
# take a screen capture
none Print :Exec mxfb-quickshot
# open help
Ctrl F1 :Exec mxfb-help
Shift F1 :Exec mx-manual
# open a little run terminal
Ctrl F2 :Exec fbrun
# use logo key for rofi
Super_L :Exec rofi -show drun
# open a file manager
Ctrl F3 :Exec thunar /home/$USER/.fluxbox
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 5:03 pm
by siamhie
Speaking of key bindings. Selecting Print doesn't launch quickshot but selecting Menu Print does.
Code: Select all
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
#Mouse4=Scroll wheel up
#Mouse5=Scroll wheel down
###########
#NOTE: unmodified Fn keys left unassigned to avoid conflict with apps
###########
# take a screen capture
none Print :Exec mxfb-quickshot
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 07, 2021 6:02 pm
by Jerry3904
So on the flight to MSP I tested again and it worked. So scratch that report @dolphin_oracle . Yeah!
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 4:51 am
by Jerry3904
siamhie wrote: Thu Oct 07, 2021 5:03 pm
Speaking of key bindings. Selecting Print doesn't launch quickshot but selecting Menu Print does.
Code: Select all
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
#Mouse4=Scroll wheel up
#Mouse5=Scroll wheel down
###########
#NOTE: unmodified Fn keys left unassigned to avoid conflict with apps
###########
# take a screen capture
none Print :Exec mxfb-quickshot
Pressing Print changes the cursor from a pointer to a select function--on my system a small cross. No program launch is visible which is what makes it so fast.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 5:10 am
by Jerry3904
About localization:
--it should be localized 2 layers down now.
--not sure ATM about the Debian menu. I did include those category translations in the template, but perhaps the localization for those will have to be done inside the menu generator app itself. Need to check with people like
@fehlix who know more about this than I do.
--MXFB documentation: for improvement of DeepL translations:
1) use docx files in /usr/share/mxflux/help/source. Send something I can easily figure out (like an entire section) to manual AT mxlinux DOT org
2) make a Pull Request on Git, files are here:
https://github.com/MX-Linux/mxfb-docs/t ... elp/source
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 7:05 am
by siamhie
Jerry3904 wrote: Fri Oct 08, 2021 4:51 am
Pressing Print changes the cursor from a pointer to a select function--on my system a small cross. No program launch is visible which is what makes it so fast.
@Jerry3904 Were talking about the Print Scr button, correct? That's what's labeled on my Logitech K360 keyboard. If I just press that button, my mouse pointer doesn't change but if I press (in combo) the Right logo key and the Print Scr button my mouse pointer changes to a cross.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 9:13 am
by Jerry3904
OK. At least there's three other ways to launch it, right? (dock icon, Appfinder, Rofi). You can remap that button if you want.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 9:18 am
by Jerry3904
I'm trying to avoid forcing the new user to resize the Settings Manager. Can people please test this change in the apps file?
--find the custom-toolbox entry
--reduce it to this
Code: Select all
[app] (name=custom-toolbox) (class=custom-toolbox)
[end]
--Menu > Leave > Refresh
--now launch the Settings Manager, and I hope you see a full two-column window open.
When you report, please include screen resolution--TIA
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 9:27 am
by Jerry3904
@kobaian I'm not sure what you want about yad. I tried deleting the entry from the apps file but then the yad window shows up in the upper left corner and, if you change dimensions or position, it won't stick unless you right-click the titlebar and check to remember those as well as Save on close. So I can't see how I could change the default setting there. But maybe I misunderstood...
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 10:34 am
by siamhie
Jerry3904 wrote: Fri Oct 08, 2021 9:13 am
OK. At least there's three other ways to launch it, right? (dock icon, Appfinder, Rofi). You can remap that button if you want.
Correct. It's probably because of my multimedia keyboard. (it has previous, play/pause, next, mute, vol up and vol down buttons on it)
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 11:37 am
by kobaian
Jerry3904 wrote: Fri Oct 08, 2021 9:27 am
@kobaian I'm not sure what you want about yad. I tried deleting the entry from the apps file but then the yad window shows up in the upper left corner and, if you change dimensions or position, it won't stick unless you right-click the titlebar and check to remember those as well as Save on close. So I can't see how I could change the default setting there. But maybe I misunderstood...
In MX19 I opened yad dialogs many times and there was no entry in app file at all. The position and dimensions was determined by Yad itself. The standard position is the upper left corner, but if you add
--center to the script the dialog is the center of the screen. I wonder why in MX21 the position of the window are determined by the app-file and not by the yad-script itself.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 11:37 am
by siamhie
Jerry3904 wrote: Fri Oct 08, 2021 9:18 am
I'm trying to avoid forcing the new user to resize the Settings Manager. Can people please test this change in the apps file?
--find the custom-toolbox entry
--reduce it to this
Code: Select all
[app] (name=custom-toolbox) (class=custom-toolbox)
[end]
--Menu > Leave > Refresh
--now launch the Settings Manager, and I hope you see a full two-column window open.
When you report, please include screen resolution--TIA
No change for me. 1920x1080
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 12:14 pm
by Jerry3904
What does the Settings Manager look like (position, dimensions)?
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 12:30 pm
by siamhie
Jerry3904 wrote: Fri Oct 08, 2021 12:14 pm
What does the Settings Manager look like (position, dimensions)?
This is what I have. No mention of dimensions but other entries have them.
Code: Select all
[app] (name=mx-tools) (class=mx-tools)
[Dimensions] {36% 82%}
[Position] (UPPERLEFT) {32% 7%}
[Close] {yes}
[end]
[app] (name=custom-toolbox) (class=custom-toolbox)
[Position] (UPPERLEFT) {32% 6%}
[Close] {yes}
[end]
[app] (name=qpdfview) (class=qpdfview)
[Dimensions] {66% 93%}
[Position] (UPPERLEFT) {20% 3%}
[Close] {yes}
[end]
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 12:51 pm
by Jerry3904
OK, thanks. Never mind the numbers--does the window show all or most of the icons? Can you attach a pic?
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 1:25 pm
by siamhie
Jerry3904 wrote: Fri Oct 08, 2021 12:51 pm
OK, thanks. Never mind the numbers--does the window show all or most of the icons? Can you attach a pic?
When I initially opened it, it showed two rows of icons but I've since resized it and saved the settings via the title bar.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 1:42 pm
by Jerry3904
Thanks.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 4:37 pm
by PPC
In MXFB 32bits RC1, live mode, in VirtualBox, when I try to install anything (I tried a couple of packages), it seems there's an error with the fluxbox menu updater hook... I get this:
Code: Select all
Please wait, creating menu file - stored in /home/demo/.fluxbox/submenus/full_menu ...
Menu file created and ready to be used
3399
E: Problem executing scripts DPkg::Post-Invoke 'su $(logname) /usr/bin/mxfb-menu-generator'
E: Sub-process returned an error code
Edit:
Also, when I open dockmaker, if I click the "edit" button, the default dock file is only displayed if I click the "all files" option on the lower right
P.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 10:26 pm
by brad
Code: Select all
Errors were encountered while processing:
backuppc
logname: no login name
su: user /usr/bin/mxfb-menu-generator does not exist or the user entry does not contain all the required fields
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Problem executing scripts DPkg::Post-Invoke 'su $(logname) /usr/bin/mxfb-menu-generator'
E: Sub-process returned an error code
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 08, 2021 10:29 pm
by dolphin_oracle
brad wrote: Fri Oct 08, 2021 10:26 pm
Code: Select all
Errors were encountered while processing:
backuppc
logname: no login name
su: user /usr/bin/mxfb-menu-generator does not exist or the user entry does not contain all the required fields
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Problem executing scripts DPkg::Post-Invoke 'su $(logname) /usr/bin/mxfb-menu-generator'
E: Sub-process returned an error code
just pushed an update for that one a few minutes ago thanks.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 11:07 am
by Girafenaine
Hello,
Thank you very much for this new release of my prefered linux OS ! I post here as a daily MX and antiX user since 2 years, especially with fluxbox windows manager.
Quick infos :
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet disable_theme splash
Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0
Distro: MX-21_fluxbox_rc1_x64 Wildflower Oct 05 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: <filter> Chassis:
type: 10 serial: <filter>
Mobo: Dell model: 0VYV0G v: A00 serial: <filter> UEFI: Dell v: 1.13.0
date: 07/22/2021
Battery: ID-1: BAT0 charge: 71.4 Wh condition: 81.0/97.0 Wh (83%) volts: 12.8/11.4
model: SMP DELL GPM0365 type: Li-ion serial: <filter> status: Unknown
CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake
family: 6 model-id: 9E (158) stepping: A (10) microcode: EA L2 cache: 12.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399
Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 801 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Dell driver: N/A
bus ID: 01:00.0 chip ID: 10de:1f91
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 00:1f.3 chip ID: 8086:a348
Device-2: Texas Instruments SMSL M-3 Desktop DAC type: USB driver: snd-usb-audio
bus ID: 1-2:3 chip ID: 0451:0003 serial: <filter>
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks driver: iwlwifi v: kernel
port: 3000 bus ID: 3b:00.0 chip ID: 8086:2723
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 480.69 GiB used: 359.64 GiB (74.8%)
ID-1: /dev/nvme0n1 vendor: Micron model: 2200S NVMe 512GB size: 476.94 GiB
block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: 22001020 scheme: GPT
ID-2: /dev/sda type: USB vendor: Generic model: Flash Disk size: 3.75 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
Partition: ID-1: / raw size: 26.99 GiB size: 26.40 GiB (97.81%) used: 4.85 GiB (18.4%) fs: ext4
dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 49.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2406 fan-2: 2412
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/mx/repo/ bullseye main non-free
Info: Processes: 300 Uptime: 17m Memory: 15.27 GiB used: 1.62 GiB (10.6%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Here are some points I would like to put forward :
1. thanks ! it's a pleaure to see this nice and fast and efficient linux OS to keep evolving.
- thanks for deadbeef and qpdfview as default apps. They have been apps of choice for me since years. I used to met an issue with qpdfview that does not get focus when already opened in the background and you open a new pdf file, but it seems that there is not this issue in MXFB 21... I don't know why but it is great.
2. great to see the new settings manager for MXFB, without the last "xfce settings manager" which was strange in MXFB 19. This setting manager has a few issues in my eyes :
- its window size is strange and does not fit the icons. I have to resize it every time I open it to be able to see all icons (with 3 or 4 icons columns).
- the buttons don't fit the categories as far as I am concerned. You have Pulseaudio, audio card and alsamixer in three different categories, while all of them are about audio ! I suggest :
a. Change "user" category in "Interface and appearance"
b. Put together "System" and "Hardware" in only one "System" category
c. Move "Trashscheck" and "Mugshot" in that "System" category
- For a next update or release, I suggest to put together "Settings manager" and "MX tools", since I guess newcomers will spend time to look in both panels. I don't see any good logical reason to keep them separated. We would have to add some categories (maintenance, utilities...) in the "MXFB settings manager". I think of antiX settings panel as a good way to follow.
3. Appearance :
- I know it's all about personal tastes, but I don't like the default background, and above all I guess it will deter some new users ! The pink tone, the blurry aspect... not very clean and modern. While it's nice to have some choice in the "background/nitrogen" setting, the default background could be much more monotone and elegant. In the available options I suggest picking mxfb_graycubes, mxfb_bluerain or MX_KXF_Blues as default background.
- great to have tint2 as default panel and a choice of preconfigured panels ! thanks for that. I find that the default one is nice, but : too large (menu icon on the left could be a little smaller, and get all the panel to be thinner), and windows buttons are not easy at all to read and pick up ! A default panel with icons and text rather than text alone could be easier to use (+apps buttons should be wider to have more text to read)
- the main app menu on the left in the tint2 panel should be modified with a little script to make it open then close. It would behave as everyone expect from such a menu. I believe that several forum members already suggested that point - and easy script to do that ! I use :
Code: Select all
test=$(ps -C xfce4-appfinder -o pid=)
if [$test == ""]; then
xfce4-appfinder --disable-server &
else
kill "$test"
fi
, I find much more efficient to have two-fingers-click for right-click, and three-fingers-click for middle-click. We could configure libinput and synaptics that way by default, or have an option in MX-adjustement "other" tab. I am used to make the change every time I install an OS, but it would be great to have it out-of-the-box, especially for new users.
5. Right-click fluxbox menu :
- I read "Settings manager", and then "settings". That's confusing, and I suggest : first, to name the second one "Fluxbox settings", and then to name the first one "System settings and tools" and to move it in the last part, next to "Fluxbox Settings".
- "out-of-sight" could be moved into the "appearance" category, as it will not be of daily use, and quite logical to find it under "appearance".
And I should add... I am very proud to see the "recent docs" submenu in the MXFB right-click menu, as I adapted it from BobC script last year :)
I will be happy to help with the above points if I can.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 11:45 am
by Jerry3904
Thanks for the details feedback! It's very late to be making changes, and some of them )menus, for instance) would cause big trouble. But they will definitely all be considered for the future.
We're have just fixed the Settings Manager problem you raise btw.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 12:22 pm
by mbmalone
I have an HP Stream-14 Notebook and cannot get the brightness systray app to function at all (systray icon does load). The screen is set to 100% brightness upon boot and I haven't discovered another way to adjust it. The PC105 US keyboard appears to be working properly and normally the F2 and F3 keys would control screen brightness on this notebook. The keys work properly on MX Xfce. I've searched through the forums with people struggling for a solution or workaround. I think this is a bug.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 12:44 pm
by dolphin_oracle
mbmalone wrote: Sat Oct 09, 2021 12:22 pm
I have an HP Stream-14 Notebook and cannot get the brightness systray app to function at all. The screen is set to 100% brightness upon boot and I haven't discovered another way to adjust it. The PC105 US keyboard appears to be working properly and normally the F2 and F3 keys would control screen brightness on this notebook. The keys work properly on MX Xfce.
if you would, try running
Code: Select all
/usr/lib/mx-tweak/backlight-brightness
in a terminal and see if you can adjust brightness that way.
also the output of
might be useful.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 12:59 pm
by mbmalone
dolphin_oracle wrote: Sat Oct 09, 2021 12:44 pm
mbmalone wrote: Sat Oct 09, 2021 12:22 pm
I have an HP Stream-14 Notebook and cannot get the brightness systray app to function at all. The screen is set to 100% brightness upon boot and I haven't discovered another way to adjust it. The PC105 US keyboard appears to be working properly and normally the F2 and F3 keys would control screen brightness on this notebook. The keys work properly on MX Xfce.
if you would, try running
Code: Select all
/usr/lib/mx-tweak/backlight-brightness
in a terminal and see if you can adjust brightness that way.
also the output of
might be useful.
Code: Select all
sudo /usr/lib/mx-tweak/backlight-brightness
seems to be working perfectly .....
$ ls /sys/class/backlight
intel_backlight
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 1:03 pm
by mbmalone
how do I delete this post?
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 1:10 pm
by mbmalone
If the systemtray display app is working, the control adjustment is off the screen somewhere or hidden below the bottom toolbar. I can't see or adjust it there, only the icon appears in the system tray.
This is working ...
Code: Select all
sudo /usr/lib/mx-tweak/backlight-brightness -10
sudo /usr/lib/mx-tweak/backlight-brightness +10
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 1:43 pm
by dolphin_oracle
Ok it’s probably coming up off screen. We just did a similar fox for the Unmounter tool.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 09, 2021 2:21 pm
by Girafenaine
Jerry3904 wrote: Sat Oct 09, 2021 11:45 am
Thanks for the details feedback! It's very late to be making changes, and some of them )menus, for instance) would cause big trouble. But they will definitely all be considered for the future.
We're have just fixed the Settings Manager problem you raise btw.
Thanks Jerry for your answer. I am sorry to be late, and I don't know how I could have helped sooner, except when I saw the beta release - but september was too heavy at work...
I just hope some of my points could be useful for MXFB 21 ! The system itself (debian, MX repo and MX tools, antiX live abilities) and the customization options (tint2, fluxbox menu and keys and startup and windows settings...) are wonderful. But the default appearance and UX could be easier and more polished for a new user.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 10, 2021 7:57 am
by siamhie
Was this removed during a recent update? I can no longer find Top under Settings>Configure.
top.png
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 10, 2021 8:17 am
by Jerry3904
Try Appearance > Style
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 10, 2021 8:51 am
by siamhie
Jerry3904 wrote: Sun Oct 10, 2021 8:17 am
Try Appearance > Style
Thanks
@Jerry3904. I couldn't remember where I saw it the first time.
Re: MX-21 Fluxbox RC1 feedback
Posted: Mon Oct 11, 2021 10:52 am
by siamhie
@manyroads I've been running the 5.14 kernel for about a week now on Fluxbox rc1 with no issues.
viewtopic.php?f=115&p=656652#p656652
@SwampRabbit asked me to test the rtl8814 driver against the kernel and report any issues (which there were none).
Code: Select all
System: Host: <filter> Kernel: 5.14.0-1mx-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1mx-amd64
root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0
Distro: MX-21_fluxbox_rc1_x64 Wildflower Oct 05 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUSTeK product: K30BF_M32BF_A_F_K31BF_6 v: N/A
serial: <filter>
Mobo: ASUSTeK model: K30BF_M32BF_A_F_K31BF_6 v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 0401 date: 04/29/2015
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 serial: <filter>
charge: 100% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: AMD A10-7800 Radeon R7 12 Compute Cores 4C+8G bits: 64
type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48) stepping: 1
microcode: 6003106 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27927
Speed: 1397 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 2033
2: 2173 3: 2341 4: 2213
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:130f
Device-2: AMD Oland PRO [Radeon R7 240/340] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 01:00.0 chip ID: 1002:6613
Display: x11 server: X.Org 1.20.11 driver: ati,radeon
unloaded: fbdev,modesetting,vesa compositor: compton v: 1 resolution: 1920x1080~60Hz
OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.14.0-1mx-amd64 LLVM 11.0.1)
v: 4.5 Mesa 20.3.5 direct render: Yes
Audio: Device-1: AMD Kaveri HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:1308
Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0
Sound Server: ALSA v: k5.14.0-1mx-amd64
Network: Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave
driver: rtl8821ae v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8821
IF: wlan0 state: down mac: <filter>
Device-2: NetGear Nighthawk A7000 802.11ac Wireless Adapter AC1900 [Realtek 8814AU]
type: USB driver: 8814au bus ID: 2-2:2 chip ID: 0846:9054 serial: <filter>
IF: wlan1 state: up mac: <filter>
Drives: Local Storage: total: 1.36 TiB used: 551.34 GiB (39.5%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC43 scheme: MBR
Partition: ID-1: / raw size: 130.00 GiB size: 126.90 GiB (97.62%) used: 7.10 GiB (5.6%) fs: ext4
dev: /dev/sda3
ID-2: /home raw size: 100.00 GiB size: 97.87 GiB (97.87%) used: 1.19 GiB (1.2%)
fs: ext4 dev: /dev/sda4
ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 0.0 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: radeon temp: N/A device: radeon temp: 29 C
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 207 Uptime: 1h 27m Memory: 14.60 GiB used: 1.88 GiB (12.8%) Init: systemd
v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX-21 Fluxbox RC1 feedback
Posted: Mon Oct 11, 2021 11:09 am
by manyroads
FWIW. [complaint] This entire process (of repos & testing) is
so much more difficult than it is on an arch distro. :lipsrsealed:. [/complaint]
As a good citizen, I try to live as close to the edge of what works on Debian, just so folks get early stress testing (and because much of what I use can't wait like a good wine to mature/stablize).
Anyway, I'm glad to see you are also having success.
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 15, 2021 4:43 pm
by siamhie
Is it possible we can get that red icon that was used prior the recent MXFB update for the Settings Manager icon on the tint2 panel back (third from the left).
This is what my modified (weather/calendar) tint2rc panel looks like now.
To me, it looks like two instances of Application Finder with one of them having some sort of blue overlay added.
211015_130531.png
Re: MX-21 Fluxbox RC1 feedback
Posted: Fri Oct 15, 2021 5:05 pm
by siamhie
manyroads wrote: Mon Oct 11, 2021 11:09 am
As a good citizen, I try to live as close to the edge of what works on Debian, just so folks get early stress testing (and because much of what I use can't wait like a good wine to mature/stablize).
Anyway, I'm glad to see you are also having success.
@manyroads As a home desktop user, I am, and I am so grateful to the coders/developers/maintainers of MXL to release a stand-alone version of Fluxbox to their line-up. Flux will always remain near and dear to my heart.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sat Oct 16, 2021 8:04 pm
by siamhie
siamhie wrote: Fri Oct 15, 2021 4:43 pm
Is it possible we can get that red icon that was used prior the recent MXFB update for the Settings Manager icon on the tint2 panel back (third from the left).
This is what my modified (weather/calendar) tint2rc panel looks like now.
To me, it looks like two instances of Application Finder with one of them having some sort of blue overlay added.
211015_130531.png
I ended up editing the custom-toolbox-mxfb.desktop file to have the icon point to mxfb-settings.svg instead of custom-toolbox.svg.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 7:59 am
by mystic
@dolphin_oracle
Monitor brightness setting doesn't work for me on my laptop in Fluxbox. Its set to maximum by default.
It works if I install other desktop environments like Cinnamon DE.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 8:44 am
by siamhie
mystic wrote: Sun Oct 17, 2021 7:59 am
@dolphin_oracle
Monitor brightness setting doesn't work for me on my laptop in Fluxbox. Its set to maximum by default.
It works if I install other desktop environments like Cinnamon DE.
Fluxbox is a window manager, not a desktop environment. Have you tried All Apps>Settings>Brightness Systray?
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 9:01 am
by mystic
@siamhie
The app doesn't even launch.
It might be specific to my hardware only, again I tested this only in a live environment since I have only one Laptop with me.
Can you tell if it works for you, the brightness settings?
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 9:14 am
by Jerry3904
It's working fine for me when installed.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 9:20 am
by ceeslans
mystic wrote: Sun Oct 17, 2021 9:01 am...
The app doesn't even launch.
It might be specific to my hardware only, again I tested this only in a live environment since I have only one Laptop with me.
...
Selecting 'brightness systray' would trigger a brightness icon showing up in the systray - and leftclicking it should show you a panel to adjust brightness and backlight levels.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 9:22 am
by dolphin_oracle
I did recently update the brightness-systray app with a fix to an issue where the app opened off-screen on fluxbox.
Re: MX-21 Fluxbox RC1 feedback
Posted: Sun Oct 17, 2021 10:39 am
by siamhie
mystic wrote: Sun Oct 17, 2021 9:01 am
@siamhie
The app doesn't even launch.
It might be specific to my hardware only, again I tested this only in a live environment since I have only one Laptop with me.
Can you tell if it works for you, the brightness settings?
Yes, it worked for me.
Re: MX-21 Fluxbox RC1 feedback
Posted: Tue Oct 19, 2021 5:58 pm
by i_ri
hello dolphin_oracle
yoga 2 11 20428
live
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us
tz=America/Phoenix
Desktop: Fluxbox 1.3.7 dm: LightDM 1.26.0
Distro: MX-21_fluxbox_rc1_x64 Wildflower Oct 05 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: LENOVO product: 20428 v: Lenovo Yoga 2 11 serial: <filter>
Chassis: type: 10 v: Lenovo Yoga 2 11 serial: <filter>
Mobo: LENOVO model: VIUU4 v: 31900058WIN serial: <filter> UEFI: LENOVO v: AACN21WW
date: 01/30/2015
Battery: ID-1: BAT0 charge: 18.5 Wh condition: 29.4/34.0 Wh (86%) volts: 8.1/7.4
model: Lenovo IdeaPad type: Unknown serial: <filter> status: Charging
CPU: Topology: Dual Core model: Intel Core i3-4012Y bits: 64 type: MT MCP arch: Haswell
family: 6 model-id: 45 (69) stepping: 1 microcode: 17 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 11972
Speed: 692 MHz min/max: 600/1500 MHz Core speeds (MHz): 1: 785 2: 786 3: 788 4: 795
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0a1e
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4200 (HSW GT2) v: 4.5 Mesa 20.3.5
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:0a0c
Device-2: Intel 8 Series HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:1b.0 chip ID: 8086:9c20
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lenovo
driver: ath9k v: kernel port: 3040 bus ID: 01:00.0 chip ID: 168c:0036
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb bus ID: 2-5:7
chip ID: 0cf3:3004
Drives: Local Storage: total: 480.67 GiB used: 1.68 GiB (0.3%)
ID-1: /dev/sda vendor: Seagate model: ST500LX012-SSHD-8GB size: 465.76 GiB
block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm
serial: <filter> rev: LVM1 scheme: GPT
ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Glide size: 14.91 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 2.94 GiB used: 291.0 MiB (9.7%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 48.5 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
Info: Processes: 202 Uptime: 27m Memory: 3.73 GiB used: 1.07 GiB (28.6%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 20, 2021 3:37 pm
by Girafenaine
Hello,
I don't see tlpui package in MX test repo, under MX21. This package does exist under MX19 (and it is nice to manage tlp in the easy way).
Is it planned to get it again ?
Re: MX-21 Fluxbox RC1 feedback
Posted: Wed Oct 20, 2021 4:04 pm
by timkb4cq
Yes.
It just got missed. I'll build the new version.
Re: MX-21 Fluxbox RC1 feedback
Posted: Thu Oct 21, 2021 9:25 am
by Girafenaine
timkb4cq wrote: Wed Oct 20, 2021 4:04 pm
Yes.
It just got missed. I'll build the new version.
Thank you very much !
