[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#673035: marked as done (useless "No symbols defined for" warnings)



Your message dated Fri, 22 Apr 2022 16:51:37 +0200
with message-id <YmLA+T0WIldLsjB+@jcristau-z4>
and subject line Re: Bug#673035: useless "No symbols defined for" warnings
has caused the Debian Bug report #673035,
regarding useless "No symbols defined for" warnings
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
673035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: x11-xkb-utils
Version: 7.5+5
Severity: minor

xkbcomp warns whenever a keycode has been given a name but does not have
symbols explicitly defined.  This happens a lot, because keycodes files
tend to name every keycode defined for their protocol, including many
obscure keys that most keyboards don't have.  For example, the evdev
set results in a lot of

Warning:          No symbols defined for <HIRA> (keycode 99)
Warning:          No symbols defined for <HENK> (keycode 100)
Warning:          No symbols defined for <HKTG> (keycode 101)
...
Warning:          No symbols defined for <HELP> (keycode 146)
Warning:          No symbols defined for <I147> (keycode 147)
Warning:          No symbols defined for <I148> (keycode 148)
Warning:          No symbols defined for <I149> (keycode 149)

It's OK to warn about this, but since it's a very normal situation
and doesn't usually represent an actual problem it should be a very
low-priority warning, that can be turned off without losing any of the
more useful warnings.

In fact it's implemented as quite a high-priority warning.  It takes
"-w 3" to turn it off; "-w 4" or higher generates this warning.
By comparison, the warning for the reverse situation, where an attempt
is made to assign symbols to a key name that hasn't been defined, which
*does* generally indicate a real problem, is turned off at "-w 4" or
below, appearing only with "-w 5" or higher.  So at "-w 4" you get the
useless warnings but not the useful ones.

Having this warning on means that any successful run of xkbcomp generates
screenfuls of useless warnings, thus hiding real warnings.  Having this
warning off means that real warnings will be suppressed.  Neither is
a good way to operate.  The "No symbols defined for" warning needs to
be lower priority than other warnings, or independently selectable,
or just abolished entirely.

-zefram



--- End Message ---
--- Begin Message ---
Version: 7.7+6

On Tue, May 15, 2012 at 04:34:18PM +0100, Zefram wrote:
> xkbcomp warns whenever a keycode has been given a name but does not have
> symbols explicitly defined.  This happens a lot, because keycodes files
> tend to name every keycode defined for their protocol, including many
> obscure keys that most keyboards don't have.  For example, the evdev
> set results in a lot of
> 
> Warning:          No symbols defined for <HIRA> (keycode 99)
> Warning:          No symbols defined for <HENK> (keycode 100)
> Warning:          No symbols defined for <HKTG> (keycode 101)
> ...
> Warning:          No symbols defined for <HELP> (keycode 146)
> Warning:          No symbols defined for <I147> (keycode 147)
> Warning:          No symbols defined for <I148> (keycode 148)
> Warning:          No symbols defined for <I149> (keycode 149)
> 
> It's OK to warn about this, but since it's a very normal situation
> and doesn't usually represent an actual problem it should be a very
> low-priority warning, that can be turned off without losing any of the
> more useful warnings.
> 
Fixed in xkbcomp 1.4.5:

commit 1955a2645670eeea83d6d163653749249cd839f2
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Thu Jan 21 13:16:53 2021 +1000

    Downgrade the warning for missing symbols to info
    
    In the interest of maintainability, it's easier to include as many keycodes as
    possible and then have the symbols mapping specific to the layout. This is
    particularly true for evdev where the kernel takes care of device-specifics
    and every keyboard has the same set of keycodes anyway.
    
    So let's downgrade this from a warning to a mere info, virtually every
    keyboard right now triggers this warning for a number of keys.
    
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Cheers,
Julien

--- End Message ---

Reply to: