MX-19 RC1 Feedback thread

[Stevo]

Only a few hours in but all seems well so far. I usually use the Adwaita-dark theme which is working fine but I can't seem to find the Adwaita-dark WM theme that was downloadable via MXPI previously. Has it been removed?

Add a package request in the appropriate sub-forum for MX19.

Adwaita dark never came with a proper WM theme. The latter was specially extracted and packaged for MX18 from a 3rd party gtk theme called adwaita-xfce-dark which is no longer maintained, but which WM theme still works for XFCE.

No need for a package request, I'll simply move to a different theme. Thank you.

I just rebuilt it for MX 19, so it should be in main pretty soon as "adwaidta-xfce-wm-themes".

[BV206]

I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of "Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.

[darknetmatrix]

Everything just works 100% perfect over here, tnx to the dev.crew.

[vtvbreech]

I just rebuilt it for MX 19, so it should be in main pretty soon as "adwaidta-xfce-wm-themes".

Thank you Stevo, very much appreciate the effort

[JayM]

I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of "Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.

Please run MX Tools/Quick System Info after booting your live USB, then right-click paste into a reply. (Quick System Info automatically copies the information to the clipboard and formats it properly for the forum so all you have to do is paste it.) Thanks.

[penguin]

Hi.

I have gone through this thread time by time.

Sorry if I repeat the same question.

Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?

I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.

Can we have the possibility to upgrade MX LInux in two steeps ?

1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE

Maybe what I am asking for is totally stupidity or wrong , but just a question.

[JayM]

I installed the 32-bit version on my Averatec 32-bit notebook this morning. It runs faster and smoother than MX-18. I love the screen that pops up when I connected my external monitor asking if I wanted to only use the netbook's display, mirror the two monitors, extend the desktop across both, or only use the external. Tha makes setting up multiple monitors easy. One little niggle though: after I made my selection my wallpaper got changed from the default one to an Xfce one with a mouse, and the wallpaper folder in Desktop Settings was changed from /usr/share/backgrounds/ to /usr/share/backgrounds/xfce/.

I went ahead and invested some time setting up the panels the way I like as I plan to just upgrade RC1 to the final release when the time comes.

Two problems with packages:

1. Lucky Backup as superuser doesn't run after I enter the root password. If I run it in a terminal it says

Code: Select all

jay@mx19:~
$ /usr/bin/luckybackup-pkexec
qt.qpa.screen: QXcbConnection: Could not connect to display 
Could not connect to any X display.

2. When I use Zulucrypt GUI to decrypt my Veracrypt-encrypted external HDD where my backups live, I always get a message (after entering the passphrase) "Unrecognized ERROR with status number 255 encountered" and the decryption/mounting dialogue window doesn't close, yet it still decrypts and mounts the drive, mounting it under run/media/private/jay now instead of /run/media/private/root as it used to in MX-18.

My QSI:

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-686-pae i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-4.19.0-6-686-pae 
           root=UUID=14a01254-11c5-4b33-83df-6a051e812e6f ro quiet splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19RC1_386 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Other-vm? System: AVERATEC product: N1130 v: N/A serial: <filter> 
           Chassis: No Enclosure type: 1 serial: <filter> 
           Mobo: AVERATEC model: N1130 serial: <filter> BIOS: Phoenix 
           v: NAPA0001.86C.0056.D.0907311757 date: 07/31/09 
Battery:   ID-1: BAT0 charge: 65.3 Wh condition: 65.3/65.4 Wh (100%) volts: 65.5/N/A 
           model: AVERATEC N1130 type: Li-ion serial: N/A status: Full 
CPU:       Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell 
           family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6384 
           Speed: 1059 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 1059 2: 1006 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 status: Not affected 
           Type: spectre_v2 status: Not affected 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:27ae 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa 
           compositor: compton v: 0.1~beta2+20150922 resolution: 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-6-686-pae 
Network:   Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 
           port: 18e0 bus ID: 02:00.0 chip ID: 1814:3090 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           v: kernel port: 2000 bus ID: 04:00.0 chip ID: 10ec:8136 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.93 TiB used: 1.22 TiB (63.1%) 
           ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 61.3 
           scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 1.82 TiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 5438 
Partition: ID-1: / raw size: 109.24 GiB size: 107.03 GiB (97.97%) used: 6.33 GiB (5.9%) fs: ext4 
           dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 76.2 MiB (15.6%) 
           fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 1.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 39.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/antix.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/antix//buster buster main
           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 https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 184 Uptime: 12m Memory: 1.90 GiB used: 388.4 MiB (20.0%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

One final niggle: I changed my wallpaper to a darker one, and as I mentioned a while ago the default conky is almost impossible to see.

[Eadwine Rose]

Hi.

I have gone through this thread time by time.

Sorry if I repeat the same question.

Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?

I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.

Can we have the possibility to upgrade MX LInux in two steeps ?

1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE

Maybe what I am asking for is totally stupidity or wrong , but just a question.

No sorry, you will have to install fresh. You can keep /home for the config files and all.

[asqwerth]

MX conky was provided so you can change colours of the conky to suit your wallpaper. The conky can't conceivably be visually suitable for every wallpaper.

[asqwerth]

Hi.

I have gone through this thread time by time.

Sorry if I repeat the same question.

Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?

I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.

Can we have the possibility to upgrade MX LInux in two steeps ?

1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE

Maybe what I am asking for is totally stupidity or wrong , but just a question.

You can try but no promises if you break it. Or it may kind of work but not perfectly, and who's going to debug that? It's not recommended and won't be supported.

You're moving from a Debian base that had systemd-shim to one where it's deprecated in buster. MX had to get their own shim package done up for mx19 via a 3rd party developer.

Xfce 4.14 is gtk 3.

Settings and configs changes in mx19 affecting xfce and perhaps systemd-shim may not carry over using a change of repo, if changes were made inside the home partition.

So your mx18 settings may not go well with new xfce, etc in mx19.

I don't think you can realistically expect MX to just specially set up a separate mx19 repo for new xfce just so mx19 users can still use xfce 4.12 if they want