MX-19.2 KDE RC 1 Feedback Thread
Re: MX-19.2 KDE RC 1 Feedback Thread
Moderator
Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-19.2 KDE RC 1 Feedback Thread
RC1 working very well on my laptop
Code: Select all
System:
Host: kc1di-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=b2b23b6c-69e5-44b6-97b9-3572ee61ba05 ro quiet splash
Desktop: KDE Plasma 5.14.5 info: latte-dock wm: kwin_x11 dm: SDDM
Distro: MX-19.2_KDE-RC1_x64 patito feo August 9 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: LENOVO product: 20BV000AUS v: ThinkPad T450 serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20BV000AUS v: SDK0E50510 WIN serial: <filter>
UEFI [Legacy]: LENOVO v: JBET71WW (1.35 ) date: 09/14/2018
Battery:
ID-1: BAT0 charge: 17.4 Wh condition: 17.7/23.2 Wh (76%) volts: 12.4/11.1
model: SANYO 45N1773 type: Li-ion serial: <filter> status: Unknown
ID-2: BAT1 charge: 15.9 Wh condition: 17.1/23.2 Wh (74%) volts: 12.0/11.1
model: SANYO 45N1775 type: Li-ion serial: <filter> status: Discharging
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 i5-5300U bits: 64 type: MT MCP
arch: Broadwell family: 6 model-id: 3D (61) stepping: 4 microcode: 2F
L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 18355
Speed: 1063 MHz min/max: 500/2900 MHz Core speeds (MHz): 1: 1063 2: 1220 3: 1187
4: 1020
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
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 mitigation: Microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:1616
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
compositor: kwin_x11 resolution: 1600x900~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.0.7
direct render: Yes
Audio:
Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:160c
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0
Sound Server: ALSA v: k5.6.0-2-amd64
Network:
Device-1: Intel Ethernet I218-LM vendor: Lenovo driver: e1000e v: 3.2.6-k
port: 3080 bus ID: 00:19.0 chip ID: 8086:15a2
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0
chip ID: 8086:095b
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 267.26 GiB used: 13.68 GiB (5.1%)
ID-1: /dev/mmcblk0 vendor: SanDisk model: SL32G size: 28.79 GiB block size:
physical: 512 B logical: 512 B serial: <filter> scheme: MBR
ID-2: /dev/sda vendor: LITE-ON model: LCH-256V2S size: 238.47 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 902
scheme: MBR
Partition:
ID-1: / raw size: 37.25 GiB size: 36.41 GiB (97.75%) used: 7.98 GiB (21.9%)
fs: ext4 dev: /dev/sda1
ID-2: /home raw size: 198.43 GiB size: 194.31 GiB (97.93%) used: 5.70 GiB (2.9%)
fs: ext4 dev: /dev/sda6
ID-3: swap-1 size: 2.79 GiB used: 0 KiB (0.0%) fs: swap
swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda5
Sensors:
System Temperatures: cpu: 38.5 C mobo: 0.0 C
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://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/opera-stable.list
1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 210 Uptime: 3m Memory: 7.49 GiB used: 704.5 MiB (9.2%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX-19.2 KDE RC 1 Feedback Thread
It is running in a VM, so from the CD ISO directly.richb wrote: Tue Aug 11, 2020 5:53 pm I would assume a CD would be slow by virtue of the technology involved.
Re: MX-19.2 KDE RC 1 Feedback Thread
I could not find this link, so I just posted the link instead of embedding it.richb wrote: Tue Aug 11, 2020 6:17 pm Moderator
Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
Re: MX-19.2 KDE RC 1 Feedback Thread
Thank you.fladd wrote: Tue Aug 11, 2020 7:47 pmI could not find this link, so I just posted the link instead of embedding it.richb wrote: Tue Aug 11, 2020 6:17 pm Moderator
Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
In Imgur, click on your username then images. Click your image and the following appears: Sorry, the image got clipped on the right when I resized. to get the file size less than 300 KB which is the Forum limit. The large is at the bottom right. Click that first then the Linked BB Code.
You do not have the required permissions to view the files attached to this post.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: MX-19.2 KDE RC 1 Feedback Thread
Interesting, there shouldn't be that much of a impact, but I only assume there might be some.
Is this with an SSD or good 'ol spinning rust HHD? I could see if with HDD depending on the location I suppose, if the drive is slower and or showing some age... but we all know that doesn't affect a SSD.
I haven't ran a live ISO in a VM in awhile outside of installing shortly after.
I wonder if anyone can take a look and test it soon. I'm a bit tied up right now, but can later this evening I think.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
- dolphin_oracle
- Developer
- Posts: 22811
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE RC 1 Feedback Thread
I run it in a vm all the time. there are a couple of factors. ram that the VM has is more important for the KDE version in my experience, especially at startup. another factor is the graphics driver in use. the kde desktop makes much more use of graphics effects when windows move or pop open, etc... So it can be slower.
Its not particularly slower for me, except for boot up. On real hardware no problems at all.
Its not particularly slower for me, except for boot up. On real hardware no problems at all.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: MX-19.2 KDE RC 1 Feedback Thread
You’ve run strictly off the live ISO booted or installed? Think the user was stating specifically they weren’t installing.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
- dolphin_oracle
- Developer
- Posts: 22811
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE RC 1 Feedback Thread
live. great for testingSwampRabbit wrote: Tue Aug 11, 2020 9:00 pmYou’ve run strictly off the live ISO booted or installed? Think the user was stating specifically they weren’t installing.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
Re: MX-19.2 KDE RC 1 Feedback Thread
I'd still like to see the option to disable the 30-second logout/reboot/shutdown/switch users delay ("Confirm logout") added to MX Tweak so people don't have to hunt all over in their plasma settings to find it. I foresee a lot of questions about that delay in the forum after MX-KDE goes live.

There should probably also be a FAQ entry about the delay: the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none. At least I haven't been able so far to find a config file where that value can be changed. But then, I don't even know what MX-KDE is using for its session manager. It's not LightDM.
Edit: found it, it's SDDM. I still can't find any config options for it that contain that 30-second timeout value that could be edited by users.

There should probably also be a FAQ entry about the delay: the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none. At least I haven't been able so far to find a config file where that value can be changed. But then, I don't even know what MX-KDE is using for its session manager. It's not LightDM.
Edit: found it, it's SDDM. I still can't find any config options for it that contain that 30-second timeout value that could be edited by users.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.