Bug 217299 - Problem with /usr/share/X11/xkb/symbols/inet
Problem with /usr/share/X11/xkb/symbols/inet
Product: Fedora
Classification: Fedora
Component: xkeyboard-config (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
Depends On: 237369
  Show dependency treegraph
Reported: 2006-11-26 13:51 EST by Patrick
Modified: 2008-08-02 19:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-15 09:40:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
FreeDesktop.org 7095 None None None Never

  None (edit)
Description Patrick 2006-11-26 13:51:57 EST
In section logitech_base, the file /usr/share/X11/xkb/symbols/inet contains 
XF86AudioMedia and XF86AudioRaiseVolume twice. This prevented me from using 
the corresponding keys under KDE. Commenting one occurance resolved the 
Comment 1 Marcin Garski 2007-04-21 09:17:19 EDT
This bug is fixed in xkeyboard-config-0.9.
Comment 2 Matěj Cepl 2007-10-31 17:40:34 EDT
Reporter, could you confirm comment 1? Are you able to reproduce the issue with
the latest upgraded version of FC6 (or any later distro)?
Comment 3 Matěj Cepl 2007-12-10 04:23:16 EST
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
Comment 4 Matěj Cepl 2008-01-15 09:40:21 EST
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional


{This is mass-closing of all obsolete bugs; if this bug was in your opinion
closed by mistake, please, reopen it with additional information; thanks a lot
and I am sorry for bothering you in such case.}

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