Page 3 of 46

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 2:50 pm
by 8bit
anticapitalista wrote: Sun May 28, 2023 11:14 am
Why don't you tell us exactly why our installer is confusing...?
The drive selection is not the easiest to figure out. Many people I've helped have stumbled here.
I find it wonderfully geeky.

viewtopic.php?p=697539#p697539

Please use those images and text in any way that helps.

8bit

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 4:21 pm
by Jerry3904
Fluxbox: we've lost the MX-Comfort theme as default for the monitors (gkrellm) again. Don't think I changed anything, but I'll go back and look.

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 4:35 pm
by cmoswizard
Failure to boot on old Core 2 quad Q9000 in HP HDX18 laptop.
Boots to Grub menu and then:
Repeating message:
......Watchdog: BUG: Soft lockup - CPU#2 stuck for -- seconds ........
MX 21 worked.
Debian based Q4OS 5 using kernel 6.1 gives the same error.
Tested with Endeavour on kernel 6.2.2 and boots ok so probably a kernel 6.1 or Debian bug for this system.
FYI.

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 4:35 pm
by FullScale4Me
MX Fluxbox 23 Beta1 Virtual Box 800x600 - an attempt to replicate an older laptop.

MX Tweek
when launched has multiple areas where items are fully cut-off (1st 2 items in left column) or partially displayed (including Apply button)
Image

MX Updater
In toolbar has the (red) "pulse" as its icon. The next two dialogs of update notification and applying updates has the (green) "wireframe" icon. (consistency)

Samba sharing
Samba is installed by default and set to autostart. I created a Samba share and attempted to connect to it. Below is the resulting error.

Code: Select all

mike@optiplex7050:~
$ smbclient -L 192.168.x.xxx
do_connect: Connection to 192.168.x.xxx failed (Error NT_STATUS_IO_TIMEOUT)
In investigating I found that the User Fire Wall aka UFW was set ON but no Samba rule was configured. Once the pre-configured Samba rule was searched for ("samba") and added the connection then worked fine.

QSI

Code: Select all

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

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 5:06 pm
by Jerry3904
800x600 resolution, huh? Did you try rootMenu > Display to make adjustments? If you try and it works better, click the Disply > Help to see how to make it permanent.
MX Updater
In toolbar has the (red) "pulse" as its icon. The next two dialogs of update notification and applying updates has the (green) "wireframe" icon. (consistency)
That is hard for me to understand: it is pulse white/red by default. If you log out/in is the pulse restored?

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 5:20 pm
by fehlix
FullScale4Me wrote: Sun May 28, 2023 4:35 pm MX Fluxbox 23 Beta1 Virtual Box 800x600 - an attempt to replicate an older laptop.
MX Updater
In toolbar has the (red) "pulse" as its icon. The next two dialogs of update notification and applying updates has the (green) "wireframe" icon. (consistency)
Yes, that's by design. Changing the tray-icon e.g. within MX-Updater preferences would only change the icon shown within the tray, not with in any other places like menu, notification popup or in any dialog-window.
This is not related to MX Fluxbox but works with Xfce and KDE the same.

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 5:21 pm
by FullScale4Me
Jerry3904 wrote: Sun May 28, 2023 5:06 pm 800x600 resolution, huh? Did you try rootMenu > Display to make adjustments? If you try and it works better, click the Display > Help to see how to make it permanent.
MX Updater
In toolbar has the (red) "pulse" as its icon. The next two dialogs of update notification and applying updates has the (green) "wireframe" icon. (consistency)
That is hard for me to understand: it is pulse white/red by default. If you log out/in is the pulse restored?
MX Tweak - My intent was to replicate the very first laptops had two resolutions: 640x480 and 800x600. I understand your point.

MX Updater When the system checks for updates at the end of the check a small pop-up "You have Updates" - it has a green "wireframe" icon not the red "pulse".

You click to apply updates.

The apply updates box comes up (the one with the check boxes) and it also has the green "wireframe" icon.

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 5:23 pm
by Jerry3904
So you're talking about a couple of window icons -- got it.

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 6:17 pm
by FullScale4Me
MX KDE 23 Beta1

Samba sharing
Samba is installed by default and set to autostart. In Dolphin I created a Samba share and failed in my attempt to connect to it. Below is the resulting error in terminal.

Code: Select all

mike@optiplex7050:~
$ smbclient -L 192.168.x.xxx
do_connect: Connection to 192.168.x.xxx failed (Error NT_STATUS_IO_TIMEOUT)
In investigating I found that the KDE Firewall was set Firewall status (check) Enabled but no Samba rule was configured.

I clicked "Add Rule..." The pre-configured Samba rule was searched for ("samba") and before clicking "create" I changed the "Policy" to "Allow". Clicking "Create" the firewall applet gave an red error bar ("!Please restart plasma firewall, the backend disconnected."). I "X'd out" of this "Create" dialog and no rule was added. Se below.

Image

Help button results in "Documentation not Found" displayed. I cleared the Enable check box in the Firewall applet and was able to connect to the share.

The UFW GUI applet is not present, only this KDE one.

I was able to install the "gufw" applet via MXPI. With the firewall enabled, samba rule in place I can successfully connect to the share from another PC.

Image

QSI

Code: Select all

System:
  Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64
    root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.2 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta1_x64 Libretto
    May 28 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required>
    Chassis: Oracle Corporation type: 1 serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> UEFI: innotek GmbH
    v: VirtualBox date: 12/01/2006
CPU:
  Info: model: Intel Core i7-7700 bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v2
    built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9 microcode: N/A
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 3600 min/max: N/A cores: 1: 3600 2: 3600 bogomips: 14399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT Host state unknown
  Type: retbleed status: Vulnerable
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Unknown: Dependent on hypervisor status
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter vendor: VMware
    driver: vboxvideo v: kernel ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 80ee:beef
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: kwin_x11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa alternate: vboxvideo dri: swrast gpu: vboxvideo display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 97 s-size: 269x202mm (10.59x7.95") s-diag: 336mm (13.24")
  Monitor-1: VGA-1 model: VBOX monitor serial: <filter> built: 1990 res: 1024x768 hz: 60
    gamma: 1.2 size: N/A modes: max: 800x600 min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0
    chip-ID: 8086:2415 class-ID: 0401
  API: ALSA v: k6.1.0-9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: c1a0 bus-ID: 00:03.0
    chip-ID: 8086:100e class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
    modules: i2c_piix4 port: N/A bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives:
  Local Storage: total: 26 GiB used: 9.82 GiB (37.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 26 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 1.0 scheme: GPT
Partition:
  ID-1: / raw-size: 25.74 GiB size: 25.17 GiB (97.78%) used: 9.82 GiB (39.0%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2401 libs: 1319 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
    2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Info:
  Processes: 169 Uptime: 35m wakeups: 610 Memory: 3.81 GiB used: 1.36 GiB (35.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Re: MX-23 beta 1 feedback thread

Posted: Sun May 28, 2023 6:20 pm
by kobaian
MXFB-Font does not work well. Selecting font for GTK does not work at all, for Fluxbox it is impossible to change the font to any non-regular style (bold, italic etc.) Are you sure this is the last version of the script from pre-Beta? (BTW - The "about" button with some information about the version of the app will be helpful.)