MX-19 Beta 2.1 Feedback

[dreamer]

I don't see apparmor installed on MX 17/18. Isn't that just another piece of Linux bloat that will annoy and create problems for newbies and more experienced users? Some people report that Debian 10 doesn't run properly with apparmor on certain hardware. Linux is already too complicated for a casual user.

[Jerry3904]

Right now it's there for beta testing.

[dolphin_oracle]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

This is broken in MX-19; the function key settings are not respected as the clocks display in 12 hour format, and at the installer screen the 12 hour radio button is pre-set.

Running live in MX-18, issuing 'timedatecl' show this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
      Local time: Tue 2019-09-17 08:33:30 BST
  Universal time: Tue 2019-09-17 07:33:30 UTC
        RTC time: Tue 2019-09-17 07:33:30
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

Whereas in MX-19, running live or installed, 'timedatectl' shows this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down


Chris

The automatic setting of the panel clock to 24 hour or 12 hour is totally based on language selected at start. I did try this morning, and setting to english-UK did set the 24 hour panel clock to 24 hour.

In fact, 24 hour is the default on the clock, and is only changed to 12 hour for a particular set of locales.

Code: Select all

case $LNG in

	LANG=en_US.UTF-8|LANG=en_AU.UTF-8|LANG=en_CA.UTF-8|LANG=en_NZ.UTF-8|LANG=ar_EG.UTF-8|LANG=el_GR.UTF-8|LANG=sq_AL.UTF-8) changeto12hour
	;;

however, if you've changed the clock plugin to something other than datetime, or if you've set your language to one of the en languages above, then the clock will set to 12 hour. I have been planning to add code back in to handle orage clock plugin, but I haven't got to it yet.

I can't speak for the installer right now, or the conky at all.

[chrispop99]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

This is broken in MX-19; the function key settings are not respected as the clocks display in 12 hour format, and at the installer screen the 12 hour radio button is pre-set.

Running live in MX-18, issuing 'timedatecl' show this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
      Local time: Tue 2019-09-17 08:33:30 BST
  Universal time: Tue 2019-09-17 07:33:30 UTC
        RTC time: Tue 2019-09-17 07:33:30
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

Whereas in MX-19, running live or installed, 'timedatectl' shows this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down


Chris

Running b2 installed it works here:

Code: Select all

$ timedatectl
               Local time: Tue 2019-09-17 06:58:43 EDT
           Universal time: Tue 2019-09-17 10:58:43 UTC
                 RTC time: Tue 2019-09-17 10:58:43
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

I just checked on two other installs on different hardware, and it doesn't work here.

Chris

[dolphin_oracle]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

This is broken in MX-19; the function key settings are not respected as the clocks display in 12 hour format, and at the installer screen the 12 hour radio button is pre-set.

Running live in MX-18, issuing 'timedatecl' show this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
      Local time: Tue 2019-09-17 08:33:30 BST
  Universal time: Tue 2019-09-17 07:33:30 UTC
        RTC time: Tue 2019-09-17 07:33:30
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

Whereas in MX-19, running live or installed, 'timedatectl' shows this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down


Chris

Running b2 installed it works here:

Code: Select all

$ timedatectl
               Local time: Tue 2019-09-17 06:58:43 EDT
           Universal time: Tue 2019-09-17 10:58:43 UTC
                 RTC time: Tue 2019-09-17 10:58:43
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

I just checked on two other installs on different hardware, and it doesn't work here.

Chris

can you post the /etc/default/locale file please.

[chrispop99]

Try disabling some of the LibreOffice AppArmor profiles:

Code: Select all

sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.oosplash /etc/apparmor.d/disable/
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin /etc/apparmor.d/disable/
sudo aa-teardown
sudo service apparmor restart

I'm at a loss as to why it doesn't work on the live system, but works perfectly on the installed system.

Entering those commands allowed LibreOffice to start normally.

Chris

[chrispop99]

can you post the /etc/default/locale file please.

Code: Select all

#  File generated by update-locale
LANG=en_GB.UTF-8

Chris

[dolphin_oracle]

can you post the /etc/default/locale file please.

Code: Select all

#  File generated by update-locale
LANG=en_GB.UTF-8

Chris

is that from the live system? (sorry I should have specified)

[fehlix]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

Booting LiveISO MX19-beta2.1. in BIOS mode:
Select F2 Language -> English (UK)
Select F3 Timezone -> London
When booted:
-> /etc/timezone is set properly to Europe/London
->Orage time in the panel is also correctly set to the 24h display format
-> The conky display format is set correctly set 24h, using the new conku_hours.lua pmfix
-> Running the installer: Language-Locale and Timezone as well als HW-clock in UTC is preset properly.
****
EDIT: I'm wrong looking at the Installer again: Time format is wrongly preset in the Installer.
Note: I have not updated to latest installer.
****
EDIT2: After Updated MX-Installer: preset is still wrongly set in 12h format instead of 24h withi the installer.
****
See this;
Boot Screen:

En_GB_London-1.png

Desktop with terminal, Conky and installer show time and locale properly:

En_GB_London-2.png

[chrispop99]

can you post the /etc/default/locale file please.

Code: Select all

#  File generated by update-locale
LANG=en_GB.UTF-8

Chris

is that from the live system? (sorry I should have specified)

Yes.

Chris