MX-23 beta 2 feedback thread

[Melber]

Just for info
I found a bug in mxfb-look where conky isn't being reset correctly.
Think I see the small code change it needs, will check tonight.

[operadude]

@pbear: I was trying to use copy-paste for posting my QSI, but Firefox would crash before I could even get logged-in to the Forum! If No Firefox -> No Paste!

Open QSI in guest VM. Click button: Copy for Forum. Switch to host system. Open thread using Firefox (or other browser) in the host system. Paste from clipboard.

Ahhh....So Simple!
Once you know what to do!
(Didn't think that I could switch back & forth just from the clipboard)

Will Try.
Thanks!

[operadude]

Thanks @pbear !
Here's my QSI from my VB instance:

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: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15  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> BIOS: innotek GmbH
    v: VirtualBox date: 12/01/2006
CPU:
  Info: model: Intel Core i3-7100 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: 6 MiB desc: 2x3 MiB
  Speed (MHz): avg: 3912 min/max: N/A cores: 1: 3912 2: 3912 bogomips: 15648
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities: <filter>
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 compositor: xfwm v: 4.18.0 driver: X: loaded: vmware
    unloaded: fbdev,modesetting,vesa dri: vmwgfx gpu: vmwgfx display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1002 s-dpi: 96 s-size: 508x265mm (20.00x10.43") s-diag: 573mm (22.56")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1920x1002 hz: 60 size: N/A modes: max: 1920x1002
    min: 640x480
  API: OpenGL v: 2.1 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: d020 bus-ID: 00:03.0
    chip-ID: 8086:100e class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
    modules: i2c_piix4 port: N/A bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives:
  Local Storage: total: 32 GiB used: 10.99 GiB (34.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 32 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1.0 scheme: MBR
Partition:
  ID-1: / raw-size: 31.99 GiB size: 31.32 GiB (97.89%) used: 10.99 GiB (35.1%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 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: 2086 libs: 1044 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free
  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://ftp.linux.org.tr/mx/repo/mx/repo/ bookworm main non-free
Info:
  Processes: 198 Uptime: 0m wakeups: 31 Memory: 15.62 GiB used: 1.01 GiB (6.5%) 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: BIOS (legacy, CSM, MBR)

Will try some of the other tweaks mentioned, as well as installing, & using FF...

[operadude]

Just tried updating (1 package-- rtl8821cu). Here's the output:

Code: Select all

full upgrade
apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   rtl8821cu-dkms (5.12.0+git20230215-1~mx23+2 => 5.12.0+git20230215-1~mx23+3)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 12.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.linux.org.tr/mx/repo/mx/repo bookworm/main amd64 rtl8821cu-dkms all 5.12.0+git20230215-1~mx23+3 [12.0 MB]
Fetched 12.0 MB in 4s (2,708 kB/s)         
(Reading database ... 287990 files and directories currently installed.)
Preparing to unpack .../rtl8821cu-dkms_5.12.0+git20230215-1~mx23+3_all.deb ...
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Unpacking rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) over (5.12.0+git20230215-1~mx23+2) ...
Setting up rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) ...
Removing old rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deleting module rtl8821ce-5.5.2.1+git20230504 completely from the DKMS tree.
Loading new rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20230504/dkms.conf)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/build/make.log for more information.
dpkg: error processing package rtl8821ce-dkms (--configure):
 installed rtl8821ce-dkms package post-installation script subprocess returned error exit status 10
Setting up rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821cu/5.12.0/build/make.log for more information.
dpkg: error processing package rtl8821cu-dkms (--configure):
 installed rtl8821cu-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 rtl8821ce-dkms
 rtl8821cu-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

full upgrade complete (or was canceled)

this terminal window can now be closed

Press any key to close...

HTH

[operadude]

@m_pav : Thanks for this:

Set up a shared folder from your host to the virtual appliance. Machine Settings > Shared Folders > Add, set permissions and automount, provide a simple name. Keep all things the same for simplicity, we'll go with the name Host. On your daily driver, make a folder called Host and use this folder as the source, the Share name and the mount point in the VM
Boot the VM, create a new folder called Host, open a terminal and issue the command as below.

Code: Select all

sudo mount -t vboxsf Host ~/Host

Can confirm that VB using shared folder is working for MX23-BETA2(XFCE, x64). Here's a screenshot of my VB settings (right-hand side), with VB using a shared folder (lower middle portion), and the Host machine showing the 2 files in VB in Host's directory (upper left portion of the screenshot), called "VB_HOST":

2023-06-20 VirtualBox Shared_Folders Setup.jpg

Unfortunately, FF crashes every time, about 3 seconds in!

Any recommendations about using a different browser in the VM(VB)?

[operadude]

@m_pav :
Forgot to mention that I am just using the following, inside VB, from a Terminal, every VB session:

Code: Select all

$ sudo mount -t vboxsf VB_HOST ~/VB_HOST

I need to do this each session of the VB. It's not automatic. I guess that's what you meant:

This is required for running Live, but for an installed VM, you only need the VirtualBox extensions installed in the virtual OS. Personally, I never install the extension pack, I just do as above. When you're all done, you can use this folder to transfer content between the host and the guest.

Yeah, easy enough to just use the Terminal one-liner, and not even worry about the "extensions" (Guest Additions?).
Again, thanks for that. Working like a charm

[Jerry3904]

Just for info
I found a bug in mxfb-look where conky isn't being reset correctly.
Think I see the small code change it needs, will check tonight.

In the same vein, I found that the MX-Comfort conky configs need some attention (e.g., battery not reporting)--will look tonight.

[ceeslans]

Yesterday I happened to see siamhie's referral to a potential scenario to upgrade MX21 to MX23.
Out of curiosity, I installed a latest snapshot of my MX21 system to a usb-3 drive (This actually is a skinny fluxbox install on a stripped-down MX21 setup, i.e with all xfce4-elements taken out) .
I then followed the instructions that @adrian provided in the wiki - just to see how this would work out.

During preparation, the command to write 'non-free-firmware' to the debian list failed, so I edited the list file manually.
Note that my 13y old laptop doesn't need the rtl8821* firmware, and as such the rtml8821*-dkms packages were already absent on my MX21 setup; as a result, I was spared from the potential dkms 'broken pipe' error.

The upgrade proces was smooth as silk, and finished without any real errors. It did take some time though, probably since I had over 2000 packages installed - and most likely the used usb drive didn't allow fast processing either.
I'm really happy with the endresult, I got a fully working MX23 setup, which hardly needed any adjustments. Had some problems with 'QSI-mx' throwing an error - and sofar I only needed to adjust a few exec paths to MX-tools in my fluxbox' rootmenu. Afterwards, I also installed the pipewire meta-package, which required some changes to be made to a few tint2-executor scripts. Surely, I will find some other small issues that would need adjustment, but overall the result is very satisfactory.

That said, I want to emphasize that this upgrade action may well be unsuccesful on other installations. The only way to check this, would be to test it on a snapshot, installed on a separate drive. And please take @adrian's warning at heart: before doing system-wide changes make a backup of your data and system.

About the wallpaper in the screenshot: I haven't a clue who portrayed Dolphin_Oracle so well... Oh well...

[Melber]

In the same vein, I found that the MX-Comfort conky configs need some attention (e.g., battery not reporting)--will look tonight.

Presume you mean MX-Comfort-Sysinfo.
Perhaps it needs the BAT0 / BAT1 check that was added in the MX-Cowon conkys?

[Jerry3904]

Yup, and temp is not reporting either (running live, maybe sensors missing?).

There's a spacing problem somewhere as well, haven't looked closely yet.