MX-19.2 KDE Beta 2 Feedback Thread
Re: MX-19.2 KDE Beta 2 Feedback Thread
my thoughts about Muon:
I don't like Muon's interface for two reasons: 1) It doesn't have search history. 2) The filters can be irritating, for example: you first want to look at all upgradeable packages, so far so good, but then you want to look at, say, all mathematics packages. If you'd click like in Synaptic, in Muon you'd see ... all upgradeable mathematics packages. I think Muon is fine if you want to look at one and only one package (but why not use MX Installer then?), not if you want to look at several. I understand you'd prefer to have KDE programs on a KDE desktop, but I can't do with Muon what I can with Synaptic, and I'm talking about pretty basic stuff like searching for more than one package.
Unless I'm a total idiot and couldn't find Muon's search history all this time.
One advantage of Muon though is that the categories are more user-friendly, in Synaptic you have separate categories for 'contrib' and 'non-free'. But I rarely use these categories anyway.
PS: Congratulations with having the conky work flawlessly in KDE, I never managed to get this right.
I don't like Muon's interface for two reasons: 1) It doesn't have search history. 2) The filters can be irritating, for example: you first want to look at all upgradeable packages, so far so good, but then you want to look at, say, all mathematics packages. If you'd click like in Synaptic, in Muon you'd see ... all upgradeable mathematics packages. I think Muon is fine if you want to look at one and only one package (but why not use MX Installer then?), not if you want to look at several. I understand you'd prefer to have KDE programs on a KDE desktop, but I can't do with Muon what I can with Synaptic, and I'm talking about pretty basic stuff like searching for more than one package.
Unless I'm a total idiot and couldn't find Muon's search history all this time.
One advantage of Muon though is that the categories are more user-friendly, in Synaptic you have separate categories for 'contrib' and 'non-free'. But I rarely use these categories anyway.
PS: Congratulations with having the conky work flawlessly in KDE, I never managed to get this right.
Re: MX-19.2 KDE Beta 2 Feedback Thread
Issue of icons not showing up for Vivaldi (menu+panel), even with another theme, resolved (at least for MX theme) with reboot.
Re: MX-19.2 KDE Beta 2 Feedback Thread
From my experience:danielson wrote: Mon Jul 20, 2020 6:24 am Issue of icons not showing up for Vivaldi (menu+panel), even with another theme, resolved (at least for MX theme) with reboot.
If you pin additional apps to the panel and were using another icon theme, and then applied the MX global theme (thus changing the icon set back):
1. with the option to apply the default MX layout checked - you may have an issue with your own pinned apps showing up as a blank "??" icon since the default MX layout will not have those apps pinned to the panel.
2. with the option to apply default MX layout NOT checked - the icons you pinned should continue to be on the panel, just with the icon set changed.
However, when you freshly install and immediately apply the said new icon themes, sometimes they don't all show up properly in the menu or panel without a logout and in again.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX-19.2 KDE Beta 2 Feedback Thread
I have run into the situation where panel icons disappear when a new icon set is chosen. That is an icon will not show but leave a blank space. Rebooting does correct that. but also the following will work without a reboot Run these commands in succession in a terminal. The first command clears the desktop including panels. The second restores them after a slight delay. Also the second command continues to run in the terminal after the desktop is restored. Just close the terminal.
Code: Select all
killall plasmashell
kstart plasmashell
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
- dolphin_oracle
- Developer
- Posts: 22114
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE Beta 2 Feedback Thread
tony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.
Let me know.how.to trigger the apply of settings changes to plasmashell and I'll do it that way instead of resetting plasmashell.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-19.2 KDE Beta 2 Feedback Thread
can't help you there, sorrydolphin_oracle wrote: Mon Jul 20, 2020 7:46 amtony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.
Let me know.how.to trigger the apply of settings changes to plasmashell and I'll do it that way instead of resetting plasmashell.
- dolphin_oracle
- Developer
- Posts: 22114
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE Beta 2 Feedback Thread
that's why I'm using the built-in plasmashell --replace function. Its the same thing Look-and-feel does. Its overkill, but its the only way outside the actual settings applications to do it. I presume there may be a dbus call you can make to trigger reload of configurations, but if there is I haven't been able to craft a working version.tony37 wrote: Mon Jul 20, 2020 7:53 amcan't help you there, sorrydolphin_oracle wrote: Mon Jul 20, 2020 7:46 amtony37 wrote: The single/double-click toggle is already there. It works, but when clicking on 'apply' I think it restarts plasmashell, which isn't necessary because switching the settings the 'normal' way doesn't do this and also works.
.
Let me know.how.to trigger the apply of settings changes to plasmashell and I'll do it that way instead of resetting plasmashell.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-19.2 KDE Beta 2 Feedback Thread
I understand, it's not a big problem.dolphin_oracle wrote: Mon Jul 20, 2020 7:59 am that's why I'm using the built-in plasmashell --replace function. Its the same thing Look-and-feel does. Its overkill, but its the only way outside the actual settings applications to do it. I presume there may be a dbus call you can make to trigger reload of configurations, but if there is I haven't been able to craft a working version.
@ danielson, asqwerth, richb: the icon theme not fully resetting is typical for Plasma, nothing MX-related, a bit faster than rebooting is logout+login, restarting plasmashell like richb suggests also works, maybe this should happen automatically (small detail: in later Plasma versions "kstart plasmashell" doesn't work, it should be "kstart5 plasmashell" there, so if someone wants to write code for this, better to already use kstart5 to avoid problems later on)
Re: MX-19.2 KDE Beta 2 Feedback Thread
@richb - thank you!
@asqwerth - the initial 'invisible' icons (menu+panel) was just after installing Vivaldi (with default MX theme).
At one point, saw the panel icon but still no menu one.
Anyhow, temporary solutions will do the trick and do appreciate your feedback!
- - -
Oddly enough, it didn't do this for Brave.
@asqwerth - the initial 'invisible' icons (menu+panel) was just after installing Vivaldi (with default MX theme).
At one point, saw the panel icon but still no menu one.
Anyhow, temporary solutions will do the trick and do appreciate your feedback!
- - -
Oddly enough, it didn't do this for Brave.
Re: MX-19.2 KDE Beta 2 Feedback Thread
Something I've never been able to find out is how to change the single-click behavior of Dolphin when opened as root. Might be a tad dangerous if someone is used to double-click and in root mode this changes in single-click. That would be a useful addition to MX Tweak, if possible.
edit: I finally found how to do this: add in /root/.config/kdeglobals under the [KDE] header
If there is no such file, like in MX KDE, create one with following content:
edit: I finally found how to do this: add
Code: Select all
SingleClick=false
If there is no such file, like in MX KDE, create one with following content:
Code: Select all
[KDE]
SingleClick=false