Bug#1035588: marked as done (installation-reports: Installation of GNOME desktop fails (in openQA))
Your message dated Fri, 23 Jun 2023 13:15:41 +0200 with message-id <87zg4qsa3m@nimble.hk.hands.com> and subject line Re: Bug#1035588: installation-reports: Installation of GNOME desktop fails (in openQA) has caused the Debian Bug report #1035588, regarding installation-reports: Installation of GNOME desktop fails (in openQA) 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.) -- 1035588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal User: debian...@lists.debian.org X-Debbugs-Cc: p...@hands.com Boot method: CD Image version: daily netinst 20230505_1104 from https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/ Date: 2023-05-05T15:57:23 Machine: qemu running on AMD64 server osuosl3.debian.net See: https://openqa.debian.net/tests/144783 Partitions: https://openqa.debian.net/tests/144783/logfile?filename=complete_install- gdisk.txt -- GPT fdisk (gdisk) version 1.0.9 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *** Disk /dev/vda: 31457280 sectors, 15.0 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 71C86CFF-DC9F-4BC4-B99D-DB5CF15F1DB3 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 31457246 Partitions will be aligned on 2048-sector boundaries Total free space is 6077 sectors (3.0 MiB) Number Start (sector)End (sector) Size Code Name 1204829456383 14.0 GiB8300 Linux filesystem 52945843231455231 975.0 MiB 8200 Linux swap -- 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:[E] Comments/Problems: After the reboot the GNOME login screen is not shown, instead the screen stays black. Judging from the output of `journalctl -b`, sddm-greeter causes a core dump https://openqa.debian.net/tests/144783/logfile?filename=_graphical_wait_login- journal.txt systemd-coredump[917]: Process 873 (sddm-greeter) of user 113 dumped core. I've used the same ISO file on my Intel-based hardware, with a similar invocation of qemu, and there the ISO images worked fine. With kind regards, Roland Clobus PS: The netinst-RC2 image has the same issue -- 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 Tec
Bug#1036171: -
I can confirm this.
Using different install options of Debian installer produce different
sources.list. With default options selected of without internet
connection user receives system that can't be updated and where many
packages can't be installed without sources.list modifications
# STEPS TO REPRODUCE
1. Boot into official debian-12.0.0-amd64-DVD-1.iso
2. Select Graphical install
3. Proceed until step "Configure package manager" and question "Scan
extra installation media?"
4. Leave default option ("No")
5. Finish installation, boot into system
6. check /etc/apt/sources.list
# TEST RESULTS:
1. With "Scan extra installation media?" = "No" I've got sources.list
with such content:
```
deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
Binary-1 with firmware 20230610-10:23]/ bookworm main non-free-firmware
```
2. With "Scan extra installation media?" = "Yes" I've got sources.list
with such content:
```
deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
Binary-1 with firmware 20230610-10:23]/ bookworm main non-free-firmware
deb http://deb.debian.org/debian/ bookworm main non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main
non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security
main non-free-firmware
# bookworm-updates, to get updates before a point release is made;
# see
https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bookworm-updates main non-free-
firmware
deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-
firmware
```
3. With Calamares installer from live media ("debian-live-12.0.0-amd64-
gnome.iso") I've got sources.list with such content:
```
# See https://wiki.debian.org/SourcesList for more information.
deb http://deb.debian.org/debian bookworm main non-free-firmware
deb-src http://deb.debian.org/debian bookworm main non-free-firmware
deb http://deb.debian.org/debian bookworm-updates main non-free-
firmware
deb-src http://deb.debian.org/debian bookworm-updates main non-free-
firmware
deb http://security.debian.org/debian-security/ bookworm-security main
non-free-firmware
deb-src http://security.debian.org/debian-security/ bookworm-security
main non-free-firmware
# Backports allow you to install newer versions of software made
available for this release
deb http://deb.debian.org/debian bookworm-backports main non-free-
firmware
deb-src http://deb.debian.org/debian bookworm-backports main non-free-
firmware
```
Bug#1036171: debian-installer: /etc/apt/sources.list isn't populated if mirror can't be reached during installation
On Fri, 23 Jun 2023 18:51:02 +0300 xalt7x.serv...@gmail.com wrote:
> I can confirm this.
> Using different install options of Debian installer produce different
> sources.list. With default options selected of without internet
> connection user receives system that can't be updated and where many
> packages can't be installed without sources.list modifications
>
> # STEPS TO REPRODUCE
> 1. Boot into official debian-12.0.0-amd64-DVD-1.iso
> 2. Select Graphical install
> 3. Proceed until step "Configure package manager" and question "Scan
> extra installation media?"
> 4. Leave default option ("No")
> 5. Finish installation, boot into system
> 6. check /etc/apt/sources.list
>
> # TEST RESULTS:
>
> 1. With "Scan extra installation media?" = "No" I've got sources.list
> with such content:
> ```
> deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
> Binary-1 with firmware 20230610-10:23]/ bookworm main non-free-
firmware
> ```
>
> 2. With "Scan extra installation media?" = "Yes" I've got
sources.list
> with such content:
>
> ```
> deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
> Binary-1 with firmware 20230610-10:23]/ bookworm main non-free-
firmware
>
> deb http://deb.debian.org/debian/ bookworm main non-free-firmware
> deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
>
> deb http://security.debian.org/debian-security bookworm-security main
> non-free-firmware
> deb-src http://security.debian.org/debian-security bookworm-security
> main non-free-firmware
>
> # bookworm-updates, to get updates before a point release is made;
> # see
>
https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
> deb http://deb.debian.org/debian/ bookworm-updates main non-free-
> firmware
> deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-
> firmware
> ```
>
> 3. With Calamares installer from live media ("debian-live-12.0.0-
amd64-
> gnome.iso") I've got sources.list with such content:
>
> ```
> # See https://wiki.debian.org/SourcesList for more information.
> deb http://deb.debian.org/debian bookworm main non-free-firmware
> deb-src http://deb.debian.org/debian bookworm main non-free-firmware
>
> deb http://deb.debian.org/debian bookworm-updates main non-free-
> firmware
> deb-src http://deb.debian.org/debian bookworm-updates main non-free-
> firmware
^ There's mistake in the description.
Choice that affects resulting sources.list is on the step
"Configure the package manager" > "Use a network mirror?"
Bug#1038958: installation-reports: gnome-control-center very slow to start - modemmanager timeout
Package: installation-reports Severity: normal After a Debian11 to Debian12 upgrade on my Desktop NUC Intel gnome-control-center very slow to start, I discover with gnome-control-center -v a modemmanager timeout, after modemmanager removed problem seems solved on my system HTH Alessandro - Lota == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u4" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux nuc 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9a49] (rev 01) lspci -knn: DeviceName: Onboard - Video lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core Processor PCIe Controller [8086:9a09] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #1 [8086:9a25] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.2 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #2 [8086:9a27] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Device [8086:9a11] (rev 01) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt USB Controller [8086:9a13] (rev 01) lspci -knn: DeviceName: Onboard - Other lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:0d.2 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt NHI #0 [8086:9a1b] (rev 01) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Device [:] lspci -knn: 00:0d.3 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt NHI #1 [8086:9a1d] (rev 01) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Device [:] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM [8086:a0ef] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: 00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 20) lspci -knn: DeviceName: Onboard - Ethernet lspci -knn: Subsystem: Intel Corporation Device [8086:0070] lspci -knn: Kernel modules: iwlwifi lspci -knn: 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 [8086:a0e8] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 [8086:a0e9] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-LP Management Engine Interface [8086:a0e0] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Device [8086:a0e3] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: Kernel driver in use: serial lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a0d3] (rev 20) lspci -knn: DeviceName: Onboard - SATA lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:a0b1] (rev 20) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Tiger Lake-LP LPC Controller [8086:a082] (rev 20) lspci -knn: DeviceName: Onboard - Other lspci -knn: Subsystem: Intel Corporation Device [8086:3003] lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio
Re: Bug#1036933: screen-udeb: Should screen really be installed setgid utmp?
Control: tags -1 + patch On 2023-05-29 21:51 +0200, Cyril Brulebois wrote: > Hallo Sven, > > Sven Joachim (2023-05-29): >> Recently I noticed that the screen program in the screen-udeb package >> is installed setgid utmp, and I wonder if this actually makes any >> sense. While I do not have much experience with the installer, I >> would expect it to run all programs as root anyway, so there should be >> no need for setgid there. > > Without being specifically knowledgeable about screen in general or > in the installer's context in particular, I'm 100% with you here. > >> Having screen installed setgid sets up a secure execution environment >> that precludes the use of certain environment variables, see the >> "Secure-execution mode" section in ld.so(8). Recently ncurses has >> also started to restrict such programs, see #1034372. >> >> Hopefully none of this matters much. I have CC'ed debian-boot, as the >> people working on the installer will be much more qualified to give >> advice than I am. > > Given the first sentence of this last paragraph, it looks like we're not > considering doing anything for Bookworm at this time (or at all). Surely. I would not expect that any changes will be made in further Bookworm point releases, unless somebody reports an actual problem. > We could try it out with Trixie Alpha 1, and see how it goes? Attached is a patch which installs /usr/bin/screen with standard permissions in the udeb. I have tested that it builds correctly, but not if it works as intended. This also removes the need for fakeroot in the build process, see the second patch. :-) Cheers, Sven From 6f4cf000e3e39d1ea78663546a6e8c38597f6f90 Mon Sep 17 00:00:00 2001 From: Sven Joachim Date: Fri, 23 Jun 2023 21:02:18 +0200 Subject: [PATCH 1/2] Do not install /usr/bin/screen setgid utmp in the udeb A setgid program does not really make sense in the installer context, as root is the only user there. Besides, setgid programs are somewhat restricted for security reasons. e.g. many environment variables have no effect. --- debian/rules | 7 --- 1 file changed, 7 deletions(-) diff --git a/debian/rules b/debian/rules index 9685e9f..49ef9f0 100755 --- a/debian/rules +++ b/debian/rules @@ -55,10 +55,6 @@ override_dh_auto_install: rm -f $(ROOT)/usr/bin/screen $(ROOT_UDEB)/usr/bin/screen mv -f $(ROOT)/usr/bin/screen* $(ROOT)/usr/bin/screen mv -f $(ROOT_UDEB)/usr/bin/screen* $(ROOT_UDEB)/usr/bin/screen - # make it setgid utmp only in udeb - chown root:utmp $(ROOT_UDEB)/usr/bin/screen - chmod 2755 $(ROOT_UDEB)/usr/bin/screen - chmod 755 $(ROOT)/usr/bin/screen # Fix package-contains-info-dir-file, remove /usr/share/info/dir.gz rm -f $(ROOT)/usr/share/info/dir* # Remove documentation from udeb @@ -69,6 +65,3 @@ override_dh_installinit: override_dh_installtmpfiles: dh_installtmpfiles --name=screen-cleanup - -override_dh_fixperms: - dh_fixperms -X/usr/bin/screen -- 2.40.1 From f696247fa6a0343030c90ebff671f215c2a6b79a Mon Sep 17 00:00:00 2001 From: Sven Joachim Date: Fri, 23 Jun 2023 21:30:08 +0200 Subject: [PATCH 2/2] Set Rules-Requires-Root to no With all files having standard ownerships and permissions, there is no need for fakeroot anymore. --- debian/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/control b/debian/control index be07368..657fcc1 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,7 @@ Build-Depends: debhelper-compat (= 13), Homepage: https://savannah.gnu.org/projects/screen Vcs-Git: https://salsa.debian.org/debian/screen.git Vcs-Browser: https://salsa.debian.org/debian/screen -Rules-Requires-Root: binary-targets +Rules-Requires-Root: no Package: screen Architecture: any -- 2.40.1
