Bug#1063728: keyboard-configuration: format of XKBOPTIONS not specified

2024-02-11 Thread Michael Gold
Package: keyboard-configuration
Version: 1.226
Severity: minor

Dear Maintainer,

/etc/default/keyboard refers to "the keyboard(5) manual page", which
says:
  XKBOPTIONS
Specifies the XKB keyboard option components. Options usually
relate to the behavior of the special keys (, ,
, , etc.) Default: not set.

This does not say how multiple options should be separated.  Luckily,
there are examples suggesting the value can be a comma-separated list
with no whitespace.

The actual expectations should be stated explicitly, and the same goes
for XKBVARIANT.

- Michael


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.85
ii  liblocale-gettext-perl  1.07-6+b1
ii  xkb-data2.41-1

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii  console-setup-linux1.226
ii  debconf [debconf-2.0]  1.5.85
ii  xkb-data   2.41-1

Versions of packages console-setup suggests:
ii  locales2.37-15
ii  sysvinit-utils [lsb-base]  3.08-6

Versions of packages console-setup-linux depends on:
ii  init-system-helpers  1.66
ii  kbd  2.6.4-2

Versions of packages console-setup-linux suggests:
ii  console-setup  1.226

Versions of packages keyboard-configuration is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.6.4-2
ii  systemd   255.3-2

-- debconf information:
  keyboard-configuration/unsupported_options: true
  console-setup/fontsize-text47: 8x16
  console-setup/guess_font:
  console-setup/fontsize-fb47: 8x16
  console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/model: Generic 105-key PC
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/switch: No temporary switch
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/layout:
  console-setup/charmap47: UTF-8
* keyboard-configuration/compose: No compose key
  keyboard-configuration/unsupported_layout: true
  console-setup/use_system_font:
  console-setup/fontface47: Fixed
  console-setup/framebuffer_only:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/xkb-keymap: us(dvorak)
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/codesetcode: Lat15
* keyboard-configuration/other:
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/variantcode: dvorak
* keyboard-configuration/modelcode: pc105
* keyboard-configuration/variant: English (US) - English (Dvorak)
  console-setup/fontsize: 8x16
  keyboard-configuration/ctrl_alt_bksp: false
* keyboard-configuration/optionscode: ctrl:swapcaps
  keyboard-configuration/unsupported_config_options: true


signature.asc
Description: PGP signature


Bug#848972: Fixed in Ubuntu

2024-02-11 Thread Ferenc Wágner
On Sun, 11 Feb 2024 13:11:51 +0100 Holger Wansing  wrote:

> Ferenc Wágner  wrote (Mon, 26 Jun 2023 12:27:49 +0200):
>
>> This issue was fixed in 1.178ubuntu12, as detailed at
>> https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227
>> Please consider taking over the fix.
> 
> I have grabbed the changings from
> https://git.launchpad.net/ubuntu/+source/console-setup/commit/?h=applied/ubuntu/disco=dc3395232928c2a3f53c7e5e29ad25a2638ddcae
> Patch attached.  Any objections?

Hi Holger,

None from my part, FWIW (very little).  I'd thank the original
author in the changelog entry, though.
-- 
Thanks for you work,
Feri.



Bug#968122: I confirm this bug

2024-02-11 Thread Thomas Lange
I can confirm this bug.

Using qemu/kvm with autopkgtests I have
keyboard-configuration 1.221 inside the testbed and the postinst
script of keyboard-configuration fails with

cat: '/sys/bus/usb/devices/*:*/bInterfaceClass': No such file or directory
cat: '/sys/bus/usb/devices/*:*/bInterfaceSubClass': No such file or directory
cat: '/sys/bus/usb/devices/*:*/bInterfaceProtocol': No such file or directory

-- 
regards Thomas



Bug#1063413: marked as done (FTBFS: cannot open /<>/Keyboard/pc105.ekbd: No such file)

2024-02-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 13:32:13 +0100
with message-id <20240211133213.1096c5547204d11da4759...@mailbox.org>
and subject line Re: Bug#1063413: FTBFS: cannot open 
/<>/Keyboard/pc105.ekbd: No such file
has caused the Debian Bug report #1063413,
regarding FTBFS: cannot open /<>/Keyboard/pc105.ekbd: No such file
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 ow...@bugs.debian.org
immediately.)


-- 
1063413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: console-setup
Version: 1.224
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid trixie ftbfs

Dear Maintainer,

console-setup 1.224 fails to build from source with the following error:

  Dumping the encoded keymaps for pc105...
  WARNING: Can not find "caps_switch" in "group".
  WARNING: Can not find "caps_toggle" in "group".
  gzip -9n >/Keyboard/pc105.ekbd 
>/<>/Keyboard/pc105.ekbd.gz
  /bin/sh: 1: cannot open /<>/Keyboard/pc105.ekbd: No such file
  make[1]: *** [rules.mk:17: /<>/Keyboard/pc105.ekbd.gz] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:204: udeb-install] Error 2

Version 1.223 builds fine in unstable instead. Perhaps this is related
to the fact that 1.224 dropped the binary package console-setup-pc-ekbd?
--- End Message ---
--- Begin Message ---
Version: 1.225

Emanuele Rocca  wrote (Thu, 8 Feb 2024 15:25:50 +0100):
> Hi,
> 
> On 2024-02-08 02:06, Colin Watson wrote:
> > On Wed, Feb 07, 2024 at 11:13:01PM +0100, Holger Wansing wrote:
> > > Am 7. Februar 2024 21:55:05 MEZ schrieb Emanuele Rocca :
> > > >Perhaps this is related to the fact that 1.224 dropped the binary
> > > >package console-setup-pc-ekbd?
> > > 
> > > What makes you think, that this has happened?
> > > 
> > > There is a merge request that includes the removal of said package,
> > > but it has not yet been merged.
> 
> Looks like the change has been uploaded though, there is no
> console-setup-pc-ekbd here:
> https://sources.debian.org/src/console-setup/1.224/debian/control/
> 
> But on 1.223 it's there:
> https://sources.debian.org/src/console-setup/1.223/debian/control/#L161
> 
> > My inclination is to upload 1.225 without that patch for now, as we need
> > to rebuild for the new xkb-data to sort out uninstallability in
> > unstable, and then get the kFreeBSD-removal patch sorted out after that.
> > Objections?

This was fixed by a clean upload of 1.225 without said changings.

Thanks everybody


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---


Re: Bug#1063413: FTBFS: cannot open /<>/Keyboard/pc105.ekbd: No such file

2024-02-11 Thread Holger Wansing
Version: 1.225

Emanuele Rocca  wrote (Thu, 8 Feb 2024 15:25:50 +0100):
> Hi,
> 
> On 2024-02-08 02:06, Colin Watson wrote:
> > On Wed, Feb 07, 2024 at 11:13:01PM +0100, Holger Wansing wrote:
> > > Am 7. Februar 2024 21:55:05 MEZ schrieb Emanuele Rocca :
> > > >Perhaps this is related to the fact that 1.224 dropped the binary
> > > >package console-setup-pc-ekbd?
> > > 
> > > What makes you think, that this has happened?
> > > 
> > > There is a merge request that includes the removal of said package,
> > > but it has not yet been merged.
> 
> Looks like the change has been uploaded though, there is no
> console-setup-pc-ekbd here:
> https://sources.debian.org/src/console-setup/1.224/debian/control/
> 
> But on 1.223 it's there:
> https://sources.debian.org/src/console-setup/1.223/debian/control/#L161
> 
> > My inclination is to upload 1.225 without that patch for now, as we need
> > to rebuild for the new xkb-data to sort out uninstallability in
> > unstable, and then get the kFreeBSD-removal patch sorted out after that.
> > Objections?

This was fixed by a clean upload of 1.225 without said changings.

Thanks everybody


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#848972: Fixed in Ubuntu

2024-02-11 Thread Holger Wansing
Control: tags -1 + patch

Ferenc Wágner  wrote (Mon, 26 Jun 2023 12:27:49 +0200):
> Control: tag + patch
> 
> Hi,
> 
> This issue was fixed in 1.178ubuntu12, as detailed at
> https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227
> Please consider taking over the fix.

I have grabbed the changings from
https://git.launchpad.net/ubuntu/+source/console-setup/commit/?h=applied/ubuntu/disco=dc3395232928c2a3f53c7e5e29ad25a2638ddcae


Patch attached.

Any objections?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/debian/changelog b/debian/changelog
index fb41ffd..ce2f43b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+console-setup (1.227) UNRELEASED; urgency=medium
+
+  * setupcon: use /run for tempfiles (and dump the various unnecessary
+fallback paths), since /run is always mountable rw at least as early as
+/tmp is and is guaranteed to be safe from tmpcleaners at boot.  Only keep
+/tmp as a fallback in case we have access to write to /tmp and to a
+console, but not to /run.  Closes: #848972
+
+ -- Holger Wansing   Sun, 11 Feb 2024 13:03:18 +0100
+
 console-setup (1.226) unstable; urgency=medium
 
   * Team upload
diff --git a/setupcon b/setupcon
index 04641c6..5d83433 100755
--- a/setupcon
+++ b/setupcon
@@ -60,11 +60,8 @@ trap 'rm -f $tempfiles >/dev/null 2>&1' 0
 trap "exit 2" 1 2 3 13 15
 tempfile () {
 if \
-TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
-|| TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
-|| TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
-|| TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
-|| TMPFILE=`mktemp 2>/dev/null`
+TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
+|| TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null`
 then
 tempfiles="$tempfiles $TMPFILE"
 return 0


Processed: Re: Bug#848972: Fixed in Ubuntu

2024-02-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #848972 [console-setup-linux] console-setup-linux: Datei /tmp/tmpkbd.BRzn8j 
kann nicht geöffnet werden
Ignoring request to alter tags of bug #848972 to the same tags previously set

-- 
848972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Debian installation wifi card not being detected

2024-02-11 Thread Andrew M.A. Cater
On Sun, Feb 11, 2024 at 11:20:43AM +0100, Pascal Hambourg wrote:
> On 10/02/2024 at 20:06, Andrew M.A. Cater wrote:
> > 
> > It may also be possible to tether via a cable to a mobile phone and do the
> >   netinst install that way.
> 
> Right, sorry for not mentioning it in my previous reply.
> 
> The OP mentioned in debian-user that they have an iOS (Apple) device. The
> package ipheth-utils provides a tethering driver for the iPhone (and
> possibly other iOS devices). I do not know whether it is required, but it is
> not available in the Debian installer environment. I did not find it in
> Debian live package lists 
> (https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/*.packages)
> either.
> 

I wouldn't expect there to be much in debian-live for Apple, no.

I'd always recommend netinst but this is one of the times when it just
won't work, obviously. For common wifi cards with loadable firmware -
it may well work. Broadcom, no.

The DVD-1 image at 
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.5.0-amd64-DVD-1.iso
 has the installer on it, so that might well
be a candidate to try.

If you do install from DVD-1 and have no network at the time when you
install, you may need to fix up /etc/apt/sources.list afterwards :)

> > With my debian-user mailing list hat on: please post to one list primarily
> > and don't cross-post between lists unless invited to. Thanks :)
> 
> When in doubt, true cross-post to a couple of lists seems acceptable to me
> (so that replies can be cross-posted too), but it looks like the OP actually
> sent multiple independent posts.
>

Yes, I was possibly a bit grumpy here: apologies 

All the very best,

Andy
(amaca...@debian.org)



Bug#1051846: marked as done (installation-reports: gnome_flashback installation fails on openQA with daily netinst image)

2024-02-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 12:25:50 +0100
with message-id <20240211122550.3ac4259eb265e31ec44cf...@mailbox.org>
and subject line Re: Bug#1051846: installation-reports: gnome_flashback 
installation fails on openQA with daily netinst image
has caused the Debian Bug report #1051846,
regarding installation-reports: gnome_flashback installation fails on openQA 
with daily netinst image
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 ow...@bugs.debian.org
immediately.)


-- 
1051846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
X-Debbugs-Cc: p...@hands.com

Boot method: CD netinst image
Image version: https://get.debian.org/images/daily-builds/daily/arch-
latest/amd64/iso-cd/debian-testing-amd64-netinst.iso from 20230913_0524
Date: 

Machine: QEMU with UEFI secure boot as on openqa.debian.net, 2GB memory
Partitions: wipe all from a 10GB virtual HD


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The installation proceeds without error.
After rebooting, the screen with 'Oh no! Something has gone wrong' is shown.

My attempts to reproduce and pinpoint the cause:
I've tested with QXL and VGA graphical cards on openQA. In both cases the 'Oh
no!' is shown.

With the netinst image from 20230909_0504, the flashback GUI started initially
with the grey top menu bar, but that got replaced by the black menu bar of the
regular GNOME desktop.

The last known good netinst image was from 20230910_0509.
The first netinst image with this issue is from 20230910_1109.
This narrows down the number of possible causes a bit.

To see more installation attempts (every 6 hours):
* Go to https://openqa.debian.net/group_overview/10
* Take a build that has no running jobs (i.e. no blue bar)
* Click on the red part of the bar
* Click on the red circle behind 'gnome_flash_flash' (before
'_graphical_wait_login' or 'complete_install')
* Installation logs and additional information can be found in the 'Logs &
Assets' tab of the test

With kind regards,
Roland Clobus


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Giga-byte 

Re: Bug#1051846: installation-reports: gnome_flashback installation fails on openQA with daily netinst image

2024-02-11 Thread Holger Wansing
Hi,

Roland Clobus  wrote (Wed, 13 Sep 2023 15:59:37 +0200):
> Comments/Problems:
> 
> The installation proceeds without error.
> After rebooting, the screen with 'Oh no! Something has gone wrong' is shown.
> 
> My attempts to reproduce and pinpoint the cause:
> I've tested with QXL and VGA graphical cards on openQA. In both cases the 'Oh
> no!' is shown.
> 

Apparently only a temporary problem; looks fine again.

Closing this bug


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Fix and improve usability of keyboard layout and input methods for users under zh_TW locale

2024-02-11 Thread Holger Wansing
Hi,

Andrew Lee  wrote (Sun, 17 Sep 2023 13:22:43 +0200):
> 
> * Add Taiwanese xkb-keymap answer and default for zh_TW locales:
>   https://salsa.debian.org/installer-team/console-setup/-/merge_requests/20

'Taiwanese' keyboard layout is now available in the installer (and default
for Traditional Chinese).

Could you try a netinst daily, to check if everything works as expected?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/


Thanks

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Debian installation wifi card not being detected

2024-02-11 Thread Pascal Hambourg

On 10/02/2024 at 20:06, Andrew M.A. Cater wrote:


It may also be possible to tether via a cable to a mobile phone and do the
  netinst install that way.


Right, sorry for not mentioning it in my previous reply.

The OP mentioned in debian-user that they have an iOS (Apple) device. 
The package ipheth-utils provides a tethering driver for the iPhone (and 
possibly other iOS devices). I do not know whether it is required, but 
it is not available in the Debian installer environment. I did not find 
it in Debian live package lists 
(https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/*.packages) 
either.



With my debian-user mailing list hat on: please post to one list primarily
and don't cross-post between lists unless invited to. Thanks :)


When in doubt, true cross-post to a couple of lists seems acceptable to 
me (so that replies can be cross-posted too), but it looks like the OP 
actually sent multiple independent posts.