MX Linux Forum

Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/

MX-21 fluxbox beta 1 feedback thread.

http://www.forum.mxlinux.org/viewtopic.php?t=66050

Page 1 of 1

MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 3:17 pm
by dolphin_oracle
This thread is for items specific to the mx-21 fluxbox beta 1 isos.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 3:58 pm
by chrispop99
Every boot live and installed, on a 64-bit desktop machine, generates an xmessage;

Code: Select all

tint2:Battery low!
Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 4:19 pm
by Jerry3904
Just getting back after a long work day, haven't had a chance to even download yet.

The tint2 we are using as default includes an active battery item for the first time. It is set to show in red when battery level drops to 30%, but perhaps there is a problem with the setup. I would think a log out/in would clear it, but if not the easiest solution for now: use Settings manager > Tint2manager to select the same tint2 without the battery: "nobattery-tint2rc"

-------

Now running Live: no message. But that may just be because I am on the same machine I do MXFB development on, and X figures it has already given me the message...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 5:02 pm
by Melber
The 64 bit download link for md5_checksum_signature points to the 32 bit md5.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 5:16 pm
by dolphin_oracle
Melber wrote: Fri Aug 20, 2021 5:02 pm The 64 bit download link for md5_checksum_signature points to the 32 bit md5.
fixed thank you.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 5:19 pm
by oops
chrispop99 wrote: Fri Aug 20, 2021 3:58 pm Every boot live and installed, on a 64-bit desktop machine, generates an xmessage;

Code: Select all

tint2:Battery low!
...
Hello,
Same here too.
PS: I have added the info:loadavg into an executor (can be useful)

Code: Select all

#-------------------------------------
# Executor 2
execp = new
execp_command = cat /proc/loadavg | awk '{print "C:"$1 }'
execp_interval = 10
execp_has_icon = 0
execp_cache_icon = 1
execp_continuous = 0
execp_markup = 1
execp_lclick_command = xterm -geometry 90x12+40+40 -hold -e "echo $USER ; echo 'Charge CPU' ; echo '1min 5min 15min' ; cat /proc/loadavg ; vmstat"
execp_rclick_command = xterm -geometry 150x38+40+40 -hold -e "inxi -v8"
execp_mclick_command = 
execp_uwheel_command = 
execp_dwheel_command = 
execp_font = Noto Sans 8
execp_font_color = #f5caff 100
execp_padding = 0 0
execp_background_id = 0
execp_centered = 0
execp_icon_w = 0
execp_icon_h = 0

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 6:06 pm
by Jerry3904
Ran it Live on my good old AAO 722:

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 
           Desktop: Fluxbox 1.3.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: AO722 v: V1.08 serial: <filter> Chassis: type: 10 
           v: 1.08 serial: <filter> 
           Mobo: Acer model: JE10-BZ serial: <filter> BIOS: Acer v: 1.08 date: 12/06/2011 
Battery:   ID-1: BAT1 charge: 29.6 Wh condition: 37.0/48.8 Wh (76%) volts: 10.8/11.1 
           model: Sanyo AL10B31 type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: AMD C-60 APU with Radeon HD Graphics bits: 64 type: MCP 
           arch: Bobcat family: 14 (20) model-id: 2 stepping: N/A microcode: 5000119 
           L2 cache: 512 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3990 
           Speed: 802 MHz min/max: 800/1000 MHz boost: enabled Core speeds (MHz): 1: 801 2: 800 
           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 status: Vulnerable 
           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 Wrestler [Radeon HD 6290] vendor: Acer Incorporated ALI driver: radeon 
           v: kernel bus ID: 00:01.0 chip ID: 1002:9807 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
           unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: AMD Wrestler HDMI Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:01.1 chip ID: 1002:1314 
           Device-2: AMD SBx00 Azalia vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: Acer Incorporated ALI 
           driver: atl1c v: kernel port: 2000 bus ID: 06:00.0 chip ID: 1969:2062 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On 
           driver: ath9k v: kernel port: 2000 bus ID: 07:00.0 chip ID: 168c:0032 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 270.83 GiB used: 1.34 GiB (0.5%) 
           ID-1: /dev/sda vendor: Crucial model: CT275MX300SSD1 size: 256.17 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: R040 scheme: MBR 
           ID-2: /dev/sdc type: USB vendor: Kingston model: DataTraveler 3.0 size: 14.65 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
Partition: ID-1: / raw size: N/A size: 5.96 GiB used: 21.6 MiB (0.4%) fs: overlay 
           source: ERR-102 
           ID-2: swap-1 size: 21.80 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 59.5 C mobo: N/A gpu: radeon temp: 59 C 
           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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 171 Uptime: 10m Memory: 7.50 GiB used: 773.9 MiB (10.1%) 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
Observations:
--took about 90 secs to come to the desktop (not installed)
--no message about low battery (also installed)
--conky had black background (not installed)
--sound was turned off somewhere (not installed)

Here is last part of Xsession_errors running Live:

Code: Select all

Running default tint2rc
Error, .desktop file 'libreoffice-startcenter.desktop' does not exist.
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Error, .desktop file 'thunderbird.desktop' does not exist.
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

/usr/bin/mxfb-menu-generator
Please wait, creating menu file - stored in /home/demo/.fluxbox/submenus/full_menu ...

If you want to insert this All categories sub-menu into your MXFB menu:
rootMenu > Settings > Configure > Menu
and insert, anywhere you want, this code:
 [submenu] (All apps)
  [include] (~/.fluxbox/submenus/full_menu)
  [separator] 
  [exec] (Update Menu) {mxfb-menu-generator} 
 [end]

/home/demo/.fluxbox/startup: 75: /usr/lib/at-spi2-core/at-spi-bus-launcher: not found
mx-welcome version: 21.08mx21
conky: no process found
conky: desktop window (6a7) is root window
conky: window type - normal
conky: drawing to created window (0x3400002)
conky: drawing to double buffer

** (xfce4-clipman:4824): WARNING **: 17:06:44.160: Unable to register GApplication: An object is already exported for the interface org.gtk.Application at /org/xfce/clipman

(xfce4-clipman:4824): GLib-GIO-CRITICAL **: 17:06:44.160: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:4824): GLib-WARNING **: 17:06:44.160: g_set_application_name() called multiple times
Menu file created and ready to be used
Could not get bg groups from config file.
Keys: Invalid key/modifier on line 41): none F6 :Exec xfce4-appfinder
Keys: Invalid key/modifier on line 183): Mod1 KP_End    :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomLeft}
Keys: Invalid key/modifier on line 184): Mod1 KP_Down   :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Bottom}
Keys: Invalid key/modifier on line 185): Mod1 KP_Next   :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomRight}
Keys: Invalid key/modifier on line 186): Mod1 KP_Left   :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left}
Keys: Invalid key/modifier on line 187): Mod1 KP_Right  :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right}
Keys: Invalid key/modifier on line 188): Mod1 KP_Home   :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopLeft}
Keys: Invalid key/modifier on line 189): Mod1 KP_Up     :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Up}
Keys: Invalid key/modifier on line 190): Mod1 KP_Prior  :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopRight}
Keys: Invalid key/modifier on line 192): Mod1 KP_Begin  :MacroCmd {ResizeTo 70% 70% } {MoveTo 00 00 Center}
Keys: Invalid key/modifier on line 194): Mod1 KP_Insert :ToggleCmd {Maximize} {Restore}
Keys: Invalid key/modifier on line 202): Control 1 :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left} 
Keys: Invalid key/modifier on line 203): Control 2 :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right} 
Keys: Invalid key/modifier on line 204): Control 3 :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Up} 
Keys: Invalid key/modifier on line 205): Control 4 :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Bottom} 
Keys: Invalid key/modifier on line 207): Control 5 :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 Up} 
Keys: Invalid key/modifier on line 208): Control 6 :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 TopRight} 
Keys: Invalid key/modifier on line 209): Control 7 :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 BottomLeft} 
Keys: Invalid key/modifier on line 210): Control 8 :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 BottomRight} 
Keys: Invalid key/modifier on line 212): Control 9 :MacroCmd {ResizeTo 33% 100%} {MoveTo 00 00 Left}
Keys: Invalid key/modifier on line 214): Control 0 :ToggleCmd {Maximize} {Restore}
Keys: Invalid key/modifier on line 220): Mod1 Left        :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left}
Keys: Invalid key/modifier on line 221): Mod1 Right       :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right}
Keys: Invalid key/modifier on line 222): Mod1 Up          :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Up}
Keys: Invalid key/modifier on line 223): Mod1 Down        :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Bottom}
Keys: Invalid key/modifier on line 225): Mod1 Mod4 Left  :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopLeft}
Keys: Invalid key/modifier on line 226): Mod1 Mod4 Up    :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopRight}
Keys: Invalid key/modifier on line 227): Mod1 Mod4 Down  :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomLeft}
Keys: Invalid key/modifier on line 228): Mod1 Mod4 Right :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomRight}
Keys: Invalid key/modifier on line 244): Mod1 KP_1 :MacroCmd {ResizeTo  50%  50%} {MoveTo 00 00 BottomLeft}
Keys: Invalid key/modifier on line 245): Mod1 KP_2 :MacroCmd {ResizeTo 100%  50%} {MoveTo 00 00 Bottom}
Keys: Invalid key/modifier on line 246): Mod1 KP_3 :MacroCmd {ResizeTo  50%  50%} {MoveTo 00 00 BottomRight}
Keys: Invalid key/modifier on line 247): Mod1 KP_4 :MacroCmd {ResizeTo  50% 100%} {MoveTo 00 00 Left}
Keys: Invalid key/modifier on line 248): Mod1 KP_6 :MacroCmd {ResizeTo  50% 100%} {MoveTo 00 00 Right}
Keys: Invalid key/modifier on line 249): Mod1 KP_7 :MacroCmd {ResizeTo  50%  50%} {MoveTo 00 00 TopLeft}
Keys: Invalid key/modifier on line 250): Mod1 KP_8 :MacroCmd {ResizeTo 100%  50%} {MoveTo 00 00 Up}
Keys: Invalid key/modifier on line 251): Mod1 KP_9 :MacroCmd {ResizeTo  50%  50%} {MoveTo 00 00 TopRight}
Keys: Invalid key/modifier on line 253): Mod1 KP_5 :MacroCmd {ResizeTo 70% 70% } {MoveTo 00 00 Center}
Keys: Invalid key/modifier on line 255): Mod1 KP_0 :ToggleCmd {Maximize} {Restore}
Keys: Invalid key/modifier on line 260): Mod1 KP_End    :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomLeft}
Keys: Invalid key/modifier on line 261): Mod1 KP_Down   :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Bottom}
Keys: Invalid key/modifier on line 262): Mod1 KP_Next   :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 BottomRight}
Keys: Invalid key/modifier on line 263): Mod1 KP_Left   :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left}
Keys: Invalid key/modifier on line 264): Mod1 KP_Right  :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right}
Keys: Invalid key/modifier on line 265): Mod1 KP_Home   :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopLeft}
Keys: Invalid key/modifier on line 266): Mod1 KP_Up     :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Up}
Keys: Invalid key/modifier on line 267): Mod1 KP_Prior  :MacroCmd {ResizeTo 50% 50% } {MoveTo 00 00 TopRight}
Keys: Invalid key/modifier on line 269): Mod1 KP_Begin  :MacroCmd {ResizeTo 70% 70% } {MoveTo 00 00 Center}
Keys: Invalid key/modifier on line 271): Mod1 KP_Insert :ToggleCmd {Maximize} {Restore}

(nm-applet:4792): Gdk-CRITICAL **: 17:07:18.807: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(volumeicon:4823): Gdk-CRITICAL **: 17:07:18.826: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(xfce4-clipman:4824): Gdk-CRITICAL **: 17:07:18.871: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
mxfluxbox "MX-Fluxbox 3.0"
Didn't actually try the tiling keystrokes.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 7:03 pm
by Melber
Ran from Live USB.

- also took about 90 secs to come to the desktop
- message about low battery. Disappears when tint2 set to nobattery-tint2rc
- conky had black background

Congrats, the new & revised tools look a lot more intuitive and accessible for newcomers.

I seem to have a few hardware issues compared to my current install
- I can only select a maximum screen resolution of 1280x1024. (graphic card not supported by new nouveau driver?)
- CPU identified as single core instead of dual core
- Shutdown hangs and doesn't complete

QSI MX21 live USB

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: quiet splasht nosplash 
           Desktop: Fluxbox 1.3.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Portable System: Dell product: MXG061 v: N/A serial: <filter> Chassis: type: 8 
           serial: <filter> 
           Mobo: Dell model: 0CF456 serial: <filter> BIOS: Dell v: A07 date: 06/27/2007 
CPU:       Topology: Single Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: 6 microcode: D1 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 3990 
           Speed: 1995 MHz min/max: N/A Core speed (MHz): 1: 1995 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           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: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G71M [GeForce Go 7900 GTX] vendor: Dell driver: N/A bus ID: 01:00.0 
           chip ID: 10de:0299 
           Display: x11 server: X.Org 1.20.11 driver: nouveau,vesa unloaded: fbdev,modesetting 
           alternate: nv resolution: 1280x1024~N/A 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Broadcom and subsidiaries NetXtreme BCM5752 Gigabit Ethernet PCI Express 
           vendor: Dell driver: tg3 v: kernel port: ef00 bus ID: 09:00.0 chip ID: 14e4:1600 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: ef00 bus ID: 0c:00.0 chip ID: 8086:4222 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 140.44 GiB used: 1.35 GiB (1.0%) 
           ID-1: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: R013 
           scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade size: 28.65 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.49 GiB used: 21.1 MiB (0.8%) fs: overlay 
           source: ERR-102 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 61.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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 159 Uptime: 3m Memory: 3.16 GiB used: 706.7 MiB (21.8%) 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
For comparison, QSI current MX19.4 install

Code: Select all

Snapshot created on: 20210405_1332
System:    Host: <filter> Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-17-amd64 
           root=UUID=<filter> ro no quiet 
           Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo February 15  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Portable System: Dell product: MXG061 v: N/A serial: <filter> Chassis: type: 8 
           serial: <filter> 
           Mobo: Dell model: 0CF456 serial: <filter> BIOS: Dell v: A07 date: 06/27/2007 
Battery:   ID-1: BAT0 charge: 12.4 Wh condition: 12.4/79.9 Wh (16%) volts: 12.3/11.1 
           model: Sanyo DELL C54478 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: 6 microcode: D1 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 7979 
           Speed: 1347 MHz min/max: 1000/2000 MHz Core speeds (MHz): 1: 1467 2: 1445 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           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: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G71M [GeForce Go 7900 GTX] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0299 
           Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa 
           alternate: nv resolution: 1920x1200~60Hz 
           OpenGL: renderer: NV49 v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-17-amd64 
Network:   Device-1: Broadcom Limited NetXtreme BCM5752 Gigabit Ethernet PCI Express 
           vendor: Dell driver: tg3 v: 3.137 port: ef00 bus ID: 09:00.0 chip ID: 14e4:1600 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: ef00 bus ID: 0c:00.0 chip ID: 8086:4222 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 111.79 GiB used: 17.72 GiB (15.8%) 
           ID-1: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: R013 
           scheme: MBR 
Partition: ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) used: 13.31 GiB (45.3%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 52.5 C mobo: N/A gpu: nouveau temp: 49 C 
           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 buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 149 Uptime: 12m Memory: 3.18 GiB used: 727.6 MiB (22.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 7:11 pm
by Jerry3904
On the display, did you try using the Monitor icon (lxrandr) on Settings Manager?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 7:22 pm
by Melber
@Jerry3904
Yes, it only gave me the options auto (which did nothing) and 3 resolutions (1280x1024 and two lower ones)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 20, 2021 9:17 pm
by siamhie
Installed my rtl8814 drivers and connected to the 5G Netgear. Been playing around for about two hours and love the speed. Now I remember what I loved about Fluxbox in the first place.

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 
           init=/lib/systemd/systemd 
           Desktop: Fluxbox 1.3.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  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 [Legacy]: 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: 27930 
           Speed: 1394 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1392 
           2: 1395 3: 1396 4: 1394 
           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.10.0-8-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.10.0-8-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.82 TiB used: 4.93 GiB (0.3%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: A7L0 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: 461.62 GiB size: 453.30 GiB (98.20%) used: 4.73 GiB (1.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /home raw size: 461.62 GiB size: 453.30 GiB (98.20%) used: 207.3 MiB (0.0%) 
           fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 1.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
           GPU: device: radeon temp: 2 C device: radeon temp: 37 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 195 Uptime: 10m Memory: 14.60 GiB used: 825.8 MiB (5.5%) 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 beta 1 feedback thread.

Posted: Fri Aug 20, 2021 10:25 pm
by m_pav
Melber wrote: Fri Aug 20, 2021 7:03 pm I seem to have a few hardware issues compared to my current install
- I can only select a maximum screen resolution of 1280x1024. (graphic card not supported by new nouveau driver?)
- CPU identified as single core instead of dual core
- Shutdown hangs and doesn't complete
It may be that your machine has a similar issue to one of mine re: the shutdown.

Have a look at the file in /etc/modprobe.d/hang-on-shutdown.conf and you'll see it's fully commented out. If you've got any recent version of MX installed, check out the file on your own machine because it should be there. You only need to uncomment the last 2 lines in the file to try it, but one way or another, to test it, you'll have to boot either live or installed with the changed file.

Another thing to look at for such a system as yours is it may only be happy to run a 4.xx series kernel, which should be fully possible, though I have not tested on MX-21 yet.

You can either try an install if this is a spare machine, or you can try remastering the Live USB to incorporate a change to test. Remastering a single time is fully reversible, it can get trickier if you do it more than once. Let us know if you need help remastering the Live USB.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 12:01 am
by Adrian
Some packages that can be removed: exfat-fuse (it's now in kernel), gcc-9-base, gcc-10-base:i386 (in 64bit, and the rest of i386 stuff, do we need i386 for anything in 64bit?), mx19-archive-keyring.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 1:23 am
by wdscharff
After yesterday's announcement still quickly installed on the laptop, that the laptop does not accept every USB stick on every port as a boot device, has nothing to do with MX, he also did with opensuse and mint.
Laptop was still set to legacy, ran through without problems.

But it should be tested UEFI. This morning switched to UEFI (secure boot:off), disks on GPT with FAT32 ESP partition, the "rest" left unformatted.
And then times the first menu item taken, the system automatically set up (I have never done before). The only thing I had to do manually was to select as boot device and for Grub/ESP the NVME, because he wanted to take me every time the SSD. There probably everyone uses the same installer, somehow, opensuse and mint did the same :)

First impression: Great, super, impressive
Only the current RAM requirement with something around 750MB (the xfce beta is not better) is still suboptimal. I hope this will improve until the final release.

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.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A717-71G v: V1.10 serial: <filter> 
           Mobo: KBL model: Charizard_KLS v: V1.10 serial: <filter> UEFI: Insyde v: 1.10 
           date: 08/22/2017 
Battery:   ID-1: BAT1 charge: 45.1 Wh condition: 45.1/48.9 Wh (92%) volts: 15.9/15.2 
           model: COMPAL PABAS0241231 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake 
           family: 6 model-id: 9E (158) stepping: 9 microcode: EA L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19999 
           Speed: 2924 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 2396 2: 2308 3: 2338 
           4: 2391 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           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: disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 630 vendor: Acer Incorporated ALI driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:591b 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Acer Incorporated ALI 
           driver: N/A bus ID: 01:00.0 chip ID: 10de:1c8d 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel CM238 HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 chip ID: 8086:a171 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Lite-On 
           driver: ath10k_pci v: kernel port: 4000 bus ID: 02:00.0 chip ID: 168c:003e 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus ID: 03:00.1 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 484.44 GiB used: 4.36 GiB (0.9%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKW256G7 size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: PSF109C scheme: GPT 
           ID-2: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: MU01 
           scheme: GPT 
           ID-3: /dev/sdb type: USB vendor: SanDisk model: Cruzer size: 7.49 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 8.01 scheme: MBR 
Partition: ID-1: / raw size: 230.19 GiB size: 225.52 GiB (97.97%) used: 4.36 GiB (1.9%) fs: ext4 
           dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 43.5 C mobo: 29.8 C 
           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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 200 Uptime: 6m Memory: 7.66 GiB used: 742.7 MiB (9.5%) 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 

Der Bericht wurde in die Zwischenablage des Systems kopiert
Der Bericht ist bereits für das Forum formatiert.
Direkt in den Forumsbeitrag einfügen
Image
https://web57.ws/test/W-1_001.png

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:04 am
by chrispop99
Just to clarify - the low battery alert only appears with desktop machines. It does not happen with laptops.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:46 am
by kobaian
Tested on live USB.
1. Very impressive look at the first glance.
2. "Low-battery" alert on a desktop PC is a little bit annoying.
3. There's a bug in "nobattery-tint2rc" - no "exit-options", browser icon instead. Probably there is one "P" missing in the config file.
4. I like simplicity, but the screenshoter is too simple for me, and makes posting screenshots much more complicated.
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.
6. On Polish translation there's a bug in RootMenu - an empty entry without any text leading to MX-Fluxbox-Settings. I haven't seen the problem in English default version.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 5:42 am
by m_pav
Adrian wrote: Sat Aug 21, 2021 12:01 am Some packages that can be removed: exfat-fuse (it's now in kernel), gcc-9-base, gcc-10-base:i386 (in 64bit, and the rest of i386 stuff, do we need i386 for anything in 64bit?), mx19-archive-keyring.
Thanks Adrian, I've removed exfat-fuse and mx19-archive-keyring from the build package list.

As for the three i386 packages in the 64-bit build listed below, they are connected with our disk/partition encryption and earlier releases like MX-19_AHS have the same 3 Debian Buster equivalents of the i386 packages installed.

The i386 packages are not in any of the 64-bit package lists so they're automatically installed and I think removing them would break disk/partition encryption. When I tested this in a VM, apt gave me it's most dire warnings

Code: Select all

This should NOT be done unless you know exactly what you are doing

Code: Select all

You are about to do something potentially harmful
and would not proceed unless I typed the venerable

Code: Select all

Yes, do as I say!
When that message comes up, you can be sure something's going to break.

gcc-10-base:i386
libc6:i386
libgcc-s1:i386

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 6:45 am
by Jerry3904
chrispop99 wrote: Sat Aug 21, 2021 3:04 am Just to clarify - the low battery alert only appears with desktop machines. It does not happen with laptops.

Chris
Big clarification, thanks. That's on the top of my list for today.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:03 am
by Jerry3904
On the low battery message: this band-aid should work (on my laptop early in the morning, can't test).

1) open /.config/tint2/tint2rc in geany or featherpad
2) search for

Code: Select all

battery_low_cmd = xmessage 'tint2: Battery low!'
3) delete the message so it looks like this

Code: Select all

battery_low_cmd =
4) save and close

Still looking for the desktop low message problem itself...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:41 am
by Jerry3904
There's a bug in "nobattery-tint2rc" - no "exit-options", browser icon instead. Probably there is one "P" missing in the config file.
I'll have to wait to see if anyone else reports this b/c the icon link is correct and I've not had a problem on the various machines I've tested on so far.
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.
It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:48 am
by oops
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.

It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.
Maybe a link can be added into the "about-mx-fluxbox" item ?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:49 am
by Jerry3904
Back to the battery: I haven't found anything yet in a web search or looking at the man file.

I can't test, but can someone try filling the last two fields in the config file like this (this is a wild guess!):

Code: Select all

# Battery
battery_tooltip = 1
battery_low_status = 10
battery_low_cmd = xmessage 'tint2: Battery low!'
battery_full_cmd = 
bat1_font = Noto Sans Bold 12
bat2_font = Noto Sans 9.5
battery_font_color = #df3030 100
bat1_format = 
bat2_format = 
battery_padding = 1 9
battery_background_id = 3
battery_hide = 25
battery_lclick_command = 
battery_rclick_command = 
battery_mclick_command = 
battery_uwheel_command = 
battery_dwheel_command = 
ac_connected_cmd = battery_hide = 101
ac_disconnected_cmd = battery_hide = 25

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:51 am
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 7:03 am On the low battery message: this band-aid should work (on my laptop early in the morning, can't test).

1) open /.config/tint2/tint2rc in geany or featherpad
2) search for

Code: Select all

battery_low_cmd = xmessage 'tint2: Battery low!'
3) delete the message so it looks like this

Code: Select all

battery_low_cmd =
4) save and close

Still looking for the desktop low message problem itself...
I did the same thing using Tint2 Manager>Config!

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:01 am
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 7:41 am
There's a bug in "nobattery-tint2rc" - no "exit-options", browser icon instead. Probably there is one "P" missing in the config file.
I'll have to wait to see if anyone else reports this b/c the icon link is correct and I've not had a problem on the various machines I've tested on so far.
I can confirm the wrong icon shows. If you copy and paste the icon address from the config, or from the text file, into Thunar, it shows the correct logout icon - weird!

feh_070272_000001_210821_5321_305x137.png

Edit:

OK, I figured it out.
Button 3 is in the wrong place, and button 4 is missing.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:20 am
by Jerry3904
Thanks.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:39 am
by Jerry3904
oops wrote: Sat Aug 21, 2021 7:48 am
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.

It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.
Maybe a link can be added into the "about-mx-fluxbox" item ?
About Fluxbox has been replaced by the About tab in Welcome.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:41 am
by Jerry3904
chrispop99 wrote: Sat Aug 21, 2021 8:01 am Edit:

OK, I figured it out.
Button 3 is in the wrong place, and button 4 is missing.

Chris
Great, thanks.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:56 am
by dolphin_oracle
Jerry3904 wrote: Sat Aug 21, 2021 7:41 am
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.
It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.

Settings Manager would be more appropriate, as lightdm-gtk-settings is not a MX tool. That is also where it is under Xfce.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:08 am
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 7:49 am Back to the battery: I haven't found anything yet in a web search or looking at the man file.

I can't test, but can someone try filling the last two fields in the config file like this (this is a wild guess!):

Code: Select all

# Battery
battery_tooltip = 1
battery_low_status = 10
battery_low_cmd = xmessage 'tint2: Battery low!'
battery_full_cmd = 
bat1_font = Noto Sans Bold 12
bat2_font = Noto Sans 9.5
battery_font_color = #df3030 100
bat1_format = 
bat2_format = 
battery_padding = 1 9
battery_background_id = 3
battery_hide = 25
battery_lclick_command = 
battery_rclick_command = 
battery_mclick_command = 
battery_uwheel_command = 
battery_dwheel_command = 
ac_connected_cmd = battery_hide = 101
ac_disconnected_cmd = battery_hide = 25
Nope; didn't fix it.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:32 am
by Jerry3904
dolphin_oracle wrote: Sat Aug 21, 2021 8:56 am
Jerry3904 wrote: Sat Aug 21, 2021 7:41 am
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.
It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.

Settings Manager would be more appropriate, as lightdm-gtk-settings is not a MX tool. That is also where it is under Xfce.
Thanks. I installed it and ran a test: moved the login box to the screen bottom, rebooted but no change. Will pursue., worked fine.

BTW: @Adrian's custom toolbox is terrific--having the edit button right on the main screen saves a lot of time for everybody.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:34 am
by Jerry3904
chrispop99 wrote: Sat Aug 21, 2021 9:08 am
Jerry3904 wrote: Sat Aug 21, 2021 7:49 am Back to the battery: I haven't found anything yet in a web search or looking at the man file.

I can't test, but can someone try filling the last two fields in the config file like this (this is a wild guess!):

Code: Select all

# Battery
battery_tooltip = 1
battery_low_status = 10
battery_low_cmd = xmessage 'tint2: Battery low!'
battery_full_cmd = 
bat1_font = Noto Sans Bold 12
bat2_font = Noto Sans 9.5
battery_font_color = #df3030 100
bat1_format = 
bat2_format = 
battery_padding = 1 9
battery_background_id = 3
battery_hide = 25
battery_lclick_command = 
battery_rclick_command = 
battery_mclick_command = 
battery_uwheel_command = 
battery_dwheel_command = 
ac_connected_cmd = battery_hide = 101
ac_disconnected_cmd = battery_hide = 25
Nope; didn't fix it.

Chris
Thanks! I'm going to try putting a sed in there later today.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:43 am
by Jerry3904
I like simplicity, but the screenshoter is too simple for me, and makes posting screenshots much more complicated.
Thanks for the feedback. Mike and I discussed this too, not totally agreeing. My feeling is that the percentage of users wanting to make Forum posts is tiny, and they have the option of just installing xce4-screenshooter for advanced features. BTW: that's true of a lot of the software on this version: it's either missing alltogether (Libreoffice) or present in a simpler app (deadbeef instead of clementine).

Not written in stone, but Tenner's little app is superfast and easy--there is a right-click (feh) menu and a config file in ~/.config/MX-Linux.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:46 am
by i_ri
Hello dolphin_oracle
%y%m%d_%M%S and png and -s and -q given in config.

Code: Select all

scrot -s -q 80 /$HOME/Pictures/%y%m%d_%M%S.png -e 'feh $f' &exit
quality -q
png type reads 90-100 as 90, [9]; 80-89 as 80; 83=80; 75=70
jpg type reads actual number
mxfb-quickshot specifies png, so -quality to 80 brings smaller file size(?), than it is now set at 100 (read as png90) big file.

To exit quickshot before feh is quit
in /usr/bin/mxfb-quickshot Add one & at the end of the scrot command line that opens feh, add & to the end of the line (?25.) seems to change the behavior of the script. though i added &exit (a bit different behavior) just like the one line above, the one-line does not work with just &.
Without this the script will exit when feh is quit, as is this original status.

I just put shortcuts to mxfb-timer and mxfb-quickshot right into the main rootmenu.

no sound from beta on this machine, WallE, beta xfce live and installed. beta1_fluxbox live, no sound this machine; not at the installed point yet.
live works in other machines sound; WallE works sound with other systems.

Code: Select all

Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio 
  driver: snd_hda_intel 
  Sound Server: ALSA v: k5.10.0-8-amd64

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:01 am
by Jerry3904
FYI: right-click on the panel clock brings up the timer (left-click the calendar)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:07 am
by Jerry3904
Only the current RAM requirement with something around 750MB (the xfce beta is not better) is still suboptimal
@wdscharff : did you try disabling wmalauncher in startup, and then using a second tint2 panel as the dock? Somewhere Ceeslans showed there is a big difference.

On minimal: like MX Xfce since the beginning, MX-21 Fluxbox is conceived as a "midweight" Fluxbox version, meaning that we try to find a balance between lightness and ease of use.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:42 am
by Jerry3904
Battery again: please see if adding these commands to the last two lines of tint2rc and rebooting fixes the problem:

Code: Select all

ac_connected_cmd = {sed -i 's/25/101/' ~/.config/tint2/tint2rc}
ac_disconnected_cmd = {sed -i 's/101/25/' ~/.config/tint2/tint2rc}

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:51 am
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 10:42 am Battery again: please see if adding these commands to the last two lines of tint2rc and rebooting fixes the problem:

Code: Select all

ac_connected_cmd = {sed -i 's/25/101/' ~/.config/tint2/tint2rc}
ac_disconnected_cmd = {sed -i 's/101/25/' ~/.config/tint2/tint2rc}
Nope.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:58 am
by Jerry3904
The command is reversed but it definitely works. But that does not appear to be where the problem lies--stumped for now, leaving it alone.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:04 am
by oops
... Maybe this kind of cmd line works for both (laptop and desktop) ?

Code: Select all

battery_low_cmd = bash -c "[[ $(upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep 'power supply' | cut -d: -f2) == no ]] && { ;} || { notify-send 'battery low'; }"

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:14 am
by dolphin_oracle
oops wrote: Sat Aug 21, 2021 11:04 am ... Maybe this kind of cmd line works for both (laptop and desktop) ?

Code: Select all

battery_low_cmd = bash -c "[[ $(upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep 'power supply' | cut -d: -f2) == no ]] && { ;} || { notify-send 'battery low'; }"
not bad. does tint2 only issue the low battery warning once?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:18 am
by Jerry3904
The verbal notification is just triggered by tint2, I think notifyd is doing the actual work. That msg will show with every login I believe.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:18 am
by oops
@dolphin_oracle ... On desktop yes.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:20 am
by dolphin_oracle
so you won't get another notification later on? if so, doing the check before issuing the message seems ok.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:24 am
by Jerry3904
Missing a single check box "Disable when plugged in"

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:32 am
by chrispop99
oops wrote: Sat Aug 21, 2021 11:04 am ... Maybe this kind of cmd line works for both (laptop and desktop) ?

Code: Select all

battery_low_cmd = bash -c "[[ $(upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep 'power supply' | cut -d: -f2) == no ]] && { ;} || { notify-send 'battery low'; }"
It prevents the unwanted message on a desktop.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:39 am
by Jerry3904
@oops thanks for that!

I will run the beta with that to make sure that I still get low battery behavior: icon percentage shows up in red next to clock.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:43 am
by chrispop99
I realise this is personal choice, but it seems a bit odd to me to have a pretty decent music player, but nothing to play video.

On the basis of lightness, what about dropping DeadBeef (sorry Jerry), and including mpv, as it will play both audio and video files.?

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:45 am
by chrispop99
The desktop right-click menu contains an entry for Email, which does nothing.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:50 am
by Jerry3904
chrispop99 wrote: Sat Aug 21, 2021 11:43 am I realise this is personal choice, but it seems a bit odd to me to have a pretty decent music player, but nothing to play video.

On the basis of lightness, what about dropping DeadBeef (sorry Jerry), and including mpv, as it will play both audio and video files.?

Chris
We discussed this at some length, and I am still a fan of using Firefox which on this B1 is very fast and error free for the desktop videos link. Pretty stubborn here...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:54 am
by Jerry3904
I have created a vertical version of the default panel (though the battery fix is not there yet) that I would like people to take a look at if possible.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:55 am
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 11:50 am
chrispop99 wrote: Sat Aug 21, 2021 11:43 am I realise this is personal choice, but it seems a bit odd to me to have a pretty decent music player, but nothing to play video.

On the basis of lightness, what about dropping DeadBeef (sorry Jerry), and including mpv, as it will play both audio and video files.?

Chris
We discussed this at some length, and I am still a fan of using Firefox which on this B1 is very fast and error free for the desktop videos link. Pretty stubborn here...
Okey Dokey!

Perhaps some common video file types could be set to open FF by default to avoid user confusion?

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 12:09 pm
by oops
FI: Unfortunatly, the batterie test must be done also for BAT1, not only BAT0 (at least into my eepc)

Code: Select all

battery_low_cmd = bash -c "[[ $(upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep 'power supply' | cut -d: -f2) == no ]] && { ;} || { notify-send 'battery low'; }"

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 12:13 pm
by dreamer
The md5 hash value seems incorrect. Sha256 hash value seems correct.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 12:51 pm
by Jerry3904
@chrispop99 I think anything on the web should be handled automatically. If you feel like creating entries for downloaded vids for a couple of the most popular formats that we can insert into mimeapps.conf that would be great. I downloaded one of my videos and clicked to open with Firefox, and now this new line is in ~/config/mimeapps.conf:

Code: Select all

video/mp4=firefox.desktop;
I bet you could copy that a few times and just change the video format.
@oops Then I think we should create a small script "lobatcmd" and not clutter up the rc.
@dreamer I think that was reported earlier but will check, thanks.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 1:19 pm
by Jerry3904
There must be a way to combine these into a single command. This isn't sophisticated but it is shorter and I trust it will still work;

Code: Select all

#!/bin/bash

#This script corrects a bug that causes a low-battery notification to show on plugged-in machines 

FRONT="battery_low_cmd = bash -c "[[ $(upower -i /org/freedesktop/UPower/devices/battery"
BACK="| grep 'power supply' | cut -d: -f2) == no ]] && { ;} || { notify-send 'battery low'; }""

$FRONT BAT0 $BACK && $FRONT BAT1 $BACK

end

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 2:04 pm
by chrispop99
Jerry3904 wrote: Sat Aug 21, 2021 12:51 pm @chrispop99 I think anything on the web should be handled automatically. If you feel like creating entries for downloaded vids for a couple of the most popular formats that we can insert into mimeapps.conf that would be great. I downloaded one of my videos and clicked to open with Firefox, and now this new line is in ~/config/mimeapps.conf:

Code: Select all

video/mp4=firefox.desktop;
I bet you could copy that a few times and just change the video format.
I have a USB stick that holds audio, video, and document files in lots of different formats; I use it when distro testing.

Unfortunately, Firefox won't play .flv, .mpg, or .mkv files. It does play .mp4 and .mov. I didn't test any further.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 2:20 pm
by Jerry3904
Firefox won't play .flv, .mpg, or .mkv files.
How common are those?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 2:23 pm
by chrispop99
Would it be possible to tidy up the Common settings panel by capitalising 'mugshot' please? I'm a bit OCD!
feh_014290_000001_210821_1803_269x196.png

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 2:27 pm
by wdscharff
Jerry3904 wrote: Sat Aug 21, 2021 10:07 am ....did you try disabling wmalauncher in startup, and then using a second tint2 panel as the dock? Somewhere Ceeslans showed there is a big difference.

On minimal: like MX Xfce since the beginning, MX-21 Fluxbox is conceived as a "midweight" Fluxbox version, meaning that we try to find a balance between lightness and ease of use.
wmalauncher is not the main culprit, even if it looks like quite a resource hog.

Good news, bad news.

My startup taken over from 19.4, which is also arg optimized. There (19.4) I come to ~310mb after startup.

Bad news: In the 21.beta it is still around 810mb,
But now it comes: this is shown in Conky, in EVERY Conky script that shows the user ram usage (I tried them all)

good news: In the terminal, with free and htop and with LXTask (I like graphical task managers) I get 370-375MB.
This is more than the 19.4, but in relation to the offered nothing that I could further criticize.

not nice : The Conky displays incorrectly at my system

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 2:41 pm
by Jerry3904
Thanks for testing. I'll focus on the good news, since I have seen DO say that Bullseye runs heavier in the first place.

We'll look at the conkies later...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:25 pm
by wdscharff
The display regarding memory usage has become chaotic and incalculable anyway.
The XFCE task manager, Gnome System Monitor and the display of Neofetch are then again on the level of Conky. I already noticed this with the XFCE beta.
Maybe it only happens on my hardware, because I haven't seen anyone else report it.

Who measures much, measures crap (old proverb)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:30 pm
by dolphin_oracle
battery thing: on a desktop system, what's the output of

Code: Select all

acpi

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:32 pm
by Jerry3904
On my Lenovo:

Code: Select all

jb@mx:~
$ acpi
Battery 0: Discharging, 62%, 04:41:05 remaining

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:34 pm
by dolphin_oracle
Jerry3904 wrote: Sat Aug 21, 2021 3:32 pm On my Lenovo:

Code: Select all

jb@mx:~
$ acpi
Battery 0: Discharging, 62%, 04:41:05 remaining
that's not a desktop, but thanks. at least a battery is shown.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:38 pm
by chrispop99
dolphin_oracle wrote: Sat Aug 21, 2021 3:30 pm battery thing: on a desktop system, what's the output of

Code: Select all

acpi

Code: Select all

No support for device type: power_supply
Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:39 pm
by dolphin_oracle
chrispop99 wrote: Sat Aug 21, 2021 3:38 pm
dolphin_oracle wrote: Sat Aug 21, 2021 3:30 pm battery thing: on a desktop system, what's the output of

Code: Select all

acpi

Code: Select all

No support for device type: power_supply
Chris
thanks @chrispop99 . how about

Code: Select all

acpi 2>/dev/null

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:48 pm
by Jerry3904
dolphin_oracle wrote: Sat Aug 21, 2021 3:34 pm
Jerry3904 wrote: Sat Aug 21, 2021 3:32 pm On my Lenovo:

Code: Select all

jb@mx:~
$ acpi
Battery 0: Discharging, 62%, 04:41:05 remaining
that's not a desktop, but thanks. at least a battery is shown.
Jeesh, been going at this too long today...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:51 pm
by i_ri
hello dolphin_oracle
<xfdesktop4> and <xfdesktop4-data> are installed packages (?)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:54 pm
by chrispop99
dolphin_oracle wrote: Sat Aug 21, 2021 3:39 pm
thanks @chrispop99 . how about

Code: Select all

acpi 2>/dev/null
That doesn't return anything.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 3:56 pm
by i_ri
I get same as Chris on those acpi...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 5:23 pm
by oops
Me too , I get same as Chris on those acpi...

Code: Select all

$ acpi
No support for device type: power_supply
...
$ acpi 2>/dev/null
$

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 5:29 pm
by dolphin_oracle

Code: Select all

acpi 2>/dev/null && echo $?
Good. One more

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 5:30 pm
by oops

Code: Select all

$ acpi 2>/dev/null && echo $?
0

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 6:17 pm
by Melber
@m_pav I changed the boot parameters from the default quiet splasht nosplash to what I have in MX19 ro no quiet
Hey presto, start up time more than halved! Correct 1920x1200 screen resolution! Shutdown and reboot work without hanging!

@Jerry3904 Nice to see greyblue tint2, even if it's spelled wrong ;)
One very minor quibble, background 4 (the MX button) doesn't need a border because the MX icon you're using already has one.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 6:53 pm
by dolphin_oracle
so something like

Code: Select all

bash -c "[[ -z $(acpi 2>/dev/null) ]] && { ;} || { notify-send 'battery low'; }"

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 7:14 pm
by Jerry3904
Melber wrote: Sat Aug 21, 2021 6:17 pm @m_pav I changed the boot parameters from the default quiet splasht nosplash to what I have in MX19 ro no quiet
Hey presto, start up time more than halved! Correct 1920x1200 screen resolution! Shutdown and reboot work without hanging!

@Jerry3904 Nice to see greyblue tint2, even if it's spelled wrong ;)
One very minor quibble, background 4 (the MX button) doesn't need a border because the MX icon you're using already has one.
We'll be doing a complete review of the tint2s next week and I hope you'll join us

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:05 pm
by dolphin_oracle
@Melber can you try your system live just removing the splasht parameter?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 8:20 pm
by i_ri
hello dolphin_oracle and everyone
Jerry3904 and kobaian
The screencapture i reach for [launch] the most is a <scrot> one line gives cursor and saves automatically. just like quickshot, but why open feh?
Can do it one line <scrot> or <import> in MX. Two shots at a time with <import>!
The quick ones that give cursor need no translation.

A screenshot utility written for antiX specific,
is here bent into MX21_fluxbox specific.
full-featured when you want different than quickshot.
Was looking at the command line capacity of lazpaint to convert files; lazpaint is not in MX_fluxbox beta1, so using <convert>.

Font path for scrot "note" option can be configured at local user level after this screenshot utility is installed; the default path is strict.

/.fluxbox/apps yad control interacts with the yad windows of this screenshot utility. yad better for this without the /apps over-ride.
A lot of work went into the /apps file, but is left some cleaning out of missing software for /apps. For fbrun to work "nearmouse" i had to take it out of /apps. Synaptic dialogs big; removed Synaptic from /apps.

Sent the wrong file first time. user/.fonts if you have them.
Edit: use the second, with l1 name
This second one has common, I hope, font paths [to liberation] 8-|

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 9:00 pm
by m_pav
Melber wrote: Sat Aug 21, 2021 6:17 pm @m_pav I changed the boot parameters from the default quiet splasht nosplash to what I have in MX19 ro no quiet
Hey presto, start up time more than halved! Correct 1920x1200 screen resolution! Shutdown and reboot work without hanging!
The "no" in your startup line is not a recognised startup switch. I tested the altered startup on my VM with only "ro quiet" and there was no change whatsoever in the time it took from keypress to first sighting of the wallpaper, so this may be simply a solution that is particular to your hardware. Be interesting to see if others can report the same or similar things.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 10:25 pm
by Jerry3904
@i_ri Thanks for posting that. I'm not myself in any hurry to change, but will look carefully at your script if and when I am.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sat Aug 21, 2021 11:43 pm
by i_ri
hello dolphin_oracle
menus. /home/demo/.fluxbox/submenus
files /appearance, /full_menu,
Can have one more [end] Tag.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 5:01 am
by siamhie
chrispop99 wrote: Fri Aug 20, 2021 3:58 pm Every boot live and installed, on a 64-bit desktop machine, generates an xmessage;

Code: Select all

tint2:Battery low!
Chris
I finally found out what generates that message. If you edit your rc file in the .config/tint2/ folder, remove B from the "panel_items =" line. You won't get the message popup anymore.

Another way is to open the settings manager, tint2 manager, config, select your theme and click on the hamburger. Select Panel items and in the Elements selected section will show

Battery. Highlight it and move it over to the other side and select apply when done.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 6:15 am
by oops
dolphin_oracle wrote: Sat Aug 21, 2021 6:53 pm so something like

Code: Select all

bash -c "[[ -z $(acpi 2>/dev/null) ]] && { ;} || { notify-send 'battery low'; }"
... Yes, very good, probably the best solution.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 7:09 am
by chrispop99
siamhie wrote: Sun Aug 22, 2021 5:01 am
chrispop99 wrote: Fri Aug 20, 2021 3:58 pm Every boot live and installed, on a 64-bit desktop machine, generates an xmessage;

Code: Select all

tint2:Battery low!
Chris
I finally found out what generates that message. If you edit your rc file in the .config/tint2/ folder, remove B from the "panel_items =" line. You won't get the message popup anymore.

Another way is to open the settings manager, tint2 manager, config, select your theme and click on the hamburger. Select Panel items and in the Elements selected section will show

Battery. Highlight it and move it over to the other side and select apply when done.
Thanks, but the idea is to have a solution that works for laptops and desktops without the user changing anything.

Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 7:30 am
by Jerry3904
chrispop99 wrote: Sat Aug 21, 2021 11:45 am The desktop right-click menu contains an entry for Email, which does nothing.

Chris
Yeah, I was thinking it would be handy for the user but it needs to go.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 7:34 am
by Jerry3904
i_ri wrote: Sat Aug 21, 2021 3:51 pm hello dolphin_oracle
<xfdesktop4> and <xfdesktop4-data> are installed packages (?)
Thanks. I need to check whether they are needed by any of the other Xfce4 packages but it doesn't look like they should be included.

@m_pav I snooped around and can see no reason why these should be included--unless you know of some disaster that would result if we took them out!

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 8:48 am
by Jerry3904
oops wrote: Sun Aug 22, 2021 6:15 am
dolphin_oracle wrote: Sat Aug 21, 2021 6:53 pm so something like

Code: Select all

bash -c "[[ -z $(acpi 2>/dev/null) ]] && { ;} || { notify-send 'battery low'; }"
... Yes, very good, probably the best solution.
And the widget is working with that command in place, having just shown up on my laptop on the right side, just inside the clock. Tooltip gives a bit detail but we might improve or remove that.

I love this b/c it's out of the way until needed. Does 25% seem like a reasonable visibility?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 9:02 am
by oops
Jerry3904 wrote: Sun Aug 22, 2021 8:48 am ...
I love this b/c it's out of the way until needed. Does 25% seem like a reasonable visibility?
Me too, it's a solution "à la Fehlix" ... 25% is ok for me.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 11:39 am
by davemx
I didn't test this on the XFCE version, but, in the fluxbox version, when I ran MX Tools and selected alsamixer the F-keys were not captured by alsamixer and their global functions happened instead.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 11:41 am
by davemx
The problem mentioned by others regarding the "no battery" error on desktops, I found that by making alterations to tint2, it came up again. At one point I had the error message on screen in three different windows! It's definitely being prompted by something that comes up when you run tint2.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 12:07 pm
by Jerry3904
That's been solved now, thanks. The functions are set in the keys file where you can comment them out of you prefer.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 12:45 pm
by Jerry3904
Hmmm. My Android phone just notified me that my battery is down to 15% -- that kinda makes more sense...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 1:22 pm
by davemx
Jerry3904 wrote: Sun Aug 22, 2021 12:07 pm That's been solved now, thanks. The functions are set in the keys file where you can comment them out of you prefer.
The Alsamixer or the Battery problem?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 1:51 pm
by Jerry3904
Battery: look earlier in the thread.
Alsamixer: your option to comment out the Fn keys in the keys file.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 2:53 pm
by m_pav
Jerry3904 wrote: Sun Aug 22, 2021 7:34 am
i_ri wrote: Sat Aug 21, 2021 3:51 pm hello dolphin_oracle
<xfdesktop4> and <xfdesktop4-data> are installed packages (?)
@m_pav I snooped around and can see no reason why these should be included--unless you know of some disaster that would result if we took them out!
These packages are not in the package list so they get pulled in automatically. It's on my list of things to check but working for an essential services provider, I have to go to work for the primary reason that there always has to be 2 people there, can't think of any other useful reason for my presence.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 3:24 pm
by ceeslans
The problem with Conky reporting oversized-memory values only started occurring with conky version 1.11.6 ( --> which is exactly the version that ships with Debian bullseye and MX-Linux).
Meanwhile this has been corrected in conky version 1.12.2. However, this build has only reached Arch, Gentoo and Fedora repositories - but not Debian or any of its derivatives (afaik).
There are some workarounds (see Bunsenlabs forum post https://forums.bunsenlabs.org/viewtopic ... 88#p111888 back in March this year), or you could downgrade to the buster version 1.10.8, which also works perfectly in bullseye. But surely it is better to wait for the corrected version 1.12.2 to hit the MX (test?)repo.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 4:02 pm
by dolphin_oracle
ceeslans wrote: Sun Aug 22, 2021 3:24 pm The problem with Conky reporting oversized-memory values only started occurring with conky version 1.11.6 ( --> which is exactly the version that ships with Debian bullseye and MX-Linux).
Meanwhile this has been corrected in conky version 1.12.2. However, this build has only reached Arch, Gentoo and Fedora repositories - but not Debian or any of its derivatives (afaik).
There are some workarounds (see Bunsenlabs forum post https://forums.bunsenlabs.org/viewtopic ... 88#p111888 back in March this year), or you could downgrade to the buster version 1.10.8, which also works perfectly in bullseye. But surely it is better to wait for the corrected version 1.12.2 to hit the MX (test?)repo.
@Stevo what do you think?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 4:17 pm
by siamhie
If the panel is situated at the bottom, the tooltip shows up below the panel (when highlighting Network or Speaker icons). It's fine when the panel is on the sides or on top.

https://postimg.cc/r04fzsbn

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 4:23 pm
by i_ri
hello dolphin_oracle
"Alsamixer: your option to comment out the Fn keys in the keys file.", Jerry3904.
hello davemx
Having no sound on one machine brought me to the alsamixer window where i had the same unsettling experience with the function keys interfering with alsamixer controls.
Common advisement for choosing shortcut key assignments is to choose a key combination not already in use. in alsamixer i can use tab key for F3, F4, and F5 controls. F1 brings a help menu as promised. The escape key works. F2 and F6 is problematic.
So let's look at the keys file like Jerry3904 suggested.
F1 brings mxfb help. alsamixer is not in that help. If F1 is commented out in the keys file, then the F1 key still brings mxfb help. no help for alsamixer.
F2 is assigned to bring up fbrun box. Comment that out in the keys file and Alt+F2 can still bring the fbrun box. no loss of a keybind and it gives F2 control to alsamixer.
F6 in the keys file is assigned to two actions. well that is a mistake.
Comment out F6 key for xfce4 appfinder.
Comment out F6 key for mx manual 20200801.
Safe to say those are available elsewhere;
It gives alsamixer control of the F6 key.

Removing these conflicting, duplicated key assignments on F2 and F6 produces a healthier alsamixer experience. For Everyone.

gthumb has default shortcuts listed for F1, F2, F4, F5, F7, F9
can be user altered in gthumbPreferences, Shortcuts modification.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 4:35 pm
by Jerry3904
That keys file is due for revision since the function keys were assigned over two years ago at the very beginning of the MXFB project.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 4:38 pm
by Melber
dolphin_oracle wrote: Sat Aug 21, 2021 8:05 pm @Melber can you try your system live just removing the splasht parameter?
@dolphin_oracle
Live USB, boot with quiet nosplash. Correct 1920x1200 screen resolution. CPU correctly identified. Shutdown and restart work without hanging.

Out of curiosity, I tried quiet splasht nosplash again afterwards. Strangely this time the laptop booted with correct screen resolution. Previous attempts always resulted in 1280x1024. Perhaps the successful boots with ro no quiet and/or quiet nosplash set some variable or configuration file? Shutdown still hung and didn't complete.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 5:25 pm
by i_ri
hello dolphin_oracle
Tint2 default on using two display screens
tint2 taskbar on each, only one has systray,
show taskbar icons separate [several] each screen.
Is Amazing.
Good first impression on two monitors.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 5:27 pm
by Jerry3904
systray can only be on one tint2rc

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 6:01 pm
by i_ri
proves directly that it is pretty smart.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 6:03 pm
by fehlix
ceeslans wrote: Sun Aug 22, 2021 3:24 pm The problem with Conky reporting oversized-memory values only started occurring with conky version 1.11.6 ( --> which is exactly the version that ships with Debian bullseye and MX-Linux).
Meanwhile this has been corrected in conky version 1.12.2. However, this build has only reached Arch, Gentoo and Fedora repositories - but not Debian or any of its derivatives (afaik).
There are some workarounds (see Bunsenlabs forum post https://forums.bunsenlabs.org/viewtopic ... 88#p111888 back in March this year), or you could downgrade to the buster version 1.10.8, which also works perfectly in bullseye. But surely it is better to wait for the corrected version 1.12.2 to hit the MX (test?)repo.
Just tried conky 1.12.2 AppImage release, which comes with a ${legacymem} to show the "old" $mem, as mentioned by Mr. brndnmtthws here https://github.com/brndnmtthws/conky/is ... -826114532

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 22, 2021 9:06 pm
by BV206
Some of the Fluxbox tiling keys conflict with Thunar view keys.
For example Ctrl+3 in Thunar is supposed to change to compact view but Fluxbox tiles the window to the top of the screen.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 3:00 am
by wdscharff
Users should be made aware of the importance of the key file and what they can do with it.
Motivate a little :-)

My key file, for example, has hardly any similarities with the original file.
I don't think you can cover every single case. In PCManFM ctrl1 to ctrl4 are used to switch the folder view. The function keys are almost all commented out in my case, because otherwise some function keys won't work in applications and so on.

In Fluxbox the keyboard codes can be chained, so I put another ctrl C in front of ctrl[number] of the tiling function (I can remember ctrl C as "control command").
just a few more examples, I use it to call submenus from the root menu, or some stuff that was on the function keys before
ctrl c ctrl s :CustomMenu ~/.fluxbox/submenus/sidebar1
ctrl c ctrl f :CustomMenu ~/.fluxbox/submenus/favorites
ctrl c ctrl o :CustomMenu ~/.fluxbox/submenus/locations
ctrl c ctrl h : CustomMenu ~/.fluxbox/submenus/helpfiles
up to
Control c Control x :exec sudo poweroff

Doesn't have to make sense to others, but makes my daily work a lot easier. Others may have other ideas and solutions.
-------
A good documentation in the key file what is behind what would not be bad. A small start has been made, but for the beginner there are still some things missing:
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
##########
what about Mouse2, Mouse4 and Mouse5. Used that yes, why not explained. (rhetorical question, I read it all together in the original documentation when I switched to Fluxbox).
Either everything or nothing, otherwise a beginner is only confused ;-}

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 6:51 am
by Jerry3904
BV206 wrote: Sun Aug 22, 2021 9:06 pm Some of the Fluxbox tiling keys conflict with Thunar view keys.
For example Ctrl+3 in Thunar is supposed to change to compact view but Fluxbox tiles the window to the top of the screen.
Thanks. It is inevitable that any set of commands we create may conflict with one app or another's special keys. For that reason, there are actually 3 different tiling methods spelled out in the keys file:
-- Control + number keys
--Alt/Alt-LogoKey + arrow keys
--Alt and numpad keys (NumLock off or on)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 6:56 am
by Jerry3904
A good documentation in the key file what is behind what would not be bad. A small start has been made, but for the beginner there are still some things missing:
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
##########
what about Mouse2, Mouse4 and Mouse5. Used that yes, why not explained. (rhetorical question, I read it all together in the original documentation when I switched to Fluxbox).
Either everything or nothing, otherwise a beginner is only confused ;-}
The intent was to list out the most common, but it could easily be expanded. We now have a revision of the keys file on our beta to-do list, thanks.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 9:18 am
by ceeslans
Just noticed that MX21 is running fluxbox-1.3.5, whereas in MX19 we were (or at least I was...) running fluxbox-1.3.7.
Is there any reason why MXFluxbox is sticking to fluxbox-1.3.5 , instead of upgrading to the 1.3.7-1-antix1 version

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 9:39 am
by Jerry3904
No good reason that I know of besides the fact that no one noticed. @m_pav ?

Thanks!

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 10:33 am
by dolphin_oracle
what would be the compelling reason to bring in 1.3.7? IIRC, there is a right-click on the fluxbox taskbar issue that is broken in 1.3.7, unless its been fixed.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 3:13 pm
by Jerry3904
I have had trouble with wireless reconnecting after waking, logging in, etc. This is on my Lenovo laptop:

Code: Select all

$ inxi -n
Network:   Device-1: Intel Ethernet I219-V driver: e1000e 
           IF: eth0 state: down mac: xxxxxxxxxxxxx
           Device-2: Intel Wireless 8260 driver: iwlwifi 
           IF: wlan0 state: up mac: xxxxxxxxxx
I finally went into the Network Manager Connections, double-clicked my SSID, and on the General tab changed the priority to "1". That seems so far to have taken care of the problem, but I have never had to do that with this or any other machine so thought it might be worth a report.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 23, 2021 4:02 pm
by ceeslans
dolphin_oracle wrote: Mon Aug 23, 2021 10:33 am what would be the compelling reason to bring in 1.3.7? IIRC, there is a right-click on the fluxbox taskbar issue that is broken in 1.3.7, unless its been fixed.
I read about such issue in an earlier forum post, ie that the fluxbox [config] menu could not be activated by rightclick on the native fluxbox toolbar.
In today's MX-Fluxbox setup this [config] option is now accessible as a cascading menu in the 'settings' submenu. And moreover: now tint2 is the default toolbar in MX21.

I'm not questioning the functionality of the current mx-fluxbox version. But over a period of two years between versions, a number of minor/major bugs were fixed (see http://fluxbox.org/news/all.php). Maybe AntiX upgraded their fluxbox version to 1.3.7-1 for that same reason?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 24, 2021 1:12 am
by kobaian
Finally tested on metal.

1. Strange menu entry in menu-mx_pl

Code: Select all

...
    [exec] (Uruchom) {fbrun}
    [exec] () {custom-toolbox /etc/custom-toolbox/mxfb-settings.list}
    [exec] (Terminal) {roxterm} 
...

Image


There is no such an entry in the non-localized menu-mx.

2. Calendar Wars (YAD vs. gsimplecal).
Episode I: The Localization Strikes Back:


Image


YAD calendar - localized out of the box, gsimplecal only in English.

The old YADa Master says: Perhaps we don't need gsimplecal at all... ;)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 7:54 am
by wdscharff
This is more than strange and odd!
I use Drill for file search, it is significantly faster than Catfish.
There are two functions, right click on file and it is opened in the editor, right click on path and the default file manager is opened in the appropriate directory.

And now it no longer opens the path in the file manager but calls qmplay2, the music player.
When I uninstall it, it calls me the harddisk allocation (baobab) in the directory.

To top it all off, Catfish does it too.

Can someone verify/falsify this on their system.

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_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Gigabyte model: B550M S2H v: x.x serial: <filter> 
           BIOS: American Megatrends v: F3 date: 08/20/2020 
CPU:       Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 182066 
           Speed: 2200 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2190 
           2: 2196 3: 1995 4: 4100 5: 2196 6: 2189 7: 2191 8: 2192 9: 2190 10: 2195 11: 2195 
           12: 2195 13: 2190 14: 2195 15: 2422 16: 2146 17: 4269 18: 2195 19: 2195 20: 2199 
           21: 2196 22: 2197 23: 2196 24: 2205 
           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, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI driver: nouveau 
           v: kernel bus ID: 09:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: compton v: 1 resolution: 1920x1200~60Hz 
           OpenGL: renderer: NV137 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:0fb9 
           Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: f000 bus ID: 08:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.18 TiB used: 1.10 TiB (34.5%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/sda type: USB vendor: Samsung model: SSD 860 QVO 1TB size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0223 scheme: MBR 
           ID-3: /dev/sdb type: USB vendor: Samsung model: SSD 860 EVO 500G size: 465.76 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0223 scheme: MBR 
           ID-4: /dev/sdc vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
Partition: ID-1: / raw size: 120.32 GiB size: 117.87 GiB (97.97%) used: 18.89 GiB (16.0%) 
           fs: ext4 dev: /dev/sdc3 
           ID-2: swap-1 size: 2.44 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 56.8 C mobo: N/A gpu: nouveau temp: 16 C 
           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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 353 Uptime: 28m Memory: 31.34 GiB used: 3.29 GiB (10.5%) 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 beta 1 feedback thread.

Posted: Wed Aug 25, 2021 8:36 am
by Jerry3904
kobaian wrote: Tue Aug 24, 2021 1:12 am Finally tested on metal.

1. Strange menu entry in menu-mx_pl

Code: Select all

...
    [exec] (Uruchom) {fbrun}
    [exec] () {custom-toolbox /etc/custom-toolbox/mxfb-settings.list}
    [exec] (Terminal) {roxterm} 
...

Image


There is no such an entry in the non-localized menu-mx.

2. Calendar Wars (YAD vs. gsimplecal).
Episode I: The Localization Strikes Back:


Image


YAD calendar - localized out of the box, gsimplecal only in English.

The old YADa Master says: Perhaps we don't need gsimplecal at all... ;)
Thanks for looking at it installed.

1. temporary issue as translations are being updated
2. I had looked at that before but the dialog screen was always to big. No longer a problem now, and I think you're right. I found this command gets a decent look:

Code: Select all

yad --calendar --no-buttons --fixed --height 50

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 9:05 am
by fehlix
wdscharff wrote: Wed Aug 25, 2021 7:54 am This is more than strange and odd!
I use Drill for file search, it is significantly faster than Catfish.
There are two functions, right click on file and it is opened in the editor, right click on path and the default file manager is opened in the appropriate directory.

And now it no longer opens the path in the file manager but calls qmplay2, the music player.
When I uninstall it, it calls me the harddisk allocation (baobab) in the directory.

To top it all off, Catfish does it too.

Can someone verify/falsify this on their system.
Yes, it may be advisable to have a default application associated with mime-type "inode/directory", set for the user.
If no default application is set for this mimetype, any app opening inode/directory, would query the mime database , and would fallback to the first one found in one of the mimeinfo.cache files.
( The result may vary depending what applications have been installed / removed and in what order, which are registered to handel inode/directory's)
One way to set the default application of mime-type "inode/directory" on the command line shown by this examples:

set PCmanFM as filemanager for mime-type "inode/directory"

Code: Select all

xdg-mime default pcmanfm-qt.desktop inode/directory
set SpaceFM filemanager for mime-type "inode/directory"

Code: Select all

xdg-mime default spacefm.desktop    inode/directory
set Thunar filemanager for mime-type "inode/directory"

Code: Select all

xdg-mime default thunar.desktop     inode/directory
Alternatively one can use the file managers own way of setting a default app for this mime type:
E.g in Thunar right click on a folder ( = "inode/directory") and select PCmanFM
use-default-filemanager-thunar.png
or in PCmanFM and select PCmanFM
:
use-default-filemanager.png
and by this the selected the File manger becomes the default mimetype association for inode/directory.
:puppy:
[Klare Sache und damit hopp!]

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 9:06 am
by i_ri
hello dolphin_oracle
install saving changes
using the modified system to install a modified system /var/log is empty of a log of the changes. log starts empty fresh with the installation. Can the logs of changes in added packages be transferred to the installation along with save changes?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 9:19 am
by wdscharff
@fehlix
Alternatively one can use the file managers own way of setting a default app for this mime type:
E.g in Thunar right click on a folder ( = "inode/directory") and select PCmanFM
...
and by this the selected the File manger becomes the default mimetype association for inode/directory.
Thanks, Works :-)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 10:04 am
by wdscharff
And now 2 more problems with my niche applications.
I use fbmenugen https://github.com/trizen/fbmenugen because it also puts icons in the root menu, it's more convenient and faster than if I had to do it myself :)
There is a problem in the meantime, you need :
- libgtk2-perl -- v2.1
- libdata-dump-perl -- v1.23-1
- libfile-desktopentry-perl -- v0.22-1

Which were also installable via synaptic in Debian 10 without any problems.
But with Debian 11 I can't find "libgtk2-perl -- v2.1" anymore, and so there are no icons anymore. The "rest" still works.
But for a menu without icons the mxfb-menu-generator is sufficient.

And something else I didn't find in Synaptic for Debian 11 : Ufraw
For me it is only needed for a niche application, the display of Sony ARW files in PCManFM.
Since gThumb as default image viewer in Fluxbox displays the Sony RAWs without problems, this is also just a nice to have and not a must be.

Any suggestions for a solution

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 12:18 pm
by i_ri
hello dolphin_oracle
fluxbox
The only problem with 1.3.7 that bothers me is the Slit Client list blanking if a dockapp is set to not visible then the menu list blanks out half.
Take me back to 1.3.5.
August 19 ceeslans' screenshot shows a full Client list with some not visible. is that 1.3.5 or 1.3.7?
Stray for pinta; to reduce and convert this image.
Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 12:46 pm
by Jerry3904
I can not confirm that on my machine:
Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 12:52 pm
by i_ri
toggle one to not visible
by clicking on an entry in that Client list of menu

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 1:00 pm
by Jerry3904
OK, I see that behavior now. It seems likely to stem from the fact that these are not independent clients, but linked within a single script.

You may be the only user in 2 years who has used that part of the menu.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 1:12 pm
by i_ri
in my trials it is a 1.3.7 problem, not just for mx-dock. docks apps all. 1.3.7.
Thank you for finding it Jerry3904. (Last time you and dolphin said, How did 'e do that?)
I did wonder if this was the reason you went back to 1.3.5.
this answered that.
I was happy to see mx-fluxbox as 1.3.5; oh well. I'd prefer hidden problems over this in your face bug. 8-| tenner' birthday is shortly in September ..

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Aug 25, 2021 4:31 pm
by i_ri
menu-mx begin mx-fluxbox
I see a lot of begin Fluxbox in screencaptures (?)
begin wildflower

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 12:18 am
by trekolet
Greetings and congratulations to the collaborators.

I just installed MX Fluxbox. As the liveUSB works perfectly for me, I used unetbootin to install it as my main OS. When logging in, the fluxbox appears with factory settings, no conky, no tint, or desktop background, even the fluxbox menu is the default. I looked at the packages and it is installed mx-fluxbox and mxfb-goodies. I managed to get the MX 21 configuration running rofi and looking for the MX Fluxbox application.

Observations and corresponding changes to solve them in my environment:

When the volume indicator uses the OSD libnotify when changing the volume it gets slow (I am overpowered in hardware power). Changing the option to GTK + PopupWindow resolves.

The battery settings for the tint panels use xmessage which does not seem to integrate well with the desktop theme or fluxbox behavior. I changed it to notify-send and it works perfectly.

Client Side Decorations and the faded GTK scrollbars, both are active and personally I find them very annoying to use and break the aesthetics of the desktop. Both features can be disabled by editing the file ~ / .fluxbox / startup, locate the section where Qt variables are exported and followed by that block, place the following:

Code: Select all

#Disable gtk scrollbar auto-hide
export GTK_OVERLAY_SCROLLING=0
#Disable gtk CSD (Client Side Decorations)
export GTK_CSD=0
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0
The nocsd library was already installed in MX 21 Fluxbox, but it is not activated until those settings are loaded. I solved it this way because it didn't work for me to activate them from the .bashrc or .profile files. In addition, this configuration is linked to starting with fluxbox only.

Apart from the above, everything is going really well :)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 5:58 am
by m_pav
Why unetbootin and not our Live USB Maker? I suspect your lack of desktop customisations may have been a bad ISO, or a flaw generated by unetbootin.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 6:01 am
by kobaian
Bad news...
If I try to install nvidia proprietary drives, I get this:

Code: Select all

nvidia driver not available, check your repo sources

Code: Select all

Graphics:  Device-1: NVIDIA G92 [GeForce 9800 GT] driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:0614 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: compton v: 1 resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV92 v: 3.3 Mesa 20.3.5 direct render: Yes
With nouveau I've got problems with screen-tearing. I'm trying now to fix it using compton. It partially succeded, but the effect is still not so satisfactory as in MX19 with proprietary drives.

In MX19 only with KDE nouveau works well out of the box. In XFCE it is possible to deal with a problem changing some settings. Dealing with noveau and Fluxbox is a really hard job... Hopefully I will not have to move to KDE on my main machine and stay with MXFluxbox only on laptops... :frown:

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 6:25 am
by Jerry3904
kobaian wrote: Thu Aug 26, 2021 6:01 am Bad news...
If I try to install nvidia proprietary drives, I get this:

Code: Select all

nvidia driver not available, check your repo sources

Code: Select all

Graphics:  Device-1: NVIDIA G92 [GeForce 9800 GT] driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:0614 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: compton v: 1 resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV92 v: 3.3 Mesa 20.3.5 direct render: Yes
With nouveau I've got problems with screen-tearing. I'm trying now to fix it using compton. It partially succeded, but the effect is still not so satisfactory as in MX19 with proprietary drives.

In MX19 only with KDE nouveau works well out of the box. In XFCE it is possible to deal with a problem changing some settings. Dealing with noveau and Fluxbox is a really hard job... Hopefully I will not have to move to KDE on my main machine and stay with MXFluxbox only on laptops... :frown:
I suggest you post this also in the main mx-21 Xfce feedback thread, where the main nvidia Devs are more likely to see it. If you didn't do this already, you might search that feedback thread since I seem to remember seeing nvidia posts being made.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 6:33 am
by dolphin_oracle
kobaian wrote: Thu Aug 26, 2021 6:01 am Bad news...
If I try to install nvidia proprietary drives, I get this:

Code: Select all

nvidia driver not available, check your repo sources

Code: Select all

Graphics:  Device-1: NVIDIA G92 [GeForce 9800 GT] driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:0614 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: compton v: 1 resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV92 v: 3.3 Mesa 20.3.5 direct render: Yes
With nouveau I've got problems with screen-tearing. I'm trying now to fix it using compton. It partially succeded, but the effect is still not so satisfactory as in MX19 with proprietary drives.

In MX19 only with KDE nouveau works well out of the box. In XFCE it is possible to deal with a problem changing some settings. Dealing with noveau and Fluxbox is a really hard job... Hopefully I will not have to move to KDE on my main machine and stay with MXFluxbox only on laptops... :frown:
Can you post you /var/log/ddm.log file and the output of both

Code: Select all

nvidia-detect
And

Code: Select all

nvidia-detect-mx
After you do updates.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 7:02 am
by kobaian
dolphin_oracle wrote: Thu Aug 26, 2021 6:33 am Can you post you /var/log/ddm.log file and the output of both

Code: Select all

tworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/24/2021 07:25:16
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?
Ok...
Odświeżanie Źródeł z apt-get update
Instalowanie najnowszego pakietu nvidia-detect
Czytanie list pakietów...
Budowanie drzewa zależności...
Odczyt informacji o stanie...
nvidia-detect is already the newest version (460.91.03-1).
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 4 nieaktualizowanych.
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
Main repo candidate is:  
MX Test repo candidate is:  
Zainstalowany to:
Który sterownik chcesz zainstalować?

Główneg repozytoria lub MX Test

1: Główne

2: MX Test

3: Wyjście

Wpisz numer wyboru
Ok...
Kandydat to:
Zainstalowany to:
nvidia driver not available, check your repo sources


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/24/2021 13:27:29
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/24/2021 13:30:20
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?
Ok...
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
nvidia driver not available, check your repo sources


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/26/2021 11:33:56
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?
Ok...
Odświeżanie Źródeł z apt-get update
Instalowanie najnowszego pakietu nvidia-detect
Czytanie list pakietów...
Budowanie drzewa zależności...
Odczyt informacji o stanie...
nvidia-detect is already the newest version (460.91.03-1).
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 7 nieaktualizowanych.
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
Main repo candidate is:  
MX Test repo candidate is:  
Zainstalowany to:
Który sterownik chcesz zainstalować?

Główneg repozytoria lub MX Test

1: Główne

2: MX Test

3: Wyjście

Wpisz numer wyboru
Ok...
Kandydat to:
Zainstalowany to:
nvidia driver not available, check your repo sources


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/26/2021 12:42:05
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/26/2021 12:43:24
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?
Ok...
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
nvidia driver not available, check your repo sources


Naciśnij <Enter> aby wyjśćtworzenie blokady ...
===================================
Zainstaluj sterowniki dla: nvidia
Zacznij od (m/d/r): 08/26/2021 12:44:12
===================================

========================================
========================================

To restore open source drivers use:  
sudo ddm-mx -p nvidia

========================================
========================================

Odświeżanie Źródeł z apt-get update
Kandydat to:
Zainstalowany to:
Czy chcesz sprawdzić repozytorium MX Test w poszukiwaniu nowszej wersji?
Ok...
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
Kandydat to:
Zainstalowany to:
nvidia driver not available, check your repo sources


Naciśnij <Enter> aby wyjść
I'm affraid we've got the answer and is not optimistic for me:

Code: Select all

test@mxfb21:~
$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2)

Checking card:  NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)
Your card is only supported by the 340 legacy drivers series, which is only available up to buster.

Code: Select all

test@mxfb21:~
$ nvidia-detect-mx
Latest =  460.91.03
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2)

Checking card:  NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)
Uh oh. Your card is only supported by the 340 legacy drivers series, which is not in any current Debian suite.
So probably there are only two options for me: spending another day dealing with noveau and compton or buy a newer graphics...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 7:04 am
by dolphin_oracle
Yes. Although the ddm tool should have told you that. What version of ddm-mx do you have?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 7:22 am
by kobaian
dolphin_oracle wrote: Thu Aug 26, 2021 7:04 am Yes. Although the ddm tool should have told you that. What version of ddm-mx do you have?

Code: Select all

test@mxfb21:~
$ apt-cache policy ddm-mx
ddm-mx:
  Zainstalowana: 21.08.03mx21
  Kandydująca:   21.08.03mx21
  Tabela wersji:
 *** 21.08.03mx21 500
        500 http://ftp.icm.edu.pl/pub/Linux/dist/antix-workspace/mx/repo bullseye/main amd64 Packages
        500 http://ftp.icm.edu.pl/pub/Linux/dist/antix-workspace/mx/repo bullseye/main i386 Packages
        100 /var/lib/dpkg/status

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 8:24 am
by dolphin_oracle
kobaian wrote: Thu Aug 26, 2021 7:22 am
dolphin_oracle wrote: Thu Aug 26, 2021 7:04 am Yes. Although the ddm tool should have told you that. What version of ddm-mx do you have?

Code: Select all

test@mxfb21:~
$ apt-cache policy ddm-mx
ddm-mx:
  Zainstalowana: 21.08.03mx21
  Kandydująca:   21.08.03mx21
  Tabela wersji:
 *** 21.08.03mx21 500
        500 http://ftp.icm.edu.pl/pub/Linux/dist/antix-workspace/mx/repo bullseye/main amd64 Packages
        500 http://ftp.icm.edu.pl/pub/Linux/dist/antix-workspace/mx/repo bullseye/main i386 Packages
        100 /var/lib/dpkg/status
thanks. apparently the reporting in the tool needs some work.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 12:08 pm
by siamhie
There's two entries for Application Finder under All Apps>Accessories.

#1
[Desktop Entry]
Version=1.0
Exec=xfce4-appfinder
NoDisplay=false
Icon=mxfcelogo-rounded
StartupNotify=true
Terminal=false
Type=Application
Categories=Utility;X-XFCE;
Name=Application Finder

Comment[zh_TW]=尋找並啟動您系統上安裝的應用程式

#2
[Desktop Entry]
Version=1.0
Exec=xfce4-appfinder
Icon=org.xfce.appfinder
StartupNotify=true
Terminal=false
Type=Application
Categories=Utility;X-XFCE;
Name=Application Finder

Comment[zh_TW]=尋找並啟動您系統上安裝的應用程式
Keywords=program;applications;bookmarks;
Keywords[be]=праграма;праграмы;закладкі;
Keywords[bg]=програма;приложения, отметки;
Keywords[ca]=programar;aplicacions;marcadors;
etc, etc, etc....

I tried to remove the first entry manually from (.fluxbox/submenus/full_menu) but it comes back when you select update menu.

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 12:57 pm
by Jerry3904
That's because we created a second desktop file in order to get the tint2 panel to accept the config we wanted. Not sure that's still necessary, thanks, will take a look.

EDIT: nope, apparently not. I took it out and rebooted, and now there's only the one with the MX logo. Not totally sure what will happen with an upgrade, but I guess we'll find out.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 1:17 pm
by i_ri
so make good the double entry by making one of them show appfinder compact; add "-c" to one of the full menu entry commands(?)
(Application Finder ) { xfce4-appfinder }
(Application Finder ) { xfce4-appfinder -c}
the -c or --collapsed brings compact run mode of appfinder.
make good of the two entries. for now, customize it while it is there and excuse the double entry (?)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 1:18 pm
by Jerry3904
Worth considering, thanks. We have the native fbrun for that purpose already so not sure about doing that.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 1:24 pm
by i_ri
okay. i am just ready to see a good side. until there is just one entry, either leave it, delete it,
Or add -c seems fun. i am not suggesting permanence default. just make the most of what you got.

what if,
If it is some user's first experience adding a code option while experiencing the changed result, then you might create a coder for life from this first encounter with code.
Or make a mx-fluxbox user for life devotee. all from a lesson using a -c in rootmenu.
silly maybe, but you never know ..

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Aug 26, 2021 8:59 pm
by siamhie
All normal. Edited full_menu and renamed Update Menu to Reset Fluxbox Menu in menu-mx so I would stop resetting my menu. lol

[submenu] (Accessories)
#[exec] (Application Finder ) { xfce4-appfinder } Categories=Utility;X-XFCE;
[exec] (Application Finder ) { xfce4-appfinder } Categories=Utility;X-XFCE;

and menu-mx

[separator]
[exec] (Reset Fluxbox Menu) {/usr/bin/mxfb-menu-generator}

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 27, 2021 6:08 am
by Jerry3904
Could someone with a non-English install please post the contents of this config file:

~/.config/gsimplecal/config

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 27, 2021 8:22 am
by ceeslans
I just noticed following error message in ~/xsession-errors: WARNING: tempfile is deprecated; consider using mktemp instead.
I don't know when this started, whether it related to MXFB21 beta1, or MX21 beta1 - or a misconfiguration from my part...
When doing a web search, I stumbled upon a debian bugs paste dated Aug 18 2021, which reports on (or may be related to) this issue:
https://linux.debian.bugs.dist.narkive. ... s-xsession

Has anyone seen this error popping up and/or can comment on possible severity:

for good order sake, below is the latest xsession-errors contents:

Code: Select all

Xsession: X session started for one at Fri 27 Aug 2021 13:52:49 CEST
WARNING: tempfile is deprecated; consider using mktemp instead.
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/one/.Xauthority
localuser:one being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting USER=one
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/one
dbus-update-activation-environment: setting DESKTOP_SESSION=fluxbox
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-LYKz9EpeC3,guid=a3b6ca2b2ff5f2e741fb1f5c6128d211
dbus-update-activation-environment: setting LOGNAME=one
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=en_IE.utf8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_IE.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=fluxbox
dbus-update-activation-environment: setting XAUTHORITY=/home/one/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/one
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=fluxbox
dbus-update-activation-environment: setting NO_AT_BRIDGE=1
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/one
dbus-update-activation-environment: setting XDG_DATA_DIRS=/home/one/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
VirtualBox Additions disabled, not in a Virtual Machine
conky: desktop window (59b) is root window
conky: window type - desktop
conky: drawing to created window (0x1e00002)
conky: drawing to double buffer
conky: forked to background, pid is 10487
and my QSI

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 
  Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0 
  Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: Sony product: VPCF23P1E v: C609XFKA serial: <filter> Chassis: 
  type: 10 serial: <filter> 
  Mobo: Sony model: VAIO serial: <filter> BIOS: American Megatrends v: R2150V3 
  date: 07/22/2011 
Battery:
  ID-1: BAT0 charge: 22.2 Wh condition: 41.3/57.2 Wh (72%) volts: N/A/123.5 
  model: Sony Corp. type: Li-ion serial: N/A status: Charging 
CPU:
  Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP 
  arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
  L2 cache: 6144 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 35120 
  Speed: 902 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 868 2: 922 3: 886 4: 877 
  5: 999 6: 1053 7: 905 8: 823 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
  Type: l1tf mitigation: PTE Inversion 
  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 status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GF108M [GeForce GT 540M] vendor: Sony driver: nouveau v: kernel 
  bus ID: 01:00.0 chip ID: 10de:0df4 
  Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
  compositor: compton v: 1 resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVC1 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Sony 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
  Device-2: NVIDIA GF108 High Definition Audio vendor: Sony driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0bea 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter 
  vendor: Foxconn Unex DHXA-225 driver: ath9k v: kernel port: d000 bus ID: 02:00.0 
  chip ID: 168c:0032 
  IF: wlan0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Sony 
  driver: r8169 v: kernel port: 9000 bus ID: 05:00.0 chip ID: 10ec:8168 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 237.89 GiB used: 91.78 GiB (38.6%) 
  ID-1: /dev/sda vendor: Kingfast model: N/A size: 223.57 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 
  scheme: MBR 
  ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra size: 14.32 GiB block size: 
  physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition:
  ID-1: / raw size: 8.12 GiB size: 7.90 GiB (97.23%) used: 4.64 GiB (58.7%) fs: ext4 
  dev: /dev/sdb1 
  ID-2: /home raw size: 5.42 GiB size: 5.25 GiB (96.88%) used: 305.6 MiB (5.7%) 
  fs: ext4 dev: /dev/sdb3 
  ID-3: swap-1 size: 768.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
  cache pressure: 100 (default) dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A gpu: nouveau temp: 56 C 
  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
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 223 Uptime: 1h 50m Memory: 5.78 GiB used: 830.7 MiB (14.0%) 
  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 beta 1 feedback thread.

Posted: Fri Aug 27, 2021 9:03 am
by Jerry3904
I see it at the very beginning of MXFB21 B1 install

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 27, 2021 5:35 pm
by Melber
@Jerry3904
Jerry3904 wrote: Fri Aug 27, 2021 6:08 am Could someone with a non-English install please post the contents of this config file:

~/.config/gsimplecal/config
Not installed but live USB with persistence, language German

Code: Select all

    show_calendar = 1
              show_timezones = 0
              mark_today = 1
              show_week_numbers = 0
              close_on_unfocus = 0
              external_viewer = featherpad
              clock_format = %I:%M
              force_lang = en_US.utf8
              mainwindow_decorated = 1
              mainwindow_keep_above = 1
              mainwindow_sticky = 0
              mainwindow_skip_taskbar = 1
              mainwindow_resizable = 1
              mainwindow_position = center
              mainwindow_xoffset = 0
              mainwindow_yoffset = 0
              clock_label = MX-Fluxbox

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 27, 2021 5:48 pm
by Melber
A couple of obsevations:
  • In the Settings Manager app the settings themselves are translated but the window text (Common settings for MX Fluxbox) and the buttons about/help/edit/close are still in english.
  • Mugshot app opens xfce Terminal as well as mugshot itself.
  • Shutdown using tint2 button and logout popup works, shutdown via fluxbox menu hangs

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Fri Aug 27, 2021 6:18 pm
by Jerry3904
Thanks. I saw the Live situation here and am just waiting for an installed to confirm.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 12:02 pm
by siamhie
I've come across a couple of quirks. Nitrogen doesn't see the images in ~/.fluxbox/backgrounds but will if I add the directory (/home/siamhie/.fluxbox/backgrounds) in preferences. I've changed the default folder for saving Quickshot screenshots from Pictures to Downloads in mxfb-quickshot.conf. How do I stop it from creating a second image that gets saved to my home folder (name of image starts with feh_)?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 12:20 pm
by Jerry3904
On the Nitrogen problem: try $HOME/.fluxbox/backgrounds instead. I have a running list where the tilde doesn't work (mea culpa).

On the second image: I need to check the script on that behavior, thanks. I had never noticed it before.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 12:55 pm
by Jerry3904
On the second image: I only see a copy in /home if I right-click the image and save it. The image is automatically saved in whatever you have set as DESTDIR in the config file. I've been thinking of removing the feh command altogether.

On the Nitrogen: try replacing the content of the config file with this:

Code: Select all

[geometry]
posx=563
posy=90
sizex=946
sizey=861

[nitrogen]
view=icon
recurse=true
sort=ralpha
icon_caps=false
dirs=/usr/share/backgrounds;$HOME/.fluxbox/backgrounds;

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 1:28 pm
by dolphin_oracle
wallpaper entries under Appearance->Wallpapers

if a user uses "separate" to set wallpapers on individual workspaces, then later disabled, this message appears on logout/login.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 1:45 pm
by Jerry3904
Thanks. I've seen that and solved it, but forgot about it since.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 3:16 pm
by siamhie
Jerry3904 wrote: Sun Aug 29, 2021 12:20 pm On the Nitrogen problem: try $HOME/.fluxbox/backgrounds instead. I have a running list where the tilde doesn't work (mea culpa).

On the second image: I need to check the script on that behavior, thanks. I had never noticed it before.
Changing to the HOME variable didn't work either. The way I get it to work is to go to Appearance>Wallpaper>Select>Preferences and add my backgrounds folder. This could be handy because I have a folder of images on a second hard drive and I could just add that directory also if I wanted.

I just happened to notice my home folder was scrollable in Thunar and saw all these feh_ images. :laugh:

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 3:54 pm
by Jerry3904
dolphin_oracle wrote: Sun Aug 29, 2021 1:28 pm wallpaper entries under Appearance->Wallpapers

if a user uses "separate" to set wallpapers on individual workspaces, then later disabled, this message appears on logout/login.
OK, took me a while. I think that works as expected if the script changed these lines in startup:

Code: Select all

#start fehbg to get last background selected
#~/.fehbg
nitrogen --restore
to this:

Code: Select all

#start fehbg to get last background selected
~/.fehbg
#nitrogen --restore
If you or others can confirm this with manual change, then a pair of sed's should take care of it I imagine. Some wording changes would follow.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 4:03 pm
by i_ri
hello siamhie and Jerry3904
"name of image starts with feh_", siamhie.
"feh" in a filename indicates something wrong with the take_shot command in mxfb-quickshot.
Can you please share the content inside /usr/bin/mxfb-quickshot. The function take_shot () scrot command for comparison to the default script.


in your screenshot, it is small to see, cannot differ the characters a dash or equals, a bracket or paren., a zero or eight or B, and the m in date?

Is the "NAME" %y%m%d ? is that an m?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 4:38 pm
by dolphin_oracle
Jerry3904 wrote: Sun Aug 29, 2021 3:54 pm
dolphin_oracle wrote: Sun Aug 29, 2021 1:28 pm wallpaper entries under Appearance->Wallpapers

if a user uses "separate" to set wallpapers on individual workspaces, then later disabled, this message appears on logout/login.
OK, took me a while. I think that works as expected if the script changed these lines in startup:

Code: Select all

#start fehbg to get last background selected
#~/.fehbg
nitrogen --restore
to this:

Code: Select all

#start fehbg to get last background selected
~/.fehbg
#nitrogen --restore
If you or others can confirm this with manual change, then a pair of sed's should take care of it I imagine. Some wording changes would follow.
this is what my startup file looks like right now.

Code: Select all

#get last background selected
#~/.fehbg
nitrogen --restore
and the error messages is generated.

edit:: looks like this message might be generated by nitrogen itself. its looking for a wallpaper stored in the .fluxbox/lastwallpaper file, but that wallpaper doesn't exist after disabling the multi-workspace wallpaper setup via the "separate" script.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:22 pm
by Jerry3904
I'm not sure that's right. I believe that nitrogen is looking at this: /home/jb/.config/nitrogen/bg-saved.cfg whenever it starts up.

Your startup file is the default, and we would like to test the separate bg with the commenting reversed at the start. Nitrogen must be disabled, as the opening screen tells us to do, but I still needed to enable the fehbg in startup to get it to work. All tested on Live.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:24 pm
by dolphin_oracle
Jerry3904 wrote: Sun Aug 29, 2021 5:22 pm I'm not sure that's right. I believe that nitrogen is looking at this: /home/jb/.config/nitrogen/bg-saved.cfg whenever it starts up.

Your startup file is the default, and we would like to test the separate bg with the commenting reversed at the start. Nitrogen must be disabled, as the opening screen tells us to do, but I still needed to enable the fehbg in startup to get it to work. All tested on Live.
Look at my error report again. I disabled separate backgrounds via the separate backgrounds script. I want to set a wallpaper via nitrogen (and it is). but that lastwallpaer file is being sourced somewhere. enabling the seperate backgrounds worked OK.

what generates the .fluxbox/lastwallpaper file?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:35 pm
by Jerry3904
I think it's feh
man feh | grep fehbg
In many desktop environments, feh can also be used as a background setter. Unless you pass the --no-fehbg option,
it will write a script to set the current background to ~/.fehbg. So to have your background restored every time
you start X, you can add "~/.fehbg &" to your X startup script (such as ~/.xinitrc). Note that the commandline
written to ~/.fehbg always includes the --no-fehbg option to ensure that it is not inadvertently changed by differ‐
--no-fehbg

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:37 pm
by dolphin_oracle
well .fehbg was commented out, so something else is sourcing the file, but maybe using feh to set the background.

maybe its idesktop. I now have both the nitrogen and .fehbg lines commented out in the startup file, and I'm still getting the xmessage I screenshoted.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:41 pm
by Jerry3904
To fix a broken system I have gone to the end of the keys file and deleted the command that the separate bg script writes/erases in 82-84 and following:

Code: Select all

#Append the needed changes to the keys config file (the "\" is needed not to replace the variables:
      echo "#This executes fbsetbg every time workspace is changed to load <workspace number>.jpg from ~/.fluxbox/backgrounds/numbered/ 
ChangeWorkspace :Exec fbsetbg ~/.fluxbox/backgrounds/numbered/\$(xprop -root _NET_CURRENT_DESKTOP |awk '{print \$3+1}').jpg" >> ~/.fluxbox/keys

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 5:51 pm
by dolphin_oracle
this is the end of my keys file

Code: Select all

#---------------------------------------------------------------
#This executes fbsetbg every time workspace is changed to load <workspace number>.jpg from ~/.fluxbox/backgrounds/numbered/
I noticed that the rotate script uses idesktop. there are a lot of moving parts here.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 6:05 pm
by Jerry3904
Let me spell out how it has gone now twice running Live:

1) reverse the disable/enable for fehbg and nitrogen as I showed above
2) launch "separate" and follow the steps
a) when it is done scroll up or down to change workspace, and the separate backgrounds kicks in
b) checking the end of the keys file, the comment and command I quoted above have been written in
c) log out/in to check persistence

3) launch "separate" and click disable
a) the command has not been removed from the end of the keys file
b) log out/in and a common background is being used
c) no error messages

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 6:09 pm
by dolphin_oracle
Jerry3904 wrote: Sun Aug 29, 2021 6:05 pm Let me spell out how it has gone now twice running Live:

1) reverse the disable/enable for fehbg and nitrogen as I showed above
2) launch "separate" and follow the steps
a) when it is done scroll up or down to change workspace, and the separate backgrounds kicks in
b) checking the end of the keys file, the comment and command I quoted above have been written in
c) log out/in to check persistence

3) launch "separate" and click disable
a) the command has not been removed from the end of the keys file
b) log out/in and a common background is being used
c) no error messages
I have the common background, and the command in the keys file is gone, but I get the error message. I think its idesktop after using the rotate option.

edit:: well its not idesktop. I commented out idesktop and I still get the message.

am I supposed to have a command at the end of keys file by default or not?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 6:14 pm
by dolphin_oracle
ah, its fluxbox's init file. it runs fehbg seperately from the startup file.

Code: Select all

session.screen0.rootCommand:	~/.fehbg -l
and that -l loads from .fluxbox/lastwallpaper.

http://fluxbox.sourceforge.net/docbook/ ... ap-bg.html

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 6:30 pm
by i_ri
hello dolphin_oracle and Jerry3904
"what generates the .fluxbox/lastwallpaper"
a better question is where does lightdm get the bg? because lightdm hands off to feh(?)
[my workspace one bg shows in lightdm and it is not Honesty. early-bg calls for Honesty. (?)]
[backgrounds conky and idesk and Style need to be unset. (?) ]

Have you tried "&" after nitrogen or fehbg in the startup. ?
(these do not fit the description of keep running, but the & is everywhere i look, including man feh. )

Yes the init fehbg is there.
We can start nitrogen after starting fluxbox(?)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 6:36 pm
by siamhie
i_ri wrote: Sun Aug 29, 2021 4:03 pm hello siamhie and Jerry3904
"name of image starts with feh_", siamhie.
"feh" in a filename indicates something wrong with the take_shot command in mxfb-quickshot.
Can you please share the content inside /usr/bin/mxfb-quickshot. The function take_shot () scrot command for comparison to the default script.


in your screenshot, it is small to see, cannot differ the characters a dash or equals, a bracket or paren., a zero or eight or B, and the m in date?

Is the "NAME" %y%m%d ? is that an m?
Here's the contents of mxfb-quickshot

Image

and here's the mxfb-quickshot.conf (from my home folder)

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 10:27 pm
by i_ri
hello siamhie
Having done as You described: configure Downloads folder for destination,
I cannot get a file named feh.

I cannot find why feh might possibly be read as a filename or Pre
in your files look like mine. the part that is shown.

and
hello Jerry3904
You can imagine many ways to script three commands scrot, mv, feh.
You expressed a fondness for the tenr script
why not gthumb? instead of feh(?) or none.
plus you did not ask for input
but keeping close to the spirit of the script among the choices might I ask if siamhie can try a different command to see if it makes a difference? removing expansion of mv. +&.

Code: Select all

scrot ${OPTION} "${DESTDIR}/${PRE}${NAME}.${SUF}" -e 'feh --geometry 800x600 --scale-down '$DESTDIR/'$n' &

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Sun Aug 29, 2021 11:10 pm
by siamhie
i_ri wrote: Sun Aug 29, 2021 10:27 pm hello siamhie
Having done as You described: configure Downloads folder for destination,
I cannot get a file named feh.

I cannot find why feh might possibly be read as a filename or Pre
in your files look like mine. the part that is shown.
This is what's happening when I take a screenshot using the icon from the dock. On the left is my image saved to the default folder I set up (Downloads) and on the right is the same image duplicated in my home folder. I wanted to know how to stop quickshot from making the feh_ named image in my home folder.

One other thing. File sizes are different. Filename 210829_5447_1433x999 is 4.1MB and feh_065046_000001_210829_5447_1433x999 is 160KB.

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 9:31 am
by siamhie
Update to mxfb-quickshot creating two screenshot images (one in Downloads and the other in my Home folder). When I grab an active window or the desktop using the quickshot shortcut from the dock, feh opens with that preview. What I had been doing was to right click on feh's window and select save from the menu. That's where the second image is coming from. If I just close feh's window after grabbing the shot, I still have my image saved to Downloads but now I don't have an image in my home folder starting with feh_.

Is there a way I can tweak mxfb-quickshot so that it doesn't bring up feh's window in the first place. I really don't need a preview of my screen grab's.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 9:38 am
by dolphin_oracle
ah, I need to check I bet I have a bunch of duplicate shots too

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 10:46 am
by Jerry3904
This straw may break the camel's back...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 10:54 am
by siamhie
I was definitely having a PEBKAC moment. :laugh:

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 5:30 pm
by Jerry3904
It is certainly possible to run quickshot without the feh part. I'm thinking of popping up a dialog box instead saying it was saved to XX with a View button. But not right now... Here is the quickshot code without the feh component.

Code: Select all

#!/bin/bash 

## this app was developed by tenner and can be downloaded in its original at http://tenr.de/snippets/scripts/shot.sh
## it was modified for use with MX-Fluxbox and released October 2020 under GPLv3
## reworked by MX Devs for use of a config file April 2021

DESTDIR="${HOME}/Pictures"
NAME="`date +%y%m%d_%M%S_`\$wx\$h"

SUF="png"
PRE=""

if [ ! -f "$HOME/.config/MX-Linux/mxfb-quickshot.conf" ]; then 
cp /usr/share/mxfb-quickshot/mxfb-quickshot.conf $HOME/.config/MX-Linux/mxfb-quickshot.conf; 
fi

source ${HOME}/.config/MX-Linux/mxfb-quickshot.conf

display_help() {
	cat << EOF
	Usage: `basename "$0"` [-r/r/-w/w/-b/b] [-png|png|-jpg|jpg] 
EOF
}

take_shot() {
	scrot ${OPTION} "${PRE}${NAME}.${SUF}" -e 'mv $f '$DESTDIR' '
}

if [ $# -gt 2 ]
then
	display_help
	exit 1
elif [ $# -eq 0 ]
then
	take_shot
	exit 0
else
	case "$1" in
		-r|r|-R|-r|root|Root|-root|-Root)
			OPTION=""
			;;		
		-w|w|-W|-W|window|Window|-window|-Window)
			OPTION="-s"
			#PRE="part_"
			;;
		-b|b|-B|-B|border|Border)
			OPTION="-sb"
			#PRE="part_"
			;;		
		*)
			display_help
			exit 1
	esac

	case "$2" in
		jpg|JPG|-jpg|-JPG)
			SUF="jpg"
			;;	
		png|PNG|-png|-PNG)
			SUF="png"
			;;
		*)
			display_help
			exit 1
	esac
	take_shot
	exit 0
fi

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Mon Aug 30, 2021 6:16 pm
by siamhie
Jerry3904 wrote: Mon Aug 30, 2021 5:30 pm It is certainly possible to run quickshot without the feh part. I'm thinking of popping up a dialog box instead saying it was saved to XX with a View button. But not right now... Here is the quickshot code without the feh component.

Code: Select all

#!/bin/bash 

## this app was developed by tenner and can be downloaded in its original at http://tenr.de/snippets/scripts/shot.sh
## it was modified for use with MX-Fluxbox and released October 2020 under GPLv3
## reworked by MX Devs for use of a config file April 2021

DESTDIR="${HOME}/Pictures"
NAME="`date +%y%m%d_%M%S_`\$wx\$h"

SUF="png"
PRE=""

if [ ! -f "$HOME/.config/MX-Linux/mxfb-quickshot.conf" ]; then 
cp /usr/share/mxfb-quickshot/mxfb-quickshot.conf $HOME/.config/MX-Linux/mxfb-quickshot.conf; 
fi

source ${HOME}/.config/MX-Linux/mxfb-quickshot.conf

display_help() {
	cat << EOF
	Usage: `basename "$0"` [-r/r/-w/w/-b/b] [-png|png|-jpg|jpg] 
EOF
}

take_shot() {
	scrot ${OPTION} "${PRE}${NAME}.${SUF}" -e 'mv $f '$DESTDIR' '
}

if [ $# -gt 2 ]
then
	display_help
	exit 1
elif [ $# -eq 0 ]
then
	take_shot
	exit 0
else
	case "$1" in
		-r|r|-R|-r|root|Root|-root|-Root)
			OPTION=""
			;;		
		-w|w|-W|-W|window|Window|-window|-Window)
			OPTION="-s"
			#PRE="part_"
			;;
		-b|b|-B|-B|border|Border)
			OPTION="-sb"
			#PRE="part_"
			;;		
		*)
			display_help
			exit 1
	esac

	case "$2" in
		jpg|JPG|-jpg|-JPG)
			SUF="jpg"
			;;	
		png|PNG|-png|-PNG)
			SUF="png"
			;;
		*)
			display_help
			exit 1
	esac
	take_shot
	exit 0
fi
Thank you so much. It's perfect.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 8:29 am
by chrispop99
On a machine with a graphics resolution of 1280x800, 'Common Settings' cuts off the icons on the right hand side.
feh_042904_000001_210831_2022_1105x708.jpg
Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 8:32 am
by Jerry3904
What happens if you readjust the window size >> narrower? Adrian's new build should rescale I think.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 8:50 am
by chrispop99
Jerry3904 wrote: Tue Aug 31, 2021 8:32 am What happens if you readjust the window size >> narrower? Adrian's new build should rescale I think.
At different window sizes the icons may fit properly; at intermediate positions, for example when going from 2 icons across to 3 icons across, the truncation occurs. At the resolution of this particular machine, that truncation happens when the window is maximised.


Chris

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 9:18 am
by Senpai
Hello:
I'm a little late and I don't know if this is already reported?
I was finally able to install MX21 Fluxbox on my test laptop.
In the usblive I could remove the desktop wallpaper and leave it with nothing, or change to another image, but in the MX installed from the Desktop app, it does not change to any wallpaper, nor do I see a way to leave it without any...
The beta is installed and updated as of today.
Here the information of the laptop.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-686-pae i686 bits: 32 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-686-pae 
           root=UUID=<filter> ro quiet splash 
           Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_386 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Other-vm? System: Acer product: Aspire 5715Z v: V1.45 serial: <filter> 
           Mobo: Acer model: Acadia v: V1.45 serial: <filter> BIOS: Acer v: 1.45 
           date: 11/10/2008 
Battery:   ID-1: BAT0 charge: 38.1 Wh condition: 38.1/48.8 Wh (78%) volts: 12.5/11.1 
           model: SANYO GC86508SAT0 type: Li-ion serial: N/A status: Full 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M215 2nd Gen 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: Dual Core model: Intel Pentium Dual T2370 bits: 64 type: MCP 
           arch: Core Merom family: 6 model-id: F (15) stepping: D (13) microcode: A4 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6915 
           Speed: 1452 MHz min/max: 800/1733 MHz Core speeds (MHz): 1: 1362 2: 1357 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           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: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Acer Incorporated ALI 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1280x800~60Hz 
           OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 82801H HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:284b 
           Sound Server: ALSA v: k5.10.0-8-686-pae 
Network:   Device-1: Broadcom and subsidiaries NetLink BCM5906M Fast Ethernet PCI Express 
           vendor: Acer Incorporated ALI driver: tg3 v: kernel port: 5000 bus ID: 05:00.0 
           chip ID: 14e4:1713 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter 
           vendor: AMBIT Microsystem AR5BXB63 802.11bg NIC driver: ath5k v: kernel port: 5000 
           bus ID: 06:00.0 chip ID: 168c:001c 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 4.95 GiB (1.1%) 
           ID-1: /dev/sda vendor: Hitachi model: HTS547550A9E384 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: A60A scheme: MBR 
Partition: ID-1: / raw size: 60.00 GiB size: 58.76 GiB (97.93%) used: 4.89 GiB (8.3%) fs: ext4 
           dev: /dev/sda3 
           ID-2: swap-1 size: 4.00 GiB used: 62.4 MiB (1.5%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 65.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://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 192 Uptime: 2h 11m Memory: 1.96 GiB used: 1.20 GiB (61.1%) 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
EDITED:
I also set the Desktop app to change wallpaper every 1 minute randomly, and nothing happens....
EDITED:
Changing the desktop wallpaper only works from "Right-click->Appearance->Wallpaper...".

Best regards

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 10:04 am
by siamhie
There are two entries in the sub menu Settings that do nothing. Window Manager and Window Manager Tweaks. Looking at full_menu they point to xfwm4-settings and xfwm4-tweaks-settings. When run from a terminal, I get this.

siamhie@mxflux:/usr/bin
$ xfwm4-settings
These settings cannot work with your current window manager (Fluxbox)
siamhie@mxflux:/usr/bin
$ xfwm4-tweaks-settings
These settings cannot work with your current window manager (Fluxbox)
siamhie@mxflux:/usr/bin
$

I suspect they are a holdover from the Xfce/Fluxbox installation? Will I need these two entries in the future or can I just remove them from full_menu?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 10:31 am
by Jerry3904
I'm not sure how they get in, but I'm unable to remove them either in a terminal or in Synaptic.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:22 am
by siamhie
Jerry3904 wrote: Tue Aug 31, 2021 10:31 am I'm not sure how they get in, but I'm unable to remove them either in a terminal or in Synaptic.
I can remove them from the full_menu file. Do I need them in the future?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:24 am
by dolphin_oracle
siamhie wrote: Tue Aug 31, 2021 11:22 am
Jerry3904 wrote: Tue Aug 31, 2021 10:31 am I'm not sure how they get in, but I'm unable to remove them either in a terminal or in Synaptic.
I can remove them from the full_menu file. Do I need them in the future?
is xfwm4 installed?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:34 am
by dolphin_oracle
ah, I see xfwm4 is installed on the beta 1 iso. it shouldn't be and can be removed. @m_pav @Jerry3904

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:40 am
by siamhie
dolphin_oracle wrote: Tue Aug 31, 2021 11:24 am
siamhie wrote: Tue Aug 31, 2021 11:22 am
Jerry3904 wrote: Tue Aug 31, 2021 10:31 am I'm not sure how they get in, but I'm unable to remove them either in a terminal or in Synaptic.
I can remove them from the full_menu file. Do I need them in the future?
is xfwm4 installed?
Yes. xfwm4-workspace-settings works, just not xfwm4-settings or xfwm4-tweaks-settings.

siamhie@mxflux:~
$ ls -l /usr/bin/xfwm4*
-rwxr-xr-x 1 root root 412168 Jan 10 2021 /usr/bin/xfwm4
-rwxr-xr-x 1 root root 113024 Jan 10 2021 /usr/bin/xfwm4-settings
-rwxr-xr-x 1 root root 84352 Jan 10 2021 /usr/bin/xfwm4-tweaks-settings
-rwxr-xr-x 1 root root 145856 Jan 10 2021 /usr/bin/xfwm4-workspace-settings
siamhie@mxflux:~
$

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:40 am
by Jerry3904
OK, not sure why it is there at all...

thanks to both, we'll get it out

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:44 am
by siamhie
dolphin_oracle wrote: Tue Aug 31, 2021 11:34 am ah, I see xfwm4 is installed on the beta 1 iso. it shouldn't be and can be removed. @m_pav @Jerry3904
Will it be removed from the final release and those corresponding entries?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 11:45 am
by dolphin_oracle
siamhie wrote: Tue Aug 31, 2021 11:44 am
dolphin_oracle wrote: Tue Aug 31, 2021 11:34 am ah, I see xfwm4 is installed on the beta 1 iso. it shouldn't be and can be removed. @m_pav @Jerry3904
Will it be removed from the final release and those corresponding entries?
it will be removed for the final iso yes. its not going to be removed automatically from any existing systems.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 12:13 pm
by siamhie
dolphin_oracle wrote: Tue Aug 31, 2021 11:45 am
siamhie wrote: Tue Aug 31, 2021 11:44 am
dolphin_oracle wrote: Tue Aug 31, 2021 11:34 am ah, I see xfwm4 is installed on the beta 1 iso. it shouldn't be and can be removed. @m_pav @Jerry3904
Will it be removed from the final release and those corresponding entries?
it will be removed for the final iso yes. its not going to be removed automatically from any existing systems.
I plan on re-installing Fluxbox once the final release is out. I've replaced my SATA hard drive with an SSD and setup a separate root and home partition for the MX21 release.

I've gone ahead and removed these entries from full_menu.

[exec] (Window Manager Tweaks ) { xfwm4-tweaks-settings } Categories=XFCE;GTK;Settings;DesktopSettings;X-XFCE-SettingsDialog;X-XFCE-PersonalSettings;
[exec] (Window Manager ) { xfwm4-settings } Categories=XFCE;GTK;Settings;DesktopSettings;X-XFCE-SettingsDialog;X-XFCE-PersonalSettings;
[exec] (Workspaces ) { xfwm4-workspace-settings } Categories=XFCE;GTK;Settings;DesktopSettings;X-XFCE-SettingsDialog;X-XFCE-PersonalSettings;

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 12:42 pm
by Jerry3904
That menu is generated by a script so as long as the applications themselves still are installed they will reappear wherever the menu is refreshed. Same for Appfinder.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Tue Aug 31, 2021 4:12 pm
by siamhie
Jerry3904 wrote: Tue Aug 31, 2021 12:42 pm That menu is generated by a script so as long as the applications themselves still are installed they will reappear wherever the menu is refreshed. Same for Appfinder.
True, if you select Update Menu. If you select Update Menu, your customized menu (any changes you've made to menu-mx and/or any of the files in the submenus folder) gets reset back to the default menu by the command /usr/bin/mxfb-menu-generator.

I still have the apps installed but they no longer appear in my menu. (any changes you make to the files mentioned above are updated right away-no need for refreshing/restarting)

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 2:32 am
by gsm
Kernel 5.10.0-8-amd64 is used in the live system and in the installed system. However Debian 64 bit (4.19) is greyed, as if it was installed, according to the popular packages list of the MX package installer.
I have trouble on my HP mini 110 netbook with kernel version 5.10 (no internet), disconnecting or no wifi connections and would like to use 4.19 or 4.9. Version 4.19 however can't be downloaded and reinstalled.
The horizontal task bar is hiding part of the windows used for installation of the system on the small screen of the HP mini 110, but one can use the Alt key to shift the windows a little when required.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 3:40 am
by kobaian
Because of abandoning legacy drivers by nVidia, I was forced to use compton to get rid off screen tearing. The effect is acceptable, although still a little bit worse than in MX19. No screen-tearing, rather smooth movement of windows, but there's a little strange behavior of Thunar and terminals (both Rox and XFCE). Their borders became about 50% transparent and there is a "flashlight effect" while launching and closing, like there was a white background beneath that launches a couple of milliseconds before the content of the window is painted. All the rest of apps, no matter if gtk or qt launch and close smoothly.

Because compton adds a real transparency, and there is only a pseudo-transparency in Fluxbox by default, after login the behavior of some windows and apps change. A problem appears with compton and idesk icons, because of the order of launching apps in the default startup: compton > idesk > nitrogen wallpaper (as far as I remember). So if you change the wallpaper you've got a glitch after login, idesk icons are painted on the lightdm wallpaper that still appears on the transparent part of the icons. I had to change the standard setup to get rid off this. First off all I've moved all the commands rather to the end of the startup, and changed the order to: nitrogen restore > idesk > compton and added a sleep command before those two last.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 5:12 am
by kobaian
I had a problem to start the fluxbox session today. After a quick research I noticed, there was a "#" before every "$HOME" variable in the startup file. So the startup was broken. I didn't have put this sign manually. The only thing I could have done is removing dock using "Disable default dock" from menu... So check out if this command work properly to you.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 5:40 am
by Jerry3904
Will check, thanks for the report.
First off all I've moved all the commands rather to the end of the startup, and changed the order to: nitrogen restore > idesk > compton and added a sleep command before those two last.
I've never used compton in my entire MX life, so hope someone who knows something about this can comment.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 6:11 am
by kobaian
I have confirmed my suspicions. After clicking the menu entry "Disable default dock" every

Code: Select all

$HOME
entry turns to

Code: Select all

#$HOME
in ~/.fluxbox/startup .

So you've got not only

Code: Select all

#$HOME/.fluxbox/scripts/DefaultDock.mxdk
but also:

Code: Select all

#$HOME/.fluxbox/scripts/conkystart
or:

Code: Select all

# mx-welcome if configured to autostart
if [ -e #$HOME/.config/autostart/mx-welcome.desktop ]; then
# launch mx-welcome
(sleep 5; /usr/bin/mx-welcome) &
fi
that breaks the startup file and the Fluxbox session does not load at all.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 6:56 am
by dolphin_oracle
kobaian wrote: Wed Sep 01, 2021 6:11 am I have confirmed my suspicions. After clicking the menu entry "Disable default dock" every

Code: Select all

$HOME
entry turns to

Code: Select all

#$HOME
in ~/.fluxbox/startup .

So you've got not only

Code: Select all

#$HOME/.fluxbox/scripts/DefaultDock.mxdk
but also:

Code: Select all

#$HOME/.fluxbox/scripts/conkystart
or:

Code: Select all

# mx-welcome if configured to autostart
if [ -e #$HOME/.config/autostart/mx-welcome.desktop ]; then
# launch mx-welcome
(sleep 5; /usr/bin/mx-welcome) &
fi
that breaks the startup file and the Fluxbox session does not load at all.
confirmed, good catch.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 6:57 am
by Jerry3904
Thanks for checking again.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 7:12 am
by dolphin_oracle
changed code for $HOME/.fluxbox/scripts/dfltdck_kill here:

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 7:28 am
by Jerry3904
mercy buttercups

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 2:02 pm
by Senpai
Trying the right-click menu entries on the screen:

Between "Run" and "Terminal" there is an empty space, if you press it it launches the "Settings manager", the name is missing to see it and be able to translate it.

I have seen a typo in my Spanish translation, is this menu uploaded to Transifex?

In All App->Accessories (full_menu):
"App Finder" entry is duplicated.
"compton" does nothing and does not show any error, from console it says that it is already running.

In All App->System
Ndivia driver installer, does not work, from MX tools, it works.
MX fix keys, the entry is duplicated and does nothing, from MX tools, it works.

All App->Settings:
Window manager settings, it does nothing...
Window manager, does nothing...

Greetings

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 4:31 pm
by siamhie
This quirk is driving me crazy and I can't figure it out. I'm running tint2rc as my panel (situated at the bottom of screen) and when I mouse over either the network or speaker icons the tool-tip is below the panel. Now if I load spacedout-tint2rc (also situated at the bottom) the tool-tip appears above the panel. I've gone through the wiki (https://mxlinux.org/wiki/applications/tint2-panel/) with no luck.

How do I get the tool-tip for the network and speaker icons to show above the panel in tint2rc?

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 5:10 pm
by kobaian
siamhie wrote: Wed Sep 01, 2021 4:31 pm How do I get the tool-tip for the network and speaker icons to show above the panel in tint2rc?
As far as I remember it is a problem of the system tray and appears not only with tint2 but also with XFCE panel and others. Appearing tooltips over or under the panel depends on the icon size. You have to try to change it and look if the problem is still there.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 5:37 pm
by siamhie
kobaian wrote: Wed Sep 01, 2021 5:10 pm
siamhie wrote: Wed Sep 01, 2021 4:31 pm How do I get the tool-tip for the network and speaker icons to show above the panel in tint2rc?
As far as I remember it is a problem of the system tray and appears not only with tint2 but also with XFCE panel and others. Appearing tooltips over or under the panel depends on the icon size. You have to try to change it and look if the problem is still there.
Thanks. I'll look into what spacedout-tint2rc icon size is for the sys tray.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 6:05 pm
by Jerry3904
I think if you increase panel size a bit it will change that behavior, but can't remember very well either.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 6:21 pm
by kobaian
It depends rather on if the icons in system tray are much smaller than the panel size or not. That's why in most of the cases you'll have to choose between smaller, but good-looking icons and the tool-tip out of the screen or ugly icons, that are as big as the rest of the panel icons, but tool-tips over the panel. The space-out panel is specific, very thin, all things on it are separated, so the tray looks ok. But on normal panel one rather expects the tray icons to be a little bit smaller than the rest and that's the source of the problem.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 7:56 pm
by siamhie
Figured it out after looking through all the options of spacedout-tint2rc. I then tested it with another panel (nobattery-tint2rc) that defaults to the bottom where the tool-tip shows up below the panel and it worked there also. You don't have to change any icon size.

Settings manager>Tint2 manager>Config>'select the panel your using' and click on the icon in the upper left corner (Edit the selected theme). From there go to Panel>Window manager interaction>Maximized windows and change that selection to Fill the screen.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Wed Sep 01, 2021 8:38 pm
by Jerry3904
Thanks. We'll look at revising those during the Beta2 review coming up.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 1:16 am
by kobaian
siamhie wrote: Wed Sep 01, 2021 7:56 pm Figured it out after looking through all the options of spacedout-tint2rc. I then tested it with another panel (nobattery-tint2rc) that defaults to the bottom where the tool-tip shows up below the panel and it worked there also. You don't have to change any icon size.

Settings manager>Tint2 manager>Config>'select the panel your using' and click on the icon in the upper left corner (Edit the selected theme). From there go to Panel>Window manager interaction>Maximized windows and change that selection to Fill the screen.
But that's not a good solution for the default panel, because it means you've got the maximized window below the panel. So if there's a status bar or another content on the bottom of the maximized window you won't see it...

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 8:41 am
by siamhie
kobaian wrote: Thu Sep 02, 2021 1:16 am
siamhie wrote: Wed Sep 01, 2021 7:56 pm Figured it out after looking through all the options of spacedout-tint2rc. I then tested it with another panel (nobattery-tint2rc) that defaults to the bottom where the tool-tip shows up below the panel and it worked there also. You don't have to change any icon size.

Settings manager>Tint2 manager>Config>'select the panel your using' and click on the icon in the upper left corner (Edit the selected theme). From there go to Panel>Window manager interaction>Maximized windows and change that selection to Fill the screen.
But that's not a good solution for the default panel, because it means you've got the maximized window below the panel. So if there's a status bar or another content on the bottom of the maximized window you won't see it...
That depends on your panel options. I have mine set to Top which keeps the panel on top of any window that tries to overlay it.

Image

The other setting you can choose (that keeps the tool-tip above the panel) is Match the hidden panel size.

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 12:28 pm
by kobaian
siamhie wrote: Thu Sep 02, 2021 8:41 am That depends on your panel options. I have mine set to Top which keeps the panel on top of any window that tries to overlay it.
Ok. Open Featherpad, maximize it and tell me is it comfortable now to use the search-bar behind the panel?
Maybe for you it is better to make the search-bar in maximized Featherpad unusable to make visible the descriptions of the tray icons, you already know what they stand for, but I'm afraid it is rather not the case for an average user. That's why I think it could work for you, but it is not good as the default setting for the default panel.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 2:51 pm
by siamhie
kobaian wrote: Thu Sep 02, 2021 12:28 pm
siamhie wrote: Thu Sep 02, 2021 8:41 am That depends on your panel options. I have mine set to Top which keeps the panel on top of any window that tries to overlay it.
Ok. Open Featherpad, maximize it and tell me is it comfortable now to use the search-bar behind the panel?
Maybe for you it is better to make the search-bar in maximized Featherpad unusable to make visible the descriptions of the tray icons, you already know what they stand for, but I'm afraid it is rather not the case for an average user. That's why I think it could work for you, but it is not good as the default setting for the default panel.
You can set your Panel layer to 'Bottom' so that any maximized window covers the panel while keeping the 'Maximized windows' option at either Match the hidden panel or Fill the screen. That way the tool-tips window for the Network and Speaker icons still show on top of the panel and not below it.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 3:21 pm
by kobaian
siamhie wrote: Thu Sep 02, 2021 2:51 pm
kobaian wrote: Thu Sep 02, 2021 12:28 pm
siamhie wrote: Thu Sep 02, 2021 8:41 am That depends on your panel options. I have mine set to Top which keeps the panel on top of any window that tries to overlay it.
Ok. Open Featherpad, maximize it and tell me is it comfortable now to use the search-bar behind the panel?
Maybe for you it is better to make the search-bar in maximized Featherpad unusable to make visible the descriptions of the tray icons, you already know what they stand for, but I'm afraid it is rather not the case for an average user. That's why I think it could work for you, but it is not good as the default setting for the default panel.
You can set your Panel layer to 'Bottom' so that any maximized window covers the panel while keeping the 'Maximized windows' option at either Match the hidden panel or Fill the screen. That way the tool-tips window for the Network and Speaker icons still show on top of the panel and not below it.
Your solution is like treating a small annoyance with a greater one. Giving up a normal panel with windows opening above, because you cannot see the description of the volume icon... Sorry, I can't understand your point of view.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 4:50 pm
by siamhie
kobaian wrote: Thu Sep 02, 2021 3:21 pm
Your solution is like treating a small annoyance with a greater one. Giving up a normal panel with windows opening above, because you cannot see the description of the volume icon... Sorry, I can't understand your point of view.
All the other panel icons (App finder, taskbar icons, Synaptic, time/cal, exit options) tool-tips pop up, why not also the network and speaker.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 5:10 pm
by Jerry3904
We're packaging Beta 2 right now, so let's reopen this topic in the new feedback thread. I haven't even had a chance to look at the problem.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 5:17 pm
by kobaian
siamhie wrote: Thu Sep 02, 2021 4:50 pm
kobaian wrote: Thu Sep 02, 2021 3:21 pm
Your solution is like treating a small annoyance with a greater one. Giving up a normal panel with windows opening above, because you cannot see the description of the volume icon... Sorry, I can't understand your point of view.
All the other panel icons (App finder, taskbar icons, Synaptic, time/cal, exit options) tool-tips pop up, why not also the network and speaker.
Changing the icon size to:

Code: Select all

systray_icon_size = 36
solves the problem without implying that the part of the maximized window is hidden behind the panel or the opposite. But then this icons seem to me really large, bigger than the launchers on the left side.

Image

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 5:34 pm
by kobaian
Jerry3904 wrote: Thu Sep 02, 2021 5:10 pm We're packaging Beta 2 right now, so let's reopen this topic in the new feedback thread. I haven't even had a chance to look at the problem.
Ok. As I said before it could be easily solved by enlarging icons to 36. Then perhaps the launchers icons should be also a little bit enlarged to preserve the natural look and feel of the panel.

Re: MX-21 fluxbox beta 1 feedback thread.

Posted: Thu Sep 02, 2021 5:45 pm
by Jerry3904
Thanks.

The Beta 2 is now in process, so I will close this thread. Thanks to all.
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited