Bug#926539: Bug#987441: s390x installation bugs

[Cyril Brulebois]

Control: block 987441 by 926539
Control: block 987441 by 987788

Hi Valentin,

Thanks for your suggestions.

Valentin Vidic  (2021-05-02):
> Probably not critical, but maybe these installation bugs on s390x
> could be fixed for the release?
> 
> rootskel: steal-ctty no longer works on at least sparc64
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539

From skimming through the bug log, it seems it was initially a sparc64
problem, that was fixed in the kernel (inconsistent naming) eventually.
The same issue exists on s390x but isn't apparently going to get fixed
so we need to have d-i be smarter (hence the merge request)?

I'd suggest at least retitling the bug report to mention s390x (release
arch, affected) instead of sparc64 (port arch, no longer affected), to
lower the chances people could overlook this issue, thinking it's only
about a port arch.

I know it's been around for a while, but trying to get that merged right
now doesn't feeel right; trying to make the change only kick in on s390x
(in an attempt to fix s390x while not risking regressing elsewhere)
might eat up some time (lots of conditionals there), but it would feel a
little safer.

Would it make sense to have two for loops (one version “after” for s390x
only, and one version “before” for all archs) as a temporary measure for
bullseye? We could then switch all archs to the “after” version at the
beginning of the bookworm release cycle and deal with possible
regressions then?

In any cases, I'm happy to keep an eye on #926539 via #987441, even if
we don't block the release on it.

> debian-installer: qemu-system-s390x installation fails due to segfault in 
> main-menu
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987788

Yes, it seems works keeping an eye on. I had asked on tips on how to
test s390x but haven't had a chance to follow up on this yet.

Also adding to the list of bugs to keep an eye on (again, possibly not
blocking the release on its being resolved; we could have the issue
listed in errata, and possibly fixed in a point release).


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


signature.asc
Description: PGP signature

Processed: Re: Bug#987441: s390x installation bugs

[Debian Bug Tracking System]

Processing control commands:

> block 987441 by 926539
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for 
Bullseye
987441 was blocked by: 987368 987788 961056 987449 987568 987377 987587 926539
987441 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #987441 to the same blocks 
previously set
> block 987441 by 987788
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for 
Bullseye
987441 was blocked by: 987368 987788 961056 987449 987568 987377 987587 926539
987441 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #987441 to the same blocks 
previously set

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

Processed: Re: Bug#987441: s390x installation bugs

[Debian Bug Tracking System]

Processing control commands:

> block 987441 by 926539
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for 
Bullseye
987441 was blocked by: 987587 987377 987568 987449 987368
987441 was not blocking any bugs.
Added blocking bug(s) of 987441: 926539 and 961056
> block 987441 by 987788
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for 
Bullseye
987441 was blocked by: 987449 987568 961056 987377 987368 987587 926539
987441 was not blocking any bugs.
Added blocking bug(s) of 987441: 987788

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

Re: Bug#987441: bug in Debian 11 RC Installer

[Cyril Brulebois]

Luna Jernberg  (2021-05-03):
> Yeah, did not think about changing it to English, but yeah looks like
> it can be that, works in the text mode installer however

That's quite normal, libpango1.0-udeb (#987587) is only used in the
graphical installer. You could confirm that it's likely the very same
issue by testing D-I Bullseye Alpha 2, that's likely *not* affected (D-I
Bullseye Alpha 3 was already buggy though).

  https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-cd/


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


signature.asc
Description: PGP signature

Bug#987441: bug in Debian 11 RC Installer

[Luna Jernberg]

Yeah, did not think about changing it to English, but yeah looks like it
can be that, works in the text mode installer however

On Mon, May 3, 2021 at 7:55 AM Cyril Brulebois  wrote:

> Luna Jernberg  (2021-05-03):
> > Gets stuck before it tries to download package from the mirrors
>
> Thanks, Luna.
>
> This is Swedish, right?
>
> It seems very likely to be yet another occurrence of this bug, that
> usually triggers a title getting displayed but nothing else:
>   https://bugs.debian.org/987587
>
> I'm currently working on it.
>
> Thanks for your report (we usually prefer people use reportbug to submit
> bug reports, but your mail to the list was fine, especially since this
> issue can easily be associated with existing reports).
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Re: bug in Debian 11 RC Installer

[Cyril Brulebois]

Luna Jernberg  (2021-05-03):
> Gets stuck before it tries to download package from the mirrors

Thanks, Luna.

This is Swedish, right?

It seems very likely to be yet another occurrence of this bug, that
usually triggers a title getting displayed but nothing else:
  https://bugs.debian.org/987587

I'm currently working on it.

Thanks for your report (we usually prefer people use reportbug to submit
bug reports, but your mail to the list was fine, especially since this
issue can easily be associated with existing reports).


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


signature.asc
Description: PGP signature

Bug#987441: bug in Debian 11 RC Installer

[Luna Jernberg]

Gets stuck before it tries to download package from the mirrors

On Mon, May 3, 2021 at 7:40 AM Cyril Brulebois  wrote:

> Hi,
>
> Luna Jernberg  (2021-05-03):
> > i found a  bug when using the graphical installer in Virtualbox under
> > Ubuntu, and the step to show to package mirrors, don't show up, but it
> > works in the text installer
>
> Any chance you could attach a screenshot when that happens? Thanks.
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Re: Bug#987947: unblock (pre-approval): gtk+3.0/3.24.24-4

[Cyril Brulebois]

Hi Simon,

Simon McVittie  (2021-05-02):
> [ Risks ]
> This is obviously an important key package that lots of things depend
> on. Technically it also has a udeb, although I'm fairly sure d-i is
> still using GTK 2 and so the udeb is not actually used for anything
> yet.

That's absolutely correct: no objections to anything you would like to
update on your side.


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


signature.asc
Description: PGP signature

Re: bug in Debian 11 RC Installer

[Cyril Brulebois]

Hi,

Luna Jernberg  (2021-05-03):
> i found a  bug when using the graphical installer in Virtualbox under
> Ubuntu, and the step to show to package mirrors, don't show up, but it
> works in the text installer

Any chance you could attach a screenshot when that happens? Thanks.


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


signature.asc
Description: PGP signature

bug in Debian 11 RC Installer

[Luna Jernberg]

Hello!

i found a  bug when using the graphical installer in Virtualbox under
Ubuntu, and the step to show to package mirrors, don't show up, but it
works in the text installer

Bug#987441: Fwd: bug in Debian 11 RC Installer

[Luna Jernberg]

-- Forwarded message -
From: Luna Jernberg 
Date: Mon, May 3, 2021 at 4:25 AM
Subject: bug in Debian 11 RC Installer
To: , , Martin Jernberg <
droidbit...@gmail.com>


Hello!

i found a  bug when using the graphical installer in Virtualbox under
Ubuntu, and the step to show to package mirrors, don't show up, but it
works in the text installer

Bug#987968: flash-kernel: Tinkered a new DTB to make my version of Olimex A64-Olinuxino-eMMC boot

[Regis Etourmy]

Package: flash-kernel
Version: 3.104
Severity: wishlist

Dear Maintainer,

I could not install a Debian Bullseye that was able to boot on my Olimex 
A64-Olinuxino-eMMC -A64-OLinuXino-1Ge16GW version - with the nightly built SD 
card images. Nothing was happening after the message "Starting kernel".

So I followed the mitigation process proposed here: 
https://wiki.debian.org/InstallingDebianOn/Allwinner#Installing_on_systems_that_are_not_supported_out_of_the_box

As the nightly built DTB was giving the same result - nothing after 'starting 
kernel', I compiled a DTB from the DTS found in the device tree git repo. It 
dit not work better.

While I was trying to have a bootable system from the nightly built SD card 
images, I had noticed that a system install with  Olimex Teres images was 
nearly woking: it was able to boot, but hanged 30 seconds after the boot.

So I have used the Olimex Teres DTS. I have removed the parts relating to 
hardware not present on a64-Olinuxino-eMMc. The system can boot. It complains 
about vcc-p* not found. When I tried to add the parts related to vcc-p* from 
the a64-Olinuxino-eMMc DTS, the system could not boot anymore (again, nothing 
after 'Starting kernel').

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-6-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.75
ii  devio  1.2-1.2+b1
ii  initramfs-tools0.140
ii  linux-base 4.6
ii  mtd-utils  1:2.1.2-2
ii  ucf3.0043

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2021.01+dfsg-4

flash-kernel suggests no packages.

-- Configuration Files:
/etc/flash-kernel/db changed:
Machine: Olimex A64-Olinuxino-eMMC
Kernel-Flavors: arm64
DTB-Id: allwinner/sun50i-a64-olinuxino-emmc.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools


-- debconf information:
* flash-kernel/linux_cmdline: quiet

Re: Tentative summary of the AMD/ATI/NVidia issue

[Thorsten Glaser]

Cyril Brulebois dixit:

>Lucas Nussbaum  (2021-04-24):

>> C) Do nothing and document this in the release notes
>
>As said above, I strongly recommend against this.

Right… what about, add another Plan C…

C) When X won’t work, fail gracefully, show a console login

… and dump the above to Plan D?

(Perhaps doing this is a good idea in general, for when a
similar issue pops up in the future?)

bye,
//mirabilos
-- 
22:59⎜ glaub ich termkit is kompliziert | glabe nicht das man
damit schneller arbeitet | reizüberflutung │ wie windows │ alles evil
zuviel bilder │ wie ein spiel | 23:00⎜ die meisten raffen auch
nicht mehr von windows | 23:01⎜ bilderbücher sind ja auch nich
wirklich verbreitet als erwachsenen literatur   ‣ who needs GUIs thus?

Bug#987368: Installer fails at first menu "Choose language"

[Samuel Thibault]

Vagrant Cascadian, le dim. 02 mai 2021 14:36:46 -0700, a ecrit:
> On 2021-04-22, Frédéric Bonnard wrote:
> > Machine: Power10 machine but got it on Power8 as well
> 
> > This happens randomly when the installer menu starts, I get to the first
> > menu "Choose language", but it is red saying "An installation failed...
> > The failing step is: Choose language".
> 
> FWIW, I've seen this a few times on arm64 too.

I got it as well somtimes while testing, on arm and ppc with qemu. I
assumed it could be a qemu emulation bug. But it does happen only on
that screen, indeed.

Samuel

Bug#987368: Installer fails at first menu "Choose language"

[Vagrant Cascadian]

On 2021-04-22, Frédéric Bonnard wrote:
> Machine: Power10 machine but got it on Power8 as well

> This happens randomly when the installer menu starts, I get to the first
> menu "Choose language", but it is red saying "An installation failed...
> The failing step is: Choose language".

FWIW, I've seen this a few times on arm64 too.

I hate to admit I rebooted and tried again the few times it happened,
rather than dive into the details of the problem, but it *usually*
worked on the second try... so this may not be a deterministic bug.

I'll try again soon and try to get more details...

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#987441: s390x installation bugs

[Valentin Vidic]

Hi,

Probably not critical, but maybe these installation bugs on s390x could
be fixed for the release?

rootskel: steal-ctty no longer works on at least sparc64
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539

debian-installer: qemu-system-s390x installation fails due to segfault in 
main-menu
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987788

-- 
Valentin

Bug#987845: hardwired proxy settings by debian-installer with network-auto-config in proxy-auto-config network

[Rado S]

=- Geert Stappers wrote on Fri 30.Apr'21 at 22:04:09 +0200 -=

> On Fri, Apr 30, 2021 at 09:25:47PM +0200, Rado Q wrote:
> > Installation network setup was auto-configured while the system was
> > in a network with proxy-auto-config active.
> > 
> > Expectation:
> > when choosing auto-configure-network during installation, the
> > resulting system should be operative in every foreign environment.
> > (think of notebook in roaming use)
> > 
> > Result:
> > applications strictly following those hardwired configs can't operate
> > outside the original installation network, where the given proxy exists,
> > but nowhere else. PAC results during installation shouldn't be
> > 'hardwired' into the system to last when moving to another network.
> 
> Acknowledge on the problem.
> 
> Which possible solutions do we see?

How about having a boot process check for the network strategy
(fixed or dhcp), and if dhcp, let it discover the proxy by WPAD/PAC
and store it in /var/run, and have general config include it from
there, if it exists, like:

/etc/profile.d/proxy-check:

DYNPROXYCFG=/var/run/proxy-cfg
if [ -s "$DYNPROXYCFG" ]
then
. "$DYNPROXYCFG"
fi

Everything else not respecting those http_proxy vars would need
similar stuff. APT seems to have its own PAC features, which could/
should be used instead of storing fixed values, or use the same as
above (if APT/itude works with those http_proxy vars).

Rado

Bug#987947: unblock (pre-approval): gtk+3.0/3.24.24-4

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org, debian-boot@lists.debian.org

I'd like to update gtk+3.0 in bullseye to pick up an assortment of fixes
from upstream. Exactly *which* fixes is something I'm happy to discuss:
I've prepared a candidate package with a reasonable set. Does this
look acceptable?

unblock gtk+3.0/3.24.24-4

[ Reason ]
Backport various targeted fixes from upstream 3.24.25 up to 3.24.29,
avoiding lower-impact and higher-regression-risk parts (notably avoiding
theme and input-method changes, which have been more problematic).

[ Impact ]
Most of the changes here are about avoiding infrequent crashes, such
as LP: #1911036 which can happen during drag-and-drop when using the
proprietary NVIDIA driver. Please let me know if you need more information
on the impact of any of the crash fixes.

d/p/x11-Be-quiet-on-exit-by-default.patch silences warnings when a
GTK application exits in response to the X11 server going away. These
warnings go to the system log and create a lot of log noise at the
end of an X11 session (at which time they are completely harmless),
or if Xorg or Xwayland crashes (in which case we want users to report
the Xorg/Xwayland crash as a bug, rather than getting distracted by all
their GTK apps exiting and misinterpreting the log as implying that an
app crash is the root cause).

d/p/gdkpixbuf-drawable-Free-the-pixbuf-on-Cairo-error.patch fixes a
resource leak.

Fixing LP: #1919404 fixes visual appearance of a specific GNOME Shell
extension (and anything else with similar behaviour) on HiDPI displays.

d/p/fontchooser-Fix-some-since-annotations.patch is low-impact but also
low-risk; it corrects API documentation.

d/p/placesview-Open-location-even-if-mount-was-not-found.patch fixes
a regression in Nautilus v40 (not in bullseye), and perhaps other
file managers. With the gvfs backends for SMB (Samba, CIFS, Windows
Networking), the intention is that smb://192.168.1.1/ lists the shares
on 192.168.1.1 and smb://192.168.1.1/music displays a specific share,
but displaying smb://192.168.1.1/ was not possible. The version of nautilus
in bullseye is unaffected by this bug.

[ Tests ]
Most of the upstream unit tests are run at build-time and as autopkgtests.
Some tests that are known-broken upstream or are particularly sensitive
to implementation details of other packages are skipped.

Manual testing: I use GNOME daily, and have been using the newer upstream
releases in experimental, from which these changes were backported. I've
now switched to this proposed version to get it some more testing. Some
of the fixes here are also used in Ubuntu.

I have a machine with the NVIDIA driver which exhibits the warnings
silenced by d/p/x11-Be-quiet-on-exit-by-default.patch during session
logout, and I confirm that the patch does successfully silence them.

I have not attempted to reproduce the various crashes.

[ Risks ]
This is obviously an important key package that lots of things depend on.
Technically it also has a udeb, although I'm fairly sure d-i is still
using GTK 2 and so the udeb is not actually used for anything yet.

The changes are targeted and simple (avoiding NULL dereferences and that
sort of thing).

I'm not particularly attached to any of the specific fixes here, and
I'm happy to drop them or postpone them to bullseye-pu if the release
team consider them to be an unacceptable risk. I don't think any of the
changes have dependencies between them, so we can keep or drop any
particular change as needed.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing
diffstat for gtk+3.0-3.24.24 gtk+3.0-3.24.24

 changelog   |   43 +
 patches/Fix-a-possible-crash-in-gtk_show_uri.patch  |   27 +
 patches/Wayland-ignore-touch-tablet-events-on-destroyed-surfaces.patch  |  241 ++
 patches/cssshadowvalue-Apply-device-scale-to-the-offset-when-blur.patch |   30 +
 patches/fontchooser-Fix-some-since-annotations.patch|   44 +
 patches/gdkpixbuf-drawable-Free-the-pixbuf-on-Cairo-error.patch |   23 
 patches/label-Skip-updating-link-state-if-we-have-no-layout.patch   |   31 +
 patches/placesview-Open-location-even-if-mount-was-not-found.patch  |   46 +
 patches/scale-Fix-sporadic-criticals.patch  |   52 ++
 patches/series  |   11 
 patches/updateiconcache-Sort-list-of-entries.patch  |1 
 patches/x11-Be-quiet-on-exit-by-default.patch   |   49 ++
 patches/x11-Don-t-beep-on-untrusted-displays.patch  |   42 +
 patches/x11-dnd-Ignore-XErrors-from-the-COW.patch   |   36 +
 14 files changed, 676