Page 1 of 1

MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 1:54 pm
by dolphin_oracle
Feedback thread for the MX-19.2 KDE Beta 1 testing cycle.

details on the release

https://mxlinux.org/blog/mx-19-2-kde-be ... r-testing/

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 5:38 pm
by AbbyT
That's what I'm talkin' 'bout. Been waiting for this. \o/ Thank you!
(how 'bout an Openbox version? :)

AbbyT

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 5:40 pm
by jeffreyC
Will it be available in a non AHS version for those without the very latest hardware?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 5:41 pm
by seaken64
Am trying it now on a LiveUSB. I wasn't sure if the AHS was going to work with my hardware. But no problem. Am logged in now in the KDE-beta posting on the forum in FF. Here's my QSI

I did have to set my BIOS to Legacy Boot to boot from the LiveUSB.

Thanks,
Seaken64

Code: Select all


System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: quiet splasht nosplash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 81F5 v: Lenovo ideapad 330S-15IKB serial: <filter> Chassis: type: 10 
           v: Lenovo ideapad 330S-15IKB serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0R32866 WIN serial: <filter> UEFI [Legacy]: LENOVO v: 7SCN27WW 
           date: 11/28/2018 
Battery:   ID-1: BAT0 charge: 26.5 Wh condition: 27.9/30.0 Wh (93%) volts: 8.1/7.4 model: LENOVO BASE-BAT type: Li-poly 
           serial: <filter> status: Unknown 
           Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 Plus serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i3-8130U bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 8E (142) 
           stepping: A (10) microcode: 96 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17599 
           Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 799 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           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 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9d71 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo driver: ath10k_pci v: kernel 
           port: 3040 bus ID: 01:00.0 chip ID: 168c:0042 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-4:4 chip ID: 0cf3:e500 
Drives:    Local Storage: total: 126.70 GiB used: 2.29 GiB (1.8%) 
           ID-1: /dev/sda model: RTOTJ128VGD2EYX size: 119.24 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
           serial: <filter> rev: 1 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 7.46 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 3.01 GiB used: 388.4 MiB (12.6%) fs: overlay source: ERR-102 
           ID-2: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 30.0 C mobo: 0.0 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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
           2: deb http://mxrepo.com/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 189 Uptime: 10m Memory: 3.82 GiB used: 989.1 MiB (25.3%) 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.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 5:44 pm
by uncle mark
Keep this up and I may have to come back and torment these forums like back in the good ol' days.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 5:49 pm
by SwampRabbit
jeffreyC wrote: Sun Jul 05, 2020 5:40 pm Will it be available in a non AHS version for those without the very latest hardware?
I do not believe there are plans for a non-AHS version from what was last decided.

AHS "should" not stop any version of MX from working on older systems. Its still MX-19 stable with just minimal updated packages to ensure it works with newer hardware.

But the only way to know if a particular system will have issues is to test.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:23 pm
by AbbyT
Image

Code: Select all


System:
  Host: zz Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=5c04fb10-6b42-41f8-bffb-eff9304c61ef ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: HP-Pavilion product: KT376AA-ABA a6542p v: N/A 
  serial: <filter> Chassis: Hewlett-Packard type: 3 serial: <filter> 
  Mobo: PEGATRON model: Benicia v: 1.01 serial: <filter> BIOS: American Megatrends 
  v: 5.43 date: 09/10/2009 
CPU:
  Topology: Quad Core model: Intel Core2 Quad Q9450 bits: 64 type: MCP arch: Penryn 
  family: 6 model-id: 17 (23) stepping: 7 microcode: 70A L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 21334 
  Speed: 2367 MHz min/max: 2000/2667 MHz Core speeds (MHz): 1: 2367 2: 2117 3: 2017 
  4: 2128 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
  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 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Dell 
  driver: radeon v: kernel bus ID: 03:00.0 chip ID: 1002:68f9 
  Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1280x1024~60Hz 
  OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) 
  v: 3.3 Mesa 20.0.7 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard Asus IPIBL-LB 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel I210 Gigabit Network vendor: Hewlett-Packard I210-T1 GbE NIC 
  driver: igb v: 5.6.0-k port: 0400 bus ID: 02:00.0 chip ID: 8086:1533 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 6.59 GiB (1.4%) 
  ID-1: /dev/sda vendor: Seagate model: ST3500320NS size: 465.76 GiB block size: 
  physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: SN05 scheme: MBR 
Partition:
  ID-1: / raw size: 64.34 GiB size: 62.83 GiB (97.65%) used: 6.59 GiB (10.5%) 
  fs: ext4 dev: /dev/sda9 
  ID-2: swap-1 size: 8.44 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda10 
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: radeon temp: 51 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 189 Uptime: 16m Memory: 7.78 GiB used: 1.13 GiB (14.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.36 
AbbyT

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:31 pm
by dolphin_oracle
AbbyT wrote: Sun Jul 05, 2020 6:23 pm Image

Code: Select all


System:
  Host: zz Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=5c04fb10-6b42-41f8-bffb-eff9304c61ef ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: HP-Pavilion product: KT376AA-ABA a6542p v: N/A 
  serial: <filter> Chassis: Hewlett-Packard type: 3 serial: <filter> 
  Mobo: PEGATRON model: Benicia v: 1.01 serial: <filter> BIOS: American Megatrends 
  v: 5.43 date: 09/10/2009 
CPU:
  Topology: Quad Core model: Intel Core2 Quad Q9450 bits: 64 type: MCP arch: Penryn 
  family: 6 model-id: 17 (23) stepping: 7 microcode: 70A L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 21334 
  Speed: 2367 MHz min/max: 2000/2667 MHz Core speeds (MHz): 1: 2367 2: 2117 3: 2017 
  4: 2128 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
  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 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Dell 
  driver: radeon v: kernel bus ID: 03:00.0 chip ID: 1002:68f9 
  Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1280x1024~60Hz 
  OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) 
  v: 3.3 Mesa 20.0.7 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard Asus IPIBL-LB 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel I210 Gigabit Network vendor: Hewlett-Packard I210-T1 GbE NIC 
  driver: igb v: 5.6.0-k port: 0400 bus ID: 02:00.0 chip ID: 8086:1533 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 6.59 GiB (1.4%) 
  ID-1: /dev/sda vendor: Seagate model: ST3500320NS size: 465.76 GiB block size: 
  physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: SN05 scheme: MBR 
Partition:
  ID-1: / raw size: 64.34 GiB size: 62.83 GiB (97.65%) used: 6.59 GiB (10.5%) 
  fs: ext4 dev: /dev/sda9 
  ID-2: swap-1 size: 8.44 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda10 
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: radeon temp: 51 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 189 Uptime: 16m Memory: 7.78 GiB used: 1.13 GiB (14.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.36 
AbbyT
Is that screenshot from the live media or an installed system?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:40 pm
by AbbyT
dolphin_oracle wrote: Sun Jul 05, 2020 6:31 pm
Is that screenshot from the live media or an installed system?
Installed system.

AbbyT

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:47 pm
by fehlix
AbbyT wrote: Sun Jul 05, 2020 6:40 pm
dolphin_oracle wrote: Sun Jul 05, 2020 6:31 pm
Is that screenshot from the live media or an installed system?
Installed system.

AbbyT
That might be a timing issue. Question to ask, ist that only a cosmetical issue and does the system works normally. If it works normally we might suppress the first dbus-call-attempt message, as the 2nd dbus-call would work.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:51 pm
by richb
fehlix wrote: Sun Jul 05, 2020 6:47 pm
AbbyT wrote: Sun Jul 05, 2020 6:40 pm
dolphin_oracle wrote: Sun Jul 05, 2020 6:31 pm
Is that screenshot from the live media or an installed system?
Installed system.

AbbyT
That might be a timing issue. Question to ask, ist that only a cosmetical issue and does the system works normally. If it works normally we might suppress the first dbus-call-attempt message, as the 2nd dbus-call would work.
I had this during the alpha cycle. It was only on the LiveUSB and had no affect on the performance of the system.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 6:54 pm
by AbbyT
fehlix wrote: Sun Jul 05, 2020 6:47 pm That might be a timing issue. Question to ask, ist that only a cosmetical issue and does the system works normally. If it works normally we might suppress the first dbus-call-attempt message, as the 2nd dbus-call would work.
It appears just before the Welcome to Plasma splash screen. Everything else seems normal.

Thx for all your good work.

AbbyT

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 9:02 pm
by uncle mark
Posting from live USB with old slow thumb drive on old slow machine. Looks promising.

On startup I'm getting 2 MX Welcome windows and it appears I have two panels, one on top of the other. Also, can't set time. Doesn't ask for authentication, so can't feed it root password and therefore.

Not in a position to give this a real workout, but wanted to let you guys know I'm really happy to see this.

Edit to add: System info didn't copy to clipboard, had to do copy/paste manually.

Code: Select all

System:
  Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: quiet splasht nosplash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Acer product: Aspire 5250 v: V1.01 serial: <filter> 
  Mobo: Acer model: Aspire 5250 v: V1.01 serial: <filter> BIOS: Acer v: 1.01 
  date: 04/21/2011 
Battery:
  ID-1: BAT1 charge: 48.1 Wh condition: 48.1/47.5 Wh (101%) volts: 12.4/10.8 
  model: Panasonic AS10D51 type: Li-ion serial: <filter> status: Full 
  Device-1: hidpp_battery_0 model: Logitech M215 serial: <filter> 
  charge: 5% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: AMD C-50 bits: 64 type: MCP arch: Bobcat 
  family: 14 (20) model-id: 1 stepping: N/A microcode: 5000029 L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3989 
  Speed: 941 MHz min/max: 800/1000 MHz Core speeds (MHz): 1: 941 2: 842 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Wrestler [Radeon HD 6250] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9804 
  Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) 
  v: 3.3 Mesa 20.0.7 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Acer Incorporated ALI driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: Acer Incorporated ALI 
  driver: atl1c v: 1.0.1.1-NAPI port: 2000 bus ID: 06:00.0 chip ID: 1969:2062 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Lite-On 
  driver: ath9k v: kernel port: 2000 bus ID: 07:00.0 chip ID: 168c:002b 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 115.56 GiB used: 400.1 MiB (0.3%) 
  ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB block size: 
  physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: BBF0 
  scheme: MBR 
  ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer size: 3.77 GiB block size: 
  physical: 512 B logical: 512 B serial: <filter> rev: 8.02 scheme: MBR 
Partition:
  ID-1: / raw size: N/A size: 2.83 GiB used: 400.1 MiB (13.8%) fs: overlay 
  source: ERR-102 
  ID-2: swap-1 size: 5.98 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 65.4 C mobo: N/A gpu: radeon temp: 64 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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
  2: deb http://mxrepo.com/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 198 Uptime: 22m Memory: 3.58 GiB used: 1.28 GiB (35.6%) 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.2 KDE Beta 1 feedback thread

Posted: Sun Jul 05, 2020 10:53 pm
by JayM
I just installed it in a VM. I don't actually like KDE anymore but MX KDE seems OK. The installation is using 6.45GB of disk space, and Plasma uses 485MB of RAM when idle as opposed to regular (non-ahs) Xfce MX-19.2 in a VM which uses 446MB. Just 40 more megs of RAM isn't too shabby considering it's Plasma, with whatever eye candy's enabled by default.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 5:46 am
by chrispop99
Couple of trivial points before I forget:

IMHO the desktop icons are way too big, and would look better vertically down the LH side.

Would it make sense to set the keybinding for Konsole to Ctrl-Alt-T to match the Xfce release?

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 9:54 am
by rrhobbs
I have it up n running (installed) on an HP Pavillion g7 1150us laptop.

I got the Dbus error booting the liveusb and my clock was off till I did a system update.

Also I have to manually connect to my network / internet each time I boot.

After letting the machine "sleep" overnight (default power settings) it was generally buggy, couldnt start any apps ie Chrome, couldnt find anything in my home.

I did a hot reboot / pretty much back to where I was.

I installed Skype it asked for the keyring each time I boot.

Quick system info will be in reply to this post.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 9:56 am
by rrhobbs

Code: Select all


System:
  Host: RRHOBBS-HP-MX Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=91739d4c-f689-4e16-81a0-f12cb59f4701 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Pavilion g7 Notebook PC 
  v: 0593110000204610000620100 serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Hewlett-Packard model: 166A v: 08.39 serial: <filter> BIOS: Insyde v: F.66 
  date: 01/24/2013 
Battery:
  ID-1: BAT0 charge: 45.5 Wh condition: 45.5/45.5 Wh (100%) volts: 0.1/11.1 
  model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Full 
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: Intel Core i3 M 370 bits: 64 type: MT MCP arch: Nehalem 
  family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 19155 
  Speed: 1605 MHz min/max: 933/2399 MHz Core speeds (MHz): 1: 1605 2: 1617 3: 1897 
  4: 1690 
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
  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 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
  Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 
  resolution: 1600x900~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 
  direct render: Yes 
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe 
  vendor: Hewlett-Packard U98Z077.00 Half-size Mini driver: rt2800pci v: 2.3.0 
  port: 5000 bus ID: 02:00.0 chip ID: 1814:5390 
  IF: wlan0 state: up mac: <filter> 
  Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
  vendor: Hewlett-Packard RTL810xE driver: r8169 v: kernel port: 3000 
  bus ID: 03:00.0 chip ID: 10ec:8136 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 223.57 GiB used: 7.77 GiB (3.5%) 
  ID-1: /dev/sda vendor: A-Data model: SU635 size: 223.57 GiB block size: 
  physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1c89 
  scheme: MBR 
Partition:
  ID-1: / raw size: 221.54 GiB size: 217.06 GiB (97.98%) used: 7.77 GiB (3.6%) 
  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:
  System Temperatures: cpu: 63.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
  1: deb [arch=amd64] https://repo.skype.com/deb stable main
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 228 Uptime: 46m Memory: 7.58 GiB used: 2.13 GiB (28.0%) 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.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 9:59 am
by asqwerth
rrhobbs wrote: Mon Jul 06, 2020 9:54 am ...
Also I have to manually connect to my network / internet each time I boot....
That is a known issue expressly set out in the Blog announcement for the Beta1

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 10:13 am
by rrhobbs
Copy wifi issue / blog / thx. Just ticked the "allow all users box" as per blog.

A couple more things....

There is an exclamation point by my wifi icon in the tray, connection works tho

Display issue in Chrome / the desktop seems t keep trying to "print thru" the browser if I scroll up or down.

On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"

Full disclosure I am not a Dev more of an enthusiast user of MX / KDE.

Sorry if I am not of more help. Will def be onboard for the stable release :)

Thx

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 10:24 am
by asqwerth
Any way you could take a pic of the notice in grub on bootup, and screenshot the Chrome "print thru" issue?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 10:56 am
by rrhobbs
I dont immediately see how to upload a pic here in the meantime here is a link to a pic of the boot up message. It comes right after the grub inset box ... and VERY quickly

I changed the link https://t.ly/iPQ3 (Google Photos)

Specifically the boot msg sez, "[ 0.093315] x86/cpu VMX (outside TXT) disabled by BIOS"

The display issue is intermittent / cannot reproduce at the moment

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 11:27 am
by sunrat
Just installed this, generally quite functional but a couple of issues:
This is a multiboot system with several other Debian type distros and I use Buster for GRUB. So I unticked "Install GRUB" but it still showed a message it was installing near the end of installation routine. Left me with Buster's GRUB wiped and booted to a GRUB prompt. Not happy. I used a live USB to boot Buster and reinstall its GRUB and all was fixed, MX subsequently booted up fine.
Another thing I may have mentioned before is there needs to be an option to include swap but not format it! So annoying in multiboot. I work around by not setting swap at all during install and add it later.

After booting it mostly seems to be behaving but I struck a minor warning message when using apt from terminal:

Code: Select all

# apt install zim
...
Fetched 1,167 kB in 1s (1,355 kB/s)
Unable to init server: Could not connect: Connection refused

(dpkg-preconfigure:6518): Gtk-WARNING **: 01:06:37.455: cannot open display: 
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
It then proceeded to complete the task successfully. I don't think it really should be looking for a Gnome frontend.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 11:50 am
by asqwerth
sunrat wrote: Mon Jul 06, 2020 11:27 am Just installed this, generally quite functional but a couple of issues:
...
Another thing I may have mentioned before is there needs to be an option to include swap but not format it! So annoying in multiboot. I work around by not setting swap at all during install and add it later.
If you choose an existing swap partition, it recognises it as swap and does not reformat it.

I just installed beta 1 last night and chose to select my existing swap partition during installation. THe blkid command today shows that the swap partition's UUID is the same as in records I made in Mar 2019 (yes, I keep such records, because I have a multiboot machine as well).

What I did however, was choose NOT to add a label name during installation, since my swap partition has never had a label.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 6:48 pm
by uncle mark
Threw this on this old slow Acer this evening. Good work, guys. All the oddities I had with the live run I did last night went away. Did a few of my usual settings tweaks and here I am. I'll play with this some more and see about importing my Firefox and Thunderbird profiles, but so far so good. I'd like to come home if you'll have me. This might do it.

Code: Select all

System:
  Host: MX19KDE Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=c2d4348d-5ab8-4276-ad41-3951a81ed979 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Acer product: Aspire 5250 v: V1.01 serial: <filter> 
  Mobo: Acer model: Aspire 5250 v: V1.01 serial: <filter> BIOS: Acer v: 1.01 
  date: 04/21/2011 
Battery:
  ID-1: BAT1 charge: 48.1 Wh condition: 48.1/47.5 Wh (101%) volts: 12.4/10.8 
  model: Panasonic AS10D51 type: Li-ion serial: <filter> status: Full 
  Device-1: hidpp_battery_0 model: Logitech M215 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: AMD C-50 bits: 64 type: MCP arch: Bobcat 
  family: 14 (20) model-id: 1 stepping: N/A microcode: 5000029 L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3990 
  Speed: 940 MHz min/max: 800/1000 MHz Core speeds (MHz): 1: 940 2: 948 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Wrestler [Radeon HD 6250] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9804 
  Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) 
  v: 3.3 Mesa 20.0.7 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Acer Incorporated ALI driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: Acer Incorporated ALI 
  driver: atl1c v: 1.0.1.1-NAPI port: 2000 bus ID: 06:00.0 chip ID: 1969:2062 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Lite-On 
  driver: ath9k v: kernel port: 2000 bus ID: 07:00.0 chip ID: 168c:002b 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 6.58 GiB (5.9%) 
  ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB block size: 
  physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: BBF0 
  scheme: MBR 
Partition:
  ID-1: / raw size: 105.81 GiB size: 103.65 GiB (97.96%) used: 6.58 GiB (6.3%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 5.98 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 69.5 C mobo: N/A gpu: radeon temp: 69 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 169 Uptime: 44m Memory: 3.58 GiB used: 1.08 GiB (30.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.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 6:51 pm
by fehlix
rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Such warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 6:55 pm
by bbfuller
I'd be hard pressed to realise this was a beta release.

On this machine:

Code: Select all

System:    Host: acer4 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.14.5 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
Machine:   Type: Laptop System: Acer product: TravelMate B113 v: V2.17 serial: <root required> 
           Mobo: Acer model: BA10_HX v: Type2 - Board Version serial: <root required> UEFI: Acer v: 2.17 
           date: 03/22/2013 
Battery:   ID-1: BAT1 charge: 27.2 Wh condition: 30.6/37.3 Wh (82%) 
CPU:       Dual Core: Intel Core i3-2375M type: MT MCP speed: 1440 MHz min/max: 800/1500 MHz 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.0.7 
Network:   Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k 
           Device-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3 
Drives:    Local Storage: total: 447.13 GiB used: 9.17 GiB (2.1%) 
Info:      Processes: 192 Uptime: 5m Memory: 3.67 GiB used: 1.02 GiB (27.8%) Shell: bash inxi: 3.0.36 
It's working very well.

I noted the reference to retention of wireless network information and with the adjustment it works fine.

I agree "Quick System Info" doesn't copy to the clipboard.

This machine dual boots with Windows 10 and on this installation it appears not to be set to "Boot Last Selected".

I've sorted that before, but it's worth a mention.

This one is for keeping installed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 7:56 pm
by sunrat
asqwerth wrote: Mon Jul 06, 2020 11:50 am
sunrat wrote: Mon Jul 06, 2020 11:27 am...
Another thing I may have mentioned before is there needs to be an option to include swap but not format it! So annoying in multiboot. I work around by not setting swap at all during install and add it later.
If you choose an existing swap partition, it recognises it as swap and does not reformat it.
That's good to know but the installer doesn't inform about this. I try to be extra cautious as I've been bitten by other distro installers reformatting swap so I have to correct the UUID afterwards.

That's a trivial point compared with the GRUB issue though. I unticked "Install GRUB" as I wanted to continue using Buster's GRUB. But it proceeded to wipe the existing GRUB and replace it with a non-working one which booted to a GRUB prompt. It's a serious bug IMHO.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 8:29 pm
by fehlix
sunrat wrote: Mon Jul 06, 2020 7:56 pm
asqwerth wrote: Mon Jul 06, 2020 11:50 am
sunrat wrote: Mon Jul 06, 2020 11:27 am...
Another thing I may have mentioned before is there needs to be an option to include swap but not format it! So annoying in multiboot. I work around by not setting swap at all during install and add it later.
If you choose an existing swap partition, it recognises it as swap and does not reformat it.
That's good to know but the installer doesn't inform about this. I try to be extra cautious as I've been bitten by other distro installers reformatting swap so I have to correct the UUID afterwards.

That's a trivial point compared with the GRUB issue though. I unticked "Install GRUB" as I wanted to continue using Buster's GRUB. But it proceeded to wipe the existing GRUB and replace it with a non-working one which booted to a GRUB prompt. It's a serious bug IMHO.
Please give more details: A minimum would be is it UEFI or a BIOS install. And what partitons did you have chosen to install.
GRUB installation differs significantly on UEFI and BIOS. So just stating GRUB wiped out or is not working, is just not enough.
FWIW, the installer creates a mxpi.log , which would give some indication about what have been choosen and whre it was installed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 9:10 pm
by sunrat
Sorry, I meant to include QSI.

Code: Select all

System:    Host: mxbrain-plasma Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 root=/dev/sda7 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> 
           Mobo: Gigabyte model: H170-HD3-CF v: x.x serial: <filter> UEFI: American Megatrends 
           v: F4 date: 10/16/2015 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> 
           charge: 50% (should be ignored) rechargeable: yes status: N/A 
CPU:       Topology: Quad Core model: Intel Core i5-6500 bits: 64 type: MCP arch: Skylake-S 
           family: 6 model-id: 5E (94) stepping: 3 microcode: DC L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25599 
           Speed: 800 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           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 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK driver: nvidia v: 440.82 
           bus ID: 01:00.0 chip ID: 10de:13c2 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 
           resolution: 3840x2160~30Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 
           direct render: Yes 
Audio:     Device-1: NVIDIA GM204 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0fbb 
           Device-2: VIA ICE1712 [Envy24] PCI Multi-Channel I/O driver: snd_ice1712 v: kernel 
           bus ID: 03:00.0 chip ID: 1412:1712 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: c000 bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.18 TiB used: 6.82 GiB (0.2%) 
           ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0B size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 90WD scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 1D05 scheme: MBR 
           ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 2B6Q scheme: MBR 
Partition: ID-1: / raw size: 51.81 GiB size: 50.74 GiB (97.95%) used: 6.82 GiB (13.4%) 
           fs: ext4 dev: /dev/sda7 
Sensors:   System Temperatures: cpu: 37.0 C mobo: 29.8 C gpu: nvidia temp: 38 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster main non-free
           2: deb http://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 186 Uptime: 7m Memory: 15.60 GiB used: 1.13 GiB (7.3%) 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 
^^ This copied automatically to the clipboard fine as it's supposed to.
It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 06, 2020 11:20 pm
by asqwerth
I left my locale during installation as default. After installation, I decided to try changing locale using the kde settings (where your currency and date format {don't like the USA date format} can be changed).

When I tried to install packages after that, I got error messages about locale and C library. Didn't affect the working of the package, but can look alarming.

I didn't change my locale in testing the alphas so had not encountered the issue until now.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 1:55 am
by JayM
Just as an experiment I installed the xfce and desktop-defaults-mx-xfce metapackages hoping to be able to log out, select an Xfce session, log back in and get the same look and feel as in the current MX with Xfce but I just got a regular Debian-looking Xfce desktop and panel. Then I tried copying/pasting the contents of /etc/skel including hidden files from my host OS into my home directory in my MX KDE guest OS but it's still not looking like I want. I wonder if there's a way of bundling everything needed to give me an almost-complete MX Xfce DE as well as KDE? I don't care about things like the greeter or boot splash screen, just my Xfce desktop after I log in. Either an mx-xfce metapackage in one of the repos or an MX Xfce entry in Popular Apps/Desktop Environments. This would make it easier for support helpers: we could easily switch between the two DEs on a single installed system rather than taking up extra disk space for a dual-boot between two installed versions of MX then having to boot back and forth between them, plus logging out and in is faster than rebooting. Is it possible to have both default desktops in MX KDE?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 2:54 am
by asqwerth
I don't think that is the intention at all. Can't you just install vanilla xfce on the kde iso and then theme it? Just need gtk, wm and icon themes. Maybe ask dolphin what other packages are needed for mx xfce desktop

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 3:01 am
by JayM
I could theme it myself but I'm looking for an easier way if there is one. I'm lazy. :smile:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 4:04 am
by baldyeti
One tiny thing I noticed (not even KDE-specific): if one clicks the About/Changelog button of apt-notifier, one gets a big *empty* window

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 4:10 am
by JayM
I don't even have a Changelog button.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 6:16 am
by richb
JayM wrote: Tue Jul 07, 2020 4:10 am I don't even have a Changelog button.
Right click on the icon, the About and changelog

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 6:20 am
by JayM
richb wrote: Tue Jul 07, 2020 6:16 am
JayM wrote: Tue Jul 07, 2020 4:10 am I don't even have a Changelog button.
Right click on the icon, the About and changelog
Ah, there it is. In Xfce I don't even get an empty window. I don't get anything at all.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:06 am
by Gerson
Installed on a small netbook in 2017 did not give me any problem. Installation of zeros with separate /home, only system on the netbook Fixed for automatic wifi connection, only two problems:
1.- The system fonts and browsers look very bad and I couldn't correct it.
2.- tutanota-desktop-linux.AppImage that worked fine in XFCE, it doesn't start in KDE
EDIT:
I've already corrected the typography issue from System Preferences > Fonts. I had changed the edge smoothing.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:13 am
by baldyeti
Gerson wrote: Tue Jul 07, 2020 7:06 am 2.- tutanota-desktop-linux.AppImage that worked fine in XFCE, it doesn't start in KDE
if you start that app from the command line (not from a graphical launcher) do you see any error message ?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:38 am
by Gerson
baldyeti wrote: Tue Jul 07, 2020 7:13 am
Gerson wrote: Tue Jul 07, 2020 7:06 am 2.- tutanota-desktop-linux.AppImage that worked fine in XFCE, it doesn't start in KDE
if you start that app from the command line (not from a graphical launcher) do you see any error message ?
Always in XFCE I started it by double-clicking on the file, in KDE it doesn't even start by command line.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:39 am
by Sparky
It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:40 am
by dolphin_oracle
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:49 am
by uncle mark
Any chance Synaptic could be added and MX-Update call that instead of Muon?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:52 am
by asqwerth
uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
I believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.

You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 7:56 am
by richb
asqwerth wrote: Tue Jul 07, 2020 7:52 am
uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
I believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.

You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
That is the way it works for me. Synaptic installed and that is what apt-updater shows.But I left Muon installed for testing purposes.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:05 am
by fehlix
asqwerth wrote: Tue Jul 07, 2020 7:52 am
uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
I believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.

You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
The logic changed within apt-notifer: If synaptic is installed, apt-notifier will use it. Otherwise if muon is found it will use muon. The right-click menu in apt-notifier, will change accordingly after installing synaptic, but you would need to close apt-notifier and start MX Updater again, to see the changes. You don't need to remove muon.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:12 am
by fehlix
baldyeti wrote: Tue Jul 07, 2020 4:04 am One tiny thing I noticed (not even KDE-specific): if one clicks the About/Changelog button of apt-notifier, one gets a big *empty* window
As it apprears the KDE Beta1 ISO does not contain most the changelog files, probably due to space constrains.
So if you want to try it out, reinstall apt-notifer:

Code: Select all

sudo apt install --reinstall apt-notifier
and you should have the changelog visible.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:22 am
by dolphin_oracle
sunrat wrote: Mon Jul 06, 2020 9:10 pm Sorry, I meant to include QSI.

Code: Select all

System:    Host: mxbrain-plasma Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 root=/dev/sda7 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> 
           Mobo: Gigabyte model: H170-HD3-CF v: x.x serial: <filter> UEFI: American Megatrends 
           v: F4 date: 10/16/2015 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> 
           charge: 50% (should be ignored) rechargeable: yes status: N/A 
CPU:       Topology: Quad Core model: Intel Core i5-6500 bits: 64 type: MCP arch: Skylake-S 
           family: 6 model-id: 5E (94) stepping: 3 microcode: DC L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25599 
           Speed: 800 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           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 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK driver: nvidia v: 440.82 
           bus ID: 01:00.0 chip ID: 10de:13c2 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 
           resolution: 3840x2160~30Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 
           direct render: Yes 
Audio:     Device-1: NVIDIA GM204 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0fbb 
           Device-2: VIA ICE1712 [Envy24] PCI Multi-Channel I/O driver: snd_ice1712 v: kernel 
           bus ID: 03:00.0 chip ID: 1412:1712 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: c000 bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.18 TiB used: 6.82 GiB (0.2%) 
           ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0B size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 90WD scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 1D05 scheme: MBR 
           ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 2B6Q scheme: MBR 
Partition: ID-1: / raw size: 51.81 GiB size: 50.74 GiB (97.95%) used: 6.82 GiB (13.4%) 
           fs: ext4 dev: /dev/sda7 
Sensors:   System Temperatures: cpu: 37.0 C mobo: 29.8 C gpu: nvidia temp: 38 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster main non-free
           2: deb http://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 186 Uptime: 7m Memory: 15.60 GiB used: 1.13 GiB (7.3%) 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 
^^ This copied automatically to the clipboard fine as it's supposed to.
It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
according to the log, grub was not installed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:24 am
by dolphin_oracle
JayM wrote: Tue Jul 07, 2020 1:55 am Just as an experiment I installed the xfce and desktop-defaults-mx-xfce metapackages hoping to be able to log out, select an Xfce session, log back in and get the same look and feel as in the current MX with Xfce but I just got a regular Debian-looking Xfce desktop and panel. Then I tried copying/pasting the contents of /etc/skel including hidden files from my host OS into my home directory in my MX KDE guest OS but it's still not looking like I want. I wonder if there's a way of bundling everything needed to give me an almost-complete MX Xfce DE as well as KDE? I don't care about things like the greeter or boot splash screen, just my Xfce desktop after I log in. Either an mx-xfce metapackage in one of the repos or an MX Xfce entry in Popular Apps/Desktop Environments. This would make it easier for support helpers: we could easily switch between the two DEs on a single installed system rather than taking up extra disk space for a dual-boot between two installed versions of MX then having to boot back and forth between them, plus logging out and in is faster than rebooting. Is it possible to have both default desktops in MX KDE?
all our Xfce settings are in the desktop-defaults-mx-xfce packages. there must be someting screwy with your copy from /etc/skel. I don't know how you did it, but don't do it while running Xfce...it won't work that way.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:28 am
by rrhobbs
fehlix wrote: Mon Jul 06, 2020 6:51 pm
rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Such warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...
Thanks I went into the bios it looks like there is a switch to allow virtual machine (I have it turned off)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:30 am
by Sparky
dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
On the top left of the monitor, its a drop down menu. If it helps, I installed it from MXPI

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:39 am
by sunrat
dolphin_oracle wrote: Tue Jul 07, 2020 8:22 am
sunrat wrote: Mon Jul 06, 2020 9:10 pm It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
according to the log, grub was not installed.
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It didn't install, but did wipe out the existing GRUB.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:44 am
by asqwerth
Sparky wrote: Tue Jul 07, 2020 8:30 am
dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
If it helps, I installed it from MXPI
Then you are not testing the Beta iso but merely installing KDE packages into your existing MX installation. It's not the same as there are tweaks not picked up when you merely install standard or full KDE.

By the way, normal MX19.1 or 19.2 iso has mx-fluxbox added to it.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:48 am
by fehlix
sunrat wrote: Tue Jul 07, 2020 8:39 am
dolphin_oracle wrote: Tue Jul 07, 2020 8:22 am
sunrat wrote: Mon Jul 06, 2020 9:10 pm It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
according to the log, grub was not installed.
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It wasn't installed, but wiped out the existing GRUB.
On UEFI, GRUB comes within different players. Taking out for now secureboot's shim. The first would be the grubx64.efi GRUB loader, which is placed with a subdir on the ESP. This grubx64.efi would be register with the UEFI firmware's NVRAM-table as a valid or the first to choosen bootloader.
The grubx64-efi will load the remaining "grub-stuff" and the menu from the /boot folder on the /root (or boot partition,
What could have happed, is this: You'r default grubx64.efi was loading from /dev/sda7 and displays a nice grub menu.
When you now wipe out and reinstall on /dev/sda7 , the existing grubx64.efi loaded at boot, cannot find any grub-stuff on the new install on /dev/sda7.
You propaby just need to choose another valid grub-efi loader with the NVRAM table to get loaded.
Either by using efibootmgr or select at start up (by pressing e.g F12) another loader.
:puppy:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:51 am
by rrhobbs
fehlix wrote: Mon Jul 06, 2020 6:51 pm
rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Such warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...
Thanks yes there is indeed a switch in the bios / enabled VT / the boot msg disappeared.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:53 am
by fehlix
Sparky wrote: Tue Jul 07, 2020 8:30 am
dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
On the top left of the monitor, its a drop down menu. If it helps, I installed it from MXPI
Thats's another topic, yes, it is related to KDE - but this thread is about feedback of the released MX KDE Beta1 ISO, not about KDE installation through MXPI.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:59 am
by rrhobbs
Gerson wrote: Tue Jul 07, 2020 7:38 am
baldyeti wrote: Tue Jul 07, 2020 7:13 am
Gerson wrote: Tue Jul 07, 2020 7:06 am 2.- tutanota-desktop-linux.AppImage that worked fine in XFCE, it doesn't start in KDE
if you start that app from the command line (not from a graphical launcher) do you see any error message ?
Always in XFCE I started it by double-clicking on the file, in KDE it doesn't even start by command line.
Didu right click / ...properties / enable as an app ?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 9:18 am
by wdscharff
Because of the view over the plate edge the KDE beta installed.
When I switched to Linux 5 years ago, I had done the first 2 months of Mint (xfce, what else) as a production system and on the side my personal distribution and desktop manager rally. I ended up at opensuse (xfxe, what else) for the next years.
I didn't warm up to KDE at that time and I guess nothing has changed.
Installation without problems (second disk, Grub in the MBR of the second disk, so it's called via the Grub of the primary installation) incl. the latest Nvidia driver from the test repo (if you want to, you can)

What I noticed negatively, the processor load. One thread was always at 100%, so in idle state the total processor load was generally between 4-5%. The processor fan was running continuously (which it does not do while writing this text under xfce). If it's possibly the NVIDIA driver, I will verify the next days.
My memory requirements are momenatly higher than with XFCE, but there I have already thrown out stuff in the autostart, which might still be loaded by KDE, whereby I don't give a damn about 50mb less or more
Now it's installed, now I'm watching it too ;-)

if of interest, QSI

Code: Select all

System:    Host: mx Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
           root=UUID=574d2ad3-8237-4c50-924a-9a3adc8d31ec ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: Gigabyte model: B450 AORUS M v: x.x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: F50 date: 11/27/2019 
CPU:       Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701013 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 182061 
           Speed: 2193 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2197 
           2: 2194 3: 2191 4: 2196 5: 2193 6: 2191 7: 2191 8: 4440 9: 1974 10: 1971 
           11: 2018 12: 2015 13: 2196 14: 2455 15: 2195 16: 2195 17: 2195 18: 4477 19: 1995 
           20: 1991 21: 2014 22: 2021 23: 2513 24: 2196 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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: 
           conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI 
           driver: nvidia v: 440.82 bus ID: 07:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 
           resolution: 1920x1200~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 
           direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 10de:0fb9 
           Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Gigabyte driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.18 TiB used: 8.54 GiB (0.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 1B6Q scheme: MBR 
           ID-3: /dev/sdb type: USB vendor: Samsung model: SSD 860 EVO 500G 
           size: 465.76 GiB block size: physical: 4096 B logical: 512 B serial: <filter> 
           rev: 0223 scheme: GPT 
           ID-4: /dev/sdc type: USB vendor: Samsung model: SSD 860 QVO 1TB size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0223 
           scheme: MBR 
Partition: ID-1: / raw size: 59.62 GiB size: 58.43 GiB (98.01%) used: 8.54 GiB (14.6%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 62.8 C mobo: N/A gpu: nvidia temp: 37 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 35% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ buster main non-free
           2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 375 Uptime: 1m Memory: 31.37 GiB used: 783.6 MiB (2.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 

Translated with www.DeepL.com/Translator (free version)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 9:53 am
by baldyeti
fehlix wrote: Tue Jul 07, 2020 8:12 amAs it apprears the KDE Beta1 ISO does not contain most the changelog files, probably due to space constrains.
Alright, makes sense; nothing crucial missing anyway.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:07 am
by Gerson
rrhobbs wrote: Tue Jul 07, 2020 8:59 am
Gerson wrote: Tue Jul 07, 2020 7:38 am
baldyeti wrote: Tue Jul 07, 2020 7:13 am
if you start that app from the command line (not from a graphical launcher) do you see any error message ?
Always in XFCE I started it by double-clicking on the file, in KDE it doesn't even start by command line.
Didu right click / ...properties / enable as an app ?
It was the first thing I did. Give him permission to run.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:14 am
by sunrat
fehlix wrote: Tue Jul 07, 2020 8:48 am
sunrat wrote: Tue Jul 07, 2020 8:39 am
dolphin_oracle wrote: Tue Jul 07, 2020 8:22 am according to the log, grub was not installed.
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It wasn't installed, but wiped out the existing GRUB.
On UEFI, GRUB comes within different players. Taking out for now secureboot's shim. The first would be the grubx64.efi GRUB loader, which is placed with a subdir on the ESP. This grubx64.efi would be register with the UEFI firmware's NVRAM-table as a valid or the first to choosen bootloader.
The grubx64-efi will load the remaining "grub-stuff" and the menu from the /boot folder on the /root (or boot partition,
What could have happed, is this: You'r default grubx64.efi was loading from /dev/sda7 and displays a nice grub menu.
When you now wipe out and reinstall on /dev/sda7 , the existing grubx64.efi loaded at boot, cannot find any grub-stuff on the new install on /dev/sda7.
You propaby just need to choose another valid grub-efi loader with the NVRAM table to get loaded.
Either by using efibootmgr or select at start up (by pressing e.g F12) another loader.
:puppy:
Sorry I don't understand what you mean. The pre-existing GRUB is on /dev/sda4 and was working perfectly prior to MX KDE install. I install OSs regularly and just boot to Buster on sda4 and run update-grub to include a new one in the boot menu. If I deselect "Install GRUB", the installer should not touch the ESP or NVRAM table. It obviously did as reboot brought up a GRUB prompt, not its usual boot screen.
I did fix it by booting into Buster from a REFInd flash key and reinstalling GRUB from there, but it shouldn't have been broken in the first place.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:51 am
by wdscharff
referring to my first posting.
It wasn't the Nvidia driver. After I removed the driver and restarted, unchanged behaviour: kwin_x11 generally loads one thread in idle mode with 100%.
That alone wouldn't bother me, but the processor temperature is generally higher and makes the fan run permanently.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:53 am
by uncle mark
richb wrote: Tue Jul 07, 2020 7:56 am
asqwerth wrote: Tue Jul 07, 2020 7:52 am
uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
I believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.

You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
That is the way it works for me. Synaptic installed and that is what apt-updater shows.But I left Muon installed for testing purposes.
Thanks guys. You were way ahead of me, obviously.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:53 am
by dolphin_oracle
sunrat wrote: Tue Jul 07, 2020 11:14 am
fehlix wrote: Tue Jul 07, 2020 8:48 am
sunrat wrote: Tue Jul 07, 2020 8:39 am
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It wasn't installed, but wiped out the existing GRUB.
On UEFI, GRUB comes within different players. Taking out for now secureboot's shim. The first would be the grubx64.efi GRUB loader, which is placed with a subdir on the ESP. This grubx64.efi would be register with the UEFI firmware's NVRAM-table as a valid or the first to choosen bootloader.
The grubx64-efi will load the remaining "grub-stuff" and the menu from the /boot folder on the /root (or boot partition,
What could have happed, is this: You'r default grubx64.efi was loading from /dev/sda7 and displays a nice grub menu.
When you now wipe out and reinstall on /dev/sda7 , the existing grubx64.efi loaded at boot, cannot find any grub-stuff on the new install on /dev/sda7.
You propaby just need to choose another valid grub-efi loader with the NVRAM table to get loaded.
Either by using efibootmgr or select at start up (by pressing e.g F12) another loader.
:puppy:
Sorry I don't understand what you mean. The pre-existing GRUB is on /dev/sda4 and was working perfectly prior to MX KDE install. I install OSs regularly and just boot to Buster on sda4 and run update-grub to include a new one in the boot menu. If I deselect "Install GRUB", the installer should not touch the ESP or NVRAM table. It obviously did as reboot brought up a GRUB prompt, not its usual boot screen.
I did fix it by booting into Buster from a REFInd flash key and reinstalling GRUB from there, but it shouldn't have been broken in the first place.
I'll look into that but if it was UEFI you could have just selected whatever EFI stub you want to boot from the system's UEFI panel. unlike mbr installs, UEFI installs won't overwrite another distro's EFI stub, but they will change the boot order.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:55 am
by fehlix
sunrat wrote: Tue Jul 07, 2020 11:14 am Sorry I don't understand what you mean. The pre-existing GRUB is on /dev/sda4 and was working perfectly prior to MX KDE install. I install OSs regularly and just boot to Buster on sda4 and run update-grub to include a new one in the boot menu. If I deselect "Install GRUB", the installer should not touch the ESP or NVRAM table. It obviously did as reboot brought up a GRUB prompt, not its usual boot screen.
I did fix it by booting into Buster from a REFInd flash key and reinstalling GRUB from there, but it shouldn't have been broken in the first place.
In UEFi, there is no one GRUB on /dev/xvz. You install GRUB-loader onto the ESP and the remaingin part from one ot the /boot/grub folders. And often there are more then one GRUB loader on the ESP. You need to look into the NVRAM table, this table is sometime re-orginzed the bootorder by UEFI firmaware itself. As the installer did not touch the ESP or the NVRAM table, you can tidy up ESP grub loader an NVRAM entries to avoid the reordering.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 12:14 pm
by baldyeti
fehlix wrote: Tue Jul 07, 2020 8:05 am The logic changed within apt-notifer: If synaptic is installed, apt-notifier will use it. Otherwise if muon is found it will use muon.
Isn't muon supposedly obsoleted by discover ? I am certainly *not* asking for the inclusion of discover, but in an MX distro wouldn't it make more sense to just default to MXPI in the absence of synaptic ? (and not include muon either)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 12:18 pm
by dolphin_oracle
baldyeti wrote: Tue Jul 07, 2020 12:14 pm
fehlix wrote: Tue Jul 07, 2020 8:05 am The logic changed within apt-notifer: If synaptic is installed, apt-notifier will use it. Otherwise if muon is found it will use muon.
Isn't muon supposedly obsoleted by discover ? I am certainly *not* asking for the inclusion of discover, but in an MX distro wouldn't it make more sense to just default to MXPI in the absence of synaptic ? (and not include muon either)
muon is more a synaptic clone and has many of the features people use synaptic for.

the version of discover available in the debian repo is bad. very bad. it fails at things like installing ffmpeg for instance.

using muon/mx-pi combo gives the same feature set as on the flagship Xfce iso.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 12:20 pm
by i_ri
Hello dolphin_oracle and everyone
First time ever pressing the power button here on an AHS version.
Started right up. Stared at an animation while the system set default for the two display monitors.
Got wireless up. posting from live MX_KDE.
Splendid.

Code: Select all

demo@mx1 
-------- 
OS: MX x86_64 
Host: HP EliteBook 8440p 
Kernel: 5.6.0-2-amd64 
Uptime: 18 mins 
Packages: 2319 (dpkg) 
Shell: bash 5.0.3 
Resolution: 1600x900, 1280x1024 
DE: Plasma 
WM: KWin 
Theme: Breeze [GTK2/3] 
Icons: breeze [GTK2/3] 
Terminal: yakuake 
CPU: Intel i5 M 560 (4) @ 2.667GHz 
GPU: Intel Core Processor 
Memory: 721MiB / 3732MiB 
next step experience the installer ... ...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 12:26 pm
by fehlix
baldyeti wrote: Tue Jul 07, 2020 12:14 pm
fehlix wrote: Tue Jul 07, 2020 8:05 am The logic changed within apt-notifer: If synaptic is installed, apt-notifier will use it. Otherwise if muon is found it will use muon.
Isn't muon supposedly obsoleted by discover ? I am certainly *not* asking for the inclusion of discover, but in an MX distro wouldn't it make more sense to just default to MXPI in the absence of synaptic ? (and not include muon either)
Muon is a bit closer to synaptic, where discover is kind of Gome-software Center.
For user who do not prefer to install Synaptic, we just kept Muon. Also within the right-click menu:
we have already an entry to open MXPI. I think it's a fair enough compromise.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 12:57 pm
by asqwerth
baldyeti wrote: Tue Jul 07, 2020 12:14 pm Isn't muon supposedly obsoleted by discover ? I am certainly *not* asking for the inclusion of discover, but in an MX distro wouldn't it make more sense to just default to MXPI in the absence of synaptic ? (and not include muon either)
I tried to like Discover. You should see my posts in the dev team private board, heh.

First I didn't like it because it didn't make clear what updateable packages came from the normal repos and which from flatpaks. You could be installing updates to your flatpak runtimes (1 GB each runtime!) if your flatpak was being actively developed and followed the latest (say) Gnome versions, and wondering how come your disk space was filling up so fast.

Then I tried to give it a chance because it could handle updates and had a nice notifier icon. And it did handle updates fine if you didn't have any flatpaks to worry about.

Then I tried to change repos from within its own repo settings, and found that it was weird. While installing updates brings up a pkexec request window for root password, trying to change repo sources brought up a different authentication window (for kdesu, which I think is deprecated) and hung the program.

The final clincher: search is bad in Discover:

My post from dev board:
Argh. Discover is not very good at searching for packages.

It cannot find papirus icons in our repos, if you make a general search or search from within "Applications" category. You get lots of themes and icons that pop up. Not just papirus. I also tried "papirus-" and "papirus-icon-theme" as search terms. Doesn't help even though the latter is the proper package name.

If you search under Application Add-ons, I found an entry the first time, but I can't repeat it. It seems to categorise icons as an Add-on, and looks for it in the KDE store rather than distro repos. The search is long and trawls up lots of other themes and icons.

I installed Muon from Discover, and Muon was able to locate and install papirus from our repos immediately. I think it will be very frustrating to depend on Discover for fine-grained searches. Unless we are going to tout MXPI as the Synaptic replacement, Discover alone is inadequate.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 1:02 pm
by baldyeti
fehlix wrote: Tue Jul 07, 2020 12:26 pm Also within the right-click menu: we have already an entry to open MXPI. I think it's a fair enough compromise.
Oh nice, i have to admit i had not paid attention to that menu. MXPI is there, perfect.

BTW the muon help page does not seem to exist yet.

Now for something completely different: in the bling department, would you consider enabling the "cover switch" effect under window mgt/task switcher ? It looks so darn good ;-)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 1:05 pm
by baldyeti
asqwerth wrote: Tue Jul 07, 2020 12:57 pm I tried to like Discover. You should see my posts in the dev team private board, heh.
I agree discover is a work in progress and i explicitly stated i was not asking for it. I just thought that maybe MXPI was sufficient in the default install, but muon is alright at least in buster.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 1:23 pm
by asqwerth
baldyeti wrote: Tue Jul 07, 2020 1:02 pm
Now for something completely different: in the bling department, would you consider enabling the "cover switch" effect under window mgt/task switcher ? It looks so darn good ;-)
Nice! I haven't dug so deeply into the plasma settings yet. I was happy enough with hot-corner windows overview, since I use my mouse more than keyboard controls.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 2:05 pm
by i_ri
MX Linux has the best installer in the business.
Hello dolphin_oracle and everyone . . Pardon me Sister while I swoon on the verge of swearing, Oh my stars, asked to invent a user account name, mxoid. is installed. second start with wlan0 up automatically. no kwallet dialogue with setting up wifi Thank you for that, though is seen kwallet in the menu.
no kdesu? found gksu yes. This is going to be familiar. Splendid.
Throw a upgrade in the bin, so we can see the little box, crate thingie light up. edit add: done. the notifier frame filled with color. did upgrade. color gone. it was sddm, so a reboot and back up no problem.
I need synaptic with my debian. with muon, fine. kinda like having apt and aptitude. konqueror?

Code: Select all

System:    Host: 8440p Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 8440p v: N/A serial: <root required> 
           Chassis: type: 10 serial: <root required> 
           Mobo: Hewlett-Packard model: 172A v: KBC Version 30.35 serial: <root required> 
           BIOS: Hewlett-Packard v: 68CCU Ver. F.60 date: 11/11/2015 
Battery:   ID-1: BAT0 charge: 45.6 Wh condition: 46.8/46.8 Wh (100%) volts: 12.3/11.1 
           model: Hewlett-Packard Primary type: Li-ion serial: 01595 2011/08/15 status: Unknown 
           Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 serial: 4004-13-87-a8-bd 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP arch: Nehalem rev: 5 
           L2 cache: 3072 KiB bogomips: 21284 
           Speed: 1758 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 1758 2: 1897 3: 1864 
           4: 2633 
           Flags: acpi aes aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de 
           ds_cpl dtes64 dtherm dts est flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor 
           msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pni popcnt pse pse36 pti 
           rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc vme xtopology 
           xtpr 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 
           resolution: 1600x900~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k 
           port: 5020 bus ID: 00:19.0 chip ID: 8086:10ea 
           Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 5000 bus ID: 43:00.0 
           chip ID: 8086:4239 
Drives:    Local Storage: total: 14.91 GiB used: 6.25 GiB (41.9%) 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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://la.mxrepo.com/mx/repo/ buster main non-free
           2: deb http://la.mxrepo.com/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Weather:   Temperature: 29.1 C (84 F) Conditions: Scattered clouds Wind: from E at 1.1 m/s (4 km/h, 2 mph) 
           Cloud Cover: 75% Humidity: 70% Dew Point: 23.2 C (74 F) Pressure: 1014 mb (34 in) 
           Location: Washington, D.C., DC, US, 20500 Current Time: Tue 07 Jul 2020 01:51:27 PM EDT 
           Observation Time: 2020-07-07 12:59:00 (America/New_York -0400) Source: WeatherBit.io 
Info:      Processes: 188 Uptime: 22m Memory: 3.65 GiB used: 598.0 MiB (16.0%) Init: SysVinit v: 2.93 
           runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: konsole 
           inxi: 3.0.36 

gone exploring ...
edit add: first start there is a welcome screen. never touched that window. second start no welcome screen. third start no welcome screen. second start there was that xmessage dbus msg. first and third start no xmessage about dbus. I just wait for the display dialogue to fade away. it sets extended monitor each time for dual. fine. ps_mem upon third start.

Code: Select all

 Private  +   Shared  =  RAM used       Program

 96.0 KiB +  21.5 KiB = 117.5 KiB       start_kdeinit
176.0 KiB +  32.0 KiB = 208.0 KiB       acpid
192.0 KiB +  36.0 KiB = 228.0 KiB       acpi_fakekeyd
220.0 KiB +  26.5 KiB = 246.5 KiB       startkde
280.0 KiB +  49.5 KiB = 329.5 KiB       init
316.0 KiB +  78.0 KiB = 394.0 KiB       cron
428.0 KiB +  26.0 KiB = 454.0 KiB       mdadm
480.0 KiB +  40.0 KiB = 520.0 KiB       rpc.idmapd
588.0 KiB +  46.5 KiB = 634.5 KiB       ksysguardd
624.0 KiB +  68.0 KiB = 692.0 KiB       cgmanager
692.0 KiB +  36.0 KiB = 728.0 KiB       ssh-agent
524.0 KiB + 210.5 KiB = 734.5 KiB       rpcbind
512.0 KiB + 296.0 KiB = 808.0 KiB       kwrapper5
656.0 KiB + 240.5 KiB = 896.5 KiB       dconf-service
776.0 KiB + 209.0 KiB = 985.0 KiB       dbus-launch (2)
284.0 KiB + 729.0 KiB =   1.0 MiB       saned (2)
876.0 KiB + 183.0 KiB =   1.0 MiB       rpc.statd
444.0 KiB + 620.5 KiB =   1.0 MiB       avahi-daemon (2)
804.0 KiB + 355.0 KiB =   1.1 MiB       getty (6)
  1.1 MiB + 272.5 KiB =   1.4 MiB       sudo
872.0 KiB + 559.0 KiB =   1.4 MiB       dbus
  1.3 MiB + 207.0 KiB =   1.5 MiB       ntpd
  1.1 MiB + 577.5 KiB =   1.6 MiB       at-spi-bus-launcher
328.0 KiB +   1.4 MiB =   1.7 MiB       kdeinit5
  1.5 MiB + 369.5 KiB =   1.8 MiB       gvfsd
  1.7 MiB + 254.0 KiB =   1.9 MiB       obexd
  1.7 MiB + 621.5 KiB =   2.3 MiB       sddm
  1.6 MiB + 725.5 KiB =   2.4 MiB       sddm-helper
  1.8 MiB + 605.5 KiB =   2.4 MiB       cupsd
928.0 KiB +   1.6 MiB =   2.5 MiB       desktop.so
  2.4 MiB + 160.0 KiB =   2.6 MiB       bash
  2.1 MiB + 587.0 KiB =   2.6 MiB       upowerd
  2.5 MiB + 428.0 KiB =   2.9 MiB       dhclient
  1.9 MiB +   1.0 MiB =   2.9 MiB       cups-browsed
  2.1 MiB +   1.0 MiB =   3.1 MiB       xembedsniproxy
  2.2 MiB + 999.0 KiB =   3.1 MiB       kscreen_backend_launcher
  3.0 MiB + 248.0 KiB =   3.3 MiB       systemd-udevd
  2.3 MiB +   1.1 MiB =   3.4 MiB       gmenudbusmenuproxy
  3.1 MiB + 471.5 KiB =   3.6 MiB       systemd-logind
  3.0 MiB + 697.5 KiB =   3.7 MiB       dbus-daemon (4)
  3.2 MiB + 528.0 KiB =   3.8 MiB       gvfsd-fuse
  3.3 MiB + 506.0 KiB =   3.8 MiB       polkitd
  4.0 MiB + 107.5 KiB =   4.1 MiB       rsyslogd
  3.6 MiB + 757.5 KiB =   4.3 MiB       wpa_supplicant
  4.2 MiB + 673.0 KiB =   4.9 MiB       ModemManager
  1.0 MiB +   3.9 MiB =   4.9 MiB       file.so (3)
  5.1 MiB +  27.0 KiB =   5.1 MiB       haveged
  4.3 MiB + 914.5 KiB =   5.2 MiB       colord
  4.7 MiB + 956.0 KiB =   5.6 MiB       udisksd
  4.2 MiB +   2.3 MiB =   6.5 MiB       klauncher
  4.3 MiB +   2.3 MiB =   6.6 MiB       kaccess
  5.4 MiB +   1.4 MiB =   6.8 MiB       NetworkManager
  4.7 MiB +   2.4 MiB =   7.1 MiB       polkit-kde-authentication-agent-1
  5.1 MiB +   2.1 MiB =   7.2 MiB       kglobalaccel5
  5.3 MiB +   1.9 MiB =   7.2 MiB       conky
  5.8 MiB +   2.0 MiB =   7.9 MiB       kactivitymanagerd
  5.4 MiB +   3.1 MiB =   8.5 MiB       org_kde_powerdevil
  7.3 MiB +   3.1 MiB =  10.5 MiB       ksmserver
  4.7 MiB +   5.9 MiB =  10.6 MiB       kwalletd
  8.7 MiB +   3.4 MiB =  12.1 MiB       kdeconnectd
  6.0 MiB +   6.3 MiB =  12.3 MiB       kuiserver
 11.3 MiB +   1.3 MiB =  12.6 MiB       python3.7
 13.0 MiB +   1.3 MiB =  14.3 MiB       pulseaudio
 15.7 MiB +   6.2 MiB =  21.9 MiB       yakuake
 21.5 MiB +   2.7 MiB =  24.2 MiB       Xorg
 17.1 MiB +   7.2 MiB =  24.3 MiB       krunner
 21.2 MiB +   4.3 MiB =  25.5 MiB       python2.7
 33.3 MiB +  11.9 MiB =  45.3 MiB       kded5
 39.6 MiB +   7.0 MiB =  46.7 MiB       kwin_x11
125.0 MiB +  14.6 MiB = 139.6 MiB       plasmashell
---------------------------------
                        563.3 MiB
=================================
keredmxoid@8440p:~

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 3:07 pm
by fehlix
sunrat wrote: Mon Jul 06, 2020 11:27 am After booting it mostly seems to be behaving but I struck a minor warning message when using apt from terminal:

Code: Select all

# apt install zim
...
Fetched 1,167 kB in 1s (1,355 kB/s)
Unable to init server: Could not connect: Connection refused

(dpkg-preconfigure:6518): Gtk-WARNING **: 01:06:37.455: cannot open display: 
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
It then proceeded to complete the task successfully. I don't think it really should be looking for a Gnome frontend.
You might consider to change your way to run command under root, or alternativeyl how to open a root terminal,

If you enter the root-shell using "su -", the DISPLAY variable is not accessible for open a DISPLAY for debcon-front ends:
Here to reproduced the message above:
going into the root shell this (non recommended) way:

Code: Select all

su -
and running on the root prompt something to trigger debconf ui:

Code: Select all

# dpkg-reconfigure locales
Unable to init server: Could not connect: Connection refused

(dpkg-reconfigure:12134): Gtk-WARNING **: 20:56:15.522: cannot open display: 
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
So a better way of running apt which might trigger debconf frontend would be:
either just simple use:

Code: Select all

sudo apt install bla-bla
or if you cannot resist to open a root-shell, which I'm rarely doing:

Code: Select all

sudo -i

In both cases debconf-frontends get a proper connection to the display.
HTH
:puppy:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 8:55 pm
by Sparky
The Devs must be very proud. I'm on the beta now and it looks *magnificent*!!!
I was on KDE for 2 years in the past so I am relatively familiar with it and this one looks great so far.
The only thing I know nothing about is Muon.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 9:08 pm
by Adrian
The only thing I know nothing about is Muon.
It's the closest thing to Synaptic but a native KDE app, we are just trying to match MX-19 (Xfce edition) features, we tried other options but plasma-discover is only half-baked, only MX PackageInstaller is not enough, I would not necessarily like to have Synpatic on a KDE release so Muon is a natural choice. Personally, I mostly use apt in console and at most MX PackageInstaller.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 9:54 pm
by sunrat
fehlix wrote: Tue Jul 07, 2020 3:07 pm You might consider to change your way to run command under root, or alternativeyl how to open a root terminal,

If you enter the root-shell using "su -", the DISPLAY variable is not accessible for open a DISPLAY for debcon-front ends:
So I have to use sudo to run root commands? Never had to do that in Debian, don't even have it installed. I don't have DISPLAY variable issues using "su -" in Debian. Wouldn't it be preferable to keep Debian functionality?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 10:14 pm
by fehlix
sunrat wrote: Tue Jul 07, 2020 9:54 pm Wouldn't it be preferable to keep Debian functionality?
This thread is about MX-19.2 KDE Beta 1 feedback, so please open a new topic about the issue you have, as it is not related to this thread.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 10:37 pm
by andyprough
The boot time on live usb with virtualbox was very slow, and left me with a blank screen for a long time. The first 3 times I tried it I thought it had died and ended the virtualbox session. The 4th time I decided to let it go for awhile and checked htop and found that vbox was very busy, so I let it keep going and KDE did come up. Would there be a way to have some type of graphic on the screen the entire time? The lengthy blank screen before going to the desktop is not uncommon with KDE, but in this case on vbox it just looks dead.

Once it is running it looks beautiful - I love that you themed it like regular MX. I feel like I'm basically in a regular MX XFCE session with lots of KDE tools.

I would recommend changing the default menu to be the whisker-style vertical menu instead of the slab. I very much dislike KDE's slab menu, and it's almost always the first thing I change with a new KDE setup. People not familiar with KDE may not know about their alternative menu options, and going with the whisker-style one that's most like the default MX XFCE menu might be a more comfortable transition.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:07 pm
by danielson
Not sure if this was talked about yet.
But, if there were an option or tweak to have the alt+tab set as windows across the screen instead of a side panel...
Did i miss it?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 07, 2020 11:51 pm
by SwampRabbit
andyprough wrote: Tue Jul 07, 2020 10:37 pm Once it is running it looks beautiful - I love that you themed it like regular MX. I feel like I'm basically in a regular MX XFCE session with lots of KDE tools.

I would recommend changing the default menu to be the whisker-style vertical menu instead of the slab. I very much dislike KDE's slab menu, and it's almost always the first thing I change with a new KDE setup. People not familiar with KDE may not know about their alternative menu options, and going with the whisker-style one that's most like the default MX XFCE menu might be a more comfortable transition.
Andy, thank you for this feedback.

This was discussed in the actual dev thread a bit. I think the KDE version is striking a good medium of familiarity and freshness so far.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:14 am
by i_ri
Hello dolphin_oracle and everyone
from MX kde ahs 19.2beta1 live on

Code: Select all

System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <root required> 
           Chassis: Hewlett-Packard type: 3 serial: <root required> 
           Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends v: 5.15 date: 06/25/2010 
CPU:       Dual Core: Intel Core i3 530 type: MT MCP arch: Nehalem speed: 1337 MHz min/max: 1200/2933 MHz 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0042 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel 
           port: d800 bus ID: 01:00.0 chip ID: 10ec:8168 
Drives:    Local Storage: total: 1.83 TiB used: 2.00 GiB (0.1%) 
Info:      Processes: 193 Uptime: 6m Memory: 7.64 GiB used: 549.9 MiB (7.0%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: yakuake inxi: 3.0.36 
demo@mx1:~

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:42 am
by asqwerth
andyprough wrote: Tue Jul 07, 2020 10:37 pm...

Once it is running it looks beautiful - I love that you themed it like regular MX. I feel like I'm basically in a regular MX XFCE session with lots of KDE tools.

I would recommend changing the default menu to be the whisker-style vertical menu instead of the slab. I very much dislike KDE's slab menu, and it's almost always the first thing I change with a new KDE setup. People not familiar with KDE may not know about their alternative menu options, and going with the whisker-style one that's most like the default MX XFCE menu might be a more comfortable transition.
Actually, we haven't really themed the Beta1 much, except for changing the panel+menu (plasma desktoptheme) to Breeze Dark so that it matched MX XFCE's dark panel and whisker menu.

The icons, window decorations and application theming in Beta 1 are all vanilla Breeze from KDE itself. That may or may not change, pending discussions amongst the devs.

I will take note of your suggestion for the alternative menu. I agree that the default menu takes some getting used to; it is a tad too "slide-y" at times.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:43 am
by JayM
Probably a Plasma thing, not an MX-KDE thing, but I'm trying to configure it the way I like my MX to be, with a horizontal panel at the bottom containing my task manager ("Window Buttons' in Xfce), system monitors and clock and a left-side panel containing the notification area and launchers. If I right-click on an application icon in the menu and select "Add to Panel" it doesn't ask me which panel as Xfce does, it just adds the launcher to the bottom panel. I wanted it in the left panel. I found a work-around: add a Quicklaunch widget in the panel you want your launchers in, then right-click on it and add your applications to it one at a time. Just for other peoples' information who are trying to do something similar.

And a couple of comments: one, for a beta 1 release MX-KDE pretty much just works OOTB. Great job! Two, I'd forgotten how much work is involved in configuring Plasma vs. Xfce. I suppose it would just take time for me to learn my way around in it again (I haven't used KDE in 2 1/2 years) then maybe my opinion will change, but right now it's a big pain to try to do anything.
Image

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:53 am
by i_ri
Hello dolphin_oracle and everyone
can you tell, with first ahs in-hand about curiosity of where it will start?
from MX 19.2ahs_KDE-beta1 live on

Code: Select all

System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5L8L-SE v: Rev 1.xx serial: <root required> BIOS: American Megatrends v: 0201 
           date: 10/09/2007 
CPU:       Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Presler rev: 5 L2 cache: 2048 KiB 
           bogomips: 13599 
           Speed: 3400 MHz min/max: N/A Core speeds (MHz): 1: 3400 2: 3400 
           Flags: acpi apic bts cid clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dts est fpu fxsr ht lahf_lm lm 
           mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge pni pse pse36 pti sep ss sse sse2 syscall tm tm2 tsc 
           vme xtpr 
Graphics:  Device-1: Intel 82945G/GZ Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:2772 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945G v: 1.4 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P5B driver: r8169 v: kernel 
           port: e800 bus ID: 02:00.0 chip ID: 10ec:8168 
Drives:    Local Storage: total: 168.29 GiB used: 2.00 GiB (1.2%) 
Info:      Processes: 150 Uptime: 14m Memory: 1.94 GiB used: 474.6 MiB (23.9%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: yakuake inxi: 3.0.36 
demo@mx1:~


Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:55 am
by JayM
chrispop99 wrote: Mon Jul 06, 2020 5:46 am Couple of trivial points before I forget:

IMHO the desktop icons are way too big, and would look better vertically down the LH side.
That's user-adjustable. Right-click on the desktop -> Configure Desktop -> Icons. Change Arrange In from Rows to Columns and use the slider to adjust their size then click Apply. (Or maybe I misunderstood you and you're actually suggesting changing the default values, not asking how to change them for yourself?)

Regarding size though, people with large hidpi hires monitors will probably appreciate the larger icons. People with notebooks with small screens or lower-res monitors, not so much.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:58 am
by Stevo
rrhobbs wrote: Tue Jul 07, 2020 8:51 am
fehlix wrote: Mon Jul 06, 2020 6:51 pm
rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Such warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...
Thanks yes there is indeed a switch in the bios / enabled VT / the boot msg disappeared.
The other way is probably to remove any virtualbox-guest-* packages after an install onto real hardware. Easier than messing with the BIOS, for sure.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:01 am
by Stevo
Here's another vote for the more whiskerlike menu, too.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:16 am
by i_ri
Hello dolphin_oracle and everyone
from MX 19.2ahs KDE-beta1 live on

Code: Select all

System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TOSHIBA product: Satellite A665 v: PSAW0U-01K001 serial: <root required> Chassis: type: 9 
           serial: <root required> 
           Mobo: TOSHIBA model: NWQAA v: 1.00 serial: <root required> UEFI [Legacy]: TOSHIBA v: 1.90 date: 12/23/10 
Battery:   ID-1: BAT1 charge: 4.0 Wh condition: 37.7/47.5 Wh (79%) volts: 11.3/10.8 model: COMPAL PA3817U-1BRS serial: 41167 
           status: Charging 
CPU:       Dual Core: Intel Core i5 M 450 type: MT MCP arch: Nehalem speed: 1560 MHz min/max: 1199/2400 MHz 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Toshiba America Info Systems driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Toshiba America Info Systems driver: r8169 
           v: kernel port: 7000 bus ID: 01:00.0 chip ID: 10ec:8168 
           Device-2: Realtek RTL8191SEvB Wireless LAN driver: rtl8192se v: kernel port: 5000 bus ID: 06:00.0 
           chip ID: 10ec:8172 
Drives:    Local Storage: total: 480.67 GiB used: 2.01 GiB (0.4%) 
Info:      Processes: 189 Uptime: 7m Memory: 3.65 GiB used: 607.6 MiB (16.3%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: yakuake inxi: 3.0.36 
demo@mx1:~


Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:40 am
by torxxl
Installation pour la Suisse.
Je retrouve le même problème que sur la version XFCE.
Un bog avait été ouvert.
Si je choisi à l'installation suisse(ch) j'ai une installation en anglais et les paramètres, région, clavier sont anglais anglais.
J'éspère qu'un jour MX arrivera à corriger ce problème.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:53 am
by Sparky
Stevo wrote: Wed Jul 08, 2020 1:01 am Here's another vote for the more whiskerlike menu, too.
You have a choice of menu styles in KDE. Right click on the launcher and choose alternatives.
Making the menu more whisker like would lessen the separation of KDE to XFCE

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:30 am
by i_ri
Hello dolphin_oracle and everyone
from MX 19.2ahs_KDE-beta1 live on

Code: Select all

System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TOSHIBA product: Satellite L355D v: PSLE8U-00L00X serial: <root required> Chassis: AMD 
           type: 10 serial: <root required> 
           Mobo: ATI model: Ant3 serial: <root required> BIOS: Insyde v: 1.10 date: 05/23/2008 
Battery:   ID-1: BAT0 charge: 18.4 Wh condition: 70.6/49.2 Wh (144%) volts: 12.3/12.3 model: PA3534U-1BRS serial: 0838 
           status: Charging 
CPU:       Topology: Dual Core model: AMD Athlon X2 QL-60 bits: 64 type: MCP arch: Turion X2 Ultra rev: 1 L2 cache: 1024 KiB 
           bogomips: 7580 
           Speed: 950 MHz min/max: 950/1900 MHz Core speeds (MHz): 1: 950 2: 1900 
           Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy constant_tsc cpuid cr8_legacy cx16 cx8 de extapic 
           extd_apicid fpu fxsr fxsr_opt ht hw_pstate lahf_lm lbrv lm mca mce mmx mmxext msr mtrr nonstop_tsc nopl nrip_save 
           nx osvw pae pat pge pni pse pse36 rdtscp rep_good sep skinit sse sse2 svm svm_lock syscall tsc vme vmmcall 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] RS780MC [Mobility Radeon HD 3100] vendor: Toshiba America Info Systems 
           driver: radeon v: kernel bus ID: 01:05.0 chip ID: 1002:9613 
           Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1440x900~60Hz 
           OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) v: 3.3 Mesa 20.0.7 compat-v: 3.0 
           direct render: Yes 
Network:   Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet vendor: Toshiba America Info Systems RTL810xE 
           driver: r8169 v: kernel port: 3000 bus ID: 04:00.0 chip ID: 10ec:8136 
           Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter vendor: Askey WLL3141 802.11bg driver: ath5k 
           v: kernel port: 3000 bus ID: 05:00.0 chip ID: 168c:001c 
Drives:    Local Storage: total: 247.79 GiB used: 2.00 GiB (0.8%) 
Info:      Processes: 226 Uptime: 6m Memory: 2.68 GiB used: 577.2 MiB (21.0%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: yakuake inxi: 3.0.36 
demo@mx1:~

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:44 am
by torxxl
Faut-il rendre le menu plus moustache ?
Je ne sais pas le % de personnes qui vont passer de XFCE à KDE dans MX Linux et le % d'utilisateur qui vont passer à MX Linux depuis une autre distribution.
Personellement n'ayant pas trop aimer XFC je suis sur une autre distribution et je vais venir sur XFCE avec un grand bonheur pour KDE, mais j'éspère trouvé un KDe pas trop modifié qui resemble à mon KDe que j'ai dans d'autres distributions.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:50 am
by JayM
Try the Application Menu widget rather than Application Launcher. If the column of icons on the left could be made smaller (and I think the can, I just don't remember how) it looks the closest to Whisker Menu of the choices that we have. I installed Excalibur Menu as it looked like it might be good but it doesn't appear to work in this version of Plasma.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:58 am
by JayM
Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless with a fresh battery.

Code: Select all


System:
  Host: mx19.2-kde-beta1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=76d0f85c-1640-4838-bc5b-f95ec10cf441 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  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 
Battery:
  ID-1: BAT0 charge: 48.5 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Unknown 
CPU:
  Topology: Dual Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64 
  type: MCP arch: Zen family: 17 (23) model-id: 11 (17) stepping: N/A 
  microcode: 6000626 L2 cache: 1024 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 7984 
  Speed: 1996 MHz min/max: N/A Core speeds (MHz): 1: 1996 2: 1996 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  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, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter vendor: VMware 
  driver: vboxvideo v: 6.1.6_Debian r137129 bus ID: 00:02.0 chip ID: 80ee:beef 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  alternate: vboxvideo compositor: kwin_x11 resolution: 1704x870~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.7 compat-v: 3.1 
  direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio driver: snd_intel8x0 v: kernel bus ID: 00:05.0 
  chip ID: 8086:2415 
  Sound Server: ALSA v: k5.6.0-2-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.00 GiB used: 7.12 GiB (28.5%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 25.00 GiB block size: 
  physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1.0 
  scheme: MBR 
Partition:
  ID-1: / raw size: 22.97 GiB size: 22.48 GiB (97.88%) used: 7.08 GiB (31.5%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 36.5 MiB (1.8%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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 https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster main non-free
  2: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 154 Uptime: 14m Memory: 985.1 MiB used: 501.5 MiB (50.9%) 
  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.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:06 am
by Sparky
JayM wrote: Wed Jul 08, 2020 2:58 am Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless.
Surely you mean 1 GB not 1 MB RAM?
Try doubling the cores to 2 (in case you havent) and set the ram at 2GB
WIdgets are resource hungry, what do you see when you run top after you open the widgets?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:10 am
by baldyeti
Stevo wrote: Wed Jul 08, 2020 1:01 am Here's another vote for the more whiskerlike menu, too.
FWIW i much prefer it as well.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:12 am
by asqwerth
Sparky wrote: Wed Jul 08, 2020 1:53 am
Stevo wrote: Wed Jul 08, 2020 1:01 am Here's another vote for the more whiskerlike menu, too.
You have a choice of menu styles in KDE. Right click on the launcher and choose alternatives.
Making the menu more whisker like would lessen the separation of KDE to XFCE
I believe the proposal raised was which of the 2 menus to set as default OOTB. That is another issue to discuss.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:15 am
by JayM
Sparky wrote: Wed Jul 08, 2020 3:06 am
JayM wrote: Wed Jul 08, 2020 2:58 am Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless.
Surely you mean 1 GB not 1 MB RAM?
Yes, I meant 1GB, and stop calling me Shirley! :happy:
Try doubling the cores to 2 (in case you havent) and set the ram at 2GB
WIdgets are resource hungry, what do you see when you run top after you open the widgets?
I gave it 2 cores when I set up the VM. I'll try bumping up the RAM to 1.5GB and test it some more. I don't want to give it 2 because I only have 4GB in the laptop. Thanks for the suggestions.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:55 am
by chrispop99
JayM wrote: Wed Jul 08, 2020 12:55 am
chrispop99 wrote: Mon Jul 06, 2020 5:46 am Couple of trivial points before I forget:

IMHO the desktop icons are way too big, and would look better vertically down the LH side.
That's user-adjustable. Right-click on the desktop -> Configure Desktop -> Icons. Change Arrange In from Rows to Columns and use the slider to adjust their size then click Apply. (Or maybe I misunderstood you and you're actually suggesting changing the default values, not asking how to change them for yourself?)

Regarding size though, people with large hidpi hires monitors will probably appreciate the larger icons. People with notebooks with small screens or lower-res monitors, not so much.
Thanks; I know how to adjust them, and in any case never have any icons on my desktops in any distro. ;-)

I test on a wide variety of machines, but even on a 1080p (1920x1080) monitor, IMO they are too large.

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 4:35 am
by JayM
JayM wrote: Wed Jul 08, 2020 3:15 am
Sparky wrote: Wed Jul 08, 2020 3:06 am
JayM wrote: Wed Jul 08, 2020 2:58 am Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless.
Surely you mean 1 GB not 1 MB RAM?
Yes, I meant 1GB, and stop calling me Shirley! :happy:
Try doubling the cores to 2 (in case you havent) and set the ram at 2GB
WIdgets are resource hungry, what do you see when you run top after you open the widgets?
I gave it 2 cores when I set up the VM. I'll try bumping up the RAM to 1.5GB and test it some more. I don't want to give it 2 because I only have 4GB in the laptop. Thanks for the suggestions.
It just happened again, this time while trying to scroll in a website in Firefox: cursor moves but left and right buttons and scroll wheel stopped working. I unplugged the mouse to enable the touchpad and its buttons don't work either.

I'd try a bare metal (well, plastic) installation but this is my only working computer ATM (except for a 32-bit netbook that can't run Plasma) and I don't want to run a beta OS on a production machine, even if it is MX Linux. :)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 4:55 am
by baldyeti
bbfuller wrote: Mon Jul 06, 2020 6:55 pm I agree "Quick System Info" doesn't copy to the clipboard.
this++ - at least from a live session

can dev(s) please ack issues mentioned in this thread so we know they're not worth repeating ? thanks.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 5:11 am
by jackdanielsesq
Greetings all

Downloaded the iso, burned it, be reboooted to live session .... Beauteous - not a squeak, not a murmur
Even the sys-tray was the perfect height - love the CPU widgets, instead of conky-stuff - hit install, again
no quibble - all love - magnificent - deleted 'moan' and installed Synaptic, then deleted all desktop icons

Prefer order, empty desktop - if this is Beta, the MX Developers have outdone themselves once again.
All this was achieved on a ten-year old dual-core Acer crock-box, with a spinny ol' 500GB Seagate HDD

Unbelievable ...... :happy: :happy: :happy: :happy:

Gentlemen - it is magnifique - to all other KDE DE O/S's out there ... be afraid, be very afraid .. :number1: :number1:

Highest Regards

Jack

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 6:29 am
by dolphin_oracle
baldyeti wrote: Wed Jul 08, 2020 4:55 am
bbfuller wrote: Mon Jul 06, 2020 6:55 pm I agree "Quick System Info" doesn't copy to the clipboard.
this++ - at least from a live session

can dev(s) please ack issues mentioned in this thread so we know they're not worth repeating ? thanks.
Right now more reports the better.

Checking the clipboard manager to see if the text is present there would be good.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 6:38 am
by JayM
dolphin_oracle wrote: Wed Jul 08, 2020 6:29 am
baldyeti wrote: Wed Jul 08, 2020 4:55 am
bbfuller wrote: Mon Jul 06, 2020 6:55 pm I agree "Quick System Info" doesn't copy to the clipboard.
this++ - at least from a live session

can dev(s) please ack issues mentioned in this thread so we know they're not worth repeating ? thanks.
Right now more reports the better.

Checking the clipboard manager to see if the text is present there would be good.
It copies QSI to CopyQ after I installed it, but not to KDE's native Clipboard.

Edit: and now it suddenly started working after I installed copyq, even after I apt-get purged the latter.

By the way, Quick System Info doesn't appear in the menu's History after running it.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 7:14 am
by Gerson
I had a problem when trying to work with Ksnip, when doing the capture it closes, I have to resort to Spectacle but it doesn't have the functions that I like of Ksnip.
I still can't work with tutanota-desktop-linux.AppImage, it has all the execution permissions. In XFCE it didn't have any failure to run.

Code: Select all

Sistema operativo: Debian GNU/Linux 10
Versión de KDE Plasma: 5.14.5
Versión de Qt: 5.11.3
Versión de KDE Frameworks: 5.54.0
Versión del kernel: 5.6.0-2-amd64
Tipo de OS: 64 bits
Procesadores: 2 × Intel® Celeron® CPU N3060 @ 1.60GHz
Memoria: 3,8 GiB de RAM

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 7:31 am
by richb
JayM wrote: Wed Jul 08, 2020 6:38 am
dolphin_oracle wrote: Wed Jul 08, 2020 6:29 am
baldyeti wrote: Wed Jul 08, 2020 4:55 am
this++ - at least from a live session

can dev(s) please ack issues mentioned in this thread so we know they're not worth repeating ? thanks.
Right now more reports the better.

Checking the clipboard manager to see if the text is present there would be good.
It copies QSI to CopyQ after I installed it, but not to KDE's native Clipboard.

Edit: and now it suddenly started working after I installed copyq, even after I apt-get purged the latter.

By the way, Quick System Info doesn't appear in the menu's History after running it.
Same result for me. Installed copyQ and QSI showed in copyQ but not native clipboard. Second trial and shows in both.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 7:36 am
by dolphin_oracle
Gerson wrote: Wed Jul 08, 2020 7:14 am I had a problem when trying to work with Ksnip, when doing the capture it closes, I have to resort to Spectacle but it doesn't have the functions that I like of Ksnip.
I still can't work with tutanota-desktop-linux.AppImage, it has all the execution permissions. In XFCE it didn't have any failure to run.

Code: Select all

Sistema operativo: Debian GNU/Linux 10
Versión de KDE Plasma: 5.14.5
Versión de Qt: 5.11.3
Versión de KDE Frameworks: 5.54.0
Versión del kernel: 5.6.0-2-amd64
Tipo de OS: 64 bits
Procesadores: 2 × Intel® Celeron® CPU N3060 @ 1.60GHz
Memoria: 3,8 GiB de RAM
please provide a link where I can download the problematic appimage. Thanks!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 8:06 am
by JayM
richb wrote: Wed Jul 08, 2020 7:31 am Same result for me. Installed copyQ and QSI showed in copyQ but not native clipboard. Second trial and shows in both.
I just tested in a fresh VM install. I installed xclip then rebooted, wondering if that would also cause QSI to get copied to the native KDE clipboard as xclip's only 26k, but no joy.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 9:11 am
by Adrian
JayM wrote: Wed Jul 08, 2020 8:06 am
richb wrote: Wed Jul 08, 2020 7:31 am Same result for me. Installed copyQ and QSI showed in copyQ but not native clipboard. Second trial and shows in both.
I just tested in a fresh VM install. I installed xclip then rebooted, wondering if that would also cause QSI to get copied to the native KDE clipboard as xclip's only 26k, but no joy.
Can't replicate that, it works perfectly fine in my live VM:
Image
It might be a timing issue that might be fixed by the latest sddm-init package, or a user issue: how do you copy with middle-mouse click or Ctrl+V?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 9:21 am
by fehlix
Adrian wrote: Wed Jul 08, 2020 9:11 am
JayM wrote: Wed Jul 08, 2020 8:06 am
richb wrote: Wed Jul 08, 2020 7:31 am Same result for me. Installed copyQ and QSI showed in copyQ but not native clipboard. Second trial and shows in both.
I just tested in a fresh VM install. I installed xclip then rebooted, wondering if that would also cause QSI to get copied to the native KDE clipboard as xclip's only 26k, but no joy.
Can't replicate that, it works perfectly fine in my live VM:
Image
It might be a timing issue that might be fixed by the latest sddm-init package, or a user issue: how do you copy with middle-mouse click or Ctrl+V?
I can reproduce it. Perhaps a timing issue or something else. The clipboard get clearly populated. But just trying to paste
from the menu or pressing Ctrl+V does not paste (always). At least reproducable after reboot.
Also I noted pressing Ctrl+V twice seems to "unblock" the clipboard paste buffer.
Not sure, a clipboard config issue?
Perhaps, I'm thinking also (in addition) to populate the primary paste buffer, so people can just paste with middle-click, if they like.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 10:47 am
by Sparky
jackdanielsesq wrote: Wed Jul 08, 2020 5:11 am
Gentlemen - it is magnifique - to all other KDE DE O/S's out there ... be afraid, be very afraid .. :number1: :number1:

Jack
My thoughts exactly!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 11:58 am
by asqwerth
I think the advantages some other distros' Plasma release would have over MX is being able to use the newer 5.18 Plasma, though. There were some improvements not available to the Buster version.

For example, the layout of all the theming options in the Settings Manager was improved, you no longer needed to set the icons separately for both Qt/Plasma and gtk applications, and if you used Breeze for both qt and gtk apps, Breeze-gtk would automatically follow the colour scheme you applied to the Plasma/Qt side of things.

Also, some of the newer sddm themes you find on KDE Store cannot work on Plasma 5.14's sddm version, unfortunately. For instance, Sweet's plasma and kvantum theme will work in 5.14, but not its rather pretty sddm theme (I'm enjoying it in Neon).

On the other hand, Plasma 5.14 is already usable and stable. If you're not looking for the flashiest, most glossy frosted glass look, 5.14 is perfectly fine (you can enable the frosted "blur" look in 5.14 manually using the blur option in Desktop Effects).

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:15 pm
by richb
In addition 5.18 does not require unlocking widgets to add them. A minor thing but ease of use enhancement. I echo asqwerth's comments however. 5.14 is buster stable and a full fledged Plasma 5 release. The MX beta1 is a pleasure to use and will fulfill KDE fan's wish for a supported MX version, with many of the MX Tool enhancements.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 12:21 pm
by Gerson
dolphin_oracle wrote: Wed Jul 08, 2020 7:36 am
Gerson wrote: Wed Jul 08, 2020 7:14 am I had a problem when trying to work with Ksnip, when doing the capture it closes, I have to resort to Spectacle but it doesn't have the functions that I like of Ksnip.
I still can't work with tutanota-desktop-linux.AppImage, it has all the execution permissions. In XFCE it didn't have any failure to run.

Code: Select all

Sistema operativo: Debian GNU/Linux 10
Versión de KDE Plasma: 5.14.5
Versión de Qt: 5.11.3
Versión de KDE Frameworks: 5.54.0
Versión del kernel: 5.6.0-2-amd64
Tipo de OS: 64 bits
Procesadores: 2 × Intel® Celeron® CPU N3060 @ 1.60GHz
Memoria: 3,8 GiB de RAM
please provide a link where I can download the problematic appimage. Thanks!
Este es:
https://mail.tutanota.com/desktop/tutan ... x.AppImage

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:45 pm
by fehlix
Gerson wrote: Wed Jul 08, 2020 12:21 pm
dolphin_oracle wrote: Wed Jul 08, 2020 7:36 am
Gerson wrote: Wed Jul 08, 2020 7:14 am I had a problem when trying to work with Ksnip, when doing the capture it closes, I have to resort to Spectacle but it doesn't have the functions that I like of Ksnip.
I still can't work with tutanota-desktop-linux.AppImage, it has all the execution permissions. In XFCE it didn't have any failure to run.

Code: Select all

Sistema operativo: Debian GNU/Linux 10
Versión de KDE Plasma: 5.14.5
Versión de Qt: 5.11.3
Versión de KDE Frameworks: 5.54.0
Versión del kernel: 5.6.0-2-amd64
Tipo de OS: 64 bits
Procesadores: 2 × Intel® Celeron® CPU N3060 @ 1.60GHz
Memoria: 3,8 GiB de RAM
please provide a link where I can download the problematic appimage. Thanks!
Este es:
https://mail.tutanota.com/desktop/tutan ... x.AppImage
You need to enable kernel-sandbox'ing with MX-Tweak -> Other, to make it run.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 1:58 pm
by chrispop99
asqwerth wrote: Wed Jul 08, 2020 11:58 am I think the advantages some other distros' Plasma release would have over MX is being able to use the newer 5.18 Plasma, though. There were some improvements not available to the Buster version.

For example, the layout of all the theming options in the Settings Manager was improved, you no longer needed to set the icons separately for both Qt/Plasma and gtk applications, and if you used Breeze for both qt and gtk apps, Breeze-gtk would automatically follow the colour scheme you applied to the Plasma/Qt side of things.

Also, some of the newer sddm themes you find on KDE Store cannot work on Plasma 5.14's sddm version, unfortunately. For instance, Sweet's plasma and kvantum theme will work in 5.14, but not its rather pretty sddm theme (I'm enjoying it in Neon).

On the other hand, Plasma 5.14 is already usable and stable. If you're not looking for the flashiest, most glossy frosted glass look, 5.14 is perfectly fine (you can enable the frosted "blur" look in 5.14 manually using the blur option in Desktop Effects).
One thing I really miss with our version of KDE is the ability to change the formats of the date. You just get the preset shortdate, longdate, or ISO.

Older versions let you change the format (although bizarrely not using strftime codes), and so does newer versions.

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:02 pm
by dolphin_oracle
fehlix wrote: Wed Jul 08, 2020 1:45 pm
Gerson wrote: Wed Jul 08, 2020 12:21 pm
dolphin_oracle wrote: Wed Jul 08, 2020 7:36 am

please provide a link where I can download the problematic appimage. Thanks!
Este es:
https://mail.tutanota.com/desktop/tutan ... x.AppImage
You need to enable kernel-sandbox'ing with MX-Tweak -> Other, to make it run.
We made that the new default on 19.2 and forward but the change didn't make it inot the kde setup...we will make that adjustment to the KDE iso for beta2.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:20 pm
by sydz
Hello There,
Nice work already. Thanks a lot.
Didn't try it myself for now, but it seems someone have found a bug with Muon :
https://youtu.be/1fCl_wLu8Vk?t=595
Muon > Configuration > Configure Software Sources. (open Software Sources window "software-properties-kde")
pop up appears > password entered but validation didn't seem to respond, with no message...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:24 pm
by richb
sydz wrote: Wed Jul 08, 2020 2:20 pm Hello There,
Nice work already. Thanks a lot.
Didn't try it myself for now, but it seems someone have found a bug with Muon :
https://youtu.be/1fCl_wLu8Vk?t=595
Muon > Configuration > Configure Software Sources. (open Software Sources window "software-properties-kde")
pop up appears > password entered but validation didn't seem to respond, with no message...
I cannot duplicate this. After entering the password the sources dialog pops up where you can edit the sources.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 2:35 pm
by asqwerth
When I clicked on configure software sources, the software sources window opened right up without password.

But I experienced the same issue with DIscover in alpha 1 or 2, and the issue was that it was expecting user password (sudo), not root password. That might be what is happening here, because I had only just run sudo in my terminal, so I would still be within the time period during which other sudo tasks could be done without password. That would explain why I didn't need a password for the Sources config window, which would mean there is an issue with Muon, namely it requires different passwords for different tasks.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 3:22 pm
by fehlix
richb wrote: Wed Jul 08, 2020 2:24 pm
sydz wrote: Wed Jul 08, 2020 2:20 pm Hello There,
Nice work already. Thanks a lot.
Didn't try it myself for now, but it seems someone have found a bug with Muon :
https://youtu.be/1fCl_wLu8Vk?t=595
Muon > Configuration > Configure Software Sources. (open Software Sources window "software-properties-kde")
pop up appears > password entered but validation didn't seem to respond, with no message...
I cannot duplicate this. After entering the password the sources dialog pops up where you can edit the sources.
I think, he entered the wrong (root's) password instead of user-password. kdesu seem to have a bug, when entering wrong password it hangs.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 4:12 pm
by asqwerth
Whenever I install updates using the green updater icon in the notification area, something triggers the notification icon's right click menu to open. I think the menu also pops up after I install/remove something using muon, just after I close muon.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 4:14 pm
by richb
asqwerth wrote: Wed Jul 08, 2020 4:12 pm Whenever I install updates using the green updater icon in the notification area, something triggers the notification icon's right click menu to open. I think the menu also pops up after I install/remove something using muon, just after I close muon.
confirmed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 4:30 pm
by Laurentius
Hello.
Here running live iso on celeron netbook.
I'm not used to kde so can't help much.
If there was a TO-DO test list I would gladly follow it.

Everything seems quite fine.
wifi ok
blootooth ok - i could pair a speaker device and use and my android phone. but when i clicked send file an error message appeared.
The apt notifier didn't show updates but untill I did an apt update.

The bad thing here is the touchpad.
If I boot with the iso I burned with multisystem, the touchpad works bad. It is painful. Does not seem to tell between single finger behavior (simple move) and double finger (scroll).
If I boot with the iso burned with mx usb maker (full feature) the touchpad device was not found at all.
By the way, to see the special MX otptions at boot screen I had to configure the uefi/bios (??) to "Legacy first".

netbook specs (QSI worked fine for me):

Code: Select all


System:
  Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=(loop)/antiX/vmlinuz fromhd=UUID=56E7-94FA 
  fromiso=/MX-19.2_KDE-beta1_x64.iso quiet splasht 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Intel product: Intel powered classmate PC v: Clamshell 
  serial: <filter> Chassis: NULL type: 9 v: 0.1 serial: <filter> 
  Mobo: Intel model: Intel powered classmate PC v: Clamshell serial: <filter> 
  UEFI [Legacy]: Phoenix v: MPBYT10A.88F.0039.2016.0622.1403 date: 06/22/2016 
Battery:
  ID-1: BAT1 charge: 32.2 Wh condition: 32.2/36.6 Wh (88%) volts: 12.5/11.1 
  model: ECS CMPC type: Li-ion serial: <filter> status: Full 
CPU:
  Topology: Dual Core model: Intel Celeron N2808 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: 6333 
  Speed: 1011 MHz min/max: 500/2249 MHz Core speeds (MHz): 1: 1011 2: 1009 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds 
  status: Vulnerable: Clear CPU buffers attempted, no microcode; 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, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
  vendor: Elite Systems 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 
  compositor: kwin_x11 resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 20.0.7 
  compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio 
  vendor: Elite Systems driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:0f04 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be 
  v: kernel port: 2000 bus ID: 01:00.0 chip ID: 10ec:b723 
  IF: wlan0 state: up mac: <filter> 
  Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
  vendor: Elite Systems RTL810xE driver: r8169 v: kernel port: 1000 bus ID: 02:00.0 
  chip ID: 10ec:8136 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 494.60 GiB used: 44.28 GiB (9.0%) 
  ID-1: /dev/sda vendor: Western Digital model: WD5000LPCX-22VHAT0 size: 465.76 GiB 
  block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm 
  serial: <filter> rev: 1A01 scheme: GPT 
  ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 28.84 GiB 
  block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
Partition:
  ID-1: / raw size: N/A size: 2.94 GiB used: 639.8 MiB (21.2%) fs: overlay 
  source: ERR-102 
  ID-2: swap-1 size: 4.00 GiB used: 3.8 MiB (0.1%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda7 
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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
  2: deb http://mxrepo.com/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 184 Uptime: 59m Memory: 3.73 GiB used: 1.41 GiB (37.9%) 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 


If you try to close a window on a modified and unsaved document on a non qt app some apps like libreoffice or mousepad, in the dialog that opens up asking you to Save, Don't save or Cancel, you cannot tell which option is selected because no one is highlighted. Only if you hover with the mouse a super tiny blue frame is barely seen. (if you don't have a mouse or want to use keybard this is not good). (Though this is a kde problem, I think, not MX)

Although they have launchers in the panel, I would add dolphin and firefox to start menu's favorites section.
May be it would be a good choice to use Icons only task bar and grouped applications instead of labelled buttons with no grouping (as Mint did) to take advantage of this kde feature and thus offer a WS7/10-like desktop experience (I don't mean this is better, just say that would feel more familiar to a lot of people). EDIT: I now see that the current widget has already an auto smart grouping feature. That's great. (as I said, I'm not used to kde)

I would also add some shortcuts to defaults like Show desktop or switch to adjacents (up/down) workspaces.

On my main drive (2009 dual core compaq cq40) the iso did not boot. Neither the multisystem nor the mx-maker one.

Cq-40 specs (taken from a previous post):

Code: Select all

System:    Host: cq40mx Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum December 15  2017 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: Hewlett-Packard product: Compaq Presario CQ40 Notebook PC 
           v: F.31 serial: <filter> 
           Mobo: Compal model: 3607 v: 99.97 serial: <filter> BIOS: Hewlett-Packard v: F.31 
           date: 02/03/2009 
Battery:   ID-1: BAT0 charge: 95.0 Wh condition: 95.0/95.0 Wh (100%) 
           model: Hewlett-Packard Primary status: Full 
CPU:       Topology: Dual Core model: Pentium T4200 bits: 64 type: MCP arch: Penryn rev: A 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7979 
           Speed: 1885 MHz min/max: 1200/2000 MHz Core speeds (MHz): 1: 1885 2: 1907 
Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard 
           driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1280x800~60Hz 
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-9-amd64 
Network:   Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Hewlett-Packard 
           driver: wl v: kernel port: 7000 bus ID: 03:00.0 
           IF: wlan0 state: dormant mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 04:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 149.05 GiB used: 91.80 GiB (61.6%) 
           ID-1: /dev/sda vendor: Samsung model: HM160HI size: 149.05 GiB 
Partition: ID-1: / size: 14.36 GiB used: 11.72 GiB (81.7%) fs: ext4 dev: /dev/sda5 
           ID-2: /home size: 114.33 GiB used: 80.07 GiB (70.0%) fs: ext4 dev: /dev/sda6 
           ID-3: swap-1 size: 1.96 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 55.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://liveusb.info/multisystem/depot/ all main
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release-.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://debian.unnoba.edu.ar/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://debian.unnoba.edu.ar/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/megasync.list 
           1: deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           Active apt repos in: /etc/apt/sources.list.d/spotify.list 
           1: deb http://repository.spotify.com/ stable non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 200 Uptime: 19m Memory: 3.76 GiB used: 1.06 GiB (28.2%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36 

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 08, 2020 5:14 pm
by Gerson
fehlix wrote: Wed Jul 08, 2020 1:45 pm
Gerson wrote: Wed Jul 08, 2020 12:21 pm
dolphin_oracle wrote: Wed Jul 08, 2020 7:36 am

please provide a link where I can download the problematic appimage. Thanks!
Este es:
https://mail.tutanota.com/desktop/tutan ... x.AppImage
You need to enable kernel-sandbox'ing with MX-Tweak -> Other, to make it run.
There, I did it and now it works, thank you very much.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 6:59 am
by Auro Kumar Sahoo
Today I checked the beta kde 19.2, I can connect network through wire, but no wifi detected. I checked there is no wifi button side to airplane radio button of network notification.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 7:19 am
by asqwerth
Could you post your qsi, Auro?

Also, did you check the checksums of the downloaded iso?

In your last line, are you saying there is no icon in the panel for WiFi/network Connection?

Re: You know a sqat about KDE

Posted: Thu Jul 09, 2020 10:21 am
by kksmith
lynyx wrote: Thu Jul 09, 2020 10:05 am Hi,

I'm a KDE user long time Fedora, ...Don't you forget .Conky. ANd give us 10 terminal with bunch of bloatware on startup! Awesom. Bluerrrghh!

kids, see what happens when you fry your brains...dont do drugs.

Re: You know a sqat about KDE

Posted: Thu Jul 09, 2020 10:25 am
by dolphin_oracle
<MOD: original stupid post deleted as well as the quote here.>

Not only have you never tried the KDE iso, I'm fairly certain you've never tried MX. If your intent is to be a jackass, you've done a fine job. Go back from whence you came.

by the by, VAAPI works fine, but you would know that if you bothered to try MX. We do do some things differently from debian.

and yeah, we are learning as we go. I suggest you try the same tactic.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:28 am
by Jerry3904
I had harsher language going in a response, very glad you got there first!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:37 am
by richb
Jerry3904 wrote: Thu Jul 09, 2020 10:28 am I had harsher language going in a response, very glad you got there first!
Agree. I am usually diplomatic with stuff like this, but it went beyond the pale, as in feeble and unimpressive.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:45 am
by MAYBL8
Maybe if it's worth it to list his points he is trying to make and see if they are worth investigating or addressing.
Some people have good intentions but don't know how to express them in a non offensive manner.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:50 am
by richb
MAYBL8 wrote: Thu Jul 09, 2020 10:45 am Maybe if it's worth it to list his points he is trying to make and see if they are worth investigating or addressing.
Some people have good intentions but don't know how to express them in a non offensive manner.
That was more than not knowing how to express his points. It was deliberate use of obnoxious language to cause disruption and invite a negative reaction. At which he succeeded.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:51 am
by dolphin_oracle
MAYBL8 wrote: Thu Jul 09, 2020 10:45 am Maybe if it's worth it to list his points he is trying to make and see if they are worth investigating or addressing.
Some people have good intentions but don't know how to express them in a non offensive manner.
I was just making a list, but I think the only one I'm actually going to look at is

--look into firewall configuration.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:00 am
by asqwerth
I trust the devs to objectively assess if anything he says has merit, but this was not a person who actually tried the iso and then didn't know how to express himself in giving real critique.

What kind of person would register with the forum just to go on a rant about MX releasing a Plasma Beta for testing, without ever trying the iso??

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:01 am
by dolphin_oracle
Let's all move on....I shouldn't have let it get under my skin...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:07 am
by Jerry3904
asqwerth wrote: Thu Jul 09, 2020 11:00 amWhat kind of person ... ??
+1

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 12:12 pm
by MAYBL8
New issue.
Don't run gparted it generates all kind or krunner errors that are hard to get out of.
Or maybe it is just my system.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 2:59 pm
by sydz
fehlix wrote: Wed Jul 08, 2020 3:22 pm
richb wrote: Wed Jul 08, 2020 2:24 pm
sydz wrote: Wed Jul 08, 2020 2:20 pm Hello There,
Nice work already. Thanks a lot.
Didn't try it myself for now, but it seems someone have found a bug with Muon :
https://youtu.be/1fCl_wLu8Vk?t=595
Muon > Configuration > Configure Software Sources. (open Software Sources window "software-properties-kde")
pop up appears > password entered but validation didn't seem to respond, with no message...
I cannot duplicate this. After entering the password the sources dialog pops up where you can edit the sources.
I think, he entered the wrong (root's) password instead of user-password. kdesu seem to have a bug, when entering wrong password it hangs.
Yes, you're right. I just receive his confirmation. False problem. Sorry for that.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 3:11 pm
by wdscharff
MAYBL8 wrote: Thu Jul 09, 2020 12:12 pm New issue.
Don't run gparted it generates all kind or krunner errors that are hard to get out of.
Or maybe it is just my system.
Just tried it, no problems, works as it should.
maybe your system

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 5:43 pm
by i_ri
Hello dolphin_oracle and everyone
automount
plugging in data usb is automounting.
In the settings for Removable Storage, Removable Devices, Configure automatic handling of removable storage media,
the topmost box "Enable" automatic mounting of removable media
is empty, unchecked, not marked.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 6:27 pm
by Gerson
I haven't been able to get Ksnip to work as well in KDE as it does with XFCE. It closes without saving and overlays the captures. A disaster.
For now it's the only problem I have, everything else works perfectly.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 6:41 pm
by richb
It is working OK here. Where did you install it from?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 7:28 pm
by MAYBL8
Nevermind on the gparted thing. I don't even have it installed. I don't know what happened.
I think there is a kparted. I will look into that.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:06 pm
by JayM
Adrian wrote: Wed Jul 08, 2020 9:11 am
JayM wrote: Wed Jul 08, 2020 8:06 am
richb wrote: Wed Jul 08, 2020 7:31 am Same result for me. Installed copyQ and QSI showed in copyQ but not native clipboard. Second trial and shows in both.
I just tested in a fresh VM install. I installed xclip then rebooted, wondering if that would also cause QSI to get copied to the native KDE clipboard as xclip's only 26k, but no joy.
Can't replicate that, it works perfectly fine in my live VM:
Image
It might be a timing issue that might be fixed by the latest sddm-init package, or a user issue: how do you copy with middle-mouse click or Ctrl+V?
Now i can't replicate it anymore either, on a fresh reinstall. It was probably the timing issue you mentioned. BTW I wasn't copying anything, just running QSI and letting the script do the copying.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:37 pm
by dolphin_oracle
we did issue a fix for the clipboard issue...it would have come with the mx-goodies update.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 10:47 pm
by JayM
Well, it worked. :smile:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:06 pm
by i_ri
Hello dolphin_oracle and everyone
handling dockapps
dockapps initiate in the upper left corner and can be moved anywhere on the desktop.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:07 pm
by i_ri
Hello dolphin_oracle and everyone
changing desktops with scroll wheel on desktop. where is the setting to select or deselect that option? edit:found this. mouse actions. mark me as no longer default. changing some settings now.

a middle-click on desktop brings a note (sticky note ) to the screen. I cannot find that shortcut listed anywhere ,, either. where is the deselect for that? or re assign?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:09 pm
by i_ri
Hello dolphin_oracle and everyone
Desktop Behavior, Screen Edges, Active Screen Corners.
The upper left active screen corner is erratic,
Present Windows-All Desktops is its default,
it flashes, flaky, selected windows change position and sometimes lose titlebar. repaint under mouse movement. Move window fixes it for continuing operations.
(The alt+tab is a different presentation than active corner. the alt+tab works.)

edit add:
first to qualify that this erratic view was over reboots with frequent visits to have it misbehave. had a solid case but not anymore.
Now willingness to declare the likelihood it may be isolated quirk to machine of install.
no settings had been changed; running default. now among the first setting changes, in compositor i switched it to faster. no change in active corner balk. switched back to default med. it now works beautifully. Either wiggling it or posting in forum made the problem go away.
Now no matter where it is set from instant to slow it remains constantly well. fixed. connected or not, the problem is gone.
It is a very nice feature.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:34 pm
by asqwerth
Gerson wrote: Thu Jul 09, 2020 6:27 pm I haven't been able to get Ksnip to work as well in KDE as it does with XFCE. It closes without saving and overlays the captures. A disaster.
For now it's the only problem I have, everything else works perfectly.
Ksnip is working fine for me. Trying running ksnip from terminal to see what error messages are displayed.

Re: You know a sqat about KDE

Posted: Thu Jul 09, 2020 11:46 pm
by Stevo
kksmith wrote: Thu Jul 09, 2020 10:21 am
lynyx wrote: Thu Jul 09, 2020 10:05 am Hi,

I'm a KDE user long time Fedora, ...Don't you forget .Conky. ANd give us 10 terminal with bunch of bloatware on startup! Awesom. Bluerrrghh!

kids, see what happens when you fry your brains...dont do drugs.
Funny, but I can't find the original post. Maybe they removed it. The forum says that user has zero posts.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:48 pm
by Stevo
MAYBL8 wrote: Thu Jul 09, 2020 7:28 pm Nevermind on the gparted thing. I don't even have it installed. I don't know what happened.
I think there is a kparted. I will look into that.
I think the KDE Partition Editor is already on the ISO.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:51 pm
by Adrian
I also had problem with ksnip not doing anything after selecting something that's why I kept Spectacle although I understand it doesn't have all the bells and whistles.

I don't see anything in terminal only that it cannot find any translation files which I doubt is the issue.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 09, 2020 11:55 pm
by Stevo
Jerry3904 wrote: Thu Jul 09, 2020 11:07 am
asqwerth wrote: Thu Jul 09, 2020 11:00 amWhat kind of person ... ??
+1
493.jpg

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 2:24 am
by Jerry3904
Yeah sure, but we were asking something else.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 3:13 am
by asqwerth
Adrian wrote: Thu Jul 09, 2020 11:51 pm I also had problem with ksnip not doing anything after selecting something that's why I kept Spectacle although I understand it doesn't have all the bells and whistles.

I don't see anything in terminal only that it cannot find any translation files which I doubt is the issue.
ksnip_20200710-150818.png
What do you mean by selecting something? You first have to choose whether to scrot the whole screen, active window or selected portion. Are you referring to selected portion? By default you should see a fancy "sniper-sight and coordinates" heads up display over your cursor.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 7:23 am
by Gerson
asqwerth wrote: Thu Jul 09, 2020 11:34 pm
Gerson wrote: Thu Jul 09, 2020 6:27 pm I haven't been able to get Ksnip to work as well in KDE as it does with XFCE. It closes without saving and overlays the captures. A disaster.
For now it's the only problem I have, everything else works perfectly.
Ksnip is working fine for me. Trying running ksnip from terminal to see what error messages are displayed.
Ksnip in graphic or terminal mode runs fine, the problem is when you give the order to make captures, it hides and you don't know where it saves, I already checked all the folders and I only found that it is in the task bar hidden and that is the capture it makes.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 7:29 am
by Gerson
richb wrote: Thu Jul 09, 2020 6:41 pm It is working OK here. Where did you install it from?
Ksnip installed it from the stable repository. But it works erratically.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 7:39 am
by richb
1. Install the version in the MX Test repo via MXPI.
2. In ksnip Options > Settings, uncheck minimize to tray.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 8:11 am
by asqwerth
Gerson, in current versions of ksnip, once you open it, it defaults to hiding in the system tray when you close it via the X button in the window bar (instead of Quit in menu bar). In other words, it wasn't really shut down but in system tray. That is similar to Clementine.

To have it working the way it used to, go to Options >> Settings, and uncheck the whole "Use Tray icon" option, instead of just "minimise to tray".

You don't need the version in Test Repo to have that option. Stable Repo version has that setting as well.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 9:24 am
by aguador
I have only tried in Live version on a small Pentium laptop and noted three things:
  1. "Could not sync environoment to dbus" - apparently already mentioned and addressed
  2. Touchpad on ahs (including XFCE-ahs live) is overly sensitive - on trying to adjust it (2x) it caused the cursor to become unresponsive both times
  3. Minor settings issues: default e-mail client is Kmail (which is not part of the live iso); terminal is Konsole even though Yakauke is loaded and functioning
Looks like a good KDE implementation, although I think XFCE should remain the flagship edition. I am a former KDE user and like many thing about the settings and hardware support, but have become less and less enthusiastic about KDE software applications.

Attaching information from the test machine . . .

Code: Select all


System:    Host: aguador-mx Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 root=/dev/sda5 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.2_x64 patito feo May 31  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Notebook product: W51PU v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Notebook model: W51PU serial: <filter> UEFI: American Megatrends v: 5.12 
           date: 11/24/2016 
Battery:   ID-1: BAT0 charge: 8.6 Wh condition: 22.8/31.1 Wh (73%) volts: 10.6/11.1 
           model: Notebook BAT type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Quad Core model: Intel Pentium N4200 bits: 64 type: MCP arch: Goldmont 
           family: 6 model-id: 5C (92) stepping: 9 microcode: 38 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
           Speed: 1492 MHz max: 1500 MHz Core speeds (MHz): 1: 1492 2: 1492 3: 1492 4: 1492 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Integrated 
           Graphics 
           vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5a84 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 505 (Broxton) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster 
           vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus ID: 00:0e.0 
           chip ID: 8086:5a98 
           Sound Server: ALSA v: k4.19.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK 
           driver: r8169 v: kernel port: e000 bus ID: 01:00.1 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: e000 bus ID: 02:00.0 
           chip ID: 8086:3165 
           IF: wlan0 state: up mac: <filter> 


Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 9:27 am
by Sparky
wifi in the beta kde version doesn't auto connect, I have to manually connect each session.
Also it has the same name as the normal regular xfce. I am dual booting and it is confusing with the same name.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 10:11 am
by asqwerth
Sparky wrote: Fri Jul 10, 2020 9:27 am wifi in the beta kde version doesn't auto connect, I have to manually connect each session....
This was expressly stated as a known issue in the Beta announcement. I have also mentioned it to another poster in this thread previously.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 10:46 am
by Auro Kumar Sahoo
asqwerth wrote: Thu Jul 09, 2020 7:19 am Could you post your qsi, Auro?

Also, did you check the checksums of the downloaded iso?

In your last line, are you saying there is no icon in the panel for WiFi/network Connection?
Yes, i checked iso that downloaded from souceforge, its ok
Please see attache image for detail problem
network_icon_notify.tar.gz
Thanks

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 11:22 am
by asqwerth
Auro Kumar Sahoo wrote: Fri Jul 10, 2020 10:46 am
asqwerth wrote: Thu Jul 09, 2020 7:19 am Could you post your qsi, Auro?

Also, did you check the checksums of the downloaded iso?

In your last line, are you saying there is no icon in the panel for WiFi/network Connection?
Yes, i checked iso that downloaded from souceforge, its ok
Please see attache image for detail problemnetwork_icon_notify.tar.gz

Thanks
You need to post your Quick system info (qsi) as stated before, so the experts here can look at your network card and other hardware specs etc.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 11:32 am
by dolphin_oracle
Sparky wrote: Fri Jul 10, 2020 9:27 am wifi in the beta kde version doesn't auto connect, I have to manually connect each session.
Also it has the same name as the normal regular xfce. I am dual booting and it is confusing with the same name.
this particular issue is fixed in an update to plasma-nm but it will only affect new connections, not existing ones.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 12:33 pm
by MAYBL8
I see that there a lot of KDE packages in the package manager after installing this beta. Also some in the Testing tab.
Is it ok to install any of these we want and should some of these be included in the default MX-KDE?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 1:14 pm
by Adrian
MAYBL8 wrote: Fri Jul 10, 2020 12:33 pm I see that there a lot of KDE packages in the package manager after installing this beta. Also some in the Testing tab.
Is it ok to install any of these we want and should some of these be included in the default MX-KDE?
Yes, you can install the ones from regular Debian repo, the one from MX Test are only for testing purpose -- so it's up to you if you want to test and report issues.
They are not going to be installed on ISO because of space consideration, it's already at 2GB...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 3:22 pm
by Gerson
Sometime when I installed KDE over XFCE the wifi icon disappeared and I fixed it with
$ sudo apt install plasma-nm
I don't know if this applies to MX-KDE

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 3:24 pm
by Gerson
asqwerth wrote: Fri Jul 10, 2020 8:11 am Gerson, in current versions of ksnip, once you open it, it defaults to hiding in the system tray when you close it via the X button in the window bar (instead of Quit in menu bar). In other words, it wasn't really shut down but in system tray. That is similar to Clementine.

To have it working the way it used to, go to Options >> Settings, and uncheck the whole "Use Tray icon" option, instead of just "minimise to tray".

You don't need the version in Test Repo to have that option. Stable Repo version has that setting as well.
Thanks again, I unchecked everything and now if it works well.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 3:58 pm
by seaken64
Under Computer|System Settings I get fonts that are greeked out. The setting application work but I can't read it all. Here's a clip of my screen after opening System Settings. This is in a VirtualBox VM. Windows Host.
Screenshot_20200710_155047.png

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 4:08 pm
by Adrian
They look perfectly fine in my VM, I wonder if it's some setting problem, how much memory did you give the the virtual graphics card?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 4:14 pm
by seaken64
Adrian wrote: Fri Jul 10, 2020 4:08 pm They look perfectly fine in my VM, I wonder if it's some setting problem, how much memory did you give the the virtual graphics card?
I have the video memory set to 128. I'll try playing around with the settings. I was troubleshooting the resolution and set it to 3D thinking it might make a difference. It ended up that I needed to re-install the GA. But I think I had these greeked fonts even before i got the GA working. I'll play with it some more.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 4:21 pm
by seaken64
I shutdown the VM and turned off 3D Acceleration. Then restarted. The fonts on the System Settings are now back to normal. False alarm.

Thanks for pointing me in the right direction Adrian.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 6:17 pm
by uncle mark
This release reminds me of a Warren Woodford product -- a beta that's as solid as many releases from other offerings.

What's the anticipated release schedule for new betas and RCs?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 7:27 pm
by Jerry3904
Under discussion ATM.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 9:10 pm
by JayM
I spent yesterday afternoon playing with MX KDE in a frugal static installation. I only had one issue: after having installed my wifi driver I right-clicked on the updater icon and checked for any initial updates. It ran through the check as fast as could be until it was "Reading package lists" which stalled at 97% for 3 minutes, then went to 98% and stalled for another 2 minutes, then finally completed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 10, 2020 10:21 pm
by Stevo
Oops, I gave Adrian the old package name for the video thumbnailer in Dolphin previews. Remove ffmpegthumbnailer and install ffmpegthumbs, then enable the video previews in Dolphin's Preview settings.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sat Jul 11, 2020 8:03 am
by MAYBL8
I would like to change the font size and color of the text in the box that comes up when you right click and check for updates.
How would I go about doing that?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sat Jul 11, 2020 10:42 pm
by JayM
That's the Konsole terminal emulator, which runs bash. Setting bash's fonts, colors and the prompt would be done the same way as setting them in Xfce Terminal, by editing your .bashrc file. A web search will tell you exactly how to edit the font colors (I'm not sure if you can change the size, but probably.) For example I found this in just a few seconds in Duckduckgo. Also there was a long thread in the forum a year or so ago about customizing the terminal prompt that contains lots of information. You can search for that.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sat Jul 11, 2020 10:46 pm
by asqwerth
He might be referring to the right click context menu of apt-notifier.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sat Jul 11, 2020 11:25 pm
by JayM
True, I think I misunderstood. If that's the case the font size is set by System Settings -> Fonts -> Fixed-width. I don't think there's a way to change the font's color unless you edit the theme.

Comment: what a great beta! Probably 99% of users' issues in this thread are just a matter of us all floundering around in Plasma and learning how it works vs. the Xfce that we're all used to. There have been very few actual problems with the OS itself, and I think those have all been fixed already (like the issue of QSI info not being copied to the clipboard which was fixed in a newer version of mx-goodies.)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sat Jul 11, 2020 11:28 pm
by JayM
One very annoying thing: whenever I install updates the right-click action menu for the update notifier always opens by itself toward the end of the updates' installation, and it stays open after the terminal closes. I have to left-click on the desktop to dismiss it.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:36 am
by i_ri
Hello dolphin_oracle
middle-click on Desktop . mouse actions.
brings up note. this is indeed consistent with middle-click set to Paste.
Even when a editor or text input box is available, with focus, a click in desktop opens note with pasted content.

I was checking to see if it interferes with highlight, middle-click to copy
and middle-click to paste. This in fact incorporates with it and does not interfere.
Sure is a quick view verify of clipboard. clipboard never empty to accomplish this? indicates this is a well thought
Feature of this desktop.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:42 am
by torxxl
Bonjour,
Comme sous XFCE, une partie des aplications ne sont pas en français. Libre Office, thunderbird, Firefox et meta paquet de langues.
De plus le dépot choisi lors de l'installation est souvent problématique, erreur lors de l'instalation des compléments de langues.
Du coup je dois 1. chercher le bon dépot 2. dans la logitec cherchrer fren pour mettre MX entièrement en français.
Je susi en Suisse

Hello,
As under XFCE, some of the applications are not in French. Free Office, thunderbird, Firefox and meta language package.
Moreover the repository chosen during installation is often problematic, error during the installation of the language complements.
So I have to 1. look for the right repository 2. in the logitec search for fren to put MX entirely in french

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 6:44 am
by Gerson
To better understand the use of the 3 System Load indicators on the taskbar, I modified the colors like this:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 8:01 am
by uncle mark
JayM wrote: Sat Jul 11, 2020 11:25 pmComment: what a great beta! Probably 99% of users' issues in this thread are just a matter of us all floundering around in Plasma and learning how it works vs. the Xfce that we're all used to. There have been very few actual problems with the OS itself, and I think those have all been fixed already (like the issue of QSI info not being copied to the clipboard which was fixed in a newer version of mx-goodies.)
Another boring, yawner beta. I haven't even had any WTF??? moments. They need to get to coding in the latest and greatest bugs and breakage if they plan on keeping the interest up.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 8:05 am
by Eadwine Rose
You are more than welcome to break things! It proves for great testing, and actually helps.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 10:04 am
by i_ri
Hello dolphin_oracle and everyone
konqueror. 4:18.12.0-1 and plugins installed. The Quit, Close window does not end the konqueror process. no new instance can launch before kill of running konqueror process. A workaround is to use the likes of the mxflux kill any window button on the konqueror window allows next launch from launcher. a workaround.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 10:26 am
by richb
i_ri wrote: Sun Jul 12, 2020 10:04 am Hello dolphin_oracle and everyone
konqueror. 4:18.12.0-1 and plugins installed. The Quit, Close window does not end the konqueror process. no new instance can launch before kill of running konqueror process. A workaround is to use the likes of the mxflux kill any window button on the konqueror window allows next launch from launcher. a workaround.
Closed ok for me but only loads the first time invoked. Once opened and closed it will not open again. The icon flashes in the panel and immediately disappears

Edit: It shows in ksysguard as opened but diplays nowhere. If I send the kill signal with ksysguard it can be re-opened.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:46 pm
by baldyeti
So ... what is this edition going to be called ? MepiX ? PlasmiX ?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:47 pm
by seaken64
I haven't noticed anybody mention the 3 "System Load" icons on the taskbar, next to the Updater icon. Why are there three icons? I can't see what the differences are and the pop-up says the same thing on all three. When I left-click they each open the same app. I do see that they seems to fill in differently from one another at times. But I can't tell which icon is for which monitoring which part of the system. Anybody know?

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:48 pm
by seaken64
baldyeti wrote: Sun Jul 12, 2020 1:46 pm So ... what is this edition going to be called ? MepiX ? PlasmiX ?
MXK? I named my VM MX-KDE.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:55 pm
by uncle mark
seaken64 wrote: Sun Jul 12, 2020 1:47 pm I haven't noticed anybody mention the 3 "System Load" icons on the taskbar, next to the Updater icon. Why are there three icons? I can't see what the differences are and the pop-up says the same thing on all three. When I left-click they each open the same app. I do see that they seems to fill in differently from one another at times. But I can't tell which icon is for which monitoring which part of the system. Anybody know?
Pretty sure they represent

CPU Memory Swap

I got rid of the swap bar, now have just two bars, and it's helpful at a glance on the old slow machine I'm testing MX KDE on to see why things might be slow.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 1:59 pm
by baldyeti
uncle mark wrote: Sun Jul 12, 2020 1:55 pm Pretty sure they represent CPU Memory Swap
That should be it - the tool-tip displayed when hovering over the widget has even slightly more data (average clock, cache dirty, writeback ...)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 2:02 pm
by seaken64
baldyeti wrote: Sun Jul 12, 2020 1:59 pm
uncle mark wrote: Sun Jul 12, 2020 1:55 pm Pretty sure they represent CPU Memory Swap
That should be it - the tool-tip displayed when hovering over the widget has even slightly more data (average clock, cache dirty, writeback ...)
Thank you both. On my screen the tooltip for all three is identical. Seems it would be better to title the tooltips to match the icon represented.

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 2:07 pm
by Gerson
seaken64 wrote: Sun Jul 12, 2020 1:47 pm I haven't noticed anybody mention the 3 "System Load" icons on the taskbar, next to the Updater icon. Why are there three icons? I can't see what the differences are and the pop-up says the same thing on all three. When I left-click they each open the same app. I do see that they seems to fill in differently from one another at times. But I can't tell which icon is for which monitoring which part of the system. Anybody know?

Seaken64
I mentioned it in a few comments back where I showed the image of the customization I made of the colors so I could better identify each process.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 2:12 pm
by seaken64
@Gerson,

okay, thanks. Can you also change the tooltips heading to say "CPU Monitor" or "MEM Monitor", in addition to changing the colors?

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 2:18 pm
by seaken64
I just noticed that when I got a Notification that I had updates available that when I click on the Notification badge nothing happens. (This is not the box turning green. Clicking on the green box does launch the updater). But I expected to be able to click on the Notification (the ones that come up over the taskbar and have red X on their right side). The same can be said if I open the Notifications area using the "Hidden icons" menu button. It seems to me that we should be able to click on those notifications to launch the appropriate app that the notification is alerting us about.

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 3:14 pm
by Gerson
seaken64 wrote: Sun Jul 12, 2020 2:12 pm @Gerson,

okay, thanks. Can you also change the tooltips heading to say "CPU Monitor" or "MEM Monitor", in addition to changing the colors?

Seaken64
When I put the cursor over each of the 3 icons, I receive the same information and I could not make it independent for each icon. That should be corrected, although I understand that you can also work with 4 or less icons, circulars or bars or with only one in which case it has all the information but it is optically more pleasant to see several icons with independent information.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 3:17 pm
by Laurentius
I did a frugal_persist on the netbook I mentioned before (the first one, the other does not boot with this iso)

Code: Select all

https://forum.mxlinux.org/viewtopic.php?f=94&t=59077&start=120#p585014
On first login it worked fine.
Very hard to use the touchpad, as I mentioned.
I went to a text file on the hdd to copy my wifi password, connected and updated.
But when I closed all windows then there was a small white screen that stored the wifi password I had copied. And couldn't close it. I think it is the clipboard. I can write things there, and copy and paste and delete, but no closing the window.

So I rebooted and went to pesist option.
Loged in fine. But this time no touchpad at all.
The sticky small white window with my password was still there.

And wifi was disconnected (I think that's expected)

As I had no touchpad, I went to "edit networks" on the menu, to see if i could connect from there. The wifi network was remembered but couldn't reach it with the keyboard, I could only move through the Wired options (no way to move to the wifi section with the keyboard (with Tab or arrow keys)

Is there a way to control the mouse pointer with the keyboard?

EDIT: after resume from suspend touchpad works again and I could close the note window

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 3:21 pm
by Gerson
seaken64 wrote: Sun Jul 12, 2020 2:18 pm I just noticed that when I got a Notification that I had updates available that when I click on the Notification badge nothing happens. (This is not the box turning green. Clicking on the green box does launch the updater). But I expected to be able to click on the Notification (the ones that come up over the taskbar and have red X on their right side). The same can be said if I open the Notifications area using the "Hidden icons" menu button. It seems to me that we should be able to click on those notifications to launch the appropriate app that the notification is alerting us about.

Seaken64
I haven't had that problem, if I put the cursor on the icon -I use the classic theme with hiding until new updates- it shows me how many updates there are, if I right click it allows me to choose them and in the hidden icons of the taskbar, I can execute them by clicking on each one.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 3:55 pm
by seaken64
Gerson wrote: Sun Jul 12, 2020 3:21 pm
seaken64 wrote: Sun Jul 12, 2020 2:18 pm I just noticed that when I got a Notification that I had updates available that when I click on the Notification badge nothing happens. (This is not the box turning green. Clicking on the green box does launch the updater). But I expected to be able to click on the Notification (the ones that come up over the taskbar and have red X on their right side). The same can be said if I open the Notifications area using the "Hidden icons" menu button. It seems to me that we should be able to click on those notifications to launch the appropriate app that the notification is alerting us about.

Seaken64
I haven't had that problem, if I put the cursor on the icon -I use the classic theme with hiding until new updates- it shows me how many updates there are, if I right click it allows me to choose them and in the hidden icons of the taskbar, I can execute them by clicking on each one.
I think this is a KDE thing. The "Notifications" feature is a separate function from the MX Updater. I can do all the things you mentioned. But I was curious as to why I can't directly respond to a KDE Notification by clicking on the notification tag. I am used to such behavior in Windows 10 notifications. You get the notification that pops up on the screen saying "You have updates available..." and then you click on that notification and it launches the update service app.

In this case, it is redundant to get a separate notification since we already get that same notification by the box turning green, like we are used to in MX. It's just curious to me that KDE gives a notification but we can't click the notification tag to act on it.

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:01 pm
by JuhaT
I have been running this beta in VMware box and since it worked flawlessy there I decided to install it on my desktop.
I have a separate Home partition so I chose not to modify it during install. I have MX on a separate SSD and Windows 10 on another. This is my experience.

After installation I noticed that it didn't find the Windows drive so Windows 10 isn't available to choose when starting the PC.
*EDIT* I dont know what happened, but I tried to install NVIDIA drivers with MX-tools but they didnt work with systemd (I need it for my VPN app from OVPN to work) so I reverted back with Timeshift, and now the option to start Windows 10 is available when starting PC :happy:

I had to reinstall these programs since they disappeared or couldnt be started:
Mailspring (although after reinstall of the program I didnt have to reconfigure Mailspring, all the mail was there) Mailspring warned that I needed a Keyring so I installed "gnome-keyring" and after that it worked just fine.
Firejail and Timeshift had disappeared, but I guess that is only what to expect since I wiped the partition where the XFCE version was installed.

There was no PDF-reader, only something called "PDF arranger" that couldnt open PDF files (nothing happened when I tried to open a PDF), so I installed "Evience" document viewer.
Other than that there was no problem and I am a happy camper since I got Wobbly Windows again :D



I dont know if it is necessary but here are info

Code: Select all


System:
  Host: mxkde Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=12b63c5c-8ce8-4c68-b753-32819f0ddb9c ro quiet splash 
  init=/lib/systemd/systemd 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Gigabyte product: Z390 GAMING X v: N/A serial: <filter> 
  Mobo: Gigabyte model: Z390 GAMING X-CF v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F9 date: 10/15/2019 
CPU:
  Topology: 8-Core model: Intel Core i7-9700K bits: 64 type: MCP arch: Kaby Lake 
  family: 6 model-id: 9E (158) stepping: D (13) microcode: D6 L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57600 
  Speed: 4600 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 4600 2: 4600 3: 4600 
  4: 4600 5: 4600 6: 4600 7: 4600 8: 4600 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  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: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds mitigation: TSX disabled 
  Type: tsx_async_abort mitigation: TSX disabled 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:1b81 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 resolution: 3440x1440~60Hz 
  OpenGL: renderer: NV134 v: 4.3 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 3.29 TiB used: 54.62 GiB (1.6%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q 
  scheme: MBR 
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 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: Seagate model: ST2000DX001-1CM164 size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
  serial: <filter> rev: CC43 scheme: MBR 
  ID-4: /dev/sdd vendor: Samsung model: SSD 860 EVO M.2 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 3B6Q scheme: MBR 
  ID-5: /dev/sde type: USB vendor: Western Digital model: WDS1 20G2G0A-00JH30 
  size: 111.80 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 0107 
Partition:
  ID-1: / raw size: 29.34 GiB size: 28.76 GiB (98.00%) used: 7.39 GiB (25.7%) 
  fs: ext4 dev: /dev/sdb1 
  ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 47.24 GiB (23.7%) 
  fs: ext4 dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 35.0 C mobo: 27.8 C gpu: nouveau temp: 30 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1528 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster main non-free
  2: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 274 Uptime: 1h 11m Memory: 23.49 GiB used: 3.44 GiB (14.7%) 
  Init: systemd v: 241 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.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:09 pm
by baldyeti
JuhaT wrote: Sun Jul 12, 2020 4:01 pm There was no PDF-reader, only something called "PDF arranger" that couldnt open PDF files (nothing happened when I tried to open a PDF), so I installed "Evience" document viewer.
Odd - okular is present in my live session and perfectly functional (can open PDFs)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:12 pm
by chrispop99
baldyeti wrote: Sun Jul 12, 2020 4:09 pm
JuhaT wrote: Sun Jul 12, 2020 4:01 pm There was no PDF-reader, only something called "PDF arranger" that couldnt open PDF files (nothing happened when I tried to open a PDF), so I installed "Evience" document viewer.
Odd - okular is present in my live session and perfectly functional (can open PDFs)
Okular is present.

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:19 pm
by Sparky
Okular is the default PDF opener in KDE, it's on my install as well.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:24 pm
by baldyeti
If the home folder was kept from a previous MX installation, then probably mime associations have been preserved (e.g. PDF associated with qpdfviewer which is not included in the KDE flavour)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 4:48 pm
by JuhaT
baldyeti wrote: Sun Jul 12, 2020 4:09 pm
JuhaT wrote: Sun Jul 12, 2020 4:01 pm There was no PDF-reader, only something called "PDF arranger" that couldnt open PDF files (nothing happened when I tried to open a PDF), so I installed "Evience" document viewer.
Odd - okular is present in my live session and perfectly functional (can open PDFs)
Thanks for info. When I clicked on a PDF file it tried to open it with "PDF arranger" for me.
If the home folder was kept from a previous MX installation, then probably mime associations have been preserved (e.g. PDF associated with qpdfviewer which is not included in the KDE flavour)
That is probably right. Thanks for the explanation.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 9:48 pm
by seaken64
I installed the MX-KDE beta with a frugal install. I got it all working but the date and time was off. When I tried using the applet to change the time it kept giving me an error. It would not let me make a change. I read up and it was said I would be asked for the password but I was not asked for a password. I figured this was why I couldn't apply the changes.

I ended up trying to change to London time. I got the error messages and then after I dismissed the errors the password box popped up. The time zone was now set to London. Then I tried setting it back to New York. It would not allow the change and I never got the password prompt.

I figured out that I could set it to UTC and it stuck. No password needed. But setting it to UTC gave me the correct time.

I couldn't figure out how to run the date & time settings from the command line using "sudo". This may be a KDE thing. I don't know if this behavior is normal for KDE or not.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 9:51 pm
by dolphin_oracle
Use MX-datetime. The kde one does have issues.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 11:11 pm
by seaken64
@d_o - thank you. I missed that app. It did ask me for the password when I launched it. I guess I was trying to learn the KDE way.

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Sun Jul 12, 2020 11:43 pm
by Adrian
seaken64 wrote: Sun Jul 12, 2020 11:11 pm @d_o - thank you. I missed that app. It did ask me for the password when I launched it. I guess I was trying to learn the KDE way.

Seaken64
Yeah, we'd like to fix that, it would be great if somebody could point us to a fix or something, it's hard to believe that KDE is broken like that in Buster...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 1:00 am
by andyprough
Adrian wrote: Sun Jul 12, 2020 11:43 pmYeah, we'd like to fix that, it would be great if somebody could point us to a fix or something, it's hard to believe that KDE is broken like that in Buster...
Only useful data I've ever seen on fixing this problem is this old Kubuntu forum post: https://askubuntu.com/questions/268073/ ... -kde-clock

Due to KDE clock getting its wrong data that had been fed to /etc/localtime, I would have to run

Code: Select all

sudo dpkg-reconfigure tzdata
and configure the time zone again.

More of a work-around than an actual fix. Not sure if that still works with the more recent versions.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 1:01 am
by shmu26
Does KDE beta differ significantly from KDE as offered in the MX software manager? I mean, if you are running MX 19.2 AHS.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 1:14 am
by asqwerth
The KDE plasma you get when you install from the package manager is the vanilla version found in Debian buster. The prepackaged list of applications it comes with is also set by the relevant metapackage for KDE Standard or KDE Full.

The MX beta iso has the dev team's own choice of applications. And some fixes to stuff that didn't work that well in Debian's version, eg sddm.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 1:22 am
by JayM
And MX-KDE will be a fully-supported official version just like the current Xfce version is.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 3:48 am
by ChrisLilly
I love that MX will have a supported KDE spin. I have been using MX with the repo KDE desktop for months and love it. But it uses about 800mb on idle whereas the Beta is using around 500 +/-. I am running the Beta on an old Thinkpad E520 i3 laptop with a lexar 128gb SSD. So nothing exciting for the test drive.
Here are the issues I have encountered in the last few days:

-Kwin always fails on boot.

-When adding Ksysgard, MX Tools and Info center to the panel only multiple failed URLs were created the first time or two. I deleted these and after some tinkering (and maybe the last update?) the "add to panel" function seems to be working better.

-Sound defaults to Dummy Audio, even after being changed to internal analogue device. I could get speaker output yesterday, but not today. No sound at all. Serious issue.

-I upgraded the Libreoffice to 6.4.5.2 (the flatpack version which includes, among others, the breeze theme unlike the Debian backport version). Flatpack would not install the full Libreoffice suite alongside the original but instead attempted to merge them resulting in a hybrid of bits of each version. When I deleted the Libreoffice 6.1 and rebooted, this did resolve itself, leaving a full suite of 6.4.5.2. It was easily enough resolved, but I would not wish the experience on a newcomer to MX Linux.

-My last point is really minor. The splash screen flashing on and off during shut down is weirdly disturbing.

I hope you don't mind if I throw in a repo wish. If the MX basic repository includes the most recent stable Libreoffice, could it please include the whole set of themes? I hate Tango, Colibre is okay, but I far prefer Breeze. It is easy enough for me to install a Flatpack or download direct from The Document Foundation, but it would be far easier, especially for a newbie to Linux with a large enough learning curve. And I would love to see MX as one of those top new user referrals like Mint or Ubuntu.

Quick system info:


System:
 Host: mxKDEBeta Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0  
 parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64  
 root=UUID=f4f0ef66-010c-4b81-a390-01026dfbb768 ro quiet splash  
 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM  
 Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020  
 base: Debian GNU/Linux 10 (buster)  
Machine:
 Type: Laptop System: LENOVO product: 1143ADU v: ThinkPad E520 serial: <filter>  
 Chassis: type: 10 serial: <filter>  
 Mobo: LENOVO model: 1143ADU serial: <filter> UEFI [Legacy]: LENOVO  
 v: 8HET40WW(1.22) date: 11/03/2011  
Battery:
 ID-1: BAT0 charge: 37.3 Wh condition: 38.0/47.5 Wh (80%) volts: 12.5/10.8  
 model: SANYO LNV-42T4751 type: Li-ion serial: <filter> status: Unknown  
CPU:
 Topology: Dual Core model: Intel Core i3-2350M 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: 18358  
 Speed: 1300 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 1300 2: 1472 3: 1206  
 4: 2042  
 Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages  
 Type: l1tf  
 mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable  
 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  
 Type: srbds status: Not affected  
 Type: tsx_async_abort status: Not affected  
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:0116  
 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa  
 compositor: kwin_x11 resolution: 1366x768~60Hz  
 OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.0.7  
 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: k5.6.0-2-amd64  
Network:
 Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo  
 driver: r8169 v: kernel port: 5000 bus ID: 02:00.0 chip ID: 10ec:8168  
 IF: eth0 state: down mac: <filter>  
 Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce v: kernel  
 port: 3000 bus ID: 08:00.0 chip ID: 10ec:8176  
 IF: wlan0 state: up mac: <filter>  
Drives:
 Local Storage: total: 260.76 GiB used: 8.88 GiB (3.4%)  
 ID-1: /dev/mmcblk0 vendor: SanDisk model: SL32G size: 29.72 GiB block size:  
 physical: 512 B logical: 512 B serial: <filter> scheme: MBR  
 ID-2: /dev/sda vendor: Lexar model: SSD size: 111.79 GiB block size:  
 physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 6 scheme: MBR  
 ID-3: /dev/sdb vendor: Dogfish model: SSD 128GB size: 119.24 GiB block size:  
 physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 7A  
 scheme: MBR  
Partition:
 ID-1: / raw size: 109.76 GiB size: 107.53 GiB (97.97%) used: 8.88 GiB (8.3%)  
 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:
 System Temperatures: cpu: 35.0 C mobo: N/A  
 Fan Speeds (RPM): cpu: 0  
Repos:
 No active apt repos in: /etc/apt/sources.list  
 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
 2: deb http://mxrepo.com/mx/repo/ buster ahs
 No active apt repos in: /etc/apt/sources.list.d/various.list  
Info:
 Processes: 188 Uptime: 19m Memory: 7.69 GiB used: 646.9 MiB (8.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  




Well, enough complaints for today. Did I mention that I love what you are doing? KDE on MX is absolutely awesome! Thank You so much for creating this awesome distro. With recent "Snappy" developments (which I will not discuss further) it is very likely MX will become my primary production OS! Thanks again!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 3:58 am
by asqwerth
Pls provide your Quick System Info for some context on the issues you have encountered. You are using an old ThinkPad, perhaps the sound card might have some bearing on your sounds issues.

I've not had issues adding MX tools and other apps to panel (nor using pin to taskbar).

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 8:43 am
by Gerson
I'm having problems with small freezes having only Vivaldi open with 4 tabs, Telegram and TextMaker. Sometimes it recovers by itself, in less than a minute, in other times it closes everything and leaves a black screen, I have to turn it off with the button and in other occasions it closes and returns me to the Login screen.

Code: Select all

System:
  Host: mx Kernel: 5.6.0-2-amd64 x86_64 bits: 64 
  compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=340b7a5c-2bba-41ae-ab7a-3c8ae3912a33 ro quiet 
  splash 
  Desktop: KDE Plasma 5.14.5 info: latte-dock 
  wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: NOBLEX product: SF20BA v: N/A 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: NOBLEX model: SF20BA serial: <filter> 
  UEFI: American Megatrends v: 3.02.00.NOL.Test7 x64 
  date: 07/14/2017 
Battery:
  ID-1: BAT1 charge: 29.0 Wh 
  condition: 29.0/30.4 Wh (96%) volts: 8.6/7.6 
  model: Standard SF20BA type: Li-ion serial: <filter> 
  status: Unknown 
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: 1308 MHz min/max: 480/2480 MHz 
  Core speeds (MHz): 1: 1308 2: 702 
  Vulnerabilities: Type: itlb_multihit 
  status: Not affected 
  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 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
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 compositor: kwin_x11 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (BSW) 
  v: 4.6 Mesa 20.0.7 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Atom/Celeron/Pentium Processor 
  x5-E8000/J3xxx/N3xxx Series High Definition Audio 
  vendor: Elite Systems driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:2284 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel 
  port: f040 bus ID: 03:00.0 chip ID: 8086:3165 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 119.24 GiB 
  used: 62.99 GiB (52.8%) 
  ID-1: /dev/sda vendor: Foresee model: 128GB SSD 
  size: 119.24 GiB block size: physical: 512 B 
  logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2 
  scheme: GPT 
Partition:
  ID-1: / raw size: 17.33 GiB size: 16.94 GiB (97.71%) 
  used: 7.65 GiB (45.2%) fs: ext4 dev: /dev/sda3 
  ID-2: /home raw size: 29.30 GiB 
  size: 28.71 GiB (98.00%) used: 15.09 GiB (52.6%) 
  fs: ext4 dev: /dev/sda4 
  ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 5 (default 60) 
  cache pressure: 50 (default 100) dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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 https://espejito.fder.edu.uy/mxlinux/packages/mx/repo/ buster main non-free
  2: deb https://espejito.fder.edu.uy/mxlinux/packages/mx/repo/ buster ahs
  Active apt repos in: /etc/apt/sources.list.d/softmaker.list 
  1: deb http://shop.softmaker.com/repo/apt wheezy non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 202 Uptime: 11m Memory: 3.76 GiB 
  used: 1.33 GiB (35.3%) 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.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 10:46 am
by Sparky
Adrian wrote: Sun Jul 12, 2020 11:43 pm
seaken64 wrote: Sun Jul 12, 2020 11:11 pm @d_o - thank you. I missed that app. It did ask me for the password when I launched it. I guess I was trying to learn the KDE way.

Seaken64
Yeah, we'd like to fix that, it would be great if somebody could point us to a fix or something, it's hard to believe that KDE is broken like that in Buster...
to change the time in KDE, right click on the time icon and select congigure digital clock, there you will find a few things you can change.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 2:12 pm
by MAYBL8
I know I might be getting ahead of things but will we be able to get newer releases of KDE in the Test Repo in the future?
Like 5.19 or 5.20? Since we are 5.14.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 2:43 pm
by dolphin_oracle
MAYBL8 wrote: Mon Jul 13, 2020 2:12 pm I know I might be getting ahead of things but will we be able to get newer releases of KDE in the Test Repo in the future?
Like 5.19 or 5.20? Since we are 5.14.
probably not.

the Qt library situation in debian...is problematic.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 5:21 pm
by danielson
MX KDE is the best thus far!
It's probably the longest i have ever run a Linux OS and as beta, it hasn't crashed a single time from day one!

Kudos to the MX team!!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 5:30 pm
by uncle mark
dolphin_oracle wrote: Mon Jul 13, 2020 2:43 pm
MAYBL8 wrote: Mon Jul 13, 2020 2:12 pm I know I might be getting ahead of things but will we be able to get newer releases of KDE in the Test Repo in the future?
Like 5.19 or 5.20? Since we are 5.14.
probably not.

the Qt library situation in debian...is problematic.
Latest and greatest should be way down the priority list.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 5:32 pm
by seaken64
Sparky wrote: Mon Jul 13, 2020 10:46 am
Adrian wrote: Sun Jul 12, 2020 11:43 pm
seaken64 wrote: Sun Jul 12, 2020 11:11 pm @d_o - thank you. I missed that app. It did ask me for the password when I launched it. I guess I was trying to learn the KDE way.

Seaken64
Yeah, we'd like to fix that, it would be great if somebody could point us to a fix or something, it's hard to believe that KDE is broken like that in Buster...
to change the time in KDE, right click on the time icon and select congigure digital clock, there you will find a few things you can change.
That didn't work for me. There appears to be some bug in that applet and it won't ask and accept a password. Hopefully that applet can be disabled and the MX Date&Time app can be run in it's place.

Seaken64

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 5:41 pm
by Gerson
That's funny. I was just expressing my problem here about the untimely freezing and shutting down so that everything now works normally.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 5:44 pm
by Adrian
seaken64 wrote: Mon Jul 13, 2020 5:32 pm
Sparky wrote: Mon Jul 13, 2020 10:46 am
Adrian wrote: Sun Jul 12, 2020 11:43 pm

Yeah, we'd like to fix that, it would be great if somebody could point us to a fix or something, it's hard to believe that KDE is broken like that in Buster...
to change the time in KDE, right click on the time icon and select congigure digital clock, there you will find a few things you can change.
That didn't work for me. There appears to be some bug in that applet and it won't ask and accept a password. Hopefully that applet can be disabled and the MX Date&Time app can be run in it's place.

Seaken64
It works only if you boot systemd, that function seems to depend on systemd.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Mon Jul 13, 2020 8:03 pm
by ChrisLilly
Hi Asqwerth, I added my system info to the text above for July 13th. I hope the feedback is helpful, and not just a fluke of this 9 year old laptop. Cheers, and thanks for all your work on this system!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 6:43 am
by kajakob
sorry - the DAU's are not dying out ...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 6:54 am
by asqwerth
ChrisLilly wrote: Mon Jul 13, 2020 8:03 pm Hi Asqwerth, I added my system info to the text above for July 13th. I hope the feedback is helpful, and not just a fluke of this 9 year old laptop. Cheers, and thanks for all your work on this system!
It may very well be that the AHS kernel is too new and not a good fit for your old 9-yr-old laptop; I do not know. Perhaps someone else can.

Since we are a small team, the MX KDE iso will be released only in 64-bit version with the newer AHS kernel.

If the live USB kind of works for you except for sound, you might wish to see if you could - while running live - install (using the mx live kernel updater tool) the 4.19 kernel that comes with the standard release of MX19, and then remaster the live usb stick to boot from the 4.19 kernel instead to see if the sound works with that.

Tutorial: https://www.youtube.com/watch?v=UWvwbwTGOZ8&t=2s

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 8:38 am
by kc1di
I've been testing the live iso and so far working well. only thing is a error message during boot that says "can not sync dB" or something like that. It appears just before the desktop begins to load.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 9:20 am
by dolphin_oracle
kc1di wrote: Tue Jul 14, 2020 8:38 am I've been testing the live iso and so far working well. only thing is a error message during boot that says "can not sync dB" or something like that. It appears just before the desktop begins to load.
thanks, we think that one is fixed for beta 2 (coming soon-ish)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 10:38 am
by asqwerth
Pdf arranger on the Beta iso does not work:

Code: Select all

pdfarranger
Traceback (most recent call last):
  File "/usr/bin/pdfarranger", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 10:43 am
by kc1di
dolphin_oracle wrote: Tue Jul 14, 2020 9:20 am
kc1di wrote: Tue Jul 14, 2020 8:38 am I've been testing the live iso and so far working well. only thing is a error message during boot that says "can not sync dB" or something like that. It appears just before the desktop begins to load.
thanks, we think that one is fixed for beta 2 (coming soon-ish)
Did not get it after install. Like what I see so far :)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 11:21 am
by Adrian
asqwerth wrote: Tue Jul 14, 2020 10:38 am Pdf arranger on the Beta iso does not work:

Code: Select all

pdfarranger
Traceback (most recent call last):
  File "/usr/bin/pdfarranger", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
Thanks, there's a package missing: python3-pkg-resources I will add it in Beta2.
Frankly that is a pdfarranger problem, it should list that as a dependency, somebody should file a bug with pdfarranger maintainer...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 11:33 am
by kc1di
Thanks for all you do Adrian I really like kde

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 12:31 pm
by SwampRabbit
Adrian wrote: Tue Jul 14, 2020 11:21 am
asqwerth wrote: Tue Jul 14, 2020 10:38 am Pdf arranger on the Beta iso does not work:

Code: Select all

pdfarranger
Traceback (most recent call last):
  File "/usr/bin/pdfarranger", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
Thanks, there's a package missing: python3-pkg-resources I will add it in Beta2.
Frankly that is a pdfarranger problem, it should list that as a dependency, somebody should file a bug with pdfarranger maintainer...
I'll post an issue on their GitHub. DONE

It may be a Debian specific issue that it doesn't get installed, I've seen this happen now with python requirements not pulling in others on a few packages now, even when the developer states what "should work".

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 2:17 pm
by JuhaT
When I try to install the Nvidia proprietary driver through MX-Tools Nvidia driver installer there is problem starting with systemd. It comes to the login window for a second or so but quickly changes to three dots and a prompt to login through CLI, not the graphical login window. When I write the credentials nothing happens.
If I reboot and change to the sysvinit start all is fine.
I have reverted back to the Noveau driver for now but I provide the ddm.log below

Code: Select all


System:
  Host: mxkde Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=12b63c5c-8ce8-4c68-b753-32819f0ddb9c ro quiet splash 
  init=/lib/systemd/systemd 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Gigabyte product: Z390 GAMING X v: N/A serial: <filter> 
  Mobo: Gigabyte model: Z390 GAMING X-CF v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F9 date: 10/15/2019 
CPU:
  Topology: 8-Core model: Intel Core i7-9700K bits: 64 type: MCP arch: Kaby Lake 
  family: 6 model-id: 9E (158) stepping: D (13) microcode: D6 L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57600 
  Speed: 3099 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 3099 2: 1873 3: 3106 
  4: 1794 5: 2541 6: 2007 7: 2327 8: 2780 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  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: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds mitigation: TSX disabled 
  Type: tsx_async_abort mitigation: TSX disabled 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:1b81 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 tty: N/A 
  OpenGL: renderer: NV134 v: 4.3 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 3.29 TiB used: 55.36 GiB (1.6%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q 
  scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST2000DX001-1CM164 size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
  serial: <filter> rev: CC43 temp: 28 C scheme: MBR 
  ID-3: /dev/sdc vendor: Samsung model: SSD 850 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-4: /dev/sdd vendor: Samsung model: SSD 860 EVO M.2 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 3B6Q scheme: MBR 
  ID-5: /dev/sde type: USB vendor: Western Digital model: WDS1 20G2G0A-00JH30 
  size: 111.80 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 0107 
Partition:
  ID-1: / raw size: 29.34 GiB size: 28.76 GiB (98.00%) used: 8.07 GiB (28.1%) 
  fs: ext4 dev: /dev/sdc1 
  ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 47.28 GiB (23.7%) 
  fs: ext4 dev: /dev/sdc2 
Sensors:
  System Temperatures: cpu: 36.0 C mobo: 27.8 C gpu: nouveau temp: 30 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1512 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  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/megasync.list 
  1: deb https://mega.nz/linux/MEGAsync/Debian_10.0/ ./
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster main non-free
  2: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 262 Uptime: 14m Memory: 23.49 GiB used: 1.78 GiB (7.6%) Init: systemd 
  v: 241 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.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 2:48 pm
by SwampRabbit
Adrian wrote: Tue Jul 14, 2020 11:21 am
asqwerth wrote: Tue Jul 14, 2020 10:38 am Pdf arranger on the Beta iso does not work:

Code: Select all

pdfarranger
Traceback (most recent call last):
  File "/usr/bin/pdfarranger", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
Thanks, there's a package missing: python3-pkg-resources I will add it in Beta2.
Frankly that is a pdfarranger problem, it should list that as a dependency, somebody should file a bug with pdfarranger maintainer...
We are using pdfarranger 1.1.1 from Debian stable, I am going to package pdfarranger 1.4.2 from Bullseye.

EDIT: Stevo already had pdfarranger 1.4.2 in the Test Repo, but I've updated it, tested it, and sent it for inclusion in the repo.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 5:40 pm
by kc1di
When I right click on the menu Icon and click on edit applications nothing happens. So there must be some kind of bug with that also. Hope it can be fixed.
Thanks.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 6:40 pm
by Adrian
kc1di wrote: Tue Jul 14, 2020 5:40 pm When I right click on the menu Icon and click on edit applications nothing happens. So there must be some kind of bug with that also. Hope it can be fixed.
Thanks.
Thanks, kmenuedit package is missing I will add it in Beta2.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 6:40 pm
by Gerson
kc1di wrote: Tue Jul 14, 2020 5:40 pm When I right click on the menu Icon and click on edit applications nothing happens. So there must be some kind of bug with that also. Hope it can be fixed.
Thanks.
I tried and I got exactly the same thing.
EDIT:
I just installed the missing package "kmenuedit" and it works perfectly.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 7:10 pm
by Gerson
From a few days ago, every time I install a package through the terminal I get the following:

Code: Select all

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.986: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.986: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.987: Theme parsing error: gtk.css:129:34: The style property GtkCheckButton:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.987: Theme parsing error: gtk.css:130:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.988: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.989: Theme parsing error: gtk.css:135:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.991: Theme parsing error: gtk.css:142:29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:16.052: Theme parsing error: gtk.css:3691:13: Not using units is deprecated. Assuming 'px'.

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.226: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.226: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.227: Theme parsing error: gtk.css:129:34: The style property GtkCheckButton:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.228: Theme parsing error: gtk.css:130:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.228: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.229: Theme parsing error: gtk.css:135:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.230: Theme parsing error: gtk.css:142:29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.271: Theme parsing error: gtk.css:3691:13: Not using units is deprecated. Assuming 'px'.
What can it be and how do I fix it?

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 7:36 pm
by Adrian
What can it be and how do I fix it?
Don't look at it :grin:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 7:38 pm
by Eadwine Rose
:laugh:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 7:39 pm
by fehlix
Adrian wrote: Tue Jul 14, 2020 7:36 pm
What can it be and how do I fix it?
Don't look at it :grin:
> /dev/null

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 7:58 pm
by kc1di
Adrian wrote: Tue Jul 14, 2020 6:40 pm
kc1di wrote: Tue Jul 14, 2020 5:40 pm When I right click on the menu Icon and click on edit applications nothing happens. So there must be some kind of bug with that also. Hope it can be fixed.
Thanks.
Thanks, kmenuedit package is missing I will add it in Beta2.
Thanks to you and Gerson Fixed :)

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 9:45 pm
by fehlix
JuhaT wrote: Tue Jul 14, 2020 2:17 pm When I try to install the Nvidia proprietary driver through MX-Tools Nvidia driver installer there is problem starting with systemd. It comes to the login window for a second or so but quickly changes to three dots and a prompt to login through CLI, not the graphical login window. When I write the credentials nothing happens.
If I reboot and change to the sysvinit start all is fine.
I have reverted back to the Noveau driver for now but I provide the ddm.log below
Hmm.., the three dots are rather an indication that plymouth boot-screen-animation is not working with nvidia and systemd. I wonder whether disabling/uninstall plymouth would help for systemd + nvidia.
Note: plymouth does not do much in systemd-boot anyway, as normaly systemd-boot is fairly fast, so plymouth boot screan is short anyway. Simplest to disable plymouth would be using MX Boot option -> disable splash.
:puppy:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Tue Jul 14, 2020 9:54 pm
by dolphin_oracle
the three dots is the fallback plymouth "text" theme. This often happens with the nvidia driver in any case when modesetting isn't supported properly.

now why that would be true under systemd vs. sysVinit, I really don't know. but in this case, plymouth is starting and finishing.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 15, 2020 8:37 am
by paul1149
Gerson wrote: Tue Jul 14, 2020 7:10 pm From a few days ago, every time I install a package through the terminal I get the following:

Code: Select all

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.986: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version
...
What can it be and how do I fix it?
You can get around this by editing the theme. In my case it was Breeze. Go to the text file as root and comment out the offending lines. They're not processed anyway, I believe, so no loss. In the above example it's line 127. Make a backup before editing.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 15, 2020 9:05 am
by fehlix
Gerson wrote: Tue Jul 14, 2020 7:10 pm From a few days ago, every time I install a package through the terminal I get the following:

Code: Select all

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.986: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.986: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.987: Theme parsing error: gtk.css:129:34: The style property GtkCheckButton:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.987: Theme parsing error: gtk.css:130:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.988: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.989: Theme parsing error: gtk.css:135:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:15.991: Theme parsing error: gtk.css:142:29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:674): Gtk-WARNING **: 19:41:16.052: Theme parsing error: gtk.css:3691:13: Not using units is deprecated. Assuming 'px'.

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.226: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.226: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.227: Theme parsing error: gtk.css:129:34: The style property GtkCheckButton:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.228: Theme parsing error: gtk.css:130:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.228: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.229: Theme parsing error: gtk.css:135:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.230: Theme parsing error: gtk.css:142:29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore. It will be removed in a future version

(dpkg-preconfigure:672): Gtk-WARNING **: 19:41:16.271: Theme parsing error: gtk.css:3691:13: Not using units is deprecated. Assuming 'px'.
What can it be and how do I fix it?
A proper fix to avoid those warnings would look like this:
First install debconf-kde-helper

Code: Select all

sudo apt install  debconf-kde-helper
Next set the default DEBIAN_FRONTEND to Kde by running this from terminal command line:

Code: Select all

mx-pkexec  env  DEBIAN_FRONTEND=kde dpkg-reconfigure debconf
and change from current Gnome
kde_debian_frontend-1.png
to Kde so it looks like this:
kde_debian_frontend-2.png
HTH
:puppy:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 15, 2020 1:25 pm
by Gerson
Thank you very much @fehlix I just did it and it was fixed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Wed Jul 15, 2020 1:27 pm
by Gerson
I have a problem; Openastro.org installed from the stable repository, it runs but the screen remains black, it doesn't show anything.
When you run it through the terminal this appears and there are no graphics, just an empty screen.

Code: Select all

ghermain@mx:~
$ openastro
Gtk-Message: 15:55:44.099: Failed to load module "canberra-gtk-module"
/usr/bin/openastro:1151: DeprecationWarning: Gdk.Screen.get_width is deprecated
  self.screen_width = screen.get_width()
/usr/bin/openastro:1152: DeprecationWarning: Gdk.Screen.get_height is deprecated
  self.screen_height = screen.get_height()
/usr/bin/openastro:1208: DeprecationWarning: Rsvg.set_default_dpi is deprecated
  Rsvg.set_default_dpi(400)

(openastro:20360): Gtk-WARNING **: 15:55:44.373: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:20360): Gtk-WARNING **: 15:55:44.373: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:20360): Gtk-WARNING **: 15:55:44.374: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:20360): Gtk-WARNING **: 15:55:44.410: Theme parsing error: gtk.css:3647:13: Not using units is deprecated. Assuming 'px'.
/usr/bin/openastro:2838: DeprecationWarning: Gtk.UIManager.add_ui_from_file is deprecated
  self.ui_mid = self.uimanager.add_ui_from_file(cfg.xml_ui)
/usr/bin/openastro:2839: DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
  accelgroup = self.uimanager.get_accel_group()
/usr/bin/openastro:5567: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self.actiongroup = Gtk.ActionGroup('UIManagerExample')
/usr/bin/openastro:5577: DeprecationWarning: Gtk.UIManager.new_merge_id is deprecated
  self.ui_mid_history = self.uimanager.new_merge_id()
/usr/bin/openastro:5582: DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
  self.actiongroup.get_action('Quit').set_property('short-label', _('Quit') )
/usr/bin/openastro:5603: DeprecationWarning: Gtk.UIManager.add_ui is deprecated
  self.uimanager.add_ui(self.ui_mid_history, '/MenuBar/File/History', 'history%i'%(i), 'history%i'%(i), Gtk.UIManagerItemType.MENUITEM, False)
/usr/bin/openastro:5604: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name, label, tooltip, stock_id" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  action=Gtk.Action('history%i'%(i),label,None,False)
/usr/bin/openastro:5606: DeprecationWarning: Gtk.Action.set_visible is deprecated
  action.set_visible(visible)
/usr/bin/openastro:5607: DeprecationWarning: Gtk.ActionGroup.add_action is deprecated
  self.actiongroup.add_action(action)
/usr/bin/openastro:5613: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name, label, tooltip, stock_id" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  action=Gtk.Action('quickopendatabase%s'%(i),self.DB[i]["name"],None,False)
/usr/bin/openastro:5620: DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
  self.uimanager.ensure_update()
/usr/bin/openastro:2895: DeprecationWarning: Gtk.UIManager.get_widget is deprecated
  menubar = self.uimanager.get_widget('/MenuBar')
sun 113.72773216121256 black moon 19.096398376777024 sun-bm 94.63133378443553=94.63133378443553
sbm 60-120
54.70683683552817 113.72773216121256 300.97910467431564
/usr/bin/openastro:2905: DeprecationWarning: Gtk.ScrolledWindow.add_with_viewport is deprecated
  scrolledwindow.add_with_viewport(self.draw)
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'


Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 8:47 am
by paul1149
fehlix wrote: Wed Jul 15, 2020 9:05 am A proper fix to avoid those warnings would look like this:
Thanks, fehlix, for the actual remedy. In all my searching a few months ago all I could find was the workaround.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 9:32 am
by andyprough
This is brilliant fehlix!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 12:52 pm
by SwampRabbit
Gerson wrote: Wed Jul 15, 2020 1:27 pm I have a problem; Openastro.org installed from the stable repository, it runs but the screen remains black, it doesn't show anything...
Gerson, can you try and install libcanberra-gtk-module either using MXPI or synaptic and see if this application works now?

A similar report was done for missing gtk-modules, which probably were not included in the ISO.
The other report was for pdfarranger, which after talking with the developer, he told me it isn't needed for pdfarranger, but the warning still exists if I package it without it as a dependency.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 4:22 pm
by Gerson
SwampRabbit wrote: Thu Jul 16, 2020 12:52 pm
Gerson wrote: Wed Jul 15, 2020 1:27 pm
I completely uninstalled the Openastro application and restarted it. Look for the package libcanberra-gtk-module in MXIP and it is neither in stable nor in the test repository. In the package manager Muon tells me that it is installed and so does Synaptic with version 0.30-7. I try again to install Openastro including the option Also Install "recommended" packages and when running it by graphical mode it follows the same empty screen without the corresponding graphics.
When I run it through the terminal the result is this:

Translated with www.DeepL.com/Translator (free version)

Code: Select all

ghermain@mx:~
$ openastro
Gtk-Message: 17:13:10.068: Failed to load module "canberra-gtk-module"
/usr/bin/openastro:1151: DeprecationWarning: Gdk.Screen.get_width is deprecated
  self.screen_width = screen.get_width()
/usr/bin/openastro:1152: DeprecationWarning: Gdk.Screen.get_height is deprecated
  self.screen_height = screen.get_height()
/usr/bin/openastro:1208: DeprecationWarning: Rsvg.set_default_dpi is deprecated
  Rsvg.set_default_dpi(400)

(openastro:4942): Gtk-WARNING **: 17:13:10.302: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.302: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.303: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.341: Theme parsing error: gtk.css:3647:13: Not using units is deprecated. Assuming 'px'.
/usr/bin/openastro:2838: DeprecationWarning: Gtk.UIManager.add_ui_from_file is deprecated
  self.ui_mid = self.uimanager.add_ui_from_file(cfg.xml_ui)
/usr/bin/openastro:2839: DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
  accelgroup = self.uimanager.get_accel_group()
/usr/bin/openastro:5567: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self.actiongroup = Gtk.ActionGroup('UIManagerExample')
/usr/bin/openastro:5577: DeprecationWarning: Gtk.UIManager.new_merge_id is deprecated
  self.ui_mid_history = self.uimanager.new_merge_id()
/usr/bin/openastro:5582: DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
  self.actiongroup.get_action('Quit').set_property('short-label', _('Quit') )
/usr/bin/openastro:5603: DeprecationWarning: Gtk.UIManager.add_ui is deprecated
  self.uimanager.add_ui(self.ui_mid_history, '/MenuBar/File/History', 'history%i'%(i), 'history%i'%(i), Gtk.UIManagerItemType.MENUITEM, False)
/usr/bin/openastro:5604: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name, label, tooltip, stock_id" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  action=Gtk.Action('history%i'%(i),label,None,False)
/usr/bin/openastro:5606: DeprecationWarning: Gtk.Action.set_visible is deprecated
  action.set_visible(visible)
/usr/bin/openastro:5607: DeprecationWarning: Gtk.ActionGroup.add_action is deprecated
  self.actiongroup.add_action(action)
/usr/bin/openastro:5620: DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
  self.uimanager.ensure_update()
/usr/bin/openastro:2895: DeprecationWarning: Gtk.UIManager.get_widget is deprecated
  menubar = self.uimanager.get_widget('/MenuBar')
sun 114.73325007995733 black moon 19.214323241210998 sun-bm 95.51892683874632=95.51892683874632
sbm 60-120
67.67196143933771 114.73325007995733 312.93871135938036
/usr/bin/openastro:2905: DeprecationWarning: Gtk.ScrolledWindow.add_with_viewport is deprecated
  scrolledwindow.add_with_viewport(self.draw)
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 4:32 pm
by srq2625
I attempted to read the entire thread, but ... well, it is 26 pages long.

Anyway, because I wasn't able to read the entire thread, I don't know if this has been posted or not. But, I thought this might be of interest.

I got the attached output when installing the nVidia driver using the wonder MX supplied tool.

-->EDIT TO ADD: TL;DR - I think this is the same "canberra-gtk-module" issue as noted below, but as I'm not even close to being a Linux dev, I have no real idea. Note that I do have available to me (but is not installed) libcanberra-gtk3-module.

Code: Select all

$ apt policy libcanberra-gtk3-mo*
libcanberra-gtk3-module:
  Installed: (none)
  Candidate: 0.30-7
  Version table:
     0.30-7 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
As one can see from my QSI, the nVidia driver(s) did install:

Code: Select all

System:    Host: BlackBoxKDE Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 root=UUID=80809185-4b1f-4c7f-9570-80724da5d01d ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 2008 
           date: 12/06/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 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: 800820D L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108794 
           Speed: 1311 MHz min/max: 1550/3400 MHz boost: disabled Core speeds (MHz): 1: 1311 2: 1605 3: 2794 4: 1281 5: 2002 
           6: 1328 7: 2205 8: 1422 9: 2589 10: 1273 11: 2148 12: 1335 13: 1371 14: 1522 15: 1284 16: 2694 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GF106 [GeForce GTS 450] driver: nvidia v: 390.138 bus ID: 08:00.0 chip ID: 10de:0dc4 
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           compositor: kwin_x11 resolution: 1600x1200~60Hz, 1600x1200~60Hz 
           OpenGL: renderer: GeForce GTS 450/PCIe/SSE2 v: 4.6.0 NVIDIA 390.138 direct render: Yes 
Audio:     Device-1: NVIDIA GF106 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 10de:0be9 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Sound Server: ALSA v: k5.6.0-2-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: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 229.38 GiB (49.2%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
Partition: ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) used: 7.10 GiB (24.1%) fs: ext4 dev: /dev/sda3 
           ID-2: /home raw size: 419.51 GiB size: 411.92 GiB (98.19%) used: 221.88 GiB (53.9%) fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A gpu: nvidia temp: 42 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 351 Uptime: 5m Memory: 15.64 GiB used: 1.49 GiB (9.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.36 


Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 5:07 pm
by fehlix
Gerson wrote: Thu Jul 16, 2020 4:22 pm I completely uninstalled the Openastro application and restarted it. Look for the package libcanberra-gtk-module in MXIP and it is neither in stable nor in the test repository. In the package manager Muon tells me that it is installed and so does Synaptic with version 0.30-7. I try again to install Openastro including the option Also Install "recommended" packages and when running it by graphical mode it follows the same empty screen without the corresponding graphics.
When I run it through the terminal the result is this:

Translated with www.DeepL.com/Translator (free version)

Code: Select all

ghermain@mx:~
$ openastro
Gtk-Message: 17:13:10.068: Failed to load module "canberra-gtk-module"
/usr/bin/openastro:1151: DeprecationWarning: Gdk.Screen.get_width is deprecated
  self.screen_width = screen.get_width()
/usr/bin/openastro:1152: DeprecationWarning: Gdk.Screen.get_height is deprecated
  self.screen_height = screen.get_height()
/usr/bin/openastro:1208: DeprecationWarning: Rsvg.set_default_dpi is deprecated
  Rsvg.set_default_dpi(400)

(openastro:4942): Gtk-WARNING **: 17:13:10.302: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.302: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.303: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

(openastro:4942): Gtk-WARNING **: 17:13:10.341: Theme parsing error: gtk.css:3647:13: Not using units is deprecated. Assuming 'px'.
/usr/bin/openastro:2838: DeprecationWarning: Gtk.UIManager.add_ui_from_file is deprecated
  self.ui_mid = self.uimanager.add_ui_from_file(cfg.xml_ui)
/usr/bin/openastro:2839: DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
  accelgroup = self.uimanager.get_accel_group()
/usr/bin/openastro:5567: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self.actiongroup = Gtk.ActionGroup('UIManagerExample')
/usr/bin/openastro:5577: DeprecationWarning: Gtk.UIManager.new_merge_id is deprecated
  self.ui_mid_history = self.uimanager.new_merge_id()
/usr/bin/openastro:5582: DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
  self.actiongroup.get_action('Quit').set_property('short-label', _('Quit') )
/usr/bin/openastro:5603: DeprecationWarning: Gtk.UIManager.add_ui is deprecated
  self.uimanager.add_ui(self.ui_mid_history, '/MenuBar/File/History', 'history%i'%(i), 'history%i'%(i), Gtk.UIManagerItemType.MENUITEM, False)
/usr/bin/openastro:5604: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "name, label, tooltip, stock_id" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  action=Gtk.Action('history%i'%(i),label,None,False)
/usr/bin/openastro:5606: DeprecationWarning: Gtk.Action.set_visible is deprecated
  action.set_visible(visible)
/usr/bin/openastro:5607: DeprecationWarning: Gtk.ActionGroup.add_action is deprecated
  self.actiongroup.add_action(action)
/usr/bin/openastro:5620: DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
  self.uimanager.ensure_update()
/usr/bin/openastro:2895: DeprecationWarning: Gtk.UIManager.get_widget is deprecated
  menubar = self.uimanager.get_widget('/MenuBar')
sun 114.73325007995733 black moon 19.214323241210998 sun-bm 95.51892683874632=95.51892683874632
sbm 60-120
67.67196143933771 114.73325007995733 312.93871135938036
/usr/bin/openastro:2905: DeprecationWarning: Gtk.ScrolledWindow.add_with_viewport is deprecated
  scrolledwindow.add_with_viewport(self.draw)
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
It works here:
openastro-mx-kde.png
But I still get this line

Code: Select all

/usr/bin/openastro                          
Gtk-Message: 22:58:25.036: Failed to load module "canberra-gtk-module"
and some warnings.
With running this:

Code: Select all

sudo apt install libcanberra-gtk3-module
At least the line "Failed to load module "canberra-gtk-module"" is gone.
Warnings and "deprecated" messages can be ignored and are more imported for the developer, to adjust to code.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 5:08 pm
by SwampRabbit
Gerson wrote: Thu Jul 16, 2020 4:22 pm Look for the package libcanberra-gtk-module in MXIP and it is neither in stable nor in the test repository. In the package manager Muon tells me that it is installed and so does Synaptic with version 0.30-7. I try again to install Openastro including the option Also Install "recommended" packages and when running it by graphical mode it follows the same empty screen without the corresponding graphics.
My apologies, it probably doesn't show in MXPI because you have to uncheck the "Hide library and developer packages" in the lower right of screen.

can you also check for libcanberra-gtk3-module?
Notice the 3 in the name.

I believe it is related a GTK3 issue, but don't know where or what yet.

EDIT: ninja'd by the great bot fehlix

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 5:19 pm
by srq2625
I don't know if this is a thing to be concerned about but ....

I can (and have) run the KDE Partition Manager directly from the menu and modify/delete/create partitions and the partition table of any device attached to the computer WITHOUT having to first enter a password to elevate privileges.

When I install and run gparted, it does (as I think it should) prompt me for the appropriate password before it will finish loading.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 5:32 pm
by fehlix
srq2625 wrote: Thu Jul 16, 2020 5:19 pm I don't know if this is a thing to be concerned about but ....

I can (and have) run the KDE Partition Manager directly from the menu and modify/delete/create partitions and the partition table of any device attached to the computer WITHOUT having to first enter a password to elevate privileges.

When I install and run gparted, it does (as I think it should) prompt me for the appropriate password before it will finish loading.
Most Kde tools do it that way and only ask for a password before the action is performed.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Thu Jul 16, 2020 9:05 pm
by phirephoto
Hi All,

Running the latest MX Beta. 2 Oddities / questions:
First, I've set the disable mouse while typing to - almost anything. I think it's now set at 500 ms. But STILL often my cursor ends up somewhere else and I'm typing where I don't intend to, while actively typing (ie it's not like I pause - just right in the middle of a sentence I see my typing is now in like a previous paragraph. I'm pretty sure I may be accidentally hitting the touchpad - it's a laptop. Any other setting I'm missing?

Second is DNS - I have MX on a LAN with a few other Windows machines. From each machine, I can ping the local name - IE my desktop is called DESKTOP, I have a NUC called NUC, etc. From desktop, I can PING NUC and it resolves - to NUC.local. On the MX (laptop), I can't ping / resolve without adding .local. Is there a way to force this in for local machines?
My /etc/resolv.conf has
nameserver 192.168.1.1 (this is correct)
search local mx.local

I've tried removing mx.local from the resolv.conf, but as soon as I reboot, it's back.

Any suggestions / hints?

Thanks!

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 2:22 am
by Stevo
Half a second seems too short a time to me to keep the pad disabled while typing, unless you never stop typing for even half a second.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 6:52 am
by Gerson
@fehlix and @SwampRabbit
I have done all the steps indicated, this application in XFCE always worked well but now in MX-KDE it doesn't show the graphics.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 8:24 am
by fehlix
Gerson wrote: Fri Jul 17, 2020 6:52 am I have done all the steps indicated, this application in XFCE always worked well but now in MX-KDE it doesn't show the graphics.
OK, something else missing:

Code: Select all

sudo apt install python3-gi-cairo
:puppy:

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 8:46 am
by srq2625
fehlix wrote: Thu Jul 16, 2020 5:32 pm
srq2625 wrote: Thu Jul 16, 2020 5:19 pm I don't know if this is a thing to be concerned about but ....

I can (and have) run the KDE Partition Manager directly from the menu and modify/delete/create partitions and the partition table of any device attached to the computer WITHOUT having to first enter a password to elevate privileges.

When I install and run gparted, it does (as I think it should) prompt me for the appropriate password before it will finish loading.
Most Kde tools do it that way and only ask for a password before the action is performed.
This I understand. However, on that install and for that one time, I was looking for and don't remember being prompted for a password. But, maybe my recollection is faulty.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 9:16 am
by fehlix
srq2625 wrote: Fri Jul 17, 2020 8:46 am
fehlix wrote: Thu Jul 16, 2020 5:32 pm
srq2625 wrote: Thu Jul 16, 2020 5:19 pm I don't know if this is a thing to be concerned about but ....

I can (and have) run the KDE Partition Manager directly from the menu and modify/delete/create partitions and the partition table of any device attached to the computer WITHOUT having to first enter a password to elevate privileges.

When I install and run gparted, it does (as I think it should) prompt me for the appropriate password before it will finish loading.
Most Kde tools do it that way and only ask for a password before the action is performed.
This I understand. However, on that install and for that one time, I was looking for and don't remember being prompted for a password. But, maybe my recollection is faulty.
It might have been using sudo authentication undeneath, which does have a authentication timeout from about 15 minutes. So if you have authenticated earlier with sudo based authetication, you might not have been asked again during that timeout.
You can always reset/clear sudo-timeout with "sudo -k"

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 9:32 am
by Gerson
fehlix wrote: Fri Jul 17, 2020 8:24 am
Gerson wrote: Fri Jul 17, 2020 6:52 am I have done all the steps indicated, this application in XFCE always worked well but now in MX-KDE it doesn't show the graphics.
OK, something else missing:

Code: Select all

sudo apt install python3-gi-cairo
:puppy:
Now you're talking! Perfect; thank you very much @fehlix

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 11:48 am
by chrispop99
Alt-F1 is configured to open the Application Launcher. It is possible to use Alt-F1 to open the User Manual, as in our other versions, but no way to get the Meta key to start the Application Launcher. (Research suggests it's a known bug in the version of KDE we are using.)

How will this be dealt with? Personally I feel we need to keep Alt-F1 for the manual, or support is going to be confusing.

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 12:19 pm
by dolphin_oracle
my super_l "windows" key opens the menu fine.

using alt+f1 for the help is a good idea. just launches mx-manual...

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 12:37 pm
by Adrian
I'm having problems setting up shortcuts globally, I tried to add Ctrl-Alt-T for Konsole but something went wrong. In general I think we should leave the KDE default shortcuts as they are if possible.

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 1:30 pm
by chrispop99
dolphin_oracle wrote: Fri Jul 17, 2020 12:19 pm my super_l "windows" key opens the menu fine.

using alt+f1 for the help is a good idea. just launches mx-manual...
Sorry, I didn't explain properly.

OOTB, either Alt-F1 or Meta open the menu. As soon as you change Alt-F1 to the manual, which works fine, the Meta key no longer opens the menu, nor can it be made to do so.

It seems you can't set a keybinding to a single key, or at least not to the Meta key.

There are lots of reports online, and it would appear to be a known bug that may be already fixed in later versions of KDE.

Chris

Re: MX-19.2 KDE Beta 1 feedback thread

Posted: Fri Jul 17, 2020 7:09 pm
by Jerry3904
This thread is now closed with the release of MX-KDE Beta 2