Bug 1780463
| Summary: | [RHEL8.2 Alpha] The message log shows 'Internal error: Could not resolve keysym XF86MonBrightnessCycle' | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Adrian Huang <ahuang12> | ||||||||||
| Component: | xorg-x11-xkb-utils | Assignee: | Peter Hutterer <peter.hutterer> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 8.2 | CC: | bugproxy, hannsj_uhl, jstodola, nospam, peter.hutterer, tpelka, yzheng | ||||||||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||||||||
| Target Release: | 8.3 | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | xorg-x11-xkb-utils-7.7-28.el8 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2020-11-04 03:28:41 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1660905, 1776265, 1852769 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Adrian Huang
2019-12-06 05:04:12 UTC
This error message is harmless, it just means that where the default keymap includes either of those keys, they cannot be resolved and thus do not actually do anything. Unless you laptop has media keys that produce the required keycodes, the effect is nil. On the technical side: the cause is simply that the xorg-x11-proto-devel release is older than xkeyboard-config release. To fix this, we would have to add the symbols to xorg-x11-proto-devel and then rebuild libX11 with those symbols. (In reply to Peter Hutterer from comment #1) > This error message is harmless, it just means that where the default keymap > includes either of those keys, they cannot be resolved and thus do not > actually do anything. Unless you laptop has media keys that produce the > required keycodes, the effect is nil. Yes. I understand the error message is harmless since it shows 'Errors from xkbcomp are not fatal to the X server'. > On the technical side: the cause is simply that the xorg-x11-proto-devel > release is older than xkeyboard-config release. To fix this, we would have > to add the symbols to xorg-x11-proto-devel and then rebuild libX11 with > those symbols. Will this be made in the upcoming releases of RHEL8.2 (beta/snapshot/RC/GA)? "not fatal" is still different to "harmless" in many cases, so my explanation was mostly that this really doesn't matter :) It is unlikely that this will be fixed for 8.2 though. If this won't be fixed for 8.2, would it be possible to have the doc to indicate this error can be ignored safely (via Red Hat Knowledge Base)? Commenting out offending lines in /usr/share/X11/xkb/symbols/inet squelches the message. It would be nice if the error could be downgraded to a warning with some doc. *** Bug 1778063 has been marked as a duplicate of this bug. *** ------- Comment From kalshett.com 2019-10-20 12:06 EDT------- (In reply to comment #4) > Installation Can be done successfully and warning messages mentioned in > defect did not interrupted installation > > ---Problem Description--- > > RHEL 8.1 (Boston/P9) : Warning while Installation : (anaconda:6501): > Gtk-WARNING **: 23:04:27.598: Attempt to load unknown IM context type > > ---Environment---- > > Kernel Build: RHEL8.1 RHEL-8.1.0-InternalSnapshot-2.1/ > System Name : Boston > Model/Type : P9 > Platform : BM (Boston 54) > > ---Steps to reproduce---- > > 1) Starting Installation > 2) Connect to VNC > 3) Proceed with install and when the installation is going in..in console > below warning messages can be seen > > 23:49:06 Please manually connect your vnc client to > ltc-boston54.aus.stglabs.ibm.com:1 (9.40.193.165:1) to begin the install. > 23:49:06 Attempting to start vncconfig > > (anaconda:6501): Gtk-WARNING **: 16:52:21.552: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 16:52:21.552: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:54:22.761: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:54:22.762: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:54:53.375: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:54:53.375: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:57:38.830: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 22:57:38.831: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:01:35.830: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:01:35.830: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:02:19.041: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:02:19.041: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:03:09.630: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:03:09.630: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:03:58.502: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:03:58.502: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:04:27.598: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:04:27.598: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:06:40.569: Attempt to load unknown IM > context type '' > > (anaconda:6501): Gtk-WARNING **: 23:06:40.569: Attempt to load unknown IM > context type '' > > [anaconda]1:main* 2:shell 3:log 4:storage-log >Switch tab: Alt+Tab | Help: > F1 Are we planning to fix this in future ? ------- Comment From preeti.thakur.com 2019-10-21 03:21 EDT------- By when we can expect fix for this issue? ------- Comment From sthoufee.com 2019-12-10 02:19 EDT------- Redhat, Is there any update on this issue ? ------- Comment From sthoufee.com 2019-12-31 01:58 EDT------- We are seeing similiar issue with RHEL 8.2 Alpha as well. ------- Comment From preeti.thakur.com 2020-01-07 00:44 EDT------- is there any update on this defect? ------- Comment From preeti.thakur.com 2020-02-07 02:31 EDT------- with RHEL8.2 BETA 1 Seeing below msg (anaconda:3116): Gtk-WARNING **: 02:20:44.734: Theme parsing error: <data>:1:75: The 'gtk-key-bindings' property has been renamed to '-gtk-key-bindings' ------- Comment From preeti.thakur.com 2020-03-24 03:41 EDT------- no update on this defect since long, kindly keep us updated. ------- Comment From preeti.thakur.com 2020-03-31 04:49 EDT------- With RHEL 8.2 (snapshot 3) Its a different error as msg shown below, the defect for which already exist. "Could not resolve keysym XF86MonBrightnessCycle" tried with RHEL 8.1 GA on boston ( boston 54) and issue is not seen now. ------- Comment From sthoufee.com 2020-03-31 05:44 EDT------- *** This bug has been marked as a duplicate of bug 182623 *** ------- Comment From preeti.thakur.com 2020-04-16 05:47 EDT------- any update here? ------- Comment From viparash.com 2020-01-03 01:08 EDT------- Hello Redhat, Any update on this ? ------- Comment From mainamdar.com 2020-01-07 00:51 EDT------- *** Bug 182705 has been marked as a duplicate of this bug. *** ------- Comment From kribalac.com 2020-01-29 02:56 EDT------- This issue is seen on rhel8.2-beta1 [kernel-4.18.0-167.el8.ppc64le] also on lpar jeeplp82 with direct FC adapter. Any update on this defect? ------- Comment From chetjain.com 2020-02-17 03:09 EDT------- (In reply to comment #11) > This is reproducible also in x64 VM with GUI. Text UI does not have this > problem. > I can't reproduce this on Rawhide. Are you going to plan a common fix here for GUI? *** Bug 178119 has been marked as a duplicate of this bug. *** Created attachment 1682901 [details]
sosreport
Created attachment 1682902 [details]
console log
Created attachment 1682903 [details]
sosreport
For reference, upstream merge request is here: https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/merge_requests/6 ------- Comment From preeti.thakur.com 2020-06-12 02:40 EDT------- Issue is seen with RHEL8.3le_Alpha1 aswell ------- Comment From preeti.thakur.com 2020-07-01 01:18 EDT------- Issue is reproducible with RHEL8.3le_PreBeta kernel-4.18.0-214.el8 aswell (In reply to IBM Bug Proxy from comment #22) > ------- Comment From preeti.thakur.com 2020-07-01 01:18 EDT------- > Issue is reproducible with RHEL8.3le_PreBeta kernel-4.18.0-214.el8 aswell . ... for which the following bugzilla was raised: LTC bug 186612 - RH1852769- RHEL8.3 Pre-Beta - warning while connecting to VNC "Warning:Could not resolve keysym XF86MonBrightnessCycle" (xorg-x11-xkb-utils) ... Not sure what to do here, moving back to ASSIGNED for further inspection. As suggested in comment #5, the previous "Internal Error" was downgraded to a "Warning". So it still shows up but it does not appear like an actual error anymore (as mentioned above, this is a cosmetic issue only and has no effect on whether anything works or not). The warning itself will disappear with the next full rebuild of the Xorg stack but that is not scheduled for 8.3. (In reply to Peter Hutterer from comment #25) > As suggested in comment #5, the previous "Internal Error" was downgraded to > a "Warning". So it still shows up but it does not appear like an actual > error anymore (as mentioned above, this is a cosmetic issue only and has no > effect on whether anything works or not). The warning itself will disappear > with the next full rebuild of the Xorg stack but that is not scheduled for > 8.3. Hanns-Joachim any objections if I move this bug to verified? If not we would need to move this to RHEL8.x where we are going to do another Xorg rebase (most probably not 8.4). (In reply to Tomas Pelka from comment #26) > (In reply to Peter Hutterer from comment #25) > > As suggested in comment #5, the previous "Internal Error" was downgraded to > > a "Warning". So it still shows up but it does not appear like an actual > > error anymore (as mentioned above, this is a cosmetic issue only and has no > > effect on whether anything works or not). The warning itself will disappear > > with the next full rebuild of the Xorg stack but that is not scheduled for > > 8.3. > > Hanns-Joachim any objections if I move this bug to verified? If not we would > need to move this to RHEL8.x where we are going to do another Xorg rebase > (most probably not 8.4). . Hello Red Hat / Tomas, ... yes, please go ahead ... ... we will open a new bugzilla if required ... Thanks for your attention and support. Thanks Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (userspace graphics, xorg-x11, and mesa bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:4742 |