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

Bug#953032: marked as done (xkbcomp: Internal error: Could not resolve keysym XF86FullScreen)

Your message dated Mon, 4 May 2020 12:21:22 +0200
with message-id <20200504102122.GA323246@chou>
and subject line Re: Bug#953032: xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
has caused the Debian Bug report #953032,
regarding xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
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.)


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

journalctl reports thousands of
sh[1052]: The XKEYBOARD keymap compiler (xkbcomp) reports:
sh[1052]: > Internal error:   Could not resolve keysym XF86FullScreen
sh[1052]: Errors from xkbcomp are not fatal to the X server

Versions of packages x11-xkb-utils depends on:
ii  libc6        2.29-10
ii  libx11-6     2:1.6.9-2
ii  libxaw7      2:1.0.13-1+b2
ii  libxkbfile1  1:1.0.9-2+b12
ii  libxt6       1:1.1.5-1+b3

--- End Message ---
--- Begin Message --- 
On Sat, Apr 18, 2020 at 01:02:33PM +0200, Reiner Herrmann wrote:
> Control: reopen -1
> 
> Reopening, as the same error is still thrown, as can be seen [0] in the
> autopkgtest runs [1] of src:awesome.

I just scheduled libx11 binNMUs which should make this go away.

It was never a critical bug though.

Cheers,
Julien

--- End Message ---
Reply to: