Hi Ismail,
Ismail Arif (2023-05-19):
> Boot the installer in EFI on virtualbox 7.0.x, select every install
> options and all results in a grey screen if in text mode and an error
> can't open display:0 on graphical gtk mode. In BIOS mode, everything
> works fine
Nice! Could you please test an im
Hello Cyril,
On 19/05/2023 00:59, Cyril Brulebois wrote:
Speaking as someone who happen{ed,s} to come across live-build things for
unrelated reasons:
Roland Clobus (2023-05-18):
I've implemented a workaround for the live images at [1].
As a result, the xfwm4 desktop manager is now the only de
Ismail Arif (2023-05-19):
> Thanks for the response, I've downloaded and tried to run the installer by
> using the iso provided, however the issue still persists, I have a
> screenshot of the error that i believe is still the same error that I
> received before.
So I'm seeing different errors on
Here's the screenshot for both the graphical and text modes,
First file should be the graphical mode, and the second is the grey screen
in text mode
The grey screen is kind of like a background for a shell, but typing and
entering any words or commands of any kind seems to be useless (no command
Cyril Brulebois (2023-05-19):
> I'll try and provide you with a full netinst image, so that you have
> both Graphical Install and (text…) Install options. My patch should fix
> graphics-related issues, in both text and graphical modes. At first
> glance it looks like your X might have another issu
Seems the problem still persists on both modes, so it might be something
else.
In bullseye there's no such issues
Trying to run the vm in windows too seems to output the same issue.
Either it's a virtualbox issue or a bookworm issue is yet to be identified,
as booting the image on my baremetal e
Ismail Arif (2023-05-19):
> Seems the problem still persists on both modes, so it might be something
> else.
>
> In bullseye there's no such issues
>
> Trying to run the vm in windows too seems to output the same issue.
>
> Either it's a virtualbox issue or a bookworm issue is yet to be identif
I've downloaded and tested the images. and it seems the issue has been
present since alpha 1
On Fri, May 19, 2023 at 4:11 PM Cyril Brulebois wrote:
> Ismail Arif (2023-05-19):
> > Seems the problem still persists on both modes, so it might be something
> > else.
> >
> > In bullseye there's no
Hi,
Roland Clobus (2023-05-19):
> I consider it a workaround, because the netinst D-I is still affected.
> If the LXQt desktop is selected in the installer, the Wayland desktop
> manager is used instead of xfwm4.
> The MR for a proposed fix (in tasksel) is at [1].
OK, I'll leave that one to peop
Package: rootskel-gtk
Version: 12.0.1
Severity: normal
Hi,
When building the package on bullseye, I'm getting transparency on both
left and right borders. When building it on sid, I'm get that at the
bottom. It would be great if we had some better or at least reproducible
export.
Since this was
Package: rootskel-gtk
Version: 12.0.1
Severity: normal
Hi,
Spotted while toying with the idea of having some code to expand the
banner automatically on the left and/or on the right, and finding the
cdebconf-gtk code handling the “dark” banner. Trying theme=dark, I'm
getting the same banner, and t
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
Package: rootskel-gtk
Version: 12.0.1
Severity: normal
Hi,
Until now, we've always been favoring one side of the banner, and that's
been encoded in cdebconf-gtk: starting the installer in “Rescue” will
result in a (translated) label being printed on top of the banner,
either on the left or on the
Package: partman-auto-raid
Severity: important
Tags: patch
Hi,
I'm not a preseed expert but it seems to me we're currently lacking
support for one rather common layout that's achievable via the
interactive installer, which is RAID+LUKS+LVM.
As far as I understand we support a few methods, but on
Control: tag -1 patch pending
Hi,
Cyril Brulebois (2023-05-19):
> Maybe something like logo_debian.properties (or whatever name) with:
>
> labelPosition=right
> bannerExpands=right
I settled for a logo_installer.ini (logo_debian.ini for us, plus a
symlink via the Makefile, as it is don
Processing control commands:
> tag -1 patch pending
Bug #1036321 [rootskel-gtk] rootskel-gtk: Include metadata about the banner
Added tag(s) patch and pending.
--
1036321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Hi,
Andrew M.A. Cater (2023-05-19):
> I'd honestly suggest *just* publishing DVD1 for i386.
>
> Netinst requires internet access: DVD1 can be used to install a basic
> system without this. Scrap *everything else* for i386 installation media.
I'm not sure how dropping one netinst ISO is going to
Hi kibi,
Cyril Brulebois wrote (Fri, 19 May 2023 10:50:57 +0200):
> Hi,
>
> Roland Clobus (2023-05-19):
> > I consider it a workaround, because the netinst D-I is still affected.
> > If the LXQt desktop is selected in the installer, the Wayland desktop
> > manager is used instead of xfwm4.
> >
Package: debian-installer
Version: 20210731+deb11u8
Severity: important
Tags: d-i
X-Debbugs-Cc: budheal...@gmail.com
Dear Maintainer,
* What led up to the situation?
Since the DLBD .iso install neither sets up sources.list with a mirror to
download from nor requests more disks to complete the
19 matches
Mail list logo
