Bug 1353046 - XkbSetBounceKeysDelay has a man page, but isn't in the libraries
Summary: XkbSetBounceKeysDelay has a man page, but isn't in the libraries
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: libX11
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-05 21:53 UTC by Göran Uddeborg
Modified: 2019-09-26 16:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-26 16:45:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab xorg/lib/libx11/issues/105 0 None None None 2019-09-26 16:45:09 UTC

Description Göran Uddeborg 2016-07-05 21:53:18 UTC
Description of problem:
While trying to do something about a remote control where the keys are generating bounces, aunt Google pointed me to the XkbSetBounceKeysDelay function.  I didn't quite understand the man page for it, but I started out to write a little program to see if I could figure it out.

It turns out that I can't compile and link the program.  The libraries do not include the symbol, nor is it a #define in any header file I can find.  This seems inconsistent, and I guess it is a bug somewhere.


Version-Release number of selected component (if applicable):
libX11-1.6.3-3.fc24 (and d:o -devel and -common)


Steps to Reproduce:
1. man XkbSetBounceKeysDelay
2. cc <program referencing XkbSetBounceKeysDelay> -lX11 


Actual results:
The first command returns what appears to be a valid manual page, but the second command fails.


Expected results:
Either the libraries should include the function, or no manual page should be there indicating they do.


Additional info:
If anyone has a better pointer on how to manage a remote control that generates key bounces than Google, I'm all ears! :-)

Comment 1 Fedora End Of Life 2017-07-25 21:36:53 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Göran Uddeborg 2017-07-27 14:31:10 UTC
The inconsistency remains in F26

libX11-devel-1.6.5-2.fc26.x86_64

Comment 3 Fedora End Of Life 2018-05-03 08:39:05 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Göran Uddeborg 2018-05-15 08:46:17 UTC
The discrepancy remains in F28.

libX11-devel-1.6.5-7.fc28.x86_64

Comment 5 Ben Cotton 2019-05-02 21:46:44 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Göran Uddeborg 2019-05-12 17:50:09 UTC
The inconsistency remains in F26.

libX11-1.6.7-1.fc30.x86_64
libX11-devel-1.6.7-1.fc30.x86_64

Comment 7 Adam Jackson 2019-09-26 16:45:09 UTC
That's amazing. As far as I can tell that function has _never_ existed in libX11.

I've filed a bug upstream:

https://gitlab.freedesktop.org/xorg/lib/libx11/issues/105

Unfortunately I don't have any suggestions for a better API for you to use, I'm not
especially familiar with XKB. Following up on the upstream bug might be your best bet.

Comment 8 Göran Uddeborg 2019-09-26 16:53:53 UTC
Thanks, I'll follow the upstreams report.


Note You need to log in before you can comment on or make changes to this bug.