MX-19 Beta 2.1 Feedback

[gsm]

Live MX-19 Beta 2.1 system 64-bit (tried also unmodified standard language: English US) .
Most things are running well, but...

Libreoffice won't start in the Live MX-19 Beta 2.1 64-bit system. Just a short flash of the startup screen is shown. Still not working after applying the latest updates.

Edit: extra information
When typing the command "libreoffice %U" in a terminal, the intro of LibreOffice is shown and just when starting the progress bar a fatal exception occurs:

Code: Select all

Fatal exception: Signal 11
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d523)[0x7ff401e2b523]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d733)[0x7ff401e2b733]
/lib/x86_64-linux-gnu/libc.so.6(+0x37840)[0x7ff401c4b840]
/usr/lib/libreoffice/program/libuno_cppu.so.3(+0x14b32)[0x7ff3ff069b32]
/usr/lib/libreoffice/program/libuno_cppu.so.3(uno_type_any_assign+0x97)[0x7ff3ff068f27]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2aac818)[0x7ff4048f8818]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2aad4f5)[0x7ff4048f94f5]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x7b)[0x7ff4048ee76b]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2b01fb8)[0x7ff40494dfb8]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x11f)[0x7ff40494f4af]
/usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x1a0)[0x7ff404ca3480]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2e58a1d)[0x7ff404ca4a1d]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7ff404ca4a70]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7ff403d76d71]
/usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55cd1cdf907b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7ff401c3809b]
/usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55cd1cdf90ba]

/Edit

There may be also an issue with the Dutch-NL Language pack. aspell-nl, hunspell-nl are installed.
No errors during install, but Dutch Language Meta-Package line is not greyed after the successful install and therefor it cannot be uninstalled.
Probably because myspell-nl is missing?

[Eadwine Rose]

GSM: were you running the installer when you tried to open LO?

[rpcm]

First off, I am amazed that MX recognized the keyboard in my Acer R11 Chromebook! I can't even tell you how many distros have failed at that.

I do have an issue with suspend and hibernate. Neither seem to work as I suspect when closing the lid. The computer stays awake and the screen turns right back on after I open the lid, but then no actions work (all keyboard and mouse input is ignored until I hit Ctrl+Alt+Backspace and log back in).

Here is the output of `quick-system-info-mx`:

Code: Select all

System:    Host: physalis Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: GOOGLE product: Cyan v: 1.1 serial: <filter> Chassis: type: 3 
           serial: <filter> 
           Mobo: N/A model: N/A serial: N/A BIOS: coreboot v: N/A date: 06/05/2018 
Battery:   ID-1: BAT0 charge: 24.7 Wh condition: 32.1/40.5 Wh (79%) volts: 11.8/11.6 
           model: SANYO AC15A3J type: Li-ion serial: <filter> status: Discharging cycles: 101 
CPU:       Topology: Dual Core model: Intel Celeron N3060 bits: 64 type: MCP arch: Airmont 
           family: 6 model-id: 4C (76) stepping: 4 microcode: 411 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 
           Speed: 526 MHz min/max: 480/2480 MHz Core speeds (MHz): 1: 555 2: 480 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated 
           Graphics 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:22b1 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (Braswell) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High 
           Definition Audio 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2284 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0 
           chip ID: 8086:095a 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 14.68 GiB used: 6.42 GiB (43.7%) 
           ID-1: /dev/mmcblk0 model: HAG2e size: 14.68 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 0x7 scheme: MBR 
Partition: ID-1: / raw size: 12.13 GiB size: 11.88 GiB (97.91%) used: 6.33 GiB (53.3%) fs: ext4 
           dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 79.9 MiB (16.4%) 
           fs: ext4 dev: /dev/mmcblk0p1 
           ID-3: swap-1 size: 1.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/keybase.list 
           1: deb http://prerelease.keybase.io/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
           1: deb https://download.sublimetext.com/ apt/stable/
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 237 Uptime: 8m Memory: 3.80 GiB used: 1.31 GiB (34.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 clang: 7.0.1-8 
           Shell: bash v: 5.0.3 running in: quick-system-in inxi: 3.0.33 

[Jerry3904]

I do have an issue with suspend and hibernate. Neither seem to work as I suspect when closing the lid. The computer stays awake and the screen turns right back on after I open the lid, but then no actions work (all keyboard and mouse input is ignored until I hit Ctrl+Alt+Backspace and log back in).

Take a look at Settings > Power Manager.

[gsm]

GSM: were you running the installer when you tried to open LO?

No, i just booted from the unmodified (flashed just before) USB-stick and then i only tried to start LO, nothing else. It was okay in Beta 1.

[rpcm]

I do have an issue with suspend and hibernate. Neither seem to work as I suspect when closing the lid. The computer stays awake and the screen turns right back on after I open the lid, but then no actions work (all keyboard and mouse input is ignored until I hit Ctrl+Alt+Backspace and log back in).

Take a look at Settings > Power Manager.

Thanks. I tried 'Suspend' and 'Hibernate' when the lid is closed under power manager. Both seem to only be turning off the display.

[fehlix]

I patched yesterday to keep automount disabled even if someone runs gparted from inside the installer (gparted would still trigger automounts when it closed, mostly because it disabled our disabling, if you catch my meaning.)

So the good news: The automount prevention seems to work, including after open and closing gparted from within the installer. So the udev-rules for blocking block devices do work.
Open the installer disables automount and takes away all devices from the filemanager device list. So this is good.
Thunar before:

fm-b.png

But if user closes the installer before it finishes or just even at the first page, the user appears to have no chance to mount any devices, as not devices are listed anymore after closing the installer:

fm-da.png

So the udev-rules do a bit more than they should have done.
Now what? Right we might have forgotten to convince udev-again to let Thunar list the devices or to trigger a partprobe again. If user issues a "sudo partprobe" the device are shown again and mountable.
FWIW, without those automount-preventing rules just this call of minstall this way :

Code: Select all

mx-pkexec /usr/lib/udisks2/udisks2-inhibit /sbin/minstall

would have done this already. Just run x-kill to close the installer and no mount appears possible anymore. The udev-rules get also not removed. The user would need to reboot to sort this.
The above udisks2-inhibit call would prevent such and no need to have this udev rule at all. Just test it with open gparted, and xkill it, all devices are shown again in Thunar in contrast to minstall, bc of the udev-rules still ins place.

[joele]

Install went fine but found the flatpak update bug from 18.x is still present..

A good example to test with is qownnotes as it gets updated multiple times a week, lol.. I have clicked 'upgrade all' but without typing anything it auto keys 'n' and doesn't do any updates.. Can do it over and over and same issue, until I drop to cli and 'flatpak update' and it updates fine and shows as such in mx package installer..

[dolphin_oracle]

I patched yesterday to keep automount disabled even if someone runs gparted from inside the installer (gparted would still trigger automounts when it closed, mostly because it disabled our disabling, if you catch my meaning.)

So the good news: The automount prevention seems to work, including after open and closing gparted from within the installer. So the udev-rules for blocking block devices do work.
Open the installer disables automount and takes away all devices from the filemanager device list. So this is good.
Thunar before:
fm-b.png
But if user closes the installer before it finishes or just even at the first page, the user appears to have no chance to mount any devices, as not devices are listed anymore after closing the installer:
fm-da.png
So the udev-rules do a bit more than they should have done.
Now what? Right we might have forgotten to convince udev-again to let Thunar list the devices or to trigger a partprobe again. If user issues a "sudo partprobe" the device are shown again and mountable.
FWIW, without those automount-preventing rules just this call of minstall this way :

Code: Select all

mx-pkexec /usr/lib/udisks2/udisks2-inhibit /sbin/minstall

would have done this already. Just run x-kill to close the installer and no mount appears possible anymore. The udev-rules get also not removed. The user would need to reboot to sort this.
The above udisks2-inhibit call would prevent such and no need to have this udev rule at all. Just test it with open gparted, and xkill it, all devices are shown again in Thunar in contrast to minstall, bc of the udev-rules still ins place.

we didn't forget. partprobe triggers automounting of partitions, asking for passwords over and over again, which is really annoying when you have a lot of partitions. the wrapper does use the same

the same happens with gparted incidentally.

the udisks2-inhibit uses the same rules names as gparted, which gparted will erase when it closes, even if our installer makes it, so we make our own named rule now so that gparted doesn't nuke it.

I will test the udisks2-inhibit approach, but I'm guess that automount will be triggered again.

What we need is a way to make things show up without udisks/thunar trying to mount them again.

[fehlix]

we didn't forget. partprobe triggers automounting of partitions, asking for passwords over and over again, which is really annoying when you have a lot of partitions.

I know, but when user pressed "close" partprobe is not triggered.