Page 57 of 60

Re: MX-19 Beta 2.1 Feedback

Posted: Sat Sep 28, 2019 1:33 pm
by mklym
tek wrote: Fri Sep 27, 2019 10:02 pm Loving this distro after trying out a heap of others..

Feedback so far .. imwheel is doing weird things, it'll work fine for a while and then will wig out and get stuck on a scrolling to the bottom of the window, clicking on the scroll bar doesn't do anything as it just keeps scrolling down. Worked fine in 18 with no issue.
Can kill imwheel and restart to fix but it's a bit janky.

imwheel.rc here:

".*"
None, Up, Button4, 5
None, Down, Button5, 5
Control_L, Up, Control_L|Button4
Control_L, Down, Control_L|Button5
Shift_L, Up, Shift_L|Button4
Shift_L, Down, Shift_L|Button5


And the only other issue is one I've had which another use reported a while ago is the mute button on the keyboard can only be unmuted by going into pulse audio..

Other than that .. super great work, happy enough that I just put my mac on eBay. Thank you! :happy:
I tried the keyboard mute button (Fn+F4) on my CF-29 and had no problem unmuting the sound with the keyboard (Fn+F4). Might have been fixed?

Re: MX-19 Beta 2.1 Feedback

Posted: Sat Sep 28, 2019 6:28 pm
by tek
Just tried it - k70 - no dice.. mute works, but unmute can only be enabled through pulse audio > Output device > unmute speaker icon.
When clicking the keyboard button the top corner volume control overlay shows it as being unmuted (speaker icon changes from grey to white - but in pulse audio mute is still active and has to be clicked to hear any sound again.

Re: MX-19 Beta 2.1 Feedback - panel failure while tweaking window selector

Posted: Sat Sep 28, 2019 9:32 pm
by imschmeg
In beta 2.1, I managed to cause the panel to fail (disappear) while changing Window Selector's (which I had as an item in the panel) preference from display as icon to list and back to icon. Following the failure, I tried to get into Settings->Panel, but that popped up an Error window saying:

Failed to show the preferences dialog
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
The name org.xfce.Panel was not provided by any .service files

Been playing exclusively in the beta, so don't know if this occurs elsewhere. This was in a virtualbox VM, so I'll save the state if anyone has suggestions on how to examine it further.

Re: MX-19 Beta 2.1 Feedback psmouse

Posted: Sat Sep 28, 2019 9:46 pm
by tbuser48
I've been running MX since MX-14 on Panasonic Toughbooks. In this instance this is for a CF-29 MK5. Touchpad and Touchscreen both run on LBPS/2.

Subject is psmouse.conf file created to speed up the draggy mouse/touchpad.

Quick fix that works per session only is

Code: Select all

xset m 8 1
Long term fix is creating /etc/modrobe.d/psmouse.conf.

Code: Select all

sudo nano /etc/modprobe.d/psmouse.conf
With contents "options psmouse resolution=400" no quotes.
[ctrl][o]
[ctrl][x]

Here is the difference not necessary for the older versions through MXLinux 17 maybe 18.

Code: Select all

sudo update-initramfs -u
Reboot.

Maybe someone could explain why update-intramfs is now needed for modprobe.d to see and use the new file.

Install was straight-forward. I like the wait for user input at 95% during install.

Code: Select all

System:    Host: mx1929 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: Laptop System: Matsushita product: CF-29NDLGFBM v: 005 serial: <filter> 
           Mobo: Matsushita model: CF29-5 v: 001 serial: <filter> BIOS: Phoenix K.K. v: 5.00L14 
           date: 08/03/2006 
Battery:   ID-1: BATA charge: 64.2 Wh condition: 65.5/84.9 Wh (77%) volts: 12.5/11.1 
           model: Panasonic CF-VZSU29A type: Li-ion serial: <filter> status: Charging 
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: Qualcomm Atheros AR5413/AR5414 Wireless Network Adapter [AR5006X 802.11abg] 
           driver: ath5k v: kernel port: 3000 bus ID: 06:02.0 chip ID: 168c:001b 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 55.75 GiB used: 6.22 GiB (11.2%) 
           ID-1: /dev/sda vendor: Renice model: E7 size: 55.75 GiB block size: physical: 512 B 
           logical: 512 B speed: <unknown> serial: <filter> rev: 1711 scheme: MBR 
Partition: ID-1: / raw size: 53.72 GiB size: 52.63 GiB (97.96%) used: 6.22 GiB (11.8%) 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: 171 Uptime: 2h 57m Memory: 1.90 GiB used: 576.4 MiB (29.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.33 

Re: MX-19 Beta 2.1 Feedback

Posted: Sun Sep 29, 2019 6:44 am
by asqwerth
Very weird. I reinstalled the Beta2.1 in VB in order to carry out some icon tests.

The matcha set of gtk themes don't show up in the beta. I could have sworn 2.1 includes the Matcha themes by default.

Code: Select all

System:    Host: mx19b21icon Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=6263acc3-0e22-4357-b9a4-99083b872c9c 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_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Single Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 6399 
           Speed: 3200 MHz min/max: N/A Core speed (MHz): 1: 3200 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
           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: InnoTek Systemberatung VirtualBox Graphics Adapter vendor: VMware 
           driver: vboxvideo v: 6.0.12_Debian r132055 bus ID: 00:02.0 chip ID: 80ee:beef 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           alternate: vboxvideo resolution: 1864x997~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI port: d010 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 25.98 GiB used: 881.58 GiB (3393.0%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 25.98 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 23.95 GiB size: 23.45 GiB (97.91%) used: 5.83 GiB (24.9%) 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: 172 Uptime: 59m Memory: 3.70 GiB used: 1.04 GiB (28.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.36 

Re: MX-19 Beta 2.1 Feedback

Posted: Sun Sep 29, 2019 9:16 am
by dolphin_oracle
asqwerth wrote: Sun Sep 29, 2019 6:44 am Very weird. I reinstalled the Beta2.1 in VB in order to carry out some icon tests.

The matcha set of gtk themes don't show up in the beta. I could have sworn 2.1 includes the Matcha themes by default.

Code: Select all

System:    Host: mx19b21icon Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=6263acc3-0e22-4357-b9a4-99083b872c9c 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_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Single Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 6399 
           Speed: 3200 MHz min/max: N/A Core speed (MHz): 1: 3200 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
           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: InnoTek Systemberatung VirtualBox Graphics Adapter vendor: VMware 
           driver: vboxvideo v: 6.0.12_Debian r132055 bus ID: 00:02.0 chip ID: 80ee:beef 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           alternate: vboxvideo resolution: 1864x997~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI port: d010 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 25.98 GiB used: 881.58 GiB (3393.0%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 25.98 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 23.95 GiB size: 23.45 GiB (97.91%) used: 5.83 GiB (24.9%) 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: 172 Uptime: 59m Memory: 3.70 GiB used: 1.04 GiB (28.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.36 
it did not, but I did pull it in a mx-system update as a depend. But a later update removed the depend. it will be back on the iso for beta 3.

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Oct 01, 2019 5:28 am
by WarhawkCZ
Guys, I've been running the beta with my trusty T430 (quadcore+FHD mod) and nearly everything works perfectly.
Especially the new XFCE finally recognizes external screens when docked (there are profiles in the Display menu now).

Nevertheless, I have two little problems. The first one is "conky". The same problem I described here: viewtopic.php?t=47257
But I don't care. I don't need conky.

The second one is more severe. I operate my laptop in a docking station. The laptop lid is closed and I use only two external screens.
When I undock the laptop and open it, I am not able to see the login window because it still thinks that the external screen is connected.
I typically see just the black screen and need to type the password blindly. After unlocking, everything is ok.
Would there be a chance to do something about it, please?

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Oct 01, 2019 6:26 am
by winemaker
i run 2 thinkpad x series and a dell inspiron for my wife - using 18.3 an i have the same problem. so it is not endemic to the 19 betas. only glitch i have using mx so far that i can see. otherwise so far all seems to work. i get the blank black screen on wake from suspend which i use all the time.

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Oct 01, 2019 7:00 am
by Ghost67
asqwerth wrote: Sun Sep 29, 2019 6:44 am Very weird. I reinstalled the Beta2.1 in VB in order to carry out some icon tests.

The matcha set of gtk themes don't show up in the beta. I could have sworn 2.1 includes the Matcha themes by default.
I noticed that as well in testing on-metal installs.
dolphin_oracle wrote: Sun Sep 29, 2019 9:16 am
it did not, but I did pull it in a mx-system update as a depend. But a later update removed the depend. it will be back on the iso for beta 3.
Back on the iso for the beta 3? Good stuff, as it seems to have disappeared from xfce-look.org (though I last checked about a week ago, so it may well be back there again).

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Oct 01, 2019 7:16 am
by WarhawkCZ
winemaker wrote: Tue Oct 01, 2019 6:26 am i run 2 thinkpad x series and a dell inspiron for my wife - using 18.3 an i have the same problem. so it is not endemic to the 19 betas. only glitch i have using mx so far that i can see. otherwise so far all seems to work. i get the blank black screen on wake from suspend which i use all the time.
There is somewhere a package that detects dock and undock event. I used it before.
This dock-undock event could trigger changing the screen profile. I'll have a look at it.