MX Linux Forum

Posted: **Sun Sep 08, 2019 8:01 am**

https://sourceforge.net/projects/mx-lin ... ing/MX-19/

If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.

If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.

If posting remaster issues, please include the contents of /var/log/live/live-remaster.log

If posting installer issues, please include the contents of /var/log/minstall.log

If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).

Thank you!

Posted: **Sun Sep 08, 2019 8:47 am**

Does upgrading from beta1 work, or has there been dramatic changes?

Posted: **Sun Sep 08, 2019 8:49 am**

There are some nice upgrades to the installer, as well as fixes, so installation needs to be tested. Just upgrading won't help with testing that.

Posted: **Sun Sep 08, 2019 8:54 am**

OK, will do a couple of re installs - & an upgrade to satisfy my own curiosity.

Posted: **Sun Sep 08, 2019 9:21 am**

Having some trouble using the new Date and Time application, likely a user error thing, but still.

Pre install:
Ahead of installing I wanted to check a file on my external harddrive, the external one did not appear in the devices overview. Couldn't get there via /media either.
Libreoffice quickly flashed but didn't start.
The crowding of the icons in the system tray seems to be gone.

Post install:

I can see the other partitions and drive post install.
Libreoffice starts like normal post install.
System tray crowding issue is back

Posted: **Sun Sep 08, 2019 9:22 am**

<This is for asqwerth>

Installed fine, will test this morning. But first a snazzy new wallpaper (though I can never get the logo overlay to work)

BTW: that conky has an error in the time script but will be fixed as seen by the next update of mx-conky-data

Posted: **Sun Sep 08, 2019 9:25 am**

When I went to reboot I got two red text lines that went away real quick, but just before it shut down I could see a Plymouth error in red. Cannot remember exactly what it said though (back in 18.3 gathering my wimpy wits haha)

Posted: **Sun Sep 08, 2019 9:34 am**

can we expect a kde plasma version once mx 19 final is released? thanks

Posted: **Sun Sep 08, 2019 9:37 am**

small thing...volumeicon is grey vs. other icons white...

audioicon.png

EDIT: Installation is on hardware, not Live USB...

Posted: **Sun Sep 08, 2019 9:38 am**

I only have 1 problem left when i hit mute on the keyboard I have to go to pulseautio to un-mute it

Code: Select all

System:    Host: mx 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: Gigabyte product: Z97-D3H v: N/A serial: <filter> Chassis: 
           type: 3 serial: <filter> 
           Mobo: Gigabyte model: Z97-D3H-CF v: x.x serial: <filter> UEFI: American Megatrends 
           v: F9 date: 09/18/2015 
CPU:       Topology: Quad Core model: Intel Core i5-4440 bits: 64 type: MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: 27 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24798 
           Speed: 863 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1200 2: 1200 3: 1200 
           4: 1200 
           Vulnerabilities: Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           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: AMD Ellesmere [Radeon RX 470/480] vendor: Tul driver: amdgpu v: kernel 
           bus ID: 01:00.0 chip ID: 1002:67df 
           Display: x11 server: X.Org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: 
           renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Tul 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aaf0 
           Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus ID: 2-4:9 
           chip ID: 046d:0825 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I217-V vendor: Gigabyte driver: e1000e v: 3.2.6-k port: f040 
           bus ID: 00:19.0 chip ID: 8086:153b 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: e000 bus ID: 05:00.0 
           chip ID: 8086:24f3 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 5.00 TiB used: 309.09 GiB (6.0%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDH3500G size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 10RL scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-75ZF5A0 size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 0A80 scheme: MBR 
           ID-3: /dev/sdc vendor: Western Digital model: WD30EFRX-68EUZN0 size: 2.73 TiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0A82 scheme: GPT 
           ID-4: /dev/sdd vendor: Seagate model: ST1000LM010-9YH146 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: CC9F scheme: MBR 
Partition: ID-1: / raw size: 463.48 GiB size: 455.21 GiB (98.21%) used: 23.60 GiB (5.2%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 3.5 MiB (0.2%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 42.0 C mobo: 29.8 C gpu: amdgpu temp: 37 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1136 
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/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/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/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/wine.list 
           1: deb https://dl.winehq.org/wine-builds/debian/ buster main
Info:      Processes: 247 Uptime: 29m Memory: 15.60 GiB used: 1.85 GiB (11.8%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Posted: **Sun Sep 08, 2019 9:40 am**

mg2635599 wrote: Sun Sep 08, 2019 9:34 am can we expect a kde plasma version once mx 19 final is released? thanks

Not officially, although I suspect someone may make a spin.

Posted: **Sun Sep 08, 2019 9:42 am**

Eadwine Rose wrote: Sun Sep 08, 2019 9:21 am Having some trouble using the new Date and Time application, likely a user error thing, but still.

Pre install:
Ahead of installing I wanted to check a file on my external harddrive, the external one did not appear in the devices overview. Couldn't get there via /media either.
Libreoffice quickly flashed but didn't start.
The crowding of the icons in the system tray seems to be gone.

Post install:

I can see the other partitions and drive post install.
Libreoffice starts like normal post install.
System tray crowding issue is back

On you pre-installed scenario, had you already started the installer?

Posted: **Sun Sep 08, 2019 9:46 am**

Paul.. wrote: Sun Sep 08, 2019 9:37 am small thing...volumeicon is grey vs. other icons white...
audioicon.png

Is the volume muted perhaps?

Chris

Posted: **Sun Sep 08, 2019 9:54 am**

Trivial:

The Help file for MX Tweak>Other references the option to toggle Hibernate, which isn't supported in 19.

Chris

Posted: **Sun Sep 08, 2019 9:59 am**

chrispop99 wrote: Sun Sep 08, 2019 9:46 am
Paul.. wrote: Sun Sep 08, 2019 9:37 am small thing...volumeicon is grey vs. other icons white...
audioicon.png
Is the volume muted perhaps?

Chris

Originally yes, but un-muting doesn't change the color of the icon. I also noticed that the "notification" in the upper right of screen does not display the white bar (or any bar) showing the volume level or the percentage when I scroll the mouse wheel while hovering over the icon. It only shows a greyed-out notice "Volume Icon" and the icon itself.

Posted: **Sun Sep 08, 2019 10:07 am**

Paul.. wrote: Sun Sep 08, 2019 9:59 am
chrispop99 wrote: Sun Sep 08, 2019 9:46 am
Paul.. wrote: Sun Sep 08, 2019 9:37 am small thing...volumeicon is grey vs. other icons white...
audioicon.png
Is the volume muted perhaps?

Chris
Originally yes, but un-muting doesn't change the color of the icon. I also noticed that the "notification" in the upper right of screen does not display the white bar (or any bar) showing the volume level or the percentage when I scroll the mouse wheel while hovering over the icon. It only shows a greyed-out notice "Volume Icon" and the icon itself.

Right click the icon and close. The restart it in a terminal with

volumeicon &

And close the terminal. See if your volume.control returns

Posted: **Sun Sep 08, 2019 10:11 am**

dolphin_oracle wrote: Sun Sep 08, 2019 10:07 am Right click the icon and close. The restart it in a terminal with
volumeicon &

And close the terminal. See if your volume.control returns

Yup...volumeicon comes up as white and is fully functional...

Posted: **Sun Sep 08, 2019 10:12 am**

Paul.. wrote: Sun Sep 08, 2019 10:11 am
dolphin_oracle wrote: Sun Sep 08, 2019 10:07 am Right click the icon and close. The restart it in a terminal with
volumeicon &

And close the terminal. See if your volume.control returns
Yup...volumeicon comes up as white and is fully functional...

ok, will have to add back the old stretch mitigations to make volumeicon work more reliably. basically we need it to force starting up after pulseaudio. irritating...

Posted: **Sun Sep 08, 2019 10:18 am**

I actually like the newer pulseaudio panel plugin even though it has the unsightly big speaker icon and isn't part of the notification area. To me, it provides so much more functionality than volumeicon.

Posted: **Sun Sep 08, 2019 10:19 am**

I see no link to the download URL in the top post ?

edit: OK, found this announcement

Posted: **Sun Sep 08, 2019 10:22 am**

baldyeti wrote: Sun Sep 08, 2019 10:19 am I see no link to the download URL in the top post ?

there is an announcement post but I went ahead and added a download link.

Posted: **Sun Sep 08, 2019 10:29 am**

chrispop99 wrote: Sun Sep 08, 2019 9:54 am Trivial:

The Help file for MX Tweak>Other references the option to toggle Hibernate, which isn't supported in 19.

Chris

Not trivial as a general problem. I will go ahead and correct it, but it puts us Devs up against the question: now that most of the Help files are installed by default, how are we going to keep them in sync with updated versions to the online version? Similar situation with FAQS.

Posted: **Sun Sep 08, 2019 10:38 am**

actually, I didn't realize hibernate wasn't supported.

its still settable in Xfconf. just need to see what its not appearing in mx tweak.

Posted: **Sun Sep 08, 2019 10:49 am**

Paul.. wrote: Sun Sep 08, 2019 9:37 am small thing...volumeicon is grey vs. other icons white...
audioicon.png EDIT: Installation is on hardware, not Live USB...

grey := mute

Posted: **Sun Sep 08, 2019 11:06 am**

dolphin_oracle wrote: Sun Sep 08, 2019 10:38 am actually, I didn't realize hibernate wasn't supported.

its still settable in Xfconf. just need to see what its not appearing in mx tweak.

Originally Xfce 4.14 was meant to have a hybrid hibernation system, which on the face of it looked good, but I guess it didn't work.

Chris

Edit:

I enabled both Hibernate, and Hybrid Sleep in xconf; all they seem to do is log you out.

Posted: **Sun Sep 08, 2019 11:11 am**

chrispop99 wrote: Sun Sep 08, 2019 11:06 am
dolphin_oracle wrote: Sun Sep 08, 2019 10:38 am actually, I didn't realize hibernate wasn't supported.

its still settable in Xfconf. just need to see what its not appearing in mx tweak.
Originally Xfce 4.14 was meant to have a hybrid hibernation system, which on the face of it looked good, but I guess it didn't work.

Chris

Edit:

I enabled both Hibernate, and Hybrid Sleep in xconf; all they seem to do is log you out.

same here. might depend on systemd

Posted: **Sun Sep 08, 2019 11:12 am**

No external media (usb hdd) in Thunar side pane (Live session)

Install fails with format error - Selecting external USB HDD partition fails to format... after dismissing error dialog installer hangs

Code: Select all

System:    Host: mx18 Kernel: 4.9.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum March 14  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A 
           serial: <filter> 
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix 
           v: 03PA.M001.20110312.XW date: 03/12/2011 
Battery:   ID-1: BAT1 charge: 5.4 Wh condition: 5.4/47.5 Wh (11%) model: SAMSUNG Electronics 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem 
           rev: 5 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20217 
           Speed: 933 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 933 2: 933 3: 1066 4: 933 
Graphics:  Device-1: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: nouveau v: kernel 
           bus ID: 02:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel 
           v: kernel bus ID: 02:00.1 
           Sound Server: ALSA v: k4.9.0-11-amd64 
Network:   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter vendor: Askey 
           driver: bcma-pci-bridge v: N/A port: 2000 bus ID: 03:00.0 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co 
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 16.99 GiB (1.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB 
Partition: ID-1: / size: 49.26 GiB used: 16.99 GiB (34.5%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 49.0 C gpu: nouveau temp: 55 C 
           Fan Speeds (RPM): N/A 
/usr/bin/strings: Warning: could not locate '/sbin/init'.  reason: Permission denied
Info:      Processes: 192 Uptime: 1h 32m Memory: 5.70 GiB used: 681.6 MiB (11.7%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

Posted: **Sun Sep 08, 2019 11:20 am**

ChrisUK wrote: Sun Sep 08, 2019 11:12 am No external media (usb hdd) in Thunar side pane (Live session)

Install fails with format error - Selecting external USB HDD partition fails to format... after dismissing error dialog installer hangs

Code: Select all

System:    Host: mx18 Kernel: 4.9.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum March 14  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A 
           serial: <filter> 
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix 
           v: 03PA.M001.20110312.XW date: 03/12/2011 
Battery:   ID-1: BAT1 charge: 5.4 Wh condition: 5.4/47.5 Wh (11%) model: SAMSUNG Electronics 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem 
           rev: 5 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20217 
           Speed: 933 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 933 2: 933 3: 1066 4: 933 
Graphics:  Device-1: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: nouveau v: kernel 
           bus ID: 02:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel 
           v: kernel bus ID: 02:00.1 
           Sound Server: ALSA v: k4.9.0-11-amd64 
Network:   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter vendor: Askey 
           driver: bcma-pci-bridge v: N/A port: 2000 bus ID: 03:00.0 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co 
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 16.99 GiB (1.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB 
Partition: ID-1: / size: 49.26 GiB used: 16.99 GiB (34.5%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 49.0 C gpu: nouveau temp: 55 C 
           Fan Speeds (RPM): N/A 
/usr/bin/strings: Warning: could not locate '/sbin/init'.  reason: Permission denied
Info:      Processes: 192 Uptime: 1h 32m Memory: 5.70 GiB used: 681.6 MiB (11.7%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

did you plug it in before or after starting the installer?

Posted: **Sun Sep 08, 2019 11:22 am**

Jerry3904 wrote: Sun Sep 08, 2019 10:29 am
chrispop99 wrote: Sun Sep 08, 2019 9:54 am Trivial:

The Help file for MX Tweak>Other references the option to toggle Hibernate, which isn't supported in 19.

Chris
Not trivial as a general problem. I will go ahead and correct it, but it puts us Devs up against the question: now that most of the Help files are installed by default, how are we going to keep them in sync with updated versions to the online version? Similar situation with FAQS.

we have to update the apps. its the only way to do it and have them local.

I would prefer not to correct it at this time, as 18.3 is still stable. and still uses the online text (I think, not sure about that). I want to play around with the how's and whys of why hibernate isn't working first.

Posted: **Sun Sep 08, 2019 11:29 am**

dolphin_oracle wrote: Sun Sep 08, 2019 11:20 am [...]

did you plug it in before or after starting the installer?

Before - obviously available in the installer drop-down, but as I said, not in Thunar.

Posted: **Sun Sep 08, 2019 11:30 am**

actually hibernate appears to be working. our version of hibernate relies on more than just enabling the option in xfconf.

the bug is actually that the option doesn't appear in mx-tweak, which I can fix.

so no change to the help file necessary.

Posted: **Sun Sep 08, 2019 11:31 am**

dolphin_oracle wrote: Sun Sep 08, 2019 9:42 am
Eadwine Rose wrote: Sun Sep 08, 2019 9:21 am Having some trouble using the new Date and Time application, likely a user error thing, but still.

Pre install:
Ahead of installing I wanted to check a file on my external harddrive, the external one did not appear in the devices overview. Couldn't get there via /media either.
Libreoffice quickly flashed but didn't start.
The crowding of the icons in the system tray seems to be gone.

Post install:

I can see the other partitions and drive post install.
Libreoffice starts like normal post install.
System tray crowding issue is back
On you pre-installed scenario, had you already started the installer?

Actually yes I had..

Posted: **Sun Sep 08, 2019 11:32 am**

ChrisUK wrote: Sun Sep 08, 2019 11:29 am
dolphin_oracle wrote: Sun Sep 08, 2019 11:20 am [...]

did you plug it in before or after starting the installer?
Before - obviously available in the installer drop-down, but as I said, not in Thunar.

but you launched thunar after the installer?

the installer is using a new method to disable automounting, and it does remove entries from thunar while the installer is running, until the copylinux starts up anyway.

if you could post the /var/log/minstall.log, that would help track down the issue. there may be something unexepected with usb devices.

Posted: **Sun Sep 08, 2019 11:33 am**

Ahhh that is what happened here then too!

Posted: **Sun Sep 08, 2019 11:38 am**

dolphin_oracle wrote: Sun Sep 08, 2019 11:32 am [...]

but you launched thunar after the installer?

the installer is using a new method to disable automounting, and it does remove entries from thunar while the installer is running, until the copylinux starts up anyway.

if you could post the /var/log/minstall.log, that would help track down the issue. there may be something unexepected with usb devices.

Yes, Thunar was running before clicking Installer... but I'll try again tomorrow just to be sure (A bit busy ATM). Didn't install, so there's no /var/log/ let alone a minstall.log - or have I missed something?

Posted: **Sun Sep 08, 2019 11:45 am**

ChrisUK wrote: Sun Sep 08, 2019 11:38 am
dolphin_oracle wrote: Sun Sep 08, 2019 11:32 am [...]

but you launched thunar after the installer?

the installer is using a new method to disable automounting, and it does remove entries from thunar while the installer is running, until the copylinux starts up anyway.

if you could post the /var/log/minstall.log, that would help track down the issue. there may be something unexepected with usb devices.
Yes, Thunar was running before clicking Installer... but I'll try again tomorrow just to be sure (A bit busy ATM). Didn't install, so there's no /var/log/ let alone a minstall.log - or have I missed something?

the entries will disappear from thunar when the automount is disable, except for already mounted devices. I wonder if thunar is open if that's enough to prevent writing to the disk?

the log is generated on the live USB, so if you get a crash, grab the log.

Posted: **Sun Sep 08, 2019 11:47 am**

I just checked, no log on the Live USB

EDIT: You mean the virtual filesystem not the media

I'll try it all again tomorrow - also try another Laptop but same USB HDD

Posted: **Sun Sep 08, 2019 11:53 am**

Installations/re-installations. (beta2.1)

To HDD no problems

To SDHC card in built in reader/writer - gets auto mounted - unmount via installer disk partitioner, & it gets remounted - have to unmount it at the command line to be able to install.

To USB/pendrive - same as above - have to manually unmount it at the commandline.

(Upgrading from beta1 to beta2.1 seems to work OK.)

Posted: **Sun Sep 08, 2019 11:58 am**

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.

Posted: **Sun Sep 08, 2019 12:01 pm**

asqwerth wrote: Sun Sep 08, 2019 11:58 am 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. my bad. I thought I added it on.

2.1 had to be completely rebuilt to deal with the kernel change.

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

Posted: **Sun Sep 08, 2019 12:06 pm**

Cool. Thanks.

Posted: **Sun Sep 08, 2019 12:28 pm**

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?

Posted: **Sun Sep 08, 2019 12:32 pm**

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.

Posted: **Sun Sep 08, 2019 12:34 pm**

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

Posted: **Sun Sep 08, 2019 12:42 pm**

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) ...

Posted: **Sun Sep 08, 2019 12:59 pm**

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

Posted: **Sun Sep 08, 2019 1:48 pm**

dolphin_oracle wrote: Sun Sep 08, 2019 12:01 pm
asqwerth wrote: Sun Sep 08, 2019 11:58 am 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?

Posted: **Sun Sep 08, 2019 2:00 pm**

asqwerth wrote: Sun Sep 08, 2019 1:48 pm
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.

Posted: **Sun Sep 08, 2019 2:05 pm**

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

Posted: **Sun Sep 08, 2019 2:16 pm**

viewtopic.php?p=525919#p525919

Posted: **Sun Sep 08, 2019 2:22 pm**

Jerry3904 wrote: Sun Sep 08, 2019 2:16 pm viewtopic.php?p=525919#p525919

I remember you saying the notification was unreadable, didn't recall the set Default bit. And I don't remember having to change the notification theme setting in b1 to get matcha's theming to show up in the popup.

Posted: **Sun Sep 08, 2019 2:36 pm**

I tried to install using beta1 - yup, sorry i wanted to avoid the big download.
I had only tried frugal with beta1.
Booted from USB key, updated mx-installer (19.9.03).
Trying to install to sda20 on an MBR-partitioned disk, but the partition drop-down stops at sda15.
Is this a known problem (no i did not read all pages from the beta1 thread, but since the problem shows up even with what should be the latest installer, i thought i'd report)
I prepared my partition using gparted and rebooted once to retry and make sure the new partition table is committed.

Posted: **Sun Sep 08, 2019 2:38 pm**

Jerry3904 wrote: Sun Sep 08, 2019 2:16 pm viewtopic.php?p=525919#p525919

good catch to you too

Posted: **Sun Sep 08, 2019 2:42 pm**

baldyeti wrote: Sun Sep 08, 2019 2:36 pm I tried to install using beta1 - yup, sorry i wanted to avoid the big download.
I had only tried frugal with beta1.
Booted from USB key, updated mx-installer (19.9.03).
Trying to install to sda20 on an MBR-partitioned disk, but the partition drop-down stops at sda15.
Is this a known problem (no i did not read all pages from the beta1 thread, but since the problem shows up even with what should be the latest installer, i thought i'd report)
I prepared my partition using gparted and rebooted once to retry and make sure the new partition table is committed.

the latest installer shouldn't have the 15 partition problem. Our current test suit includes 2 devices, 1 with 21 patitions, the other with 4 partitions, and with encrypted partitions on each. the installer lists all 21 partitions on the one device.

Posted: **Sun Sep 08, 2019 2:54 pm**

I booted from USB once more to make sure. Beta1 had 19.8.06, which indeed has the same issue.
Is 19.9.03 _not_ the latest version (as included in beta2.1) ?

Code: Select all

2019-09-08 20:50:45.108 DBG default: Installer version: 19.9.03
2019-09-08 20:50:45.272 DBG default: +++ void MInstall::startup() +++
2019-09-08 20:50:45.272 DBG default: Exec #1: "du -sb /live/aufs/boot"
2019-09-08 20:50:45.312 DBG default: Exit #1: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:45.312 DBG default: Exec #2: "du -cb /live/aufs/bin /live/aufs/dev /live/aufs/etc /live/aufs/lib /live/aufs/lib64 /live/aufs/media /live/aufs/mnt /live/aufs/opt /live/aufs/root /live/aufs/sbin /live/aufs/selinux /live/aufs/usr /live/aufs/var /live/aufs/home | tail -n 1"
2019-09-08 20:50:52.128 DBG default: SErr #2: "du: cannot access '/live/aufs/selinux': No such file or directory\n"
2019-09-08 20:50:52.129 DBG default: Exit #2: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.129 DBG default: Minimum space: 268435456 (boot), 5234491392 (root)
2019-09-08 20:50:52.129 DBG default: Exec #3: "uname -m | grep -q i686"
2019-09-08 20:50:52.134 DBG default: Exit #3: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.135 DBG default: Exec #4: "test -d /sys/firmware/efi"
2019-09-08 20:50:52.142 DBG default: Exit #4: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.142 DBG default: uefi = false
2019-09-08 20:50:52.142 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2019-09-08 20:50:52.145 DBG default: Exec #5: "ps -e | grep 'udisksd'"
2019-09-08 20:50:52.172 DBG default: SOut #5: "   5360 ?        00:00:00 udisksd\n"
2019-09-08 20:50:52.172 DBG default: Exit #5: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.172 DBG default: Exec #6: "egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d"
2019-09-08 20:50:52.178 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2019-09-08 20:50:52.179 DBG default: Exit #6: 2 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.179 DBG default: Exec #7: "systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'"
2019-09-08 20:50:52.196 DBG default: Exit #7: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.196 DBG default: Exec #8: "mkdir -p /run/udev/rules.d"
2019-09-08 20:50:52.206 DBG default: Exit #8: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.206 DBG default: Exec #9: "touch "
2019-09-08 20:50:52.211 DBG default: SErr #9: "touch: missing file operand\nTry 'touch --help' for more information.\n"
2019-09-08 20:50:52.211 DBG default: Exit #9: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.212 DBG default: Exec #10: "echo 'SUBSYSTEM==\"block\", ENV{UDISKS_IGNORE}=\"1\"' > /run/udev/rules.d/90-udisks-inhibit.rules"
2019-09-08 20:50:52.216 DBG default: Exit #10: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.216 DBG default: Exec #11: "udevadm control --reload"
2019-09-08 20:50:52.232 DBG default: Exit #11: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.232 DBG default: Exec #12: "udevadm trigger --subsystem-match=block"
2019-09-08 20:50:52.267 DBG default: Exit #12: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.273 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2019-09-08 20:50:52.273 DBG default: Exec #13: "find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\\n"
2019-09-08 20:50:52.324 DBG default: Exit #13: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.325 DBG default: Exec #14: "locale -a | grep -Ev '^(C|POSIX)\\.?' | grep -E 'utf8|UTF-8'"
2019-09-08 20:50:52.363 DBG default: Exit #14: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:52.364 DBG default: Exec #15: "grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
2019-09-08 20:50:55.027 DBG default: Exit #15: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:55.027 DBG default: Exec #16: "/bin/ls -1 /home | grep -Ev '(lost\\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]"
2019-09-08 20:50:55.032 DBG default: Exit #16: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:55.033 DBG default: Exec #17: "test -d /live/linux/home/demo"
2019-09-08 20:50:55.034 DBG default: Exit #17: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:55.035 DBG default: Exec #18: "dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'"
2019-09-08 20:50:55.068 DBG default: Exit #18: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:50:55.068 DBG default: +++ void MInstall::buildServiceList() +++
2019-09-08 20:50:55.072 DBG default: +++ void MInstall::updatePartitionWidgets() +++
2019-09-08 20:50:55.072 DBG default: Exec #19: "/sbin/partprobe"
2019-09-08 20:51:04.685 DBG default: Exit #19: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:04.685 DBG default: Exec #20: "blkid -c /dev/null"
2019-09-08 20:51:06.639 DBG default: SOut #20: "/dev/sda1: LABEL=\"C-Shoebox\" UUID=\"5C911F3447455495\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-01\"\n/dev/sda2: LABEL=\"tank1\" UUID=\"11232821599605640233\" UUID_SUB=\"3401535660721932983\" TYPE=\"zfs_member\" PTUUID=\"90909090\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-02\"\n/dev/sda4: PTUUID=\"388a4ff0\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-04\"\n/dev/sda5: LABEL=\"D-Shoebox\" UUID=\"0C0FCA686495A631\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-05\"\n/dev/sda6: LABEL=\"E-Shoebox\" UUID=\"2845C22F0E994859\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-06\"\n/dev/sda7: LABEL=\"debian\" UUID=\"745d1e23-19fd-4e77-84cd-943898b62334\" SEC_TYPE=\"ext2\" TYPE=\"ext3\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-07\"\n/dev/sda8: LABEL=\"stretch\" UUID=\"c079d677-897b-44b4-af31-01dd44ccb066\" TYPE=\"ext4\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-08\"\n/dev/sda9: LABEL=\"linswap\" UUID=\"7b8b76fd-9ea6-40e6-8282-c029c8b7e387\" TYPE=\"swap\" PARTUUID=\"388a4ff0-09\"\n/dev/sda10: LABEL=\"SL6\" UUID=\"6010212d-58e8-4085-8393-05fe7ade73b3\" TYPE=\"ext4\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-0a\"\n/dev/sda11: LABEL=\"Archive-D\" UUID=\"C6D02F2ED02F2461\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-0b\"\n/dev/sda12: LABEL=\"Archive-E\" UUID=\"3C309C9F309C61A6\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-0c\"\n/dev/sda13: LABEL=\"Archive-C\" UUID=\"4C73B2163DAD364B\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-0d\"\n/dev/sda14: LABEL=\"wheezy\" UUID=\"5b91a69e-dbd3-475e-8c66-d960a292644e\" TYPE=\"ext4\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-0e\"\n/dev/sda15: LABEL=\"wheedata\" UUID=\"6ec3f1f0-2566-44a1-a272-37540ddd075f\" TYPE=\"ext4\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-0f\"\n/dev/sda16: LABEL=\"Media\" UUID=\"0EA226FFA226EB43\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-10\"\n/dev/sda17: LABEL=\"Backups\" UUID=\"cf267666-13e7-4245-935f-f0a475dc8bf7\" SEC_TYPE=\"ext2\" TYPE=\"ext3\" PARTUUID=\"388a4ff0-11\"\n/dev/sda18: LABEL=\"WinBak\" UUID=\"3D29C72D2BAD1ECF\" TYPE=\"ntfs\" PARTUUID=\"388a4ff0-12\"\n/dev/sda19: LABEL=\"jessie\" UUID=\"dfc28a38-1cf8-488a-ae5a-5862f0944880\" TYPE=\"ext4\" PTTYPE=\"dos\" PARTUUID=\"388a4ff0-13\"\n/dev/sda20: LABEL=\"MX19buster\" UUID=\"25b9f8f9-e02f-4d76-a3a2-d99e124b9c79\" TYPE=\"ext4\" PARTUUID=\"388a4ff0-14\"\n/dev/sdb1: LABEL_FATBOOT=\"BDelmee.128\" LABEL=\"MULTIBOOT\" UUID=\"E75F-3DF9\" TYPE=\"vfat\" PARTUUID=\"e70cb13d-01\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2019-09-08 20:51:06.639 DBG default: Exit #20: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:06.639 DBG default: Exec #21: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\  -f1 | cut -d/ -f3"
2019-09-08 20:51:06.834 DBG default: Exit #21: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:06.834 DBG default: Exec #22: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL |sed 's/├─//' |sed 's/└─//'  | grep -E '^(disk|part)'"
2019-09-08 20:51:06.854 DBG default: Exit #22: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:06.854 DBG default: Exec #23: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
2019-09-08 20:51:06.862 DBG default: Exit #23: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:06.863 DBG default: Exec #24: "blkid /dev/sdb | grep -q PTTYPE=\\\"gpt\\\""
2019-09-08 20:51:06.874 DBG default: Exit #24: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:06.874 DBG default: Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
2019-09-08 20:51:06.874 DBG default: "sda" 2000397852160 "WDC_WD20EARS-00MVWB0" "" | true false false false false false
2019-09-08 20:51:06.874 DBG default: "sda1" 251658236416 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.874 DBG default: "sda2" 16777216000 "" "zfs_member" | false false false false false false
2019-09-08 20:51:06.874 DBG default: "sda3" 1024 "" "" | false false false false false false
2019-09-08 20:51:06.874 DBG default: "sda4" 6291456000 "" "" | false false false false false false
2019-09-08 20:51:06.874 DBG default: "sda5" 268435452416 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.875 DBG default: "sda6" 268435452416 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.875 DBG default: "sda7" 11405357056 "" "ext3" | false false false false true false
2019-09-08 20:51:06.875 DBG default: "sda8" 13421772800 "" "ext4" | false false false false true false
2019-09-08 20:51:06.875 DBG default: "sda9" 4351582208 "" "swap" | false false false false true true
2019-09-08 20:51:06.875 DBG default: "sda10" 5992611840 "" "ext4" | false false false false true false
2019-09-08 20:51:06.875 DBG default: "sda11" 67108860416 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.875 DBG default: "sda12" 67108860416 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.875 DBG default: "sda13" 67108864000 "" "ntfs" | false false false false false false
2019-09-08 20:51:06.875 DBG default: "sda14" 8589934592 "" "ext4" | false false false false true false
2019-09-08 20:51:06.875 DBG default: "sda15" 8589934592 "" "ext4" | false false false false true false
2019-09-08 20:51:06.875 DBG default: "sdb" 123768668160 "USB_DISK_3.0" "" | true false true false false false
2019-09-08 20:51:06.875 DBG default: "sdb1" 123764539392 "" "vfat" | false false true false false false
2019-09-08 20:51:06.875 DBG default: "sda16" 268435456000 "" "ntfs" | false false true false false false
2019-09-08 20:51:06.875 DBG default: "sda17" 115498549248 "" "ext3" | false false true false true false
2019-09-08 20:51:06.875 DBG default: "sda18" 510978424832 "" "ntfs" | false false true false false false
2019-09-08 20:51:06.875 DBG default: "sda19" 21473787904 "" "ext4" | false false true false true false
2019-09-08 20:51:06.875 DBG default: "sda20" 18718130176 "" "ext4" | false false true false true false
2019-09-08 20:51:24.744 DBG default: +++ bool MInstall::abort(bool) +++
2019-09-08 20:51:24.752 DBG default: +++ void MInstall::cleanup(bool) +++
2019-09-08 20:51:24.752 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2019-09-08 20:51:24.752 DBG default: Exec #25: "ps -e | grep 'udisksd'"
2019-09-08 20:51:24.771 DBG default: SOut #25: "   5360 ?        00:00:00 udisksd\n"
2019-09-08 20:51:24.772 DBG default: Exit #25: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.772 DBG default: Exec #26: "egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d"
2019-09-08 20:51:24.776 DBG default: SErr #26: "grep: /lib/udev/rules.d: Is a directory\n"
2019-09-08 20:51:24.776 DBG default: Exit #26: 2 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.776 DBG default: Exec #27: "rm -f /run/udev/rules.d/90-udisks-inhibit.rules"
2019-09-08 20:51:24.780 DBG default: Exit #27: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.780 DBG default: Exec #28: "udevadm control --reload"
2019-09-08 20:51:24.787 DBG default: Exit #28: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.787 DBG default: Exec #29: "rm -f "
2019-09-08 20:51:24.791 DBG default: Exit #29: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.791 DBG default: Exec #30: "/bin/cp /var/log/minstall.log /mnt/antiX/var/log >/dev/null 2>&1"
2019-09-08 20:51:24.795 DBG default: Exit #30: 1 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.795 DBG default: Exec #31: "/bin/rm -rf /mnt/antiX/mnt/antiX >/dev/null 2>&1"
2019-09-08 20:51:24.798 DBG default: Exit #31: 0 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.798 DBG default: Exec #32: "/bin/umount -l /mnt/antiX/boot/efi"
2019-09-08 20:51:24.805 DBG default: SErr #32: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2019-09-08 20:51:24.805 DBG default: Exit #32: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.805 DBG default: Exec #33: "/bin/umount -l /mnt/antiX/proc"
2019-09-08 20:51:24.808 DBG default: SErr #33: "umount: /mnt/antiX/proc: no mount point specified.\n"
2019-09-08 20:51:24.809 DBG default: Exit #33: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.809 DBG default: Exec #34: "/bin/umount -l /mnt/antiX/sys"
2019-09-08 20:51:24.813 DBG default: SErr #34: "umount: /mnt/antiX/sys: no mount point specified.\n"
2019-09-08 20:51:24.813 DBG default: Exit #34: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.813 DBG default: Exec #35: "/bin/umount -l /mnt/antiX/dev/shm"
2019-09-08 20:51:24.818 DBG default: SErr #35: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2019-09-08 20:51:24.818 DBG default: Exit #35: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.818 DBG default: Exec #36: "/bin/umount -l /mnt/antiX/dev"
2019-09-08 20:51:24.821 DBG default: SErr #36: "umount: /mnt/antiX/dev: no mount point specified.\n"
2019-09-08 20:51:24.821 DBG default: Exit #36: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.821 DBG default: Exec #37: "/bin/umount -l /mnt/antiX/home"
2019-09-08 20:51:24.825 DBG default: SErr #37: "umount: /mnt/antiX/home: no mount point specified.\n"
2019-09-08 20:51:24.825 DBG default: Exit #37: 32 QProcess::ExitStatus(NormalExit)
2019-09-08 20:51:24.825 DBG default: Exec #38: "/bin/umount -lR /mnt/antiX"
2019-09-08 20:51:24.829 DBG default: SErr #38: "umount: /mnt/antiX: not found\n"
2019-09-08 20:51:24.829 DBG default: Exit #38: 1 QProcess::ExitStatus(NormalExit)

oddly enough, the partition from the USB key (sdb) appears between sda15 and sd16, perhaps that's the problem ?

Posted: **Sun Sep 08, 2019 3:40 pm**

on my system, partitions after 15 do show up out of order, but they do show up.

Posted: **Sun Sep 08, 2019 3:43 pm**

baldyeti wrote: Sun Sep 08, 2019 2:54 pm oddly enough, the partition from the USB key (sdb) appears between sda15 and sd16, perhaps that's the problem ?

The "isBoot" flag listed seems to be a bit odd:

Code: Select all

Name Size Model FS                             | isDisk isGPT isBoot isESP isNative isSwap
"sda" 2000397852160  "WDC_WD20EARS-00MVWB0" "" | true  false  false  false false    false
"sda1" 251658236416  "" "ntfs"                 | false false  false  false false    false
"sda2" 16777216000   "" "zfs_member"           | false false  false  false false    false
"sda3" 1024 "" ""                              | false false  false  false false    false
"sda4" 6291456000    "" ""                     | false false  false  false false    false
"sda5" 268435452416  "" "ntfs"                 | false false  false  false false    false
"sda6" 268435452416  "" "ntfs"                 | false false  false  false false    false
"sda7" 11405357056   "" "ext3"                 | false false  false  false true     false
"sda8" 13421772800   "" "ext4"                 | false false  false  false true     false
"sda9" 4351582208    "" "swap"                 | false false  false  false true     true
"sda10" 5992611840   "" "ext4"                 | false false  false  false true     false
"sda11" 67108860416  "" "ntfs"                 | false false  false  false false    false
"sda12" 67108860416  "" "ntfs"                 | false false  false  false false    false
"sda13" 67108864000  "" "ntfs"                 | false false  false  false false    false
"sda14" 8589934592   "" "ext4"                 | false false  false  false true     false
"sda15" 8589934592   "" "ext4"                 | false false  false  false true     false
"sdb" 123768668160   "USB_DISK_3.0" ""         | true  false  true   false false    false
"sdb1" 123764539392  "" "vfat"                 | false false  true   false false    false
"sda16" 268435456000 "" "ntfs"                 | false false  true   false false    false
"sda17" 115498549248 "" "ext3"                 | false false  true   false true     false
"sda18" 510978424832 "" "ntfs"                 | false false  true   false false    false
"sda19" 21473787904  "" "ext4"                 | false false  true   false true     false
"sda20" 18718130176  "" "ext4"                 | false false  true   false true     false

Starting from listed sdb the "isBOOT" shown as "true",

Code: Select all

Name Size Model FS                             | isDisk isGPT isBoot isESP isNative isSwap
"sdb" 123768668160   "USB_DISK_3.0" ""         | true  false  true   false false    false
"sdb1" 123764539392  "" "vfat"                 | false false  true   false false    false
"sda16" 268435456000 "" "ntfs"                 | false false  true   false false    false
"sda17" 115498549248 "" "ext3"                 | false false  true   false true     false
"sda18" 510978424832 "" "ntfs"                 | false false  true   false false    false
"sda19" 21473787904  "" "ext4"                 | false false  true   false true     false
"sda20" 18718130176  "" "ext4"                 | false false  true   false true     false

probably wrongly propagate from the real "isBOOT" device /dev/sdb or /dev/sdb1.
And by this the "isBOOT"-flagged devices are not listed as target install devices

Posted: **Sun Sep 08, 2019 3:47 pm**

Alright and what does 'minstall --version' report on beta2.1 (to make sure i received the very same version)

it's an old test system, its MBR boot is owned by windows, with stretch/grub (sda8) entry plugged using EasyBCD.
I intended to install MX19/buster to sda20, with its own grub only installed to sda20,
then regenerate the stretch gub.cfg to collect the newly installed MX.

Something that may be unusual: due to a long history of playing with this 2TB HDD, its partitions are not in physical order anymore - could that cause confusion ?

Posted: **Sun Sep 08, 2019 4:10 pm**

Another data point : i booted the same system again from USB/sdb, using an MX18_i386 version, and its installer (18.12.3) does show me all partitions.

Posted: **Sun Sep 08, 2019 4:19 pm**

baldyeti wrote: Sun Sep 08, 2019 3:47 pm Alright and what does 'minstall --version' report on beta2.1 (to make sure i received the very same version)

the 19.9.03 version.
The mentioned isBOOT flag issue has rather todo with the minstaller itself, not with the old disk or the devise name order.
IIRC, this issue was already addressed and mentioned as fixed.

Posted: **Sun Sep 08, 2019 4:44 pm**

External monitor didn't show on install or after.
Had to choose 'display' to have it show up.
Conky fails to show up (too pale) on external monitor set to default and can not move them about as before by hitting alt+.

Code: Select all

System:    Host: danielson 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: cairo-dock, 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: Laptop System: Hewlett-Packard product: HP EliteBook 8460p v: A0001D02 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 161C v: KBC Version 97.4E serial: <filter> 
           BIOS: Hewlett-Packard v: 68SCF Ver. F.65 date: 04/06/2017 
Battery:   ID-1: BAT0 charge: 27.2 Wh condition: 28.7/28.7 Wh (100%) volts: 12.4/11.1 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19954 
           Speed: 798 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
Graphics:  Device-1: AMD Seymour [Radeon HD 6400M/7400M Series] vendor: Hewlett-Packard 
           driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6760 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1600x900~60Hz, 1680x1050~60Hz 
           OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
           vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:1c20 
           Device-2: Logitech Headset H390 type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 3-1:2 chip ID: 046d:0a44 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: 5020 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel 
           port: 4000 bus ID: 25:00.0 chip ID: 8086:0085 
           IF: wlan0 state: down mac: <filter> 
           Device-3: ASIX AX88772B type: USB driver: asix bus ID: 2-1.1.2:6 chip ID: 0b95:772b 
           serial: <filter> 
           IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 5.48 GiB (2.5%) 
           ID-1: /dev/sda vendor: PNY model: CS1311 240GB SSD size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1122 scheme: MBR 
Partition: ID-1: / raw size: 54.25 GiB size: 53.15 GiB (97.97%) used: 5.48 GiB (10.3%) fs: ext4 
           dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 53.0 C mobo: 52.0 C gpu: radeon temp: 53 C 
           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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 209 Uptime: 35m Memory: 15.62 GiB used: 1.88 GiB (12.1%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Posted: **Sun Sep 08, 2019 4:53 pm**

What Conky? The default Conky shows up very well on the default wallpaper. If you want it on another wallpaper, use MX Conky to change the colors (details in the Help file)

Posted: **Sun Sep 08, 2019 5:13 pm**

I think fehlix hit on something with those bootflags. there is something wrong there. the installer won't show partitions on the boot device by default.

Posted: **Sun Sep 08, 2019 5:28 pm**

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.

Posted: **Sun Sep 08, 2019 5:30 pm**

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

Posted: **Sun Sep 08, 2019 5:50 pm**

looks like there might be a partial reversion of install fix. I'll have another to try in a little bit.

Posted: **Sun Sep 08, 2019 6:06 pm**

richb wrote: Sun Sep 08, 2019 5:28 pm 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.

Posted: **Sun Sep 08, 2019 6:59 pm**

fehlix wrote: Sun Sep 08, 2019 6:06 pm
richb wrote: Sun Sep 08, 2019 5:28 pm 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

Posted: **Sun Sep 08, 2019 7:13 pm**

Jerry3904 wrote: Sun Sep 08, 2019 4:53 pm What Conky? The default Conky shows up very well on the default wallpaper. If you want it on another wallpaper, use MX Conky to change the colors (details in the Help file)

After updates and reboot, conkies (which were previously invisible) all came back.
Depending on background image, some do clash while others are hard to make out.

- - - - -

Any word on alt+ alternatives to move conkies around?

Update: went to MX Conky and unchecked "all desktops" and checked off "Desktop 1" and things seem to work just as good as before.

Posted: **Sun Sep 08, 2019 7:14 pm**

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

Posted: **Sun Sep 08, 2019 7:19 pm**

baldyeti wrote: Sun Sep 08, 2019 5:30 pm 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

Posted: **Sun Sep 08, 2019 7:20 pm**

superduperuser wrote: Sun Sep 08, 2019 7:14 pm 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...

Posted: **Sun Sep 08, 2019 7:44 pm**

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?

Posted: **Sun Sep 08, 2019 8:06 pm**

richb wrote: Sun Sep 08, 2019 6:59 pm
fehlix wrote: Sun Sep 08, 2019 6:06 pm
richb wrote: Sun Sep 08, 2019 5:28 pm 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

Posted: **Sun Sep 08, 2019 8:17 pm**

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

Posted: **Sun Sep 08, 2019 8:27 pm**

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

Posted: **Sun Sep 08, 2019 8:33 pm**

Thanks for checking in -- welcome to the Forum!

Posted: **Sun Sep 08, 2019 8:37 pm**

richb wrote: Sun Sep 08, 2019 8:17 pm @fehlix Understand. So it is a known issue, not requiring further investigation.

Yes, issue known - Seattle

made.

Posted: **Sun Sep 08, 2019 9:03 pm**

fehlix wrote: Sun Sep 08, 2019 8:37 pm
richb wrote: Sun Sep 08, 2019 8:17 pm @fehlix Understand. So it is a known issue, not requiring further investigation.
Yes, issue known - Seattle made.

Do not understand the Seattle reference.

Posted: **Sun Sep 08, 2019 9:10 pm**

richb wrote: Sun Sep 08, 2019 9:03 pm
fehlix wrote: Sun Sep 08, 2019 8:37 pm
richb wrote: Sun Sep 08, 2019 8:17 pm @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.

Posted: **Sun Sep 08, 2019 9:44 pm**

fehlix wrote: Sun Sep 08, 2019 10:49 am
Paul.. wrote: Sun Sep 08, 2019 9:37 am small thing...volumeicon is grey vs. other icons white...
audioicon.png EDIT: Installation is on hardware, not Live USB...
grey := mute

viewtopic.php?p=526169#p526169

Posted: **Sun Sep 08, 2019 9:47 pm**

fehlix wrote: Sun Sep 08, 2019 9:10 pm
richb wrote: Sun Sep 08, 2019 9:03 pm
fehlix wrote: Sun Sep 08, 2019 8:37 pm
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.

Interesting. Uninformed question then. Why when I checked Local Time during the install process the resulting install did not exhibit the problem?

Posted: **Sun Sep 08, 2019 10:26 pm**

Is there any possibility that the new MX time & date app is interacting weirdly with the rest of the distro, thereby causing these issues in beta 2.1?

Just a completely non techie, off the shelf, thought .

Posted: **Sun Sep 08, 2019 10:48 pm**

MX Date & Time only runs when you run it, and will only change system settings when buttons are pushed. There are some known issues that are being worked on and should be fixed in an update soon.

Posted: **Sun Sep 08, 2019 11:55 pm**

USB Live.LibreOffice not start,just flash for a moment.

Posted: **Mon Sep 09, 2019 12:06 am**

Hi-

Looks very nice!

Don't know if this is intentional:

When the panels (transparent or not) are in "hidden" mode, they leave a white line on the screen where they are hidden.

and

Grub Customizer has to be installed manually.

Posted: **Mon Sep 09, 2019 12:28 am**

rej wrote: Mon Sep 09, 2019 12:06 am Hi-

Looks very nice!

Don't know if this is intentional:

When the panels (transparent or not) are in "hidden" mode, they leave a white line on the screen where they are hidden.

and

Grub Customizer has to be installed manually.

Due to various issues caused by Grub Customiser, it will not be a default program on the MX iso. Its use is not recommended. Use MX Boot Options for the basic grub settings tweaks. If you still want to use Grub Customiser, you'll have to install it yourself.

White line issue - Pls post a screenshot here.

Posted: **Mon Sep 09, 2019 12:35 am**

I tried the first beta and it would just not work. Put 18.3 back on, but wondering if it was worth it to try the next beta iteration?

Posted: **Mon Sep 09, 2019 12:40 am**

blindside wrote: Mon Sep 09, 2019 12:35 am I tried the first beta and it would just not work. Put 18.3 back on, but wondering if it was worth it to try the next beta iteration?

Only if you want to find bugs, report them, in the idea that bringing them to light might make it easier for devs to fix them. That's the purpose of betas.

Posted: **Mon Sep 09, 2019 12:49 am**

I would love to pitch in with any small way I could, and I know what a beta is. My thought on trying the newer beta is that it *just* might actually install on my machine. Like, is there anything that might have changed as far as it working with a brand new drive, and a brand new machine for the most part. It not being able to install was mind-boggling in the least.

Adrian wrote: Mon Sep 09, 2019 12:40 am
blindside wrote: Mon Sep 09, 2019 12:35 am I tried the first beta and it would just not work. Put 18.3 back on, but wondering if it was worth it to try the next beta iteration?
Only if you want to find bugs, report them, in the idea that bringing them to light might make it easier for devs to fix them. That's the purpose of betas.

Posted: **Mon Sep 09, 2019 12:58 am**

I don't know why it didn't install on your computer so I cannot tell you if the changes would influence that, but there were fixes in the installer. It's only you who can tell us if it installs on your computer, we cannot tell you if it will install on your computer. If it's too hard to test, then don't test it and cross the fingers that the official release will work.

Posted: **Mon Sep 09, 2019 1:00 am**

blindside wrote: Mon Sep 09, 2019 12:35 am I tried the first beta and it would just not work. Put 18.3 back on, but wondering if it was worth it to try the next beta iteration?

"Work" as in,

1) cannot even bootup, or
2) can boot up live but can't install?

If the latter, I'm sure the devs working on the installer like AK-47, fehlix, etc would love to hear from you, as your terminal output might help them squash even more bugs.

If 1), the live system devs would love to hear from you.

Posted: **Mon Sep 09, 2019 1:18 am**

Running from Live USB. Have found no problems so far. Did take a long time to get WiFi setup, needed driver unblacklisted.

Siles]

Posted: **Mon Sep 09, 2019 1:58 am**

dolphin_oracle wrote: Sun Sep 08, 2019 7:19 pm try this installer please:

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

Success ! I could install to sda20

One remark, when i chose to install grub to pbr , the drop-down did not defautl to the root i had chosen (sda20) but to the first linux-type partition (sda7)
I wanted to post the minstall.log, but the system rebooted at the end of installation (without prompting me)
Also i am a little surprised at the one-line fstab that was generated

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=6d78f48e-4c54-449d-9774-1a6dd5b15ec3 / ext4 defaults 1 1

edit: forget the remark about eagerly rebooting, i simply had not noticed the checkbox in the last installer screen (reboot immediately or something to that effect)

Posted: **Mon Sep 09, 2019 3:32 am**

First test on Samsung Laptop with Nvidia GFX

Clean install to existing partition.
Installed OK - auto-mounting and auto-opening a window for each partition appears to be fixed on Installer, but NOT on Thunar. So, if you're just exploring the Live session and plug in an external USB HDD a window opens for each partition... this might freak-out newish users with many partitions on external media.
All settings carried over from Live session to install

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A 
           serial: <filter> 
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix 
           v: 03PA.M001.20110312.XW date: 03/12/2011 
Battery:   ID-1: BAT1 charge: 5.4 Wh condition: 5.4/47.5 Wh (11%) model: SAMSUNG Electronics 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem 
           rev: 5 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20218 
           Speed: 1463 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 1464 2: 1463 3: 1463 
           4: 1463 
Graphics:  Device-1: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: nouveau v: kernel 
           bus ID: 02:00.0 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel 
           v: kernel bus ID: 02:00.1 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter vendor: Askey 
           driver: wl v: kernel port: 2000 bus ID: 03:00.0 
           IF: wlan0 state: dormant mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co 
           driver: r8169 v: kernel port: 4000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 5.09 GiB (0.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: MK2555GSX H size: 232.89 GiB 
Partition: ID-1: / size: 25.71 GiB used: 5.09 GiB (19.8%) fs: ext4 dev: /dev/sdb8 
Sensors:   System Temperatures: cpu: 57.0 C mobo: 57.0 C gpu: nouveau temp: 61 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 186 Uptime: 2m Memory: 5.69 GiB used: 485.0 MiB (8.3%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

First test on Toshiba Laptop with AMD GFX

Clean install to existing partition.
Installed OK - auto-mounting and auto-opening a window for each partition appears to be fixed on Installer, but NOT on Thunar. So, if you're just exploring the Live session and plug in an external USB HDD a window opens for each partition... this might freak-out newish users with many partitions on external media.
All settings carried over from Live session to install

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TOSHIBA product: Satellite L650D v: PSK1SE-00C00PEN 
           serial: <filter> 
           Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: Insyde v: 1.80 
           date: 06/29/2011 
Battery:   ID-1: BAT0 charge: 22.8 Wh condition: 23.1/47.5 Wh (49%) model: PA3817U-1BRS 
           status: Charging 
CPU:       Topology: Dual Core model: AMD Turion II P520 bits: 64 type: MCP arch: K10 rev: 3 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 9177 
           Speed: 800 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 800 2: 800 
Graphics:  Device-1: AMD RV710/M92 [Mobility Radeon HD 4530/4570/545v] 
           vendor: Toshiba America Info Systems driver: radeon v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD RV710 (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: Toshiba America Info Systems driver: snd_hda_intel 
           v: kernel bus ID: 00:14.2 
           Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series] 
           vendor: Toshiba America Info Systems driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8191SEvB Wireless LAN driver: rtl8192se v: kernel port: 3000 
           bus ID: 02:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet 
           vendor: Toshiba America Info Systems driver: atl1c v: 1.0.1.1-NAPI port: 2000 
           bus ID: 08:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 344.68 GiB used: 4.89 GiB (1.4%) 
           ID-1: /dev/sda vendor: Fujitsu model: MHW2120BH size: 111.79 GiB 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: MK2555GSX H size: 232.89 GiB 
Partition: ID-1: / size: 25.71 GiB used: 4.89 GiB (19.0%) fs: ext4 dev: /dev/sdb8 
Sensors:   System Temperatures: cpu: 59.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 156 Uptime: 4m Memory: 2.93 GiB used: 453.4 MiB (15.1%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

FN Keys for Brightness work out-of-the-box on AMD-based Laptop - Needed acpi_backlight=vendor etc to fix on Nvidia-based Laptop

Posted: **Mon Sep 09, 2019 3:39 am**

jorgosek wrote: Sun Sep 08, 2019 11:55 pm USB Live.LibreOffice not start,just flash for a moment.

Were you running liveUSB at the time AND running the installer, or?

Because I saw the same thing happen in that exact scenario.

Posted: **Mon Sep 09, 2019 3:41 am**

rej wrote: Mon Sep 09, 2019 12:06 am
Don't know if this is intentional:

When the panels (transparent or not) are in "hidden" mode, they leave a white line on the screen where they are hidden.

Could this be that you are running Compton or similar and have shadows (I believe that is what it is called) enabled?

Posted: **Mon Sep 09, 2019 4:21 am**

Needed acpi_backlight=vendor etc to fix on Nvidia-based Laptop

What's the "etc" part? Is this boot parameter something that needs to go in the Manual/Wiki?

Posted: **Mon Sep 09, 2019 4:40 am**

On a UEFI machine, updated from live, during install no disk is pre-selected for the user. The 'Use Disk' field is blank. Selecting 'Auto install using entire disk' with the 'Use Disk' field blank is permitted. The confirmation pop-up asks if disk(0) should be used. Clicking 'Yes' causes the installer to close. Launching the installer again, and trying to manually select a disk to install to fails because no disk can be selected; the field stays blank.

Re-booting, but not updating first allows installation to proceed normally, with the only disk in the machine appearing in the 'Use Disk@ filed.

Installation worked normally on this machine with 19b1.

Chris

Posted: **Mon Sep 09, 2019 4:55 am**

That's a known issue with the most recent version of the installer (19.9.05). You can check which version you have by running: minstall --version
The previous build (19.9.03) does not have this problem and is the one included in MX 19b2.1 so, just this time, try it without updating the installer.

Posted: **Mon Sep 09, 2019 4:58 am**

Jerry3904 wrote: Mon Sep 09, 2019 4:21 am
Needed acpi_backlight=vendor etc to fix on Nvidia-based Laptop
What's the "etc" part? Is this boot parameter something that needs to go in the Manual/Wiki?

Yeah, sorry, Jerry, I was in a rush again

Edit /etc/default/grub as root - change the line:

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux acpi_backlight=vendor"

Then do

Code: Select all

sudo update-grub

Posted: **Mon Sep 09, 2019 5:03 am**

On MX Date & Time > Hardware clock: Time zone for Hardware Clock shows neither choice checked. Yet one is functioning (UTC by default IIRC) and should already be checked IMO. The man file to hwclock says this will show which:

Code: Select all

     -l, --localtime
       -u, --utc
              Indicate which timescale the Hardware Clock is set to.

But for me I think that only provides the time:

Code: Select all

$ sudo hwclock --utc
2019-09-09 04:56:19.243412-04:00

Posted: **Mon Sep 09, 2019 5:59 am**

AK-47 wrote: Mon Sep 09, 2019 4:55 am That's a known issue with the most recent version of the installer (19.9.05). You can check which version you have by running: minstall --version
The previous build (19.9.03) does not have this problem and is the one included in MX 19b2.1 so, just this time, try it without updating the installer.

Thanks; things are happening so fast I'm having trouble keeping up!

Chris

Posted: **Mon Sep 09, 2019 6:31 am**

Thought i had "non-mobile" conky issue resolved with dual monitor, but after reboot this a.m., it would not move as usual with alt+
Went over again to MX Conky and unchecked "Desktop 1" to check it back again, and things work as before.
Not a huge issue, just an annoyance.

- - - - -

On the bright side of things... never saw MX boot up so fast!!!
(even faster than Solus - which up until now, had been the fastest on my system).

Posted: **Mon Sep 09, 2019 6:50 am**

chrispop99 wrote: Mon Sep 09, 2019 5:59 am
AK-47 wrote: Mon Sep 09, 2019 4:55 am That's a known issue with the most recent version of the installer (19.9.05). You can check which version you have by running: minstall --version
The previous build (19.9.03) does not have this problem and is the one included in MX 19b2.1 so, just this time, try it without updating the installer.
Thanks; things are happening so fast I'm having trouble keeping up!

Chris

Fixed one thing broke another! My bad.

Posted: **Mon Sep 09, 2019 6:57 am**

My external monitor either isn't being detected properly or isn't being used properly, resulting in a too-short panel. I'm booting a live USB with persist_all on a netbook with a 1024x600 internal screen and also an external 1280x1020 monitor connected which I'm using as my primary monitor. The second monitor displays the desktop and it's in Settings/Display, where I've set it as my primary monitor, yet the screen always has the panel only 600px high, and also the second monitor isn't showing up in Quick System Info. If I run MX Tweak and change the panel from vertical/left to horizontal/bottom then back again it changes to the full 1020px height, but that only lasts for the current session. I forgot to check whether both monitors' resolutions are shown in QSI after I do that.

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-6-686-pae i686 bits: 32 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_386 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Other-vm? System: AVERATEC product: N1130 v: N/A serial: <filter> 
           Chassis: No Enclosure type: 1 serial: <filter> 
           Mobo: AVERATEC model: N1130 serial: <filter> BIOS: Phoenix 
           v: NAPA0001.86C.0056.D.0907311757 date: 07/31/09 
Battery:   ID-1: BAT0 charge: 0.2 Wh condition: 0.2/2.1 Wh (10%) volts: 1.1/65.4 
           model: AVERATEC N1130 type: Li-ion serial: N/A status: Full 
CPU:       Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell 
           family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6384 
           Speed: 1205 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 821 2: 986 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 status: Not affected 
           Type: spectre_v2 status: Not affected 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:27ae 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-6-686-pae 
Network:   Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 
           port: 18e0 bus ID: 02:00.0 chip ID: 1814:3090 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           v: kernel port: 2000 bus ID: 04:00.0 chip ID: 10ec:8136 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 126.24 GiB used: 4.40 GiB (3.5%) 
           ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 61.3 
           scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 1.49 GiB used: 435.9 MiB (28.6%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 41.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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 182 Uptime: 9m Memory: 1.90 GiB used: 306.8 MiB (15.8%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Compare to an MX 18.3 live USB with persist_all, where everything works as expected:

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-5-686-pae i686 bits: 32 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_386 Continuum May 26  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Other-vm? System: AVERATEC product: N1130 v: N/A serial: <filter> 
           Mobo: AVERATEC model: N1130 serial: <filter> BIOS: Phoenix 
           v: NAPA0001.86C.0056.D.0907311757 date: 07/31/09 
Battery:   ID-1: BAT0 charge: 0.2 Wh condition: 0.2/2.1 Wh (10%) model: AVERATEC N1130 
           status: Full 
CPU:       Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell rev: 2 
           L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6385 
           Speed: 1253 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 1334 2: 1332 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-5-686-pae 
Network:   Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 
           port: 18e0 bus ID: 02:00.0 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           v: kernel port: 2000 bus ID: 04:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 119.29 GiB used: 1.41 GiB (1.2%) 
           ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB 
           ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 7.50 GiB 
Partition: ID-1: / size: 1.49 GiB used: 3.5 MiB (0.2%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 44.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/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.tw.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.tw.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.yzu.edu.tw/Linux/mx-workspace/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 171 Uptime: 3m Memory: 1.90 GiB used: 243.0 MiB (12.5%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

(Edited to make it clearer what the problem is.)

Posted: **Mon Sep 09, 2019 7:00 am**

I missed some news maybe.. I went and followed my instruction file to see if all is operational, and one of the things I do after installing nvidia is

Code: Select all

rm /etc/X11/xorg.conf

But it is not there.

Is it removed by default now?

In that same area, I haven't activated the screentearing fix yet, it seems to not be needed thus far, and neither is arandr to remember the screen positions. Of course that can still change after I have rebooted a few times more, time will tell.

Posted: **Mon Sep 09, 2019 7:43 am**

At some point the Synaptic icon disappeared from the notification area.
Ran MX Updater and it's back now.
Speaking of notification area, there is still crowding and overlapping going on.

Code: Select all

System:    Host: eadwinemx19beta2.1 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 Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102198 
           Speed: 1394 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1497 
           2: 1497 3: 1537 4: 1547 5: 1488 6: 1421 7: 1546 8: 1545 9: 1426 10: 1547 11: 1541 
           12: 1433 13: 1546 14: 1546 15: 1483 16: 1385 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 67.05 GiB (3.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.78 GiB (10.1%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 129.7 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 35.4 C mobo: 27.0 C gpu: nvidia temp: 36 C 
           Fan Speeds (RPM): cpu: 557 mobo: 225000 fan-2: 841 fan-3: 0 fan-4: fan-6: 0 
           gpu: nvidia fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 358 Uptime: 44m Memory: 31.41 GiB used: 1.49 GiB (4.8%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Posted: **Mon Sep 09, 2019 7:45 am**

Eadwine Rose wrote: Mon Sep 09, 2019 7:00 am I missed some news maybe.. I went and followed my instruction file to see if all is operational, and one of the things I do after installing nvidia is
Code: Select all
rm /etc/X11/xorg.conf
But it is not there.

Is it removed by default now?

its only generated for legacy 340 drivers now.

Posted: **Mon Sep 09, 2019 7:49 am**

Eadwine Rose wrote: Mon Sep 09, 2019 7:43 am [...]
Speaking of notification area, there is still crowding and overlapping going on.

Same here - seems like the Notification Area (System Tray) isn't expanding more than 4 icon widths, so others get squashed and are behind others

Posted: **Mon Sep 09, 2019 7:56 am**

I can see them all, but there are duplicates:

And the fun part is when you start something else the duplicate becomes something else.
At first it was the duplicate Yad icon behind the Synaptic one, now I installed and started Hotshots and the duplicate bluetooth icon hides behind that now.

snapshot.jpg

I put a separator between the area and the weather plugin in the image above, otherwise it'll look like this:

snapshot-1.jpg

To add, the two action buttons still don't want to stack on top of each other, one disappears. I wager that is an Xfce issue though, nothing we can do about it.

Posted: **Mon Sep 09, 2019 8:00 am**

I see that there are translations to Spanish that are not very organized, I am already checking them in Transifex for the final version.

Posted: **Mon Sep 09, 2019 8:02 am**

We can try to change the css, though I am not seeing this. Is it only when the panel is horizontal?

Posted: **Mon Sep 09, 2019 8:03 am**

dolphin_oracle wrote: Mon Sep 09, 2019 7:45 am
Eadwine Rose wrote: Mon Sep 09, 2019 7:00 am I missed some news maybe.. I went and followed my instruction file to see if all is operational, and one of the things I do after installing nvidia is
Code: Select all
rm /etc/X11/xorg.conf
But it is not there.

Is it removed by default now?
its only generated for legacy 340 drivers now.

Ah thank you :)

In that same area, I haven't activated the screentearing fix yet, it seems to not be needed thus far, and neither is arandr to remember the screen positions. Of course that can still change after I have rebooted a few times more, time will tell.

Posted: **Mon Sep 09, 2019 8:09 am**

Jerry3904 wrote: Mon Sep 09, 2019 8:02 am We can try to change the css, though I am not seeing this. Is it only when the panel is horizontal?

Looks like it.. I can start and close hotshots and things won't duplicate or crawl behind in the vertical one. It still is crowded though on the first four icons.

The separator between weather and notification area is not present and not needed in vertical.

snapshot.jpg

Mind, that is the nuvola icon theme running.

Posted: **Mon Sep 09, 2019 8:30 am**

TVtime, image is just fine, sound is VERY crackled. Just verified in Windows that sound is normal there, so it has to do with something in MX19beta2.1. I set pulseaudio up just like I did in MX18.3 and I THINK (iirc) that 19 beta1 was performing fine as well on those settings.

What changed, because that apparently messes something up on 19 beta2.1.

Hardware info:

Code: Select all

System:    Host: eadwinemx19beta2.1 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 Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102195 
           Speed: 1512 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1538 
           2: 1432 3: 1475 4: 1545 5: 1374 6: 1468 7: 1546 8: 1546 9: 1377 10: 1378 11: 1374 
           12: 1375 13: 1546 14: 1546 15: 1542 16: 1397 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 67.11 GiB (3.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.83 GiB (10.2%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 138.3 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 42.1 C mobo: 27.0 C gpu: nvidia temp: 34 C 
           Fan Speeds (RPM): cpu: 636 fan-2: 863 fan-3: 0 fan-4: 779 fan-6: 0 gpu: nvidia 
           fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 471 Uptime: 2m Memory: 31.41 GiB used: 1.06 GiB (3.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Posted: **Mon Sep 09, 2019 8:45 am**

dolphin_oracle wrote: Mon Sep 09, 2019 6:50 am
chrispop99 wrote: Mon Sep 09, 2019 5:59 am
AK-47 wrote: Mon Sep 09, 2019 4:55 am That's a known issue with the most recent version of the installer (19.9.05). You can check which version you have by running: minstall --version
The previous build (19.9.03) does not have this problem and is the one included in MX 19b2.1 so, just this time, try it without updating the installer.
Thanks; things are happening so fast I'm having trouble keeping up!

Chris
Fixed one thing broke another! My bad.

OK, give us a signal when a version is out to test, as I just tested with 19.9.03 on the ISO, but prefer not to report, as my finding might already have been fixed.

Posted: **Mon Sep 09, 2019 8:53 am**

fehlix wrote: Mon Sep 09, 2019 8:45 am
dolphin_oracle wrote: Mon Sep 09, 2019 6:50 am
chrispop99 wrote: Mon Sep 09, 2019 5:59 am

Thanks; things are happening so fast I'm having trouble keeping up!

Chris
Fixed one thing broke another! My bad.
OK, give us a signal when a version is out to test, as I just tested with 19.9.03 on the ISO, but prefer not to report, as my finding might already have been fixed.

19.09.03 has one set of problems, 19.09.05 has a different set. but we think we have a plan, probably.

Posted: **Mon Sep 09, 2019 8:56 am**

Eadwine Rose wrote: Mon Sep 09, 2019 3:39 am
jorgosek wrote: Sun Sep 08, 2019 11:55 pm USB Live.LibreOffice not start,just flash for a moment.
Were you running liveUSB at the time AND running the installer, or?

Because I saw the same thing happen in that exact scenario.

Running liveUSB(Kingston 4GB usb2) and I looked What News.I reported for information.Maybe it's important for DEV Team.

Posted: **Mon Sep 09, 2019 9:10 am**

Installation of a driver using the Nvidia driver installer on a dual graphics laptop fails. It works successfully on the same machine under 18.3.

During installation, accepting all defaults, the following message appears:

Screenshot-1.png

Proceeding with or without the checkbox selected makes no difference. After a reboot attempting to test the Nvida card results in the following:

Code: Select all

chris@mx19b2Nvidia:~/Desktop
$ optirun glxgears
[   43.535779] [ERROR]No bridge found. Try installing primus or virtualgl.

The graphics specification of the machine is as follows:

Code: Select all

$ inxi -G
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GF108GLM [NVS 5200M] driver: N/A 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6

Chris

Posted: **Mon Sep 09, 2019 9:15 am**

I am running 2.1 beta and have no issues. Reused /home and everything went well.

Code: Select all

System:    Host: ThinkCentre-M92p-2 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: LENOVO product: 3212CF7 v: ThinkCentre M92p serial: <filter> 
           Chassis: type: 3 serial: <filter> 
           Mobo: LENOVO model: MAHOBAY v: NOK serial: <filter> BIOS: LENOVO v: 9SKT9BAUS 
           date: 07/17/2018 
CPU:       Topology: Quad Core model: Intel Core i5-3550 bits: 64 type: MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26339 
           Speed: 1596 MHz min/max: 1600/3700 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 
           4: 1596 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           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: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 
           vendor: Bitland Information driver: radeon v: kernel bus ID: 01:00.0 
           chip ID: 1002:6779 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k 
           port: f040 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 13.98 GiB (1.5%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC57 scheme: MBR 
Partition: ID-1: / raw size: 32.23 GiB size: 31.47 GiB (97.65%) used: 5.75 GiB (18.3%) fs: ext4 
           dev: /dev/sda1 
           ID-2: /home raw size: 867.06 GiB size: 852.45 GiB (98.32%) used: 8.23 GiB (1.0%) 
           fs: ext4 dev: /dev/sda2 
           ID-3: swap-1 size: 32.23 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 39 C 
           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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 203 Uptime: 1h 33m Memory: 7.72 GiB used: 1.17 GiB (15.2%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Posted: **Mon Sep 09, 2019 9:17 am**

dolphin_oracle wrote: Mon Sep 09, 2019 8:53 am
fehlix wrote: Mon Sep 09, 2019 8:45 am
dolphin_oracle wrote: Mon Sep 09, 2019 6:50 am

Fixed one thing broke another! My bad.
OK, give us a signal when a version is out to test, as I just tested with 19.9.03 on the ISO, but prefer not to report, as my finding might already have been fixed.
19.09.03 has one set of problems, 19.09.05 has a different set. but we think we have a plan, probably.

Does the solution plan cover the issues related to the not yet fully fixed automount issue. If not I might prepare a report and a tested solution, prefable within another dev thread. If yes, I prefer rather to re-test the implemented solution....

Posted: **Mon Sep 09, 2019 9:24 am**

fehlix wrote: Mon Sep 09, 2019 9:17 am
dolphin_oracle wrote: Mon Sep 09, 2019 8:53 am
fehlix wrote: Mon Sep 09, 2019 8:45 am
OK, give us a signal when a version is out to test, as I just tested with 19.9.03 on the ISO, but prefer not to report, as my finding might already have been fixed.
19.09.03 has one set of problems, 19.09.05 has a different set. but we think we have a plan, probably.
Does the solution plan cover the issues related to the not yet fully fixed automount issue. If not I might prepare a report and a tested solution, prefable within another dev thread. If yes, I prefer rather to re-test the implemented solution....

that depends on what you are talking about.

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.)

Posted: **Mon Sep 09, 2019 9:38 am**

dolphin_oracle wrote: Mon Sep 09, 2019 9:24 am
fehlix wrote: Mon Sep 09, 2019 9:17 am
dolphin_oracle wrote: Mon Sep 09, 2019 8:53 am

19.09.03 has one set of problems, 19.09.05 has a different set. but we think we have a plan, probably.
Does the solution plan cover the issues related to the not yet fully fixed automount issue. If not I might prepare a report and a tested solution, prefable within another dev thread. If yes, I prefer rather to re-test the implemented solution....
that depends on what you are talking about.

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.)

Right, that was one part which I tested. So I might take the latest and see what it does.

Posted: **Mon Sep 09, 2019 10:15 am**

Installed on my Linx 1010B

Code: Select all

System:    Host: djh 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: Laptop System: LINX product: LINX1010B v: N/A serial: <filter> 
           Mobo: Type2 - Board model: Type2 - Board Product Name v: Type2 - Board Version 
           serial: <filter> UEFI: INSYDE v: LINX1010B.R22.03.010 date: 07/24/2015 
CPU:       Topology: Quad Core model: Intel Atom Z3735F bits: 64 type: MCP arch: Silvermont 
           family: 6 model-id: 37 (55) stepping: 8 microcode: 838 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10662 
           Speed: 1493 MHz min/max: 500/1833 MHz Core speeds (MHz): 1: 601 2: 544 3: 500 4: 500 
           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 Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 800x1280~60Hz 
           OpenGL: renderer: Mesa DRI Intel Bay Trail v: 4.2 Mesa 18.3.6 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel HDMI/DP LPE Audio driver: HdmiLpeAudio 
           message: bus/chip ids unavailable 
           Device-2: bytcr-rt5640 driver: bytcr-rt5640 message: bus/chip ids unavailable 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Message: No Device data found. 
           IF-ID-1: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 58.84 GiB used: 27.80 GiB (47.2%) 
           ID-1: /dev/mmcblk1 model: 032G72 size: 29.12 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 0x7 scheme: GPT 
           ID-2: /dev/mmcblk2 model: SC32G size: 29.72 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> scheme: MBR 
Partition: ID-1: / raw size: 26.84 GiB size: 26.29 GiB (97.96%) used: 5.41 GiB (20.6%) fs: ext4 
           dev: /dev/mmcblk1p2 
           ID-2: swap-1 size: 2.00 GiB used: 768 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/mmcblk1p3 
Sensors:   System Temperatures: cpu: 44.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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 199 Uptime: 26m Memory: 1.89 GiB used: 531.9 MiB (27.5%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

Everything is working except the screen brightness, this is the first time I have managed to install MX Linux on this device and I have not looked into the brightness issue yet, will update when I have.

This device has a 32bit efi and a 64bit cpu, so I generally have to do a lot of messing around to get anything other than Fedora up and running on it; MX 19 Beta 2.1 booted straight up - brilliant.

Update - I have not had success with the screen back light yet, I have discovered that the system does not recognise the battery whereby there is no discharge data. I am working on this, but any suggestions would be appreciated.

I have noted that brightness control does work when I boot to the Live environment.

Changed the kernel to 5.2.0-13.3-liquorix-amd64 from MX Package installer and I now have battery discharge data; now to work on the screen back light adjustment.

I found and installed a useful utility "brightness-controller-simple" I now have control of my brightness outside of CLI, however, not on the keyboard buttons, but it is a solution for now.

Thanks

Posted: **Mon Sep 09, 2019 10:20 am**

I downloaded the beta 2.1, md5 was good, so I burned it to the USB and installed. Live everything worked so I hit install, and 10 minutes later I was in the rebooted beta 2.1.
The install was normal, I used existing partitions, grub and install to root on my 4th 100G partition I use for testing.

First nvidia. I used the MX tools nvidia installer, no check for updates or backports. Installed and I rebooted to see an error message-

Code: Select all

KVM: disable by BIOS

That repeated maybe 115 lines, then something about a watchdog timer. Then the boot proceeded normally. A fresh boot weighs in at 518mB of RAM.

Then I tweaked the panel, added my data drive with disk manager, changed wallpaper, replaced conky with antiX, making 4 small tweaks.
Did synaptic updates, added 129 packages (including all the dependencies).
Customized firefox, all working youtube, sound, wired eth0.

I saw a mention of the MX time utility being new.
So I tried that. In the network tab, when I do a ntp synch, the new one does not show the offset that was changed. The old MX time would show the offset after running.

So, in summary, looks good, just that KVM: disable by BIOS error and the time synch not giving the offset.
I will make a few more tweaks tonight and test for stability. Before I installed, the beta1 had 9 days uptime with no crashes or hangs. So MX buster is looking solid.

Posted: **Mon Sep 09, 2019 10:28 am**

Due to various issues caused by Grub Customiser, it will not be a default program on the MX iso. Its use is not recommended. Use MX Boot Options for the basic grub settings tweaks. If you still want to use Grub Customiser, you'll have to install it yourself.

White line issue - Pls post a screenshot here.

Thank you, will try MX Boot Options

Posted: **Mon Sep 09, 2019 10:53 am**

Eadwine Rose wrote: Mon Sep 09, 2019 8:30 am TVtime, image is just fine, sound is VERY crackled. Just verified in Windows that sound is normal there, so it has to do with something in MX19beta2.1. I set pulseaudio up just like I did in MX18.3 and I THINK (iirc) that 19 beta1 was performing fine as well on those settings.

What changed, because that apparently messes something up on 19 beta2.1.

Hardware info:

Code: Select all

System:    Host: eadwinemx19beta2.1 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 Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102195 
           Speed: 1512 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1538 
           2: 1432 3: 1475 4: 1545 5: 1374 6: 1468 7: 1546 8: 1546 9: 1377 10: 1378 11: 1374 
           12: 1375 13: 1546 14: 1546 15: 1542 16: 1397 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 67.11 GiB (3.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.83 GiB (10.2%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 138.3 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 42.1 C mobo: 27.0 C gpu: nvidia temp: 34 C 
           Fan Speeds (RPM): cpu: 636 fan-2: 863 fan-3: 0 fan-4: 779 fan-6: 0 gpu: nvidia 
           fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
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/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 471 Uptime: 2m Memory: 31.41 GiB used: 1.06 GiB (3.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33

I just tried something suggested by AK-47, which was download the beta2.

Booted that liveUSB, didn't do anything to it, just installed tvtime and ran it and that was that.
Image and sound worked like a peach.
Installed the codecs and tested again, all was fine.

Booted the 2.1 liveUSB, just installed tvtime and ran it.
Image is fine, sound cracklecracklecrackle.

Something changed between 2 and 2.1 that is causing issues with tvtime here.

Posted: **Mon Sep 09, 2019 10:58 am**

the kernel, and therefore the audio drivers, are new on beta 2.1

the kernel on beta 2.1 is the current debian stable kernel.

Posted: **Mon Sep 09, 2019 10:59 am**

ok.. then I wager I am going to be a victim of having to run an older kernel or different audio drivers?

Posted: **Mon Sep 09, 2019 11:01 am**

Oh to add: other sound works fine. I ran an audio check "front left-front right", that one. No crackles. Do still have to test VLC and such though.

Posted: **Mon Sep 09, 2019 11:02 am**

Eadwine Rose wrote: Mon Sep 09, 2019 10:59 am ok.. then I wager I am going to be a victim of having to run an older kernel or different audio drivers?

don't know. there are some differences though, they bumped the abi on the kernel.

you could try killing pulseaudio and restarting it.

Code: Select all

pulseaudio -k
pulseaudio-start-x11

as user, not root.

Posted: **Mon Sep 09, 2019 11:03 am**

Ok will boot into 2.1 liveusb, do that and report back!

Posted: **Mon Sep 09, 2019 11:06 am**

I forgot I had the install of 2.1

Code: Select all

eadwine@eadwinemx19beta2.1:~
$ pulseaudio -k
eadwine@eadwinemx19beta2.1:~
$ pulseaudio-start-x11
bash: pulseaudio-start-x11: command not found
eadwine@eadwinemx19beta2.1:~
$

Posted: **Mon Sep 09, 2019 11:12 am**

Maybe

start-pulseaudio-X11

Posted: **Mon Sep 09, 2019 11:14 am**

Nope, that is not it either..

Posted: **Mon Sep 09, 2019 11:17 am**

start-pulseaudio-x11

(lowercase x...that's what I get for working from memory)

all this should do is restart pulseaudio.

Posted: **Mon Sep 09, 2019 11:23 am**

That worked.. unfortunately still crackles real badly, so that isn't solving this. VLC sound is normal.

Tried changing kernels (went to liquorix) by suggestion of AK-47, but that thing stopped at the text screen with a plymouth error. It did tell me that Logitech was there. Thank you yes I know.

Attached the log and we'll see, there are other fish to fry in this ocean of a topic

Posted: **Mon Sep 09, 2019 11:49 am**

Eadwine Rose wrote: Mon Sep 09, 2019 11:23 am That worked.. unfortunately still crackles real badly, so that isn't solving this. VLC sound is normal.

Tried changing kernels (went to liquorix) by suggestion of AK-47, but that thing stopped at the text screen with a plymouth error. It did tell me that Logitech was there. Thank you yes I know.

Attached the log and we'll see, there are other fish to fry in this ocean of a topic

you can also drop back to the kernel on beta 2. linux-image-4.19.0-5-amd64 for instance. and the headers of course. that entry is not in mxpi->popular apps, so probably easier in synaptic.

Posted: **Mon Sep 09, 2019 11:57 am**

Thanks :)

I would need some guidance on that, but I will ask AK-47 if he will help me with that on Slack. Don't want to hog the topic. At least we determined that the thing worked with the kernel that is on beta2.

Posted: **Mon Sep 09, 2019 4:38 pm**

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?

Posted: **Mon Sep 09, 2019 4:40 pm**

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

Posted: **Mon Sep 09, 2019 5:01 pm**

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

Posted: **Mon Sep 09, 2019 5:03 pm**

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.

Posted: **Mon Sep 09, 2019 5:08 pm**

Eadwine Rose wrote: Mon Sep 09, 2019 4:40 pm 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.

Posted: **Mon Sep 09, 2019 6:15 pm**

Jerry3904 wrote: Mon Sep 09, 2019 5:03 pm
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.

Posted: **Mon Sep 09, 2019 7:15 pm**

dolphin_oracle wrote: Mon Sep 09, 2019 9:24 am 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.

Posted: **Mon Sep 09, 2019 7:29 pm**

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..

Posted: **Mon Sep 09, 2019 8:21 pm**

fehlix wrote: Mon Sep 09, 2019 7:15 pm
dolphin_oracle wrote: Mon Sep 09, 2019 9:24 am 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.

Posted: **Mon Sep 09, 2019 8:25 pm**

dolphin_oracle wrote: Mon Sep 09, 2019 8:21 pm 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.

Posted: **Mon Sep 09, 2019 8:28 pm**

fehlix wrote: Mon Sep 09, 2019 8:25 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:21 pm 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.

see edits above. its intentional.

Posted: **Mon Sep 09, 2019 8:32 pm**

just tried the udisks2-inhibit approach. close out early still triggers an attempt to automount every partition in the machine. and those that don't require root passwords get automounted.

Posted: **Mon Sep 09, 2019 8:39 pm**

fehlix, the real question is...can be block just automounting without actually blocking devices?

Posted: **Mon Sep 09, 2019 8:41 pm**

dolphin_oracle wrote: Mon Sep 09, 2019 8:32 pm just tried the udisks2-inhibit approach. close out early still triggers an attempt to automount every partition in the machine. and those that don't require root passwords get automounted.

Propably, but I was not talking about automount after closing. Rather about current minstall does not allow to mount with thunar after closing. But prevents any automount during the run of minstall even without the udev-rules used within minstall at all.

Posted: **Mon Sep 09, 2019 8:42 pm**

dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?

is this meant during the "run" of minstall or after.

Posted: **Mon Sep 09, 2019 8:44 pm**

fehlix wrote: Mon Sep 09, 2019 8:42 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.

either way would actually work. during the active minstall run would mimic what we have in 18.3 by just disabling Xfce's automount.

Posted: **Mon Sep 09, 2019 9:00 pm**

fehlix wrote: Mon Sep 09, 2019 8:42 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.

what do you think of something like this, if it even still works. got it out of the depths of stackoverflow.

Code: Select all

echo 'SUBSYSTEM=="block", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/90-udisks-inhibit.rules

supposedly that disables automounting. it certainly leaves the list in place in thunar.

i tried with gparted in my test suite with some success, but I need more data points.

**never mind, didn't work in practice **

Posted: **Mon Sep 09, 2019 9:31 pm**

I've edited my post #106 on page 11 to make it clearer what the problem is. I originally posted it yesterday evening and upon rereading it this morning I realized that other people might not be able to understand what problem I was reporting. It seems that the x server isn't detecting my external monitor though Xfce detects it.

Posted: **Tue Sep 10, 2019 12:47 am**

I have just installed the latest MX Linux Beta ISO and I have found an issue.

Window cycling is just showing active windows, the minimized ones are not getting shown on Alt+Tab.

Is there a way to fix this problem?

Thanks in advance.

Edit: Fixed when checked the option "Include hidden (i.e. iconified) windows" on Window Manager Tweaks.

Posted: **Tue Sep 10, 2019 4:30 am**

I just tried changing to the Intel video driver instead of modset in MX Tweaks: no change after restarting. Also I found that the 1280x1020 resolution is still not showing up in QSI after using MX Tweak to change the panel to horizontal and back, which causes the panel to appear as normal on the external monitor for my current session (it doesn't survive a reboot or log out/log in.)

Posted: **Tue Sep 10, 2019 4:56 am**

I made some appearance changes, then used the User Manager tool to create a second user. I copied full configuration across to the new user.

When I log in as the new user, two speaker icons appear in the N/A. The original user does not have this problem. Rebooting doesn't fix it. If I untick the single entry for the speaker in the N/A properties dialogue, both speakers disappear.

speakers.png

Chris

Posted: **Tue Sep 10, 2019 6:44 am**

Also if the panel is vertical?

When you click them one at a time, are both the same app?

Posted: **Tue Sep 10, 2019 6:47 am**

This has been happening to me with MX-18.3 too. I just unticked the single entry for the speaker and both disappeared, since I don't need them.

Posted: **Tue Sep 10, 2019 6:51 am**

JayM wrote: Tue Sep 10, 2019 4:30 am I just tried changing to the Intel video driver instead of modset in MX Tweaks: no change after restarting. Also I found that the 1280x1020 resolution is still not showing up in QSI after using MX Tweak to change the panel to horizontal and back, which causes the panel to appear as normal on the external monitor for my current session (it doesn't survive a reboot or log out/log in.)

Instead of flipping the panel, could you just do

Code: Select all

xfce4-panel --restart

Posted: **Tue Sep 10, 2019 6:55 am**

chrispop99 wrote: Tue Sep 10, 2019 4:56 am I made some appearance changes, then used the User Manager tool to create a second user. I copied full configuration across to the new user.

When I log in as the new user, two speaker icons appear in the N/A. The original user does not have this problem. Rebooting doesn't fix it. If I untick the single entry for the speaker in the N/A properties dialogue, both speakers disappear.

speakers.png

Chris

Is the first user still logged in when you do this?

Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon

Posted: **Tue Sep 10, 2019 7:27 am**

Questions about antix Advert Blocker.
Could you explain why by visiting the sites you place to bookmark, the browser returns me that they are unsafe or that it has nothing to do with the subject?
I leave you the screenshots:

Posted: **Tue Sep 10, 2019 7:37 am**

Are you talking about antiX?

Posted: **Tue Sep 10, 2019 7:38 am**

antiX Adblocker is now in MX 19

Posted: **Tue Sep 10, 2019 7:40 am**

But what bookmarks?

Posted: **Tue Sep 10, 2019 7:51 am**

Jerry3904 wrote: Mon Sep 09, 2019 5:03 am On MX Date & Time > Hardware clock: Time zone for Hardware Clock shows neither choice checked. Yet one is functioning (UTC by default IIRC) and should already be checked IMO. The man file to hwclock says this will show which:
Code: Select all
     -l, --localtime
       -u, --utc
              Indicate which timescale the Hardware Clock is set to.
But for me I think that only provides the time:
Code: Select all
$ sudo hwclock --utc
2019-09-09 04:56:19.243412-04:00

Thanks for the report, finally got that fixed. Just waiting for a new build and an update. Hopefully the fix doesn't result in any regressions.

Posted: **Tue Sep 10, 2019 7:56 am**

Cool, glad that helped.

Posted: **Tue Sep 10, 2019 8:56 am**

dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Is the first user still logged in when you do this?

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon

The second user has 2 pulse audio entries, although one is unchecked:

user2.png

Here is the relevant part for the first user created:

user1.png

Chris

Posted: **Tue Sep 10, 2019 8:59 am**

chrispop99 wrote: Tue Sep 10, 2019 8:56 am
dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Is the first user still logged in when you do this?
It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon
The second user has 2 pulse audio entries, although one is unchecked:

user2.png

Here is the relevant part for the first user created:

user1.png

Chris

that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.

Posted: **Tue Sep 10, 2019 9:08 am**

dolphin_oracle wrote: Tue Sep 10, 2019 8:59 am
chrispop99 wrote: Tue Sep 10, 2019 8:56 am
dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Is the first user still logged in when you do this?
It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

dolphin_oracle wrote: Tue Sep 10, 2019 6:55 am Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon
The second user has 2 pulse audio entries, although one is unchecked:

user2.png

Here is the relevant part for the first user created:

user1.png

Chris
that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.

I just opened this to post I had tried what you have suggested!

If I uncheck the 2nd user's pulseaudio entry, so there are two entries unchecked, it all works fine even after a reboot, and whomever is logged in first.

Presumably there will be a way to fix it so that won't be needed?

Chris

Posted: **Tue Sep 10, 2019 9:42 am**

dolphin_oracle wrote: Mon Sep 09, 2019 9:00 pm
fehlix wrote: Mon Sep 09, 2019 8:42 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.
what do you think of something like this, if it even still works. got it out of the depths of stackoverflow.
Code: Select all
echo 'SUBSYSTEM=="block", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/90-udisks-inhibit.rules
supposedly that disables automounting. it certainly leaves the list in place in thunar.

i tried with gparted in my test suite with some success, but I need more data points.

**never mind, didn't work in practice **

The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule

Code: Select all

echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block

seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.

Posted: **Tue Sep 10, 2019 9:47 am**

chrispop99 wrote: Tue Sep 10, 2019 9:08 am
dolphin_oracle wrote: Tue Sep 10, 2019 8:59 am
chrispop99 wrote: Tue Sep 10, 2019 8:56 am

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

The second user has 2 pulse audio entries, although one is unchecked:

user2.png

Here is the relevant part for the first user created:

user1.png

Chris
that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.
I just opened this to post I had tried what you have suggested!

If I uncheck the 2nd user's pulseaudio entry, so there are two entries unchecked, it all works fine even after a reboot, and whomever is logged in first.

Presumably there will be a way to fix it so that won't be needed?

Chris

joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.

Posted: **Tue Sep 10, 2019 9:53 am**

dolphin_oracle wrote: Tue Sep 10, 2019 9:47 am
joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.

I'm only trying things to see if they break!

Chris

Posted: **Tue Sep 10, 2019 9:58 am**

chrispop99 wrote: Tue Sep 10, 2019 9:53 am
dolphin_oracle wrote: Tue Sep 10, 2019 9:47 am
joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.
I'm only trying things to see if they break!

Chris

and I apprecite it very much !!!!!!!!!!

that particular one won't break on release, rest assured!

Posted: **Tue Sep 10, 2019 10:01 am**

fehlix wrote: Tue Sep 10, 2019 9:42 am
dolphin_oracle wrote: Mon Sep 09, 2019 9:00 pm
fehlix wrote: Mon Sep 09, 2019 8:42 pm
is this meant during the "run" of minstall or after.
what do you think of something like this, if it even still works. got it out of the depths of stackoverflow.
Code: Select all
echo 'SUBSYSTEM=="block", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/90-udisks-inhibit.rules
supposedly that disables automounting. it certainly leaves the list in place in thunar.

i tried with gparted in my test suite with some success, but I need more data points.

**never mind, didn't work in practice **
The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule
Code: Select all
echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block
seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.

that's close. but the ones that I get asked to automount aren't the ones we are installing to anyway (there are already mounted), its other partitions and especially partitions on other devices.

Posted: **Tue Sep 10, 2019 10:05 am**

**never mind, I don't like what I wrote so I removed it**

Posted: **Tue Sep 10, 2019 10:27 am**

dolphin_oracle wrote: Tue Sep 10, 2019 10:01 am
fehlix wrote: Tue Sep 10, 2019 9:42 am
dolphin_oracle wrote: Mon Sep 09, 2019 9:00 pm

what do you think of something like this, if it even still works. got it out of the depths of stackoverflow.
Code: Select all
echo 'SUBSYSTEM=="block", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/90-udisks-inhibit.rules
supposedly that disables automounting. it certainly leaves the list in place in thunar.

i tried with gparted in my test suite with some success, but I need more data points.

**never mind, didn't work in practice **
The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule
Code: Select all
echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block
seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.
that's close. but the ones that I get asked to automount aren't the ones we are installing to anyway (there are already mounted), its other partitions and especially partitions on other devices.

On my system partprobe does not trigger automount, when nothing has changed. Only when kernel signals some changes,partpobe seems to triggers automount. The above example "hides" the changes hence at least on my system I get not automount triggered, even with having added partitions.

Posted: **Tue Sep 10, 2019 10:39 am**

fehlix wrote: Tue Sep 10, 2019 10:27 am
dolphin_oracle wrote: Tue Sep 10, 2019 10:01 am
fehlix wrote: Tue Sep 10, 2019 9:42 am
The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule
Code: Select all
echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block
seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.
that's close. but the ones that I get asked to automount aren't the ones we are installing to anyway (there are already mounted), its other partitions and especially partitions on other devices.
On my system partprobe does not trigger automount, when nothing has changed. Only when kernel signals some changes,partpobe seems to triggers automount. The above example "hides" the changes hence at least on my system I get not automount triggered, even with having added partitions.

I need to think about that one. I'm not sure where such a rule would be included, and how we deal with things before we know what devices are changed (in otherwords, when the user runs gparted from the installer).

Posted: **Tue Sep 10, 2019 10:56 am**

dolphin_oracle wrote: Tue Sep 10, 2019 10:39 am
fehlix wrote: Tue Sep 10, 2019 10:27 am
dolphin_oracle wrote: Tue Sep 10, 2019 10:01 am

that's close. but the ones that I get asked to automount aren't the ones we are installing to anyway (there are already mounted), its other partitions and especially partitions on other devices.
On my system partprobe does not trigger automount, when nothing has changed. Only when kernel signals some changes,partpobe seems to triggers automount. The above example "hides" the changes hence at least on my system I get not automount triggered, even with having added partitions.
I need to think about that one. I'm not sure where such a rule would be included, and how we deal with things before we know what devices are changed (in otherwords, when the user runs gparted from the installer).

If the above could be proved is working ( means hiding partitions changes made by minstall), we could regard the gparted-call to be identical as when called from the menu. So the user would have identical "gparted" experiences.
The above "hide" rules would only need to be added as soon as we know what partitions are involved ( i.e. before re-creation/re-formatting), e.g. just before that action and only at the end to be removed (if at all).

Posted: **Tue Sep 10, 2019 11:27 am**

fehlix wrote: Tue Sep 10, 2019 10:56 am
dolphin_oracle wrote: Tue Sep 10, 2019 10:39 am
fehlix wrote: Tue Sep 10, 2019 10:27 am
On my system partprobe does not trigger automount, when nothing has changed. Only when kernel signals some changes,partpobe seems to triggers automount. The above example "hides" the changes hence at least on my system I get not automount triggered, even with having added partitions.
I need to think about that one. I'm not sure where such a rule would be included, and how we deal with things before we know what devices are changed (in otherwords, when the user runs gparted from the installer).
If the above could be proved is working ( means hiding partitions changes made by minstall), we could regard the gparted-call to be identical as when called from the menu. So the user would have identical "gparted" experiences.
The above "hide" rules would only need to be added as soon as we know what partitions are involved ( i.e. before re-creation/re-formatting), e.g. just before that action and only at the end to be removed (if at all).

so maybe hide everything until the installer actually launches, then remove the rule that hides everything and then put in place the new rule above, reload the rules, partprobe, and see what happens.

Posted: **Tue Sep 10, 2019 12:04 pm**

The orage preferences that I set (from the whisker menu) seem to have no influence at all at the layout of the calendar that I see when I click on the clock in the panel.
Any idea how to fix this? I would like to remove the week numbers.

Posted: **Tue Sep 10, 2019 12:16 pm**

phykris wrote: Tue Sep 10, 2019 12:04 pm The orage preferences that I set (from the whisker menu) seem to have no influence at all at the layout of the calendar that I see when I click on the clock in the panel.
Any idea how to fix this? I would like to remove the week numbers.

are you using the orage clock plugin? by default, we are not.

Posted: **Tue Sep 10, 2019 12:22 pm**

phykris wrote: Tue Sep 10, 2019 12:04 pm The orage preferences that I set (from the whisker menu) seem to have no influence at all at the layout of the calendar that I see when I click on the clock in the panel.
Any idea how to fix this? I would like to remove the week numbers.

Yes, bc the default clock/calendar in the panel is not the orage calender/clock but the xfce4-datetime-plugin.

clocks.png

Not sure how to hide week-numbers within xfce4-datetime calendar.

Posted: **Tue Sep 10, 2019 12:52 pm**

The calendar is a gtk widget. Looking at the documentation here, I see there is a way to hide the week numbers, but the method would take some snooping around. You can use the Orage Panel Clock plugin instead.

I made a request on the Xfce Forum where you can keep track of responses.

Posted: **Tue Sep 10, 2019 1:41 pm**

On a fresh install of beta 2.1 here, I decided to first test out the vsync thing in mx tweak - compositor because my second monitor is not displaying correctly (resolution is correct but it is smaller in size than the screen itself) and AK-47 told me to try that. Well, it doesn't help that bit, however as soon as I changed it a second volume icon popped up right above the other one (or below).

One on top has the slider all the way up, the other one has it all the way down.

I don't think that is supposed to happen?

Posted: **Tue Sep 10, 2019 2:04 pm**

Another thingie is going on: gdebi isn't behaving like it should. Noticed this on the earlier install but went meh. Want to report it anyway.

I wanted to install the .deb for Slack-desktop (that thing is not in the repos), so I right click it to open with Gdebi and it just sits there doing nothing, so it seems, indefinitely. Screen empty and all:

Screenshot.png

Now, if I go to file - open and navigate to the .deb it WILL call in what I want to see:

Screenshot-1.png

Posted: **Tue Sep 10, 2019 2:20 pm**

I added some extra info, about LibreOffice not starting, to my reaction #141.

Posted: **Tue Sep 10, 2019 2:26 pm**

Just clucking on the deb works though, right?

Posted: **Tue Sep 10, 2019 2:34 pm**

Matcha theme uses around 100 MB more than default Arc theme, is that expected?

Posted: **Tue Sep 10, 2019 2:38 pm**

Jerry3904 wrote: Tue Sep 10, 2019 2:26 pm Just clucking on the deb works though, right?

*cluckcluck*

hehe sorry couldn't help it..

lessee..

Nope, doesn't work either, same result.

I wanted to try with a different file but this is the only .deb I have. I can send it to you via Slack if you want to try it? (if that is possible)

Posted: **Tue Sep 10, 2019 2:46 pm**

Not really. Gdebi works fine for me on 64 bit.

Posted: **Tue Sep 10, 2019 2:50 pm**

OK.. ah well.. I can get it working, so no biggie :)

Posted: **Tue Sep 10, 2019 4:07 pm**

Looks pretty good so far on my VM. Still getting a laugh out of the "patito feo" release name. :D

Posted: **Tue Sep 10, 2019 4:12 pm**

chrispop99 wrote: Mon Sep 09, 2019 9:10 am Installation of a driver using the Nvidia driver installer on a dual graphics laptop fails. It works successfully on the same machine under 18.3.

During installation, accepting all defaults, the following message appears:

Screenshot-1.png

Proceeding with or without the checkbox selected makes no difference. After a reboot attempting to test the Nvida card results in the following:
Code: Select all
chris@mx19b2Nvidia:~/Desktop
$ optirun glxgears
[   43.535779] [ERROR]No bridge found. Try installing primus or virtualgl.
The graphics specification of the machine is as follows:
Code: Select all
$ inxi -G
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GF108GLM [NVS 5200M] driver: N/A 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6 
Chris

what driver gets installed under 18.3?

Posted: **Tue Sep 10, 2019 4:19 pm**

nixy wrote: Tue Sep 10, 2019 2:34 pm Matcha theme uses around 100 MB more than default Arc theme, is that expected?

might need to update the icon cache, which I forget how to do at the moment but usually makes a big difference to ram. If that's the problem anyway.

Posted: **Tue Sep 10, 2019 5:40 pm**

I have 8 partitions on this Intel Nuc, with Mint 19.2 Mate the boot distro on sda2. I tried both MX 19 b1 & b2.1 and both wiped Mate & came up with a Grub prompt. I had MX 18.3 and wiped it before trying the Betas. On the 'Choose Partitions' I put Home to sda6. Swap is 2GB on sda1. I didn't notice the the label on root said "rootMX" The next screen says the installer will FORMAT & DESTROY data on these partitions. sda2 for /, sda6 for /home, & sda1 for MX swap. I don't want the installer to format my Boot partition (sda2)! Looks to me that it's a misnomer to say your can put MX on any partition you select. What am I doing wrong? Thanks, 2jcm.

MX Linux Forum

MX-19 Beta 2.1 Feedback

MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

(cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: (cannot install to sda20)

Re: (cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: (cannot install to sda20)

Re: (cannot install to sda20)

Re: (cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: (cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: (cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback