Page 1 of 1

MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 10:42 am
by dolphin_oracle
Don't forget to post your quick-system-info and any logs that might be applicable!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 12:31 pm
by bbfuller
That's it downloaded and installed with no difficulties experienced.

I 'm especially pleased to see that in the blog it is shown as being upgradeable to final release as I do want to install it on a "regular use" machine.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 12:57 pm
by kangburra
When installing at command line I get this error

Code: Select all

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
but the commands work successfully.

To get korganiser working I had to

Code: Select all

$ sudo rm -r ~/.local/share/akonadi/
and reboot.

Otherwise no issues so far.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 2:22 pm
by bbfuller
I've just installed KMail from the package manager, on the first run there was a complaint about "parent process" not found.

Trying to create an account from the menu system afterwards tells me that:

"Could not start the account wizard. Please make sure you have the AccountWizard properly installed"..

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 2:56 pm
by dolphin_oracle
bbfuller wrote: Sun Aug 09, 2020 2:22 pm I've just installed KMail from the package manager, on the first run there was a complaint about "parent process" not found.

Trying to create an account from the menu system afterwards tells me that:

"Could not start the account wizard. Please make sure you have the AccountWizard properly installed"..
so did you install accountwizard?

also I'm relatively certain the version of kmail in debian (and consequently what we have available) won't work with gmail OOTB, in case that matters.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 4:14 pm
by bbfuller
Two points there.

GMail is not the only email provider out there. Some distributions are offering the newest KMail which certainly does work with GMail.

I do now see the "accountwizard" in the package manager, but surely, if KMail is dependent on it to set up an account it ought to be brought in as a dependency.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 4:22 pm
by SwampRabbit
bbfuller wrote: Sun Aug 09, 2020 4:14 pm Some distributions are offering the newest KMail which certainly does work with GMail.
Do you know which distros based on Debian 10 (Buster) provide the newest KMail?
If it would be helpful to know this.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 5:51 pm
by m_pav
bbfuller wrote: Sun Aug 09, 2020 4:14 pmsurely, if KMail is dependent on it to set up an account it ought to be brought in as a dependency.
Kmail is part of a suite of apps and in and of itself, kmail does not list accountwizard as a dependency, instead, accountwizard is listed with the recommends.

Usually the command line apt installer will try to make the best decisions and install selected recommends, but if apt-get is used, it will do only that which it's told to do. By default, I believe package manager uses apt so either the logic didn't pick up accountwizard as necessary to install, or you've stumbled on a bug. I would test, but I'm on crappy internet and trying to upload an ISO which has failed 3 times already, so hopefully others can assist with a test, or you might want to employ the command line and repeat your actions while watching what is happening in the background. You'll have to reverse all you've done first.

Code: Select all

sudo apt remove --purge kmail
sudo apt autoremove --purge
sudo apt install kmail
sudo apt install kmail accountwizard
If the third command pulls in accountwizard, then this shows we might need to look at MXPI, if not, then it's functioning as it should.

The KDE developers and packagers are responsible for decisions related to dependencies, so they are the way they are. I believe the KDE Desktop metapackages will pull in all the necessary recommends, so as far as KDE/Debian are concerned, this may be sufficiently catered for within the metapackages.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 6:50 pm
by bbfuller
I've just executed those four commands in a row.

Code: Select all

sudo apt remove --purge kmail
lists all the packages that went in from the graphical package manager as far as I can see. I can list the packages if you wish to see them.

Code: Select all

sudo apt autoremove --purge
deletes all of those packages.

An extra command:

Code: Select all

sudo apt remove --purge accountwizard
Removes the accountwizard package which following the earlier advice I'd already found and installed.

Code: Select all

sudo apt install kmail
Installs all of the packages removed with commands one and two.

Code: Select all

sudo apt install kmail accountwizard
Installs one package the account wizard.

It would be OK if that was all the problem there was, however, when trying to create an account with accountwizard installed, the installer complains because it can't find kwallet and instead offers to store the password insecurely.

Beyond that, I understand from what has been said above that KMail probably won't work with GMail, something that I can confirm. It fails with a message "KMail resource GMail is broken".

I guess from what was said above that it is due to an older version of KMail being packaged by your "upstream distribution". Is that the correct terminology? I'm not sure that as a user I'd appreciated that. I'm not sure that I could really be expected to know the antecedents of the distributions where it does work. The cases I'm referring to though are on Mageia and Manjaro

I notice that removing and reinstalling those packages can't have removed the KMail configuration folder because it didn't offer the "first run" wizard after reinstall. I also don't know if the next problem might be happening because there is some hangover from the previous attempts to add an account. I'll see if I can find and delete that folder tomorrow. However:

Trying to add a Yahoo account to KMail results in the same message about "resource being broken" as was the case for the GMail account non-creation.

Time for bed here!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 9:11 pm
by sunrat
m_pav wrote: Sun Aug 09, 2020 5:51 pm
bbfuller wrote: Sun Aug 09, 2020 4:14 pmsurely, if KMail is dependent on it to set up an account it ought to be brought in as a dependency.
Kmail is part of a suite of apps and in and of itself, kmail does not list accountwizard as a dependency, instead, accountwizard is listed with the recommends.
I've never had a satisfactory answer to why MX does not install recommends. Debian does by default now. I get that antiX wants to stay slim, but doesn't make sense to me for MX. There are regularly issues on the forums which are only because recommends are not installed.
I suggest MX-KDE RC2 tests whether recommends can be default installed.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 9:39 pm
by SwampRabbit
sunrat wrote: Sun Aug 09, 2020 9:11 pm There are regularly issues on the forums which are only because recommends are not installed.
That’s a stretch of a comment I think.

One minute someone is complaining something is bloated, the next it’s that stuff isn’t installed. The flip flopping, it gets old fast.

Let’s stick to suggesting dependencies that have been properly identified as needed to give the the majority of users of the KDE version what they need OOTB... leave the rest off the table.

As far as changes to what’s installed that’s up to Adrian and dolphin_oracle.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 9:51 pm
by m_pav
sunrat wrote: Sun Aug 09, 2020 9:11 pmI suggest MX-KDE RC2 tests whether recommends can be default installed.
I think you might be missing an important point. MX uses Debian, so the rules set out in the Debian repos are inherently adopted as-is into our builds. This is not a Debian vs MX issue, this is a Debian default condition. If it's done that way through Debian, then it will go the same with MX, it's as simple as that. Sometimes, we intervene where a flaw is discovered or awhen a work-around is needed, but we do not change the Debian defaults because we are not Debian, we are Debian compatible.

Of the 58,000+ packages available in the Debian repos, which ones would you like us to test? All of them? We provide public Beta releases and Release Candidate updates where people like you are invited to test not only the form and function of the build as a whole, but also how your own preferred packages operate with this build and report back on them in a respectful and helpful manner.

We only ask for RESPECTFUL dialogues from those who wish to participate in testing these pre-release builds, that they show a willingness to participate in the proper TESTING and reporting on our our pre-release builds. If you're not willing to do that, then testing is simply not for you, you are in the wrong place and in the wrong mindset.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 10:58 pm
by sunrat
@m_pav - Not sure why you say I'm being disrespectful. I make a suggestion which I believe may improve MX and what better time for this version when it is still in testing phase.
You're mistaken about recommends defaults by the way. I just did a test install of Kmail on Buster/KDE and it pulls in accountwizard. MX has a file /etc/apt/apt.conf which alters the Debian default.

Code: Select all

// Recommends are as of now still abused in many packages
APT::Install-Recommends "0";
APT::Install-Suggests "0";
Debian did have that as default a long time ago as packagers were abusing it. It's much more controlled now.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 11:26 pm
by dolphin_oracle
sunrat wrote: Sun Aug 09, 2020 10:58 pm @m_pav - Not sure why you say I'm being disrespectful. I make a suggestion which I believe may improve MX and what better time for this version when it is still in testing phase.
You're mistaken about recommends defaults by the way. I just did a test install of Kmail on Buster/KDE and it pulls in accountwizard. MX has a file /etc/apt/apt.conf which alters the Debian default.

Code: Select all

// Recommends are as of now still abused in many packages
APT::Install-Recommends "0";
APT::Install-Suggests "0";
Debian did have that as default a long time ago as packagers were abusing it. It's much more controlled now.
Thanks for.the suggestion.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 11:32 pm
by SwampRabbit
First lets keep this to the RC, if accountwizard needs added, it can be added... we don't need to beat a dead horse here.

Second...
sunrat wrote: Sun Aug 09, 2020 10:58 pm // Recommends are as of now still abused in many packages
...
Debian did have that as default a long time ago as packagers were abusing it. It's much more controlled now.
Note the bold and underlined you referenced.... "PACAKGES" meaning the actual package either from the actual upstream developer or Debian package maintainers... not the MX Package Maintainers (packagers). Our packages don't affect Debian packages upstream at all.

Its not controlled at all at the Debian level, folks have no clue how much worthless crap we have saved ya'll from having to have installed on your systems. How about how Stevo spends tons of time to make sure our Chromium does hardware accelerated video?

I mean I can start leaving systemd, mono, dozens of other stuff as mandatory dependencies if you want?

Lets stop making assumptions.

Let's stick to clearly articulating that a dependency is needed or an application would be good to have and exactly why. This is an RC1 release after all, if we missed accountwizard, it might because those that needed KMail didn't test it enough in the Betas.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sun Aug 09, 2020 11:35 pm
by dolphin_oracle
SwampRabbit wrote: Sun Aug 09, 2020 11:32 pm First lets keep this to the RC, if accountwizard needs added, it can be added... we don't need to beat a dead horse here.

Second...
sunrat wrote: Sun Aug 09, 2020 10:58 pm // Recommends are as of now still abused in many packages
...
Debian did have that as default a long time ago as packagers were abusing it. It's much more controlled now.
Note the bold and underlined you referenced.... "PACAKGES" meaning the actual package either from the actual upstream developer or Debian package maintainers... not the MX Package Maintainers (packagers). Our packages don't affect Debian packages upstream at all.

Its not controlled at all at the Debian level, folks have no clue how much worthless crap we have saved ya'll from having to have installed on your systems. How about how Stevo spends tons of time to make sure our Chromium does hardware accelerated video?

I mean I can start leaving systemd, mono, dozens of other stuff as mandatory dependencies if you want?

Lets stop making assumptions.

Let's stick to clearly articulating that a dependency is needed or an application would be good to have and exactly why. This is an RC1 release after all, if we missed accountwizard, it might because those that needed KMail didn't test it enough in the Betas.
we decided to not install kmail by default because the version of kmail in the debian repo doesn't actually work with several mail services, including gmail.

the recommends vs. depends thing is a long standing point (debian installs recommends as if they are depends by default, and we don't), and it crops up from time to time, the issue is just very obvious in kmail's case.

moving along now...

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:09 am
by JayM
Don't forget that MX Package Installer, which is the recommended way to install packages anyway, still has the checkbox to also install recommends on a case-by-case basis on the stable, test repo and Debian backports tabs. I usually select it then review what will be installed prior to clicking continue, then if it wants to install a bunch of junk I don't want I click cancel and start over, this time not checking the recommends box. Or if I install something and it doesn't work as expected due to a missing recommend I just reinstall it, this time checking the recommends checkbox.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:16 am
by Stevo
We do have several KDE programs in testing that are quite a bit newer than the Buster version, or very near, but we don't get much feedback, if any at all, so they're still there. I've taken to just sending Krita directly to main, since it doesn't affect any other programs. Others that still need testers are K3B, digiKam, and Marble--it would be nice to have those available in the repo so we could mention those along with the KDE edition final release.

I'll look at Kmail to see if it can also be updated, but I get a feeling that it's too closely tied to a newer Plasma. But we ship T-bird anyway--why the fuss about Kmail?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:47 am
by JayM
I can't help with K3B or digiKam 'cause I don't have an optical drive or digital camera but I installed

Code: Select all

2020-08-10  12:38:21  install  plasma-marble           amd64  <none>         4:20.04.1-0.1~mx19+1
2020-08-10  12:38:20  install  marble-qt               amd64  <none>         4:20.04.1-0.1~mx19+1
2020-08-10  12:38:20  install  marble-plugins          amd64  <none>         4:20.04.1-0.1~mx19+1
2020-08-10  12:38:20  install  marble-maps             amd64  <none>         4:20.04.1-0.1~mx19+1
2020-08-10  12:38:20  install  marble                  amd64  <none>         4:20.04.1-0.1~mx19+1
from the test repo and briefly tested both Marble and KDE Marble. All maps work, zooming in and out works, changing location view works. I didn't try the to and from directions part yet but so far nothing appears to be broken.

Code: Select all

System:
  Host: mx Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=3d06c757-cfee-4ee9-9e35-0ee4203bd383 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: 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: 49.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Unknown 
CPU:
  Topology: Dual Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64 
  type: MCP arch: Zen family: 17 (23) model-id: 11 (17) stepping: N/A 
  microcode: 6000626 L2 cache: 1024 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 7984 
  Speed: 1996 MHz min/max: N/A Core speeds (MHz): 1: 1996 2: 1996 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: 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: 1896x965_vbox~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.7 compat-v: 3.1 
  direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell 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: 20.00 GiB used: 7.01 GiB (35.1%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.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: 17.97 GiB size: 17.56 GiB (97.73%) used: 7.01 GiB (39.9%) 
  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: 171 Uptime: 43m Memory: 3.85 GiB used: 644.5 MiB (16.4%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
  running in: quick-system-in inxi: 3.0.36 
Hopefully someone who's done a bare metal install on a system with an optical drive burner and a spare blank disk can install and test K3B from the test repo.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 1:54 am
by andyprough
k3b 19.04.2 is running well for me. I burned a couple of antiX ISO's tonight on DVD-R's using an external usb3-connected dvd burner. Quick and accurate as usual. Good project.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 3:17 am
by baldyeti
sunrat wrote: Sun Aug 09, 2020 9:11 pm I get that antiX wants to stay slim, but doesn't make sense to me for MX.
this++

Mentioned before, e.g. here. Correct me if i am wrong but i do not think installing from the "popular packages" section has the "install recommends" check-box.

Anyway, congrats for the plasma-flavoured MX

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 3:33 am
by JayM
Popular Applications does things differently. It installs things using scripts found in /usr/share/mx-packageinstaller-pkglist/ if I'm not mistaken. Those scripts in turn contain the apt commands. The stable, test and backports repos' tabs run the apt commands directly, in the case of the test and Debian backports repos first temporarily enabling those repos.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 4:01 am
by bbfuller
Stevo wrote: Mon Aug 10, 2020 12:16 am I'll look at Kmail to see if it can also be updated, but I get a feeling that it's too closely tied to a newer Plasma. But we ship T-bird anyway--why the fuss about Kmail?
I hadn't realised that Debian stayed that much behind. One of the instances where KMail just works runs Plasma 5.15.4 and KMail 5.11.0.

MX rc1 of course is on 5.14.5 and 5.9.3

As the person who started this friction can I just say that I like to run two email programs. One with my current email addresses (Thunderbird) and one with legacy addresses that I've never got round to fully abandoning. If there was an alternative to KMail that dealt with HTML mail decently I personally wouldn't worry about KMail. Or if I could easily run two instances of Thunderbird, which it doesn't support.

Without trying to be antagonistic or aggressive I'd just like to add that it seems an odd strategy to bring out a KDE based distribution where some of the KDE apps don't work. Surely the idea behind KDE being that you buy into an integrated environment where Mail integrates with Calendar and doubtless other examples as well.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 4:58 am
by kangburra
bbfuller wrote: Mon Aug 10, 2020 4:01 am
Stevo wrote: Mon Aug 10, 2020 12:16 am I'll look at Kmail to see if it can also be updated, but I get a feeling that it's too closely tied to a newer Plasma. But we ship T-bird anyway--why the fuss about Kmail?
I hadn't realised that Debian stayed that much behind. One of the instances where KMail just works runs Plasma 5.15.4 and KMail 5.11.0.

MX rc1 of course is on 5.14.5 and 5.9.3

As the person who started this friction can I just say that I like to run two email programs. One with my current email addresses (Thunderbird) and one with legacy addresses that I've never got round to fully abandoning. If there was an alternative to KMail that dealt with HTML mail decently I personally wouldn't worry about KMail. Or if I could easily run two instances of Thunderbird, which it doesn't support.

Without trying to be antagonistic or aggressive I'd just like to add that it seems an odd strategy to bring out a KDE based distribution where some of the KDE apps don't work. Surely the idea behind KDE being that you buy into an integrated environment where Mail integrates with Calendar and doubtless other examples as well.
I don't see the need to change everything to include recommded packages, many times I go to the command line to exclude them on other systems, maybe with the next release of kmail (the one with the HTML colour fix) we can include the account wizard.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 5:15 am
by bbfuller
It's not just the account wizard though is it.

It's the current KMail's inability to work with GMail and apparently from my attempts last evening, its inability to work with Yahoo Mail even with the "accountwizard" added manually.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 5:30 am
by tony37
bbfuller wrote: Mon Aug 10, 2020 5:15 am It's not just the account wizard though is it.

It's the current KMail's inability to work with GMail and apparently from my attempts last evening, its inability to work with Yahoo Mail even with the "accountwizard" added manually.
I also had KMail not connecting to GMail on a more recent distro (Kubuntu 20.04). It used to work but at some point it stopped working.

Btw, there are still some leftover config files from not-installed Akonadi packages on RC1.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 5:45 am
by bbfuller
The KMail developer used to have a blog post where they apologised for KMail not working with GMail due to the correct procedure for linking the two not having been followed. That post disappeared sometime in the last six months and recent versions of KMail started working with GMail again.

Never had any trouble getting it to work with Yahoo before though.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 6:34 am
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

Hello dolphin_oracle and everyone
From dd write iso Image install
MX 19ahs KDE_RC on

Code: Select all

System:    Host: heap8440p Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 
           wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 8440p v: N/A serial: <root required> Chassis: type: 10 
           serial: <root required> 
           Mobo: Hewlett-Packard model: 172A v: KBC Version 30.35 serial: <root required> BIOS: Hewlett-Packard 
           v: 68CCU Ver. F.60 date: 11/11/2015 
Battery:   ID-1: BAT0 charge: 46.8 Wh condition: 46.8/46.8 Wh (100%) volts: 12.5/11.1 model: Hewlett-Packard Primary 
           type: Li-ion serial: 01595 2011/08/15 status: Full 
           Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 serial: 4004-13-87-a8-bd 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP arch: Nehalem rev: 5 L2 cache: 3072 KiB 
           bogomips: 21283 
           Speed: 2337 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 2337 2: 1972 3: 2605 4: 2314 
           Flags: acpi aes aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 
           dtherm dts est flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae 
           pat pbe pcid pclmulqdq pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 
           ssse3 stibp syscall tm tm2 tsc vme xtopology xtpr 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1600x900~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k port: 5020 
           bus ID: 00:19.0 chip ID: 8086:10ea 
           Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 5000 bus ID: 43:00.0 chip ID: 8086:4239 
Drives:    Local Storage: total: 14.91 GiB used: 6.57 GiB (44.1%) 
           ID-1: /dev/sda type: USB vendor: SanDisk model: Cruzer Glide size: 14.91 GiB speed: <unknown> 
           serial: 2006107973054D5273CF rev: 1.00 scheme: MBR 
Weather:   Message: No weather data found. Internet connection working? 
Info:      Processes: 188 Uptime: 12m Memory: 3.65 GiB used: 539.6 MiB (14.5%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: konsole inxi: 3.0.36 
Packages: 2348 (dpkg)
 Private  +   Shared  =  RAM used       Program

 92.0 KiB +  21.5 KiB = 113.5 KiB       start_kdeinit
176.0 KiB +  32.0 KiB = 208.0 KiB       acpid
188.0 KiB +  36.0 KiB = 224.0 KiB       acpi_fakekeyd
220.0 KiB +  28.5 KiB = 248.5 KiB       startkde
292.0 KiB +  51.5 KiB = 343.5 KiB       init
312.0 KiB +  71.0 KiB = 383.0 KiB       cron
436.0 KiB +  27.0 KiB = 463.0 KiB       mdadm
484.0 KiB +  39.0 KiB = 523.0 KiB       rpc.idmapd
588.0 KiB +  40.5 KiB = 628.5 KiB       ksysguardd
624.0 KiB +  70.0 KiB = 694.0 KiB       cgmanager
692.0 KiB +  36.0 KiB = 728.0 KiB       ssh-agent
540.0 KiB + 191.5 KiB = 731.5 KiB       rpcbind
516.0 KiB + 269.0 KiB = 785.0 KiB       kwrapper5
660.0 KiB + 237.5 KiB = 897.5 KiB       dconf-service
772.0 KiB + 211.0 KiB = 983.0 KiB       dbus-launch (2)
284.0 KiB + 720.0 KiB =   1.0 MiB       saned (2)
872.0 KiB + 178.0 KiB =   1.0 MiB       rpc.statd
432.0 KiB + 627.5 KiB =   1.0 MiB       avahi-daemon (2)
808.0 KiB + 367.0 KiB =   1.1 MiB       getty (6)
  1.1 MiB + 247.5 KiB =   1.4 MiB       sudo
  1.3 MiB +  67.5 KiB =   1.4 MiB       smartd
896.0 KiB + 550.0 KiB =   1.4 MiB       dbus
  1.3 MiB + 217.0 KiB =   1.5 MiB       ntpd
  1.0 MiB + 578.5 KiB =   1.6 MiB       at-spi-bus-launcher
  1.4 MiB + 392.5 KiB =   1.8 MiB       gvfsd
  1.7 MiB + 275.0 KiB =   1.9 MiB       obexd
332.0 KiB +   1.7 MiB =   2.1 MiB       kdeinit5
  2.1 MiB + 117.5 KiB =   2.2 MiB       rsyslogd
  1.7 MiB + 604.5 KiB =   2.3 MiB       sddm
  1.7 MiB + 714.5 KiB =   2.4 MiB       sddm-helper
  1.9 MiB + 616.5 KiB =   2.5 MiB       cupsd
  2.1 MiB + 571.0 KiB =   2.6 MiB       upowerd
  1.8 MiB + 993.5 KiB =   2.8 MiB       cups-browsed
  2.5 MiB + 452.0 KiB =   2.9 MiB       dhclient
  2.8 MiB + 248.0 KiB =   3.0 MiB       systemd-udevd
  2.1 MiB + 978.0 KiB =   3.0 MiB       xembedsniproxy
  2.1 MiB + 956.0 KiB =   3.1 MiB       kscreen_backend_launcher
  3.2 MiB +  26.0 KiB =   3.2 MiB       haveged
  2.3 MiB +   1.0 MiB =   3.3 MiB       gmenudbusmenuproxy
  3.0 MiB + 469.0 KiB =   3.5 MiB       systemd-logind
  3.0 MiB + 692.5 KiB =   3.7 MiB       dbus-daemon (4)
  3.3 MiB + 543.5 KiB =   3.8 MiB       gvfsd-fuse
  3.3 MiB + 510.0 KiB =   3.8 MiB       polkitd
736.0 KiB +   3.4 MiB =   4.1 MiB       file.so (2)
  2.9 MiB +   1.2 MiB =   4.1 MiB       bash (2)
  3.6 MiB + 749.5 KiB =   4.3 MiB       wpa_supplicant
  4.3 MiB + 599.0 KiB =   4.9 MiB       ModemManager
  4.4 MiB + 921.5 KiB =   5.3 MiB       colord
  3.8 MiB +   1.9 MiB =   5.7 MiB       kactivitymanagerd
  4.3 MiB +   2.3 MiB =   6.6 MiB       klauncher
  4.5 MiB +   2.1 MiB =   6.6 MiB       kuiserver5
  5.6 MiB +   1.4 MiB =   7.0 MiB       NetworkManager
  4.9 MiB +   2.3 MiB =   7.2 MiB       polkit-kde-authentication-agent-1
  5.3 MiB +   1.9 MiB =   7.2 MiB       conky
  5.3 MiB +   2.1 MiB =   7.3 MiB       kglobalaccel5
  6.7 MiB + 932.5 KiB =   7.6 MiB       udisksd
  6.4 MiB +   2.1 MiB =   8.4 MiB       kaccess
  5.5 MiB +   3.0 MiB =   8.5 MiB       org_kde_powerdevil
  7.0 MiB +   3.3 MiB =  10.3 MiB       kdeconnectd
  7.4 MiB +   3.0 MiB =  10.4 MiB       ksmserver
 11.2 MiB +   1.6 MiB =  12.8 MiB       python3.7
 13.0 MiB +   1.2 MiB =  14.1 MiB       pulseaudio
 14.0 MiB +   1.6 MiB =  15.6 MiB       kwalletd
 12.8 MiB +   5.4 MiB =  18.2 MiB       yakuake
 11.6 MiB +   7.2 MiB =  18.8 MiB       konsole
 15.3 MiB +   7.1 MiB =  22.3 MiB       krunner
 22.6 MiB +   3.1 MiB =  25.7 MiB       Xorg
 21.8 MiB +   4.2 MiB =  26.0 MiB       python2.7
 32.9 MiB +  11.6 MiB =  44.5 MiB       kded5
 40.7 MiB +   7.1 MiB =  47.8 MiB       kwin_x11
122.4 MiB +  13.9 MiB = 136.3 MiB       plasmashell
---------------------------------
                        570.8 MiB
=================
keremxoidrc@heap8440p:~
$ hello everyone          
.mem at start with auto wlan0

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:14 am
by Gerson
The .featherpad and .geany folders still appear in the /home

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:16 am
by richb
Gerson wrote: Mon Aug 10, 2020 8:14 am The .featherpad and .geany folders still appear in the /home
I do not see them.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:20 am
by chrispop99
Gerson wrote: Mon Aug 10, 2020 8:14 am The .featherpad and .geany folders still appear in the /home
Not here.

Did you preserve your home folder?

Chris

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:21 am
by JayM
Gerson wrote: Mon Aug 10, 2020 8:14 am The .featherpad and .geany folders still appear in the /home
Not in my freshly installed MX-KDE RC1 in a VirtualBox VM, nor are there any such folders in my host OS, MX-19.2 AHS, either.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:27 am
by dolphin_oracle
richb wrote: Mon Aug 10, 2020 8:16 am
Gerson wrote: Mon Aug 10, 2020 8:14 am The .featherpad and .geany folders still appear in the /home
I do not see them.
its actually ~/.config/featherpad and ~/.config/geany

its not a bug in the sense that we didn't expect them. we are only maintaining one desktop-defaults-mx-applications package, and thats where those are stored. there is some overlap in apps between KDE and XFCE versions of the iso.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:42 am
by tony37
richb wrote: Mon Aug 10, 2020 8:16 am
Gerson wrote: Mon Aug 10, 2020 8:14 am The .featherpad and .geany folders still appear in the /home
I do not see them.
I don't see them either in my /home directory, but I've noticed there are featherpad and geany folders in /etc/skel/.config

edit: I'm only now reading the latest replies

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:56 am
by paul1149
Stevo wrote: Mon Aug 10, 2020 12:16 amwe ship T-bird anyway--why the fuss about Kmail?
In my preliminary testing I really liked the look and feel of kmail. I was sorry to see it unable to connect properly to gmail and vivaldi.net mail. I see that v. 5.18 is out but not in the repositories, so maybe when that filters down all will be well.

I then went to T-bird and it is doing fine, especially with the birdtray adjunct prog. I will give the new kmail a spin when it comes out, but at the same time the new T-bird is already out, though not yet released to repositories, and it is a major upgrade. Encryption is built in and there are new themes, for starters. So I will be looking at both progs.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 9:57 am
by i_ri
featherpad and geany are in /Home/.config

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 9:58 am
by andyprough
bbfuller wrote: Mon Aug 10, 2020 4:01 amWithout trying to be antagonistic or aggressive I'd just like to add that it seems an odd strategy to bring out a KDE based distribution where some of the KDE apps don't work. Surely the idea behind KDE being that you buy into an integrated environment where Mail integrates with Calendar and doubtless other examples as well.
I used suse/opensuse for most of the past 22 years, which was the primary distro that defaulted to KDE during that time, and suse was one of the primary supporters of the KDE project during that time. I can't recall suse using kmail as the default email handler over Thunderbird anytime in the past dozen years, simply because kmail is not a well maintained program and Thunderbird is. Back around 2003-2004, suse was defaulting to kmail, but that was a long time ago on a version of KDE that no longer exists. Maybe kubuntu is defaulting to kmail, I don't know, I never used any ubuntu distros, but if they were defaulting to kmail it would not have been a very good choice during many of the years when kmail was basically broken.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 10:09 am
by SwampRabbit
paul1149 wrote: Mon Aug 10, 2020 8:56 am In my preliminary testing I really liked the look and feel of kmail. I was sorry to see it unable to connect properly to gmail and vivaldi.net mail. I see that v. 5.18 is out but not in the repositories, so maybe when that filters down all will be well.
there is no kmail 5.18, also kmail is a mess, don't believe me? look at all the red and yellow here
https://repology.org/project/kmail/versions
This is why there are issues across all distros as mentioned in this thread already.

Edit: oh and that yellow triangle with the exclamation point on some of them, that means there are vulnerabilities in those versions that haven't been fixed.

If are confusing it it with KDE 5.18, this also has been discussed numerous times now.

Like dolphin_oracle said a bit ago:
moving along now...

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 10:21 am
by tony37
andyprough wrote: Mon Aug 10, 2020 9:58 amMaybe kubuntu is defaulting to kmail, I don't know, I never used any ubuntu distros, but if they were defaulting to kmail it would not have been a very good choice during many of the years when kmail was basically broken.
Kmail was the default in Kubuntu 18.04, this was changed to Thunderbird in 20.04. Which I read as: Kmail (+ the whole akonadi thing) is slowly getting abandoned.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 10:23 am
by sunrat
I just installed RC1 and it went well. The GRUB issue I had in beta1 didn't rear its ugly head. Nvidia installer worked fine.
Just a couple of points.
- The MX Tools icon for Bash Config also appears on the taskbar for KDE System Settings and again for Screen Locking in System Settings. System Settings in Application Menu has a different icon again. System Settings may be better using the default KDE System Settings icon. I guess the default ePapirus theme doesn't have separate icons for these.
- Yakuake default hotkey is F4. KDE normally uses F4 to open the embedded terminal in Dolphin's window which is one of Dolphin's killer features and KDE expats from any other distro would expect this. IIRC, the normal default for Yakuake is F12.
- Clementine output seemed really quiet so I installed DeadBeef and playback was much louder, maybe 10dB more. Both applications had volume set to 100% through PulseAudio and showed as such in Pavucontrol. I use an old M-Audio Audiophile card which sometimes needs special tweaks to behave, but having 2 applications set at the same level but sounding so different is rather strange.

Otherwise, from a very brief install/bootup, this appears to be shaping up nicely. And the splash screen is really cute. :cool:

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 11:43 am
by paul1149
SwampRabbit wrote: Mon Aug 10, 2020 10:09 am there is no kmail 5.18, also kmail is a mess,
Strange:

KMail

Details for KMail
Project website
Latest stable release
5.14.3
July 9, 2020

I had the exact number wrong, but I will agree that kmail is a mess at this point.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:39 pm
by tony37
back to RC1 now:
I like it that you chose to have the Application Menu instead of the Application Launcher. The latter may look good, but I never really used it.
The Papirus icons are nice too.
The Monochrome SDDM-theme looks a bit, hmm, black and not very inviting to me. It could use a non-black background to enliven things. And when you just lock the current user, you still get the Breeze icons. Maybe that's part of having Breeze Dark as desktop theme.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:49 pm
by mystic
Can we not adjust date and time in a live boot?

I am unable to change the time. It says something along the lines of the that NTP time is unable to be changed.

Can someone else reproduce this?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:51 pm
by tony37
mystic wrote: Mon Aug 10, 2020 12:49 pm Can we not adjust date and time in a live boot?

I am unable to change the time. It says something along the lines of the that NTP time is unable to be changed.

Can someone else reproduce this?
I think that's one of the known issues in the release notes

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 12:59 pm
by asqwerth
tony37 wrote: Mon Aug 10, 2020 12:39 pm...
The Monochrome SDDM-theme looks a bit, hmm, black and not very inviting to me. It could use a non-black background to enliven things. And when you just lock the current user, you still get the Breeze icons. Maybe that's part of having Breeze Dark as desktop theme.
I've been busy the last 3 days and haven't tested the RC1.

Are you saying the default MX19.2 wallpaper doesn't appear as the default background (blurred of course, while the login elements and buttons are on screen) for Monochrome SDDM theme?

Hmm.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 1:09 pm
by tony37
asqwerth wrote: Mon Aug 10, 2020 12:59 pm Are you saying the default MX19.2 wallpaper doesn't appear as the default background (blurred of course, while the login elements and buttons are on screen) for Monochrome SDDM theme?
No, it doesn't, but it can be changed in the settings.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 1:17 pm
by Gerson
I am using "touchpad-indicator" installed from the stable repository (3 packages) and I have it configured to be disabled when I place an external mouse or when I am writing but it does not get disabled. I have tried all the combinations present and none of them work, but XFCE works perfectly.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 1:48 pm
by Adrian
Gerson wrote: Mon Aug 10, 2020 1:17 pm I am using "touchpad-indicator" installed from the stable repository (3 packages) and I have it configured to be disabled when I place an external mouse or when I am writing but it does not get disabled. I have tried all the combinations present and none of them work, but XFCE works perfectly.
KDE has a nice configuration option for touchpad, maybe you don't need that touchpad-indicator. I usually disable the touchpad completely when a mouse is connected (I really like that option).

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 2:25 pm
by Gerson
Adrian wrote: Mon Aug 10, 2020 1:48 pm
Gerson wrote: Mon Aug 10, 2020 1:17 pm I am using "touchpad-indicator" installed from the stable repository (3 packages) and I have it configured to be disabled when I place an external mouse or when I am writing but it does not get disabled. I have tried all the combinations present and none of them work, but XFCE works perfectly.
KDE has a nice configuration option for touchpad, maybe you don't need that touchpad-indicator. I usually disable the touchpad completely when a mouse is connected (I really like that option).
I've gone through all the system settings and can't find a way to make it work so that it is disabled when typing or when connecting an external mouse. Now I can use the touch panel but the system tells me that it doesn't detect it.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 2:39 pm
by tony37
Gerson wrote: Mon Aug 10, 2020 2:25 pm I've gone through all the system settings and can't find a way to make it work so that it is disabled when typing or when connecting an external mouse. Now I can use the touch panel but the system tells me that it doesn't detect it.
My only guess here is that you may have to uninstall touchpad-indicator first.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 4:04 pm
by tony37
Ctrl+Alt+T to open Konsole is still not working
maybe easier to just add it by default in 'Custom Shortcuts'

I see Plasma isn't adding stuff to favorites when switching menus, well done. But when I've removed some of the default favorites, they do return when I switch menu. Oh well, maybe difficult to change this.

Muon Help in the MX-updater context menu returns "Oops! That page can’t be found." (although I would still prefer to have Synaptic there of course, I found out Muon can't even find liblfunction when I'm looking for 'lfunction')
Maybe very small niggle but the close button of MX-updater's 'About' doesn't work. (And in Dutch I need to click on a button saying the equivalent of 'Undo' to close)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 6:13 pm
by Gerson
tony37 wrote: Mon Aug 10, 2020 2:39 pm
Gerson wrote: Mon Aug 10, 2020 2:25 pm I've gone through all the system settings and can't find a way to make it work so that it is disabled when typing or when connecting an external mouse. Now I can use the touch panel but the system tells me that it doesn't detect it.
My only guess here is that you may have to uninstall touchpad-indicator first.
The indicator is removed. I restarted and can work with the touch panel but the notifier says there is no touch panel as seen in the picture.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 6:36 pm
by fehlix
tony37 wrote: Mon Aug 10, 2020 4:04 pm Ctrl+Alt+T to open Konsole is still not working
maybe easier to just add it by default in 'Custom Shortcuts'

I see Plasma isn't adding stuff to favorites when switching menus, well done. But when I've removed some of the default favorites, they do return when I switch menu. Oh well, maybe difficult to change this.

Muon Help in the MX-updater context menu returns "Oops! That page can’t be found." (although I would still prefer to have Synaptic there of course, I found out Muon can't even find liblfunction when I'm looking for 'lfunction')
Maybe very small niggle but the close button of MX-updater's 'About' doesn't work. (And in Dutch I need to click on a button saying the equivalent of 'Undo' to close)
Yea, the windows close button shall better work and the Cancel button better also renamed to "Close". Also, you can just install Synaptic e.g. using Muon, and Synaptic will be shown in the right-click menu. About the Muon help page, hmm.. probably someone would need to write one, I guess.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Mon Aug 10, 2020 8:56 pm
by JuhaT
I did a clean install of the RC1. I installed Firejail from Muon as usual.
I had no problems using Firejail in the betas, but when I installed it on RC1 it started to act strange. It firejailed Dolphin, so all of a sudden appimages or other executables couldnt be started at all. It said I didnt have the right credentials. I couldnt do any root actions in dolphin.
I am not sure if Firejail had firejailed Dolphin before but I had no problems running stuff from dolphin before.
Also it prevented me from changing refresh rate of the monitor to 115hz
And top of that it turned out the lights of my lit keyboard.
Once I uninstalled Firejail with Muon all went back to normal.

I dont know if this is a new Firejail issue (maybe it was updated yesterday?) but I had no problems with Firejail on MX-KDE beta 1 or 2.

Code: Select all

System:    Host: <filter> 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=8a8b1134-27ff-4d2b-b7a6-1f601a7e1383 ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: 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: 1272 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 1272 2: 1049 3: 932 4: 1635 5: 902 6: 1228 7: 1194 
           8: 1038 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort mitigation: TSX disabled 
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:1b81 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 tty: N/A 
           OpenGL: renderer: NV134 v: 4.3 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a348 
           Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:10f0 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15bc 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 3.29 TiB used: 11.27 GiB (0.3%) 
           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: 8.24 GiB (28.6%) fs: ext4 dev: /dev/sdb1 
           ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 3.03 GiB (1.5%) fs: ext4 dev: /dev/sdb2 
Sensors:   System Temperatures: cpu: 33.0 C mobo: 27.8 C gpu: nouveau temp: 28 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 1276 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb https://mega.nz/linux/MEGAsync/Debian_10.0/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster main non-free
           2: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 253 Uptime: 17m Memory: 23.49 GiB used: 2.66 GiB (11.3%) Init: systemd v: 241 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 1:06 am
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

hello dolphin_oracle
Muon
had a little slip-up. first use. after check for updates the categories showed 88000 packages and two upgradable,
but these were not added to SHOW in the muon lists. , clicking on status upgradeable showed empty page when it states on status bar two upgradeable. needed to quit and Open; then the list is full. easy to notice a difference between three thousand and eighty-eight thousand.
Will this happen just first time open or will it happen later? this only time i have seen it.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 2:08 am
by Stevo
Edit: Oops! The new version was moved to main. :bagoverhead: Carry on!
Gerson wrote: Mon Aug 10, 2020 6:13 pm
tony37 wrote: Mon Aug 10, 2020 2:39 pm
Gerson wrote: Mon Aug 10, 2020 2:25 pm I've gone through all the system settings and can't find a way to make it work so that it is disabled when typing or when connecting an external mouse. Now I can use the touch panel but the system tells me that it doesn't detect it.
My only guess here is that you may have to uninstall touchpad-indicator first.
The indicator is removed. I restarted and can work with the touch panel but the notifier says there is no touch panel as seen in the picture.
Can you install the newer touchpad-indicator in the test repo? It works for me in KDE, except it doesn't show the disabled icon in the system tray, it just sits there and sort of pulsates every so often.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 4:32 am
by kangburra
The installer still has a bug where renaming the old home works but it creates a file for the user which then cannot be wrtten into. This was reported in Beta2.
Renaming/removing the file and then

Code: Select all

mkhomedir_helper username
fixes the problem.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:52 am
by Ghost67
Great system! I'm very enthusiastic about this build as it seems to have eradicated the problem I was having with the XFCE build ( here: viewtopic.php?p=538506#p538506 )
One thing I noted was that 'Show hidden' in Dolphin seems to apply on a 'per folder' basis and needs to be set for every folder visited rather than applying to all folders. I am not familiar with KDE and Dolphin though, so for all I know this might be the default behaviour.

Code: Select all

System:    Host: <filter> 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=cceda323-5bd4-4053-b53a-7da9015c53bf ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: N/A System: Advent product: DT1410 v: N/A serial: <filter> 
           Mobo: Foxconn model: H61MXL/H61MXL-K serial: <filter> BIOS: American Megatrends v: B63D3A04 date: 09/22/2011 
CPU:       Topology: Quad Core model: Intel Core i5-2320 bits: 64 type: MCP arch: Sandy Bridge family: 6 model-id: 2A (42) 
           stepping: 7 microcode: 2F L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23943 
           Speed: 2763 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 2763 2: 2406 3: 2483 4: 2438 
           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 status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Foxconn driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0102 
           Device-2: NVIDIA GK107 [GeForce GT 640] vendor: ASUSTeK driver: nvidia v: 440.100 bus ID: 01:00.0 
           chip ID: 10de:0fc1 
           Display: x11 server: X.Org 1.20.4 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv 
           compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 640/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Foxconn driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Device-2: NVIDIA GK107 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:0e1b 
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-1.2:3 
           chip ID: 046d:082d serial: <filter> 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: Foxconn driver: atl1c v: 1.0.1.1-NAPI port: d000 
           bus ID: 03:00.0 chip ID: 1969:1083 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 74.53 GiB used: 32.99 GiB (44.3%) 
           ID-1: /dev/sda vendor: Samsung model: HD080HJ size: 74.53 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 0-41 scheme: MBR 
Partition: ID-1: / raw size: 72.50 GiB size: 70.86 GiB (97.74%) used: 32.98 GiB (46.5%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 13.8 MiB (0.7%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 50 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 11% 
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://mxlinux.mirrors.uk2.net/packages/mx/repo/ buster main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 219 Uptime: 4h 35m Memory: 7.69 GiB used: 1.96 GiB (25.5%) Init: SysVinit v: 2.93 runlevel: 5 
           default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:59 am
by asqwerth
Ghost67 wrote: Tue Aug 11, 2020 5:52 am Great system! I'm very enthusiastic about this build as it seems to have eradicated the problem I was having with the XFCE build ( here: viewtopic.php?p=538506#p538506 )
One thing I noted was that 'Show hidden' in Dolphin seems to apply on a 'per folder' basis and needs to be set for every folder visited rather than applying to all folders. I am not familiar with KDE and Dolphin though, so for all I know this might be the default behaviour....
I believe so, and it remembers your display/view settings for each folder, which I like.

What I miss in THunar is that the settings are global. If I set 'view hidden" it applies to all. If I set "sort files based on Modified Date, in descending order" it applies to all. If I set "View as Thumbnails", it's globally applied.

In Dolphin (as in Nemo and Caja), you can per per folder view settings. So my wallpaper folder could have "VIew THumbnails" while my documents folder could simply display all File Details.

PS. I'm almost sure though that Dolphin does have a setting where you can make your view settings apply to all folders.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 6:07 am
by tony37
asqwerth wrote: Tue Aug 11, 2020 5:59 am PS. I'm almost sure though that Dolphin does have a setting where you can make your view settings apply to all folders.
indeed, it's actually the very first setting: General - Behavior - View

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 6:10 am
by Ghost67
Ah! My thanks to both of you :)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 6:14 am
by tony37
The information on hibernation in the updated manual (p.31) doesn't apply to KDE as there it is enabled, as can be seen in the picture on p.30. And hibernation doesn't seem to work out of the box. I mentioned this issue in the beta2 thread btw

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 7:33 am
by kc1di
So Far RC1 is working well on my Laptop. I have to agree with some here Moun is not my favorite tool much perfer synaptic , but that being said couuld be just because I'm use to it.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 7:34 am
by exploder
I have been following the development of this release and like what I am seeing! I actually started using Linux full time with Simply Mepis many years ago. RC 1 is looking far better than any Mepis release I can remember. The out of the box tools and documentation are outstanding! I see a lot of attention to detail. Looking forward to the final release.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 7:50 am
by uncle mark
exploder wrote: Tue Aug 11, 2020 7:34 am I have been following the development of this release and like what I am seeing! I actually started using Linux full time with Simply Mepis many years ago. RC 1 is looking far better than any Mepis release I can remember. The out of the box tools and documentation are outstanding! I see a lot of attention to detail. Looking forward to the final release.
Blasphemer!!!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:01 am
by exploder
I was very impressed with the tool that fixed screen tearing. Most distros would simply call it an upstream issue and leave it to the end user to try and fix. The fact that the developers actually took the time to include a simple way to fix this says a lot! I wish more distros used this measure of quality and took ownership of these kinds of problems. Very nice work!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:01 am
by dolphin_oracle
kangburra wrote: Tue Aug 11, 2020 4:32 am The installer still has a bug where renaming the old home works but it creates a file for the user which then cannot be wrtten into. This was reported in Beta2.
Renaming/removing the file and then

Code: Select all

mkhomedir_helper username
fixes the problem.
I thought I fixed that bug. Can you post the /var/log/minstall.log please

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:14 am
by GuiGuy
uncle mark wrote: Tue Aug 11, 2020 7:50 am
exploder wrote: Tue Aug 11, 2020 7:34 am I have been following the development of this release and like what I am seeing! I actually started using Linux full time with Simply Mepis many years ago. RC 1 is looking far better than any Mepis release I can remember. The out of the box tools and documentation are outstanding! I see a lot of attention to detail. Looking forward to the final release.
Blasphemer!!!
Some of these youngsters don't know that Warren Woodford was worshipped by Mepis users (including me).

My favourite version was the one with kde3 - never liked kde4.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:19 am
by exploder
Warren Wooford made Linux easy to install and the installer was reliable!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:39 am
by kangburra
dolphin_oracle wrote: Tue Aug 11, 2020 8:01 am
kangburra wrote: Tue Aug 11, 2020 4:32 am The installer still has a bug where renaming the old home works but it creates a file for the user which then cannot be wrtten into. This was reported in Beta2.
Renaming/removing the file and then

Code: Select all

mkhomedir_helper username
fixes the problem.
I thought I fixed that bug. Can you post the /var/log/minstall.log please
Here is the file.
It looks like a copy command created a file because it is missing the trailing slash.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 9:39 am
by dolphin_oracle
kangburra wrote: Tue Aug 11, 2020 8:39 am
dolphin_oracle wrote: Tue Aug 11, 2020 8:01 am
kangburra wrote: Tue Aug 11, 2020 4:32 am The installer still has a bug where renaming the old home works but it creates a file for the user which then cannot be wrtten into. This was reported in Beta2.
Renaming/removing the file and then

Code: Select all

mkhomedir_helper username
fixes the problem.
I thought I fixed that bug. Can you post the /var/log/minstall.log please
Here is the file.
It looks like a copy command created a file because it is missing the trailing slash.
ok they updated installer never made it to the repo. will get that updated later today. thanks!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 10:33 am
by tony37
One small niggle with the Papirus icons is that the Clementine icon in the panel doesn't look good at all on a dark theme.
I fixed this by copying /usr/share/icons/Papirus/16x16/apps/clementine.svg to /usr/share/icons/Papirus/16x16/panel/clementine-panel.svg. And then also for 22x22 and 24x24.
I had to switch to another icon set, then back to Papirus and then relogin to make it work, but it's really so much better, works on both light and dark theme.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 12:07 pm
by uncle mark
GuiGuy wrote: Tue Aug 11, 2020 8:14 am]Some of these youngsters don't know that Warren Woodford was worshipped by Mepis users (including me).

My favourite version was the one with kde3 - never liked kde4.
He had it tamed by M11. But yes, M8 was sweet.

I skipped every other release.

M6.5
M8
M11

was my progression.

Hoping this release will be the next step.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 2:08 pm
by Gerson
Stevo wrote: Tue Aug 11, 2020 2:08 am Edit: Oops! The new version was moved to main. :bagoverhead: Carry on!
Gerson wrote: Mon Aug 10, 2020 6:13 pm
tony37 wrote: Mon Aug 10, 2020 2:39 pm
Can you install the newer touchpad-indicator in the test repo? It works for me in KDE, except it doesn't show the disabled icon in the system tray, it just sits there and sort of pulsates every so often.
It's not in the test repository, it's in the stable repository, I reinstalled it but it doesn't inactivate the touchpad when prompted.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 4:28 pm
by fladd
Maybe a silly question, but is there something that makes KDE slow in a VirtualBox VM in particular, or is KDE just generally really slow (like slower than Win 10)? Opening applications like a terminal or opening system settings takes between 3 and 5 seconds, and even when scrolling through the KDE menu, the selected menu item is lagging behind the mouse for about 1 sec. Regular MX is fully responsive in the same VM, and other OS I tested are as well.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 4:38 pm
by richb
I do not know about a VB install, but plenty fast on an SSD.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:28 pm
by SwampRabbit
No issues in VirtualBox either on any of the Betas or RC1

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:33 pm
by fladd
richb wrote: Tue Aug 11, 2020 4:38 pm I do not know about a VB install, but plenty fast on an SSD.
It's the Live CD.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:44 pm
by fladd
SwampRabbit wrote: Tue Aug 11, 2020 5:28 pm No issues in VirtualBox either on any of the Betas or RC1
I also don't know what expected behaviour is of course. But this is the experience here:

https://imgur.com/6FBxFRS

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 5:53 pm
by richb
I would assume a CD would be slow by virtue of the technology involved.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 6:17 pm
by richb
Moderator

Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 6:51 pm
by kc1di
RC1 working very well on my laptop

Code: Select all

System:
  Host: kc1di-mx Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=b2b23b6c-69e5-44b6-97b9-3572ee61ba05 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 info: latte-dock wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: LENOVO product: 20BV000AUS v: ThinkPad T450 serial: <filter> 
  Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20BV000AUS v: SDK0E50510 WIN serial: <filter> 
  UEFI [Legacy]: LENOVO v: JBET71WW (1.35 ) date: 09/14/2018 
Battery:
  ID-1: BAT0 charge: 17.4 Wh condition: 17.7/23.2 Wh (76%) volts: 12.4/11.1 
  model: SANYO 45N1773 type: Li-ion serial: <filter> status: Unknown 
  ID-2: BAT1 charge: 15.9 Wh condition: 17.1/23.2 Wh (74%) volts: 12.0/11.1 
  model: SANYO 45N1775 type: Li-ion serial: <filter> status: Discharging 
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: Intel Core i5-5300U bits: 64 type: MT MCP 
  arch: Broadwell family: 6 model-id: 3D (61) stepping: 4 microcode: 2F 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 18355 
  Speed: 1063 MHz min/max: 500/2900 MHz Core speeds (MHz): 1: 1063 2: 1220 3: 1187 
  4: 1020 
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
  STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable 
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:1616 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 resolution: 1600x900~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.0.7 
  direct render: Yes 
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
  bus ID: 00:03.0 chip ID: 8086:160c 
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Ethernet I218-LM vendor: Lenovo driver: e1000e v: 3.2.6-k 
  port: 3080 bus ID: 00:19.0 chip ID: 8086:15a2 
  IF: eth0 state: down mac: <filter> 
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
  chip ID: 8086:095b 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 267.26 GiB used: 13.68 GiB (5.1%) 
  ID-1: /dev/mmcblk0 vendor: SanDisk model: SL32G size: 28.79 GiB block size: 
  physical: 512 B logical: 512 B serial: <filter> scheme: MBR 
  ID-2: /dev/sda vendor: LITE-ON model: LCH-256V2S size: 238.47 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 902 
  scheme: MBR 
Partition:
  ID-1: / raw size: 37.25 GiB size: 36.41 GiB (97.75%) used: 7.98 GiB (21.9%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: /home raw size: 198.43 GiB size: 194.31 GiB (97.93%) used: 5.70 GiB (2.9%) 
  fs: ext4 dev: /dev/sda6 
  ID-3: swap-1 size: 2.79 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 38.5 C mobo: 0.0 C 
  Fan Speeds (RPM): cpu: 0 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian buster main contrib non-free
  2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
  1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 210 Uptime: 3m Memory: 7.49 GiB used: 704.5 MiB (9.2%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
  running in: quick-system-in inxi: 3.0.36 

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 7:46 pm
by fladd
richb wrote: Tue Aug 11, 2020 5:53 pm I would assume a CD would be slow by virtue of the technology involved.
It is running in a VM, so from the CD ISO directly.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 7:47 pm
by fladd
richb wrote: Tue Aug 11, 2020 6:17 pm Moderator

Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
I could not find this link, so I just posted the link instead of embedding it.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:04 pm
by richb
fladd wrote: Tue Aug 11, 2020 7:47 pm
richb wrote: Tue Aug 11, 2020 6:17 pm Moderator

Forum image rules are mages shall be a maximum of 640 x 620. Larger images disrupt the flow of the topic.I see you are using Imgur. Pick the "Large" image link which meets Forum Requirements.
I could not find this link, so I just posted the link instead of embedding it.
Thank you.

In Imgur, click on your username then images. Click your image and the following appears: Sorry, the image got clipped on the right when I resized. to get the file size less than 300 KB which is the Forum limit. The large is at the bottom right. Click that first then the Linked BB Code.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:08 pm
by SwampRabbit
fladd wrote: Tue Aug 11, 2020 7:46 pm
richb wrote: Tue Aug 11, 2020 5:53 pm I would assume a CD would be slow by virtue of the technology involved.
It is running in a VM, so from the CD ISO directly.
Interesting, there shouldn't be that much of a impact, but I only assume there might be some.
Is this with an SSD or good 'ol spinning rust HHD? I could see if with HDD depending on the location I suppose, if the drive is slower and or showing some age... but we all know that doesn't affect a SSD.

I haven't ran a live ISO in a VM in awhile outside of installing shortly after.

I wonder if anyone can take a look and test it soon. I'm a bit tied up right now, but can later this evening I think.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 8:43 pm
by dolphin_oracle
I run it in a vm all the time. there are a couple of factors. ram that the VM has is more important for the KDE version in my experience, especially at startup. another factor is the graphics driver in use. the kde desktop makes much more use of graphics effects when windows move or pop open, etc... So it can be slower.

Its not particularly slower for me, except for boot up. On real hardware no problems at all.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 9:00 pm
by SwampRabbit
dolphin_oracle wrote: Tue Aug 11, 2020 8:43 pm I run it in a vm all the time.
You’ve run strictly off the live ISO booted or installed? Think the user was stating specifically they weren’t installing.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 9:06 pm
by dolphin_oracle
SwampRabbit wrote: Tue Aug 11, 2020 9:00 pm
dolphin_oracle wrote: Tue Aug 11, 2020 8:43 pm I run it in a vm all the time.
You’ve run strictly off the live ISO booted or installed? Think the user was stating specifically they weren’t installing.
live. great for testing

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 10:07 pm
by JayM
I'd still like to see the option to disable the 30-second logout/reboot/shutdown/switch users delay ("Confirm logout") added to MX Tweak so people don't have to hunt all over in their plasma settings to find it. I foresee a lot of questions about that delay in the forum after MX-KDE goes live.
Image
There should probably also be a FAQ entry about the delay: the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none. At least I haven't been able so far to find a config file where that value can be changed. But then, I don't even know what MX-KDE is using for its session manager. It's not LightDM.

Edit: found it, it's SDDM. I still can't find any config options for it that contain that 30-second timeout value that could be edited by users.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 10:25 pm
by richb
JayM wrote: Tue Aug 11, 2020 10:07 pm I'd still like to see the option to disable the 30-second logout/reboot/shutdown/switch users delay ("Confirm logout") added to MX Tweak so people don't have to hunt all over in their plasma settings to find it. I foresee a lot of questions about that delay in the forum after MX-KDE goes live.
Image
There should probably also be a FAQ entry about the delay: the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none. At least I haven't been able so far to find a config file where that value can be changed. But then, I don't even know what MX-KDE is using for its session manager. It's not LightDM.

Edit: found it, it's SDDM. I still can't find any config options for it that contain that 30-second timeout value that could be edited by users.
I do not understand. In SDDM screen you just click on the appropriate icon to suspend, logout, shutdown, etc. and it immediately executes. No need to hunt in plasma settings. Or am I misunderstanding.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 10:54 pm
by sunrat
JayM wrote: Tue Aug 11, 2020 10:07 pmEdit: found it, it's SDDM. I still can't find any config options for it that contain that 30-second timeout value that could be edited by users.
System Settings > Startup and Shutdown > Desktop Session > untick "Confirm logout"

Plasma has a lot of settings. Seems redundant to duplicate them in MX Tweak. Just ask someone more familiar with Plasma. ;)

Edit - ^ that's for Session logout which is what I assume you meant.
Or did you mean the SDDM login screen like richb just mentioned. The restart/shutdown etc. icons there execute immediately

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 11:00 pm
by JayM
richb wrote: Tue Aug 11, 2020 10:25 pm I do not understand. In SDDM screen you just click on the appropriate icon to suspend, logout, shutdown, etc. and it immediately executes. No need to hunt in plasma settings. Or am I misunderstanding.
This:
Image
The default of having a delay before performing a logout, shutdown, etc. action can be switched off in System Settings -> Startup and Shutdown -> Desktop Session by unchecking "Confirm logout", and that's a bit difficult to find for KDE newbies. (I always have to hunt for it for a few minutes myself.) It would be easier if it could also be enabled/disabled in MX Tweak: kind of "one stop shopping" if you will for what I anticipate will be frequently asked-about settings such as this one. (The Internet is full of posts by newbs asking how to change or get rid of that 30-second delay as it can be an annoyance.)

You get that screen when you're in a session and choose a logout/shutdown/etc. action in the menu. Many users prefer that it would then just do what they told it to do rather than having a Windowslike "Are you sure?" confirmation dialog first.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 11:08 pm
by SwampRabbit
@sunrat and JayM... thank you both for saving me the time having to locate that!

It was driving me nutz! :killcomputer:

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 11:09 pm
by sunrat
JayM wrote: Tue Aug 11, 2020 11:00 pmThe default of having a delay before performing a logout, shutdown, etc. action can be switched off in System Settings -> Startup and Shutdown -> Desktop Session by unchecking "Confirm logout", and that's a bit difficult to find for KDE newbies.
I don't buy it. You learn to drive a car after only riding a bike, the brakes are not on the handlebars. Change from one DE to one you are unfamiliar with, you will need to learn a few new things. Otherwise you create perpetual newbies.
SwampRabbit wrote: Tue Aug 11, 2020 11:08 pm @sunrat and JayM... thank you both for saving me the time having to locate that!

It was driving me nutz! :killcomputer:
I think I posted exactly the same info for d_o a few days ago when he asked. :happy: Happy to help with little questions like this. KDE has been my main DE for 15 years, except for a year or so with MX-16 (just not a fan of Xfce).

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Tue Aug 11, 2020 11:45 pm
by JayM
sunrat wrote: Tue Aug 11, 2020 11:09 pm
JayM wrote: Tue Aug 11, 2020 11:00 pmThe default of having a delay before performing a logout, shutdown, etc. action can be switched off in System Settings -> Startup and Shutdown -> Desktop Session by unchecking "Confirm logout", and that's a bit difficult to find for KDE newbies.
I don't buy it. You learn to drive a car after only riding a bike, the brakes are not on the handlebars. Change from one DE to one you are unfamiliar with, you will need to learn a few new things. Otherwise you create perpetual newbies.
I agree somewhat. However, MX and MEPIS before it have been known to have a philosophy of easing the burden on newbies by making and offering various simple-to-use GUI tools. Some people install Linux in order to use their computer to do work, not to spend unproductive hours hunting for and changing settings and in learning the minutae of their DE (although it's a very good idea to do so.) Also I'm thinking as one of the support volunteers: it's easier to tell people to just use MX Tweak rather than talking them through finding things in Plasma's settings, especially when I have trouble finding things there myself. Besides, MX Tweak for KDE is rather sparsely-populated compared to it in Xfce. It would be nice if it were fleshed out a little more. :)

While we're on the subject, how about an addition to MX Tweak for Dolphin's configuration, toggling between "Remember properties for each folder" (which is the default) and "Use common properties for all folders"? With the latter setting the default view (icons view mode, which is the default view, compact view mode and details view) only has to be configured once for that user rather than over and over again in every single directory. I forgot how annoying Plasma's default settings are: having to change to from icon view to compact view each time I enter a new directory in Dolphin, the 30-second shutdown confirmation delay instead of just shutting down, single-clicking opens files in their associated apps instead of just selecting them, etc. I remember now that these settings were the first ones I'd change after installing any KDE distro. It would be great if I could change them all in one place, MX Tweak, instead of having to go all over the place to find and change them and try to remember where they all are.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 4:04 am
by m_pav
JayM wrote: Tue Aug 11, 2020 10:07 pm the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none.
Found it !
I have hated this thing sooooooo much since the day I first encountered it. Yes, it is "hard coded" in a simple text file that can be edited with root privileges.

/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml

It's a regular text file. On line 57, change to a sane timeout, 30 seconds is for turtles. Use F11 to see line numbers. This is what you'll see
property real timeout: 30

I vote we divide and conquer this filthy beast and split it 6 ways to give us 5 seconds. Personally though, I'd prefer 2-3 seconds max.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 4:14 am
by m_pav
Who knew? I just discovered that touching the PrtSc button on my keyboard after login, before the desktop shows, during the animation, would capture a screenshot of the boot animation !

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 4:42 am
by JayM
m_pav wrote: Wed Aug 12, 2020 4:04 am
JayM wrote: Tue Aug 11, 2020 10:07 pm the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none.
Found it !
I have hated this thing sooooooo much since the day I first encountered it. Yes, it is "hard coded" in a simple text file that can be edited with root privileges.

/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml

It's a regular text file. On line 57, change to a sane timeout, 30 seconds is for turtles. Use F11 to see line numbers. This is what you'll see
property real timeout: 30

I vote we divide and conquer this filthy beast and split it 6 ways to give us 5 seconds. Personally though, I'd prefer 2-3 seconds max.
Thank you! :winner:

I agree, a shorter value should be the default. 10 seconds should be plenty of time to let users change their minds. 5 might not be long enough for those with slower reaction times. (Now, if only there was a GUI tool with an entry where users could adjust this value to suit themselves... :biggrin: )

Edit: I changed it to 10 seconds and tested it. 10 seconds is livable-with and saner than having to wait for what seems like forever. OTOH grub's default time-out is 5 seconds so maybe make it 5 for consistency? I don't know.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 5:07 am
by tony37
Maybe totally disabling the delay by default is even better. I can guarantee you this will cause the least amount of complaints. But changing the delay from 30 to 10 for those who want a delay seems a no-brainer.
JayM wrote: Wed Aug 12, 2020 4:42 am OTOH grub's default time-out is 5 seconds so maybe make it 5 for consistency? I don't know.
Grub allows people to make a choice of which OS/kernel to start, but in clicking on 'shutdown' I already made a choice, so I don't need a delay to ask me: Are you REALLY sure? Grub doesn't ask me if I'm really sure. So I think the two timeouts are different things
Maybe this delay is useful on a server or such, but for a normal desktop user?

Another non-intuitive default setting in Plasma 5.14 is that the task manager sorts the programs alphabetically... Starting from 5.15 (see Mageia 7) this has been changed to 'manually' so the programs appear in the order of being opened and people can sort them themselves.
Personally I'd also have the task manager show only the programs from the current desktop (the default in the latest Plasma version), but that may be just me.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 5:23 am
by Jerry3904
We had a message that I thought I might paste here in case it had already not been noticed:
MX-19.2 KDE RC 1 a few things left from XFCE in .config and in /etc/skel/, a good job was done

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 5:57 am
by richb
As regards the delay, I will be odd man out. You can always shortcut it from the SDDM screen that shows up. And I prefer the delay. If I change my mind I can cancel. Thirty seconds is excessive., 10 or 15 more reasonable. Apparently more are bothered by it so I retreat.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:14 am
by m_pav
Jerry3904 wrote: Wed Aug 12, 2020 5:23 amMX-19.2 KDE RC 1 a few things left from XFCE in .config and in /etc/skel/, a good job was done
I saw that but I didn't respond because it was not the first time and I'd seen it, or a question like it that has a response along the lines of, one of our desktop-defaults metapackages, possible the common one puts them in there.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:21 am
by kc1di
m_pav wrote: Wed Aug 12, 2020 4:04 am
JayM wrote: Tue Aug 11, 2020 10:07 pm the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none.
Found it !

/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml
Thanks for sharing great find :)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:29 am
by kangburra
m_pav wrote: Wed Aug 12, 2020 4:04 am
JayM wrote: Tue Aug 11, 2020 10:07 pm the 30-second value seems to be hard-coded in Plasma so it's either 30 seconds or none.
Found it !
I have hated this thing sooooooo much since the day I first encountered it. Yes, it is "hard coded" in a simple text file that can be edited with root privileges.

/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml

It's a regular text file. On line 57, change to a sane timeout, 30 seconds is for turtles. Use F11 to see line numbers. This is what you'll see
property real timeout: 30

I vote we divide and conquer this filthy beast and split it 6 ways to give us 5 seconds. Personally though, I'd prefer 2-3 seconds max.
Wow thank you! Happy days.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:38 am
by JayM
30 seconds isn't only long enough for you to change your mind and click cancel, it's practically long enough to go pour yourself a cup of coffee or tea while you're still deciding. Every other KDE distro I've used has the default and annoying 30-second pause. Let's be different.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:42 am
by tony37
JayM wrote: Wed Aug 12, 2020 6:38 am Every other KDE distro I've used has the default and annoying 30-second pause. Let's be different.
+1: why have so many distros if they don't even dare to change a simple setting?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:44 am
by kc1di
JayM wrote: Wed Aug 12, 2020 6:38 am 30 seconds isn't only long enough for you to change your mind and click cancel, it's practically long enough to go pour yourself a cup of coffee or tea while you're still deciding. Every other KDE distro I've used has the default and annoying 30-second pause. Let's be different.
+1 I agree I set mine for 5 sec. which is plenty of time for me. thanks again. RC1 is looking very good. Thanks to all the Devs for their work.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:51 am
by JayM
tony37 wrote: Wed Aug 12, 2020 6:42 am
JayM wrote: Wed Aug 12, 2020 6:38 am Every other KDE distro I've used has the default and annoying 30-second pause. Let's be different.
+1: why have so many distros if they don't even dare to change a simple setting?
Probably because they don't have an m_pav on their development team to find where that setting gets hidden.

(Thinking about it further, as it's a setting that's presumably in each individual look and feel's config file I don't think it can be made a change item in MX Tweak after all, but it can be make a wiki entry telling people how to change it for their particular look and feel.)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:03 am
by tony37
JayM wrote: Wed Aug 12, 2020 6:51 am(Thinking about it further, as it's a setting that's presumably in each individual look and feel's config file I don't think it can be made a change item in MX Tweak after all, but it can be make a wiki entry telling people how to change it for their particular look and feel.)
Can't you try to put these files by default in /home/user/.local/share ? I'll test this and see if it works when I create a new user.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:04 am
by richb
JayM wrote: Wed Aug 12, 2020 6:38 am 30 seconds isn't only long enough for you to change your mind and click cancel, it's practically long enough to go pour yourself a cup of coffee or tea while you're still deciding. Every other KDE distro I've used has the default and annoying 30-second pause. Let's be different.
Already said 30 seconds is too long. I just do not prefer an immediate action taken. No need to belabor this further.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:12 am
by Eadwine Rose
Indeed.. let's not get caught up with rehashing details like these. They have been noted.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:13 am
by tony37
tony37 wrote: Wed Aug 12, 2020 7:03 am
JayM wrote: Wed Aug 12, 2020 6:51 am(Thinking about it further, as it's a setting that's presumably in each individual look and feel's config file I don't think it can be made a change item in MX Tweak after all, but it can be make a wiki entry telling people how to change it for their particular look and feel.)
Can't you try to put these files by default in /home/user/.local/share ? I'll test this and see if it works when I create a new user.
update: I copied /usr/share/plasma/look-and-feel/org.kde.breeze.desktop to /etc/skel/.local/share/plasma/look-and-feel, then I changed the timeout to 10 seconds (in /etc/skel), created a new user and it works. The /home/user/.local/share files override the /usr/share files (which I didn't change), so each user can change his own files.

@JayM: But rereading what you said, I see you meant something else, but I think all look-and-feels use the standard breeze one for logout. I tested this with McMojave and it has no logout folder as its own, neither has the MX look-and-feel btw
I was thinking of: how let a user change these logout settings without having them affect other users.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:44 am
by dolphin_oracle
tony37 wrote: Wed Aug 12, 2020 7:13 am
tony37 wrote: Wed Aug 12, 2020 7:03 am
JayM wrote: Wed Aug 12, 2020 6:51 am(Thinking about it further, as it's a setting that's presumably in each individual look and feel's config file I don't think it can be made a change item in MX Tweak after all, but it can be make a wiki entry telling people how to change it for their particular look and feel.)
Can't you try to put these files by default in /home/user/.local/share ? I'll test this and see if it works when I create a new user.
update: I copied /usr/share/plasma/look-and-feel/org.kde.breeze.desktop to /etc/skel/.local/share/plasma/look-and-feel, then I changed the timeout to 10 seconds (in /etc/skel), created a new user and it works. The /home/user/.local/share files override the /usr/share files (which I didn't change), so each user can change his own files.

@JayM: But rereading what you said, maybe you meant something else, but I think all look-and-feels use the standard breeze one for logout. I tested this with McMojave and it has no logout folder as its own, neither has the MX look-and-feel btw
I was thinking of: how let a user change these logout settings without having them affect other users.
do you have to copy the entire theme, or just the one changed file?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 7:47 am
by tony37
dolphin_oracle wrote: Wed Aug 12, 2020 7:44 am do you have to copy the entire theme, or just the one changed file?
I tested with copying only the logout folder but that doesn't work, my test user hangs when logging out.

One issue I can see is if there would be updates to the breeze look-and-feel, then the updates would be overridden by the .local/share files.
The latest update to the breeze package was January 2019, I don't think there will be updates here until you upgrade the Plasma version.
edit: I see these files are actually owned by the plasma-workspace package, so latest update February '19

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 8:18 am
by kangburra
I have just finished installing on a Chromebook.
It's a bit sluggish when doing a few things at once but it is also 35C here today so I will let it off.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 8:41 am
by j2mcgreg
I haven't used KDE since MX was launched, so it may be just my ignorance showing, but, I can't find a way to toggle Conky off and have that setting retained from session to session. In standard MX, I can configure Conky as I like it and then toggle it off in the first session after the install and then activate it later on an 'as needed" basis. In the RC, I have to go to the Conky configuration utility and select Stop each session.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 9:12 am
by chrispop99
j2mcgreg wrote: Wed Aug 12, 2020 8:41 am I haven't used KDE since MX was launched, so it may be just my ignorance showing, but, I can't find a way to toggle Conky off and have that setting retained from session to session. In standard MX, I can configure Conky as I like it and then toggle it off in the first session after the install and then activate it later on an 'as needed" basis. In the RC, I have to go to the Conky configuration utility and select Stop each session.
Conky Toggle works fine here.

Whatever state it is in at shutdown is maintained after reboot.

Note that Conky Toggle is in the Utilities menu.

Chris

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 9:31 am
by j2mcgreg
Thank You

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 11:15 am
by junoluna
just installed and had my first look ... i have been mainly using KDE/plasma for a while now and it is my favorite desktop environment

really nice to have a 'proper' MX KDE ready to go.

i think you have done a lovely job ...

thank you team

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 11:18 am
by tony37
JayM wrote: Tue Aug 11, 2020 11:45 pm I forgot how annoying Plasma's default settings are: having to change to from icon view to compact view each time I enter a new directory in Dolphin, the 30-second shutdown confirmation delay instead of just shutting down, single-clicking opens files in their associated apps instead of just selecting them, etc.
I actually started liking single-click behavior because of all this MX KDE testing. Double-click is starting to annoy me now.
But if it so happens (no idea if this is the case) that 90% of computer users are used to double-click, it's probably more user-friendly to have double-click as default.

I also think that having separate view properties for each directory in Dolphin is confusing for most users (I always change it). Asqwerth said in post #59 he likes it and it's good the option is there but I guess it's mostly for people who have thought a bit about this, how they want to organize things etc., but having this as default leads to stuff like "hey, I put it on 'show hidden files' and now I can't see them anymore"
Just my thoughts

edit: one thing I'm missing with single-click behavior is that I can't rename the file by using a 'slow' double-click

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 2:00 pm
by fladd
SwampRabbit wrote: Tue Aug 11, 2020 8:08 pm
fladd wrote: Tue Aug 11, 2020 7:46 pm
richb wrote: Tue Aug 11, 2020 5:53 pm I would assume a CD would be slow by virtue of the technology involved.
It is running in a VM, so from the CD ISO directly.
Interesting, there shouldn't be that much of a impact, but I only assume there might be some.
Is this with an SSD or good 'ol spinning rust HHD? I could see if with HDD depending on the location I suppose, if the drive is slower and or showing some age... but we all know that doesn't affect a SSD.

I haven't ran a live ISO in a VM in awhile outside of installing shortly after.

I wonder if anyone can take a look and test it soon. I'm a bit tied up right now, but can later this evening I think.
This is on a 2013 MacbookPro.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 2:14 pm
by SwampRabbit
fladd wrote: Wed Aug 12, 2020 2:00 pm This is on a 2013 MacbookPro.
Running macOS, using VirtualBox to run MX or is something else installed on your MacbookPro?
What version of VirtualBox are you using?

Sorry if you already stated these.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 2:50 pm
by Gerson
WIFI Internet stopped working after last update. The card works well on other distributions including Windows but, although it detects the available networks, it does not connect to the home wifi, when I use MX-KDE, it was working fine.
If I use MX-XFCE if there is connection.
EDIT:
For some strange reason I changed the network password to the login password but I fixed it.
It has "magic" MX-KDE JAJAJA

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 3:05 pm
by fladd
I now tried to install it in a VM, but installation fails at the very end with "Sorry, failed to create user directory!".

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 3:13 pm
by tony37
I have this slow behavior in VirtualBox too, host OS being MX KDE RC1, no problems there.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 3:30 pm
by fladd
Changing the panel position to left in the MX tools seems to crash plasma shell, leaving you with just a cursor.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 3:50 pm
by tony37
fladd wrote: Wed Aug 12, 2020 3:05 pm I now tried to install it in a VM, but installation fails at the very end with "Sorry, failed to create user directory!".
Doing a VirtualBox install went fine for me.
Maybe a stupid question, but does your virtual drive have enough space? If the space gets dynamically allocated, I've had it happen to me it doesn't allocate well, so I only use virtual drives with a fixed size.

RC1 is still a bit slow also on VBox install, but nothing extraordinary and it's a VBox after all, so...
Maybe a KDE thing.

What you also have on the live .iso after booting is some apt processes running like cnf-update-db

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:31 pm
by fladd
I now managed to install in a VM, but it is still extremely slow. I might try one more time booting from a USB stick into the live system. If an i7 with 8GB memory is not enough to run this, then KDE is probably not for me :-)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 6:51 pm
by sunrat
fladd wrote: Wed Aug 12, 2020 6:31 pmIf an i7 with 8GB memory is not enough to run this, then KDE is probably not for me :-)
I run KDE Plasma 5.17.5 Sid-based system on a Core2Duo from 2008 with 4GB RAM. It's quite responsive for everyday tasks. Same rig runs Buster/KDE in multiboot which is also quite snappy. Haven't tried MX-KDE on this one, only on my other rig - i5 6500 w/ 16GB RAM.
i7 w/ 8GB should be a speed demon. ;)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 8:17 pm
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

Hello dolphin_oracle
different machine install RC_mx19ahs_kde_RC
has same
Muon
oddity. on first update
After Check for Updates the ALL will not load. Need to quit muon and open muon for ALL to show.

Code: Select all

System:    Host: WallE Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <root required> 
           Chassis: Hewlett-Packard type: 3 serial: <root required> 
           Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends v: 5.15 date: 06/25/2010 
CPU:       Topology: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP arch: Nehalem rev: 2 L2 cache: 4096 KiB 
           bogomips: 23409 
           Speed: 1980 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1980 2: 2540 3: 2426 4: 1970 
           Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm 
           dts est flush_l1d fpu fxsr ht ibpb ibrs lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe 
           pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 
           tsc vme xtopology xtpr 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0042 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel 
           port: d800 bus ID: 01:00.0 chip ID: 10ec:8168 
Drives:    Local Storage: total: 480.67 GiB used: 6.99 GiB (1.5%) 
           ID-1: /dev/sda vendor: Seagate model: ST3500841AS size: 465.76 GiB speed: 3.0 Gb/s serial: 3PM1RFLA rev: M 
           scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 14.91 GiB serial: AAAUE73K7YMLI6U8 rev: 1100 
           scheme: MBR 
Weather:   Temperature: 25.4 C (78 F) Conditions: Overcast clouds Wind: from NW at 1.4 m/s (5 km/h, 3 mph) Cloud Cover: 75% 
           Humidity: 72% Dew Point: 20 C (68 F) Pressure: 1013.6 mb (34 in) Location: Washington, D.C., DC, US, 20500 
           Current Time: Wed 12 Aug 2020 08:08:44 PM EDT Observation Time: 2020-08-12 19:44:00 (America/New_York -0400) 
           Source: WeatherBit.io 
Info:      Processes: 184 Uptime: 48m Memory: 7.64 GiB used: 615.1 MiB (7.9%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: konsole inxi: 3.0.36
Packages: 2348 (dpkg) 
rcmxahsk5rc@WallE:~

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 8:43 pm
by fehlix
i_ri wrote: Wed Aug 12, 2020 8:17 pm After Check for Updates the ALL will not load. Need to quit muon and open muon for ALL to show.
Can you provide pictures as I don't get this one "Need to quit muon and open muon for ALL to show. "

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 8:55 pm
by jeffreyC
tony37 wrote: Wed Aug 12, 2020 11:18 am
JayM wrote: Tue Aug 11, 2020 11:45 pm I forgot how annoying Plasma's default settings are: having to change to from icon view to compact view each time I enter a new directory in Dolphin, the 30-second shutdown confirmation delay instead of just shutting down, single-clicking opens files in their associated apps instead of just selecting them, etc.
I actually started liking single-click behavior because of all this MX KDE testing. Double-click is starting to annoy me now.
But if it so happens (no idea if this is the case) that 90% of computer users are used to double-click, it's probably more user-friendly to have double-click as default.

I also think that having separate view properties for each directory in Dolphin is confusing for most users (I always change it). Asqwerth said in post #59 he likes it and it's good the option is there but I guess it's mostly for people who have thought a bit about this, how they want to organize things etc., but having this as default leads to stuff like "hey, I put it on 'show hidden files' and now I can't see them anymore"
Just my thoughts

edit: one thing I'm missing with single-click behavior is that I can't rename the file by using a 'slow' double-click
The number one complaint about MX Xfce in comments on Distrowatch is the default single click in Thunar (it follows the Debian default but MX still gets the blame).
I would agree that most users seem to prefer double click. I know that it is the first thing I change.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 9:20 pm
by sunrat
jeffreyC wrote: Wed Aug 12, 2020 8:55 pmI would agree that most users seem to prefer double click.
Can you show your source for this assumption?
Single click rules, ok! :cool:

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Wed Aug 12, 2020 10:06 pm
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

hello fehlix
Muon
install. open muon. Check for updates.
At this point is the error. the status bar package numbers jump by 85000 total. the muon screen has not added the new found entries to a list that is seen and scrolled. click any Filter in the list by Filter left column and all cannot be projected into the list. Even a staus of 3 upgradeable when Filter click to Upgradeaable the window or list is blank. quit muon window; open muon. now all is okay.
That's not so bad.

More concerning is that the muon search box returns results Only for Installed packages.

In muon >Settings >Configure Software Sources >Updates ,Debian updates ,
there is no checkmark in the box "Security updates." Is it a concern that the Security updates checkbox is empty?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 1:31 am
by kangburra
fladd wrote: Wed Aug 12, 2020 6:31 pm I now managed to install in a VM, but it is still extremely slow. I might try one more time booting from a USB stick into the live system. If an i7 with 8GB memory is not enough to run this, then KDE is probably not for me :-)
It is a bit slow on a Chromebook with 2gb memory and 32gb drive. It is however very usable and once the program is open it is all fine. I switched from XFCE and startup times are very similar.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 4:44 am
by tony37
i_ri wrote: Wed Aug 12, 2020 10:06 pm More concerning is that the muon search box returns results Only for Installed packages.
I think you may not understand how Muon works: if during your session you clicked on 'Installed' in the 'By Status' box on the left, it will keep filtering for installed packages until you go back to that box and select 'All'. I think this kind of behavior can be highly annoying and non-intuitive for first time users. Development of Muon has been totally abandoned in favor of Discover. My impression is the latest versions of Discover are quite fine (although I don't use it much), but it's not really a Synaptic replacement.
i_ri wrote: Wed Aug 12, 2020 10:06 pm In muon >Settings >Configure Software Sources >Updates ,Debian updates ,
there is no checkmark in the box "Security updates." Is it a concern that the Security updates checkbox is empty?
That may be an issue. In MX repo manager 'deb http://deb.debian.org/debian-security buster/updates main contrib non-free' is enabled though.

An extra tidbit I noticed is that Muon can't find the changelog for the synaptic package, Synaptic can. Censorship? ;) (edit: same thing for mx-tweak, maybe Muon can't read changelogs of mx packages as synaptic version is 0.90+mx19)
One tiny advantage of Muon is that is has a separate 'box' for changelogs.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 5:32 am
by m_pav
IIRC, the install/upgrade.uninstall history displayed when right clicking the tray icon for MX Update Notifier > history, is pulled from the dpkg log files, cleaned up and put into a single cohesive display window. Synaptic simply keeps its own record of changes in your /root/.synaptic/log folder, but all changes are still recorded by dpkg, so the MXUN is IMHO the best option for checking historic DPKG logs for changes.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 5:57 am
by asqwerth
The version of Discover in Debian Buster is not very good. If you thought searching in Muon was bad, try Buster's Discover. I couldn't even search for papirus-icons in our repos using Discover (it was included in an early alpha) because once it knows you're looking for icons, it defaults to searching only in the KDE store.

I believe there was less fine grained control over which sources (repos, KDE Store, Flatpaks) you wished to search, and it was harder to distinguish the origin of the packages in search results and also in the list of updates.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 6:10 am
by tony37
I know previous versions (so also 5.14) of Discover are sloppy. But at least it gets improved, while the design failures in Muon won't ever get corrected. But of course for real package management Synaptic will still be superior to the latest Discover version. What I use Discover for in Kubuntu is mainly to have an updater (similar to MX updater) and once in a while some 'program shopping'.
And maybe I overestimated the latest Discover as looking for 'Papirus' in Kubuntu 20.04's Discover shows 'Breeze Papirus Light' as only the 9th result. Looking for 'Papirus' in 'Get New Icons' in system settings works better.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 6:13 am
by kc1di
sunrat wrote: Wed Aug 12, 2020 9:20 pm
jeffreyC wrote: Wed Aug 12, 2020 8:55 pmI would agree that most users seem to prefer double click.
Can you show your source for this assumption?
Single click rules, ok! :cool:
Single click :)

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 7:03 am
by asqwerth
Single click only in KDE Plasma, regardless of distro. I got used to it.

Double click for all other desktop environments.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 7:07 am
by tony37
jeffreyC wrote: Wed Aug 12, 2020 8:55 pm The number one complaint about MX Xfce in comments on Distrowatch is the default single click in Thunar (it follows the Debian default but MX still gets the blame).
I would agree that most users seem to prefer double click. I know that it is the first thing I change.
In an ideal world, choosing between single-click and double-click would be one of the questions asked during the install process. (People have to wait anyway so why not ask some extra useful questions)
But I suppose that would take a lot of programming to implement.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 7:44 am
by kangburra
tony37 wrote: Thu Aug 13, 2020 7:07 am
jeffreyC wrote: Wed Aug 12, 2020 8:55 pm The number one complaint about MX Xfce in comments on Distrowatch is the default single click in Thunar (it follows the Debian default but MX still gets the blame).
I would agree that most users seem to prefer double click. I know that it is the first thing I change.
In an ideal world, choosing between single-click and double-click would be one of the questions asked during the install process. (People have to wait anyway so why not ask some extra useful questions)
But I suppose that would take a lot of programming to implement.
I haven't used KDE since 3.5 (or something like that) and it's not easy to find all the settings again. It is good to learn where things are though, looking for the lock from suspend I found a GUI option to edit the grub config. There is documentation which is great.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 8:21 am
by tony37
I have a few suggestions to put in 'Popular Applications':
- in Desktop Environments: the xfce-desktop of course
- in Graphics: Krita and for people wanting something simple there's Kolourpaint
- in Utilities: Catfish (which isn't installed by default as on xfce, but version 1.4.10 should be avoided as mentioned in the beta2 thread) and Ksystemlog, which has one bug I know of: it searches for the .xsession-errors file at ~/.xsession-errors, but ~ is /root here, so this should be /home/username/.xsession-errors
- and maybe Krusader in File Managers

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 8:46 am
by sunrat
kangburra wrote: Thu Aug 13, 2020 7:44 amI haven't used KDE since 3.5 (or something like that) and it's not easy to find all the settings again. It is good to learn where things are though, looking for the lock from suspend I found a GUI option to edit the grub config. There is documentation which is great.
KDE System Settings has a decent search function.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 8:49 am
by Gerson
Seen in the forum in Spanish: (viewtopic.php?f=12&t=59795)

To see the preview (thumbnails) of opendocument documents in MX linux KDE

The solution is to install

kde-odf-thumbnail_1.0.0-4.2_amd64.deb

and then execute the next command:

$ sudo mv /usr/lib64/qt5/plugins/opendocumentthumbnail.so /usr/lib/x86_64-linux-gnu/qt5/plugins/

After that enter the Dolphin settings and enable the preview of ODF files.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 9:33 am
by tony37
@ Gerson: It works. As it's a really small package, maybe an idea to install it by default (preferably at once to the right directory).
In later versions .odt thumbnails work automatically because of an update to kio-extras.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:15 am
by kangburra
sunrat wrote: Thu Aug 13, 2020 8:46 am
kangburra wrote: Thu Aug 13, 2020 7:44 amI haven't used KDE since 3.5 (or something like that) and it's not easy to find all the settings again. It is good to learn where things are though, looking for the lock from suspend I found a GUI option to edit the grub config. There is documentation which is great.
KDE System Settings has a decent search function.
Possibly but if you type grub there are no results, so you have to know what they have called it.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:25 am
by chrispop99
kangburra wrote: Thu Aug 13, 2020 10:15 am Possibly but if you type grub there are no results, so you have to know what they have called it.
Other boot loaders are available...

Chris

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:29 am
by tony37
tony37 wrote: Thu Aug 13, 2020 9:33 am @ Gerson: It works. As it's a really small package, maybe an idea to install it by default (preferably at once to the right directory).
In later versions .odt thumbnails work automatically because of an update to kio-extras.
I couldn't help myself and tried to repackage the .deb file with the right directory. It's really the first time I do this, I used https://fabianlee.org/2018/09/28/ubuntu ... -deb-file/ as a guide. I think it worked, I added '~1' to the version number, no idea if this is the professional way of numbering, I also didn't change the changelog (but I did the change the control files), so this is just my own experiment.
I put it into a .zip file simply because I can't post .deb files here.
edit: I see the ownership of the installed files is wrong, sorry for bothering you with this.
edit2: at least this one works better

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:35 am
by kangburra
chrispop99 wrote: Thu Aug 13, 2020 10:25 am
kangburra wrote: Thu Aug 13, 2020 10:15 am Possibly but if you type grub there are no results, so you have to know what they have called it.
Other boot loaders are available...

Chris
I don't see an option to change it, back to the manual I guess.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:46 am
by chrispop99
kangburra wrote: Thu Aug 13, 2020 10:35 am
chrispop99 wrote: Thu Aug 13, 2020 10:25 am
kangburra wrote: Thu Aug 13, 2020 10:15 am Possibly but if you type grub there are no results, so you have to know what they have called it.
Other boot loaders are available...

Chris
I don't see an option to change it, back to the manual I guess.
My point is that the KDE developers don't know what boot loader will be used, so you wouldn't expect a search for any of them within the desktop settings to find anything.

Chris

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 10:49 am
by tony37
kangburra wrote: Thu Aug 13, 2020 10:35 am I don't see an option to change it, back to the manual I guess.
Don't you just want to open 'MX Boot options'?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 11:08 am
by leslie1017
I have setup a l2tp VPN in network-manager and choose save password to this user. But every time I connect to VPN it requires me to input password.
I don't use kwallet.

BTW, I have fresh install MX KDE RC1, it works flawless to me for daily work and entertainment.
MX KDE is really great work.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 11:58 am
by CyberGhost
Not sure if this is the place to post this, but I've been wondering is this version going to include Konversation the IRC chat client? I don't see it in the main menu. Also what about KDE Connect? Will that be included too? Just curious...So far no issues yet testing RC 1. I'm very impressed! Keep up the good work ya'll!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 12:12 pm
by asqwerth
Kde Connect is already installed.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 12:13 pm
by torxxl
Hello,
Excuse my English.
Do you think the final version will be out by the beginning of September.
I will set up some Linux machines and I love Mx Linux KDE

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 12:15 pm
by CyberGhost
asqwerth wrote: Thu Aug 13, 2020 12:12 pm Kde Connect is already installed.
Oh ok. I guess I didn't see it. Thanks!

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 1:38 pm
by bbfuller
Following on from my first posts in this thread.

And for anyone like me who doesn't like loose ends and who wants KMail for all it faults.

Don't install KMail.

Install kdepim instead.

It then brings in 97 other packages, two of which are KMail and the accountwizard. Among the others is the addressbook component, along with all the other "Personal Information Management" things like the calendar.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 2:53 pm
by tony37
In MX Tools 'HIde individual tools from the menu' doesn't work. Didn't test that in the beta2.
Correction: it does work after restarting plasmashell.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 2:54 pm
by fehlix
tony37 wrote: Thu Aug 13, 2020 2:53 pm In MX Tools 'HIde individual tools from the menu' doesn't work. Didn't test that in the beta2.
You need to wait some secondes until the menu system gets itself updated.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 2:57 pm
by tony37
fehlix wrote: Thu Aug 13, 2020 2:54 pm
tony37 wrote: Thu Aug 13, 2020 2:53 pm In MX Tools 'HIde individual tools from the menu' doesn't work. Didn't test that in the beta2.
You need to wait some secondes until the menu system gets itself updated.
Indeed, no restarting required.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 4:03 pm
by tony37
One thing I would really like is if MX Updater could be set to show automatically in the system area settings without changing back to 'shown'. This is simply the most natural way to go about this in KDE (instead of having to click on 'Hide until updates available' each time). I know you already solved a few bugs with MX Updater, so great work there.

And I agree with m_pav in post 138 that MX Updater's History is simply the best there is. I'm often searching in /var/log/apt/history.log but this is way easier.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 4:17 pm
by fehlix
tony37 wrote: Thu Aug 13, 2020 4:03 pm One thing I would really like is if MX Updater could be set to show automatically in the system area settings without changing back to 'shown'. This is simply the most natural way to go about this in KDE (instead of having to click on 'Hide until updates available' each time). I know you already solved a few bugs with MX Updater, so great work there.
It's doing exactly this within my system. After login and about 6 seconds the mx-updater icon is shown in systray.
Can you check the Item line

Code: Select all

grep Items= ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Also check auto-start is enabled (using right-click menu Prefrences) and disabled in saved session. There should be line
to disable "yakuake,conky,apt-notifier" with saved session.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 4:58 pm
by tony37
fehlix wrote: Thu Aug 13, 2020 4:17 pm It's doing exactly this within my system. After login and about 6 seconds the mx-updater icon is shown in systray.
I don't know if we're talking about the same thing. I only want mx-updater to be shown (on my panel) when there are updates, and hidden (but preferably in the 'system tray menu', and not as just a zombie process) when not. So like the 'Device Notifier' popping up when I plug in a USB drive, and hiding when nothing's plugged in. Is that what you mean?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 5:21 pm
by fehlix
tony37 wrote: Thu Aug 13, 2020 4:58 pm
fehlix wrote: Thu Aug 13, 2020 4:17 pm It's doing exactly this within my system. After login and about 6 seconds the mx-updater icon is shown in systray.
I don't know if we're talking about the same thing. I only want mx-updater to be shown (on my panel) when there are updates, and hidden (but preferably in the 'system tray menu', and not as just a zombie process) when not. So like the 'Device Notifier' popping up when I plug in a USB drive, and hiding when nothing's plugged in. Is that what you mean?
Ah right, I misunderstood, and thought it's always hidden not visible. Will look into this one ... later

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 5:27 pm
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

Hello dolphin_oracle
Just had a strange one time action. On power-up, RC installed just logged-in the user automatically. It is not set to do that. This one is at all defaults. First time in two decades that this has happened. The keyboard was stowed (and was yet) under the desk, so no chance I had logged-in.
Did a shutdown and power-on; it went to the dm as it should.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 5:49 pm
by fehlix
tony37 wrote: Thu Aug 13, 2020 4:58 pm
fehlix wrote: Thu Aug 13, 2020 4:17 pm It's doing exactly this within my system. After login and about 6 seconds the mx-updater icon is shown in systray.
I don't know if we're talking about the same thing. I only want mx-updater to be shown (on my panel) when there are updates, and hidden (but preferably in the 'system tray menu', and not as just a zombie process) when not. So like the 'Device Notifier' popping up when I plug in a USB drive, and hiding when nothing's plugged in. Is that what you mean?
Just checked. It's working as designed. When no packages are available for updates, you can right click on the mx-updater icon and select "Hide until updates are available". The mx-updater icon will be completely hidden, not visible in the systray nore within "systray-hidden" section. When update becomes available the icon will be visible again.
EDIT: If you want to unhide it again, regardless of the update status, click MX Updater in the menu to unhide.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 6:03 pm
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

hello tony37
Thank You for writing to clarify the expected behavior of muon searchbox. My expectation of muon searchbox behavior agrees with your description.
On two installs of RC here, muon returns search result Only for Installed packages.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 6:29 pm
by tony37
i_ri wrote: Thu Aug 13, 2020 6:03 pm hello tony37
Thank You for writing to clarify the expected behavior of muon searchbox. My expectation of muon searchbox behavior agrees with your description.
On two installs of RC here, muon returns search result Only for Installed packages.
If every box on the left is put on 'All', then I have no explanation why you'd only see installed packages.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 6:59 pm
by i_ri
.**Ignore this post; determination: installed Image corrupt.
.**Thank you all for your help. i_ri "

Status All; Categories All ;
RCmuon searchbox All resulting list never includes a package that is not installed. Only installed packages seem eligible to appear listed.

So much explaining would be not necessary if this is common. You all installed from iso and do not have this problem? I am flabbergasted. I can start another download; though the last md5sum matched.

I am into muon because I want to get it fixed-up. It needs to be perfect as the representative of the mx packaging department excellence.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 7:24 pm
by richb
curious. just installed Synaptic after searching for it and it showed immediately. I have not changed any Muon defaults. The nice thing with synaptic installed with no updates showing in MX updater, clicking on it brings up synaptic now instead of Muon. Thanks to the devs.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 7:35 pm
by tony37
One thing I noticed is that my .xsession-errors file keeps growing. It's now 10 MB from only four days.
I found out MX Xfce creates a new file every session and the old file goes to .xsession-errors.old, but that doesn't happen here.
Ubuntu-distros have the following lines in /etc/X11/Xsession to keep the file size in check:

Code: Select all

# truncate ERRFILE if it is too big to avoid disk usage DoS
if [ "`stat -c%s \"$ERRFILE\"`" -gt 500000 ]; then
  T=`mktemp -p "$HOME"`
  tail -c 500000 "$ERRFILE" > "$T" && mv -f "$T" "$ERRFILE" || rm -f "$T"
fi

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 8:16 pm
by sunrat
tony37 wrote: Thu Aug 13, 2020 7:35 pm One thing I noticed is that my .xsession-errors file keeps growing. It's now 10 MB from only four days.
I found out MX Xfce creates a new file every session and the old file goes to .xsession-errors.old, but that doesn't happen here.
Ubuntu-distros have the following lines in /etc/X11/Xsession to keep the file size in check:

Code: Select all

# truncate ERRFILE if it is too big to avoid disk usage DoS
if [ "`stat -c%s \"$ERRFILE\"`" -gt 500000 ]; then
  T=`mktemp -p "$HOME"`
  tail -c 500000 "$ERRFILE" > "$T" && mv -f "$T" "$ERRFILE" || rm -f "$T"
fi
That's a good idea. .xsession-errors does get rather huge after a while. Just checked my sid install and it's at 314MB. I have the habit of checking filesystem usage with Filelight regularly and just delete it then. It rarely holds any useful information worth keeping long-term.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 8:17 pm
by i_ri
okay richb. thanks for another quote that your muon searchbox works. asqwerth reports working. hmmmm. mine bumbling.
I picked debian. synaptic. learned from mepis; that would be you folks. Thanks. synaptic will get installed here.

Now try to make funny about muon searchbox. The installed packages list is what gets loaded on a Discover front page. (?) So maybe I have a Discover searchbox living on my muon page.

edit:Found installed image corrupt.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Thu Aug 13, 2020 9:51 pm
by i_ri
hello all
opened muon and marked muon for reinstallation. apply.
quit muon and open muon. search broken still. Shutdown and power-on. muon searchbox now showing all results include not installed packages. fixed. downloading iso again.

edit: Found installed Image corrupt.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 12:30 am
by kangburra
bbfuller wrote: Thu Aug 13, 2020 1:38 pm Following on from my first posts in this thread.

And for anyone like me who doesn't like loose ends and who wants KMail for all it faults.

Don't install KMail.

Install kdepim instead.

It then brings in 97 other packages, two of which are KMail and the accountwizard. Among the others is the addressbook component, along with all the other "Personal Information Management" things like the calendar.
Never mind. I forgot this version doesn't have the colour override.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 7:24 am
by tony37
fehlix wrote: Thu Aug 13, 2020 5:49 pm Just checked. It's working as designed. When no packages are available for updates, you can right click on the mx-updater icon and select "Hide until updates are available". The mx-updater icon will be completely hidden, not visible in the systray nore within "systray-hidden" section. When update becomes available the icon will be visible again.
EDIT: If you want to unhide it again, regardless of the update status, click MX Updater in the menu to unhide.
I understand this is the design, and in Xfce this was probably the best way to do this, but in KDE what I described is more natural, that way I don't have to click on "Hide until updates available" after each update.
But: I have no idea how easy/difficult it is to implement this.
fladd wrote: Wed Aug 12, 2020 3:30 pm Changing the panel position to left in the MX tools seems to crash plasma shell, leaving you with just a cursor.
For me it works, I just have to wait a few seconds until plasmashell is restarted.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 7:39 am
by tony37
In the manual on page 57 there is a bit about System Locales, but I can't find this anywhere in MX KDE.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 7:59 am
by dolphin_oracle
tony37 wrote: Fri Aug 14, 2020 7:39 am In the manual on page 57 there is a bit about System Locales, but I can't find this anywhere in MX KDE.
Should be in the mx-tools menu.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 8:07 am
by dolphin_oracle
tony37 wrote: Fri Aug 14, 2020 7:39 am In the manual on page 57 there is a bit about System Locales, but I can't find this anywhere in MX KDE.
you are right. for some the locales and keyboard are set to show only in Xfce.

That will be fixed in an update.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 5:44 pm
by i_ri
Hello dolphin_oracle and Everyone
That last install was on two machines deceptively corrupt.
Sorry for smudge this shiny rc. I want to blame something, so the hdd that wrote the image is out of the test loop.

difference!

MX 19ahs_KDE-RC1 on

Code: Select all

System:    Host: WallE Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-RC1_x64 patito feo August 9  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <root required> 
           Chassis: Hewlett-Packard type: 3 serial: <root required> 
           Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends v: 5.15 date: 06/25/2010 
CPU:       Topology: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP arch: Nehalem rev: 2 L2 cache: 4096 KiB 
           bogomips: 23408 
           Speed: 1317 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1317 2: 1976 3: 1568 4: 1770 
           Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm 
           dts est flush_l1d fpu fxsr ht ibpb ibrs lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe 
           pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 
           tsc vme xtopology xtpr 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0042 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel 
           port: d800 bus ID: 01:00.0 chip ID: 10ec:8168 
Drives:    Local Storage: total: 111.79 GiB used: 7.03 GiB (6.3%) 
           ID-1: /dev/sda vendor: Seagate model: ST3120813AS size: 111.79 GiB speed: 3.0 Gb/s serial: 5LS9L1X5 rev: E 
           scheme: MBR 
Weather:   Temperature: 28.9 C (84 F) Conditions: Scattered clouds Wind: from ENE at 2.2 m/s (8 km/h, 5 mph) Cloud Cover: 75% 
           Humidity: 69% Dew Point: 22.7 C (73 F) Pressure: 1003.5 mb (33 in) Location: Washington, D.C., DC, US, 20500 
           Current Time: Fri 14 Aug 2020 05:31:27 PM EDT Observation Time: 2020-08-14 17:00:00 (America/New_York -0400) 
           Source: WeatherBit.io 
Info:      Processes: 191 Uptime: 11h 20m Memory: 7.64 GiB used: 665.1 MiB (8.5%) Init: SysVinit v: 2.93 runlevel: 5 
           default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: konsole inxi: 3.0.36 
Packages: 2348 (dpkg)
rconemxkde@WallE:~
$ hello everyone      

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 9:41 pm
by Stevo
tony37 wrote: Thu Aug 13, 2020 10:29 am
tony37 wrote: Thu Aug 13, 2020 9:33 am @ Gerson: It works. As it's a really small package, maybe an idea to install it by default (preferably at once to the right directory).
In later versions .odt thumbnails work automatically because of an update to kio-extras.
I couldn't help myself and tried to repackage the .deb file with the right directory. It's really the first time I do this, I used https://fabianlee.org/2018/09/28/ubuntu ... -deb-file/ as a guide. I think it worked, I added '~1' to the version number, no idea if this is the professional way of numbering, I also didn't change the changelog (but I did the change the control files), so this is just my own experiment.
I put it into a .zip file simply because I can't post .deb files here.
edit: I see the ownership of the installed files is wrong, sorry for bothering you with this.
edit2: at least this one works better
I have openoffice document thumbnails already in Dolphin without that Ubuntu package, but some research hints that's because I also have Calligra installed, which provides some thumbnailers.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Fri Aug 14, 2020 11:52 pm
by i_ri
Image
Hello dolphin_oracle and everyone
Very crisp. .

here Look, launcher, dashboard, menu still on window key and also screen corner; those mx logo now everywhere. Got full path into dolphin titlebar. user manager has given user avatar "notme"
neofetch reports the icon as breeze based on widgets set at breeze(?); the system icons are set adwaita, yes a few are missing. no care. got text black except active titlebar. active screen edges. pagers on desktopS grid is fantastic.
LiKe it. Nice K, MX.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 12:54 am
by kangburra
i_ri wrote: Fri Aug 14, 2020 11:52 pm Image
Hello dolphin_oracle and everyone
Very crisp. .

here Look, launcher, dashboard, menu still on window key and also screen corner; those mx logo now everywhere. Got full path into dolphin titlebar. user manager has given user avatar "notme"
neofetch reports the icon as breeze based on widgets set at breeze(?); the system icons are set adwaita, yes a few are missing. no care. got text black except active titlebar. active screen edges. pagers on desktopS grid is fantastic.
LiKe it. Nice K, MX.
I have many of the same settings and yet so different. Very happy with how it is all going though.
Screenshot_20200815_065150.png

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 6:31 am
by i_ri
Hello dolphin_oracle and everyone
hello kangburra, i will raise you an applet, if you will throw in a cashew.
Image
image of capturerightcenterthatsrc.
This is a big screen to traverse with a touchpad.
put open controls on the side where are scroll and close button controls. window list at end of tasks. notifications panel can expand. top panel for only minimized windows listed there.windows and even f4yakuake and runner visible under ( not below?) respecting top panel. not sure if pinned is a good fit for minimized only(?.) no live preview will be in top task panel. live preview of non-minimized windows in bottom task panel. show desktop in panel adjacent Dashboard icon in desktop. Menu that far to the right forces submenus to pop out on left, toward center. seems tighter mousing.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 7:48 am
by gsm
I compared the speed of the live systems MX-19.2 KDE RC 1 and KDE neon on my HP Mini 110 netbook with 2GB memory and SSD drive, where MX 19 XFCE runs just fine.
I just opened the Settings manager to only choose another theme, etc. Reaction time was very slow.
Both live systems seem much to slow in comparison to the live MX-19 XFCE and of course very much slower then the installed MX-19 XFCE.
However the KDE neon live performance seems to be much better then the MX-19.2 KDE RC 1 live system performance.
Perhaps the performance of MX-19.2 KDE could still be improved?

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 8:16 am
by chrispop99
gsm wrote: Sat Aug 15, 2020 7:48 am I compared the speed of the live systems MX-19.2 KDE RC 1 and KDE neon on my HP Mini 110 netbook with 2GB memory and SSD drive, where MX 19 XFCE runs just fine.
I just opened the Settings manager to only choose another theme, etc. Reaction time was very slow.
Both live systems seem much to slow in comparison to the live MX-19 XFCE and of course very much slower then the installed MX-19 XFCE.
However the KDE neon live performance seems to be much better then the MX-19.2 KDE RC 1 live system performance.
Perhaps the performance of MX-19.2 KDE could still be improved?

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
You have answered your own question.

Chris

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 8:26 am
by kangburra
gsm wrote: Sat Aug 15, 2020 7:48 am

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
I also tried neon and many things are not as stable as the MX RC, well done to the devs at MX.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 8:38 am
by asqwerth
gsm wrote: Sat Aug 15, 2020 7:48 am I compared the speed of the live systems MX-19.2 KDE RC 1 and KDE neon on my HP Mini 110 netbook with 2GB memory and SSD drive, where MX 19 XFCE runs just fine.
I just opened the Settings manager to only choose another theme, etc. Reaction time was very slow.
Both live systems seem much to slow in comparison to the live MX-19 XFCE and of course very much slower then the installed MX-19 XFCE.
However the KDE neon live performance seems to be much better then the MX-19.2 KDE RC 1 live system performance.
Perhaps the performance of MX-19.2 KDE could still be improved?

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
Were you referring to the overall KDE Neon live performance being "better", or just the startup/bootup?

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 9:02 am
by tony37
kangburra wrote: Sat Aug 15, 2020 8:26 am
gsm wrote: Sat Aug 15, 2020 7:48 am

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
I also tried neon and many things are not as stable as the MX RC, well done to the devs at MX.
I think it helps a lot using Debian stable.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 9:40 am
by kangburra
tony37 wrote: Sat Aug 15, 2020 9:02 am
kangburra wrote: Sat Aug 15, 2020 8:26 am
gsm wrote: Sat Aug 15, 2020 7:48 am

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
I also tried neon and many things are not as stable as the MX RC, well done to the devs at MX.
I think it helps a lot using Debian stable.
To be honest I forgot I am testing this and am just using it like a production release. I installed it on several machines and maybe should have waited. :eek:

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 10:36 am
by tony37
gsm wrote: Sat Aug 15, 2020 7:48 am I compared the speed of the live systems MX-19.2 KDE RC 1 and KDE neon on my HP Mini 110 netbook with 2GB memory and SSD drive, where MX 19 XFCE runs just fine.
I just opened the Settings manager to only choose another theme, etc. Reaction time was very slow.
Both live systems seem much to slow in comparison to the live MX-19 XFCE and of course very much slower then the installed MX-19 XFCE.
However the KDE neon live performance seems to be much better then the MX-19.2 KDE RC 1 live system performance.
Perhaps the performance of MX-19.2 KDE could still be improved?

Remark: MX-19.2 KDE RC 1 looks stable, while KDE neon gives each time after a fresh boot a startup message that kwin crashed.
One thing to keep in mind with the live system is that on first boot RC1 seems to take a lot of time (and CPU, see conky) to check for updates. MX Xfce's live system doesn't do this as far as I can see in VB.
Another thing I noticed: the application menu is semi-transparent in the live session, but not transparent on my installed system. And I can't find a setting to change this transparency.
edit: But this transparency is only in virtualbox, not in a 'normal' live session. I also have the impression that 'kwin' and 'Xorg' are way more active in virtualbox than normally: just look at their CPU usage when you go through the application menu. Maybe some special effects enabled in virtualbox.

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 11:50 am
by MAYBL8
I need a lesson in how to do something in KDE:
I have a NAS attached to my network and when I use Thunar and select browse network I see the NAS.
I can submit screen captures if you need them.

When I use Dolphin and select network I don't see the NAS.
I see Bluetooth, MTP Devices, Network, Shared Folders (SMB), Add Network Folder

Obviously it isn't as easy as Thunar.
Can anyone point me in the direction to make this work.

I can open another post somewhere on the forum for this but this seemed like the correct place since I was testing MX-KDE

Re: MX-19.2 KDE RC 1 Feedback Thread

Posted: Sat Aug 15, 2020 11:56 am
by Eadwine Rose
Please repost once Final is released. Thread closed pending the release.