MX-19 Beta 2.1 Feedback

[dolphin_oracle]

I tried on another similarly partitioned system with the same outcome - partitions after 15 flagged as isBoot=true, not showing up

try this installer please:

https://drive.google.com/open?id=17fyNn ... YwX_zBfiWa

[dolphin_oracle]

This beta is behaving weird. After I set up live persistence: Laggy responses. $ sudo apt remove libreoffice-base libreoffice-base-core freezes. Had to control+C out and apt autoremove freezes. Firefox freezes.

Ive never ever had these problems with MX. Even 19.1 Beta was great. :/ Super frustrating

if you could send the system info (quick-system-info in the menu) while you are running with persistence that might be of some use. the kernel is new...

[Jerry3904]

Welcome to the Forum! It sounds like you might have a bad download. Can you click Start and start typing to launch Quick System Info and paste it back here so we can take a look at your system?

[fehlix]

Running Live I receive this same error as on the preview. Waiting makes no difference nor does changing repos.
viewtopic.php?f=86&t=52564&p=525951&hil ... ta#p525951
I then installed and that error does not occur.

Also running Live the mouse cursor theme will apparently not change not change in size. However after the install when saving Home changes that were made, the change made in Live for the mouse is implemented.

Seem to me somehow systematic issue, kind of timezone in combinations with localtime or wrong hardware clock issue.
As apt always appear to think your "clock" is a bit to late (or to early resp.)
Hmm.. what about checking clock, UTC, and RTC (= hardwareclock) before a next live update, e.g. with persistence.

Not an issue I am trying to fix. Just reported it in case it is a common problem others may experience. No one else has reported it. I can try your suggestion tomorrow if it will be helpful

When you boot the LiveUSB on a system which run the clock in localtime (e.g. having booted before in WinOS),
and the LiveSystem boots in UTC the system assumes (wrongly) the RTC-clock is set to UTC.
E.g. your timezone is set to UTC-4: Now when apt/dpkg fetches an InRelease file, which is not older then 4 hours
it appears to "apt" that this InRelase file comes from the future and hence rejects to process this file. ( "not yet" )
Or with other words, the system appears to be 4 hours in the past.
You would have now to wait exactly as long so that the InRelease file becomes older until it is not anymore from the future.
To sort this you can either set the RTC-clock to correct UTC-time or set LOCAL for using the locale RTC-time
by using "MX Date & Time". Alternatively you could also boot live with boot option hwclock=local .
HTH

[richb]

@fehlix Understand. So it is a known issue, not requiring further investigation.

[rskempf]

I just loaded this release on an i5, 64 bit system. The pc is working well - no problems at all. Nice work!

[Jerry3904]

Thanks for checking in -- welcome to the Forum!

[fehlix]

@fehlix Understand. So it is a known issue, not requiring further investigation.

Yes, issue known - Seattle made.

[richb]

@fehlix Understand. So it is a known issue, not requiring further investigation.

Yes, issue known - Seattle made.

Do not understand the Seattle reference.

[fehlix]

@fehlix Understand. So it is a known issue, not requiring further investigation.

Yes, issue known - Seattle made.

Do not understand the Seattle reference.

using locatime instead of UTC and resisting to change to UTC was somehow grown up in a suburb of that mentioned place.