MX Linux Forum

Jerry3904 wrote: Fri Jul 17, 2020 9:25 pm Running live on my Lenovo, clicking"Brightness tray" in MX Tools does nothing that I can see. Running mx-tweak-systray in the terminal: "command not found." Tried to install it--not available.

Sorry if this has already been reported earlier...

JayM wrote: Fri Jul 17, 2020 10:21 pm I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

byterhythm wrote: Sat Jul 18, 2020 3:58 am I'm planning on installing the KDE beta bare metal on my machine. I just wanted to know if I can upgrade it to the final version once it is released.

richb wrote: Fri Jul 17, 2020 10:53 pm

JayM wrote: Fri Jul 17, 2020 10:21 pm I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

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?

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.

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.

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

arjaybe wrote: Sat Jul 18, 2020 11:44 am 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.

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 

WinExodus wrote: Sat Jul 18, 2020 9:08 am - Display settings don't show the right refresh rates on the 1440p (limited up to 60hz), but NVidia Settings does (165hz).

WinExodus wrote: Sat Jul 18, 2020 9:46 am I also can't install Steam from The MX Package Installer

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.

I did not receive a message for the License Agreement.

kc1di wrote: Sat Jul 18, 2020 12:12 pm So it's a personal taste thing.

dolphin_oracle wrote: Sat Jul 18, 2020 12:18 pm Purge off the nvidia drivers and then install steam. Then reinstall the nvidia drivers

sudo ddm-mx -p nvidia

We are sorry, ksmserver-logout-greeter closed unexpectedly.

dolphin_oracle wrote: Sat Jul 18, 2020 12:35 pm Ok that's weird. Will look into it but for now it's probably easier to reinstall.

Oh the joys of beta testing.

kc1di wrote: Sat Jul 18, 2020 12:12 pm ...
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.

dolphin_oracle wrote: Sat Jul 18, 2020 12:18 pm Purge off the nvidia drivers and then install steam. Then reinstall the nvidia drivers

Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian-security buster/updates InRelease
Hit:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 zlib1g:i386
Suggested packages:
  lm-sensors:i386 nvidia-driver-libs-i386:i386 nvidia-vulkan-icd:i386
Recommended packages:
  libgpg-error-l10n:i386 mesa-vulkan-drivers:i386 | vulkan-icd:i386
  steam-devices:i386 libxss1:i386 mesa-vulkan-drivers:i386 xterm:i386
  | x-terminal-emulator:i386
The following NEW packages will be installed:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 steam:i386 zlib1g:i386
0 upgraded, 45 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.9 MB of archives.
After this operation, 377 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main i386 zlib1g i386 1:1.2.11.dfsg-1 [95.7 kB]
Get:2 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm2 i386 2.4.101-2~mx19+1 [44.5 kB]
Get:3 http://deb.debian.org/debian buster/main i386 libpciaccess0 i386 0.14-1 [55.7 kB]
Get:4 http://deb.debian.org/debian buster/main i386 libelf1 i386 0.176-1.1 [166 kB]
Get:5 http://deb.debian.org/debian buster/main i386 libexpat1 i386 2.2.6-2+deb10u1 [104 kB]
Get:6 http://deb.debian.org/debian buster/main i386 libatomic1 i386 8.3.0-6 [9,472 B]
Get:7 http://deb.debian.org/debian buster/main i386 libbsd0 i386 0.9.1-2 [104 kB]
Get:8 http://deb.debian.org/debian buster/main i386 libtinfo6 i386 6.1+20181013-2+deb10u2 [326 kB]
Get:9 http://deb.debian.org/debian buster/main i386 libedit2 i386 3.1-20181209-1 [98.2 kB]
Get:10 http://deb.debian.org/debian buster/main i386 libffi6 i386 3.2.1-9 [20.0 kB]
Get:11 http://deb.debian.org/debian buster/main i386 libstdc++6 i386 8.3.0-6 [424 kB]
Get:12 http://deb.debian.org/debian buster/main i386 libsensors5 i386 1:3.5.0-3 [53.5 kB]
Get:13 http://deb.debian.org/debian buster/main i386 libzstd1 i386 1.3.8+dfsg-3 [236 kB]
Get:14 http://deb.debian.org/debian buster/main i386 libxau6 i386 1:1.0.8-1+b2 [20.3 kB]
Get:15 http://deb.debian.org/debian buster/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB]
Get:16 http://deb.debian.org/debian buster/main i386 libxext6 i386 2:1.3.3-1+b2 [55.2 kB]
Get:17 http://deb.debian.org/debian buster/main i386 libxshmfence1 i386 1.3-1 [8,976 B]
Get:18 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-amdgpu1 i386 2.4.101-2~mx19+1 [31.4 kB]
Get:19 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-intel1 i386 2.4.101-2~mx19+1 [73.7 kB]
Get:20 http://deb.debian.org/debian buster/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21.7 kB]
Get:21 http://deb.debian.org/debian buster/main i386 libgpg-error0 i386 1.35-1 [75.7 kB]
Get:22 http://deb.debian.org/debian buster/main i386 libxinerama1 i386 2:1.1.4-2 [17.9 kB]
Get:23 http://deb.debian.org/debian buster/non-free i386 steam i386 1.0.0.59-4 [1,447 kB]
Get:24 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-nouveau2 i386 2.4.101-2~mx19+1 [28.6 kB]
Get:25 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-radeon1 i386 2.4.101-2~mx19+1 [33.1 kB]
Get:26 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglapi-mesa i386 20.0.7-0.1~mx19ahs+1 [70.5 kB]
Get:27 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libllvm10 i386 1:10.0.0-4~mx19+1 [15.5 MB]
Get:28 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libvulkan1 i386 1.2.135.0-2~mx19ahs+1 [109 kB]
Get:29 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1-mesa-dri i386 20.0.7-0.1~mx19ahs+1 [11.4 MB]
Get:30 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglvnd0 i386 1.3.1-1mx19+1 [44.1 kB]
Get:31 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb1 i386 1.14-2~mx19+1 [144 kB]
Get:32 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libx11-6 i386 2:1.6.9-2~mx19+1 [778 kB]
Get:33 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libx11-xcb1 i386 2:1.6.9-2~mx19+1 [190 kB]
Get:34 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-dri2-0 i386 1.14-2~mx19+1 [103 kB]
Get:35 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-dri3-0 i386 1.14-2~mx19+1 [103 kB]
Get:36 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-glx0 i386 1.14-2~mx19+1 [120 kB]
Get:37 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-present0 i386 1.14-2~mx19+1 [101 kB]
Get:38 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-sync1 i386 1.14-2~mx19+1 [105 kB]
Get:39 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxfixes3 i386 1:5.0.3-2~mx19ahs+1 [22.7 kB]
Get:40 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxdamage1 i386 1:1.1.5-2~mx19ahs+1 [16.0 kB]
Get:41 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglx-mesa0 i386 20.0.7-0.1~mx19ahs+1 [192 kB]
Get:42 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglx0 i386 1.3.1-1mx19+1 [38.6 kB]
Get:43 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1 i386 1.3.1-1mx19+1 [83.6 kB]
Get:44 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1-mesa-glx i386 20.0.7-0.1~mx19ahs+1 [50.3 kB]
Get:45 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/main i386 libudev1 i386 1:241-7~deb10u4+mx19 [153 kB]
Preconfiguring packages ...
Fetched 32.9 MB in 2s (19.9 MB/s)
Selecting previously unselected package libdrm2:i386.
(Reading database ... 206469 files and directories currently installed.)
Preparing to unpack .../00-libdrm2_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm2:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-amdgpu1:i386.
Preparing to unpack .../01-libdrm-amdgpu1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-amdgpu1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package zlib1g:i386.
Preparing to unpack .../02-zlib1g_1%3a1.2.11.dfsg-1_i386.deb ...
Unpacking zlib1g:i386 (1:1.2.11.dfsg-1) ...
Selecting previously unselected package libpciaccess0:i386.
Preparing to unpack .../03-libpciaccess0_0.14-1_i386.deb ...
Unpacking libpciaccess0:i386 (0.14-1) ...
Selecting previously unselected package libdrm-intel1:i386.
Preparing to unpack .../04-libdrm-intel1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-intel1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-nouveau2:i386.
Preparing to unpack .../05-libdrm-nouveau2_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-nouveau2:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-radeon1:i386.
Preparing to unpack .../06-libdrm-radeon1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-radeon1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libelf1:i386.
Preparing to unpack .../07-libelf1_0.176-1.1_i386.deb ...
Unpacking libelf1:i386 (0.176-1.1) ...
Selecting previously unselected package libexpat1:i386.
Preparing to unpack .../08-libexpat1_2.2.6-2+deb10u1_i386.deb ...
Unpacking libexpat1:i386 (2.2.6-2+deb10u1) ...
Selecting previously unselected package libglapi-mesa:i386.
Preparing to unpack .../09-libglapi-mesa_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libglapi-mesa:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libatomic1:i386.
Preparing to unpack .../10-libatomic1_8.3.0-6_i386.deb ...
Unpacking libatomic1:i386 (8.3.0-6) ...
Selecting previously unselected package libbsd0:i386.
Preparing to unpack .../11-libbsd0_0.9.1-2_i386.deb ...
Unpacking libbsd0:i386 (0.9.1-2) ...
Selecting previously unselected package libtinfo6:i386.
Preparing to unpack .../12-libtinfo6_6.1+20181013-2+deb10u2_i386.deb ...
Unpacking libtinfo6:i386 (6.1+20181013-2+deb10u2) ...
Selecting previously unselected package libedit2:i386.
Preparing to unpack .../13-libedit2_3.1-20181209-1_i386.deb ...
Unpacking libedit2:i386 (3.1-20181209-1) ...
Selecting previously unselected package libffi6:i386.
Preparing to unpack .../14-libffi6_3.2.1-9_i386.deb ...
Unpacking libffi6:i386 (3.2.1-9) ...
Selecting previously unselected package libstdc++6:i386.
Preparing to unpack .../15-libstdc++6_8.3.0-6_i386.deb ...
Unpacking libstdc++6:i386 (8.3.0-6) ...
Selecting previously unselected package libllvm10:i386.
Preparing to unpack .../16-libllvm10_1%3a10.0.0-4~mx19+1_i386.deb ...
Unpacking libllvm10:i386 (1:10.0.0-4~mx19+1) ...
Selecting previously unselected package libsensors5:i386.
Preparing to unpack .../17-libsensors5_1%3a3.5.0-3_i386.deb ...
Unpacking libsensors5:i386 (1:3.5.0-3) ...
Selecting previously unselected package libvulkan1:i386.
Preparing to unpack .../18-libvulkan1_1.2.135.0-2~mx19ahs+1_i386.deb ...
Unpacking libvulkan1:i386 (1.2.135.0-2~mx19ahs+1) ...
Selecting previously unselected package libzstd1:i386.
Preparing to unpack .../19-libzstd1_1.3.8+dfsg-3_i386.deb ...
Unpacking libzstd1:i386 (1.3.8+dfsg-3) ...
Selecting previously unselected package libgl1-mesa-dri:i386.
Preparing to unpack .../20-libgl1-mesa-dri_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libglvnd0:i386.
Preparing to unpack .../21-libglvnd0_1.3.1-1mx19+1_i386.deb ...
Unpacking libglvnd0:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libxau6:i386.
Preparing to unpack .../22-libxau6_1%3a1.0.8-1+b2_i386.deb ...
Unpacking libxau6:i386 (1:1.0.8-1+b2) ...
Selecting previously unselected package libxdmcp6:i386.
Preparing to unpack .../23-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp6:i386 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:i386.
Preparing to unpack .../24-libxcb1_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb1:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libx11-6:i386.
Preparing to unpack .../25-libx11-6_2%3a1.6.9-2~mx19+1_i386.deb ...
Unpacking libx11-6:i386 (2:1.6.9-2~mx19+1) ...
Selecting previously unselected package libx11-xcb1:i386.
Preparing to unpack .../26-libx11-xcb1_2%3a1.6.9-2~mx19+1_i386.deb ...
Unpacking libx11-xcb1:i386 (2:1.6.9-2~mx19+1) ...
Selecting previously unselected package libxcb-dri2-0:i386.
Preparing to unpack .../27-libxcb-dri2-0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-dri2-0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-dri3-0:i386.
Preparing to unpack .../28-libxcb-dri3-0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-dri3-0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-glx0:i386.
Preparing to unpack .../29-libxcb-glx0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-glx0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-present0:i386.
Preparing to unpack .../30-libxcb-present0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-present0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-sync1:i386.
Preparing to unpack .../31-libxcb-sync1_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-sync1:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxfixes3:i386.
Preparing to unpack .../32-libxfixes3_1%3a5.0.3-2~mx19ahs+1_i386.deb ...
Unpacking libxfixes3:i386 (1:5.0.3-2~mx19ahs+1) ...
Selecting previously unselected package libxdamage1:i386.
Preparing to unpack .../33-libxdamage1_1%3a1.1.5-2~mx19ahs+1_i386.deb ...
Unpacking libxdamage1:i386 (1:1.1.5-2~mx19ahs+1) ...
Selecting previously unselected package libxext6:i386.
Preparing to unpack .../34-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Unpacking libxext6:i386 (2:1.3.3-1+b2) ...
Selecting previously unselected package libxshmfence1:i386.
Preparing to unpack .../35-libxshmfence1_1.3-1_i386.deb ...
Unpacking libxshmfence1:i386 (1.3-1) ...
Selecting previously unselected package libxxf86vm1:i386.
Preparing to unpack .../36-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ...
Unpacking libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Selecting previously unselected package libglx-mesa0:i386.
Preparing to unpack .../37-libglx-mesa0_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libglx-mesa0:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libglx0:i386.
Preparing to unpack .../38-libglx0_1.3.1-1mx19+1_i386.deb ...
Unpacking libglx0:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libgl1:i386.
Preparing to unpack .../39-libgl1_1.3.1-1mx19+1_i386.deb ...
Unpacking libgl1:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libgl1-mesa-glx:i386.
Preparing to unpack .../40-libgl1-mesa-glx_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libgl1-mesa-glx:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libgpg-error0:i386.
Preparing to unpack .../41-libgpg-error0_1.35-1_i386.deb ...
Unpacking libgpg-error0:i386 (1.35-1) ...
Selecting previously unselected package libudev1:i386.
Preparing to unpack .../42-libudev1_1%3a241-7~deb10u4+mx19_i386.deb ...
Unpacking libudev1:i386 (1:241-7~deb10u4+mx19) ...
Selecting previously unselected package libxinerama1:i386.
Preparing to unpack .../43-libxinerama1_2%3a1.1.4-2_i386.deb ...
Unpacking libxinerama1:i386 (2:1.1.4-2) ...
Selecting previously unselected package steam:i386.
Preparing to unpack .../44-steam_1.0.0.59-4_i386.deb ...
dpkg: error processing archive /tmp/apt-dpkg-install-w2mUJD/44-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:
 /tmp/apt-dpkg-install-w2mUJD/44-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:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 zlib1g:i386
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
44 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.Setting up libexpat1:i386 (2.2.6-2+deb10u1) ...Setting up libzstd1:i386 (1.3.8+dfsg-3) ...Setting up libx11-xcb1:i386 (2:1.6.9-2~mx19+1) ...Setting up libxau6:i386 (1:1.0.8-1+b2) ...Setting up libgpg-error0:i386 (1.35-1) ...Setting up libglvnd0:i386 (1.3.1-1mx19+1) ...Setting up zlib1g:i386 (1:1.2.11.dfsg-1) ...Setting up libffi6:i386 (3.2.1-9) ...Setting up libatomic1:i386 (8.3.0-6) ...Setting up libsensors5:i386 (1:3.5.0-3) ...Setting up libglapi-mesa:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libvulkan1:i386 (1.2.135.0-2~mx19ahs+1) ...Setting up libudev1:i386 (1:241-7~deb10u4+mx19) ...Setting up libdrm2:i386 (2.4.101-2~mx19+1) ...Setting up libxshmfence1:i386 (1.3-1) ...Setting up libbsd0:i386 (0.9.1-2) ...Setting up libelf1:i386 (0.176-1.1) ...Setting up libstdc++6:i386 (8.3.0-6) ...Setting up libtinfo6:i386 (6.1+20181013-2+deb10u2) ...Setting up libdrm-amdgpu1:i386 (2.4.101-2~mx19+1) ...Setting up libpciaccess0:i386 (0.14-1) ...Setting up libxdmcp6:i386 (1:1.1.2-3) ...Setting up libdrm-nouveau2:i386 (2.4.101-2~mx19+1) ...Setting up libxcb1:i386 (1.14-2~mx19+1) ...Setting up libdrm-radeon1:i386 (2.4.101-2~mx19+1) ...Setting up libxcb-glx0:i386 (1.14-2~mx19+1) ...Setting up libedit2:i386 (3.1-20181209-1) ...Setting up libdrm-intel1:i386 (2.4.101-2~mx19+1) ...Setting up libllvm10:i386 (1:10.0.0-4~mx19+1) ...Setting up libxcb-present0:i386 (1.14-2~mx19+1) ...Setting up libxcb-sync1:i386 (1.14-2~mx19+1) ...Setting up libxcb-dri2-0:i386 (1.14-2~mx19+1) ...Setting up libx11-6:i386 (2:1.6.9-2~mx19+1) ...Setting up libxcb-dri3-0:i386 (1.14-2~mx19+1) ...Setting up libgl1-mesa-dri:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libxext6:i386 (2:1.3.3-1+b2) ...Setting up libxxf86vm1:i386 (1:1.1.4-1+b2) ...Setting up libxfixes3:i386 (1:5.0.3-2~mx19ahs+1) ...Setting up libxinerama1:i386 (2:1.1.4-2) ...Setting up libxdamage1:i386 (1:1.1.5-2~mx19ahs+1) ...Setting up libglx-mesa0:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libglx0:i386 (1.3.1-1mx19+1) ...Setting up libgl1:i386 (1.3.1-1mx19+1) ...Setting up libgl1-mesa-glx:i386 (20.0.7-0.1~mx19ahs+1) ...Processing triggers for man-db (2.8.5-2) ...Processing triggers for libc-bin (2.28-10) ...

WinExodus wrote: Sat Jul 18, 2020 11:53 am

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.

chrispop99 wrote: Sat Jul 18, 2020 1:08 pm

WinExodus wrote: Sat Jul 18, 2020 11:53 am

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.

If you are new to KDE, you will need to get used to the fact that you won't like all the default options. Others however will like them.

FWIW, I like the audible feedback as it gives a guide to how loud the actual volume might be.

Chris

WinExodus wrote: Sat Jul 18, 2020 1:18 pm Just saying how it is from a UX perspective. I'll go ahead and figure things out for myself, and post back here on how to do it for anyone else that's interested.

asqwerth wrote: Sat Jul 18, 2020 1:16 pm I thought right click has long been a thing, even in Windows.

WinExodus wrote: Sat Jul 18, 2020 1:22 pm

WinExodus wrote: Sat Jul 18, 2020 1:18 pm Just saying how it is from a UX perspective. I'll go ahead and figure things out for myself, and post back here on how to do it for anyone else that's interested.

I figured it out. You have to right click on the volume icon in the panel, go to general, and uncheck "Volume feedback". I was having a brain fart and right-clicking on the desktop, and got lost.

I guess I just don't remember this being a part of Beta 1.

asqwerth wrote: Sat Jul 18, 2020 1:58 pm I was just in my Beta 1 install (to use Live USB Maker to make the Beta 2 live USB). The volume slider does issue the bubble sound when used.

richb wrote: Fri Jul 17, 2020 10:53 pm

JayM wrote: Fri Jul 17, 2020 10:21 pm I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

WinExodus wrote: Sat Jul 18, 2020 1:02 pm

dolphin_oracle wrote: Sat Jul 18, 2020 12:18 pm Purge off the nvidia drivers and then install steam. Then reinstall the nvidia drivers

Alright, so I just did a fresh install of Beta 2. I did not install the NVIDIA drivers, and when I went to install steam, I did get the agreement window this time around, but also got an error through the MX Package Installer:

Code: Select all

Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian-security buster/updates InRelease
Hit:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 zlib1g:i386
Suggested packages:
  lm-sensors:i386 nvidia-driver-libs-i386:i386 nvidia-vulkan-icd:i386
Recommended packages:
  libgpg-error-l10n:i386 mesa-vulkan-drivers:i386 | vulkan-icd:i386
  steam-devices:i386 libxss1:i386 mesa-vulkan-drivers:i386 xterm:i386
  | x-terminal-emulator:i386
The following NEW packages will be installed:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 steam:i386 zlib1g:i386
0 upgraded, 45 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.9 MB of archives.
After this operation, 377 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main i386 zlib1g i386 1:1.2.11.dfsg-1 [95.7 kB]
Get:2 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm2 i386 2.4.101-2~mx19+1 [44.5 kB]
Get:3 http://deb.debian.org/debian buster/main i386 libpciaccess0 i386 0.14-1 [55.7 kB]
Get:4 http://deb.debian.org/debian buster/main i386 libelf1 i386 0.176-1.1 [166 kB]
Get:5 http://deb.debian.org/debian buster/main i386 libexpat1 i386 2.2.6-2+deb10u1 [104 kB]
Get:6 http://deb.debian.org/debian buster/main i386 libatomic1 i386 8.3.0-6 [9,472 B]
Get:7 http://deb.debian.org/debian buster/main i386 libbsd0 i386 0.9.1-2 [104 kB]
Get:8 http://deb.debian.org/debian buster/main i386 libtinfo6 i386 6.1+20181013-2+deb10u2 [326 kB]
Get:9 http://deb.debian.org/debian buster/main i386 libedit2 i386 3.1-20181209-1 [98.2 kB]
Get:10 http://deb.debian.org/debian buster/main i386 libffi6 i386 3.2.1-9 [20.0 kB]
Get:11 http://deb.debian.org/debian buster/main i386 libstdc++6 i386 8.3.0-6 [424 kB]
Get:12 http://deb.debian.org/debian buster/main i386 libsensors5 i386 1:3.5.0-3 [53.5 kB]
Get:13 http://deb.debian.org/debian buster/main i386 libzstd1 i386 1.3.8+dfsg-3 [236 kB]
Get:14 http://deb.debian.org/debian buster/main i386 libxau6 i386 1:1.0.8-1+b2 [20.3 kB]
Get:15 http://deb.debian.org/debian buster/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB]
Get:16 http://deb.debian.org/debian buster/main i386 libxext6 i386 2:1.3.3-1+b2 [55.2 kB]
Get:17 http://deb.debian.org/debian buster/main i386 libxshmfence1 i386 1.3-1 [8,976 B]
Get:18 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-amdgpu1 i386 2.4.101-2~mx19+1 [31.4 kB]
Get:19 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-intel1 i386 2.4.101-2~mx19+1 [73.7 kB]
Get:20 http://deb.debian.org/debian buster/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21.7 kB]
Get:21 http://deb.debian.org/debian buster/main i386 libgpg-error0 i386 1.35-1 [75.7 kB]
Get:22 http://deb.debian.org/debian buster/main i386 libxinerama1 i386 2:1.1.4-2 [17.9 kB]
Get:23 http://deb.debian.org/debian buster/non-free i386 steam i386 1.0.0.59-4 [1,447 kB]
Get:24 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-nouveau2 i386 2.4.101-2~mx19+1 [28.6 kB]
Get:25 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libdrm-radeon1 i386 2.4.101-2~mx19+1 [33.1 kB]
Get:26 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglapi-mesa i386 20.0.7-0.1~mx19ahs+1 [70.5 kB]
Get:27 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libllvm10 i386 1:10.0.0-4~mx19+1 [15.5 MB]
Get:28 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libvulkan1 i386 1.2.135.0-2~mx19ahs+1 [109 kB]
Get:29 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1-mesa-dri i386 20.0.7-0.1~mx19ahs+1 [11.4 MB]
Get:30 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglvnd0 i386 1.3.1-1mx19+1 [44.1 kB]
Get:31 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb1 i386 1.14-2~mx19+1 [144 kB]
Get:32 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libx11-6 i386 2:1.6.9-2~mx19+1 [778 kB]
Get:33 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libx11-xcb1 i386 2:1.6.9-2~mx19+1 [190 kB]
Get:34 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-dri2-0 i386 1.14-2~mx19+1 [103 kB]
Get:35 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-dri3-0 i386 1.14-2~mx19+1 [103 kB]
Get:36 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-glx0 i386 1.14-2~mx19+1 [120 kB]
Get:37 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-present0 i386 1.14-2~mx19+1 [101 kB]
Get:38 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxcb-sync1 i386 1.14-2~mx19+1 [105 kB]
Get:39 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxfixes3 i386 1:5.0.3-2~mx19ahs+1 [22.7 kB]
Get:40 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libxdamage1 i386 1:1.1.5-2~mx19ahs+1 [16.0 kB]
Get:41 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglx-mesa0 i386 20.0.7-0.1~mx19ahs+1 [192 kB]
Get:42 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libglx0 i386 1.3.1-1mx19+1 [38.6 kB]
Get:43 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1 i386 1.3.1-1mx19+1 [83.6 kB]
Get:44 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/ahs i386 libgl1-mesa-glx i386 20.0.7-0.1~mx19ahs+1 [50.3 kB]
Get:45 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster/main i386 libudev1 i386 1:241-7~deb10u4+mx19 [153 kB]
Preconfiguring packages ...
Fetched 32.9 MB in 2s (19.9 MB/s)
Selecting previously unselected package libdrm2:i386.
(Reading database ... 206469 files and directories currently installed.)
Preparing to unpack .../00-libdrm2_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm2:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-amdgpu1:i386.
Preparing to unpack .../01-libdrm-amdgpu1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-amdgpu1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package zlib1g:i386.
Preparing to unpack .../02-zlib1g_1%3a1.2.11.dfsg-1_i386.deb ...
Unpacking zlib1g:i386 (1:1.2.11.dfsg-1) ...
Selecting previously unselected package libpciaccess0:i386.
Preparing to unpack .../03-libpciaccess0_0.14-1_i386.deb ...
Unpacking libpciaccess0:i386 (0.14-1) ...
Selecting previously unselected package libdrm-intel1:i386.
Preparing to unpack .../04-libdrm-intel1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-intel1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-nouveau2:i386.
Preparing to unpack .../05-libdrm-nouveau2_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-nouveau2:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libdrm-radeon1:i386.
Preparing to unpack .../06-libdrm-radeon1_2.4.101-2~mx19+1_i386.deb ...
Unpacking libdrm-radeon1:i386 (2.4.101-2~mx19+1) ...
Selecting previously unselected package libelf1:i386.
Preparing to unpack .../07-libelf1_0.176-1.1_i386.deb ...
Unpacking libelf1:i386 (0.176-1.1) ...
Selecting previously unselected package libexpat1:i386.
Preparing to unpack .../08-libexpat1_2.2.6-2+deb10u1_i386.deb ...
Unpacking libexpat1:i386 (2.2.6-2+deb10u1) ...
Selecting previously unselected package libglapi-mesa:i386.
Preparing to unpack .../09-libglapi-mesa_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libglapi-mesa:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libatomic1:i386.
Preparing to unpack .../10-libatomic1_8.3.0-6_i386.deb ...
Unpacking libatomic1:i386 (8.3.0-6) ...
Selecting previously unselected package libbsd0:i386.
Preparing to unpack .../11-libbsd0_0.9.1-2_i386.deb ...
Unpacking libbsd0:i386 (0.9.1-2) ...
Selecting previously unselected package libtinfo6:i386.
Preparing to unpack .../12-libtinfo6_6.1+20181013-2+deb10u2_i386.deb ...
Unpacking libtinfo6:i386 (6.1+20181013-2+deb10u2) ...
Selecting previously unselected package libedit2:i386.
Preparing to unpack .../13-libedit2_3.1-20181209-1_i386.deb ...
Unpacking libedit2:i386 (3.1-20181209-1) ...
Selecting previously unselected package libffi6:i386.
Preparing to unpack .../14-libffi6_3.2.1-9_i386.deb ...
Unpacking libffi6:i386 (3.2.1-9) ...
Selecting previously unselected package libstdc++6:i386.
Preparing to unpack .../15-libstdc++6_8.3.0-6_i386.deb ...
Unpacking libstdc++6:i386 (8.3.0-6) ...
Selecting previously unselected package libllvm10:i386.
Preparing to unpack .../16-libllvm10_1%3a10.0.0-4~mx19+1_i386.deb ...
Unpacking libllvm10:i386 (1:10.0.0-4~mx19+1) ...
Selecting previously unselected package libsensors5:i386.
Preparing to unpack .../17-libsensors5_1%3a3.5.0-3_i386.deb ...
Unpacking libsensors5:i386 (1:3.5.0-3) ...
Selecting previously unselected package libvulkan1:i386.
Preparing to unpack .../18-libvulkan1_1.2.135.0-2~mx19ahs+1_i386.deb ...
Unpacking libvulkan1:i386 (1.2.135.0-2~mx19ahs+1) ...
Selecting previously unselected package libzstd1:i386.
Preparing to unpack .../19-libzstd1_1.3.8+dfsg-3_i386.deb ...
Unpacking libzstd1:i386 (1.3.8+dfsg-3) ...
Selecting previously unselected package libgl1-mesa-dri:i386.
Preparing to unpack .../20-libgl1-mesa-dri_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libglvnd0:i386.
Preparing to unpack .../21-libglvnd0_1.3.1-1mx19+1_i386.deb ...
Unpacking libglvnd0:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libxau6:i386.
Preparing to unpack .../22-libxau6_1%3a1.0.8-1+b2_i386.deb ...
Unpacking libxau6:i386 (1:1.0.8-1+b2) ...
Selecting previously unselected package libxdmcp6:i386.
Preparing to unpack .../23-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp6:i386 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:i386.
Preparing to unpack .../24-libxcb1_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb1:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libx11-6:i386.
Preparing to unpack .../25-libx11-6_2%3a1.6.9-2~mx19+1_i386.deb ...
Unpacking libx11-6:i386 (2:1.6.9-2~mx19+1) ...
Selecting previously unselected package libx11-xcb1:i386.
Preparing to unpack .../26-libx11-xcb1_2%3a1.6.9-2~mx19+1_i386.deb ...
Unpacking libx11-xcb1:i386 (2:1.6.9-2~mx19+1) ...
Selecting previously unselected package libxcb-dri2-0:i386.
Preparing to unpack .../27-libxcb-dri2-0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-dri2-0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-dri3-0:i386.
Preparing to unpack .../28-libxcb-dri3-0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-dri3-0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-glx0:i386.
Preparing to unpack .../29-libxcb-glx0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-glx0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-present0:i386.
Preparing to unpack .../30-libxcb-present0_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-present0:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxcb-sync1:i386.
Preparing to unpack .../31-libxcb-sync1_1.14-2~mx19+1_i386.deb ...
Unpacking libxcb-sync1:i386 (1.14-2~mx19+1) ...
Selecting previously unselected package libxfixes3:i386.
Preparing to unpack .../32-libxfixes3_1%3a5.0.3-2~mx19ahs+1_i386.deb ...
Unpacking libxfixes3:i386 (1:5.0.3-2~mx19ahs+1) ...
Selecting previously unselected package libxdamage1:i386.
Preparing to unpack .../33-libxdamage1_1%3a1.1.5-2~mx19ahs+1_i386.deb ...
Unpacking libxdamage1:i386 (1:1.1.5-2~mx19ahs+1) ...
Selecting previously unselected package libxext6:i386.
Preparing to unpack .../34-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Unpacking libxext6:i386 (2:1.3.3-1+b2) ...
Selecting previously unselected package libxshmfence1:i386.
Preparing to unpack .../35-libxshmfence1_1.3-1_i386.deb ...
Unpacking libxshmfence1:i386 (1.3-1) ...
Selecting previously unselected package libxxf86vm1:i386.
Preparing to unpack .../36-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ...
Unpacking libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Selecting previously unselected package libglx-mesa0:i386.
Preparing to unpack .../37-libglx-mesa0_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libglx-mesa0:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libglx0:i386.
Preparing to unpack .../38-libglx0_1.3.1-1mx19+1_i386.deb ...
Unpacking libglx0:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libgl1:i386.
Preparing to unpack .../39-libgl1_1.3.1-1mx19+1_i386.deb ...
Unpacking libgl1:i386 (1.3.1-1mx19+1) ...
Selecting previously unselected package libgl1-mesa-glx:i386.
Preparing to unpack .../40-libgl1-mesa-glx_20.0.7-0.1~mx19ahs+1_i386.deb ...
Unpacking libgl1-mesa-glx:i386 (20.0.7-0.1~mx19ahs+1) ...
Selecting previously unselected package libgpg-error0:i386.
Preparing to unpack .../41-libgpg-error0_1.35-1_i386.deb ...
Unpacking libgpg-error0:i386 (1.35-1) ...
Selecting previously unselected package libudev1:i386.
Preparing to unpack .../42-libudev1_1%3a241-7~deb10u4+mx19_i386.deb ...
Unpacking libudev1:i386 (1:241-7~deb10u4+mx19) ...
Selecting previously unselected package libxinerama1:i386.
Preparing to unpack .../43-libxinerama1_2%3a1.1.4-2_i386.deb ...
Unpacking libxinerama1:i386 (2:1.1.4-2) ...
Selecting previously unselected package steam:i386.
Preparing to unpack .../44-steam_1.0.0.59-4_i386.deb ...
dpkg: error processing archive /tmp/apt-dpkg-install-w2mUJD/44-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:
 /tmp/apt-dpkg-install-w2mUJD/44-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:
  libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libgpg-error0:i386 libllvm10:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libudev1:i386
  libvulkan1:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxinerama1:i386 libxshmfence1:i386 libxxf86vm1:i386
  libzstd1:i386 zlib1g:i386
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
44 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.Setting up libexpat1:i386 (2.2.6-2+deb10u1) ...Setting up libzstd1:i386 (1.3.8+dfsg-3) ...Setting up libx11-xcb1:i386 (2:1.6.9-2~mx19+1) ...Setting up libxau6:i386 (1:1.0.8-1+b2) ...Setting up libgpg-error0:i386 (1.35-1) ...Setting up libglvnd0:i386 (1.3.1-1mx19+1) ...Setting up zlib1g:i386 (1:1.2.11.dfsg-1) ...Setting up libffi6:i386 (3.2.1-9) ...Setting up libatomic1:i386 (8.3.0-6) ...Setting up libsensors5:i386 (1:3.5.0-3) ...Setting up libglapi-mesa:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libvulkan1:i386 (1.2.135.0-2~mx19ahs+1) ...Setting up libudev1:i386 (1:241-7~deb10u4+mx19) ...Setting up libdrm2:i386 (2.4.101-2~mx19+1) ...Setting up libxshmfence1:i386 (1.3-1) ...Setting up libbsd0:i386 (0.9.1-2) ...Setting up libelf1:i386 (0.176-1.1) ...Setting up libstdc++6:i386 (8.3.0-6) ...Setting up libtinfo6:i386 (6.1+20181013-2+deb10u2) ...Setting up libdrm-amdgpu1:i386 (2.4.101-2~mx19+1) ...Setting up libpciaccess0:i386 (0.14-1) ...Setting up libxdmcp6:i386 (1:1.1.2-3) ...Setting up libdrm-nouveau2:i386 (2.4.101-2~mx19+1) ...Setting up libxcb1:i386 (1.14-2~mx19+1) ...Setting up libdrm-radeon1:i386 (2.4.101-2~mx19+1) ...Setting up libxcb-glx0:i386 (1.14-2~mx19+1) ...Setting up libedit2:i386 (3.1-20181209-1) ...Setting up libdrm-intel1:i386 (2.4.101-2~mx19+1) ...Setting up libllvm10:i386 (1:10.0.0-4~mx19+1) ...Setting up libxcb-present0:i386 (1.14-2~mx19+1) ...Setting up libxcb-sync1:i386 (1.14-2~mx19+1) ...Setting up libxcb-dri2-0:i386 (1.14-2~mx19+1) ...Setting up libx11-6:i386 (2:1.6.9-2~mx19+1) ...Setting up libxcb-dri3-0:i386 (1.14-2~mx19+1) ...Setting up libgl1-mesa-dri:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libxext6:i386 (2:1.3.3-1+b2) ...Setting up libxxf86vm1:i386 (1:1.1.4-1+b2) ...Setting up libxfixes3:i386 (1:5.0.3-2~mx19ahs+1) ...Setting up libxinerama1:i386 (2:1.1.4-2) ...Setting up libxdamage1:i386 (1:1.1.5-2~mx19ahs+1) ...Setting up libglx-mesa0:i386 (20.0.7-0.1~mx19ahs+1) ...Setting up libglx0:i386 (1.3.1-1mx19+1) ...Setting up libgl1:i386 (1.3.1-1mx19+1) ...Setting up libgl1-mesa-glx:i386 (20.0.7-0.1~mx19ahs+1) ...Processing triggers for man-db (2.8.5-2) ...Processing triggers for libc-bin (2.28-10) ...

Thanks again. You're all doing a great job.

dolphin_oracle wrote: Sat Jul 18, 2020 3:22 pm Dumb question from me...did you say yes to the agreement. For whatever reason the default is no.

dolphin_oracle wrote: Fri Jul 17, 2020 9:41 pm

Jerry3904 wrote: Fri Jul 17, 2020 9:25 pm Running live on my Lenovo, clicking"Brightness tray" in MX Tools does nothing that I can see. Running mx-tweak-systray in the terminal: "command not found." Tried to install it--not available.

Sorry if this has already been reported earlier...

it tends to slide into the hidden part of the systray. click that littel triangle.

it shows up without an icon though...

chrispop99 wrote: Sat Jul 18, 2020 4:09 am It must be popular - the SourceForge download is pitifully slow for me at the moment!

Chris

asqwerth wrote: Sat Jul 18, 2020 4:44 pm Is this a fresh install? Did you preserve home from beta 1?

Jerry3904 wrote: Sat Jul 18, 2020 4:10 pm

dolphin_oracle wrote: Fri Jul 17, 2020 9:41 pm

Jerry3904 wrote: Fri Jul 17, 2020 9:25 pm Running live on my Lenovo, clicking"Brightness tray" in MX Tools does nothing that I can see. Running mx-tweak-systray in the terminal: "command not found." Tried to install it--not available.

Sorry if this has already been reported earlier...

it tends to slide into the hidden part of the systray. click that littel triangle.

it shows up without an icon though...

Sorry, but I'd like to dredge it up one more time: why would we want it included if it's hidden and has no icon, whereas KDE's power manager (name?) is readily available and covers this function just fine? What does it add? Wouldn't it be better if we just tag it with something like DontShowIn=KDE?

asqwerth wrote: Sat Jul 18, 2020 1:44 pm Was busy and have only just tested beta2 live and then installed it.

Live-USB: testing of the new KDE additions to MX-Tweak:
The panel orientation worked to move the bottom panel to the left side. However, if I made the bottom panel fatter (increased height) and then moved it, the left panel still remained at its original default skinny thickness. On the other hand, moving it back to the bottom restored it to the increased height that I had set.

There was no option to save the current panel config before moving the panels around. I assume that the settings for panel configs are not so easy to get to/more complex unlike in XFCE.

Tested the option to disable the KDE single-click default mode. Works.

During installation, I chose to save desktop changes.

After installation, I rebooted and found:
1. bottom panel had the increased panel height I had set, yay!
2. the single click remained disabled so I was straight away in double click mode.

That's where I am so far.

tony37 wrote: Sun Jul 19, 2020 8:23 am @ Gerson: try right-click on 'Escritorio' in Dolphin in the left menu and edit location to '/home/ghermain/Escritorio'

kc1di wrote: Sun Jul 19, 2020 9:37 am Also in Okular the odt backend should be installed by default as many files today are .odt files.

kc1di wrote: Sun Jul 19, 2020 9:37 am I think thunderbird should be set as default mail client since Kmail is not install in the Beta version. Also in Okular the odt backend should be installed by default as many files today are .odt files.

tony37 wrote: Sun Jul 19, 2020 10:10 am

kc1di wrote: Sun Jul 19, 2020 9:37 am Also in Okular the odt backend should be installed by default as many files today are .odt files.

My naive idea would be that there is LibreOffice for those. Plus: when I try to install okular-backend-odt, it needs 7 dependencies, 56,8 MiB needed to install. I don't think it's an option to add this to the iso.

dolphin_oracle wrote: Sun Jul 19, 2020 12:08 pm we haven't changed anythemes, but its very possible with Qt that some apps won't work with a given theme.

Gerson wrote: Sun Jul 19, 2020 12:56 pm

dolphin_oracle wrote: Sun Jul 19, 2020 12:08 pm we haven't changed anythemes, but its very possible with Qt that some apps won't work with a given theme.

But why did they look good in Beta 1 and now in Beta 2, do they look blank? It's the same theme I'm using.

tony37 wrote: Sun Jul 19, 2020 10:10 am

kc1di wrote: Sun Jul 19, 2020 9:37 am Also in Okular the odt backend should be installed by default as many files today are .odt files.

My naive idea would be that there is LibreOffice for those. Plus: when I try to install okular-backend-odt, it needs 7 dependencies, 56,8 MiB needed to install. I don't think it's an option to add this to the iso.

tony37 wrote: Sun Jul 19, 2020 11:23 am About the many compress options in Dolphin: with .odt, .docx and .epub files this results in having a context menu with: 'KEC: Compress', 'KEC: Extract', 'Compress' [with Ark] and 'Extract' [with Ark]. A bit too much I think.

chrispop99 wrote: Sun Jul 19, 2020 2:45 pm

tony37 wrote: Sun Jul 19, 2020 11:23 am About the many compress options in Dolphin: with .odt, .docx and .epub files this results in having a context menu with: 'KEC: Compress', 'KEC: Extract', 'Compress' [with Ark] and 'Extract' [with Ark]. A bit too much I think.

Dolphin>Control>Services lets you select what the context menu shows.

Chris

tony37 wrote: Sun Jul 19, 2020 3:03 pm Sorry if I'm nitpicking here.

dolphin_oracle wrote: Sun Jul 19, 2020 1:06 pm

Gerson wrote: Sun Jul 19, 2020 12:56 pm

dolphin_oracle wrote: Sun Jul 19, 2020 12:08 pm we haven't changed anythemes, but its very possible with Qt that some apps won't work with a given theme.

But why did they look good in Beta 1 and now in Beta 2, do they look blank? It's the same theme I'm using.

I don't know, but we literally did 0 with the themes.

what's the theme you are using?

kc1di wrote: Sun Jul 19, 2020 9:37 am I think thunderbird should be set as default mail client since Kmail is not install in the Beta version. Also in Okular the odt backend should be installed by default as many files today are .odt files.

m_pav wrote: Sun Jul 19, 2020 8:32 pm The elevation prompt for KDE Partition manager fails to pass the user entered password when clicking the button to send it (sorry, not on any KDE machine right now) and the only option out of the floating elevation prompt window is to use the top right X to close it. The next informative windows says it will open without admin rights and therefore, it becomes useless, however, it is opened correctly by the MX Installer. It was a little slow to display the installed drives (5 in my just obtained test machine) due to calling up smartctl on each one as they are opened, which I think is a nice touch. This is repeatable irrespective of what machine it is run on, however, using the F4 terminal drop down, sudo partitionmanager opens it just fine.

Also confirming the Update Notifier opening itself after an update is finished, however, only tried it running live on a 9YO machine with plenty of RAM where it appeared sluggish.

QSI from the Live session of my own monthly snapshot of regular MX-ahs, so ignore the trimmings and differences, it's just 5 times faster than this KDE beta. I see no reason to include repos and extra so I removed the options from the inxi switches

Code: Select all

$ inxi -Fxxxz
System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.2_ahs_x64 PavsUpdate June 23  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: M5A97 v: Rev 1.xx serial: <filter> 
           UEFI: American Megatrends v: 0705 date: 08/22/2011 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185/M225 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K270 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: 6-Core model: AMD FX-6100 bits: 64 type: MCP arch: Bulldozer rev: 2 
           L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 39734 
           Speed: 1422 MHz min/max: 1400/3300 MHz boost: enabled Core speeds (MHz): 1: 1672 
           2: 1624 3: 1465 4: 1423 5: 1415 6: 1592 
Graphics:  Device-1: NVIDIA GT218 [GeForce 210] vendor: ASUSTeK driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0a65 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1680x1050~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: NVIDIA High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0be3 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8P67 and other motherboards driver: r8169 v: kernel port: d000 
           bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 6.00 TiB used: 27.0 MiB (0.0%) 
           ID-1: /dev/sda vendor: A-Data model: SP900 size: 59.63 GiB speed: 6.0 Gb/s 
           serial: <filter> rev: C3G scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD5000AAKX-001CA0 size: 465.76 GiB 
           speed: 6.0 Gb/s serial: <filter> rev: 1H15 scheme: GPT 
           ID-3: /dev/sdc vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB 
           speed: 6.0 Gb/s serial: <filter> rev: 1D05 scheme: GPT 
           ID-4: /dev/sdd vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB 
           speed: 6.0 Gb/s serial: <filter> rev: 1D05 scheme: GPT 
           ID-5: /dev/sde vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB 
           speed: 6.0 Gb/s serial: <filter> rev: 1D05 scheme: GPT 
           ID-6: /dev/sdf type: USB vendor: A-Data model: USB Flash Drive size: 28.91 GiB 
           serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / size: 6.13 GiB used: 27.0 MiB (0.4%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 15.2 C mobo: N/A gpu: nouveau temp: 35 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 220 Uptime: 5m Memory: 7.73 GiB used: 563.0 MiB (7.1%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: xfce4-terminal inxi: 3.0.36

• Disable the 30-second pause before logging out, shutting down or restarting so you don't have to go hunting through the Plasma settings to find it.(Even better would be to be able to change the timer value if that setting's in a config file somewhere, but via the Plasma GUI it's either the default 30 second delay or none.)
• Toggle between single- and double-click to open apps on the desktop and in Dolphin (it's a global setting for both, unlike Thunar where its behavior and the desktop's behavior can be set separately.)

JayM wrote: Mon Jul 20, 2020 2:45 am Some MX Tweaks I'd like to see be added:

• Disable the 30-second pause before logging out, shutting down or restarting so you don't have to go hunting through the Plasma settings to find it.(Even better would be to be able to change the timer value if that setting's in a config file somewhere, but via the Plasma GUI it's either the default 30 second delay or none.)
• Toggle between single- and double-click to open apps on the desktop and in Dolphin (it's a global setting for both, unlike Thunar where its behavior and the desktop's behavior can be set separately.)

tony37 wrote: Mon Jul 20, 2020 4:40 am The single/double-click toggle is already there.

danielson wrote: Mon Jul 20, 2020 6:24 am Issue of icons not showing up for Vivaldi (menu+panel), even with another theme, resolved (at least for MX theme) with reboot.

tony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.

dolphin_oracle wrote: Mon Jul 20, 2020 7:46 am

tony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.

Let me know.how.to trigger the apply of settings changes to plasmashell and I'll do it that way instead of resetting plasmashell.

tony37 wrote: Mon Jul 20, 2020 7:53 am

dolphin_oracle wrote: Mon Jul 20, 2020 7:46 am

tony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.

Let me know.how.to trigger the apply of settings changes to plasmashell and I'll do it that way instead of resetting plasmashell.

can't help you there, sorry

dolphin_oracle wrote: Mon Jul 20, 2020 7:59 am that's why I'm using the built-in plasmashell --replace function. Its the same thing Look-and-feel does. Its overkill, but its the only way outside the actual settings applications to do it. I presume there may be a dbus call you can make to trigger reload of configurations, but if there is I haven't been able to craft a working version.

tony37 wrote: Mon Jul 20, 2020 10:40 am Something I've never been able to find out is how to change the single-click behavior of Dolphin when opened as root. Might be a tad dangerous if someone is used to double-click and in root mode this changes in single-click. That would be a useful addition to MX Tweak, if possible.

edit: I finally found how to do this: add

Code: Select all

SingleClick=false

in /root/.config/kdeglobals under the [KDE] header
If there is no such file, like in MX KDE, create one with following content:

Code: Select all

[KDE]
SingleClick=false

sudo systemsettings5

uncle mark wrote: Mon Jul 20, 2020 12:04 pm Just an observation, but it sounds like most of the posts concern config teaks as opposed to actual bugs or problems with the OS. Testament to the job well done by the devs.

tony37 wrote: Mon Jul 20, 2020 12:39 pm Small issue: When I put the 'Desktop Theme' on Breeze Light the MX Updater icon is barely visible (also after rebooting), it is light grey on slightly lighter grey. I can't find a dark mx-updater or mnotify icon in /usr/share/icons so I think some extra icons have to be created there.

tony37 wrote: Mon Jul 20, 2020 12:39 pm Small issue: When I put the 'Desktop Theme' on Breeze Light the MX Updater icon is barely visible (also after rebooting), it is light grey on slightly lighter grey. I can't find a dark mx-updater or mnotify icon in /usr/share/icons so I think some extra icons have to be created there.

dolphin_oracle wrote: Mon Jul 20, 2020 1:16 pm

tony37 wrote: Mon Jul 20, 2020 12:39 pm Small issue: When I put the 'Desktop Theme' on Breeze Light the MX Updater icon is barely visible (also after rebooting), it is light grey on slightly lighter grey. I can't find a dark mx-updater or mnotify icon in /usr/share/icons so I think some extra icons have to be created there.

there are alternate icons available in the updater preferences.

tony37 wrote: Mon Jul 20, 2020 1:26 pm

dolphin_oracle wrote: Mon Jul 20, 2020 1:16 pm

tony37 wrote: Mon Jul 20, 2020 12:39 pm Small issue: When I put the 'Desktop Theme' on Breeze Light the MX Updater icon is barely visible (also after rebooting), it is light grey on slightly lighter grey. I can't find a dark mx-updater or mnotify icon in /usr/share/icons so I think some extra icons have to be created there.

there are alternate icons available in the updater preferences.

Ok, hadn't looked there yet, I still think I prefer the wireframe though

srq2625 wrote: Mon Jul 20, 2020 2:03 pm On every system startup or reboot, everything goes well until the logon screen is displayed. It is displayed for a split-second, screen is blanked to black, and then the logon screen is re-displayed.

To the best of my knowledge, I've not made any changes to the boot-up process other than to edit /etc/default/grub to remove the "quite splash" from the GRUB_CMDLINE_LINUX_DEFAULT parameter.

This is installed as the only O/S on the system and is installed on bare-metal.

Here's my QSI:

Code: Select all

System:    Host: SagerKDEB2 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=d2c61003-1f2e-4841-9464-115a2b829c78 ro 
           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: Laptop System: Notebook product: W65_67SZ v: N/A serial: <filter> Chassis: type: 9 
           serial: <filter> 
           Mobo: Notebook model: W65_67SZ serial: <filter> UEFI: American Megatrends v: 1.03.05RLS1 
           date: 03/13/2014 
Battery:   ID-1: BAT0 charge: 56.3 Wh condition: 56.3/62.2 Wh (91%) volts: 12.8/11.1 model: Notebook BAT 
           type: Li-ion serial: <filter> status: Full 
           Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter> charge: 55% (should be ignored) 
           rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-4710MQ bits: 64 type: MT MCP arch: Haswell family: 6 
           model-id: 3C (60) stepping: 3 microcode: 28 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 39911 
           Speed: 2625 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 2625 2: 1921 3: 2333 4: 2247 
           5: 2127 6: 2947 7: 2392 8: 2546 
           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 mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: CLEVO/KAPOK driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0416 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.0.7 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: CLEVO/KAPOK 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: CLEVO/KAPOK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel port: f040 bus ID: 04:00.0 
           chip ID: 8086:08b1 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK 
           driver: r8169 v: kernel port: e000 bus ID: 05:00.2 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 69.96 GiB (15.0%) 
           ID-1: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 90WD scheme: GPT 
Partition: ID-1: / raw size: 20.00 GiB size: 19.56 GiB (97.81%) used: 7.16 GiB (36.6%) fs: ext4 
           dev: /dev/sda3 
           ID-2: /home raw size: 429.51 GiB size: 421.77 GiB (98.20%) used: 62.40 GiB (14.8%) 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: 56.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 https://mirrors.evowise.com/mxlinux-packages/mx/repo/ buster main non-free
           2: deb https://mirrors.evowise.com/mxlinux-packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 267 Uptime: 2m Memory: 15.57 GiB used: 925.1 MiB (5.8%) 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 

dolphin_oracle wrote: Mon Jul 20, 2020 2:26 pm There's not a problem, that's how we have it set to work under sysVinit.

asqwerth wrote: Tue Jul 21, 2020 1:07 pm What was the modification in the virtualbox-guest-utils-modified-init package?

When I installed Beta 2 (real metal) and tried to run Virtualbox on the same, my VM (manjaro kde) kept flickering and flashing whenever I scrolled dolphin or webpages using the mouse. If I clicked on various places on the screen, the flashing might also happen.

I didn't face this issue in the alphas (didn't install VB in Beta 1).

chrispop99 wrote: Tue Jul 21, 2020 3:54 pm Using MX User Manager to permit a user to automatically logon does not work. Password entry is still required after making the change.

Chris

bbfuller wrote: Tue Jul 21, 2020 4:02 pm Dolphin file Manager

One of the useful things about the Dolphin file manager is the ability to create entries in the Places Panel for Network machines, or individual shares.

In my installation of the MX KDE Beta, that facility seems to require the manual creation of an entry by right clicking on a heading, selecting "Add" and typing in the address. That also seems to be the default configuration for Mageia and PCLinuxOS.

I've found one distribution so far (Manjaro) that has an "Add to Places" option on the Dolphin "File" menu that automates the whole process.

Any chance that facility could be added to MX?

itsme wrote: Tue Jul 21, 2020 3:30 pm

Code: Select all

chris@mx:~$ timedatectl 
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down

Only me or is this already been made aware?

chrispop99 wrote: Tue Jul 21, 2020 3:39 pm When you right-click the Application Launcher icon, then select Alternatives to try another type of menu, the MX icon is lost. If you then revert to the Application Launcher, you don't get thew MX icon back.

chrispop99 wrote: Tue Jul 21, 2020 4:08 pm

bbfuller wrote: Tue Jul 21, 2020 4:02 pm Dolphin file Manager

One of the useful things about the Dolphin file manager is the ability to create entries in the Places Panel for Network machines, or individual shares.

In my installation of the MX KDE Beta, that facility seems to require the manual creation of an entry by right clicking on a heading, selecting "Add" and typing in the address. That also seems to be the default configuration for Mageia and PCLinuxOS.

I've found one distribution so far (Manjaro) that has an "Add to Places" option on the Dolphin "File" menu that automates the whole process.

Any chance that facility could be added to MX?

'Add to places' is available in the context menu by right-clicking the folder directly.

Chris

chrispop99 wrote: Tue Jul 21, 2020 3:29 pm Alt-F1 is not able to be used for the MX Manual as it is set to open the menu, along with the Meta key. If you redefine Alt-F1, the Meta key no longer opens the menu, and can't be configured to do so.

I've found a sort of work-around. If you define Alt-F1 for mx-manual, then change the menu key to the Meta key plus something random (I used Meta + M), it all works as wanted. Meta opens the menu, Alt-F1 opens the manual.

I haven't been able to get this to work in Global Shortcuts, but it seems they are broken to some extent in any case.

Chris

baldyeti wrote: Tue Jul 21, 2020 4:31 pm Speaking of the application menu icon, this reminds me that forum user "Mike" once contributed a very nice icon that combines the MX logo with the KDE gears.

I have been using it ever since on my MX18/Neptune install.

tony37 wrote: Tue Jul 21, 2020 6:26 pm ....

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' ....

chrispop99 wrote: Tue Jul 21, 2020 3:39 pm When you right-click the Application Launcher icon, then select Alternatives to try another type of menu, the MX icon is lost. If you then revert to the Application Launcher, you don't get thew MX icon back.

Can that icon be made the default for all menu types?

Chris

asqwerth wrote: Tue Jul 21, 2020 10:33 pm

tony37 wrote: Tue Jul 21, 2020 6:26 pm ....

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' ....

You might want to explore the preinstalled custom actions available in the right click context menu....

tony37 wrote: Tue Jul 21, 2020 6:26 pm PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' with command

Code: Select all

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin

Gerson wrote: Wed Jul 22, 2020 2:07 pm If you like and are interested, this would be a nice logo for the KDE menu.

richb wrote: Wed Jul 22, 2020 7:19 pm Very nice indeed. Thanks for the work and posting. I modified it for my use and panel settings. Click image to see full size.

JayM wrote: Wed Jul 22, 2020 12:19 am The updater auto-opened its right-click context menu again after applying today's update (mx-tweak.) I changed its preferences afterward to use Muon instead of MX Updater View and Upgrade window. I'll find out if it still happens after the next update.

JayM wrote: Thu Jul 23, 2020 6:51 am

JayM wrote: Wed Jul 22, 2020 12:19 am The updater auto-opened its right-click context menu again after applying today's update (mx-tweak.) I changed its preferences afterward to use Muon instead of MX Updater View and Upgrade window. I'll find out if it still happens after the next update.

No right-click menu opened, but what a pain in the behind Muon is to use! <-opinion

tony37 wrote: Wed Jul 22, 2020 4:10 pm- .tiff files are set to be opened by Gwenview but that doesn't work (does work on version 19.12 though), GIMP and Okular can open them, so default mime setting should be changed there. Preview in Dolphin of .tiff files at first doesn't seem to work, but after the file has been opened by GIMP it does work. Weird.

fehlix wrote: Thu Jul 23, 2020 6:55 am

JayM wrote: Thu Jul 23, 2020 6:51 am

JayM wrote: Wed Jul 22, 2020 12:19 am The updater auto-opened its right-click context menu again after applying today's update (mx-tweak.) I changed its preferences afterward to use Muon instead of MX Updater View and Upgrade window. I'll find out if it still happens after the next update.

No right-click menu opened, but what a pain in the behind Muon is to use! <-opinion

Would the additional popup of the "right-click-menu" also show if you initiate "View and Upgrade" not through the left-click but through the option within the right-click menu?

Gerson wrote: Thu Jul 23, 2020 6:39 am

richb wrote: Wed Jul 22, 2020 7:19 pm Very nice indeed. Thanks for the work and posting. I modified it for my use and panel settings. Click image to see full size.

It looks great! It would be good to include it in final KDE.

Gerson wrote: Thu Jul 23, 2020 6:39 am

richb wrote: Wed Jul 22, 2020 7:19 pm Very nice indeed. Thanks for the work and posting. I modified it for my use and panel settings. Click image to see full size.

It looks great! It would be good to include it in final KDE.

JayM wrote: Thu Jul 23, 2020 6:51 am but what a pain in the behind Muon is to use! <-opinion

tony37 wrote: Tue Jul 21, 2020 6:26 pm Ctrl+Alt+T to 'Launch Konsole' doesn't work. I can add a custom entry with action konsole and shortcut Ctrl+Alt+T, now it works.
When I try to add other Application Launchers in Global Shortcuts, they consistently fail to work.

The problem may be that System Settings always adds 'Launch ...' to the name of the program (maybe restart of system settings required to see this). So maybe it thinks the program is called "launch konsole". Because I have some preset application launchers in Kubuntu (Plasma 5.18) and they work fine and don't have 'Launch' in the title. But when I try to make an extra launcher there, it prepends 'Launch' to the name. In KDE Neon (Plasma 5.19) it doesn't do this, but there seems to be another bug there.
Actually it's the first time I notice this because I always made custom entries for starting programs (and websites). Only problem is you sometimes have to search the actual command, like synaptic-pkexec

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' with command

Code: Select all

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin

tony37 wrote: Thu Jul 23, 2020 7:46 am

JayM wrote: Thu Jul 23, 2020 6:51 am but what a pain in the behind Muon is to use! <-opinion

+1
Is there any distro outside Kubuntu installing it by default? It also pulls in the potentially very irritating apt-xapian-index, but maybe that has been turned off in MX.

jeffreyC wrote: Thu Jul 23, 2020 9:43 am But apt-xapian-index is what makes Synaptic search work, and on my (several) MX installs it is turned on.

Gerson wrote: Wed Jul 22, 2020 2:07 pm If you like and are interested, this would be a nice logo for the KDE menu.

leslie1017 wrote: Thu Jul 23, 2020 11:34 am MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

asqwerth wrote: Thu Jul 23, 2020 7:41 am

Gerson wrote: Thu Jul 23, 2020 6:39 am

richb wrote: Wed Jul 22, 2020 7:19 pm Very nice indeed. Thanks for the work and posting. I modified it for my use and panel settings. Click image to see full size.

It looks great! It would be good to include it in final KDE.

I would prefer to open this to the community to create artwork and wallpaper exploring the combination of different elements of the MX and KDE/plasma name and/or graphical logos (KDE is more than just the gear + K logo, there's also the logo comprising the > with 3 dots ).

Gerson's graphic is just the start. Let loose your imagination, people. Start a new thread in the artwork sub forum. Maybe gerson can post his icon/graphic there to start us off, so it doesn't get lost in this bug reporting thread.


If there are some really nice pics or artwork , it might find its way to the iso or perhaps the future mx20-kde.

SwampRabbit wrote: Thu Jul 23, 2020 12:58 pm

leslie1017 wrote: Thu Jul 23, 2020 11:34 am MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

Can you verify that it is only an issue on MX KDE beta2 and not also an issue on MX-19.2 Xfce?

You don't really need to use systemd as your init to use flatpaks and I honestly don't think it is part of the reason the install or starting has issues.
You also don't need install Steam via a flatpak either, it is in the repository and can be installed via MX Package Installer, fcitx can be installed the same way.

If there is a flatpak issue only with the KDE beta2, then it needs looked at, if not then this discussion can continue in the other thread you started.

Gerson wrote: Thu Jul 23, 2020 1:28 pm Do you already have a name for MX-KDE? Just as MX 19 is called "ugly duckling" I suggest that MX-KDE is called "caterpillar"; if the ugly duckling turns into a beautiful swan, the caterpillar turns into a beautiful butterfly!

Gerson wrote: Thu Jul 23, 2020 1:17 pm Please @asqwerth, could you put it in the right place? I went to do it, but I got lost in so many threads... HAHAHA

Gerson wrote: Thu Jul 23, 2020 1:28 pm Do you already have a name for MX-KDE? Just as MX 19 is called "ugly duckling" I suggest that MX-KDE is called "caterpillar"; if the ugly duckling turns into a beautiful swan, the caterpillar turns into a beautiful butterfly!

JayM wrote: Thu Jul 23, 2020 7:13 am FYI I do have the two checkboxes checked to answer yes to all prompts and to close the updater when complete. It seems that the next testing step is to change those back to unselected, then select one at a time to see which one if any is making the right-click menu appear. I hope there are a few more updates coming over the next few days.

asqwerth wrote: Thu Jul 23, 2020 2:06 pm

Gerson wrote: Thu Jul 23, 2020 1:17 pm Please @asqwerth, could you put it in the right place? I went to do it, but I got lost in so many threads... HAHAHA

Done. Go here:
viewtopic.php?f=116&t=59393#p587902

SwampRabbit wrote: Thu Jul 23, 2020 12:58 pm

leslie1017 wrote: Thu Jul 23, 2020 11:34 am MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

Can you verify that it is only an issue on MX KDE beta2 and not also an issue on MX-19.2 Xfce?

You don't really need to use systemd as your init to use flatpaks and I honestly don't think it is part of the reason the install or starting has issues.
You also don't need install Steam via a flatpak either, it is in the repository and can be installed via MX Package Installer, fcitx can be installed the same way.

If there is a flatpak issue only with the KDE beta2, then it needs looked at, if not then this discussion can continue in the other thread you started.

dolphin_oracle wrote: Thu Jul 23, 2020 1:19 pm

SwampRabbit wrote: Thu Jul 23, 2020 12:58 pm

leslie1017 wrote: Thu Jul 23, 2020 11:34 am MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

Can you verify that it is only an issue on MX KDE beta2 and not also an issue on MX-19.2 Xfce?

You don't really need to use systemd as your init to use flatpaks and I honestly don't think it is part of the reason the install or starting has issues.
You also don't need install Steam via a flatpak either, it is in the repository and can be installed via MX Package Installer, fcitx can be installed the same way.

If there is a flatpak issue only with the KDE beta2, then it needs looked at, if not then this discussion can continue in the other thread you started.

might need xdg-desktop-portal-kde installed. on Xfce we have xdg-desktop-portal-gtk . flatpaks use the xdg-desktop-portal system for accessing things like home folders, which steam would.

leslie@leslie-desktop ~/Downloads $ sudo apt install xdg-desktop-portal-kde 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  xdg-desktop-portal-kde
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 94.0 kB of archives.
After this operation, 473 kB of additional disk space will be used.
Get:1 http://mirrors.ustc.edu.cn/debian buster/main amd64 xdg-desktop-portal-kde amd64 5.14.5-1 [94.0 kB]
Fetched 94.0 kB in 0s (312 kB/s)            
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Selecting previously unselected package xdg-desktop-portal-kde.
(Reading database ... 211947 files and directories currently installed.)
Preparing to unpack .../xdg-desktop-portal-kde_5.14.5-1_amd64.deb ...
Unpacking xdg-desktop-portal-kde (5.14.5-1) ...
Setting up xdg-desktop-portal-kde (5.14.5-1) ...
leslie@leslie-desktop ~/Downloads $ 

leslie1017 wrote: Thu Jul 23, 2020 9:38 pm I just tried boot without systemd enabled and got same issue for steam and fcitx.
I enable systemd for snap applications, now I can see shutter(a screen capture app I use daily, provided only by snappy) not started.
My software install order is flatpak>snap>apt, doing this is expecting consistent app experience. BTW fcitx is installed by apt neither flatpak nor snap.
I don't have another machine for MX-19.2 Xfce, very sorroy that I can't do such kind comparision.

kangburra wrote: Fri Jul 24, 2020 12:58 am I have setup fingerprint-gui and it works well except now when I resume the machine the password does not unlock the machine, neither does the fingerprint. I have to enter the password and see it say failed to unlock, then swipe my finger with that password still in the box. It seems excessively secure to require both.

SwampRabbit wrote: Fri Jul 24, 2020 1:24 am

kangburra wrote: Fri Jul 24, 2020 12:58 am I have setup fingerprint-gui and it works well except now when I resume the machine the password does not unlock the machine, neither does the fingerprint. I have to enter the password and see it say failed to unlock, then swipe my finger with that password still in the box. It seems excessively secure to require both.

Pretty sure fingerprint-gui is not created by the MX team, so how “excessive“ it’s functionality is is not up to MX really.

You may want to research the application more and see if it is a setting or known issue.

If it’s a bug in the particular version package, and it just needs updated or is missing a dependency to make it work as expected, then that is another topic unrelated to the KDE beta.

SwampRabbit wrote: Fri Jul 24, 2020 1:24 am

kangburra wrote: Fri Jul 24, 2020 12:58 am I have setup fingerprint-gui and it works well except now when I resume the machine the password does not unlock the machine, neither does the fingerprint. I have to enter the password and see it say failed to unlock, then swipe my finger with that password still in the box. It seems excessively secure to require both.

Pretty sure fingerprint-gui is not created by the MX team, so how “excessive“ it’s functionality is is not up to MX really.

You may want to research the application more and see if it is a setting or known issue.

If it’s a bug in the particular version package, and it just needs updated or is missing a dependency to make it work as expected, then that is another topic unrelated to the KDE beta.

SwampRabbit wrote: Thu Jul 23, 2020 10:19 pm

leslie1017 wrote: Thu Jul 23, 2020 9:38 pm I just tried boot without systemd enabled and got same issue for steam and fcitx.
I enable systemd for snap applications, now I can see shutter(a screen capture app I use daily, provided only by snappy) not started.
My software install order is flatpak>snap>apt, doing this is expecting consistent app experience. BTW fcitx is installed by apt neither flatpak nor snap.
I don't have another machine for MX-19.2 Xfce, very sorroy that I can't do such kind comparision.

So your only machine you are running a BETA on?
Yes
There is no upgrade path that I am aware of from the beta to final, you're probably going to have to reinstall anyway.
Sad to know this, I can reinstall, I will keep my home folder with all settings and installed games/data.
So you are having more issues than just with flatpaks on the KDE Beta2?
These two are blocking issue, fcitx is more critical, I use it to input message in Chinese.
There are some other issues(may be not issue, I didn't success on other distro), like can't set scaling seperately for my 1080p monitor and 4K monitor.
You didn't mention needing snap support, but yes you need systemd for snaps.

You're having the following issues?
- Steam flatpak
- fcitx via apt

I just installed Steam flatpak using MX Package Installer on MX-KDE beta2, it installed fine, and opens fine.
I found something new, I installed steam on my AMD CPU/GPU working machine, and it opens well, after I got home, I plug my MX system(it's installed on a USB drive) into a machine with interl CPU and NVidia GPU, and I installed Nvidia graphics driver first, then start steam, and see crash.
Just now I reached my working place and plugged MX system in AMD CPU/GPU machine, steam can open correctly again.
fcitx 4.x series with Qt5 front end installed via the MX Package Installer no issues and at least the Input Method - System Settings Module opens... I can't test past this right now.
I can also open the fcitx settings window, the problem is when press ctrl+space or shift key to use fcitx input method, nothing shows up
Now the only difference is I didn't boot with systemd, but I don't think booting with systemd is the issue... it may be. But having just tested both of those, I think the issue may be isolated to your system and not a issue with the Beta or those applications.

leslie1017 wrote: Fri Jul 24, 2020 1:45 am Inline

SwampRabbit wrote: Fri Jul 24, 2020 2:08 am

leslie1017 wrote: Fri Jul 24, 2020 1:45 am Inline

I don’t believe your issues are related to the KDE beta2 except maybe the Screen scaling issue, but I don’t know.

As far as the rest, this isn’t really the place to discuss them. Running from a live USB swapping from an AMD system to Intel/Nvidia
system for example... total different monster problem unrelated to KDE beta2.

So please start a thread for each issue separately. It is very hard to diagnose problems when it is a dozen different ones all at once, plus it doesn’t get the attention and help from other users.

JayM wrote: Fri Jul 24, 2020 3:12 am I'm not SwampRabbit, but issues specifically with the KDE beta 2 belong here. As far as the Nvidia driver installation problem goes, normally it would go in the MX KDE forum after it gets created which will be after that version of MX is officially released, but meanwhile I guess it also goes here?

It would be helpful if, when you're on the machine with the Intel/Nvidia combo, you described the issue in some detail including which Nvidia driver you selected, and if you posted the Quick System Info from that machine.

Gerson wrote: Fri Jul 24, 2020 6:44 am How can you make all the windows have the same color of the chosen theme? Some applications appear with a white background when using dark themes.

sudo bash -c "lookandfeeltool -a $(grep -oP 'LookAndFeelPackage=\K.*' ~/.config/kdeglobals)  2>/dev/null"

JayM wrote: Fri Jul 24, 2020 3:33 am The fcitx keyboard shortcuts are probably just a matter of mapping them in Plasma, but I have no idea how as I'm an Xfce kind of guy. Perhaps this will help? https://www.addictivetips.com/ubuntu-li ... -plasma-5/

JayM wrote: Fri Jul 24, 2020 3:12 am I'm not SwampRabbit, but issues specifically with the KDE beta 2 belong here. As far as the Nvidia driver installation problem goes, normally it would go in the MX KDE forum after it gets created which will be after that version of MX is officially released, but meanwhile I guess it also goes here?

It would be helpful if, when you're on the machine with the Intel/Nvidia combo, you described the issue in some detail including which Nvidia driver you selected, and if you posted the Quick System Info from that machine.

System:    Host: leslie-desktop 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=c5af275b-a0d4-4aea-830e-3b11c9a44ad6 ro quiet splash 
           Desktop: KDE Plasma 5.14.5 info: plank 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: H110M-K v: Rev X.0x serial: <filter> UEFI [Legacy]: American Megatrends v: 3405 
           date: 08/24/2017 
CPU:       Topology: Quad Core model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake family: 6 model-id: 9E (158) 
           stepping: 9 microcode: D6 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27199 
           Speed: 800 MHz min/max: 800/3800 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 GP106 [GeForce GTX 1060 3GB] driver: nvidia v: 440.100 bus ID: 01:00.0 chip ID: 10de:1c02 
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           compositor: kwin_x11 resolution: 3840x2160~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-H HD Audio vendor: ASUSTeK 100 Series/C230 Series Family driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 
           Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f1 
           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: d000 
           bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.47 TiB used: 279.31 GiB (18.5%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-08M2NA0 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A01 temp: 32 C scheme: MBR 
           ID-2: /dev/sdb vendor: Tigo model: SSD 120GB size: 111.79 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 6A temp: 49 C scheme: GPT 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: SD9SN8W512G size: 465.76 GiB block size: physical: 4096 B 
           logical: 512 B serial: <filter> rev: 1012 scheme: MBR 
Partition: ID-1: / raw size: 74.51 GiB size: 72.83 GiB (97.76%) used: 13.85 GiB (19.0%) fs: ext4 dev: /dev/sdc2 
           ID-2: /home raw size: 390.78 GiB size: 383.64 GiB (98.17%) used: 265.45 GiB (69.2%) fs: ext4 dev: /dev/sdc3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 53 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 34% 
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://mirrors.ustc.edu.cn/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://mirrors.ustc.edu.cn/debian/ buster main contrib non-free
           2: deb http://mirrors.ustc.edu.cn/debian-security/ buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirrors.tuna.tsinghua.edu.cn/mxlinux/mx/repo/ buster main non-free
           2: deb https://mirrors.tuna.tsinghua.edu.cn/mxlinux/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/sogoupinyin.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 230 Uptime: 8m Memory: 15.58 GiB used: 2.39 GiB (15.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 

fehlix wrote: Fri Jul 24, 2020 6:49 am

Gerson wrote: Fri Jul 24, 2020 6:44 am How can you make all the windows have the same color of the chosen theme? Some applications appear with a white background when using dark themes.

Perhaps try this line wunning within the konsole opend as normal user:

Code: Select all

sudo bash -c "lookandfeeltool -a $(grep -oP 'LookAndFeelPackage=\K.*' ~/.config/kdeglobals)  2>/dev/null"

It's set the theme for GUI's app running as root the same as for the user.

Gerson wrote: Fri Jul 24, 2020 7:03 am I applied the line from Konsole and even restarted and changed the theme but I get the same result of white background in dark themes.

sudo systemsettings5

tony37 wrote: Fri Jul 24, 2020 7:07 am

Gerson wrote: Fri Jul 24, 2020 7:03 am I applied the line from Konsole and even restarted and changed the theme but I get the same result of white background in dark themes.

It worked for me. You can also try

Code: Select all

sudo systemsettings5

and make the changes in GUI
Is it possible it didn't work for you because you didn't have a /root/.config/kdeglobals file yet? I simply don't know if the command creates the file if it isn't there

Gerson wrote: Fri Jul 24, 2020 7:03 am

fehlix wrote: Fri Jul 24, 2020 6:49 am

Gerson wrote: Fri Jul 24, 2020 6:44 am How can you make all the windows have the same color of the chosen theme? Some applications appear with a white background when using dark themes.

Perhaps try this line wunning within the konsole opend as normal user:

Code: Select all

sudo bash -c "lookandfeeltool -a $(grep -oP 'LookAndFeelPackage=\K.*' ~/.config/kdeglobals)  2>/dev/null"

It's set the theme for GUI's app running as root the same as for the user.

I applied the line from Konsole and even restarted and changed the theme but I get the same result of white background in dark themes.

lookandfeeltool --list

mx-pkexec  lookandfeeltool --list

tony37 wrote: Fri Jul 24, 2020 7:21 am Is the color scheme set to KvBrown when you open system settings with sudo?

leslie1017 wrote: Fri Jul 24, 2020 6:56 am

JayM wrote: Fri Jul 24, 2020 3:33 am The fcitx keyboard shortcuts are probably just a matter of mapping them in Plasma, but I have no idea how as I'm an Xfce kind of guy. Perhaps this will help? https://www.addictivetips.com/ubuntu-li ... -plasma-5/

I solved the fcitx issue, by installing sogoupinyin:
http://cdn2.ime.sogou.com/dl/index/1571 ... _amd64.deb

I think this package installed some neccessary depencies for fcitx and make it work.

chrispop99 wrote: Tue Jul 21, 2020 3:54 pm Using MX User Manager to permit a user to automatically logon does not work. Password entry is still required after making the change.

Chris

chrispop99 wrote: Fri Jul 24, 2020 8:52 am

chrispop99 wrote: Tue Jul 21, 2020 3:54 pm Using MX User Manager to permit a user to automatically logon does not work. Password entry is still required after making the change.

Chris

Just confirmation that today's update to mx-user fixed this.

Chris

richb wrote: Fri Jul 17, 2020 10:53 pm

JayM wrote: Fri Jul 17, 2020 10:21 pm I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

kangburra wrote: Fri Jul 24, 2020 1:30 am It works perfectly well in the XFCE version, I installed the same way and Konsole works as expected. I am guessing it is a PAM problem but I thought I should report it.

dolphin_oracle wrote: Fri Jul 24, 2020 7:56 am

leslie1017 wrote: Fri Jul 24, 2020 6:56 am I solved the fcitx issue, by installing sogoupinyin:
http://cdn2.ime.sogou.com/dl/index/1571 ... _amd64.deb

I think this package installed some neccessary depencies for fcitx and make it work.

quite possibly. looks like there is some Xsession setup too. Thanks!

fcitx-sogouimebs uses qt5, and it is indeed MUCH more stable than the current version of fcitx-sogoupinyin

Gerson wrote: Fri Jul 24, 2020 9:33 am

richb wrote: Fri Jul 17, 2020 10:53 pm

JayM wrote: Fri Jul 17, 2020 10:21 pm I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

I have installed beta 2 in a solid disk and I don't have that problem, right click to see the updates, I run and when I finish the update it closes itself and the icon disappears until when there are new updates.

leslie1017 wrote: Fri Jul 24, 2020 1:45 am I found something new, I installed steam on my AMD CPU/GPU working machine, and it opens well, after I got home, I plug my MX system(it's installed on a USB drive) into a machine with interl CPU and NVidia GPU, and I installed Nvidia graphics driver first, then start steam, and see crash.
Just now I reached my working place and plugged MX system in AMD CPU/GPU machine, steam can open correctly again.

SwampRabbit wrote: Fri Jul 24, 2020 10:05 am

leslie1017 wrote: Fri Jul 24, 2020 1:45 am I found something new, I installed steam on my AMD CPU/GPU working machine, and it opens well, after I got home, I plug my MX system(it's installed on a USB drive) into a machine with interl CPU and NVidia GPU, and I installed Nvidia graphics driver first, then start steam, and see crash.
Just now I reached my working place and plugged MX system in AMD CPU/GPU machine, steam can open correctly again.

How are you installing the Nvidia drivers, via MX Package Installer or the Nvidia Driver Installer application?
MX Package Installer(MX Tools->Nvidia driver installer)
Just so we are understanding that QSI is the system showing the issue, but you're booting from a Live USB?
No, I installed MX KDE into a USB disk, which means I boot from a Live USB then installed MX KDE to another USB disk, I think I should not mention this to make confusing

dolphin_oracle wrote: Fri Jul 24, 2020 10:59 am you'll want to post the log for the /var/log/ddm.log so we can see what happened. there is a variety of things that can happen, not the least of which is installing the wrong driver, etc... those nvidia laptops with intel/nvidia are tricky and I doubt its actually related to the kde setup.

leslie1017 wrote: Fri Jul 24, 2020 10:36 am

SwampRabbit wrote: Fri Jul 24, 2020 10:05 am Just so we are understanding that QSI is the system showing the issue, but you're booting from a Live USB?

No, I installed MX KDE into a USB disk, which means I boot from a Live USB then installed MX KDE to another USB disk, I think I should not mention this to make confusing

leslie1017 wrote: Fri Jul 24, 2020 12:21 pm Lutris+battle.net crashes on start.
I use apt to install the lutris, then use lutris offical site script installed battle.net. ... Not sure the steps to enable lutris on MX KDE

SwampRabbit wrote: Fri Jul 24, 2020 9:35 am

kangburra wrote: Fri Jul 24, 2020 1:30 am It works perfectly well in the XFCE version, I installed the same way and Konsole works as expected. I am guessing it is a PAM problem but I thought I should report it.

It is still hard to know if this is specific for the KDE Beta2.

We need know how you installed this, I looked and didn't find this "fingerprint-gui" for MX or Debian, so you installed this from source?

I am assuming it is this application:
https://aur.archlinux.org/packages/fingerprint-gui

Note its been flagged as out of date, the developer's website has an expired self-signed cert, blah, blah, blah.
Doesn't look like it has been packaged for Debian or any derivative either.

There could potentially already be an alternative application to use that works though, just don't know what it is.
Doesn't our MX Manual, Wiki or FAQ have something on fingerprint readers?

kangburra wrote: Fri Jul 24, 2020 4:55 pm Since coming to MX Linux from whatever I was using before I have used this PPA https://launchpad.net/~fingerprint/+arc ... rprint-gui or at least added the apt file and imported the key. As I say it works properly in XFCE and works for Konsole commands but the lock screen requires multiple entries to get back in.

I will have a look for an MX fingerprint reader, I must admit when I find a way that works I use it until it stops working.

GNOME users: The package policykit-1-fingerprint-gui replaces GNOME's standard PolicyKit daemon (contained in package policykit-1-gnome) ... KDE SC users: The above instructions for GNOME users apply to you as well

Please note that Fingerprint GUI doesn't work with kdm and kscreensaver because of a bug in these applications

Check /var/log/auth.log for any clues. Fingerprint GUI is set up to run in debugging mode by default.

JayM wrote: Fri Jul 24, 2020 10:26 pm This is really a minor thing but it bothers me, and I know darned well that there will be forum posts and bug reports about it later. It's little niggles like this that give a poor overall impression of a distro IMO (thinking of reviewers.)

SwampRabbit wrote: Fri Jul 24, 2020 10:40 pm

JayM wrote: Fri Jul 24, 2020 10:26 pm This is really a minor thing but it bothers me, and I know darned well that there will be forum posts and bug reports about it later. It's little niggles like this that give a poor overall impression of a distro IMO (thinking of reviewers.)

Post your darn QSI Jay! :lipsrsealed:

I am extremely impressed by the amount of effort and success that has been done with all of that for the KDE version. I know they will get it fixed one way or another.
If any reviewers don't like it, they can actually help the team, or go use Kubuntu! (partially joking about the Kubuntu part)

System:
  Host: mx-kde-b2 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=3de26e4a-56c2-420f-b19b-18102ba13170 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: 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: 50.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Full 
CPU:
  Topology: Triple 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: 1536 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 11977 
  Speed: 1996 MHz min/max: N/A Core speeds (MHz): 1: 1996 2: 1996 3: 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: 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: 1884x968~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: 25.00 GiB used: 6.63 GiB (26.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: 6.63 GiB (29.5%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  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: 180 Uptime: N/A Memory: 3.85 GiB used: 463.5 MiB (11.8%) 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 

JayM wrote: Fri Jul 24, 2020 10:44 pm That's what happens when thunderstorms at night plus frightened dogs crying means you're sleep-deprived.

richb wrote: Fri Jul 24, 2020 10:59 pm Yes the exact same opening of the MX Updater window happens with me when the updater icon changes from green to wireframe. It is not only JayM. This is not a VB install but a hardware install.

I would post my QSI but at the moment I am running Kubuntu 20.04.1 LTS, KDE Plasma 5.18.5 to check out that KDE version and see what is different from the 5.8 release.

SwampRabbit wrote: Fri Jul 24, 2020 11:37 pm

richb wrote: Fri Jul 24, 2020 10:59 pm Yes the exact same opening of the MX Updater window happens with me when the updater icon changes from green to wireframe. It is not only JayM. This is not a VB install but a hardware install.

I would post my QSI but at the moment I am running Kubuntu 20.04.1 LTS, KDE Plasma 5.18.5 to check out that KDE version and see what is different from the 5.8 release.

You get a pass this time on the QSI Rich! I was just kidding with Jay anyway.

From the dev thread, apt-notifier is getting a lot of attention.

SwampRabbit wrote: Fri Jul 24, 2020 10:20 pm

kangburra wrote: Fri Jul 24, 2020 4:55 pm Since coming to MX Linux from whatever I was using before I have used this PPA https://launchpad.net/~fingerprint/+arc ... rprint-gui or at least added the apt file and imported the key. As I say it works properly in XFCE and works for Konsole commands but the lock screen requires multiple entries to get back in.

I will have a look for an MX fingerprint reader, I must admit when I find a way that works I use it until it stops working.

Thanks for the link.

By chance can you provide which version of Ubuntu you install from?

I don't see why we can't package it for our repos from the sources on Launchpad, it may help identify if something on the KDE beta2 is actually causing it.
Although it may be mute since this application is no longer maintained as well and that means fixes to this application won't come.

Several interesting things I noticed:

GNOME users: The package policykit-1-fingerprint-gui replaces GNOME's standard PolicyKit daemon (contained in package policykit-1-gnome) ... KDE SC users: The above instructions for GNOME users apply to you as well

Please note that Fingerprint GUI doesn't work with kdm and kscreensaver because of a bug in these applications

Check /var/log/auth.log for any clues. Fingerprint GUI is set up to run in debugging mode by default.

Does that log seem like it provides anything useful?

I hate to push you off to find another application, but its hard to recommend an application that isn't maintained, and has some known issues already. I'm sure fingerprint readers and applications have been talked about on the forums already.

Maybe dolphin_oracle, fehlix, or Adrian can look at this and potentially figure out why it works for Xfce and not KDE. That doesn't mean there's a fix, but its worth a shot.

asqwerth wrote: Sat Jul 25, 2020 5:29 am The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

asqwerth wrote: Sat Jul 25, 2020 5:29 am The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

tony37 wrote: Sat Jul 25, 2020 5:55 am One thing I noticed now that I installed the beta to hard drive is that /boot/efi is not 'locked', like in any other distro I've seen. Is this intentional? And funnily the 'changed' and 'opened' dates are set to 1/1/1970

dolphin_oracle wrote: Sat Jul 25, 2020 8:43 am

tony37 wrote: Sat Jul 25, 2020 5:55 am One thing I noticed now that I installed the beta to hard drive is that /boot/efi is not 'locked', like in any other distro I've seen. Is this intentional? And funnily the 'changed' and 'opened' dates are set to 1/1/1970

what do you mean "locked".?

its a fat32 partition.

UUID=6E90-22EA /boot/efi vfat defaults,noatime,dmask=0002,fmask=0113 0 0

tony37 wrote: Sat Jul 25, 2020 8:49 am In my fstab I have

Code: Select all

UUID=6E90-22EA /boot/efi vfat defaults,noatime,dmask=0002,fmask=0113 0 0

Normally I have umask=0077 there

dolphin_oracle wrote: Sat Jul 25, 2020 8:42 am

asqwerth wrote: Sat Jul 25, 2020 5:29 am The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

I've messed around with a lot of themes, and haven't seen this.

but it very possible. if a look-and-feel theme doesn't have something defined, then that thing doesn't change. asqwerth educated us on that with the icons.

chrispop99 wrote: Sat Jul 25, 2020 10:59 am The Package Installer still has an entry for the KDE desktop. Might attempting to install that cause a disaster? (I can test if needed.)

Chris

chrispop99 wrote: Sat Jul 25, 2020 2:40 pm Anyone deciding to multi-boot with MX-19.2 Xfce will only be able to determine which version to choose from GRUB if they remember the partition each version is installed to. Is there any way the name that appears in GRUB can have something added to it to indicate it is the KDE version?

Chris

PRETTY_NAME="MX 19.2 patito feo KDE"

tony37 wrote: Sat Jul 25, 2020 2:52 pm

chrispop99 wrote: Sat Jul 25, 2020 2:40 pm Anyone deciding to multi-boot with MX-19.2 Xfce will only be able to determine which version to choose from GRUB if they remember the partition each version is installed to. Is there any way the name that appears in GRUB can have something added to it to indicate it is the KDE version?

Chris

In /etc/lsb-release I changed the first line into

Code: Select all

PRETTY_NAME="MX 19.2 patito feo KDE"

Works after sudo update-grub

dolphin_oracle wrote: Sat Jul 25, 2020 3:24 pm no plans on the name. those names are used for things by various utilities in the operating system and in the package building. I prefer not to touch them.

GRUB_DISTRIBUTOR="$(unset PRETTY_NAME; (. /etc/lsb-release; echo ${PRETTY_NAME:?}) 2>/dev/null || echo Debian) KDE"

tony37 wrote: Sat Jul 25, 2020 11:43 am A tidbit about hibernation: on https://mxlinux.org/wiki/system/hibernate/ I can find: "Hibernation was removed from default locations in MX Linux such as the logout box because it proved highly unreliable in users’ tests."
But in KDE this is one of my logout options and it is the default setting for when the battery reaches the critical level (set to 5%). For me hibernation has never worked on this laptop, when I try the option in the beta my screen turns black for a few seconds and then returns to normal. When I use the method suggested on viewtopic.php?f=77&t=53742&p=583515 (so reconfiguring uswsusp) then hibernation does what it normally does on this pc: screen turns black and for minutes on end I can hear it is busy doing something and in the end I have to terminate this nonsense with the power button.
I know how to disable hibernate completely with systemd, but how to do this with sysvinit?

Stevo wrote: Sun Jul 26, 2020 1:50 am I get the same behavior no matter what the DE with a 5.6 kernel booted with sysvinit. The only way I can hibernate is to boot with systemd. You can revert to the standard Debian 4.19 kernel if it supports your hardware, which usually means it should be at least a year old by now.

tony37 wrote: Sun Jul 26, 2020 8:43 am Some options on the Welcome Screen aren't working: Wiki, Forums, Videos and (strangely) Contribute. So the ones opening a browser.

asqwerth wrote: Sun Jul 26, 2020 12:13 pm Thanks for the thorough testing, tony37!

leslie1017 wrote: Fri Jul 24, 2020 4:54 am I've deleted Libreoffice icon from Favourite menu several times, but once I reboot, it comes back here.

asqwerth wrote: Mon Jul 27, 2020 2:41 am Have you been changing application menu widgets, or switching between different global look and feel themes and choosing to use their default layouts?

leslie1017 wrote: Mon Jul 27, 2020 3:10 am

asqwerth wrote: Mon Jul 27, 2020 2:41 am Have you been changing application menu widgets, or switching between different global look and feel themes and choosing to use their default layouts?

Yes, I use another theme WhiteSur-dark downloaded from system setting

tony37 wrote: Mon Jul 27, 2020 5:03 am For me WhiteSur-dark doesn't put LIbreoffice in the menu favourites, also when I apply the desktop layout, reboot, or change the menu to another one.

tony37 wrote: Mon Jul 27, 2020 8:38 am When I install catfish (version 4.10-0.1~mx19+1), there are two serious problems:
- it goes into infinite loops (as /home/user/.wine/dosdevices/z:/home/user/.wine/dosdevices/z:/.....)
- it doesn't find recently created files

dolphin_oracle wrote: Mon Jul 27, 2020 8:44 am catfish requires you to update the locate database before it will find newer files.

dolphin_oracle wrote: Mon Jul 27, 2020 8:44 am also the "find" function in dolphin is pretty good.

asqwerth wrote: Mon Jul 27, 2020 5:21 am

tony37 wrote: Mon Jul 27, 2020 5:03 am For me WhiteSur-dark doesn't put LIbreoffice in the menu favourites, also when I apply the desktop layout, reboot, or change the menu to another one.

Noted. Then I don't know why LO keeps returning to his Favourites after he removes it.

Leslie1017, what are your Sessions settings? Are you starting with an empty session every login or do you keep logging in from a saved session?

leslie1017 wrote: Mon Jul 27, 2020 10:47 pm Where to look at this? I think even for starting with a saved session, it should be able to remove item from favourite menu.
Another information is I didn't install MX KDE from a clean home folder, I have kubuntu and opensuse installed and replaced by MX KDE, but I think there are some KDE settings in home folder remained.

JayM wrote: Mon Jul 27, 2020 11:44 pm

leslie1017 wrote: Mon Jul 27, 2020 10:47 pm Where to look at this? I think even for starting with a saved session, it should be able to remove item from favourite menu.
Another information is I didn't install MX KDE from a clean home folder, I have kubuntu and opensuse installed and replaced by MX KDE, but I think there are some KDE settings in home folder remained.

If that favorite was there when you saved the session it'll be back every time you log in using that session. That's how it's meant to work.
System Settings -> Workplace -> Startup and Shutdown -> Desktop Session. Select start with an empty session.

asqwerth wrote: Tue Jul 28, 2020 1:40 am With you using a pre-used /home with settings and configs from other distros, it's very hard to know if your issues are due to the Beta2 or your pre-existing settings.

I would suggest you make a separate clean install of the Beta2 and see if the issue still arises. Any other feedback should also be based on this new install. This is a Testing thread, for a release that is still in Beta phase.

leslie1017 wrote: Tue Jul 28, 2020 2:22 am My understanding that all these KDE distro (similar plasma version) uses same kde/plasma settings, unless MX KDE has some customization on kde/plasma. A fresh clean installation of MX will have no issue, as some one already tried. I'd like to do more investigation on why MX can read the favourite but cannot delete one, or a method to reset all KDE settings to default, just like a fresh install.

JayM wrote: Tue Jul 28, 2020 2:34 am The installer installs MX Linux. It's not a backup utility.

asqwerth wrote: Tue Jul 28, 2020 3:34 am This is just semantics, JayM and kangburra.

When you rename the home directory, it is just to tell the installer not to wipe it but to set it aside under a different name. Meanwhile, the installer will then create a fresh /home for the current installation being done.

Is renaming the old /home "backup"? Yes and no. Yes because you are setting it aside/preserving it for future use. No because often when people think of backup, they are thinking of a new copy being created. Here no new copy of the old partition is made.

JayM wrote: Tue Jul 28, 2020 4:06 am It's not just semantics. Words have meanings. Telling the installer to preserve /home isn't the same thing as performing a backup of /home. The latter gives you a second copy of /home's contents saved in another location in case something happens to the original.

dolphin_oracle wrote: Tue Jul 28, 2020 7:38 am we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

kangburra wrote: Tue Jul 28, 2020 8:39 am

dolphin_oracle wrote: Tue Jul 28, 2020 7:38 am we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

dolphin_oracle wrote: Tue Jul 28, 2020 8:52 am

kangburra wrote: Tue Jul 28, 2020 8:39 am

dolphin_oracle wrote: Tue Jul 28, 2020 7:38 am we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

was the file "simon.001" or just "simon"?

I think I see what may have happened, but would like to confirm those points.

kangburra wrote: Tue Jul 28, 2020 10:06 am

dolphin_oracle wrote: Tue Jul 28, 2020 8:52 am

kangburra wrote: Tue Jul 28, 2020 8:39 am

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

was the file "simon.001" or just "simon"?

I think I see what may have happened, but would like to confirm those points.

The old home was moved simon.001 and the file was simon.

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

dolphin_oracle wrote: Wed Jul 29, 2020 7:00 am

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

If you installed nvidia drivers before you changed kernel, depending on method used to install the kernel the drivers might not have rebuilt.

chrispop99 wrote: Wed Jul 29, 2020 6:56 am

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

That is more likely to be a problem with your hardware not being compatible with the 5.7 kernel.

Can you boot MX Linux AHS version (with Xfce), and successfully use the 5.7 kernel?

Chris

Gerson wrote: Wed Jul 29, 2020 7:15 am

dolphin_oracle wrote: Wed Jul 29, 2020 7:00 am

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

If you installed nvidia drivers before you changed kernel, depending on method used to install the kernel the drivers might not have rebuilt.

I don't use Nvidia, I use Intel and by the way, if I set from Tweak tab other Use Intel driver, when I restart and work the screen starts flashing and blinking, I have to go back to the default driver it has. My computer is from 2018 with solid disk and 4 gb RAM

chrispop99 wrote: Wed Jul 29, 2020 6:56 am

Gerson wrote: Wed Jul 29, 2020 6:51 am Both in KDE beta 1 and beta 2, I have installed a liquorix 5.7 kernel but although it starts and goes to the Login, after writing the password the screen remains black with the cursor active and doesn't advance. I have to turn off with the button and start with the 5.6 kernel and delete the 5.7. It doesn't work even if I start with Systemd.

That is more likely to be a problem with your hardware not being compatible with the 5.7 kernel.

Can you boot MX Linux AHS version (with Xfce), and successfully use the 5.7 kernel?

Chris

tony37 wrote: Thu Jul 23, 2020 7:10 am

tony37 wrote: Wed Jul 22, 2020 4:10 pm- .tiff files are set to be opened by Gwenview but that doesn't work (does work on version 19.12 though), GIMP and Okular can open them, so default mime setting should be changed there. Preview in Dolphin of .tiff files at first doesn't seem to work, but after the file has been opened by GIMP it does work. Weird.

When I install qt5-image-formats-plugins, Gwenview can open .tiff files and Dolphin previews them without problem.

Commit Log for Fri Jul 31 17:29:16 2020 -------- Dolphin Previews TIFF --- OK !


Installed the following packages:
qt5-image-formats-plugins (5.11.3-2)

tony37 wrote: Thu Jul 23, 2020 10:04 am

jeffreyC wrote: Thu Jul 23, 2020 9:43 am But apt-xapian-index is what makes Synaptic search work, and on my (several) MX installs it is turned on.

Synaptic search has been working fine for me on my Kubuntu without any apt-xapian-index. Maybe you mean libxapian30

tony37 wrote: Sat Aug 01, 2020 9:17 am Will there be another beta after this or a release candidate? or already the final version?

Adrian wrote: Sat Aug 01, 2020 9:30 am

tony37 wrote: Sat Aug 01, 2020 9:17 am Will there be another beta after this or a release candidate? or already the final version?

No more betas, the next one will be a RC.

JuhaT wrote: Sat Aug 01, 2020 12:14 pm I use the "Nvidia driver installer" in MX-tools and it installs fine but doesnt work when booting into systemd. I just get a scrambled prompt after the three dots and before the login page loads. I have to restart the computer to get out of it. I can boot into sysVinit just fine with the Nvidia driver..

I had this problem in beta 1 too and the suggestion to disable plymoth in boot options (add: disable splash) didnt help.I have now made a clean install to see if the problem was that I used the same home-folder from XFCE, but that wasnt the problem it seems.

I have no problem contiuning using Noveau driver since it is fast enough and works in systemd (I need to use systemd since my VPN software from OVPN doesnt work in sysVinit), I just wanted to report this for info. Maybe I am the only one having this problem with my hardware?

Code: Select all

System:
  Host: muka 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=b0f96b86-7912-40a0-93e1-be72166b325c ro quiet splash 
  init=/lib/systemd/systemd 
  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 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: 4061 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 4061 2: 3070 3: 3445 
  4: 4414 5: 3612 6: 3381 7: 4239 8: 3261 
  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: 7.49 GiB (0.2%) 
  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 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 
  ID-4: /dev/sdd 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-5: /dev/sde 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 
Partition:
  ID-1: / raw size: 29.34 GiB size: 28.76 GiB (98.00%) used: 7.16 GiB (24.9%) 
  fs: ext4 dev: /dev/sdb1 
  ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 334.2 MiB (0.2%) 
  fs: ext4 dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: 27.8 C gpu: nouveau temp: 32 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1363 
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: 244 Uptime: 11m Memory: 23.49 GiB used: 1.80 GiB (7.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 

dolphin_oracle wrote: Sat Aug 01, 2020 12:35 pm my suggestion is to boot into systemd mode first, install the nvidia drivers, and see if that improves the situation.

heywoodidaho wrote: Sun Aug 02, 2020 11:57 am This mornings update changed my background pic? Anyone else? no big deal,but odd.

srq2625 wrote: Sun Aug 02, 2020 12:08 pm

heywoodidaho wrote: Sun Aug 02, 2020 11:57 am This mornings update changed my background pic? Anyone else? no big deal,but odd.

Yep - me too.

And, the MX Update notifier is missing from my "task bar". I don't know when it went missing, but the quoted post made me look and I noticed it was not showing after having been logged in for about 20 minutes. For me, not a big deal as I do the updates from the command line but ... if I'm not the only person for whom it is missing, well this might be an issue.

fehlix wrote: Sun Aug 02, 2020 12:15 pm Will it show up when you either login/logout or run MX Updater (unhide icon) from the menu.

srq2625 wrote: Sun Aug 02, 2020 12:44 pm

fehlix wrote: Sun Aug 02, 2020 12:15 pm Will it show up when you either login/logout or run MX Updater (unhide icon) from the menu.

I can run the MX Updater and it will appear. I logged out and logged back in, after 20 minutes did not re-appear.

Like I said, not a major issue for me but it might be an issue for those that depend on this wonderful tool.

ETA: I looked at the KDE autostart list and it's there, but unchecked/disabled.

tony37 wrote: Mon Aug 03, 2020 8:26 am I also had my wallpaper changed to the default MX one after the latest update, the one with 'desktop-defaults-mx-kde:amd64 (20.07.05, 20.07.07)'.
I have a terrible bug in Kubuntu where at login (but only sometimes, so not reproducible) my wallpaper gets reset and my desktop icons are sorted alphabetically. No need to introduce this here.

CaputAlista wrote: Mon Aug 03, 2020 10:14 am Is it possible that kde plasma is more updated?
NORBERT PREINING · PUBLISHED 2020/07/30 · UPDATED 2020/07/30
Only a short update on the current status of my KDE/Plasma package for Debian sid and testing:Frameworks 5.72;plasma 5.19.4;Apps 20.04.3;Digikam 7.0.0;Ark CVE-2020-16116 fixed in version 20.04.3-1~np2 and use opensuse repositories.

https://www.preining.info/blog/2020/07/ ... 020-07-04/

CaputAlista wrote: Mon Aug 03, 2020 10:14 am Is it possible that kde plasma is more updated?
NORBERT PREINING · PUBLISHED 2020/07/30 · UPDATED 2020/07/30
Only a short update on the current status of my KDE/Plasma package for Debian sid and testing:Frameworks 5.72;plasma 5.19.4;Apps 20.04.3;Digikam 7.0.0;Ark CVE-2020-16116 fixed in version 20.04.3-1~np2 and use opensuse repositories.

https://www.preining.info/blog/2020/07/ ... 020-07-04/

tony37 wrote: Mon Aug 03, 2020 12:01 pm ... and in Manjaro KDE my system area more or less disappeared with the latest update.

dolphin_oracle wrote: Mon Aug 03, 2020 10:22 am

CaputAlista wrote: Mon Aug 03, 2020 10:14 am Is it possible that kde plasma is more updated?
NORBERT PREINING · PUBLISHED 2020/07/30 · UPDATED 2020/07/30
Only a short update on the current status of my KDE/Plasma package for Debian sid and testing:Frameworks 5.72;plasma 5.19.4;Apps 20.04.3;Digikam 7.0.0;Ark CVE-2020-16116 fixed in version 20.04.3-1~np2 and use opensuse repositories.

https://www.preining.info/blog/2020/07/ ... 020-07-04/

nope.

at the moment, due to the way Qt is supported in the debian repo, we are stuck with what we got.

JayM wrote: Wed Aug 05, 2020 4:54 am I have a feeling that MX-KDE's release is going to be announced pretty soon now

sunrat wrote: Wed Aug 05, 2020 5:50 am One of the devs said a few posts back there may be an RC version before the release.

tony37 wrote: Wed Aug 05, 2020 6:50 am @ leslie: are you still using your old /home config files?

leslie1017 wrote: Wed Aug 05, 2020 6:50 am Every time I click the "software updater" on system tray, the panel and desktop becomes not click able and requires plasmashell restart:
https://i.loli.net/2020/08/05/OK8YHEkxG6ilz1f.png

richb wrote: Wed Aug 05, 2020 7:01 am

leslie1017 wrote: Wed Aug 05, 2020 6:50 am Every time I click the "software updater" on system tray, the panel and desktop becomes not click able and requires plasmashell restart:
https://i.loli.net/2020/08/05/OK8YHEkxG6ilz1f.png

Moderator

Images added to post via hot links from other websites as they appear in a post will be limited to a 640 x 620 pixel size. The image at the image hosting site can be a full size image without restriction. Large images take up large areas of the post and thread space, are distracting and impede the flow of the thread.
You can post the link to the full image without the [img] tags, or use a link provided by the image site of a smaller size.

leslie1017 wrote: Wed Aug 05, 2020 7:09 am

richb wrote: Wed Aug 05, 2020 7:01 am

leslie1017 wrote: Wed Aug 05, 2020 6:50 am Every time I click the "software updater" on system tray, the panel and desktop becomes not click able and requires plasmashell restart:
https://i.loli.net/2020/08/05/OK8YHEkxG6ilz1f.png

Moderator

Images added to post via hot links from other websites as they appear in a post will be limited to a 640 x 620 pixel size. The image at the image hosting site can be a full size image without restriction. Large images take up large areas of the post and thread space, are distracting and impede the flow of the thread.
You can post the link to the full image without the [img] tags, or use a link provided by the image site of a smaller size.

Will find another img hosting site that providing smaller resolution

leslie1017 wrote: Wed Aug 05, 2020 6:52 am

tony37 wrote: Wed Aug 05, 2020 6:50 am @ leslie: are you still using your old /home config files?

Yes, this system is my daily use one, I can't switch my home folder, need lots of configuration for other software in my home directory

shmu26 wrote: Wed Aug 05, 2020 4:32 am I have Kubuntu 20.04 installed. I want to replace it with MX KDE Beta, and keep my home directory.
1 Is this tantamount to suicide?
...

Code: Select all

shmuel@shmuel-Kubuntu:~$ inxi -F
System:
  Host: shmuel-Kubuntu Kernel: 5.4.0-42-generic x86_64 bits: 64 
  Desktop: KDE Plasma 5.18.5 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
...

tony37 wrote: Wed Aug 05, 2020 8:08 am

leslie1017 wrote: Wed Aug 05, 2020 6:52 am

tony37 wrote: Wed Aug 05, 2020 6:50 am @ leslie: are you still using your old /home config files?

Yes, this system is my daily use one, I can't switch my home folder, need lots of configuration for other software in my home directory

It's very likely all your problems are caused by version conflicts in the config files, so you'll have to find a way to keep the config files you want and get rid of the other ones. But you'll have to reinstall MX KDE anyway as the beta apparently won't be upgraded, so what you can do then (there may be other options) is to transform your current /home folder into a separate data partition and have your /home folder (on the new install) on the same partition as /. Then you link the folders you want to use from your old /home to your new /home (you may have to delete some newly created folders first) and that's about it. And also put your data partition in /etc/fstab, so it is mounted at boot, for example at /mnt/data.

I suspect you're seeing a lot of problems because you have downgraded your Plasma from a newer version to 5.14, and the newer version will have put stuff in the config files that the older version isn't programmed to understand.

leslie1017 wrote: Wed Aug 05, 2020 9:16 am

tony37 wrote: Wed Aug 05, 2020 8:08 am

leslie1017 wrote: Wed Aug 05, 2020 6:52 am

Yes, this system is my daily use one, I can't switch my home folder, need lots of configuration for other software in my home directory

It's very likely all your problems are caused by version conflicts in the config files, so you'll have to find a way to keep the config files you want and get rid of the other ones. But you'll have to reinstall MX KDE anyway as the beta apparently won't be upgraded, so what you can do then (there may be other options) is to transform your current /home folder into a separate data partition and have your /home folder (on the new install) on the same partition as /. Then you link the folders you want to use from your old /home to your new /home (you may have to delete some newly created folders first) and that's about it. And also put your data partition in /etc/fstab, so it is mounted at boot, for example at /mnt/data.

I suspect you're seeing a lot of problems because you have downgraded your Plasma from a newer version to 5.14, and the newer version will have put stuff in the config files that the older version isn't programmed to understand.

Is there any plasma/kde log to look for what error occured?

leslie1017 wrote: Wed Aug 05, 2020 9:41 am This issue may not caused by reuse /home folder, I have installed MX KDE for about 1 month, and this issue appears today.

leslie1017 wrote: Wed Aug 05, 2020 9:16 am Is there any plasma/kde log to look for what error occured?

tony37 wrote: Wed Aug 05, 2020 12:22 pm One remark about apt-notifier: when I put it on 'Auto' in the system area settings, it always reverts to 'Shown' after reboot.

Adrian wrote: Wed Aug 05, 2020 4:59 pm It's in KDE Tray settings:
It's a KDE issue not an app one. However that option works fine for me.

You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

Adrian wrote: Wed Aug 05, 2020 4:59 pm You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

tony37 wrote: Thu Aug 06, 2020 3:24 am

Adrian wrote: Wed Aug 05, 2020 4:59 pm You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

when I looked there, there was a gigantic mass of \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ signs there, never seen such thing before
my file is 8 MB big because of this, I'm adding it in attachment as zip file

asqwerth wrote: Sun Aug 02, 2020 1:00 pm

srq2625 wrote: Sun Aug 02, 2020 12:44 pm

fehlix wrote: Sun Aug 02, 2020 12:15 pm Will it show up when you either login/logout or run MX Updater (unhide icon) from the menu.

I can run the MX Updater and it will appear. I logged out and logged back in, after 20 minutes did not re-appear.

Like I said, not a major issue for me but it might be an issue for those that depend on this wonderful tool.

ETA: I looked at the KDE autostart list and it's there, but unchecked/disabled.

What is your Plasma Systray setting for the displaying of apt-notifier (under tab 2)? Is it set at "auto" or "always" or "hidden"? It should be at "always". "Auto" will keep the icon hidden until there are updates available.

fehlix wrote: Thu Aug 06, 2020 5:40 am

tony37 wrote: Thu Aug 06, 2020 3:24 am

Adrian wrote: Wed Aug 05, 2020 4:59 pm You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

when I looked there, there was a gigantic mass of \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ signs there, never seen such thing before
my file is 8 MB big because of this, I'm adding it in attachment as zip file

OK, thanks for this findings. WIll be fixed shortly.

fehlix wrote: Thu Aug 06, 2020 10:16 am OK, pushed the fix for stopping plasma writing zero-terminated entries.

i_ri wrote: Fri Aug 07, 2020 8:15 pm Hello everyone
I may be a trailing zero.
hello \\\\0,
hello \\\\0,
hello \\\\0,
Checking the slashed file After the upgrade. Now no slashes. With wireframe empty.
diffout.png
Next trial when becomes wireframe filled.
Having added toolbar launchers on this machine that got slashes. it had all upgrades.
The other kde machine has not shown slashes. Now wireframe empty, it skipped an upgrade (?)(when this doubt popped up.) As default, it had zero changes to toolbar or anything else.

i_ri wrote: Sat Aug 08, 2020 3:35 am does anyone else always put an up button in dolphin? or just me. that's a do after installing list. ... (?)

i_ri wrote: Sat Aug 08, 2020 3:35 am does anyone else always put an up button in dolphin? or just me. that's a do after installing list. ... (?)

sunrat wrote: Sat Aug 08, 2020 7:31 am That's kinda redundant when you can click on the path in the top bar and get clickable breadcrumbs.

[General]
ShowFullPath=true

tony37 wrote: Sat Aug 08, 2020 9:34 am

sunrat wrote: Sat Aug 08, 2020 7:31 am That's kinda redundant when you can click on the path in the top bar and get clickable breadcrumbs.

Maybe, but there's one thing: 'Show full path inside location bar' is disabled by default.

sunrat wrote: Sat Aug 08, 2020 10:32 am

tony37 wrote: Sat Aug 08, 2020 9:34 am

sunrat wrote: Sat Aug 08, 2020 7:31 am That's kinda redundant when you can click on the path in the top bar and get clickable breadcrumbs.

Maybe, but there's one thing: 'Show full path inside location bar' is disabled by default.

So you have to click on the little arrow at left of path ">" to get a dropdown of the full tree to click on.