MX-19 Beta 3 Feedback

[chrispop99]

Is this the reappearance of the login screen before system shutdown/reboot?

If so, it doesn't happen to me in 18.3, fully updated install.

If you mean the very brief appearance of a grey screen, yeah that does happen, but it's very short (much shorter than that login screen), like half a second or so.

Confirmed here.

Chris

[gsm]

If that "US international, with € at 5" the proper keyboard which shall be the default for Netherland?.
To check on the command line I got this details:

Code: Select all

setxkbmap -query
rules:      evdev
model:      pc105
layout:     us
variant:    euro
options:    compose:rctrl-altgr

I checked this on my Microsoft Multimedia Keyboard 1.0A:

Code: Select all

setxkbmap -query
rules:      evdev
model:      pc105
layout:     us
variant:    euro
options:    grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp

After adding the Compose combination to the keyboard layout:

Code: Select all

setxkbmap -query
rules:      evdev
model:      pc105
layout:     us
variant:    euro
options:    compose:ralt,grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp

[/quote]
Regards GSM

[bpr323]

Installed 19-b3 on baremetal box1 - all good
Took a snapshot (not preserving user profile, "for distribution" - done
Created bootable USB with MX USB creator - done
Trying to install from this snapshot on a different laptop (X1 carbon, all ssd partitions deleted) and got stuck with installer problems:

1) The snapshot USB boots to desktop, but hasn't preserved my "horizontal panel" settings, although menu items are correct.
2) When I start the install from GUI icon it spits out errors "minstall.conf has incorrect settings", etc - it reports that it can't format partitions, can't install Grub automatically
3) Tried "custom install" - same
Both the source PC and target PC are basic aio Intel x64 laptops - nothing fancy, no nvidia - what's the deal with the minstall.conf?

[bpr323]

Created a new snapshot on the donor PC - now preserving the user settings and created new USB image
Boots fine, but when I run the Install GUI, I get the same "minstall.conf incorrect settings" and the target drive is highlighted red.
Ignored the error, kept pressing <next> and finished install. NB - on the source PC the user logs in automatically
Now I want to change the user name for the cloned PC. I log out as User 1 and log in as root
Fire up user manager, select the User 1 account and enter new name - no can do. It tells me User 1 is still logged in.
Is there a way, on an "log in automatically" machine to invoke the login prompt by pressing a key during boot time, like F6 or something, so I can log in as root before default user is logged in?

[Paul..]

no nvidia - what's the deal with the minstall.conf?

Try installing the updates...which fix installing nvidia drivers (ddm-mx -i nvidia)

[Adrian]

Installed 19-b3 on baremetal box1 - all good
Took a snapshot (not preserving user profile, "for distribution" - done
Created bootable USB with MX USB creator - done
Trying to install from this snapshot on a different laptop (X1 carbon, all ssd partitions deleted) and got stuck with installer problems:

1) The snapshot USB boots to desktop, but hasn't preserved my "horizontal panel" settings, although menu items are correct.
2) When I start the install from GUI icon it spits out errors "minstall.conf has incorrect settings", etc - it reports that it can't format partitions, can't install Grub automatically
3) Tried "custom install" - same
Both the source PC and target PC are basic aio Intel x64 laptops - nothing fancy, no nvidia - what's the deal with the minstall.conf?

1. is not a bug per se, snapshot never saved desktop changes, that's controlled by /etc/skel and you'd need to customize that manually.
2. we probably need to exclude that minstall.conf when taking a "for distribution" snapshot, it simply tried to use the last install configuration since your drives have different names/partitions it would say that the config file is wrong but it should still let you choose your own settings, doesn't that work? You could also for now remove /etc/minstall.conf
3. I'm not sure what "--same" means. That it cannot format partitions? What did you select? Did you create the partitions with Gparted and then selected them and it could use then?

[bpr323]

@Paul - thank you, I meant to say I do NOT have any fancy hardware like nvidia video cards, raid arrays, etc. that may complicate the install, both and target machines are plain vanilla Intel aio's.
Adrian understood the installation issue correctly - i.e. " we probably need to exclude that minstall.conf when taking a "for distribution" snapshot, it simply tried to use the last install configuration since your drives have different names/partitions it would say that the config file is wrong"

[Srdjan]

That shutdown issue - is it somehow possible to deal with it
in a way when shutdown is called, but before that login screen reappears, just black
screen is drown directly from graphic driver and that further screen drawing stuff that
XFCE or whatever proces does is just redirected to /dev/null or something? :D

[bpr323]

@ Adrian - thanks mate, you're spot on! Because the crown jewel of MX (and now Antix) is the ability to clone the "fine-tuned" systems via snapshots - maybe it's worth:
a) removing minstall.conf
b) in the mean time, somehow warn users they should create "personalised" snapshots and complete the install ignoring the "minstall.conf" error messages

I'm now stuck with the autologon issue - how do I log on as root before default user logs in automatically so I can manage that user settings as root?

[Jerry3904]

I don't think you can log in as root, but if you launch MX User manager it will pop up a box for root access. (Is that what you mean?)