On Thu, 31 Aug 2023 23:59:11 +0200
Michel Verdier wrote:
> According to your link and what I do myself I think you need to have a
> daemon running. And emacsclient -a="" launches it if it's missing.
You need an emacs process running in order to use emacsclient. It need
not be a daemon. -a=""
On 2023-08-31, Charles Curley wrote:
> Having set up to use emacsclient, you (or more likely, programs
> you use such as a mail reader) can then call emacsclient so you can then
> edit files from that program in emacs. If you do it that way, you don't
> get (or need) an instance of emacs in
On 8/31/23, Wang Yizhen wrote:
>
> I recently noticed a bug for the emacs package in sid. I have not
> reported a bug before, so I wrote this email to seek for help.
>
> After upgraded to emacs 29.1+1-5, I found that the emacsclient command
> is not working. More specifica
On Fri, 1 Sep 2023 01:10:46 +0800
Wang Yizhen wrote:
> After upgraded to emacs 29.1+1-5, I found that the emacsclient
> command is not working. More specifically, the following command
> hangs emacs in daemon forever and no emacs frame pops up:
>
>
> ```
>
> emacsclient -c -a "" -n
>
> ```
On 1 Sep 2023 01:10 +0800, from wang1zhe...@gmail.com (Wang Yizhen):
> I recently noticed a bug for the emacs package in sid. I have not reported a
> bug before, so I wrote this email to seek for help.
See https://www.debian.org/Bugs/ for information on the Debian bug
tracking process, inc
Dear Debian-user group:
I recently noticed a bug for the emacs package in sid. I have not
reported a bug before, so I wrote this email to seek for help.
After upgraded to emacs 29.1+1-5, I found that the emacsclient command
is not working. More specifically, the following command hangs
hardcoded in the BIOS.
The reason, why I am telling this is, that all former kernels did not show
this issue, the only one is the actual kernel in bookworm. Maybe this is a
bug? I am thinking of a buggy timeout error or, if there is no EDD, then it
tries again and again. This issue appeared only on my
mail' message appears when it should not. In the example below I pressed TAB
> after the letter 'T' (which gave me expansion 'TODO'). I am running bash.
>
> $ me TYou have mail in /var/spool/mail/addw
> ODO
You can always look for bugs filed against a package in the packa
I have recently upgraded to Bookworm.
I have set:
MAIL=/var/spool/mail/addw
MAILCHECK=60
I find that when doing filename expansion, by pressing TAB, that the 'You have
mail' message appears when it should not. In the example below I pressed TAB
after the letter 'T' (which gave
Hello,
I have set up 40 identical systems with Debian 12.0: same SBC, same OS
version, same preseed file. These systems use a touchscreen monitor with an
eGalax USB controller. eGalax driver was installed on all of the 40 systems
and everything works fine except for 2 systems that are connected
It is a MATE problem regrading two, possibly related issues. I was thinking
mate-desktop-environment, but maybe that is wrong. Maybe it is
mate-desktop-common or something else.
It has to do with:
(1) the panel placement; Limits on which displays it allows me to place the
panel; and,
(2) the
On Thu, Jul 20, 2023 at 03:19:20PM -0700, Jon Folsom wrote:
> Hello,
>
> In a fresh installation of Bookworm, up-to-date as of today, there is a
> problem with CUPS printer configuration. I'm not sure which package to file
> a bug report against. I'll give a summary here; please le
Hello,
In a fresh installation of Bookworm, up-to-date as of today, there is a
problem with CUPS printer configuration. I'm not sure which package to file
a bug report against. I'll give a summary here; please let me know which
package I should reference using `reportbug`.
I have a network
On 6/27/23, Stefan Monnier wrote:
>> I recently updated from Bullseye to Bookworm and noticed that font hinting
>> settings in
>> `~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
>> Bullseye and I'd like to
>> report this as a bug. When I run r
> I recently updated from Bullseye to Bookworm and noticed that font hinting
> settings in
> `~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
> Bullseye and I'd like to
> report this as a bug. When I run reportbug it asks for a package name, but I
>
Hi all,
I recently updated from Bullseye to Bookworm and noticed that font hinting
settings in
`~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
Bullseye and I'd like to
report this as a bug. When I run reportbug it asks for a package name, but I
have no idea which
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
пн, 5 июн. 2023 г. в 05:36, Paul Martz :
> If I mute audio in the desktop, then reboot into console mode, the SpeakUp
> screen reading software is also muted. I think this is a bug - muting the
> desktop should be a desktop property and should not affect the console screen
> rea
Hi all.
If I mute audio in the desktop, then reboot into console mode, the SpeakUp
screen reading software is also muted. I think this is a bug - muting the
desktop should be a desktop property and should not affect the console screen
reader. But I’m not sure which package I should file
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention
Bonjour
Je n'utilise pas clamav. J'en éprouve pas le besoin.
Sur le lien, ce bug est résolu pour la version 1.0.0 (Debian Sid)
Donc pour ta version, il doit encore existé.
Comme mentionné, il faudrait rester à la version
0.103.7+dfsg-0+deb11u1 pour ne pas l'avoir.
A+
Sil writes:
Bonjour
Bonjour la liste,
J'ai une alerte de bug grave pour la mise à jour des paquets Clamav sur
une installation stable amd64. Elle fait référence à ce bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027130
libclamav9: LibClamAV Error: Can't verify database integrity
Je ne comprend pas
On Sat, May 13, 2023 at 10:18:37AM +, Schwibinger Michael wrote:
> * For Debian based distributions:
> # dpkg -i epson-inkjet-printer-escpr_.deb
>
>
>
> What is the name of architecture?
Typically, either amd64 or i386, depending on which one you installed.
The canonical way to find
On Sat, May 13, 2023 at 10:18:37AM +, Schwibinger Michael wrote:
> First
> You asked for the bug message:
>
> https://ibb.co/Xtbz1Qp
> [https://i.ibb.co/jDTLmNG/epsonprot.jpg]<https://ibb.co/Xtbz1Qp>
> epsonprot hosted at ImgBB<https://ibb.co/Xtbz1Qp>
>
First
You asked for the bug message:
https://ibb.co/Xtbz1Qp
[https://i.ibb.co/jDTLmNG/epsonprot.jpg]<https://ibb.co/Xtbz1Qp>
epsonprot hosted at ImgBB<https://ibb.co/Xtbz1Qp>
Image epsonprot hosted in ImgBB
ibb.co
Good morning
https://www.epson.co.uk/products/printers/ink
ook
> > > > > > > just the same?
> > > > > > I enable GRUB_DISABLE_OS_PROBER so that the various other operating
> > > > > > systems are shown
> > > > > > if the new GRUB is properly installed I get the "new" o
ot;old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the
list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
Olá, Hebert.
Uma pena que precisou formatar para resolver, mas ainda bem que
resolveu! O importante é funcionar.
Há alguns diretórios de caches no sistema que armazenam configurações da
interface. Uma possível causa para o problema que teve é ter ocorrido
algum erro de configuração nesses
Olá, obrigado pelo retorno! Havia tentando o htop anteriormente, mas o
consumo de memória aparentava estar normal. Ao executar o glxgears eu via
que o FPS não estava mais o mesmo. Então acabei formatando, fazendo backup
e atualizando novamente o Debian. Desta vez tudo correu bem e seguirei
Le 29/04/2023 à 18:31, hebert.thallys.pecore...@gmail.com a écrit :
o sistema ficou extremamente lento
para tarefas simples e e programas ficaram extremamente lentos.
O comando htop, por exemplo, deve mostrar quais processos estão
consumindo mais memória e processamento.
Gostaria de saber
Prezados,
Não estou familiarizado ainda com o sitema linux. Mas estava utilizando
meu Debian 11 normalmente, mas após a ultima atualização dos pacotes
alguma funcionalidades ficaram prejudicas exemplo: alterar brilho da
tela não funciona mais. Além disso, o sistema ficou extremamente lento
para
it has Several
operating systems listed, my old default OS is still at the top of the
list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still have access to the
On Fri 21 Apr 2023 at 23:05:53 (+0700), Max Nikulin wrote:
> On 21/04/2023 11:26, David Wright wrote:
> > On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
> >
> > > Opt-out variant for ESP sounds reasonable for me. However I am unsure
> > > if it is possible to complete installation
On 21/04/2023 11:26, David Wright wrote:
On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
Opt-out variant for ESP sounds reasonable for me. However I am unsure
if it is possible to complete installation with no ESP at all.
If you mean: to install Grub but not write to the ESP,
On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
> Opt-out variant for ESP sounds reasonable for me. However I am unsure
> if it is possible to complete installation with no ESP at all.
If you mean: to install Grub but not write to the ESP, I think you can
do this by saying Yes to:
on 2 disks, both ones are marked
for usage as ESP. I am unsure if it causes installation error later or
grub is installed on both ones (taking into account single /boot/efi
mount point).
Do you contribute to d-i?
No, I do not. You may check if your case has been discussed on the
insta
On 18/04/2023 11:47, David Wright wrote:
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
I have never seen a document that completely and accurately explains,
in computer engineering and science terms, the design and
implementation of the boot processes for Debian (or FreeBSD,
I've subscribed to a bug at 09:09:57 UTC and received a
"Please confirm subscription" message from bendel.debian.org
two minutes later. Fine.
I've subscribed to 3 more bugs at 10:01:05 UTC, but I haven't received
any "Please confirm subscription" message. I cannot see
On Tuesday 18 April 2023 12:47:44 am David Wright wrote:
> > I have never seen a document that completely and accurately explains,
> > in computer engineering and science terms, the design and
> > implementation of the boot processes for Debian (or FreeBSD, or
> > Windows, or macOS) for all the
On 4/17/23 21:47, David Wright wrote:
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
I have never seen a document that completely and accurately explains,
in computer engineering and science terms, the design and
implementation of the boot processes for Debian (or FreeBSD,
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
> On 4/17/23 07:41, David Wright wrote:
> > On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> > > On 4/16/23 22:08, Max Nikulin wrote:
> > > > On 17/04/2023 09:18, David Christensen wrote:
> > > > > On 4/16/23 03:41,
> > > > > *** I tried a second time, same as above being super careful, same
> > > > > result.
> > > > >
> > > > > I then booted with my default system, ran grub-install /dev/sde &&
> > > > > update-grub
On 4/17/23 03:35, Max Nikulin wrote:
My point is that UEFI and MBR install may have different behavior. You
might underestimate role of implicit conventions and agreements.
I used to think that d-i would inform me and get my permission before
making changes to my computer.
It is
On 4/17/23 07:41, David Wright wrote:
On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5"
o the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still have access to the bookworm system, you can check whether
it claimed to have completed installing Grub successfully. You sh
On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> On 4/16/23 22:08, Max Nikulin wrote:
> > On 17/04/2023 09:18, David Christensen wrote:
> > > On 4/16/23 03:41, Max Nikulin wrote:
> > > > On 16/04/2023 05:51, David Christensen wrote:
> > > > > When I moved the 2.5" SATA SSD to a
On 17/04/2023 15:27, David Christensen wrote:
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
...
The SSD
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
and configured BIOS Setup:
"Boot" -> "UEFI Boot" ->
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
and configured BIOS Setup:
"Boot" -> "UEFI Boot" -> "Enable"
The SSD would not boot.
New
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
I installed a 2.5" SATA SSD, inserted a debian-11.6.0-amd64-netinst
CD, booted the CD, and installed Debian:
"Debian GNU/Linux UEFI Installer menu" -> "Install"
...
"Partitioning method" ->
u installed Grub on /dev/sde.
> > Which method did you use to boot the "default" system (which I assume
> > is bullseye, in a different partition on one or other of the disks),
> > in view of the rather sparse menu from grub.cfg on the new system?
> I boot with the "old"
the new system?
I boot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are
the new system?
I boot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are
expect that shim is booted with no user
action when a disk is installed into another computer.
-rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
-rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
-rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
-rwxr-xr-x 1 root root 93424
7My reason for suggesting changing debconf priority to low was that
perhaps additional questions might have uncovered some strangeness in the
installer. It was not intended to fix this bug but only as a means to
further analyze the bug. Apparently those on this list failed to
understand
On Sat, Apr 15, 2023 at 07:09:58PM -0400, rhkra...@gmail.com wrote:
> On Sat, Apr 15, 2023 at 03:37:54PM -0400, Greg Wooledge wrote:
> > On Sat, Apr 15, 2023 at 07:20:58PM +0200, Geert Stappers wrote:
> > > [1] I needed a websearch on S.W.A.G. Did find
> > > - Sharing Warmth Around the Globe
> >
is a defect with d-i:
> >
> > 2023-04-15 15:10:34 root@taz ~
> > # ls -ld /mnt/nvme0n1p1/EFI/debian
> > drwxr-xr-x 2 root root 4096 Mar 16 22:19 /mnt/nvme0n1p1/EFI/debian
> >
> > 2023-04-15 15:10:36 root@taz ~
> > # ls -l /mnt/nvme0n1p1/EFI/debian
> > total 5892
> > -rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
> > -rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
> > -rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
> > -rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
> > -rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
> > -rwxr-xr-x 1 root root 934240 Mar 16 22:19 shimx64.efi
> >
> >
> > So, I agree that d-i "Install" choice has bug(s) when installing
> > Debian into a computer with multiple storage devices.
>
> Cheers,
> David.
>
>
15:10:34 root@taz ~
> # ls -ld /mnt/nvme0n1p1/EFI/debian
> drwxr-xr-x 2 root root 4096 Mar 16 22:19 /mnt/nvme0n1p1/EFI/debian
>
> 2023-04-15 15:10:36 root@taz ~
> # ls -l /mnt/nvme0n1p1/EFI/debian
> total 5892
> -rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
> -rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
> -rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
> -rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
> -rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
> -rwxr-xr-x 1 root root 934240 Mar 16 22:19 shimx64.efi
>
>
> So, I agree that d-i "Install" choice has bug(s) when installing
> Debian into a computer with multiple storage devices.
Cheers,
David.
On Saturday, April 15, 2023 03:37:54 PM Greg Wooledge wrote:
> I think it's either "Stupid Wild-Ass Guess" or "Silly Wild-Ass Guess".
In my experience (and usage) it was "Scientific Wild Ass Guess".
--
rhk
| No entity has permission to use this email to train an AI.
~
# ls -l /mnt/nvme0n1p1/EFI/debian
total 5892
-rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
-rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
-rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
-rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
-rwxr-xr-x 1 root root 8
On Sat, Apr 15, 2023 at 07:20:58PM +0200, Geert Stappers wrote:
> [1] I needed a websearch on S.W.A.G. Did find
> - Sharing Warmth Around the Globe
> - Sealed With A Gift
> - Stolen Without A Gun
> - So What? Another Giveaway?
> - Sub-Watershed Advisory Group
> - Some Women Are Great
> -
On Sat, Apr 15, 2023 at 06:24:34PM +0100, Andrew Wood wrote:
> On 15/04/2023 18:20, Geert Stappers wrote:
> > On Sat, Apr 15, 2023 at 11:02:02AM -0400, Jude DaShiell wrote:
> > > On Sat, 15 Apr 2023, Geert Stappers wrote:
> > > > On Sat, Apr 15, 2023 at 10:36:14AM +0100, Andrew Wood wrote:
> > > >
You've never seen debian main menu in the installer. That's selection 19
on that main menu and selection 21 helps big time with debugging since you
choose that to save log files and selection 3 under that will save logs to
/var/log/installer directory. Two ways to get to main menu. First and
On 15/04/2023 18:20, Geert Stappers wrote:
Time will tell if original poster shares information
on whether or not if priority for debian-install was changed.
Nothing was changed. I dont even know what that is. Ive installed Debian
on many systems over the past 12 years and have never
riority if memory serves is
> medium.
Time will tell if original poster shares information
on whether or not if priority for debian-install was changed.
> > Please make it possible to reproduce what is encountered.
> > Yeah, I would like to known what happened
> > and I say
On 15/04/2023 14:12, Geert Stappers wrote:
Way before "grub install" should have been asked
On which disk to install
I do read "two devices were effected", I think it is the same error of
On which disk to install
If you mean did it install Debian on the NVme ssd then no, the
A s.w.a.g. here. Priority of questions asked was not set to low in the
main menu. I routinely change that to low when doing a debian install and
preserve logs for future reference. Default priority if memory serves is
medium.
-- Jude "There are four boxes to be used in
defense of liberty:
On Sat, Apr 15, 2023 at 10:36:14AM +0100, Andrew Wood wrote:
> Ive just used the Debian 11 installer ISO running from a USB stick to do an
> install (AMD64/UEFI) on another USB stick to use as a 'portable PC'.
>
> When it got to the Grub install stage I was expecting it to ask me which
> disk I
Ive just used the Debian 11 installer ISO running from a USB stick to do
an install (AMD64/UEFI) on another USB stick to use as a 'portable PC'.
When it got to the Grub install stage I was expecting it to ask me which
disk I wanted Grub installed on as it has in the past but instead it did
kernel: watchdog: BUG: soft lockup - CPU#15 stuck
for 26s! [kworker/15:2:1033]
Apr 10 07:50:28 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4
dns_resolver nfs lockd grace fscache netfs rfkill qrtr sunrpc
binfmt_misc
her of the disks),
in view of the rather sparse menu from grub.cfg on the new system?
> back to the WiFi dongle, again the obscure firmware was properly installed
>
> Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still have access to
Pankaj Jangid writes:
> I just discovered that there is no "input source" for Hindi (language)
> or Devanagari Script. Which package should I file the bug against?
>
> In Debian 11.6, the input source was present and switching with
> Super+Space was working just fine.
I just discovered that there is no "input source" for Hindi (language)
or Devanagari Script. Which package should I file the bug against?
In Debian 11.6, the input source was present and switching with
Super+Space was working just fine.
I have upgraded to "bookworm"
mware was properly installed
Is this a Bug or a user/hardware issue?
t;Skylake" are processor code names. For the Core
2 Duo E8400 this is "Wolfdale" according to ark.intel.com
Do I need to worry about those microcode bugs?
Your CPU us far older than the ones affected by the microcode bug. It
does not have a code name matching one of the listed
> I have no idea whether my old processor is a "CoffeeLake" or a "Skylake" or
> something else. It is a pc that I bought in 2008, I think (and still
> working just fine).
For those kinds of questions, I find Wikipedia to be the most helpful
source of info.
Stefan
Jesper Dybdal composed on 2023-03-19 19:00 (UTC+0100):
> /proc/cpuinfo says:
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
> Do I need to worry about those microcode bugs?
IIRC, I have 3
On 2023-03-19 at 14:00, Jesper Dybdal wrote:
> I am planning to upgrade from Buster to Bullseye, and trying to prepare
> for any problems.
>
> The release notes say
>> The intel-microcode package currently in bullseye and buster-security
>> (see DSA-4934-1 (https:
>>
gs?
Your CPU us far older than the ones affected by the microcode bug. It does
not have a code name matching one of the listed ones. I'd conclude that your
CPU is not affected.
HTH
Linux-Fan
öö
pgpVU7E3j6RtC.pgp
Description: PGP signature
I am planning to upgrade from Buster to Bullseye, and trying to prepare
for any problems.
The release notes say
The intel-microcode package currently in bullseye and buster-security
(see DSA-4934-1 (https:
//www.debian.org/security/2021/dsa-4934)) is known to contain two
significant bugs. For
to
> skip the generation of the error. Do you confirm that you are following
> this approach ?
That's certainly what I would do. There are four workarounds listed at
https://bugs.launchpad.net/oem-priority/+bug/1842320/comments/125
three of which seem simple: MODULES=dep, COMPRESS=,
and GRUB_GFXMODE.
On Tue, 14 Mar 2023 Mario Marietto wrote:
No problem. But without offence,what you are suggesting to me is not to
make something to understand what's the real problem and why it's
happening,
I believe that the locution above --"make something to understand"--
paraphrases "diagnose".
but you
On Tue, 14 Mar 2023 Mario Marietto wrote in reply to Andrew Cater:
--> *Which* Debian .iso did you install with ?
debian-live-11.5.0-amd64-xfce.iso.
Is there a way to upgrade this to the version that you have
suggested ? I prefer to learn how to upgrade it than to make a
fresh installation. I
;
I am suggesting a re-install with a more current Debian version. 11.5 was
released in September last year, 11.6 in December last year. Each point
release brings fixes.
If you are installing from an old medium and one that I can no longer find,
I can't remember all of the bug fixes that have gone
No problem. But without offence,what you are suggesting to me is not to
make something to understand what's the real problem and why it's
happening,but you are suggesting to change something in my configuration to
skip the generation of the error. Do you confirm that you are following
this
Andrew M.A. Cater composed on 2023-03-14 22:02 (UTC):
> I would suggest that you try with the netinst for the main Debian installer.
> Other larger media are also available.
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0+nonfree/amd64/
> has iso-cd and
On Tue, Mar 14, 2023 at 09:23:32PM +0100, Mario Marietto wrote:
> --> *Which* Debian .iso did you install with ?
>
> debian-live-11.5.0-amd64-xfce.iso. Is there a way to upgrade this to the
> version that you have suggested ? I prefer to learn how to upgrade it than
> to make a fresh
h one came from the original
> .iso
>
> All the very best, as ever,
>
> Andy Cater
> >
>
> >
> > On Mon, Mar 13, 2023 at 8:48 PM davidson wrote:
> >
> > > On Mon, 13 Mar 2023 Mario Marietto wrote:
> > > > Hello to every Debian user.
> > >
lowing question
> > off-topic in another thread]
> > >
> > > "I've just installed Debian 11
> > > and I see that it is affected by the bug
> > > explained here :
> > >
> > > https://bugs.launchpad.net/oem-priority/+bug/1842320
> >
for posting the following question
> off-topic in another thread]
> >
> > "I've just installed Debian 11
> > and I see that it is affected by the bug
> > explained here :
> >
> > https://bugs.launchpad.net/oem-priority/+bug/1842320
> >
&
On Mon, 13 Mar 2023 Mario Marietto wrote:
Hello to every Debian user.
[elided: Mario Marietto's apology for posting the following question
off-topic in another thread]
"I've just installed Debian 11
and I see that it is affected by the bug
explained here :
https://bugs.launchpad.ne
I see that it is affected by the bug
explained here :
https://bugs.launchpad.net/oem-priority/+bug/1842320
I see that the bug has been fixed on Ubuntu. Do you confirm that,to fix
it,I just need to install the package
"grub-efi-amd64_2.06-2ubuntu14.1_amd64.deb" with the command "dpkg -i
On Thu, Mar 02, 2023 at 09:52:35AM +0800, Jeremy Ardley wrote:
> On 2/3/23 05:51, Greg Wooledge wrote:
> > unicorn:~$ namei -l ~/.ssh/config
> > f: /home/greg/.ssh/config
> > drwxr-xr-x root root /
> > drwxr-xr-x root root home
> > drwxr-xr-x greg greg greg
> > drwxr-xr-x greg greg .ssh
> >
On Wed, Mar 1, 2023 at 8:53 PM Jeremy Ardley wrote:
> [...]
> However I've found the cause of the problem, but not necessarily
> resolved the bug.
>
> For some reason on my journey /etc/ssh/ssh_config had acquired
>
> UserKnownHostsFile /etc/ssh/ssh_kno
-- 1 jeremy jeremy 567 Dec 11 11:47 id_rsa.pub
However I've found the cause of the problem, but not necessarily
resolved the bug.
For some reason on my journey /etc/ssh/ssh_config had acquired
UserKnownHostsFile /etc/ssh/ssh_known_hosts
changing to
# UserKnownHostsFile /etc/ssh
On 2/3/23 05:52, Jeffrey Walton wrote:
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
I may have found a bug in openssh.
[...]
I have created a ~/.ssh/config file with contents
Host jeremy_client
HostName client.example.com
User jeremy
IdentityFile ~/.ssh
On Wed, Mar 01, 2023 at 04:52:57PM -0500, Jeffrey Walton wrote:
> On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
> >
> > I may have found a bug in openssh.
> > [...]
> > I have created a ~/.ssh/config file with contents
> >
> > Host jeremy_clie
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
>
> I may have found a bug in openssh.
> [...]
> I have created a ~/.ssh/config file with contents
>
> Host jeremy_client
> HostName client.example.com
> User jeremy
> IdentityFile ~/.ssh/com.example.jer
On Wed, Mar 01, 2023 at 02:43:38PM -0700, Charles Curley wrote:
> On Thu, 2 Mar 2023 03:48:49 +0800
> jeremy ardley wrote:
>
> > 2. The known hosts file used is /etc/ssh/known_hosts rather that
> > ~/.ssh/known_hosts - which causes a permissions error
>
> I am not seeing that, for either root
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
>
> I may have found a bug in openssh.
>
> I raise it here as the ssh mailing list is actually a newsgroup that
> no-one seems to use.
You might give comp.security.openssh a try:
https://groups.google.com/g/co
201 - 300 of 8562 matches
Mail list logo
