MX-19.2 KDE Beta 1 feedback thread

Message
Author
User avatar
seaken64
Posts: 819
Joined: Wed Jan 02, 2019 1:43 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#201 Post by seaken64 »

@Gerson,

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

Seaken64
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K

User avatar
seaken64
Posts: 819
Joined: Wed Jan 02, 2019 1:43 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#202 Post by seaken64 »

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

Seaken64
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K

User avatar
Gerson
Posts: 879
Joined: Sun Nov 12, 2017 9:58 am

Re: MX-19.2 KDE Beta 1 feedback thread

#203 Post by Gerson »

seaken64 wrote: Sun Jul 12, 2020 2:12 pm @Gerson,

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

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

User avatar
Laurentius
Posts: 102
Joined: Sat Jan 20, 2018 8:44 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#204 Post by Laurentius »

I did a frugal_persist on the netbook I mentioned before (the first one, the other does not boot with this iso)

Code: Select all

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

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

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

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

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

EDIT: after resume from suspend touchpad works again and I could close the note window
Last edited by Laurentius on Sun Jul 12, 2020 4:07 pm, edited 1 time in total.

User avatar
Gerson
Posts: 879
Joined: Sun Nov 12, 2017 9:58 am

Re: MX-19.2 KDE Beta 1 feedback thread

#205 Post by Gerson »

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

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

User avatar
seaken64
Posts: 819
Joined: Wed Jan 02, 2019 1:43 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#206 Post by seaken64 »

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

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

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

Seaken64
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K

JuhaT
Posts: 34
Joined: Tue Apr 21, 2020 11:07 am

Re: MX-19.2 KDE Beta 1 feedback thread

#207 Post by JuhaT »

I have been running this beta in VMware box and since it worked flawlessy there I decided to install it on my desktop.
I have a separate Home partition so I chose not to modify it during install. I have MX on a separate SSD and Windows 10 on another. This is my experience.

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

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

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



I dont know if it is necessary but here are info

Code: Select all


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

User avatar
baldyeti
Posts: 717
Joined: Sat Dec 05, 2009 3:37 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#208 Post by baldyeti »

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

User avatar
chrispop99
Global Moderator
Posts: 3350
Joined: Tue Jan 27, 2009 2:07 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#209 Post by chrispop99 »

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

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

User avatar
Sparky
Posts: 1205
Joined: Sun Dec 23, 2018 6:07 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#210 Post by Sparky »

Okular is the default PDF opener in KDE, it's on my install as well.
MX Linux Asus F552, 12GB RAM, 500GB WD SSD MX19.2
Dell Inspiron 7559 16GB RAM 1X 256GB SSD & 1TB SSD MX KDE 21.1 & Windows 11
Mini Tower PC 2X 256GB SSD MX KDE21.1

Locked

Return to “General”