Ethernet device names change Bullseye => Bookworm. How to assign unchanging name to device?

[Rick Thomas]

I've been upgrading my machines Bullseye => Bookworm recently.  In a few of 
these upgrades, the name of the ethernet device changed.  (E.g. enP2p32s15f0 => 
enP2p0s15f0)  This required changes to /etc/network/interfaces in order to 
start up the interface.

This is only a minor inconvenience (though it may require me to take a drive 
out 30 miles to the location where a few of these machines reside -- no 
problem, it's a beautiful drive!)

However, I seem to remember that once upon a time there was a way to get (I 
think it involved udev) the system to assign an arbitrary name (e.g. (enet0") 
to a given interface based on something that doesn't change when the 
firmware/driver gets upgraded. For example, the MAC address for an Ethernet 
interface would be a good basis.

The trouble is that it was a while ago and I can't remember how to do that?

Any hints will be appreciated.  Pointers to documentation on the subject would 
be especially helpful!

Thanks in advance!
Rick

Re: Installer: get rid off second checkbox “Show password in Clear”

[David Wright]

On Tue 20 Jun 2023 at 03:31:48 (+0200), Damian wrote:

> I want to suggest to change behavior of the installer in user password 
> configuration step.
> 
> In my opinion would be great to leave only one - second checkbox “Show 
> password in Clear”.
> It will be much easier to tabbing to confirmation field and cleaner without 
> redundant filed.

Why do you need to tab at all? Just press Return when you have typed
the password.

If you insist on tabbing, the checkbox adds one more tab keystroke
to cycle round the fields.

If you have an unreliable keyboard, it's much more important to
allow checking that both passwords were typed correctly than to
satisfy somebody's idea of a "cleaner" screen, whatever that means.

Cheers,
David.

Re: Strange message

[David Wright]

On Fri 16 Jun 2023 at 23:32:12 (-0400), Maureen L Thomas wrote:
> On 6/15/23 8:27 AM, ogis wrote:
> > 15.06.2023 08:09, Maureen L Thomas пишет:
> > > Failed to receive portal pid: org.freedesktop.DBus, error,
> > > NameHasNoOwner
> > 
> > Hello. Just check this:
> > 
> > https://forums.debian.net/viewtopic.php?t=150193
> > 
> I followed the instructions but they did not work.  Now what?

That depends on what you're trying to achieve, which is …?

Cheers,
David.

Re: fetchamil / procmail as non root : unable to call script

[tomas]

On Tue, Jun 20, 2023 at 07:52:24AM +0200, BASSAGET Cédric wrote:
> Hello
> I'm using fetchamil / procmail to fetch mails from an POP server and parse
> it then launch a script or system call :
> 
> 
> # cat .fetchmailrc
> set logfile fetchmail.log
> poll imaps.dom.tld proto POP3
> user "u...@dom.tld" pass "xx" preconnect "date >> ~/fetchmail.log"
> ssl
> fetchall
> keep
> no rewrite
> mda "/usr/bin/procmail ~/.procmailrc";
> 
> # cat .procmailrc
> LOGFILE=procmail.log
> VERBOSE=yes
> :0
> * ^Message-ID: \/.*
> #| /usr/bin/curl http://mail.dom.tld/script.php?messageid=$MATCH
> | echo "whoami" > test.txt
> 
> 
> This work fine when calling fetchamil as root with "fetchamil -f
> .fetchmailrc". But when calling fetchmail from a dedicated user, the
> external script in procmail is not called. It's written in the logfile that
> :
> 
> procmail: [25332] Mon Jun 19 16:20:28 2023
> procmail: Assigning "MATCH="
> procmail: Matched "<9088600d-446a-96b4-4043-29ecd0d5a...@dom.tld>"
> procmail: Match on "^Message-ID: \/.*"
> procmail: Assigning "LASTFOLDER= echo "whoami" > test.txt"
>  Subject: test
>   Folder:  echo "whoami" > test.txt
>  1824
> procmail: Executing " echo "whoami" > test.txt"
> 
> but nothung happens.

Hm. Long time I didn't play with fetchmail. One suggestion,
though: when this 'echo "whoami"...' is executed, do you
know which directory it is happening in? Try redirecting
to /tmp/test.txt or whatever, just to be sure.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[siso]

On Mon, Jun 19, 2023 at 6:30 PM Steve McIntyre  wrote:
>
> Apologies, it's just too large at this point. Adding all the firmware
> made things grow too much. We have some ideas on how to fix this, and
> I hope that the 12.1 images will work better.

Glad to hear this. Looking forward to debian-12.1.0-amd64-netinst.iso.
My stack of blank CD-Rs can serve their purpose again.

Re: ibus-wayland question

[Byung-Hee HWANG]

> Really i have so much ***WAYLAND*** ^^^

s/i have/i like/g 

Sorry for mis-typing... 

Re: Bookworm: IBus input method preferences frequently forgotten

[Christian Gelinek]

On 20/6/23 12:52, Byung-Hee HWANG (황병희) wrote:

Also i am using ibus under Debian 12. But my desktop is Gnome Wayland.

This may be not good reply, but just another opinion. Gnome is good with
ibus i think. How about using Gnome?


This would be an interesting experiment, but I'm not in a position to 
try it at the moment... Since IBus came with XFCE I believe (I certainly 
didn't install it manually), I would expect it to work without too much 
hassle I hope.


Thanks for your Time!
Christian

Re: ibus-wayland question

[Byung-Hee HWANG]

On Tue, Jun 20, 2023 at 12:07:25PM +0900, Byung-Hee HWANG (황병희) wrote:
> Hellow Debian hackers,
> 
> I'm CJK user with Debian Gnome from South Korea.
> Nowdays i am interested in Wayland and Input Method.
> 
> So i did install ibus-wayland:
> 
> 
> soyeomul@yw-1130:~$ dpkg -s ibus-wayland
> Package: ibus-wayland
> Status: install ok installed
> Priority: optional
> Section: utils
> Installed-Size: 311
> Maintainer: Debian Input Method Team 
> Architecture: amd64
> Multi-Arch: foreign
> Source: ibus
> Version: 1.5.27-5
> Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.31.8), libibus-1.0-5 (>= 1.5.1), 
> libwayland-client0 (>= 1.20.0), libxkbcommon0 (>= 0.5.0)
> Description: Intelligent Input Bus - Wayland support
>  IBus is an Intelligent Input Bus. It is a new input framework for the Linux
>  OS. It provides full featured and user friendly input method user interface.
>  It also may help developers to develop input method easily.
>  .
>  This package contains the Wayland input method support.
>  .
>  This package is only needed if you are using a Wayland compositor which
>  supports the "input-method-unstable-v1" protocol, and if you want to input
>  text via this protocol. Note that even on Wayland compositors with no support
>  of this protocol, IBus could still work using its own transport protocol and
>  APIs.
> Homepage: https://github.com/ibus/ibus
> soyeomul@yw-1130:~$ 
> 
> 
> 
> soyeomul@yw-1130:~$ env | grep SESSION
> SESSION_MANAGER=local/yw-1130:@/tmp/.ICE-unix/2064,unix/yw-1130:/tmp/.ICE-unix/2064
> GNOME_DESKTOP_SESSION_ID=this-is-deprecated
> DESKTOP_SESSION=gnome
> XDG_SESSION_DESKTOP=gnome
> XDG_SESSION_TYPE=wayland
> XDG_SESSION_CLASS=user
> GDMSESSION=gnome
> DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/3253/bus
> soyeomul@yw-1130:~$ 
> 
> 
> 
> soyeomul@yw-1130:~$ env | grep ibus
> GTK_IM_MODULE=ibus
> XMODIFIERS=@im=ibus
> QT_IM_MODULE=ibus
> soyeomul@yw-1130:~$ 
> 
> 
> 
> soyeomul@yw-1130:~$ cat /etc/environment
> GTK_IM_MODULE=ibus
> XMODIFIERS=@im=ibus
> soyeomul@yw-1130:~$ 
> 
> 
> Please please show me the example config for testing inputing with
> ibus-wayland. Yep, i am on Debian 12 (Bookworm).
> 
> Any comments welcome everytime!!!
> 
> Really i have so much ***WAYLAND*** ^^^
> 
> As you know, this input is from ibus (GNU Emacs 28.2) ;;;
> 
> 
> Sincerely, Byung-Hee (CJK user with Debian 12)

OK. This is same story. Currently i'm running ibus under Gnome Wayland.

However i did not launch /usr/libexec/ibus-wayland. Though my
XDG_SESSUIN_TYPE is "wayland":


soyeomul@yw-1130:~$ env | grep XDG_SESSION
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
XDG_SESSION_CLASS=user
soyeomul@yw-1130:~$



soyeomul@yw-1130:~$ ps -ax | grep ibus-wayland
  14200 pts/2S+ 0:00 grep ibus-wayland
soyeomul@yw-1130:~$


If so, what is this ibus-wayland for?
Already i do type as wayland without ibus-wayland.

Seriously, i'm curious about the purpose of this ibus-wayland package.


Sincerely, Byung-Hee

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[siso]

Hi,

On Mon, Jun 19, 2023 at 6:49 AM Thomas Schmitt  wrote:
>
> I have no report of persistent damage. But drives can take offense from
> overburning and then need a power cycle.

Thumbs up for cdrskin. I use it almost exclusively to burn CDs.
Definitely my first go-to.

> I rather hope for a netinst-CD ISO without firmware as companion of the
> netinst DVD ISO with firmware.
> Once there was the "businesscard CD" ISO with less than 50 MiB. Very handy
> for xorriso regression tests.

Yes, I hope so too. The 300+MB netinst CD isos of previous releases
were a joy to work with. Quick to burn. And it was easy to get to the
non-free firmware page by following the links from the netinst page.
At least for me it wasn't a problem.

siso

fetchamil / procmail as non root : unable to call script

[BASSAGET Cédric]

Hello
I'm using fetchamil / procmail to fetch mails from an POP server and parse
it then launch a script or system call :


# cat .fetchmailrc
set logfile fetchmail.log
poll imaps.dom.tld proto POP3
user "u...@dom.tld" pass "xx" preconnect "date >> ~/fetchmail.log"
ssl
fetchall
keep
no rewrite
mda "/usr/bin/procmail ~/.procmailrc";

# cat .procmailrc
LOGFILE=procmail.log
VERBOSE=yes
:0
* ^Message-ID: \/.*
#| /usr/bin/curl http://mail.dom.tld/script.php?messageid=$MATCH
| echo "whoami" > test.txt


This work fine when calling fetchamil as root with "fetchamil -f
.fetchmailrc". But when calling fetchmail from a dedicated user, the
external script in procmail is not called. It's written in the logfile that
:

procmail: [25332] Mon Jun 19 16:20:28 2023
procmail: Assigning "MATCH="
procmail: Matched "<9088600d-446a-96b4-4043-29ecd0d5a...@dom.tld>"
procmail: Match on "^Message-ID: \/.*"
procmail: Assigning "LASTFOLDER= echo "whoami" > test.txt"
 Subject: test
  Folder:  echo "whoami" > test.txt
 1824
procmail: Executing " echo "whoami" > test.txt"

but nothung happens.
Am I missing something ?
Regards
Cédric

Re: VirtualBox key is store in deprecated legacy keyring

[DdB]

Am 20.06.2023 um 04:58 schrieb Rick Thomas:
> PS: As an aside,  it appears that the VirtualBox developers at Oracle waited 
> until Bookworm was officially released before they started working on getting 
> a bookworm version of their software, so I'm still using the Bullseye version 
> -- which seems to work fine.  Presumably, fixing this problem would be one of 
> the things they might want to do before releasing a new version...  (One can 
> hope, anyway...)  Would it be worth filing a bug-report to Oracle?  If so, 
> does anyone know how to do that?

I used to use their forum first in order to get confirmation for the bug
existing, before actually filing a bug on their public bugtracker
https://www.virtualbox.org/wiki/Bugtracker

Re: package managers problem

[Anders Andersson]

On Tue, Jun 20, 2023 at 5:38 AM gene heskett  wrote:
>
> On 6/19/23 22:41, pa...@quillandmouse.com wrote:
> > On Tue, 20 Jun 2023 03:58:18 +0200
> > Anders Andersson  wrote:
> >
> > [snip]
> >
> >> I've been watching this thread from afar for a while and it still
> >> puzzles me why people keep bringing up wayland. I've been running
> >> wayland for years, and synaptic works with no issues as far as I can
> >> tell. Is this just FUD from a user that never tried it or is something
> >> broken on that user's system?
> >>
> >
> > A couple of years ago, I switched to Wayland temporarily and was unable
> > to run Synaptic (with an error message). The phenomenon is real. I
> > don't know how you manage it. But I don't recall anyone on this thread
> > besides you claiming it could be done.
> >
> > Paul
> >
> I'm with you Paul, if Anders know how to do it, please PUBLISH the how.
> For a while on bullseye, a "sudo -E synaptic" worked, then even that
> died mid-bullseye, somebody plugged a perceived hole and didn't bother
> to mention it to the many thousands of users.

There's really nothing to publish. I started synaptic from my desktop
environment using the default icon installed by the debian package. No
weird "sudo" incantations. It asks my password and then starts up.

Since I normally don't use Synaptic and have not started it in years
as far as I can remember, I have not configured it to do anything
special. As demonstrated by Didier Gaumet in this thread it works by
default on a fresh install of debian stable.

All the bugs I find online are from the time before bullseye.

Re: package managers problem

[Felix Miata]

gene heskett composed on 2023-06-19 23:37 (UTC-0400):

> paulf@q... wrote

>> On Tue, 20 Jun 2023 03:58:18 +0200 Anders Andersson wrote:

>>> I've been watching this thread from afar for a while and it still
>>> puzzles me why people keep bringing up wayland. I've been running
>>> wayland for years, and synaptic works with no issues as far as I can
>>> tell. Is this just FUD from a user that never tried it or is something
>>> broken on that user's system?

>> A couple of years ago, I switched to Wayland temporarily and was unable
>> to run Synaptic (with an error message). The phenomenon is real. I
>> don't know how you manage it. But I don't recall anyone on this thread
>> besides you claiming it could be done.

> I'm with you Paul, if Anders know how to do it, please PUBLISH the how. 
> For a while on bullseye, a "sudo -E synaptic" worked, then even that 
> died mid-bullseye, somebody plugged a perceived hole and didn't bother 
> to mention it to the many thousands of users.

Why is it Gene thinks any trouble he has has anything to do with Wayland? XFCE
doesn't run in Wayland. The only Wayland XFCE users must have is the foundation
Wayland requires from Xorg, which no one can be rid of (nor need to), except by
running an ancient distro from before Wayland support was stuffed into Xorg, or 
by
running MacOS, BSD, OS/2, Unix or Windows.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: package managers problem

[gene heskett]

On 6/19/23 22:41, pa...@quillandmouse.com wrote:

On Tue, 20 Jun 2023 03:58:18 +0200
Anders Andersson  wrote:

[snip]


I've been watching this thread from afar for a while and it still
puzzles me why people keep bringing up wayland. I've been running
wayland for years, and synaptic works with no issues as far as I can
tell. Is this just FUD from a user that never tried it or is something
broken on that user's system?



A couple of years ago, I switched to Wayland temporarily and was unable
to run Synaptic (with an error message). The phenomenon is real. I
don't know how you manage it. But I don't recall anyone on this thread
besides you claiming it could be done.

Paul

I'm with you Paul, if Anders know how to do it, please PUBLISH the how. 
For a while on bullseye, a "sudo -E synaptic" worked, then even that 
died mid-bullseye, somebody plugged a perceived hole and didn't bother 
to mention it to the many thousands of users.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: VirtualBox key is store in deprecated legacy keyring

[Jeffrey Walton]

On Mon, Jun 19, 2023 at 11:15 PM Rick Thomas  wrote:
>
> I recently upgraded one of my Debian Bullseye machines to Bookworm.  The 
> machine's main purpose is to run Virtualbox to allow me to experiment on 
> disposable VMs rather than real hardware.
>
> Now when I do "apt update" I get this message:
> .W: 
> https://download.virtualbox.org/virtualbox/debian/dists/bullseye/InRelease: 
> Key is stored in legacy trusted.gpg
>keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
> apt-key(8) for details.
>
> I've thoroughly RTFM in search of a clue as to how to fix this, but I can't 
> figure out what I'm supposed to do.
>
> Has anybody else seen this?  If so, what did you do?  And did it help?

I _think_ the key should be stored in its own file under
/etc/apt/trusted.gpg.d. Maybe something like
/etc/apt/trusted.gpg.d/virtual-box.gpg.

Also see https://wiki.debian.org/SecureApt and the part:

apt-key is a program that is used to manage a keyring of OpenPGP keys
for secure apt. The keyring is kept in the file /etc/apt/trusted.gpg
(not to be confused with the related but not very interesting
/etc/apt/trustdb.gpg). apt-key can be used to show the keys in the
keyring, and to add or remove a key. In more recent Debian GNU/Linux
versions (Wheezy, for example), the keyrings are stored in specific
files all located in the /etc/apt/trusted.gpg.d directory. For example,
that directory could contain the following files:
debian-archive-squeeze-automatic.gpg or
debian-archive-wheezy-automatic.gpg. Incidentally, both files are
provided by the debian-archive-keyring package.

Jeff

Re: Bookworm: IBus input method preferences frequently forgotten

[황병희]

Christian Gelinek  writes:

> Hi all,
>
> I'm running the XFCE desktop on Bookworm.
>
> Via the IBus Preferences ("ibus panel" under Status Tray Items) dialog under
> Input Method, I like to add the "English (intl., with AltGr dead keys)" input
> method as a default to use across the whole system. Also, to prevent
> accidental switching, I remove the default "English (US)" input method and on
> the General tab, I delete the "space" keyboard shortcut to switch input
> methods.
>
> I have done this a number of times already but often after re-booting my
> system, the old settings are back, including the "English (US)" input method
> and the "space" keyboard shortcut.
>
> How can I find out what the problem is and make my preferences "stick"?
>
> Thanks for your time!

Hellow Christian!

Also i am using ibus under Debian 12. But my desktop is Gnome Wayland.

This may be not good reply, but just another opinion. Gnome is good with
ibus i think. How about using Gnome?


Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

VirtualBox key is store in deprecated legacy keyring

[Rick Thomas]

I recently upgraded one of my Debian Bullseye machines to Bookworm.  The 
machine's main purpose is to run Virtualbox to allow me to experiment on 
disposable VMs rather than real hardware.

Now when I do "apt update" I get this message:
.W: 
https://download.virtualbox.org/virtualbox/debian/dists/bullseye/InRelease: Key 
is stored in legacy trusted.gpg
   keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.

I've thoroughly RTFM in search of a clue as to how to fix this, but I can't 
figure out what I'm supposed to do.

Has anybody else seen this?  If so, what did you do?  And did it help?

Thanks in advance!
Rick

PS: As an aside,  it appears that the VirtualBox developers at Oracle waited 
until Bookworm was officially released before they started working on getting a 
bookworm version of their software, so I'm still using the Bullseye version -- 
which seems to work fine.  Presumably, fixing this problem would be one of the 
things they might want to do before releasing a new version...  (One can hope, 
anyway...)  Would it be worth filing a bug-report to Oracle?  If so, does 
anyone know how to do that?

ibus-wayland question

[황병희]

Hellow Debian hackers,

I'm CJK user with Debian Gnome from South Korea.
Nowdays i am interested in Wayland and Input Method.

So i did install ibus-wayland:


soyeomul@yw-1130:~$ dpkg -s ibus-wayland
Package: ibus-wayland
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 311
Maintainer: Debian Input Method Team 
Architecture: amd64
Multi-Arch: foreign
Source: ibus
Version: 1.5.27-5
Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.31.8), libibus-1.0-5 (>= 1.5.1), 
libwayland-client0 (>= 1.20.0), libxkbcommon0 (>= 0.5.0)
Description: Intelligent Input Bus - Wayland support
 IBus is an Intelligent Input Bus. It is a new input framework for the Linux
 OS. It provides full featured and user friendly input method user interface.
 It also may help developers to develop input method easily.
 .
 This package contains the Wayland input method support.
 .
 This package is only needed if you are using a Wayland compositor which
 supports the "input-method-unstable-v1" protocol, and if you want to input
 text via this protocol. Note that even on Wayland compositors with no support
 of this protocol, IBus could still work using its own transport protocol and
 APIs.
Homepage: https://github.com/ibus/ibus
soyeomul@yw-1130:~$ 



soyeomul@yw-1130:~$ env | grep SESSION
SESSION_MANAGER=local/yw-1130:@/tmp/.ICE-unix/2064,unix/yw-1130:/tmp/.ICE-unix/2064
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
DESKTOP_SESSION=gnome
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
XDG_SESSION_CLASS=user
GDMSESSION=gnome
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/3253/bus
soyeomul@yw-1130:~$ 



soyeomul@yw-1130:~$ env | grep ibus
GTK_IM_MODULE=ibus
XMODIFIERS=@im=ibus
QT_IM_MODULE=ibus
soyeomul@yw-1130:~$ 



soyeomul@yw-1130:~$ cat /etc/environment
GTK_IM_MODULE=ibus
XMODIFIERS=@im=ibus
soyeomul@yw-1130:~$ 


Please please show me the example config for testing inputing with
ibus-wayland. Yep, i am on Debian 12 (Bookworm).

Any comments welcome everytime!!!

Really i have so much ***WAYLAND*** ^^^

As you know, this input is from ibus (GNU Emacs 28.2) ;;;


Sincerely, Byung-Hee (CJK user with Debian 12)

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: package managers problem

[paulf]

On Tue, 20 Jun 2023 03:58:18 +0200
Anders Andersson  wrote:

[snip]

> I've been watching this thread from afar for a while and it still
> puzzles me why people keep bringing up wayland. I've been running
> wayland for years, and synaptic works with no issues as far as I can
> tell. Is this just FUD from a user that never tried it or is something
> broken on that user's system?
> 

A couple of years ago, I switched to Wayland temporarily and was unable
to run Synaptic (with an error message). The phenomenon is real. I
don't know how you manage it. But I don't recall anyone on this thread
besides you claiming it could be done.

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: package managers problem

[Anders Andersson]

On Sun, Jun 18, 2023 at 10:34 AM DdB
 wrote:
>
> Am 17.06.2023 um 14:38 schrieb Greg Wooledge:
> > On Fri, Jun 16, 2023 at 11:03:59PM -0400, pa...@quillandmouse.com wrote:
> >> Why isn't there a ONE WAY for packages to be managed?
> >
> > Because each user has a different preference.  Just read this thread
> > for example, and see all the differing opinions about how we like
> > our packages to be managed.
> >
> >
> Back in the days, i have been using synaptic myself. And after reading
> this thread, i was curious about its appearance today. Thus, in my
> virtualised buster install, i did log out of wayland and logged in as
> "system X11 default" (under the wheel on login screen). Then, i was able
> to install synaptic and use it, although the gnome-software mentionned
> its source being debian-old-oldstable-main.
>
> I seem to have left it behind since stretch, when i moved to commandline
> tools instead. When things got really hairy, i recall having used
> aptitude on few occasions, but only after thorough experimentation in
> virtualized world, before applying the steps on bare metal.
>
> But since most of you are on bullseye, with a huge crowd even already
> landing in bookworm, this report from an outdated software will most
> certainly be neglected. FWIW, i chose to let you know anyway.

I've been watching this thread from afar for a while and it still
puzzles me why people keep bringing up wayland. I've been running
wayland for years, and synaptic works with no issues as far as I can
tell. Is this just FUD from a user that never tried it or is something
broken on that user's system?

Installer: get rid off second checkbox “Show password in Clear”

[Damian]

Hi guys,

I want to suggest to change behavior of the installer in user password 
configuration step.

In my opinion would be great to leave only one - second checkbox “Show password 
in Clear”.
It will be much easier to tabbing to confirmation field and cleaner without 
redundant filed.

BR
Damian

Installer change suggestion

[Damian]

Hi guys,

I want to suggest to change behavior of the installer in user password 
configuration step.

In my opinion would be great to leave only one - second checkbox “Show password 
in Clear”.
It will be much easier to tabbing to confirmation field and cleaner without 
redundant filed

BR
Damian

Re: How to stop systemd or whatever does,to always tries to check and fix disk errors

[Jeffrey Walton]

On Mon, Jun 19, 2023 at 8:48 PM Stefan Monnier  wrote:
>
> [...]
> > of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to boot. I
> > don't understand where the error is. When I insert the sd card into the
> > slot it beeps and it prepares itself to boot chrome OS from the internal
> > memory,not Linux from the sd card.
> >
> > The problem could be systemd or whatever does that,to check and fix disk
>
> What makes you think so?  The description of the error you give about
> gives me the impression the Chromebook doesn't even begin to boot the
> GNU/Linux distribution on your SD card, in which case systemd can't be
> the culprit.

Yeah, I had a lot of problems with a Chromebook several years ago. I
think I could get it into Developer Mode, but I could not get it to
boot to USB. I spent days trying to get it to work. It was a Toshiba
CB35, if I recall correctly.

I find it best to donate old Chromebooks to a church or other
non-profit. They are low-end, and they are not worth spending too much
time on.

Jeff

Re: How to stop systemd or whatever does,to always tries to check and fix disk errors

[Stefan Monnier]

[...]
> of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to boot. I
> don't understand where the error is. When I insert the sd card into the
> slot it beeps and it prepares itself to boot chrome OS from the internal
> memory,not Linux from the sd card.
>
> The problem could be systemd or whatever does that,to check and fix disk

What makes you think so?  The description of the error you give about
gives me the impression the Chromebook doesn't even begin to boot the
GNU/Linux distribution on your SD card, in which case systemd can't be
the culprit.


Stefan

Re: W: Possible missing firmware /lib/firmware/brand/yada*

[bw]

in-reply-to=<11580298-c877-35c1-cf54-99e56af75...@earthlink.net>

>> Is there something that can be done to avoid this screen and log
>> litter?

It's your machine, you could hack it out?  possibly just #comment out and put a 
/bin/true under it?  Don't blame me if it all goes wrong.

/usr/share/initramfs-tools/hook-functions 
4322/23580  18%
 if grep -q "^$kmod_modname\\>" /proc/modules 
"${CONFDIR}/modules"; then
 echo "W: Possible missing firmware 
/lib/firmware/${firmware} for module
 fi

Bug Report Question

[Christopher Quinn]

Hello Debian Team,

I have a bug to report and have not done that before, thus, I need some 
assistance. My bug isn't with a specific package. If so, I am not sure 
which one. Below I will describe the issue.



I use a Lenovo T560 with a Lenovo dock. It is the one that Lenovo made 
for this specific laptop. If I have it off of the dock and am using it, 
there is not an issue. However, if I have it locked or in hibernation 
mode, and place it on the dock while it is in one of those states, the 
computer locks up and I have to do a manual restart using the power 
button. The first time I thought it might have just been a fluke but it 
has happened every time. I have ran Debian 10 and Debian 11 on this 
laptop and it did not do that. That is why I think it might be a bug.



Thank you,

Chris

Bookworm: IBus input method preferences frequently forgotten

[Christian Gelinek]

Hi all,

I'm running the XFCE desktop on Bookworm.

Via the IBus Preferences ("ibus panel" under Status Tray Items) dialog 
under Input Method, I like to add the "English (intl., with AltGr dead 
keys)" input method as a default to use across the whole system. Also, 
to prevent accidental switching, I remove the default "English (US)" 
input method and on the General tab, I delete the "space" 
keyboard shortcut to switch input methods.


I have done this a number of times already but often after re-booting my 
system, the old settings are back, including the "English (US)" input 
method and the "space" keyboard shortcut.


How can I find out what the problem is and make my preferences "stick"?

Thanks for your time!

Christian

Compiling Virtualbox on "bookworm" [plain text email]

[Ian Tan]

Hello,

Apologies for sending "rich text" of the same email previously. That
was an accident.
Here should be the plain text now.

Due to upstream issues, Virtualbox is not available on bookworm.
I have an urgent business use case, that required virtualbox to be installed
on Debian 12 bookworm, as soon as possible.

However, I am not able to compile virtual box on Debian 12 that easily,
due to the error:

"/usr/share/kBuild/footer-inherit-uses-tools.kmk:1012: *** kBuild:
Cannot find include file for the SDK 'LIBSDL2'!"

I have shown the details below. Any advice would be appreciated, thank you.

Regards.
Ian


1) Show lsb_release

$ lsb_release -d
No LSB modules are available.
Description: Debian GNU/Linux 12 (bookworm)


2) Edit sources.list so that it points to sid

deb-src http://deb.debian.org/debian sid ... ... ...


3) When I do apt-get source virtualbox, I get the source in sid

$ apt source virtualbox
Reading package lists... Done
NOTICE: 'virtualbox' packaging is maintained in the 'Git' version
control system at:
https://salsa.debian.org/pkg-virtualbox-team/virtualbox.git
Please use:
git clone https://salsa.debian.org/pkg-virtualbox-team/virtualbox.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 78.7 MB of source archives.
Get:1 http://deb.debian.org/debian sid/contrib virtualbox 7.0.8-dfsg-2
(dsc) [3,537 B]
Get:2 http://deb.debian.org/debian sid/contrib virtualbox 7.0.8-dfsg-2
(tar) [78.6 MB]
Get:3 http://deb.debian.org/debian sid/contrib virtualbox 7.0.8-dfsg-2
(diff) [78.9 kB]
Fetched 78.7 MB in 13s (5,927 kB/s)
dpkg-source: info: extracting virtualbox in virtualbox-7.0.8-dfsg
dpkg-source: info: unpacking virtualbox_7.0.8-dfsg.orig.tar.xz
dpkg-source: info: unpacking virtualbox_7.0.8-dfsg-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 01-build-arch.patch
dpkg-source: info: applying 02-gsoap-build-fix.patch
dpkg-source: info: applying 04-vboxdrv-references.patch
dpkg-source: info: applying 06-xsession.patch
dpkg-source: info: applying 07-vboxnetflt-reference.patch
dpkg-source: info: applying 12-make-module.patch
dpkg-source: info: applying 13-module-mismatch.patch
dpkg-source: info: applying 16-no-update.patch
dpkg-source: info: applying 23-remove-invalid-chars-check.patch
dpkg-source: info: applying 27-hide-host-cache-warning.patch
dpkg-source: info: applying 28-no-selinux-fedora.patch
dpkg-source: info: applying 32-disable-guest-version-check.patch
dpkg-source: info: applying 35-libvdeplug-soname.patch
dpkg-source: info: applying 36-fix-vnc-version-string.patch
dpkg-source: info: applying 37-do-not-run-if-not-in-vm.patch
dpkg-source: info: applying python3.11.patch
dpkg-source: info: applying add-lzma.patch

I assume that the patches should be fine for Debian 12.


4) I checked whether I have installed all the dependencies for build,
I seem to be ok.

$ sudo apt-get build-dep virtualbox
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


5) Begin the build process ...

$ dpkg-buildpackage --check-builddeps --build=binary --no-sign
dpkg-buildpackage: info: source package virtualbox
dpkg-buildpackage: info: source version 7.0.8-dfsg-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Gianfranco Costamagna

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean --with python3
dh: warning: The target override_dh_systemd_enable references a now
obsolete command and will not be run! (Marked by debhelper, will be an
error in compat 13)
   debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/vbox/virtualbox-7.0.8-dfsg-2/virtualbox-7.0.8-dfsg'
dh_auto_clean
# Cleaning package
rm -rf out
rm -f build-stamp
rm -f debian/virtualbox.README.Debian debian/README.Debian.html
rm -f debian/virtualbox-dkms.install
r

How to stop systemd or whatever does,to always tries to check and fix disk errors

[Mario Marietto]

Hello.

I would like to upgrade the kernel and I want to enable KVM on my old but
still functional "Samsung Chromebook ARM model XE303C12 SNOW" because later
I want to virtualize FreeBSD with qemu and kvm. I've started following this
tutorial :


*http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/*



As you can see,they used Ubuntu 13.04 as userland. No,I don't want to run
such an old ubuntu version ! Actually my problem is that only 2 times over
10 tries my chromebook is able to boot correctly with the same setup. I've
also completely erased the sd card with sudo dd if=/dev/zero
of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to boot. I
don't understand where the error is. When I insert the sd card into the
slot it beeps and it prepares itself to boot chrome OS from the internal
memory,not Linux from the sd card.

The problem could be systemd or whatever does that,to check and fix disk
errors because it does not support natively chrome os disk partitions
flags. So it may break those flags after the first boot. So,I want to ask
if there is a method that stops systemd or whatever to check and fix disk
errors. Thanks.

-- 
Mario.

Re: W: Possible missing firmware /lib/firmware/brand/yada*

[Felix Miata]

Sven Joachim composed on 2023-04-29 09:02 (UTC+0200):

> On 2023-04-28 21:30 -0400, Felix Miata wrote:
 
>> # inxi -Gxx
>> Graphics:
>>   Device-1: Intel 82Q963/Q965 Integrated Graphics vendor: Dell driver: i915
>> v: kernel arch: Gen-4 ports: active: DVI-D-1 empty: VGA-1 bus-ID: 00:02.0
>> chip-ID: 8086:2992   # aka ancient
>> # grep MODULES /etc/initramfs-tools/initramfs.conf
>> # MODULES: [ most | netboot | dep | list ]
>> MODULES=dep
>> #

>> These many per transaction $SUBJECT initrd construction messages have been 
>> routine
>> for a long time in Bullseye and Bookworm regardless of active GPU installed, 
>> and
>> whether or not a firmware-brand-graphics .deb exists and is installed
>> for it.
 
> It would be useful to give an example of these messages, as well as a
> list of firmware packages you have installed.
 
>> Is there something that can be done to avoid this screen and log
>> litter?
 
> Install the package that contains the firmware files.  For Intel and
> NVidia graphics that is firmware-misc-nonfree, for AMD it is
> firmware-amd-graphics.
 
>> Can anyone
>> point to an existing meta-bug report on the subject of stopping the litter?
>> Searching seems to find only reports pointing to particular GPUs, e.g.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016286
 
# inxi -CGS
System:
  Host: fi965 Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Console: pty pts/0
Distro: Debian GNU/Linux 12 (bookworm)
CPU:
  Info: dual core model: Intel Core2 6700 bits: 64 type: MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1596 min/max: 1596/2660 cores: 1: 1596 2: 1596
Graphics:
  Device-1: AMD Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM]
driver: amdgpu v: kernel chip-ID: 1002:6611
  Display: server: X.org v: 1.21.1.7 driver: X: loaded: modesetting
dri: radeonsi gpu: amdgpu resolution: 1: 2560x1440 2: 1680x1050
# dpkg-query -W | grep firmware
firmware-amd-graphics   20230210-5
firmware-linux-free 20200122-1
firmware-misc-nonfree   20230210-5
firmware-sof-signed 2.2.4-1
# update-initramfs -u -k 6.1.0-9-amd64
update-initramfs: Generating /boot/initrd.img-6.1.0-9-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=57a644a9-4f6a-41ea-b24a-8983806a)
I: Set the RESUME variable to override this.
#
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Steve McIntyre]

j...@jretrading.com wrote:
>On Mon, 19 Jun 2023 11:30:04 +0100
>Steve McIntyre  wrote:
>
>> ssmcmlxx+debianu...@gmail.com wrote:
>> >I tried to write the debian-12.0.0-amd64-netinst.iso to cd using
>> >cdrskin and xorriso but they both refused my command.  
>> 
>> Apologies, it's just too large at this point. Adding all the firmware
>> made things grow too much. We have some ideas on how to fix this, and
>> I hope that the 12.1 images will work better.
>> 
>
>Is compression practical in this case? Tom used to get 1.7MB on a 1.44MB
>floppy, and Knoppix claims to put 2GB on a live CD.

Just about everything on the media is already heavily compressed,
e.g. xz for data inside the .deb packages.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
  note stuck to the mini-bar saying "Paul: This fridge and
  fittings are the correct way around and do not need altering"

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Charles Curley]

On Mon, 19 Jun 2023 14:10:48 +0100
Joe  wrote:

> Tom used to get 1.7MB on a 1.44MB
> floppy,

If you mean Tom's rootboot, tomsrtbt: he got some of that "compression"
by adding extra tracks beyond the 1.44MB. It is also possible to add an
extra sector per track. (But not all floppy drives supported those extra
tracks and sectors gracefully or at all.) That got 1.7 MB out of a
1.44MB diskette. I don't know if he did compression on top of that.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Sound volume doesn't stick between reboots

[Andreas Rönnquist]

Hi!

I have a problem where sound volume doesn't stick between reboots - I
have an external USB sound "card", a Behringer UMC204HD, which is
detected just fine by the alsa tools and everything, but, as said, it
doesn't get volume stuck between reboots.

I need to go into alsamixer in the terminal and select the Behringer
and increase the volume there every time.

I have done alsactl store, as mentioned on 
https://wiki.debian.org/SoundConfiguration

(which as mentioned should be done automatically on every shutdown, but
which it seems not to be done as I have described).

In the mixer of Xfce's puvlseaudio plugin all volumes are properly set,
and nothing needs to be done there.

This is on a Bookworm system, just upgraded from Bullseye (where all
this wasn't necessary), running Xfce.

Does anyone have any clue to a fix?

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

[Please don't CC me, if I mail to a mailinglist, I am subscribed to it.]

Re: Why wouldn't "stringing" of an input parameter using an array work? ...

[Greg Wooledge]

On Sun, Jun 18, 2023 at 11:41:12PM -0500, Albretch Mueller wrote:
> time ( find "${_DIR_BRNX}" -path "${_X_SUB_DIRS_AR[@]}" -prune -type f
> -printf '%s|%d|%P|' -exec file --brief {} \; 1> "${_TMPFL}" 2>
> "${_ERR_LOG}" ) > "${_TM_LOG}" 2>&1

I believe I've said this before, but it DEMANDS repeating: STOP using
these variable names!!

A shell variable that is not being exported through the environment for
another program to use should contain at least one lower-case letter.
It should also not begin with an underscore unless you have a REALLY
GOOD REASON to start it with an underscore.

There are REASONS for these conventions.

The capital letter thing: variables that contain only capital letters,
underscores and digits are part of a namespace that's reserved for
environment variables, and special shell variables.  Examples are
HOME, PATH, RANDOM, BASH_VERSION.

The underscore thing: using a leading underscore is reserved for special
needs.  It's sort of like creating your own semi-private namespace,
except that you're only relying on a gentlemen's agreement to enforce
it.  The one place where I would use such a variable is in a function
that's using a bash "name reference" (declare -n).  In such a function,
there is an absolute need to ensure that your local variables do not
ever share the name of the output variable, or "pass by reference"
variable, that the caller is supplying.

Thus, in a function "foobar" I would use a local variable like _foobar_i
to *try* to avoid a variable name collision.

Once again, this ONLY applies to functions that are receiving a variable
name passed by a caller and then stored in a local nameref variable.

Now, with that out of the way, and with the almost certain knowledge
that you are going to CONTINUE to ignore me, and CONTINUE to post this
eyeball-searing code

You tried to do this:   -path "${array[@]}"

This makes no sense.  -path takes ONE argument.  You're passing many.

You need to decide what your find command is supposed to do.  Do you
want it to require a match against ALL of the array elements?  Or only
against ONE of the array elements?  In other words, do you want your
multiple -path filters to be joined with AND or with OR?

If you want an AND join, then build up an argument array like this:

args=( "$dir_brnx" \( )
for p in "${paths[@]}"; do
args+=( -path "$p" )
done
args+=( \) -prune -type f -printf ... )
find "${args[@]}"

If you want an OR join, it's a tiny bit trickier:

args=( "$dir_brnx" \( )
first=1
for p in "${paths[@]}"; do
if (( ! first )); then args+=( -o ); fi
args+=( -path "$p" )
first=0
done
args+=( \) -prune -type f -printf ... )
find "${args[@]}"

In the first case, you will end up with a find command like this:

find /dir/brnx \( -path p1 -path p2 \) -prune ...

In the second case:

find /dir/brnx \( -path p1 -o -path p2 \) -prune ...

I strongly suspect you want the second case, but it's not clear from
my skimming of your code, so I gave both examples.

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Steve McIntyre]

ssmcmlxx+debianu...@gmail.com wrote:
>I tried to write the debian-12.0.0-amd64-netinst.iso to cd using
>cdrskin and xorriso but they both refused my command.

Apologies, it's just too large at this point. Adding all the firmware
made things grow too much. We have some ideas on how to fix this, and
I hope that the 12.1 images will work better.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
  note stuck to the mini-bar saying "Paul: This fridge and
  fittings are the correct way around and do not need altering"

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Pierre Tomon]

The mini.iso image is 62M:
https://www.debian.org/distrib/netinst#verysmall

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[mick.crane]

On 2023-06-18 23:48, Thomas Schmitt wrote:

Once there was the "businesscard CD" ISO with less than 50 MiB. Very 
handy

for xorriso regression tests.


30 something Mb, Slitaz would fit on them.
mick

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Thomas Schmitt]

Hi,

Joe wrote:
> Just a thought: Knoppix has never considered 700MB much of a limit.
> "Because of its transparent decompression, up to 2 gigabyes of
> executable software can be present on a CD, and up to 10GB on a
> single-layered DVD."

Debian ISOs have all their big data files compressed: kernels, initrds,
packages.

There's not much potential for compression gains:

  $ cat 

Re: How does the bookworm amd64 netinst 738MB iso fit into a 700MB cd-r?

[Joe]

On Mon, 19 Jun 2023 05:51:09 +0800
siso  wrote:

> Hi,
> 
> On Mon, Jun 19, 2023 at 3:32 AM Thomas Schmitt 
> wrote:
> >
> > You ran into a known bug of cdrskin which will be fixed by version
> > 1.5.6. It did not even try to burn more than the official number of
> > blocks.
> >
> > Nevertheless it most probably would not have worked, because 36 MiB
> > of overburning is just too much for a "700 MB" CD.  
> 
> The bug saved my drive fortunately. Yay for that.
> 
> > > And there it went, one good cd. FATAL indeed.  
> >
> > Sorry for that.  
> 
> Don't worry about it. It was my poor attempt at tongue-in-cheek humour
> :). Just lost one CD-R. The drive is still working fine, i think.
> 
> > After fixing option -force i added quite some warning to the man
> > page of cdrskin:
> >
> >   -force
> >   Assume that the user knows better in situations when cdrskin
> > or libburn  are  refusing  because of concerns about drive or media
> >   state.
> >   Caution: Use option -force only when in urgent need.
> > ...
> >   First consider to use a medium with more  capacity  rather
> > than trying to overburn a CD.
> >
> > There are "800 MB"/"90 minutes" CD-R which could take the ISO.
> >
> > One reason for being able to overburn at all are "900 MB"/"100
> > minutes" CD-R media. They cannot announce their full capacity to
> > the drive, because together with the wasteful lead-in and lead-out
> > areas they exceed the addressing limit of 100 minutes.  
> 
> I see what i missed. I had no idea that 800MB or even 900MB CD-R
> existed. Have only seen 700MB CD-R. Which explains my disbelief that
> Debian would make a cd iso that couldn't fit into a standard cd. My
> bad. But still it is a surprise to me that nobody thought this
> deserved a mention in the release notes. I wonder if we are seeing the
> last of CD-R as a Debian install medium. Wait, there is still the mini
> iso. Ha, CD-R will live on. :)
> 
> > Have a nice day :)  
> 
> I appreciate the detailed reply very much. Thank you for taking the
> time. You have a nice day too.
> 

Just a thought: Knoppix has never considered 700MB much of a limit.

"Because of its transparent decompression, up to 2 gigabyes of
executable software can be present on a CD, and up to 10GB on a
single-layered DVD."
https://www.knopper.net/knoppix-info/index-en.html

-- 
Joe