d-i-n-i vs. riscv64

2024-12-27 Thread Cyril Brulebois 
Hello Aurélien,

Let's pretend I know nothing about riscv64… I see you added support for
it in debian-installer (thanks!) and the resulting images tarball
includes netboot stuff, so I've staged the addition of a riscv64 package
on the d-i-n-i side:
  
https://salsa.debian.org/installer-team/debian-installer-netboot-images/-/commit/eec4e7add8cd0aac06eb29e54fcf161c1539e39c
  
https://salsa.debian.org/installer-team/debian-installer-netboot-images/-/commit/d9d653ccc36c6e8499cb37ae016cee5274bc6497

I just wanted to make sure that makes sense before throwing the updated
package in NEW's direction (we have the 12→13 bump already anyway…).

Thanks already!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processing of debian-installer_20241227_source.changes

2024-12-27 Thread Debian FTP Masters 
debian-installer_20241227_source.changes uploaded successfully to localhost
along with the files:
  debian-installer_20241227.dsc
  debian-installer_20241227.tar.xz
  debian-installer_20241227_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1089010: marked as done (debian-installer: armhf cdrom initrd.gz does not set the selected keyboard layout)

2024-12-27 Thread Debian Bug Tracking System 
Your message dated Sat, 28 Dec 2024 00:04:26 +
with message-id 
and subject line Bug#1089010: fixed in debian-installer 20241227
has caused the Debian Bug report #1089010,
regarding debian-installer: armhf cdrom initrd.gz does not set the selected 
keyboard layout
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.)


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

Package: debian-installer
Version: 20240914

After booting debian-testing-armhf-netinst.iso, I select the French 
keyboard.

Expected outcome: French keyboard layout is set.
Observed outcome: default US keyboard layout remains.

Error message in /var/log/syslog:

 ckbcomp-mini: /usr/share/console-setup/pc105.ekmap.gz does not exist

Indeed the armhf cdrom initrd.gz does not contain this file.
/usr/share/console-setup/pc105.ekmap.gz appears to be provided by 
console-setup-pc-ekmap udeb. Looking at debian-installer source, I see 
that console-setup-pc-ekmap is not listed in 
build/pkg-lists/cdrom/armhf.cfg.


Conversely, the armhf hd-media initrd.gz correctly sets the selected 
keyboard layout and contains /usr/share/console-setup/pc105.ekmap.gz. 
console-setup-pc-ekmap is listed in build/pkg-lists/hd-media/armhf.cfg.


Note: build/pkg-lists/cdrom/arm64.cfg does not list 
console-setup-pc-ekmap and arm64/cdrom/initrd.gz does not contain 
/usr/share/console-setup/pc105.ekmap.gz either.
--- End Message ---
--- Begin Message ---
Source: debian-installer
Source-Version: 20241227
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1089...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debian-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Dec 2024 10:14:03 +0100
Source: debian-installer
Architecture: source
Version: 20241227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1037186 1089010
Changes:
 debian-installer (20241227) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * The “さようなら、あーうぇんちゃん” release.
   * Bump Linux kernel ABI to 6.12.6.
   * Bump (temporary) linux-image build-deps accordingly.
   * Set DRM_DIR using /usr/lib/… instead of /lib/… since the former is where
 linux-image-* packages ship their modules.
   * Update translation-status for the release.
   * Drop the “12” version from the Emerald boot screen: drop the SVG paths
 for the 1 and 2 digits after the Debian logo and name, to avoid any
 confusion until the Ceratopsian theme gets integrated.
 .
   [ Aurelien Jarno ]
   * Add riscv64 to RELEASE_ARCHES in order to use udebs from testing. Do not
 force DEBIAN_RELEASE to unstable.
   * Add monolithic support for riscv64.
   * Update riscv64 grub config to use UEFI Graphics Output Protocol if
 available.
   * Create a UEFI Unified Kernel Image (UKI) for the netboot and monolithic
 targets on riscv64.
 .
   [ Ben Hutchings ]
   * Update pkg-lists to make kernel udebs removed in 6.11.2-1 optional
 .
   [ John Paul Adrian Glaubitz ]
   * loong64: Add scsi-modules to cdrom pkg-lists
 .
   [ Pascal Hambourg ]
   * Add console-setup-pc-ekmap for arm64 and armhf cdrom. Closes: #1089010.
 .
   [ Timothy Pearson ]
   * Add fb-modules for ppc64 and ppc64el cdrom and netboot. Closes: #1037186.
 .
   [ John Paul Adrian Glaubitz ]
   * sh4: Don't unversion the kernel as multiple flavors are supported
Checksums-Sha1:
 007a7218d6f80d8f8dd20d8b343a0b7a5e10a223 3987 debian-installer_20241227.dsc
 13c3795a746f8094587294054e9dfb991e41196f 1181928 
debian-installer_20241227.tar.xz
 6997c7941ecbfc69d51a83412c60a689f9c5 17297 
debian-installer_20241227_source.buildinfo
Checksums-Sha256:
 fb89850710be95c6ec8287ac0c71135b46f7283f935c2481bc06dec274697a19 3987 
debian-installer_20241227.dsc
 e86c2c02c36a9f6217fd9b8ab41495d2495bc7162b6b08b0c1bb3bc86634ee52 1181928 
debian-installer_20241227.t

Bug#1037186: marked as done (debian-installer: bookworm d-i graphics are not shown on Raptor system)

2024-12-27 Thread Debian Bug Tracking System 
Your message dated Sat, 28 Dec 2024 00:04:26 +
with message-id 
and subject line Bug#1037186: fixed in debian-installer 20241227
has caused the Debian Bug report #1037186,
regarding debian-installer: bookworm d-i graphics are not shown on Raptor system
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.)


-- 
1037186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-installer
Version: 20230526
Severity: important
X-Debbugs-Cc: tpear...@raptorcs.com, zu...@debian.org

Hello,

We found latest installer for bookworm is missing ast DRM kernel module, 
causing graphical failure on ppc64el Raptor machines. Could you please consider 
the following change or similar for the debian-installer bookworm release.

  https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34

Regards

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES:ca
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: debian-installer
Source-Version: 20241227
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debian-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Dec 2024 10:14:03 +0100
Source: debian-installer
Architecture: source
Version: 20241227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1037186 1089010
Changes:
 debian-installer (20241227) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * The “さようなら、あーうぇんちゃん” release.
   * Bump Linux kernel ABI to 6.12.6.
   * Bump (temporary) linux-image build-deps accordingly.
   * Set DRM_DIR using /usr/lib/… instead of /lib/… since the former is where
 linux-image-* packages ship their modules.
   * Update translation-status for the release.
   * Drop the “12” version from the Emerald boot screen: drop the SVG paths
 for the 1 and 2 digits after the Debian logo and name, to avoid any
 confusion until the Ceratopsian theme gets integrated.
 .
   [ Aurelien Jarno ]
   * Add riscv64 to RELEASE_ARCHES in order to use udebs from testing. Do not
 force DEBIAN_RELEASE to unstable.
   * Add monolithic support for riscv64.
   * Update riscv64 grub config to use UEFI Graphics Output Protocol if
 available.
   * Create a UEFI Unified Kernel Image (UKI) for the netboot and monolithic
 targets on riscv64.
 .
   [ Ben Hutchings ]
   * Update pkg-lists to make kernel udebs removed in 6.11.2-1 optional
 .
   [ John Paul Adrian Glaubitz ]
   * loong64: Add scsi-modules to cdrom pkg-lists
 .
   [ Pascal Hambourg ]
   * Add console-setup-pc-ekmap for arm64 and armhf cdrom. Closes: #1089010.
 .
   [ Timothy Pearson ]
   * Add fb-modules for ppc64 and ppc64el cdrom and netboot. Closes: #1037186.
 .
   [ John Paul Adrian Glaubitz ]
   * sh4: Don't unversion the kernel as multiple flavors are supported
Checksums-Sha1:
 007a7218d6f80d8f8dd20d8b343a0b7a5e10a223 3987 debian-installer_20241227.dsc
 13c3795a746f8094587294054e9dfb991e41196f 1181928 
debian-installer_20241227.tar.xz
 6997c7941ecbfc69d51a83412c60a689f9c5 17297 
debian-installer_20241227_source.buildinfo
Checksums-Sha256:
 fb89850710be95c6ec8287ac0c71135b46f7283f935c2481bc06dec274697a19 3987 
debian-installer_20241227.dsc
 e86c2c02c36a9f6217fd9b8ab41495d2495bc7162b6b08b0c1bb3bc86634ee52 1181928 
debian-installer_20241227.tar.xz
 821e35e6c97a2abba67b66ee03230451938a30ffd7bd62bcfbae59b9b67d624c 17297 
debian-installer_

debian-installer_20241227_source.changes ACCEPTED into unstable

2024-12-27 Thread Debian FTP Masters 
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Dec 2024 10:14:03 +0100
Source: debian-installer
Architecture: source
Version: 20241227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1037186 1089010
Changes:
 debian-installer (20241227) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * The “さようなら、あーうぇんちゃん” release.
   * Bump Linux kernel ABI to 6.12.6.
   * Bump (temporary) linux-image build-deps accordingly.
   * Set DRM_DIR using /usr/lib/… instead of /lib/… since the former is where
 linux-image-* packages ship their modules.
   * Update translation-status for the release.
   * Drop the “12” version from the Emerald boot screen: drop the SVG paths
 for the 1 and 2 digits after the Debian logo and name, to avoid any
 confusion until the Ceratopsian theme gets integrated.
 .
   [ Aurelien Jarno ]
   * Add riscv64 to RELEASE_ARCHES in order to use udebs from testing. Do not
 force DEBIAN_RELEASE to unstable.
   * Add monolithic support for riscv64.
   * Update riscv64 grub config to use UEFI Graphics Output Protocol if
 available.
   * Create a UEFI Unified Kernel Image (UKI) for the netboot and monolithic
 targets on riscv64.
 .
   [ Ben Hutchings ]
   * Update pkg-lists to make kernel udebs removed in 6.11.2-1 optional
 .
   [ John Paul Adrian Glaubitz ]
   * loong64: Add scsi-modules to cdrom pkg-lists
 .
   [ Pascal Hambourg ]
   * Add console-setup-pc-ekmap for arm64 and armhf cdrom. Closes: #1089010.
 .
   [ Timothy Pearson ]
   * Add fb-modules for ppc64 and ppc64el cdrom and netboot. Closes: #1037186.
 .
   [ John Paul Adrian Glaubitz ]
   * sh4: Don't unversion the kernel as multiple flavors are supported
Checksums-Sha1:
 007a7218d6f80d8f8dd20d8b343a0b7a5e10a223 3987 debian-installer_20241227.dsc
 13c3795a746f8094587294054e9dfb991e41196f 1181928 
debian-installer_20241227.tar.xz
 6997c7941ecbfc69d51a83412c60a689f9c5 17297 
debian-installer_20241227_source.buildinfo
Checksums-Sha256:
 fb89850710be95c6ec8287ac0c71135b46f7283f935c2481bc06dec274697a19 3987 
debian-installer_20241227.dsc
 e86c2c02c36a9f6217fd9b8ab41495d2495bc7162b6b08b0c1bb3bc86634ee52 1181928 
debian-installer_20241227.tar.xz
 821e35e6c97a2abba67b66ee03230451938a30ffd7bd62bcfbae59b9b67d624c 17297 
debian-installer_20241227_source.buildinfo
Files:
 9f1507a72c36902423ea5b8efb0c0c66 3987 devel optional 
debian-installer_20241227.dsc
 dc1a8b3e6a1fd1c39f4e7aba4989af25 1181928 devel optional 
debian-installer_20241227.tar.xz
 3ec3b24b401ec02ebaae309e3e787804 17297 devel optional 
debian-installer_20241227_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmdvPaYQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIKpcD/43KaQvl6jhc5KQXhGJbX0xMPh6cuuN4frP
pLQXtDjP1NjcBOZ3JAs64u4WCjJ0QAfSRxMenGBGor4Q0+2vOjIgRsE55uAYRYgE
S5PQtJNw3au8pppchkuBrkp5KxOTPDU9yWbo9IoEeHcCcpA45TxLefWB5Z13C1Ua
li2OX4c19qYadiAP0F+Wjchj8QKyZ1IUtl1eCfzt1/Q/z82xesSJn1h40PJ8X1uZ
tZk3QvOUZQVGXxL1L0EAK7XXXCvRMU8+7nGShB6ZVpsscRKyuo56BlkGOpEpRNc9
ed3P8QTyL2s+3nOVCWSZIom1iYzyxeGnQxutREVAvIcgW8+k8oeBK35H2uYWQ03+
UzsN5556s0hwUPEFYP/z3GX+ile5nkzlbKIK6W939FnKcfenz9owkws5dK+/T5PJ
zDa4soSuFUJ7ERyiDoQhnRiuQfZ4AgPKTOAN2g8h2QSH5mfGoMiXwwwsg8oAGbP4
EHTkkNz9Nh3+/dRFBMxARzq2F64LsAn1Qpg+e9xuMWmfVytanlpuKlYPz0u/O5L8
bxKNtDeKyvTuTz5uMHmNQXci9oA8BB3r4rJtL/i1Yv2o/jR9nQ7LrMcLX35QI1RG
AW/23/N/mUrg1sRw3w4GYGStf70jOVRVVB7XvXSaI6LOnOb4oPBhnYeLhOsD0gF0
KX+i5+iShA==
=kahu
-END PGP SIGNATURE-



pgpvj5Nu34X6w.pgp
Description: PGP signature

Bug#1036523: should not install CPU microcode on virtualized systems

2024-12-27 Thread Daniel Lewart 
On Wed, Dec 25, 2024 at 1:32 AM Cyril Brulebois  wrote:
>
> Daniel Lewart  (2024-12-24):
> > I hope this can be resolved for Trixie.
> >
> > Patch attached.  Tested with QEMU.
>
> Thanks, but that doesn't look appropriate: this disables not just CPU
> microcode but also modalias-based firmware lookup entirely…

Revised patch attached.

Thank you!
Daniel Lewart
Urbana, Illinois
diff -ru a/hw-detect.post-base-installer.d/50install-firmware b/hw-detect.post-base-installer.d/50install-firmware
--- a/hw-detect.post-base-installer.d/50install-firmware	2023-05-09 15:01:46.0 -0500
+++ b/hw-detect.post-base-installer.d/50install-firmware	2024-12-27 00:00:00.0 -0600
@@ -48,20 +48,25 @@
 	fi
 done
 
-# Check whether microcode packages are desirable, based on CPU vendor.
-# Only detect and queue installation: they aren't needed in the
-# installer context, and they cannot be deployed via `dpkg -i` by the
-# install-firmware hook due their dependencies; let the finish-install
-# hook handle them instead. Note the component hardcoding.
-printf "GenuineIntel intel-microcode\nAuthenticAMD amd64-microcode\n" | while read vendor pkg; do
-	if grep -qs "^vendor_id.*$vendor$" /proc/cpuinfo; then
-		log "queuing $pkg installation ($vendor)"
-		echo $pkg >> /tmp/microcode.list
-		mkdir -p /var/cache/firmware
-		echo non-free-firmware >> /var/cache/firmware/components
-		echo "$pkg non-free-firmware cpu" >> /var/log/firmware-summary
-	fi
-done
+if chroot /target systemd-detect-virt --quiet; then
+	virt=$(chroot /target systemd-detect-virt)
+	log "detected virtualization '$virt', CPU microcode packages not installed"
+else
+	# Check whether microcode packages are desirable, based on CPU vendor.
+	# Only detect and queue installation: they aren't needed in the
+	# installer context, and they cannot be deployed via `dpkg -i` by the
+	# install-firmware hook due their dependencies; let the finish-install
+	# hook handle them instead. Note the component hardcoding.
+	printf "GenuineIntel intel-microcode\nAuthenticAMD amd64-microcode\n" | while read vendor pkg; do
+		if grep -qs "^vendor_id.*$vendor$" /proc/cpuinfo; then
+			log "queuing $pkg installation ($vendor)"
+			echo $pkg >> /tmp/microcode.list
+			mkdir -p /var/cache/firmware
+			echo non-free-firmware >> /var/cache/firmware/components
+			echo "$pkg non-free-firmware cpu" >> /var/log/firmware-summary
+		fi
+	done
+fi
 
 # enable components based on firmware packages that were installed:
 if [ -d /var/cache/firmware ]; then

Re: Bug#885563: vte: Do not release with forky

2024-12-27 Thread Simon McVittie 
Control: retitle -1 vte: Do not release with forky
Control: tags -1 = forky sid experimental

On Thu, 12 Jan 2023 at 10:17:07 +, Simon McVittie wrote:
> The transition/toolchain freeze for bookworm is today, so it's clearly
> too late to port d-i to GTK 3 for bookworm, and we are stuck with vte
> for another cycle.

I have started trying to port the graphical d-i to GTK 3, but it's too late
to seriously consider landing that work this cycle, so vte will have to get
another stay of execution.

smcv

Debian KDE SDDM login screen issue, possible bug

2024-12-27 Thread chris.bingham 
Hello,

I encountered an SSDM problem, the system crashed, I selected to report to the 
developers, via an error prompt, (described below), but was unsuccessful.

The following is a detailed chronological list of events, commands, results, 
and remediation efforts.

System information:
uname -a
Linux Debian 6.1.0-28-amd64
#1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux

Additional
Debian bookworm 12.8 x86_64
Kernel: 6.1.0-28-amd64
DE: KDE Plasma 5.27.5
WM Theme: BreezeLinux Debian 12, KDE plasma desktop environment.

Issue/problem.
After I lock the screen, and I accidentally hit the tab key on my keyboard.
This results in the username and password fields longer being present, and I am 
unable to login via the GUI.

This has happened in the past and I restarted via it via Alt Sys req REISUB
And was able to login successfully.

The most recent re-occurrence, was today, (12/27/2024)
I locked the screen, and I accidentally hit the tab key on my keyboard when 
trying to log back in.

The username and password fields disappeared, and my screen lock screen 
remained., (just no login credentials fields).

Attempts to troubleshoot and access the GUI login
I was able to login via dropping to the TTY (F2),
After logging in I entered the following commands in this order.

Restart the screen locker
killall kscreenlocker_greet
( this command created no response/result)

Attempted a second time, and nothing
killall kscreenlocker_greet

Then attempted to restart the display manager:
sudo systemctl restart sddm

That command caused the virtual console/TTY to crash, and I was greeted by a 
box:
"Report issue to devs option, do you consent?"
I agreed, and clicked the following options.

- agree, share with devs

- selected the check box on the following:

- Yes, share information with developers.

- Yes I remember what i was doing

- No I did not retry

- I remember what i was doing when the app crashed

- Noticed unusual desktop behavior

Before I could proceed, the spinning waiting wheel began,
It was still spinning after 5 - 8 minutes.
That is when I performed the hard reboot: Alt Sys req REISUB
And, was able to login via GUI, and all worked fine.

If this is a bug, and further information is needed, or if there is a 
setting/config file, I should edit, let me know.

Sincerely,
-Chris

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

--- Forwarded Message ---
From: chris.bingham 
Date: On Friday, December 27th, 2024 at 11:48 AM
Subject: Debian KDE SDDM login screen lock login issue, possible bug
To: chris.bingha...@proton.me 

> Hello,
>
> I encountered an SSDM problem, system crashed, selected to report to the 
> developers, via an error prompt, (described below), but was unsuccessful.
>
> The following is a detailed chronological list of events, commands, results, 
> and remediation efforts.
>
> System information:
> uname -a
> Linux Debian 6.1.0-28-amd64
> #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
>
> Additional
> Debian bookworm 12.8 x86_64
> Kernel: 6.1.0-28-amd64
> DE: KDE Plasma 5.27.5
> WM Theme: BreezeLinux Debian 12, KDE plasma desktop environment.
>
> Issue/problem.
> After I lock the screen, and I accidentally hit the tab key on my keyboard.
> This results in the username and password fields longer being present, and I 
> am unable to login via the GUI.
>
> This has happened in the past and I restarted via it via Alt Sys req REISUB
> And was able to login successfully.
>
> The most recent re-occurrence, was today, (12/27/2024)
> I locked the screen, and I accidentally hit the tab key on my keyboard when 
> trying to log back in.
>
> The username and password fields disappeard, and my screen lock screen 
> remained., (just no login fields).
>
> Attempts to troubleshoot and access the GUI login
> I was able to login via dropping to the TTY (F2),
> After logging in I entered the following commands in this order.
>
> Restart the screen locker
> killall kscreenlocker_greet
> ( this command created no response/result)
>
> Attempted a second time, and nothing
> killall kscreenlocker_greet
>
> Then attempted to restart the display manager:
> sudo systemctl restart sddm
>
> That command caused the virtual console/TTY to crash, and I was greeted by a 
> box:
> "Report issue to devs option, do you consent?"
> I agreed, and clicked the following options.
>
> - agree, share with devs
>
> - selected the check box on the following:
>
> - Yes, share information with developers.
>
> - Yes I remember what i was doing
>
> - No I did not retry
>
> - I remember what i was doing when the app crashed
>
> - Noticed unusual desktop behavior
>
> Before I could proceed, the spinning waiting wheel began,
> It was still spinning after 5 - 8 minutes.
> That is when I performed the hard reboot: Alt Sys req REISUB
> And, was able to login via GUI, and all worked fine.
>
> If this is a bug, and further information is needed, or if there is a 
> setting/config file, I

Disregard my previous message

2024-12-27 Thread chris.bingham 
I misread the contact us page, and sent my email to
ow...@bugs.debian.org

I am not encountering an installation issue.

Best,
-Chris

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

Bug#1037256: debian-installer: GUI font for Japanese was incorrectly rendered

2024-12-27 Thread Kentaro HAYASHI 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037256#20

Above Message #20 approach might be too ad-hoc, it might be better to
investigate more generic alternative.

just as PoC, it might be useful to apply custom style, but
this is just an idea and not fully confirmed yet.

>From 22ba16ddf1f7246db8dd8da6deda53ef76f20a81 Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi 
Date: Mon, 23 Dec 2024 23:26:17 +0900
Subject: [PATCH 1/2] gtk: support to apply custom styles with gtkrc

In the previous versions, it does not support
applying language specific custom style.

Without custom style, it can't resolve language specific
style issue such as Han unification.

Because of Han unification, wrong font typefaces are
rendered by default when you choose Japanese language
using GUI installer.

Most of typefaces are correct, but there are wrong
typefaces (Simplified Chinese) which is used for widget rendering.

Notably, even though "Continue" or "Back" button can't be rendered
correctly.

This issue [1] will not be solved by using DroidSansFallback.ttf
(which is shipped by fonts-android udeb) for Japanese.

It means that we need to switch font itself which contains Japanese
typeface to fix this issue.

In this commit, add fallback to apply custom gtkrc to
override existing style.

[1] Your Code Displays Japanese Wrong
https://heistak.github.io/your-code-displays-japanese-wrong/

Signed-off-by: Kentaro Hayashi 
---
 src/modules/frontend/gtk/di.c | 34 ++
 1 file changed, 34 insertions(+)

diff --git a/src/modules/frontend/gtk/di.c b/src/modules/frontend/gtk/di.c
index a6cb38f1..843624d4 100644
--- a/src/modules/frontend/gtk/di.c
+++ b/src/modules/frontend/gtk/di.c
@@ -45,6 +45,7 @@
 
 #include 
 #include 
+#include 
 
 #include "question.h"
 #include "database.h"
@@ -355,6 +356,36 @@ static GtkTextDirection get_text_direction(struct frontend * fe)
 return direction;
 }
 
+/** Set language specific style explicitly
+ *
+ * @param fe cdebconf frontend
+ */
+static void set_language_specific_style(struct frontend *fe)
+{
+gchar rc_language_path[PATH_MAX];
+gchar * rc_contents;
+gsize length;
+char * language = cdebconf_gtk_get_text(fe, "debconf/language",
+"Current language for installer");
+if (language) {
+/* Apply language specific custom style, such as
+ * font name.
+ *
+ * Typically, it is required to resolve Han Unification issue
+ * for rendering Japanese typeface correctly.
+ *
+ * [1] https://wiki.debian.org/DebianInstaller/GUIFonts
+ */
+g_snprintf(rc_language_path, PATH_MAX, "/etc/gtk-2.0/%s.gtkrc", language);
+if (g_file_test(rc_language_path, G_FILE_TEST_IS_REGULAR)) {
+if (g_file_get_contents(rc_language_path, &rc_contents, &length, NULL)) {
+gtk_rc_parse_string(rc_contents);
+g_free(rc_contents);
+}
+}
+}
+}
+
 /** Update various settings with the current language settings.
  *
  * @param fe cdebconf frontend
@@ -365,6 +396,9 @@ static void refresh_language(struct frontend * fe)
 gtk_rc_reparse_all();
 /* Adapt text direction. */
 gtk_widget_set_default_direction(get_text_direction(fe));
+
+/* Override specific style supplementary */
+set_language_specific_style(fe);
 }
 
 /** Update what needs to be updated on a new user interaction.
-- 
2.45.2

Re: Slow 'daily-build' command (Was: Bug#1091366: debian-installer: No graphical mode in sid)

2024-12-27 Thread Cyril Brulebois 
Hi,

Cyril Brulebois  (2024-12-25):
> daily-build calls `make all_list`, which is nice to reproduce the issue
> (it's mostly Makefile-based introspection).
> 
> With the brand new make in unstable, that looked like an easy target,
> and it is indeed: after downgrading make to testing's version in my sid
> chroot, `make all_list` only takes a few seconds, as expected.
> 
> If someone wants to pick that up, `make -d all_list` gives a lot of
> details about what's happening inside make.

Having a quick look at whether that's impacting daily builds being
performed on porterboxes, I'm seeing a huge penalty but it's much more
recent than the make(-dfsg) update in unstable:

The “Accepted” mail is dated: Wed, 18 Dec 2024 18:22:14 +.

  
https://tracker.debian.org/news/1595412/accepted-make-dfsg-441-1-source-into-unstable/

barriere:/home/d-i/di/logs/di-autobuild_daily-amd64-20241222- ends
with an unhide call at 20241222-00:14

barriere:/home/d-i/di/logs/di-autobuild_daily-amd64-20241223- ends
with an unhide call at 20241223-01:42, meaning 90 extra minutes.

I'm not going to dive into that right now (my focus is trying to get the
Trixie Alpha 1 train rolling), but I suspect this might be a case of
make's being installed already (as opposed to build-deps), and maybe not
getting upgraded by our tooling. Yet at some point we catch up with
newer versions, possibly when chroots are getting rebuilt (once a week
if memory serves). If that's confirmed, maybe it would be best to call
dist-upgrade in the first place, to avoid delaying seeing the impacts of
changes/regressions, and to make it easier to pinpoint/confirm theories
when we see something strange?

The same effect can be seen on at least platti and zelenka (there the
build is very fast, but got bumped from 1-2 minutes to 10+), between the
22nd and the 23rd as well.

TL;DR: Yes, this issue impacts regular d-i daily builds and wastes time
on porterboxes every night, it'd nice to rewrite the make introspection
soon-ish. As mentioned (I think) earlier that doesn't affect regular
builds, and therefore debian-installer uploads, so this can definitely
wait until Trixie Alpha 1 (I have no idea yet whether other uploads are
going to be required).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature