Debian Bug report logs - #815573
Purges 'caps:none' in XKBOPTIONS after upgrade

Full log

🔗 View this message in rfc822 format

X-Loop: [email protected]
Subject: Bug#709883: Bugs which do not belong to console-setup
Reply-To: Tomas Pospisek <[email protected]>, [email protected]
Resent-From: Tomas Pospisek <[email protected]>
Resent-To: [email protected]
Resent-CC: Debian Install System Team <[email protected]>
X-Loop: [email protected]
Resent-Date: Wed, 13 Aug 2014 22:12:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Debian-PR-Message: followup 709883
X-Debian-PR-Package: keyboard-configuration
X-Debian-PR-Keywords: l10n
X-Debian-PR-Source: console-setup
Received: via spool by [email protected] id=B709883.140796776815705
          (code B ref 709883); Wed, 13 Aug 2014 22:12:02 +0000
Received: (at 709883) by bugs.debian.org; 13 Aug 2014 22:09:28 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2-bugs.debian.org_2005_01_02
	(2011-06-06) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=4.0 tests=BAYES_00,SPF_PASS,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.2-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 151; neutral, 87; spammy,
	0. spammytokens: hammytokens:0.000-+--gdm3, 0.000-+--H*f:sk:2014080,
	0.000-+--xsession, 0.000-+--H*i:sk:2014080, 0.000-+--startx
Received: from brisi.sourcepole.ch ([5.9.57.43])
	by buxtehude.debian.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
	(Exim 4.80)
	(envelope-from <[email protected]>)
	id 1XHgjY-00044o-1D
	for [email protected]; Wed, 13 Aug 2014 22:09:28 +0000
Received: from 16-233.195-178.cust.bluewin.ch ([178.195.233.16] helo=[192.168.0.102])
	by vilan-mail with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128)
	(Exim 4.80)
	(envelope-from <[email protected]>)
	id 1XHg2f-0000gw-JT; Wed, 13 Aug 2014 23:25:09 +0200
Message-ID: <[email protected]>
Date: Wed, 13 Aug 2014 23:25:08 +0200
From: Tomas Pospisek <[email protected]>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Anton Zinoviev <[email protected]>, [email protected]
CC: [email protected]
References: <[email protected]>
In-Reply-To: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: delayed 2645 seconds by postgrey-1.34 at buxtehude; Wed, 13 Aug 2014 22:09:27 UTC

Am 07.08.2014 12:32, schrieb Anton Zinoviev:

> I have two bugs reported against console-setup about keybord not working 
> properly under X Window.  In both cases I have asked the reportes to 
> provide the file /etc/default/keyboard and in both cases the file was 
> correct.  Therefore, the bugs are not related to console-setup in any 
> way.
> 
> Unfortunately X Window and the various desktop environments are 
> something I don't understand well enough, so I have no idea where to 
> reassign these bugs.  In result, at the moment both bugs are completely 
> ignored.
> 
> Please advise what should I do in such cases.
> 
> The bugs are: 
> #709883 - reported 14 months ago and #724869 - reported 10 months ago.

Wrt. #709883 the original bug reporter (OBR) wrote:

> [...]
> I tried with gdm3/ligthdm/only startx, and the problems is still
> here. It seems related to X or udev since the upgrade, because gnome
> is well set and gives a french keyboard (macbook pro one), and for
> awesome, my main wm, i have to setxkbmap fr in ~/.xsession to get a
> french keyboard layout
> [...]
> I'm still trying to figure out how to get french back at dm greeter

So most window managers and login managers don't get the keyboard right,
however gnome does.

The correct/wrong keyboard setup/information must come from *somewhere*,
but from where?

So one thing the OBR could do to figure out what's going on is to
"strace -f" startx and the gnome startup, figure out which files are
being accessed (only stat, open and mmap calls are of interest I guess)
and then compare the produced lists.

Otherwise, if nobody can figure out what's going on, or the OBR doesn't
care any more either the OBR or the console-setup maintainers can decide
to close the bug, since no way forward can be made unless there's more
info. Or leave it open.

HTH a bit,
*t

Send a report that this bug log contains spam.