Re: kde-gtk-config Plasma/5.27 build failure

[Fusion Future]

https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/94 should 
fix it. Sorry for not checking GLib version beforehand.

plasma-workspace: Backport recommendation to fix potential crash when closing Plasma popup

[Fusion Future]

Dear distro maintainers:

This patch fixes a potential crash when user closes a Plasma popup on 
Wayland. Please consider backporting the patch to plasma-workspace 
5.27.7. Thank you.


https://invent.kde.org/plasma/plasma-workspace/-/commit/fc01a7f837d06ee9e92d02f13acb79c2b06e9e3c

which fixes https://bugs.kde.org/show_bug.cgi?id=473054

Re: Do you use votes on Bugzilla tickets to help you make decisions?

[Fusion Future]

I do vote on Bugzilla, but given the limited development resource, I 
find vote less useful than the number of duplicates or CCs.

Re: Plasma 5.27.4 backport recommendation to fix oversized title buttons in GTK3 apps

[Fusion Future]

On 2023/4/9 10:06, Fusion Future wrote:
https://invent.kde.org/plasma/breeze-gtk/-/commit/c5e757a198321208c6b1e99313652577c263ecc0 
<https://github.com/sddm/sddm/pull/1603>


Ignore the link to sddm

Plasma 5.27.4 backport recommendation to fix oversized title buttons in GTK3 apps

[Fusion Future]

This commit partially reverts a previous change in Breeze GTK theme.

https://invent.kde.org/plasma/breeze-gtk/-/commit/c5e757a198321208c6b1e99313652577c263ecc0
  

The previous commit attempts to make title buttons in GTK3 apps 
clickable even at the edges but it makes title buttons in GTK3 apps on 
Wayland look oversized and blurry when scaling is 100%.


Sorry for the disruption.

plasma-workspace now requires passing tests in Plasma/5.27 branch

[Fusion Future]

Hi,

After 
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2605 has 
been merged, plasma-workspace now requires passing tests in Plasma/5.27 
branch to avoid unintentional changes that cause regressions. Please 
create a merge request when cherry-picking any commit to Plasma/5.27. 
Thanks in advance.

wayland-protocols 1.31 is a new optional dependency for plasma-workspace 5.27.0

[Fusion Future]

Hi,

In 5.27.0 wayland-protocols becomes an optional dependency for 
plasma-workspace because it was added after the hard freeze date. But 
enabling wayland-protocols build dependency can make XEmbed on Wayland 
work properly.


See also: 
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2503


and

https://bugs.kde.org/show_bug.cgi?id=448050

Please consider adding wayland-protocols 1.31 to your build environment. 
Thanks for reading.

Re: Soft Feature Freeze Approaching

[Fusion Future]

Is it possible to make Hebrew/Jewish calendar available in Plasma 5.27? 
The code is largely borrowed from the Indian calendar backend so the 
actual change is small.


https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/313

Re: Frameworks 6 Branching

[Fusion Future]

On 2022/12/19 20:17, Volker Krause wrote:

 From that point on, KDE Frameworks 5 is considered feature-frozen, feature
work should continue to happen in the master branch, primarily targeting KF6
then.
If I merge a merge request now in Frameworks group now, will the change 
exist in KF5.102, or KF6?

New optional build dependencies in Plasma 5.26

[Fusion Future]

Hello,

There are 3 additional optional build dependencies introduced in Plasma 
5.26:


1. KF5KExiv2: 
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1852
2. KF5NetworkManagerQt: 
https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/207
3. libicu-devel >= 66: 
https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/112


Though the two packages can still be built without those libraries, it's 
still advised to add those build dependencies, to provide a complete 
Plasma experience.


Thank you for reading this.

Re: kcm_bluetooth changed ?

[Fusion Future]

On 2022/2/13 21:31, Martin Koller wrote:

But still I wonder if such a change is something like breaking ABI 
compatibility.
If KDE/plamsa is such a moving target where I can not rely on compatibility even
between minor versions, that is really not fun.



Perhaps the breakage is due to these commits [1-3]. Need to ask 
Alexander Lohnau if there is a proper solution. I added him to the Cc list.


Sorry for the inconvenience.

[1] 
https://invent.kde.org/plasma/bluedevil/-/commit/ac71faf781e1b3690f33bf54f27eeaaee7ec30e3
[2] 
https://invent.kde.org/plasma/bluedevil/-/commit/87ad90b54592817d77d50c4284ff899659fa0550
[3] 
https://invent.kde.org/plasma/bluedevil/-/commit/62856fe4d95ab4c1b795cf487ea0dbc61459412c

Re: kcm_bluetooth changed ?

[Fusion Future]

On 2022/2/13 20:20, Martin Koller wrote:

I already tried this but it did not solve the issue.


This code snippet works on my system. Please have a try.

```cpp
dialog = new KCMultiDialog();

KPluginMetaData 
module(QPluginLoader("plasma/kcms/systemsettings/kcm_bluetooth"));

if (!module.name().isEmpty())
dialog->addModule(module);

dialog->show();
```

Re: kcm_bluetooth changed ?

[Fusion Future]

On 2022/2/13 05:46, Martin Koller wrote:

What has changed and how would I now use the new KCM in a KCMultiDialog ?


It can be changed to "kcm_bluetooth". Please see [1] to see if that helps.

[1] https://invent.kde.org/plasma/bluedevil/-/merge_requests/49

[Usability] Possible to provide an option or a sugeestion in KScreen to (guide the user to) enable "PLASMA_USE_QT_SCALING"?

[Fusion Future]

Currently, Plasma on X11 disables `PLASMA_USE_QT_SCALING` by default to 
avoid some more serious bugs (and many of them have been fixed [1]).


Bug 356446 [2] was marked "RESOLVED INTENTIONAL"  because "it breaks 
mixed-DPI screen arrangements" and there seems no way to overcome the 
defect because of design flaws in upstream X11 library (if I understand 
it correctly).


However, for any user who has only one screen or has multiple screens 
with the same DPI value, and has to use X11 for whatever reason, the 
visual experience becomes much worse after the user changes the global 
scale factor and finds Plasma Desktop (or plasmashell) doesn't scale 
correctly.


The problem can be alleviated by setting "PLASMA_USE_QT_SCALING=1" 
environment variable, but the user may not be aware of that variable 
when changing the scale factor and therefore leave a bad impression on 
Plasma Desktop.


==

I have some suggestions to help the user understand why the environment 
variable is not set by default:


1. Inform the user that Plasma Desktop will not obey the scale factor 
when changing the value in KScreen KCM, and the technical reason.


2. Show an inline message to guide the user to add 
"PLASMA_USE_QT_SCALING=1" in the environment variable list, and possible 
consequences of doing so.


3. If possible, KScreen can provide an option to directly enable it when 
the current session uses X11. [3]


(But where should the setting be saved? "~/.profile" or a config file 
like "startkderc"? The latter may require modifying 
"plasma-workspace/startkde/startplasma.cpp". I am not familiar with how 
the start process works so I just put some ideas here.)


I am not sure if my suggestions are applicable. Any ideas are welcome!

==

References:

[1] https://bugs.kde.org/show_bug.cgi?id=356446 (See "Depends on")
[2] https://bugs.kde.org/show_bug.cgi?id=356446#c70
[3] https://bugs.kde.org/attachment.cgi?id=146517

Re: 5.24 as LTS

[Fusion Future]

As a contributor I would like to say using 5.18 is fine as long as there 
are still active backports, but **using Qt 5.12** is problematic and 
many programs has requirement on 5.15 nowadays.


To my knowledge openSUSE Leap 15.3 is still using Qt 5.12 to keep 
compatibility with Plasma 5.18, as a result, some latest programs cannot 
be packed for Leap 15.3 anymore.

Re: Where can I find wayland-plasma-shell-client-protocol.h

[Fusion Future]

It seems I have to build the project first in order to generate those files.

Thank you for reminding.

Tom Zander  于2021年11月20日周六 下午10:34写道：
>
> On zaterdag 20 november 2021 03:19:56 CET Fusion Future wrote:
> > I was studying kwayland/src/client/plasmashell.cpp, but a
> > header file named `wayland-plasma-shell-client-protocol.h` is
> > missing.
> >
> > I ran `zypper se -f wayland-plasma-shell-client-protocol.h` and
> > found that kwayland-debugsource is the package that provides
> > the file. But the file is empty.
> >
> > The question is where can I find
> > wayland-plasma-shell-client-protocol.h?
> >
> > Thanks in advance.
>
> THat file is generated by `wayland-scanner`, according to the
> generated file in my build dir.
> In Arch this tool is owned by the 'wayland' package.
>
>
>

Where can I find wayland-plasma-shell-client-protocol.h

[Fusion Future]

I was studying kwayland/src/client/plasmashell.cpp, but a header file
named `wayland-plasma-shell-client-protocol.h` is missing.

I ran `zypper se -f wayland-plasma-shell-client-protocol.h` and found
that kwayland-debugsource is the package that provides the file. But
the file is empty.

The question is where can I find wayland-plasma-shell-client-protocol.h?

Thanks in advance.