[Bug 246331] [exp-run] Update KDE Frameworks to 5.70.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246331 Bug ID: 246331 Summary: [exp-run] Update KDE Frameworks to 5.70.0 Product: Ports & Packages Version: Latest Hardware: Any URL: https://github.com/freebsd/freebsd-ports-kde/tree/kf5- 5.70 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: port...@freebsd.org Reporter: tcber...@freebsd.org CC: k...@freebsd.org Flags: exp-run? Created attachment 214311 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214311&action=edit v1 Moin moin kde@ would like to ask for an exp-run to upgrade KF5 to 5.70.0. The patch is attached, and can also be found here: https://people.freebsd.org/~tcberner/patches/kf5-5.70.0.v1.diff mfg Tobias -- You are receiving this mail because: You are on the CC list for the bug.
Re: weird problem with 'win' key
On 04/05/2020 10:23, Andriy Gapon wrote:
> Those \t entries were a red herring.
> From a cursory look through the code I see that \t is indeed a separator used
> by
> kglobalaccel to multiple separate key combinations assigned to the same action
> and type (default, custom). Not sure if the UI supports such multiple
> combinations, but the backend certainly does.
>
> Anyway, more importantly, simply restarting kglobalaccel ('kquitapp5
> kglobalaccel ; kglobalaccel5 &') fixes the meta key shortcuts, no need to edit
> kglobalshortcutsrc.
>
> So, it must be something in startup code of some kde/plasma component that
> messes up "Meta" key.
> But what and how?..
Good news.
After a recent update from 5.18.4.1 to 5.18.5 the problem is gone.
--
Andriy Gapon
Re: weird problem with 'win' key
Glad to hear :)
mfg Tobias
On Sat, 9 May 2020 at 17:46, Andriy Gapon wrote:
>
> On 04/05/2020 10:23, Andriy Gapon wrote:
> > Those \t entries were a red herring.
> > From a cursory look through the code I see that \t is indeed a separator
> > used by
> > kglobalaccel to multiple separate key combinations assigned to the same
> > action
> > and type (default, custom). Not sure if the UI supports such multiple
> > combinations, but the backend certainly does.
> >
> > Anyway, more importantly, simply restarting kglobalaccel ('kquitapp5
> > kglobalaccel ; kglobalaccel5 &') fixes the meta key shortcuts, no need to
> > edit
> > kglobalshortcutsrc.
> >
> > So, it must be something in startup code of some kde/plasma component that
> > messes up "Meta" key.
> > But what and how?..
>
> Good news.
> After a recent update from 5.18.4.1 to 5.18.5 the problem is gone.
>
> --
> Andriy Gapon
