MX-19 Beta 1 Feedback

[danielson]

Great!

-Secondary (external) monitor failed to show up at initial boot from usb as well as after installation.
Did however work when selected from display.
-Cairo-dock installed and worked as expected (always a worry when "upgrading")!
-Conky can no longer be moved while selected and holding alt.

So much to discover!!

Thanks MX guys and gals for the hard work! :)

[Jerry3904]

Conky can no longer be moved while selected and holding alt.

I had noticed that too, and can confirm. I thought it might be b/c the compositor is now enabled by default, but turning it off did not solve it (though maybe I needed to log out/in, will try again later).

[Gaer Boy]

Beta runs fine live on laptop and desktop. Installation to laptop (Thinkpad X220) clean and most things I use regularly work as expected.

I have the same problem with installation to the desktop as I had with a4. On the first installer screen, there's a popup request for root password to mount sda2. Whether I enter the password or cancel, Thunar proceeds to mount 13 partitions and open instances for each. At about 4 sec intervals, I have to sit and wait for a minute and then clear them before I can proceed with installation.

I avoided the problem by disabling Volume Management in Thunar on the live system before installation. I don't see why this works - I thought Volume Management only affected plugged-in drives and the mounted partitions are on 2 of my 3 fixed disks.

I have 28 partitions in total - 7 on sda (SSD, ESP + 6 ext4), 11 on sdb (HDD, 3 primary ext4, 5 ext4 + 1 ntfs + 1 swap) and 10 on sdc (3 primary ext4, 5 ext4 + 1 ntfs). sdb is mainly a data disk and sdc is used for internal backup. Thunar mounted all the sdc partitions, none of the sdb partitions and 4 of the sda primary partitions. There doesn't seem to be any logic here. I identified all the partitions by UUID to eliminate any confusion.

I'm leaving any testing of b1 until I can resolve this.

[ChrisUK]

As above trying to install, problem with Thunar mounting all partitions... close a window, and it opens again - desktop full of Thunar windows. Solved same way by disabling Volume Management and starting Installation again.

Successfully installed on the following Laptop - all OK so far, except FN Brightness keys not working (not investigated yet, just reporting not working out of the box like MX16/17/18)

Code: Select all

           Desktop: Xfce 4.14.1 Distro: MX-19beta-1_x64 patito feo August 25  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: 6.3 Wh condition: 6.5/47.5 Wh (14%) model: SAMSUNG Electronics 
           status: Unknown 
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: 1463 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 1463 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-5-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: up 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.22 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.22 GiB (20.3%) fs: ext4 dev: /dev/sdb8 
Sensors:   System Temperatures: cpu: 59.0 C mobo: 59.0 C gpu: nouveau temp: 62 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: 190 Uptime: 1m Memory: 5.69 GiB used: 464.7 MiB (8.0%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33 

[Jerry3904]

On the first installer screen, there's a popup request for root password to mount sda2

I saw that as well, so just exited the installer, then started it again and didn't see it after that.

[fehlix]

As above trying to install, problem with Thunar mounting all partitions... close a window, and it opens again - desktop full of Thunar windows. Solved same way by disabling Volume Management and starting Installation again.

So the automounts (and the corresponding popup's) are triggered after starting the installer, right?

[Jerry3904]

For me: right after starting.

[dolphin_oracle]

Beta runs fine live on laptop and desktop. Installation to laptop (Thinkpad X220) clean and most things I use regularly work as expected.

I have the same problem with installation to the desktop as I had with a4. On the first installer screen, there's a popup request for root password to mount sda2. Whether I enter the password or cancel, Thunar proceeds to mount 13 partitions and open instances for each. At about 4 sec intervals, I have to sit and wait for a minute and then clear them before I can proceed with installation.

I avoided the problem by disabling Volume Management in Thunar on the live system before installation. I don't see why this works - I thought Volume Management only affected plugged-in drives and the mounted partitions are on 2 of my 3 fixed disks.

I have 28 partitions in total - 7 on sda (SSD, ESP + 6 ext4), 11 on sdb (HDD, 3 primary ext4, 5 ext4 + 1 ntfs + 1 swap) and 10 on sdc (3 primary ext4, 5 ext4 + 1 ntfs). sdb is mainly a data disk and sdc is used for internal backup. Thunar mounted all the sdc partitions, none of the sdb partitions and 4 of the sda primary partitions. There doesn't seem to be any logic here. I identified all the partitions by UUID to eliminate any confusion.

I'm leaving any testing of b1 until I can resolve this.

please post the /var/log/minstall.log file. we've included a lot more debugging output to track down this sort of thing. we may need to disable automounting earlier for instance. also, is that without any input or did you run gparted at some point, either from inside the installer or from outside the installer.

[dolphin_oracle]

I can't reproduce the issue here, so going to need those logs...

[Jerry3904]

I will look as well, but aren't those logs lost as soon as the Live session ends and the user removes the USB?