MX-19 Beta 3 Feedback

[yuul]

~~
((mainly cuz there's an annoying bug appearing in MX-18.3, and I wanna check if it's already solved in 19::
When I've lowered the Display-Brightness via Fn+arrow_keys, and put the laptop to sleep, after wake-up, I sometimes can't change the brightness at all, the Fn+arrow_keys just won't work.. ..needs a restart then.. [Lenovo G580]))
~~

..just happened


~ ' ~
^^ ...going for sleep & wake-up once more solved it, though..

[Jerry3904]

Lenovos are fussy and unpredictable.

[winemaker]

i went to thinkpads after all of the others never really worked with linux without a ton of work. years ago al of the heavies in linux ran TP's. i run 2 older x series and have run a couple of old r series and never had issues. the others - i could write a book. just my take from a no know nothing linux user.

[micronaut]

Firefox replaces the number nine with a long dash on some websites, such as this forum. clearing the checkbox to allow custom fonts in websites fixes it.

[jbMacAZ]

mx-19 beta 3 has the fix for https://forum.mxlinux.org/viewtopic.php?f=92&t=51965. The installer does see my partitions above 15. Also, the same liveUSB boots fine on my skylake desktop and my baytrail 2-in1(uefi32).

[JayM]

I did some experimentation re: Nvidia video drivers and OpenGL. Here's what I did:

1. Created a live USB, booted it with persist_all, used MX Repo Manager to select my mirrors, ran sudo apt update, ran the MX Updater to install all available updates, then remastered and rebooted.

2. Installed the Nvidia driver from the test repo and rebooted. Still no OpenGL renderers per inxi -G. This shows that it's not an issue with my installed version of 19b3.

3. Installed the antiX 4.9 kernel then ran the Live Kernel Updater, remastered, installed the 4.9 kernel in the live USB, rebooted. Booting stopped at the udev portion. Alt+F1 showed a console login prompt. Logged in and deleted /etc/X11/xorg.conf and rebooted.

4. Ran /usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh as su as my wifi no longer worked, rebooted, logged in to my SSID, reinstalled the Nvidia driver from test repo, rebooted. Still no OpenGL renderer. This shows that it's not an issue with the kernel.

5. Reinstalled MX-19b3 from my live USB, this time also installing its grub on my MBR.

(BTW there's a new option in the MX-19 installer if you install to existing partitions and preserve /home. Later on it prompts you whether you want to reuse your personal home directory, save it, delete it, plus one other option that I can't remember. It's not at all clear what the difference is between reuse and save. Once in the past I selected reuse, thinking that meant to reuse the existing home directory of my user name, while still preserving its contents as I'd already told the installer to do. I'm pretty sure it didn't save the contents, it replaced them all with those in /etc/skel. This time I selected save, but it saved it as /home/jay.001. It appears to no longer leave the contents of your home directory alone as it does in MX-18. I could be mistaken though.)

6. MX-19's grub didn't pick up my encrypted MX-18 installation and only gave me the MX-19 boot options, even after running sudo update-grub and rebooting. I selected booting MX-19 with the 4.9 kernel with systemd from advanced options. Still no OpenGL renderer. This shows it has nothing to do with booting with Sys V or the shim in MX-19 Buster.

7. Booted my MX-18 personal snapshot USB, ran MX Boot Repair to reinstall the MX-18 grub, got the usual can't create a chroot environment error. Reinstalled MX-18 from my snapshot that I made a few weeks ago. MX-18's grub shows all of both 18 and 19's boot options in its (flat) grub menu plus memtest, so I'm back in business. (However I just have the nouveau video driver as I made the snapshot just prior to installing the Nvidia driver in MX-18 the first time. I may just leave it that way. I only installed Nvidia's driver to see if it would work or not.)

8. I just reburned the 19b3 iso to my USB and booted it:

Code: Select all

demo@mx1:~
$ inxi -G
Graphics:  Device-1: NVIDIA GT216M [GeForce GT 230M] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA5 v: 3.3 Mesa 18.3.6

showing it's strictly an Nvidia driver issue, not something to do with OpenGL in general on this machine.

Conclusion: Something is wrong with the OpenGL packages for the Nvidia 340.170 legacy drivers, both the ones in stable and test. They get installed but they don't work or don't get loaded or something. The Nvidia driver itself works, but there's no OpenGL rendering so some apps don't work.

[Belham]

Hi MX Team,

Been running MX-19 since for a few months now. Use it stock--translation: I add nothing to it except the spyware (haha) Chrome browser since everything else I need is included. To me, 19 is pretty much awesome like 18 and 17 is/was.

Have one question though: since the update to 19.2.1 a few weeks back, the mx-updater tray icon no longer checks for updates by itself. What I mean is, that before, the updater tray icon would light up green and let me know updates were available. Then, I could go about installing any updates.

But after 19.2.1, I've went quite a few days (or week and a half) where I suddenly realized: "why hasn't there been any updates notice'? I mean, I knew that couldn't be right. Stuff doesn't go that long nowadays in Linux (well, er, not like it used to ). Sure enough, first time I realized this, I manually checked, and there were over 200MB of updates I should have installed many days prior


As things now stand, I have to right click the mx-updater tray icon, then click "Check for Updates", to see if any updates are available. Like I said, it used to light up green all by itself & let me know if any updates were available. Has the mx-updater been changed and we (users) are now required to "manually" activate the update search process to see if anything updates are available?

I also thought maybe I did something to cause this behavior since the last big update, but I cannot figure out how to correct it. Should I just use the terminal, delete the mx-updater, restart the machine, and then use the terminal again and re-install the mx-updater, all just to get it working in the background by itself so it is periodically checking for updates & lighting up green to let me know if any are available??

Here's some system info from one of my systems, a NUC machine, if it helps:

System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=########-####-####-####-############ 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-19beta-2.1_x64 patito feo September 8 2019 base: Debian GNU/Linux 10 (buster)

Thank you for help/feedback/tips to fix this.

[JayM]

@Belham: Please run MX Tools/Quick System Info, then right-click paste into a reply. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.

[Belham]

Code: Select all

System:    Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=########-####-####-####-############ 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-19beta-2.1_x64 patito feo September 8  2019 base: Debian GNU/Linux 10 (buster) 

.......(Machine, CPU, Graphics, Audio, Network, Drives not provided, no relevance for them to be)..........
 
Partition: ID-1: / raw size: 19.53 GiB size: 19.10 GiB (97.79%) used: 6.15 GiB (32.2%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 14.90 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p4 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 27.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/antix.list 
           1: deb https://mirror.vcu.edu/pub/gnu_linux/mxlinux/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/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.vcu.edu/pub/gnu_linux/mxlinux/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 226 Uptime: 9d 3h 31m Memory: 15.53 GiB used: 1.15 GiB (7.4%) 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 

Hmmm, is that the problem in "Repos"? Where it says: "No active apt repos in: /etc/apt/sources.list"??

[JayM]

Can you post an attachment consisting of a screenshot of the Individual Sources tab of MX Repo Manager? Click the Attachments tab at the bottom of the full (not quick reply) forum editor to attach it.