MX-19 Beta 2.1 Feedback

[asqwerth]

Cool. Thanks.

[Jerry3904]

This posted as a comment:

LMCE 19 19.1 19.2 as well as LM xfce introduced a vertical dark strip when using my Canolide 100 scanner. This was blamed on Ubuntu. I switched to LMDE and the strip ceased to exist. One up for Debian.
Then I experimented with MX 18 and again no vertical strip. However when MX 19 beta became available the strip re-appeared.
So much for blaming Ubuntu. Debian now shares the scanner fault.
I have become used to Linux MX 18 and 19 (don’t see much difference) but I hope this scanner problem can be eliminated.

I went to the Canon site for CanoLide and selected Linux 64bit, and got the message that the device was no longer supported. End of the story?

[KBD]

Looking very good. Just want to compliment you guys for the work on the installer. I didn't mind the old MX installer, but a linear experience that doesn't require the user to wait around for the next thing to happen, and then the next, really makes the installer much more user friendly.
Also wondering what magic you worked to get MX 19 beta 2 to boot on my Lenovo 11e? No version of Debian Buster or based on Debian Buster will boot on that machine. Even the first MX beta refused to do so, but this 2nd beta booted up without issue--very nice. I also had no issue with my Lenovo X220 with a full install from a separate drive.

[ChrisUK]

OK, ignore my last few posts... installed as expected to USB HDD - booted OK and saved live settings as wanted. Maybe I knocked the USB lead or it was a race condition, either way it's fine now

Will try with AMD laptop tomorrow

[asqwerth]

There were 3 virtualbox module updates: virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11

I updated and this was part of the text in terminal: [relevant bit is about not being booted into systemd init]

depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down...

The whole section of text in which the above appears:

Code: Select all

Unpacking virtualbox-guest-dkms (6.0.12-dfsg-1~mx19+1) over (6.0.10-dfsg-1~mx19+1) ...
Setting up virtualbox-guest-dkms (6.0.12-dfsg-1~mx19+1) ...
Loading new virtualbox-guest-6.0.12 DKMS files...
Building for 4.19.0-6-amd64
Building initial module for 4.19.0-6-amd64
Done.

vboxguest.ko:
Running module version sanity check.
 - Original module
   - Found /lib/modules/4.19.0-6-amd64/updates/vboxguest.ko
   - Storing in /var/lib/dkms/virtualbox-guest/original_module/4.19.0-6-amd64/x86_64/
   - Archiving for uninstallation purposes
 - Installation
   - Installing to /lib/modules/4.19.0-6-amd64/updates/

vboxsf.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.19.0-6-amd64/updates/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - Found /lib/modules/4.19.0-6-amd64/updates/vboxvideo.ko
   - Storing in /var/lib/dkms/virtualbox-guest/original_module/4.19.0-6-amd64/x86_64/
   - Archiving for uninstallation purposes
 - Installation
   - Installing to /lib/modules/4.19.0-6-amd64/updates/

depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

DKMS: install completed.
Setting up virtualbox-guest-utils (6.0.12-dfsg-1~mx19+1) ...
Setting up virtualbox-guest-x11 (6.0.12-dfsg-1~mx19+1) ...
Processing triggers for systemd (1:241-5+mx19+2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...

[Jerry3904]

I saw that too, but it's not wrong b/c it says very helpfully that systemd was not the init.

[asqwerth]

I just realised that matcha theme isn't on the beta 2.1 iso by default, even though it was on the superceded beta 2.

Sorry, didn't have time to test until now.

whoops....I'll bring it in as a temporary depend to mx-system. just for beta purposes.

I went ahead to install matcha theme.

Matcha-azul's theming for the top-right notification popup is nicer than greybird's, IMO (the pics below are for the volume slider's notification popup).

ksnip_20190909-012906.png

But even though I had applied matcha, the notification popup was still on greybird-mx-bright theme, which isn't very nice.

WHen I opened the settings for Notifications, I found that the theming dropdown menu had been set to blank (which presumably means the original theme the iso was shipped with?) instead of "Default", which would follow the gtk theme applied to the desktop by the user.

ksnip_20190909-013218.png

Perhaps notifications theming should be set to "Default" by default? Is that possible?

[dolphin_oracle]

I just realised that matcha theme isn't on the beta 2.1 iso by default, even though it was on the superceded beta 2.


Perhaps notifications theming should be set to "Default" by default? Is that possible?

very likely. will give it a go.

[dolphin_oracle]

good catch on the notificqtions. the theme was set to "Greybird-mx17" which doesn't exist. will update to "Default".

[Jerry3904]

viewtopic.php?p=525919#p525919