#1102253 debian-installer: Message is truncated in graphical installer when erasing storage for use with encrypted volume

Package:
debian-installer
Source:
debian-installer
Description:
Debian Installer documentation
Submitter:
Tyler Riddle
Date:
2025-05-17 18:03:05 UTC
Severity:
normal
Tags:
#1102253#5
Date:
2025-04-06 18:53:02 UTC
From:
To:
Dear Maintainer,

There is some message truncation during the phase of partition setup where a
storage device used for encrypted volumes is erased. I've taken screen shots
using a virtual machine but I don't see a way to attach images with the report-
bug tool. I'm supplying links to imgur instead.

Graphical installer showing message truncation: https://i.imgur.com/l1qLGNk.png
Text installer with no truncation: https://i.imgur.com/pFWV2kY.png
Galery of both images: https://imgur.com/a/XD3lPpc

Steps to reproduce:
  1) Boot Alpha 1 version of Trixie installer in Graphical mode
  2) Partition with encrypted storage
  3) Ensure option to erase storage device is enabled
  4) View message supplied when erasing data

#1102253#10
Date:
2025-04-19 23:12:28 UTC
From:
To:
Hi,

Tyler Riddle <cardboardaardvark@gmail.com> wrote (Sun, 06 Apr 2025 12:53:02 -0600):

A possible workaround is at
https://salsa.debian.org/installer-team/partman-crypto/-/merge_requests/10

#1102253#15
Date:
2025-04-21 08:22:30 UTC
From:
To:
In source package cdebconf, file src/modules/frontend/gtk/progress.c,
function create_progress_label(), the information text is displayed
below the progress bar with a GTKentry widget type which is a single
line text entry widget according to
<https://docs.gtk.org/gtk3/class.Entry.html>. The text is not really
truncated, you can drag and scroll it with the mouse.

I guess that in order to wrap, the information text should be displayed
with a different widget type which supports multiline text.

#1102253#20
Date:
2025-04-21 15:20:10 UTC
From:
To:
Hi,

Pascal Hambourg <pascal@plouf.fr.eu.org> (2025-04-21):

Let's not change anything there at this stage either. Rendering has been
a huge problem in the past, let's not take any risks for a problem that
affects I think a single screen, and for which documentation exists
anyway.



Cheers,