MX-23 beta 2 feedback thread

[8bit]

Hope this is posted in the correct place.
In 23B2 when one clicks on the clock a separate window opens which must be manually closed. In 21.x the same click opened a pop-out that closed with another click. Can and how do I get 23b2 to act like 21.x
PS I've tried all the settings I could find before asking.

Thanks for your time.
Al

[dolphin_oracle]

@gRegNfo

Ok good.

so the updated tool should have installed that driver anyway, without the -f option. likely your problem was with the tool prior to the update.

[dolphin_oracle]

Hope this is posted in the correct place.
In 23B2 when one clicks on the clock a separate window opens which must be manually closed. In 21.x the same click opened a pop-out that closed with another click. Can and how do I get 23b2 to act like 21.x
PS I've tried all the settings I could find before asking.

Thanks for your time.
Al

swap out the default clock plugin for the deprecated but still present datetime plugin.

[gRegNfo]

@gRegNfo

Ok good.

so the updated tool should have installed that driver anyway, without the -f option. likely your problem was with the tool prior to the update.

@dolphin_oracle

Oh no, quite the opposite.
I first may have messed up with the DDM-MX installer I don't know. But I couldn't boot any kernel at al!!! They all panicked and stalled...
So I did revert it to the snapshot I made earlier. And after that I installed drivers (470 TESLA)via the Synaptic GUI tool. And locked the v.470 Tesla version.
It worked... And after I did mess with dkms and initramfs just to be sure all modules were up to date and installed.
It all checked out!

I never tried the ddm-mx again! As I reverted it to the point I was before using it the first time... so no merit for that
But I will in the future so you know if it's reliable or I made a mess... I bet the later

Thanks man!

[fehlix]

I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.

As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.

Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.

[siamhie]

the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.

@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.

you could try updating the initramfs again. it should have been done automatically.

Code: Select all

sudo update-initramfs -u -k all

@dolphin_oracle Still no go. I even tried changing my grub theme from mx_linux to mx_logo_ribbon but it didn't help. I'll make a post in the MX Boot Animation thread.

[Danathar]

I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.

As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.

Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.

wait...that last part, about toram. The first image I made I booted with the toram option. Maybe it's as simple as that?

[dolphin_oracle]

Revisiting the burning issue with k3b and Xfburn:
On Mint XFCE 21.2 Beta, everything works fine. k3b works great, no errors, Xfburn burns .mp3s without the above-mentioned distortion and easyMP3gain can easily be installed via Snap instead of manually downloading the front-end here (as stated in another thread). Also, on the other PC which runs MX23 Beta, for some reason, easyMP3gain does not work, but on the PC I'm using right now it does...
I'm pretty sure things with k3b are gonna be OK on MX23 KDE Beta 2, but for the sake of the argument, I'll download it and check it out so the developers now where to focus.
Overall, each one uses their PC for their own personal reasons, with a set of specific tasks in mind they want to perform.
There are some who still burn CDs (for some crazy reason) and it seems I cannot do that right now on MX23 Beta. Thus, I'll have to uninstall MX23 Beta from the other PC
and install an Ubuntu derivative that does the job (probably Mint XFCE). However, I wouldn't like to uninstall MX23 from this PC, so I would appreciate it if a solution could be found concerning the issue with k3b. Alternatively, I'll have to go for another distro that can do that hassle free.

xfburn does indeed seem to have an issue burning audio cds from mp3 files. I get high-pitched distoration with mine.

k3b was OK, after I did this from the commandline (without k3b running) to set permissions on a couple of helper programs that k3b needs.

Code: Select all

sudo chmod 4711 /usr/bin/wodim; sudo chmod 4711 /usr/bin/cdrdao

there is an interface in k3b for changing the permissions, but it sets 4710 instead of 4711 and the apps did not actually start configured such.

[dolphin_oracle]

I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.

As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.

Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.

wait...that last part, about toram. The first image I made I booted with the toram option. Maybe it's as simple as that?

could be. I just verified with a standard full live-usb that the live-usb-storage folder is created.

[i_ri]

Hello @PPC
mxfb-menu-generator
nodisplay true
line 121 if [[ $nodisplay == *"true"* ]]; then

"rue" is "true"?

i visit in <mxfb-menu-generator> to add a custommenu

and then add a matching [end] for the [begin] placed at the start.
after the [submenu][end] line 186
another end;
line 187 echo '[end]' >> $FILE