Control: reassign -1 mate-desktop-environment
Control: retitle -1 Not possible to adjust location/timezone via UI preferences
Hi,
Am 5. Mai 2025 20:34:17 MESZ schrieb Peter Ehlert :
>However, these problems still exist as before:
>
>"when I try to set Clock Preferences-> Choose Location the cloc
Processing control commands:
> reassign -1 mate-desktop-environment
Bug #1104713 [installation-report] Package: installation-report
Bug reassigned from package 'installation-report' to 'mate-desktop-environment'.
Ignoring request to alter found versions of bug #110
On 05/05/2025 at 20:34, Peter Ehlert wrote:
However, these problems still exist as before:
"when I try to set Clock Preferences-> Choose Location the clock it
closes and must be reset
Time and Date Manager is grayed out"
I am not surprised:
On 5/5/25 10:12, Pascal Hambourg wrote:
Maybe som
However, these problems still exist as before:
"when I try to set Clock Preferences-> Choose Location the clock it
closes and must be reset
Time and Date Manager is grayed out"
On 5/5/25 11:28, Peter Ehlert wrote:
fresh install alongside with daily build:
debian-testing-amd64-netinst.iso 2025-
fresh install alongside with daily build:
debian-testing-amd64-netinst.iso 2025-05-05 17:24
on first boot --- time is correct... no other testing of the system yet
thanks to all
On 5/5/25 10:12, Pascal Hambourg wrote:
Peter Ehlert wrote (Sun, 4 May 2025 18:22:56
-0700):
debian-trixie-DI-alph
Peter Ehlert wrote (Sun, 4 May 2025 18:22:56 -0700):
debian-trixie-DI-alpha1-amd64-netinst.iso
Time was not set correctly, it is GMT when I specified Pacific time
zone.
syslog:
May 4 18:14:13 anna[4299]: DEBUG: retrieving tzsetup-udeb 1:0.125
...
May 4 18:20:02 tzsetup: Warning: ignoring in
Hi,
Peter Ehlert wrote (Sun, 4 May 2025 18:22:56 -0700):
> Time was not set correctly, it is GMT when I specified Pacific time zone.
> when I try to set Clock Preferences-> Choose Location the clock it
> closes and must be reset
> Time and Date Manager is grayed out
>
> Please make sure that an
Your message dated Sat, 5 Apr 2025 17:10:34 +0200
with message-id <71a23fc4-129f-4498-b712-0c56af101...@rclobus.nl>
and subject line Resolved
has caused the Debian Bug report #1036319,
regarding installation-reports: Multiple Installation report for RC3 on openQA
to be marked as done.
This
Your message dated Sat, 15 Mar 2025 20:03:41 +
with message-id
<15a2dfbe3c5583ff875c0f2e34d8df88e53821c7.ca...@adam-barratt.org.uk>
and subject line Closing report of successful Debian installation
has caused the Debian Bug report #958844,
regarding installation-reports: installation
On 24/01/2025 à 00:14, Charles Curley wrote:
The installation was preseeded using a configuration that has worked
well on this and other machines. Normally the network setup runs
correctly. However this time the Ethernet was changed from eth0 to
enp1s0, as usual, but the entry in /etc/network/in
Your message dated Wed, 1 Jan 2025 19:37:07 +0100
with message-id <20250101193707.9a5ad44457f9af39aeb0a...@mailbox.org>
and subject line Re: Bug#1025186: installation-reports: Successful Installation
Report
has caused the Debian Bug report #1025186,
regarding installation-reports: Succ
Package: installation-reports
Installation date: 2024-12-28
Installation image: debian-trixie-DI-alpha1-armhf-netinst.iso
Installation media: USB flash drive
Boot mode: U-Boot EFI on micro-SD card (no EFI boot variables)
Target: Olimex A20-OLinuXIno-LIME2 (Allwinner A20 ARMv7 SoC)
Tasksel selecte
Your message dated Sun, 6 Oct 2024 21:08:01 +0200
with message-id <20241006210801.af3f21d40c981c45faf0d...@mailbox.org>
and subject line Re: #1025522 Debian successful installation report for Dell
Inspiron 5482
has caused the Debian Bug report #1025522,
regarding Debian successful instal
Package: debian-installer
Severity: normal
X-Debbugs-Cc: charlescur...@charlescurley.com
Dear Maintainer,
I took delivery of two Ace Magic T8+ computers recently.
https://www.acemagic.com/products/t8plus I am bringing one up as a router
running Debian 12.2 (Bookworm).
A full hardware probe of
On 25/11/2023 at 22:29, David Hillman wrote:
On 11/25/23 01:37, Cyril Brulebois wrote:
Extracting /var/log/syslog would be useful to understand what's going on
there. (...)
Thanks Cyril. This system is running Debian 12, so there is no
/var/log/syslog.
Cyril meant the installer syslog, whic
David Hillman (2023-11-25):
> Thanks Cyril. This system is running Debian 12, so there is no
> /var/log/syslog. As I mentioned in the original report, I found nothing
> apparently related in the Journal.
I'm confused. You filed an installation report regarding a failure to
rec
On 11/25/23 01:37, Cyril Brulebois wrote:
Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's
Lennart Sorensen (2023-11-25):
> I suspect you are missing the firmware file for the network port. I think
> this one:
>
> firmware-misc-nonfree: /lib/firmware/tigon/tg3.bin
>
> The installer probably does not include that.
The netinst *definitely* does ship that package:
https://cdimage.d
On Fri, Nov 24, 2023 at 12:34:50PM -0600, David Hillman wrote:
>
> Package: installation-reports
>
> Boot method: USB stick
> Image version:
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
> Date: 2023-November-23 11PM GMT
>
> Machine: Dell R720
> Pro
On Saturday, 25 November 2023 08:37:09 CET Cyril Brulebois wrote:
> Hard to tell without any logs.
The output of `lsmod` and `dmesg` from both Ubuntu and Debian may also help to
figure out why it's working in one but not the other.
signature.asc
Description: This is a digitally signed message pa
Hi,
Am 24. November 2023 23:54:49 MEZ schrieb David Hillman
:
>On 11/24/23 12:59, Holger Wansing wrote:
>Thanks Holger. I could do that, but that would completely defeat the purpose.
> I installed Debian 12 on this machine as a test, to confirm that everything
>necessary works, before installi
Hi David,
David Hillman (2023-11-24):
> Thanks Holger. I could do that, but that would completely defeat the
> purpose. I installed Debian 12 on this machine as a test, to confirm that
> everything necessary works, before installing it on a dozen or so other
> similar machines.
>
> And clearly
On 11/24/23 12:59, Holger Wansing wrote:
Hi,
David Hillman wrote (Fri, 24 Nov 2023 12:34:50 -0600):
Ubuntu 20 and 22 installers work just fine on the same hardware, so this
is a Debian-specific issue. All four interfaces work just fine under
both Ubuntu 20 and 22, but are totally dysfunctiona
Hi,
David Hillman wrote (Fri, 24 Nov 2023 12:34:50 -0600):
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this
> is a Debian-specific issue. All four interfaces work just fine under
> both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.
Maybe you could t
Package: installation-reports
Boot method: USB stick
Image version:
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
Date: 2023-November-23 11PM GMT
Machine: Dell R720
Processor: 2 x Xeon E5-2650
Memory: 192GB
Base System Installation Checklist:
[O] =
Processing control commands:
> close -1
Bug #1035392 [installation-reports] installation-reports: Installation Report:
Bookworm RC2: Raspberry Pi 400 (netboot)
Marked Bug as done
--
1035392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035392
Debian Bug Tracking System
Contact
Followup-For: Bug #1035392
Control: close -1
(closing; I'll likely re-attempt an install on the same hardware with a more
recent release of Debian in future, for comparison purposes)
On Thu, 15 Jun 2023 18:28:51 +0100 Abhinav Praveen
wrote:
> This issue persists in the current Debain 12 installer:
debian-12.0.0-amd64-netinst.iso
> --
> Abhinav Praveen
>
>
The issue is also in the latest installer, debian-12.1.0-amd64-netinst.iso
This issue persists in the current Debain 12 installer:
debian-12.0.0-amd64-netinst.iso
--
Abhinav Praveen
Package: installation-reports
Severity: normal
X-Debbugs-Cc: p...@hands.com
Boot method: CD in openQA
Image version:
https://cdimage.debian.org/cdimage/bookworm_di_rc3/amd64/iso-cd/debian-
bookworm-DI-rc3-amd64-netinst.iso
Date:
Machine: openQA x86_64 qemu video: qxl memory: 2GB. SeaBIOS and Ti
On May 4, 2023 3:35:40 PM Pascal Hambourg wrote:
On 04/05/2023 at 16:21, Peter Ehlert wrote:
"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_
On 04/05/2023 at 16:21, Peter Ehlert wrote:
"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)
I selected /dev/sde and pre
der
installation" ? If yes, what option did you select exactly ?
from my initial installation-report:
"when install was finished, a list of drives was displayed, asking where
to install GRUB.
the install drive was highlighted
I selected the drive with bios_grub
the display showed "in
Package: installation-reports
Followup-For: Bug #1035392
> The only customized dnsmasq setting required was:
>
> pxe-service=0, "Raspberry Pi Boot"
Oops, I lied. There was one other relevant dnsmasq setting:
dhcp-boot=bootnetaa64.efi
(telling the device what EFI filename to retrieve and ru
On 02/05/2023 at 15:21, Peter Ehlert wrote:
DI asks on which drive to install GRUB
User says disk X
DI attempts to install on Drive Y
result ... GRUB does not get installed at all
This is completely different from what I understood.
The statement "GRUB does not get installed at all" is refute
Package: installation-reports
Severity: normal
Tags: d-i
Boot method: network
Image version: [2023-04-28] Bookworm Release Candidate 2 Installer
Date: 2023-05-02
Machine: Raspberry Pi 400
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev devtmpfs 18
On 4/30/23 01:17, Pascal Hambourg wrote:
On 30/04/2023 at 01:47, Peter Ehlert wrote:
On 4/29/23 15:41, Pascal Hambourg wrote:
On 29/04/2023 at 16:02, Peter Ehlert wrote:
reboot gave me the Old GRUB menu, not including my new system.
What do you mean by "old GRUB menu" ? The GRUB which wa
On 30/04/2023 at 01:47, Peter Ehlert wrote:
On 4/29/23 15:41, Pascal Hambourg wrote:
On 29/04/2023 at 16:02, Peter Ehlert wrote:
reboot gave me the Old GRUB menu, not including my new system.
What do you mean by "old GRUB menu" ? The GRUB which was previously
installed on /dev/sdb ?
the
On 4/29/23 15:41, Pascal Hambourg wrote:
Hello Peter,
On 29/04/2023 at 16:02, Peter Ehlert wrote:
Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub
install was on a drive without bios_grub
when install was fini
Hello Peter,
On 29/04/2023 at 16:02, Peter Ehlert wrote:
Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub
install was on a drive without bios_grub
when install was finished, a list of drives was displayed, asking
On 4/29/23 09:21, Steve McIntyre wrote:
On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:
On 4/29/23 07:23, Steve McIntyre wrote:
Hi Peter,
Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.
there i
On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:
>
>On 4/29/23 07:23, Steve McIntyre wrote:
>> Hi Peter,
>>
>> Could you please share a copy of the installer logs? You should be
>> able to find them in /var/log/installer on the installed system.
>there is no file "installer" in /var/l
Hi Peter,
Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.
On Sat, Apr 29, 2023 at 07:02:43AM -0700, Peter Ehlert wrote:
>Package: grub-installer
>Boot method: USB
>Image version: debian-bookworm-DI-rc2-amd64-netin
Package: grub-installer
Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
download from Debian
Date: 2023-04-28 ~17
Machine: HP Z820 Workstation
Processor: 2x 8-core model: Intel Xeon E5-2687W
Memory: 47.06 GiB
Partitions:
peter@RC2net:~$ df -T
Filesystem Type 1K-bl
Your message dated Wed, 22 Mar 2023 19:49:28 +
with message-id
and subject line Bug#1033325: fixed in installation-report 2.87
has caused the Debian Bug report #1033325,
regarding installation-report: store and report firmware information
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #1033325 [installation-report] installation-report: store and report
firmware information
Added tag(s) pending.
--
1033325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033325
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
This is still a problem to this day and the bookworm freeze is right
around the corner...
Package: installation-reports
Boot method: USB stick
Image version:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.5.0-live+nonfree/amd64/iso-hybrid/debian-live-11.5.0-amd64-kde+nonfree.iso
Date: 02 October 2022
Machine: Dell Inspiron 5482
Processor: # dmidecod
Package: installation-reports
Severity: wishlist
X-Debbugs-Cc: spenserpulleyk...@yahoo.com
(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)
Boot method: USB
Image version:
https://cdimage.debian.org/debia
Processing control commands:
> severity -1 important
Bug #1005308 [installation-reports] Installation Report: Crash of Debian
netinst iso in Xen HVM guest
Severity set to 'important' from 'normal'
--
1005308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005308
Deb
installation-report 2.80 is marked for autoremoval from testing on 2022-06-30
It (build-)depends on packages with these RC bugs:
1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183,
CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192
https://bugs.debian.org
Package: installation-reports
Boot method: DVD
Image version:Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64
NETINST 20211218-11:12
Date: 31st Mar 2022
Machine:AMD A4-4000 APU with Radeon(tm) HD Graphics
BIOS: MSI FM2-A75MA-P33
Partitions:
/dev/sda1 FAT32 - unused
sda2 FAT16
(charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
installation-report depends on no packages.
Versions of packages installation-report recommends:
ii pciutils 1:3.5.2-1
ii reportbu
Your message dated Sun, 16 Jan 2022 13:22:09 +0100
with message-id <20220116132209.f5d2130cc006cf61f4d0f...@mailbox.org>
and subject line Re: Bug#988797: RC1 installation report
has caused the Debian Bug report #988797,
regarding RC1 installation report
to be marked as done.
This means th
Hi,
"Andrew M.A. Cater" wrote (Thu, 20 May 2021 18:32:00
+):
> On Thu, May 20, 2021 at 10:59:37AM +0200, Paul van der Vlis wrote:
> > Op 19-05-2021 om 20:06 schreef Cyril Brulebois:
> > > I think deactivating cdrom entries was implemented several release
> > > cycles ago. That should be the
Your message dated Sun, 16 Jan 2022 12:41:40 +0100
with message-id <20220116124140.628d7a55b6a1101100458...@mailbox.org>
and subject line Re: #989300 Bullseye installation report
has caused the Debian Bug report #989300,
regarding Bullseye installation report
to be marked as done.
This mean
> Initial boot: [O]
> Detect network card:[E]
> Configure network: [E]
> Detect media: [O]
> Load installer modules: [O]
> Detect hard drives: [O]
> Partition hard drives: [O]
> Install base system:[O]
> Clock/timezone setup: [O]
> User/password setup:
Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #292513,
regarding installation-report: Unable to install grub-pc on LVM/RAID5
On 2021-10-02, Vagrant Cascadian wrote:
> On 2021-02-15, Vieno Hakkerinen wrote:
>> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
>> to use a @rootfs subvolume for btrfs the linux bootargs need to have
>> set "rootflags=subvol=@rootfs". This was not set during configuration
>
On 2021-02-15, Vieno Hakkerinen wrote:
> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
> to use a @rootfs subvolume for btrfs the linux bootargs need to have
> set "rootflags=subvol=@rootfs". This was not set during configuration
> of flash-kernel. Without this argument debia
Hi,
Gunnar Wolf wrote (Tue, 19 May 2020 00:33:32 -0500):
> The Buster installer could not find my wireless card (RTL 8821CE).
>
> I performed the install using a spare external wireless interface; after
> booting to the installed system, I found an unofficial module supporting
> this hardware at
Your message dated Sun, 29 Aug 2021 21:12:05 +0200
with message-id <20210829211205.5cf88e58c35cf70db3aa7...@mailbox.org>
and subject line Closing successful installation-reports bugs
has caused the Debian Bug report #991899,
regarding RC3 installation report
to be marked as done.
This mean
Your message dated Sun, 29 Aug 2021 21:11:06 +0200
with message-id <20210829211106.6e971be92f233e38a28ea...@mailbox.org>
and subject line Closing installation-reports bugs without further information
has caused the Debian Bug report #962802,
regarding Installation Report
to be marked a
Your message dated Sun, 29 Aug 2021 21:11:06 +0200
with message-id <20210829211106.6e971be92f233e38a28ea...@mailbox.org>
and subject line Closing installation-reports bugs without further information
has caused the Debian Bug report #961089,
regarding installation-report bullseye alpha2
Your message dated Sun, 29 Aug 2021 21:09:59 +0200
with message-id <20210829210959.f3d5b403cce267ff9e69d...@mailbox.org>
and subject line Closing bugreports related to missing/not installed firmware
has caused the Debian Bug report #963755,
regarding installation-report: fails to boot with
m: Cyril Brulebois
Sent: Monday, August 23, 2021 06:00
To: lucas; 992...@bugs.debian.org
Cc: pkg-raspi-maintain...@alioth-lists.debian.net
Subject: Re: Bug#992774: installation-report
Hi,
lucas (2021-08-23):
> Installation was successful except for disabled usb port.
Thanks for your report. F
Hi,
lucas (2021-08-23):
> Installation was successful except for disabled usb port.
Thanks for your report. FWIW we deal with installations that were
performed using the Debian Installer; I'm putting the maintainers of the
relevant Raspberry Pi tooling in copy.
> Documentation for hardware (Ras
Package: installation-reports
Boot method: Flashing eMMC
Image version:
https://raspi.debian.net/verified/20210718_raspi_4_bullseye.img.xz
Date: 20-08-2021, 15:08
Machine: Raspberry Pi Compute Module 4 IO Board
Processor: Broadcom BCM2711 quad-core Cortex-A72 (ARM v8) 64-bit SoC
Memory: 8G
Package: installation-reports
Boot method:
Date: Tuesday Aug 3 3:30 PM
Machine: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03)
Subsystem: Gigabyte Technology Co., Ltd GA-EP45-DS5/GA-EG45M-DS2H Motherboard
[1458:5000]
Processor: Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.
Package: installation-reports
Severity: normal
See attached file.
Thank you for your hard work on Debian !
Filippo
Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using g
Package: installation-reports
Version: 2.71
Severity: normal
(report done from another macn
-- Package-specific info:
Boot method: DVD (Xen PV mode)
Image version:
https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-10.10.0-amd64-DVD-1.iso.torrent
2021-06-19 19:20
Date: 2021-06-20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Cyril,
you are welcome.
On Thu, 17 Jun 2021 15:23:02 +0200
Cyril Brulebois wrote:
> Hallo Oliver,
>
> And thanks for your report.
>
> Oliver Psotta (2021-06-17):
> > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
PS: I forgot to mention that Gnome forgets the settings of screen
brightness after restarts. Same bug with Ubuntu. I could file a bug
report. Could you point me to the package that is relevant here? Thanks!
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAd
Hallo Oliver,
And thanks for your report.
Oliver Psotta (2021-06-17):
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot: [O ]
> Detect network card:[E ]
> Configure network: [O ]
> Detect media: [E ]
> Load installer modules: [E
Package: installation-reports
Severity: normal
(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)
Boot method: USB
Image version:
https://cdimage.debian.org/cdimage/bullseye_di_rc2/amd64/iso-cd/debian-bulls
Hi Cyril,
thanks for the analysis.
On Thu, Jun 10, 2021 at 05:16:31PM +0200, Cyril Brulebois wrote:
> May 25 11:15:32 localechooser: info: System locale
> (debian-installer/locale) = 'en_US.UTF-8'
> May 25 11:15:32 localechooser: info: Set debian-installer/language =
> 'en_US:en'
>
Marc Haber (2021-06-09):
> I have attached the installer's syslog of a new installation. All
> issues that I reported were observed during this installation.
Thanks, this sticks out:
May 25 11:15:32 localechooser: info: System locale
(debian-installer/locale) = 'en_US.UTF-8'
May 25 11:1
On Wed, Jun 09, 2021 at 12:24:33AM +0200, Geert Stappers wrote:
> Repeating this:
I apologize for waiting for delivery of a new usb stick so that the
new installation would not be a complete waste of time.
> If you were to retry the installation, saving /var/log/syslog manually
> before rebooting
Hi,
Cyril Brulebois wrote (Tue, 8 Jun 2021 17:07:52 +0200):
> Marc Haber (2021-06-08):
> > Since my default domain types differently with US and DE keyboard, I
> > guess this might be an actual regression, I would have noticed this in
> > earlier versions of the installer.
>
> I guess someone c
On Tue, Jun 08, 2021 at 09:49:15PM +0200, Marc Haber wrote:
>
> The more pressing issue IMO is the deletion of /sbin/start-stop-daemon.
>
Repeating this:
If you were to retry the installation, saving /var/log/syslog manually
before rebooting into the installed system would be useful. Without it,
On Tue, Jun 08, 2021 at 09:27:57PM +0200, Holger Wansing wrote:
> I checked with rc1 and the *brandnew* rc2 netinst images on amd64 qemu
> VM machine (text installer), and I cannot reproduce such issue with wrong
> keyboard layout; German is correctly available immediately after the
> "Configure
installer most of the
time, and I don't know the specifics of the text version by heart.
> > Simply /var/log/syslog for the main log. Other files are mentioned
> > there:
> >
> > https://salsa.debian.org/installer-team/installation-report/-/blob/master/debian/installa
r source packages show 3 possibilities:
> - debootstrap
> - debian-installer-utils
> - apt-setup (code apparently copied from d-i-utils until some clean-up
>happens, which never did)
>
> > And, the installed system does neither have /var/log/installer nor
> >
ean-up
happens, which never did)
> And, the installed system does neither have /var/log/installer nor
> /var/log/debian-installer. This is also reproducible :-( Where would
> I find the files that get copied to /target/var/log/installer in the
> still running installer?
Simply /var
n the
still running installer?
Greetings
Marc
-- Package-specific info:
installation-report depends on no packages.
Versions of packages installation-report recommends:
ii pciutils 1:3.7.0-5
ii reportbug 7.10.3
installation-report suggests no packages.
-- no debconf information
On Thu, May 20, 2021 at 10:59:37AM +0200, Paul van der Vlis wrote:
> Op 19-05-2021 om 20:06 schreef Cyril Brulebois:
> > Goedendag Paul,
> >
> > and thanks for your report.
> >
> > Paul van der Vlis (2021-05-19):
>
> Correction, I did use: "pci=noaer", no capitals.
>
> I guess this will become
Goedendag Paul,
and thanks for your report.
Paul van der Vlis (2021-05-19):
> I did install Debian on an Acer laptop. The installation went OK, but
> I have some things to tell:
>
> 1. After the installation the 240GB SSD was after a short period full
> with PCIe AER errors in the logs. I thin
Package: installation-reports
I did install Debian on an Acer laptop. The installation went OK, but I
have some things to tell:
1. After the installation the 240GB SSD was after a short period full
with PCIe AER errors in the logs. I think it's good to tell about
errors in the logs, but doi
Your message dated Fri, 23 Apr 2021 23:25:23 +0200
with message-id <20210423212523.ifn6kdifh3rk3...@mraw.org>
and subject line Re: Bug#985832: installation report: netboot debian-installer
kernel too old
has caused the Debian Bug report #985832,
regarding installation report: netboot
Your message dated Thu, 15 Apr 2021 14:19:57 +0200 (CEST)
with message-id
and subject line closing successfull installation report
has caused the Debian Bug report #986894,
regarding installation report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 15 Apr 2021 14:09:26 +0200 (CEST)
with message-id
and subject line closing successfull installation report
has caused the Debian Bug report #973530,
regarding installation-report: successful installation on SD card on EEE PC,
runs on X230
to be marked as done.
This means
Your message dated Thu, 15 Apr 2021 14:02:00 +0200 (CEST)
with message-id
and subject line closing successfull installation report
has caused the Debian Bug report #984727,
regarding installation-reports: just an installation report
to be marked as done.
This means that you claim that the
Package: installation-reports
Boot method: DVD 1
Image version:
https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-dvd/
Date: 04/12/2021 23:00 UTC-5
Machine: Desktop
Processor: Intel Core i5-8600k
Memory: 16.0 GiB
Partitions:
S.ficheros Tipo bloques de 1KUsados Disponibl
Package: installation-reports
Boot method: SSD built with Rufus using this installation guide:
https://www.raspberrypi.org/forums/viewtopic.php?f=50&t=282839
Image version: Debian 11 ARM64 net install ISO
Debian-testing-arm64-netinst.iso 2021-03-15 04:03
Date: 2021-03-
Package: installation-reports
Boot method: network
Image version:
http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Date: 2021-03-11 ++
Machine: KVM
Processor: x86_64
Memory: 2 GB
Partitions: does not matter
Output of lspci -knn
Package: installation-reports
Severity: wishlist
-- Package-specific info:
Boot method: USB
Image version: debian-mac-10.8.0-amd64-netinst.iso
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ 2021-02-06
Date:
Machine: MacBook3,1 (Nov 2007)
Partitions:
Base System Installation Chec
Your message dated Wed, 24 Feb 2021 18:33:26 +
with message-id
and subject line Bug#980929: fixed in installation-report 2.78
has caused the Debian Bug report #980929,
regarding reportbug and installation-report
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
On 18.02.2021 18.04, Holger Wansing wrote:
> Now merged.
Thanks!
> Will upload at the weekend, I think.
A new reportbug upload will follow within 24 hours after you upload.
Nis
Hi,
Holger Wansing wrote (Sat, 6 Feb 2021 16:50:40 +0100):
> Hi,
>
> Nis Martensen wrote:
> > What do you think about including the installation-report message
> > template directly in reportbug?
> >
> > In reportbug's GTK interface, the output of bugscr
On 2/17/21 3:20 PM, Jeff Forsyth wrote:
Comments/Problems:
RPI4 with 4GiB Ram. This system is netbooted using RPI-UEFI 1.22 and
iPXE 1.2.x.
DNSMASQ send the RPI-UEFI to the RPI. The RPI-UEFI pulls the arm64
EFI/ipxe. The iPXE
shows a menu for booting into the Debian Installer. The Installe
1 - 100 of 4661 matches
Mail list logo
