MX-19 Beta 3 Feedback

[hunghung]

I don't know what it's called on Linux but it's Task Bar on Windows. On previous versions of MX, it's large enough so the icons are also larger and easy to work with. But with MX 19 I think it's become too slim so it's very difficult to work with the icons since they're too small now. I want the old Task Bar back

[Eadwine Rose]

Right click, properties, increase the size.

[hunghung]

Right click, properties, increase the size.

I know this. But I think it should be large by default like on previous versions of MX.

[hunghung]

On MX Package Installer, could you add Zulu JDK? They provide ready to use .deb packages: https://www.azul.com/downloads/zulu-com ... x86-64-bit

I asked about it because Azul Zulu does patched their java for better font rendering, it helps Swing based applications like Netbeans very much

p/s: I know I shouldn't post it here but I don't know where to post it at all, sorry

[Srdjan]

I know this. But I think it should be large by default like on previous versions of MX.

First thing after I install OS is resizing that thing to 28 pixels :D

[entropyfoe]

I thought my beta3, on an fscked partition was solid, but it crashed after 1 day and 14 hours, at idle. Of the 6 or so all freezes have been at idle, when I am not present, only one was when I was doing something (opening the MXPI).

This one was at almost idle. I had firefox with 6 tabs, minimized on the panel and clementine, also not playing minimized. I had the terminal open to top, so I see, frozen (no response to mouse of KB) what was running.
The items of interest are kworker and rcu_sched. See attached.

I don't know what kworker does, there is some kind of event.
And the rcu is of interest, because way back when Ryzen came out, I needed some boot parameter RCU_NO_CBS or something. This has not been necessary since a BISO fix prevented the machine from going to such low power it locked up. Is it related that my freezes are now with low work loads?

Any ideas? This is a fresh install from a day and a half ago, nvidia not yet installed, not many other programs yet. I was thinking the power supply after I had a power failure (I do have a surge protector), but why at low work loads? At seeming random?
MEMTEST?

What next?

[Stevo]

I thought I'd install the 32-bit version on the Acer Skylake Optimus laptop to see how the 390 Nvidia legacy driver install went on it, though I think almost all users will be installing 64-bit on these type of laptops. One thing I noticed right away is that I could only install in the spinning HD's MBR and boot in legacy mode, probably because it was 32-bit instead of 64 bit.

The MX Nvidia installer performed well and installed the 390xx legacy driver automatically, since that's the latest version that supports 32-bit, but the Bumblebee GPU switching didn't work, even after several reboots. I then booted with the systemd option, and Bumblebee started working, and continued working, even after I rebooted without systemd. IDK if it was coincidence or systemd that made it start to work, but not many users will be installing 32-bit on this type of machine anyway, so I'm going to test it with 64-bit next.

[JayM]

What would you do when you're on other Unix-like system and don't have MX Live USB Maker?

HOWTO: Burn bootable USBs from Tips&Tricks covers this.

[JayM]

Right click, properties, increase the size.

I know this. But I think it should be large by default like on previous versions of MX.

That's a matter of personal taste. Others think it's fine the way it is, still others think it should be smaller, some think it should be at the bottom or top... whatever is chosen as the default, it isn't going to please everyone. That's why it's adjustable.

Plus, not everyone has a big high-def monitor. If the default panel is large it will be way too big on an old low-res netbook with an 11" screen.

[JayM]

What next?

Quick System Info? No one can help you without any information about your computer.