MX-19 Beta 2.1 Feedback

[chrispop99]

Whereas the option "Bildschirmfüllend" (sorry don't know the english option name for stretching one picture over all screens), is definitely in 18.3 and seems to be missing in the beta. Which of course could be a regression in the new XFCE version, but I'm just a simple user who noted that one of the first options usually set by me on any system is missing

The option to stretch one wallpaper across two screens is still there in Xfce 4.14 (and thus in MX-19). In English it is called 'Spanning screens'.

scr.jpg

(Added)

Note that the entry in the dialogue for 'Spanning screens' only appears when you open the Desktop Settings on the primary screen.


Chris

[Croton]

The option to stretch one wallpaper across two screens is still there in Xfce 4.14 (and thus in MX-19). In English it is called 'Spanning screens'.
(Added)

Note that the entry in the dialogue for 'Spanning screens' only appears when you open the Desktop Settings on the primary screen.

Thank you very much - That may very well explain why I didn't found it

[dolphin_oracle]

I know Dolphin_oracle was concerned about us getting the right version of the stock Debian kernel, as in unsigned vs signed, and possible updates of that breaking persistent Live USBs, but Debian just pushed an updated 4.19.0-6 kernel to all of us, so I am wondering if anyone is reporting any ill effects.

I'm also wondering how we are going to handle Debian security updates to the 4.19 kernel, especially if they go to 4.19.0-7 and so on.

the automatica 4.19.0-6 update went thru fine on the live USB.

4.19.0-7 will have to be manual for folks. Doing it automatically will almost certainly break the live system. we don't have the debian metapackage installed by default, so that shouldn't be a problem.

[grelos]

Testing on a VM (MX18 being the host, of course..) on my Lenovo. Nothing serious to report, so far. Just a couple of comments.

However i did notice that placing the panel on the way I like it took one more step than in MX18. I had to select "horizontal" then it was placed horizontally but on top of display, I had to unlock it and move it to the bottom. If I recall well, in MX18 when selecting Horizontal panel went straight to the bottom.

In Thunar, selection of all files with Shift+left click does not work. However I am not sure it's MX19 or a VM (Virtualbox) setting that prevents it.

EDIT: a reboot fixed that Thunar problem.

[winemaker]

I know Dolphin_oracle was concerned about us getting the right version of the stock Debian kernel, as in unsigned vs signed, and possible updates of that breaking persistent Live USBs, but Debian just pushed an updated 4.19.0-6 kernel to all of us, so I am wondering if anyone is reporting any ill effects.

I'm also wondering how we are going to handle Debian security updates to the 4.19 kernel, especially if they go to 4.19.0-7 and so on.

asqwerth - i was just adding info to what stevo had mentioned. not trying to add garbage I sincerely thought i was enhancing his post. sorry. i will remain silent re: comments from now on. thank you.

[winemaker]

p.s. also since mx is based on debian and you guys are working so hard on mx 19 i figured I was doing you guys a favor - and i realize that maybe you guys are on top of all of this new NEWS but i was trying to help out in what little way i could. not trying to argue. I am new here. Just wanted to explain this to you in my defense and intention. thanks.

[mklym]

Code: Select all

System:    Host: mx-19b-29l Kernel: 4.19.0-6-686-pae i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-686-pae 
           root=UUID=339e8840-27ab-46d2-a70c-1c6ed620bdcc ro quiet splash 
           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: Laptop System: Matsushita product: CF-29LTQGZBM v: 004 serial: <filter> 
           Mobo: Matsushita model: CF29-4 v: 001 serial: <filter> BIOS: Phoenix K.K. v: 4.00L11 
           date: 07/19/2005 
Battery:   ID-1: BATA charge: 66.2 Wh condition: 66.2/84.9 Wh (78%) volts: 12.3/11.1 
           model: Panasonic CF-VZSU29A type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan 
           family: 6 model-id: D (13) stepping: 8 microcode: 20 L2 cache: 2048 KiB 
           flags: nx pae sse sse2 bogomips: 1196 
           Speed: 600 MHz min/max: 600/1600 MHz Core speed (MHz): 1: 600 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
Graphics:  Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics vendor: Matsushita 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2592 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio vendor: Matsushita 
           driver: snd_intel8x0 v: kernel bus ID: 00:1e.2 chip ID: 8086:266e 
           Sound Server: ALSA v: k4.19.0-6-686-pae 
Network:   Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet vendor: Matsushita driver: sky2 
           v: 1.30 port: 3000 bus ID: 02:00.0 chip ID: 11ab:4362 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 2915ABG [Calexico2] Network driver: ipw2200 
           v: 1.2.2kmprq port: 3000 bus ID: 06:02.0 chip ID: 8086:4223 
           IF: eth1 state: up mac: <filter> 
Drives:    Local Storage: total: 55.89 GiB used: 25.15 GiB (45.0%) 
           ID-1: /dev/sda vendor: Hitachi model: IC25N060ATMR04-0 size: 55.89 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: AD1A 
           scheme: MBR 
Partition: ID-1: / raw size: 53.86 GiB size: 52.76 GiB (97.97%) used: 25.15 GiB (47.7%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
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: 163 Uptime: 15m Memory: 1.40 GiB used: 608.3 MiB (42.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.36 

I have been testing MX-19B2.1 on my CF-29 Panasonic Toughbook. All seems okay except for a few issues.

When I get an informational popup, after hovering the pointer over an icon, or anything else that has an info popup like the back arrow in Firefox, the popup does not disappear when the pointer is moved. I have to move the pointer over the popup before it disappears. Minor but a bit frustrating when using a stylus on the touchscreen instead of a mouse.

There are some menu icons that are greyed out but clicking on the icons brings up the program as it should. The icons in question are 'Notes', 'Onboard' (keyboard) and 'Onboard Settings'. They are in the 'Accessories' menu. The 'Onboard Settings' is also found in the 'Settings' menu and is greyed out. Minor and not frustrating.

I was surprised, pleasantly, when MX-19B2.1 installed on my CF-29 without any problems.

I do have a couple issues that are not specifically related to MX-19 so I will start a thread, or two, in the appropriate section(s) of the forum.

Overall, a very nice job. Kudos to the devs.

[xtrail]

@xtrail
I am confused as to why systemd is important to you?
Are you a sysadmin?

To use sysvinit you don't have to do anything but boot the default kernel, start up the apps you wish to use, and do your thing.

im sorry im just new to linux overal, so i follow some tutorials on line about tweaking linux and making it better, but none of the commands work in Mx, but it worked in Manjaro, so i don't know what im doing wrong. Thanks. I just need to learn how to use linux, and none of the commands i fuond online seems to work in Mx, so i don't konw what to do...

As you are a newcomer to Linux, I suggest:

1. That you do NOT start your introduction to Linux by running a Beta release that is still in testing. This is supposed to be a feedback thread to report bugs of Beta 2.1, but it is starting to become a help thread which is not ideal, because it might become unclear whether you are having trouble because you did something wrong (or did not do something you should have) or because the beta had a bug you stumbled upon.

2. that you install FRESH the MX18.3 release, and then if you have problems, start fresh threads for each problem.

3. Meanwhile, just note that if you just booted into MX (whether 18 or 19) without doing anything special or choosing any other boot menu entry except the first one in the menu, you will have booted into sysvinit. You don't need to do anything to be booted in sysvinit.

4. Whether or not you continue in MX19 beta 2.1 or install MX18.3, your first stop for information should be the MX Manual, not just visiting random webpages all over the internet and just inputting commands you don't understand that may apply to other distros only.

Manjaro boots into systemd by default, unlike MX, so "systemctl" commands work for Manjaro.
systemctl is the command for systemd.

For MX, it boots into sysvinit by default, so systemctl commands won't work. If you want to know the equivalent command(s) in sysvinit, you must ASK in a separate thread, not this one, and set out what you were trying to do/achieve, so people can help you achieve the same result. Give the weblink to the so-called instructions you were trying to follow.

Yes, i will Thankyou for your support!! i was told to come to this forum by another moderator, i actually didn't want to post here, thanks

[dolphin_oracle]

p.s. also since mx is based on debian and you guys are working so hard on mx 19 i figured I was doing you guys a favor - and i realize that maybe you guys are on top of all of this new NEWS but i was trying to help out in what little way i could. not trying to argue. I am new here. Just wanted to explain this to you in my defense and intention. thanks.

I actually very much appreciated the heads-up on the kernel update. the live system is sensitive to kernel changes, and I've been watching each one very closely.

[Gerson]

I don't know if it's a beta problem but sometimes the thumbnails disappear from the files placed on the desktop, there's a black box and it alternates with thumbnails that if you see them, sometimes you see them all and sometimes none at all.