MX-19.2 KDE Beta 2 Feedback Thread
Re: MX-19.2 KDE Beta 2 Feedback Thread
Things are on a roll here!
Silly question, but suppose with KDEb1 updated, there's no need to try b2?
Unless maybe, to check installation process?
Silly question, but suppose with KDEb1 updated, there's no need to try b2?
Unless maybe, to check installation process?
Re: MX-19.2 KDE Beta 2 Feedback Thread
This is pretty amazing so far!!!
Couple of issues I noticed:
- The screen to decrypt the drive on boot is at a low resolution on a 1440p monitor after the NVidia drivers update
- Display settings don't show the right refresh rates on the 1440p (limited up to 60hz), but NVidia Settings does (165hz).
- The subtext for the menu is garbled after I installed the NVidia drivers (not sure if this happens before that) https://imgur.com/mEYhNjp
Couple of issues I noticed:
- The screen to decrypt the drive on boot is at a low resolution on a 1440p monitor after the NVidia drivers update
- Display settings don't show the right refresh rates on the 1440p (limited up to 60hz), but NVidia Settings does (165hz).
- The subtext for the menu is garbled after I installed the NVidia drivers (not sure if this happens before that) https://imgur.com/mEYhNjp
Code: Select all
System: Host: MX-KDE-Beta2 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/vmlinuz-5.6.0-2-amd64 root=UUID=35552f90-5d50-43b1-a762-c5606aeb5f5e ro quiet splash
Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-beta2_x64 patito feo July 5 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI) v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 1407 date: 04/01/2020
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: 182058
Speed: 2195 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2194 2: 2194 3: 2196 4: 2196
5: 2190 6: 2187 7: 2191 8: 2192 9: 2195 10: 2188 11: 2195 12: 2196 13: 2193 14: 2196 15: 2184 16: 2193
17: 2196 18: 2195 19: 2195 20: 2195 21: 2195 22: 2196 23: 2195 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 TU102 [GeForce RTX 2080 Ti Rev. A] driver: nvidia v: 440.100 bus ID: 08:00.0
chip ID: 10de:1e07
Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce RTX 2080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes
Audio: Device-1: NVIDIA TU102 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1
chip ID: 10de:10f7
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0a: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: ASUSTeK 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>
IF-ID-1: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 14.35 TiB used: 313.13 GiB (2.1%)
ID-1: /dev/nvme0n1 model: Sabrent size: 953.87 GiB block size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: ECFM22.4 scheme: GPT
ID-2: /dev/sda vendor: Seagate model: ST5000DM000-1FK178 size: 4.55 TiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s rotation: 5980 rpm serial: <filter> rev: CC47 temp: 37 C scheme: GPT
ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0B-00YS70 size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 90WD temp: 42 C scheme: GPT
ID-4: /dev/sdc vendor: Western Digital model: WD20EADS-11R6B1 size: 1.82 TiB block size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 0A80 temp: 43 C scheme: GPT
ID-5: /dev/sdd vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A02 temp: 41 C scheme: MBR
ID-6: /dev/sde 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: MBR
ID-7: /dev/sdf type: USB vendor: Seagate model: Backup+ Desk size: 3.64 TiB block size: physical: 4096 B
logical: 4096 B serial: <filter> rev: 050B scheme: MBR
ID-8: /dev/sdg type: USB vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B rotation: 7200 rpm serial: <filter> scheme: MBR
ID-9: /dev/sdh type: USB vendor: Western Digital model: WD My Passport 259F size: 931.48 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1004
Partition: ID-1: / raw size: 462.96 GiB size: 454.70 GiB (98.21%) used: 7.31 GiB (1.6%) fs: ext4 dev: /dev/dm-0
ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 100.4 MiB (20.6%) fs: ext4 dev: /dev/sdb2
ID-3: swap-1 size: 1.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/dm-1
Sensors: System Temperatures: cpu: 61.8 C mobo: N/A gpu: nvidia temp: 50 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 41%
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: 431 Uptime: 20m Memory: 29.95 GiB used: 3.12 GiB (10.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
MX 19.2 AHS
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
Re: MX-19.2 KDE Beta 2 Feedback Thread
I also can't install Steam from The MX Package Installer
I did not receive a message for the License Agreement.
Code: Select all
Hit:1 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://deb.debian.org/debian buster InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Recommended packages:
steam-devices:i386 libxss1:i386 xterm:i386 | x-terminal-emulator:i386
The following NEW packages will be installed:
steam:i386
Preconfiguring packages ...
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,447 kB of archives.
After this operation, 4,472 kB of additional disk space will be used.
(Reading database ... 211166 files and directories currently installed.)
Preparing to unpack .../steam_1.0.0.59-4_i386.deb ...
dpkg: error processing archive /var/cache/apt/archives/steam_1.0.0.59-4_i386.deb (--unpack):
new steam:i386 package pre-installation script subprocess returned error exit status 1
Installation terminated: Steam License Agreement was DECLINED.
Errors were encountered while processing:
/var/cache/apt/archives/steam_1.0.0.59-4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
libgl1-mesa-glx:i386 libgpg-error0:i386 libudev1:i386 libxinerama1:i386
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
MX 19.2 AHS
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
Re: MX-19.2 KDE Beta 2 Feedback Thread
If I have beta 1 installed is it update to beta2 if I've keep it upgraded?
Re: MX-19.2 KDE Beta 2 Feedback Thread
In the announcement.kc1di wrote: Sat Jul 18, 2020 11:00 am If I have beta 1 installed is it update to beta2 if I've keep it upgraded?
I see this question coming up again and again. Betas are meant for testing and reporting problems, not for installing a upgradable stable system so the best way to provide feedback is to download the latest Beta and test that, if you want to install and use it in "production" and not have to reinstall wait at least till a Release Candidate. That's unfortunate because it can potentially reduce the number of testers but that's how it works...The beta will receive updates over time through the repositories, but certain items, such as the live system and some user settings defaults, will not be obvious without some user intervention.
Re: MX-19.2 KDE Beta 2 Feedback Thread
I definitely don't like bubble sounds on my volume control. I think it's completely unnecessary.
MX 19.2 AHS
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
Re: MX-19.2 KDE Beta 2 Feedback Thread
Running live in Virtualbox. When I try alternative menus it changes the menu icon from MX to generic Plasma one. It stays that way when I switch back.
After switching menus, the list of applications in Favorites is changed to what looks like a combination of MX and Plasma entries.
Since I was live in VB, I ran QSI there.
After switching menus, the list of applications in Favorites is changed to what looks like a combination of MX and Plasma entries.
Since I was live in VB, I ran QSI there.
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-beta2_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
CPU:
Topology: Dual Core model: Intel Celeron 1007U bits: 64 type: MCP arch: Ivy Bridge
family: 6 model-id: 3A (58) stepping: 9 microcode: 19 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 5987
Speed: 1497 MHz min/max: N/A Core speeds (MHz): 1: 1497 2: 1497
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; 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: VMware SVGA II Adapter driver: vmwgfx v: 2.17.0.0 bus ID: 00:02.0
chip ID: 15ad:0405
Display: x11 server: X.Org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa
compositor: kwin_x11 resolution: 800x600~60Hz
OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 20.0.7 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: d020 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: 8.00 GiB used: 65.0 MiB (0.8%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 8.00 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0
scheme: MBR
Partition:
ID-1: / raw size: N/A size: 1.12 GiB used: 64.7 MiB (5.6%) fs: overlay
source: ERR-102
ID-2: swap-1 size: 1024.0 MiB used: 268 KiB (0.0%) fs: swap
swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2
Sensors:
Message: No sensors data was found. Is sensors configured?
Repos:
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: 166 Uptime: 3m Memory: 1.45 GiB used: 515.4 MiB (34.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
Green Comet
Space particles.
Space particles.
- chrispop99
- Global Moderator
- Posts: 3341
- Joined: Tue Jan 27, 2009 2:07 pm
Re: MX-19.2 KDE Beta 2 Feedback Thread
It's easy enough to turn it off. Right-click is your friend...WinExodus wrote: Sat Jul 18, 2020 11:40 am I definitely don't like bubble sounds on my volume control. I think it's completely unnecessary.
KDE has many more configurations than the other desktop environments.
Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Re: MX-19.2 KDE Beta 2 Feedback Thread
chrispop99 wrote: Sat Jul 18, 2020 11:45 am
It's easy enough to turn it off. Right-click is your friend...
KDE has many more configurations than the other desktop environments.
Chris
This is not obvious at all for someone new to KDE or even Linux in general. I'm trying to look at this from a UX perspective.
I believe this should be off by default, as every other OS I've used does not have volume control sounds. It definitely ruins immersion when listening to songs.
EDIT: And just to add to this, if I use my volume control on my keyboard, for example, and I quickly change the volume, it gets "frozen" on that bubble sound for a few seconds sometimes.
MX 19.2 AHS
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
AMD Ryzen 9 3900X, ASUS TUF GAMING X570-PLUS (WI-FI), NVIDIA GeForce RTX 2080 Ti Rev. A, 32GB Memory, Sabrent Rocket NVMe SSD (1TB), Samsung SSD 850 EVO (250GB)
Re: MX-19.2 KDE Beta 2 Feedback Thread
I think the sounds on the volume control are good thing. So it's a personal taste thing.
Thanks Adrian for the reply. I kind of thought that but I've seen it done both ways in other distros. So thought I would ask.
Thanks Adrian for the reply. I kind of thought that but I've seen it done both ways in other distros. So thought I would ask.