Bug 136150

Summary:	automatic resolution of accelerator keys selects special characters (p.e. ü)
Product:	[Unmaintained] kdelibs	Reporter:	Pau Tallada Crespí <pau_tallada>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	aacid
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pau Tallada Crespí 2006-10-22 23:35:23 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I'm a translator ok Amarok.
In latests versions, it has a dialog with a lot of accelerators (19 distinct) and the automatic accelerator key conflict resolution selected the letter «ü» from the word «Següent» (Next) as one of the accelerators.

I've tried to use that accelerator probing all type of combinations using the keyborad, but unsucessfully.

So if this type of accelerator cannot be used through keyboard, should not be selected at all from the automatic conflict resolution.

Thanks in advance!

Pau Tallada.

Comment 1 Albert Astals Cid 2006-10-23 19:25:25 UTC

To clarify the problem, ü can only be typed in catalan using Shift+key that has the two points and then pressing u. I think it is difficult or impossible to detect that as that depends on the keyboard layout, maybe the bug is Qt not detecting the accelerator has been pressed?

Comment 2 Andrew Crouthamel 2018-11-02 04:26:22 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-16 02:41:40 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 4 Justin Zobel 2022-12-07 00:23:48 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2022-12-22 05:18:50 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Christoph Cullmann 2024-09-14 17:06:49 UTC

Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have resolved this bug.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann