MX-19 Beta 3 Feedback

[Srdjan]

When XFCE Terminal is opened, prompt is at new line, rather then inline (default Terminal setting).

(wishlist, not a bug :) )

[dreamer]

When XFCE Terminal is opened, prompt is at new line, rather then inline (default Terminal setting).
(wishlist, not a bug :) )

I like how it is now. Looks clean.

A few things:

1. antiX repo has no release file, will not refresh, at least not a couple of days ago
2. MX Boot Options will not disable Plymouth despite the option being there. Only uninstalling Plymouth packages makes it go away.
3. Xfce 4.14 has weird placement of notifications. If panel is at the top the notification will cover the panel. This is not the case in Xfce 4.12. Seems the grid for notifications has changed.

[Jerry3904]

Got it, thanks. You can change the location of the notifications in Settings > Notifications

[dreamer]

Got it, thanks. You can change the location of the notifications in Settings > Notifications

There are only 4 settings:
Top right
Top left
Bottom right
Bottom left

In Xfce 4.14 they are all wrong, meaning they cover a panel that is placed at the top or bottom. There is supposed to be empty space between panel and notification. Notifications shouldn't cover a panel no matter which side a panel is attached to. It works well in Xfce 4.12.

[Jerry3904]

Maybe there is some dependence on resolution. On my test machine, I am unable to make the notifications cover the panel when it is at the top or bottom, no matter how big I make the panel(went up to 70).

[halw]

Wifi will not connect.

Edit: After rebooting the live image, was able to connect to wifi. Not sure what the difference, if any was.

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 4177CTO v: ThinkPad T420 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 4177CTO serial: <filter> UEFI: LENOVO v: 83ET82WW (1.52 ) 
           date: 06/04/2018 
Battery:   ID-1: BAT0 charge: 40.2 Wh condition: 42.8/47.5 Wh (90%) volts: 12.0/10.8 
           model: SANYO 42T4763 type: Li-ion serial: <filter> status: Discharging 
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: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19936 
           Speed: 801 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 797 2: 797 3: 797 4: 797 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; 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: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           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: 5080 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel 
           port: efa0 bus ID: 03:00.0 chip ID: 8086:0085 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.37 TiB used: 1.50 GiB (0.1%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 QVO 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO mSATA 500GB size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B6Q 
           scheme: GPT 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer Fit size: 7.45 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 12.38 GiB used: 90.4 MiB (0.7%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 3238 
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: 210 Uptime: 31m Memory: 15.55 GiB used: 901.9 MiB (5.7%) 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.36 

[Adrian]

2. MX Boot Options will not disable Plymouth despite the option being there. Only uninstalling Plymouth packages makes it go away.

Can't really replicate it, I tried it right now, installed MX-19 B3, rebooted to installed, started MX Boot Options, unchecked Theme -> Enable Theme and apply, it removed the "splash" boot parameter and the reboot I don't see the Plymouth splash anymore. What happens for you, do you still have that "splash" in the boot arguments?

[dreamer]

Maybe there is some dependence on resolution. On my test machine, I am unable to make the notifications cover the panel when it is at the top or bottom, no matter how big I make the panel(went up to 70).

OK, sounds good. I'm using a 1920x1200 display and notification does cover the top panel which is set to 38. This is beta 2.1 so I will take a new look when I'm up to date.

[dreamer]

2. MX Boot Options will not disable Plymouth despite the option being there. Only uninstalling Plymouth packages makes it go away.

Can't really replicate it, I tried it right now, installed MX-19 B3, rebooted to installed, started MX Boot Options, unchecked Theme -> Enable Theme and apply, it removed the "splash" boot parameter and the reboot I don't see the Plymouth splash anymore. What happens for you, do you still have that "splash" in the boot arguments?

I followed those steps, unchecked Enable Theme and Apply. I don't know if it removed splash parameter, I just noticed that Plymouth was still working both during shut down phase and the next boot. So I uninstalled plymouth packages instead and then it was gone. This was beta 2.1 so obsolete now. I thought I would report it anyway since apps are not that tied to a specific MX version. I'm glad MX Boot Options does not depend on plymouth packages, but instead asks to install them if they aren't present on the system. Very nice behavior.

I will try this again with an up to date version of MX. I guess we can consider it solved for now.

Maybe you can tell me where I should look for the splash parameter?

[Adrian]

Yeah, it's normal to still show when it shuts down but at reboot it shouldn't be there anymore, if you see this again, can you please let me know if you still see the "splash" in the boot options line? That shows both in mx-boot-options "kernel parameters line" and more importantly it's in the "linux" line in /boot/grub/grub.conf you could check that with a one liner:

Code: Select all

grep splash /boot/grub/grub.cfg

If you see some output there it means the key word is present.