On Wed, 12 Jun 2024 22:56:34 -0400
Greg Wooledge wrote:
> On Thu, Jun 13, 2024 at 12:16:00PM +1000, Charlie wrote:
> > Cannot recall what version of Debian stopped copying text in xterm
> > by Ctrl + C or Shift + Ctrl + C So don't know how to copy from
> > xterm
>
> xterm is a terminal
Hi Hans!
On Sat, Jun 08, 2024 at 11:43:38AM +0200, Hans wrote:
> Hello!
>
> For those, who are interested in my discovering with bootcd, I attached a
> screenshot of the
> message, the installer told and why grub can not be installed. It might
> explain more.
>
You might want to try OFTC
Hello!
For those, who are interested in my discovering with bootcd, I attached a
screenshot of the
message, the installer told and why grub can not be installed. It might explain
more.
However, I suppose, there are not many people in the world, building
a live-system + installer + bootcd on
On Sat, 8 Jun 2024 11:45:49 +0700
Max Nikulin wrote:
Hello Max,
>On 08/06/2024 00:48, Hans wrote:
>> BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed
>No it does not. I have both installed. I think, the latter needs .mod
The pedant in me would point out that actually, no,
On 08/06/2024 00:48, Hans wrote:
BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed
No it does not. I have both installed. I think, the latter needs .mod
files provided by the former.
On Fri, Jun 7, 2024 at 1:48 PM Hans wrote:
>
> Got it! Found the reason and a fix for it.
>
> Just not easy to find. It is an dependency-problem!
>
> What happened?
>
> Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul
> exist in my live-system. During build this made
Looks like a typo from me.
apt-cache search grub-efi-amd | grep signed
grub-efi-amd64-signed - GRand Unified Bootloader, version 2 (amd64 UEFI signed
by Debian)
grub-efi-amd64-signed-template - GRand Unified Bootloader, Version 2
(Signaturvorlage für
EFI-AMD64)
It is grub-efi-amd64-signed.
On Fri 07 Jun 2024 at 19:48:21 (+0200), Hans wrote:
> Got it! Found the reason and a fix for it.
> Just not easy to find. It is an dependency-problem!
>
> What happened?
>
> Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul
> exist in my live-
> system. During build
Got it! Found the reason and a fix for it.
Just not easy to find. It is an dependency-problem!
What happened?
Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul
exist in my live-
system. During build this made no problems and all dependencies are ok. But -
during
On 2024-06-03, Chris M wrote:
>
> Thunderbird is the name of a cheap wine?
>
A mutt is a mongrel dog, if that adds anything to the conversation.
songbird wrote:
>
> as an FYI, last night this wasn't a good idea:
>
> The following packages will be upgraded:
>gir1.2-matepanelapplet-4.0 (1.27.1-2+b2 => 1.27.1-3)
>libmate-panel-applet-4-1 (1.27.1-2+b2 => 1.27.1-3)
>libmate-panel-applet-dev (1.27.1-2+b2 => 1.27.1-3)
>
On Mon 03 Jun 2024 at 14:08:46 (-0500), Chris M wrote:
> I am needing a "refresher course" on mail clients that use the .mbox
> format to store emails.
> It's been years since I've used this kind of mail client.
>
> Is there any "dangers" I need to know about? Like, keeping the mailbox
> a
On Mon, 3 Jun 2024 15:25:12 -0400
e...@gmx.us wrote:
> The USAF Thunderbirds predate Gallo Thunderbird by at least a year.
> They were founded in 1953, and the law allowing Gallo Thunderbird's
> creation wasn't passed until the next year. The wine was certainly
> out by 1957. The Ford
On Tue, Jun 04, 2024 at 03:45:11AM +0800, Bret Busby wrote:
> On 4/6/24 03:25, e...@gmx.us wrote:
> > On 6/3/24 12:10, James H. H. Lampert wrote:
> > > (who still hasn't figured out why Ford named a car, and the Air
> > > Force named
> > > its demonstration team, after that same cheap wine)
> >
>
On 4/6/24 04:30, e...@gmx.us wrote:
On 6/3/24 15:45, Bret Busby wrote:
On 4/6/24 03:25, e...@gmx.us wrote:
On 6/3/24 12:10, James H. H. Lampert wrote:
(who still hasn't figured out why Ford named a car, and the Air Force
named its demonstration team, after that same cheap wine)
The USAF
debian-u...@howorth.org.uk wrote:
Chris M wrote:
I love Evolution and Claws to a point. Its a PITA to forward emails
with HTML in them, like the Informed Delivery email I get each morning
letting us know whats coming in the USPS that day.
Claws forwards mails with a text/html part just fine.
On 6/3/24 15:45, Bret Busby wrote:
On 4/6/24 03:25, e...@gmx.us wrote:
On 6/3/24 12:10, James H. H. Lampert wrote:
(who still hasn't figured out why Ford named a car, and the Air Force
named its demonstration team, after that same cheap wine)
The USAF Thunderbirds predate Gallo Thunderbird
Chris M wrote:
> I love Evolution and Claws to a point. Its a PITA to forward emails
> with HTML in them, like the Informed Delivery email I get each morning
> letting us know whats coming in the USPS that day.
Claws forwards mails with a text/html part just fine. What's your actual
problem with
On 4/6/24 03:25, e...@gmx.us wrote:
On 6/3/24 12:10, James H. H. Lampert wrote:
(who still hasn't figured out why Ford named a car, and the Air Force
named
its demonstration team, after that same cheap wine)
The USAF Thunderbirds predate Gallo Thunderbird by at least a year. They
were
On 6/3/24 12:10, James H. H. Lampert wrote:
(who still hasn't figured out why Ford named a car, and the Air Force named
its demonstration team, after that same cheap wine)
The USAF Thunderbirds predate Gallo Thunderbird by at least a year. They
were founded in 1953, and the law allowing Gallo
I am needing a "refresher course" on mail clients that use the .mbox
format to store emails.
It's been years since I've used this kind of mail client.
Is there any "dangers" I need to know about? Like, keeping the mailbox a
certain size?
or a certain amount of emails per folder etc?
The last
James H. H. Lampert wrote:
I will say that one should probably not expect perfection from an
email reader that's named after a cheap wine.
In my experience, T-Bird is the worst email reader I've ever used . .
. except for *every other* email reader (without a single exception)
I've tried.
Bret Busby wrote:
> On 4/6/24 00:10, James H. H. Lampert wrote:
> > I will say that one should probably not expect perfection from an email
> > reader that's named after a cheap wine.
> >
>
> ?
USA-centric reference. See https://en.wikipedia.org/wiki/Flavored_fortified_wine
-dsr-
On Mon, Jun 3, 2024 at 2:14 PM Bret Busby wrote:
>
> On 4/6/24 00:10, James H. H. Lampert wrote:
> > I will say that one should probably not expect perfection from an email
> > reader that's named after a cheap wine.
>
> ?
Thunderbird wine was extremely inexpensive and 42 proof.
In retrospect I'm
On 4/6/24 00:10, James H. H. Lampert wrote:
I will say that one should probably not expect perfection from an email
reader that's named after a cheap wine.
?
Bret Busby
Armadale
Western Australia
(UTC+0800)
.
I will say that one should probably not expect perfection from an email
reader that's named after a cheap wine.
In my experience, T-Bird is the worst email reader I've ever used . . .
except for *every other* email reader (without a single exception) I've
tried. I'm particularly irritated
Bret Busby wrote:
On 3/6/24 04:14, Chris M wrote:
Felix Miata wrote:
It might be worth checking what language the emails are in. Thunderbird
allows you to specify fonts separately for each writing system (e.g. if
you want to specify fonts for Japanese or Greek or Khmer messages, you
can
Bret Busby wrote:
Hello, Chris.
We appear to be 13 hours ahead of you (see my signature), so, the time
here, is now about 0430. I am a creature of the night.
OH man, 4:30 AM! That's way too early for me!
Andika? Search for it in Synaptic...
:)
I am not sure whether
On 3/6/24 04:14, Chris M wrote:
Felix Miata wrote:
It might be worth checking what language the emails are in. Thunderbird
allows you to specify fonts separately for each writing system (e.g. if
you want to specify fonts for Japanese or Greek or Khmer messages, you
can do). For English and
On 3/6/24 03:56, Chris M wrote:
Bret Busby wrote:
Whilst, at groups.io, two different Tbird email users lists exist; one
for blind people, and, the other, for those of us who still have
sufficient sight, and, these messages about Tbird, should, more
properly, be directed to the Tbird users
Felix Miata wrote:
It might be worth checking what language the emails are in. Thunderbird
allows you to specify fonts separately for each writing system (e.g. if
you want to specify fonts for Japanese or Greek or Khmer messages, you
can do). For English and comparable languages, you want to
Bret Busby wrote:
For
Language
Choose the languages used to display menus, messages, and
notifications from Thunderbird.
I have set English (GB) which, I expect, will confound anything that
tries to impose characters that are not what I want.
Bret Busby
Armadale
Western Australia
Darac Marjal wrote:
It might be worth checking what language the emails are in.
Thunderbird allows you to specify fonts separately for each writing
system (e.g. if you want to specify fonts for Japanese or Greek or
Khmer messages, you can do). For English and comparable languages, you
want to
Bret Busby wrote:
Whilst, at groups.io, two different Tbird email users lists exist; one
for blind people, and, the other, for those of us who still have
sufficient sight, and, these messages about Tbird, should, more
properly, be directed to the Tbird users lists, try the following.
In
UPDATE:
I might of found a solution to my problem:
I somehow stumbled across:
https://addons.thunderbird.net/en-US/seamonkey/addon/no-small-text/?src=search
Then launched Seamonkey browser and set the " NO SMALL TEXT" settings to:
https://imgur.com/a/DvJaTeG
If you're in the US scroll down
Just to compare, when Red Hat released 9.0 maybe 2 years ago (9.2 is
current until 30 June) they disabled by default many older key-lengths and
algorithms in SSL that were known to be weak. This caused issues for
existing installations. You could either re-enable the weaker methods (easy
but a
DdB wrote:
...
> But i cannot endorse on bookworm without finding alternatives viable to
> my handicap. Does that mean, i am back to square one?
> Currently, i am 6 years behind (still on debian 10), because i was not
> willing to lose functionality i am used to. BTW: the GNOME team did that
> to
On 01/06/2024 16:42, Thomas Schmitt wrote:
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1
Debian-5
(I wonder what the string "Debian-5" may mean. The Debian 12 machine has
debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u2
So "-5" is not
DdB wrote:
> Am 01.06.2024 um 11:02 schrieb Andrew M.A. Cater:
> > You would need to go from buster - bullseye to bookworm anyway.
> >
> > Read the Release Notes for Bullseye to pick up on any changes.
> >
> > Do note also that Bookworm is currently supported: Bullseye security
> > support ends
On Sat, 1 Jun 2024 11:47:59 +0200
DdB wrote:
Hello DdB,
>BTW: the GNOME team did that to me repeatedly
In fairness, it's not just Gnome that erodes features. TBH, they *all*
do it. I've seen features removed from Plasma, Claws Mail, Tellico,
loads of stuff. Worst of all is when the removal
Am 01.06.2024 um 11:02 schrieb Andrew M.A. Cater:
> You would need to go from buster - bullseye to bookworm anyway.
>
> Read the Release Notes for Bullseye to pick up on any changes.
>
> Do note also that Bookworm is currently supported: Bullseye security
> support ends round July 31st this year
Hi,
Jeffrey Walton wrote:
> If I am not mistaken, the problem you are experiencing is due to using
> RSA/SHA-1 on the old machine.
Max Nikulin wrote:
> My reading of /usr/share/doc/openssh-client/NEWS.Debian.gz is that ssh-rsa
> means SHA1 while clients offers SHA256 for the same id_rsa key.
On Sat, Jun 01, 2024 at 08:52:14AM +0200, DdB wrote:
> Am 31.05.2024 um 12:57 schrieb DdB:
> > Hello,
> >
> >
> > Now is the time to plan ahead for years to come and i don't know, what i
> > should do.
> >
> > DdB
>
> Thanks for all your input.
> In the meantime, i did check for the specific
Am 31.05.2024 um 12:57 schrieb DdB:
> Hello,
>
> while being on old-old-stable still (buster) and preparing for an
> upgrade to bookworm, i noticed, that GNOME once again lost compatibility
> to my preferred extensions, giving me a hard choice to either go on with
> my outdated system as long as
Hi,
the following line in ~/.ssh/config did the trick:
PubkeyAcceptedAlgorithms +ssh-rsa
This lets ssh -v report:
debug1: Offering public key: /home/.../.ssh/id_rsa RSA SHA256:...
debug1: Server accepts key: /home/.../.ssh/id_rsa RSA SHA256:...
Authenticated to ... ([...]:22) using
In the end, the problem had nothing to do with APT pinning, mixing
Debian flavors, nor anything else mentioned in the previous messages.
I've just noticed that in my XFCE mixer there is a tab "Configuration",
where you can set the audio profile. I don't even know what an audio
profile is
digital out but this is not
your setup.
You can have a look at [1] for software fixes on this.
[1] https://alsa.opensrc.org/SurroundSound
I solved by buying a Toslink (S/PDIF) optical cable, and using thus the
"Surround 5.1 Digital output" and unplugging the three jacks analog
On Wed Apr 24, 2024 at 1:50 PM BST, Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix for
On 26/04/2024 12:56, David Wright wrote:
On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
Innocent question: what difference does the comment make vs just ending the
file with an empty line?
Nothing for the computer, but visibility for me.
Say you print the file on paper. All you
On 26/04/2024 10:56, David Wright wrote:
Editor examples: a windowed emacs buffer has a ≣ decoration at the
extreme left edge after the last line of text, so that you can
distinguish an absence of lines from empty lines.
Perhaps that decoration should be explicitly enabled. However it
On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
> On 24/04/2024 22:37, David Wright wrote:
> > On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> > > upon gathering my thoughts for answering to you I found the solution to
> > > this: update-initramfs can't handle the case that
On 24/04/2024 22:37, David Wright wrote:
On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character.
On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix
Hi Michel,
upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character. I think there either
should be a fix for this or at least a way to handle this case with
On 4/24/24 00:46, Charlie Gibbs wrote:
On 2024-04-22 16:50, Jeffrey Walton wrote:
What are the old and new hard drive model numbers and specs?
Correction: the 4TB drive is a Western Digital WD40EFPX. I was reading
it by shining a flashlight through a gap in the frame and squinting from
a
On 2024-04-22 16:50, Jeffrey Walton wrote:
What are the old and new hard drive model numbers and specs?
Correction: the 4TB drive is a Western Digital WD40EFPX. I was reading
it by shining a flashlight through a gap in the frame and squinting from
a wide angle because I didn't want to take
On Thu, Apr 11, 2024 at 04:14:33PM +0200, DdB wrote:
> - the resulting transfer is way faster than say ... ssh.
AFAIK ssh is mono-threaded (like OpenVPN, unless you use the kernel
module). wireguard is multi-threaded.
The symptom will be one CPU ("core") at 100% and the rest mostly
idle.
Hi Greg,
ah, I wasn't aware of this. This is really great news! And it will help me
much.
You made my day! Thank you very much.
Best regards
Hans
> On Thu, Apr 11, 2024 at 08:42:20PM +0200, Hans wrote:
> > in my case it is the config freom from bootcdwrite, which is
> > bootcdwrite.conf.
>
Am 11.04.2024 um 15:49 schrieb Marc SCHAEFER:
> Hello,
>
> On Tue, Apr 09, 2024 at 03:13:01PM +0200, DdB wrote:
>> from my research, the abbreviated takeaway is:
>
> I never used mbuffer, I use buffer combined with netcat-traditional:
>
># receiver (TCP server on port 8000)
>nc -l -p
Hi all,
thank you for the fast response. Your answers did help much and made
everything clear.
Have a nice weekend!
Best
Hans
On Thu, Apr 4, 2024 at 4:06 AM Stefan Monnier wrote:
>
> > I have a 128 MB USB flash drive from back in the day that includes a write
> > protect switch. There are few products today that offer that feature.
>
> Side note: AFAIK this "write protect switch" doesn't prevent writing.
> It just
On 4/3/24 19:05, Stefan Monnier wrote:
I have a 128 MB USB flash drive from back in the day that includes a write
protect switch. There are few products today that offer that feature.
Side note: AFAIK this "write protect switch" doesn't prevent writing.
It just tells your card reader that
> I have a 128 MB USB flash drive from back in the day that includes a write
> protect switch. There are few products today that offer that feature.
Side note: AFAIK this "write protect switch" doesn't prevent writing.
It just tells your card reader that you'd like to avoid writing to it.
On 4/3/24 08:16, David Wright wrote:
On Tue 02 Apr 2024 at 05:54:06 (-0700), David Christensen wrote:
On 4/1/24 11:35, DdB wrote:
Am 01.04.2024 um 18:52 schrieb David Christensen:
A bad USB flash drive would explain why you cannot boot the Debian
installer. Please buy a good quality USB 3.0+
On Tue 02 Apr 2024 at 05:54:06 (-0700), David Christensen wrote:
> On 4/1/24 11:35, DdB wrote:
> > Am 01.04.2024 um 18:52 schrieb David Christensen:
> > > A bad USB flash drive would explain why you cannot boot the Debian
> > > installer. Please buy a good quality USB 3.0+ flash drive and try
On 4/3/24 03:36, David Christensen wrote:
On 4/3/24 00:30, Thomas Schmitt wrote:
Hi,
David Christensen wrote:
It's a relatively simple experiment to confirm that a USB flash drive
with
d-i changes after the first boot.
This could still be
On 4/3/24 00:30, Thomas Schmitt wrote:
Hi,
David Christensen wrote:
It's a relatively simple experiment to confirm that a USB flash drive with
d-i changes after the first boot.
This could still be
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or
Hi,
David Christensen wrote:
> It's a relatively simple experiment to confirm that a USB flash drive with
> d-i changes after the first boot.
This could still be
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or MS-Windows altered the USB stick.
> Same for
On 4/2/24 08:56, Thomas Schmitt wrote:
Hi,
David Christensen wrote:
the Debian installer modifies the contents of the USB flash drive when
it runs.
Do you mean inside the range of the ISO image or outside by creating a
new partition ?
songbird wrote:
if it is an iso image copied to the
On 4/2/24 07:55, songbird wrote:
David Christensen wrote:
I thought about suggesting that in my last post, but did not want to
complicate things. A key advantage of using a CD-R disc is that you can
verify the disc contents and/or checksum against the ISO and/or checksum
now and in the future.
Hi,
David Christensen wrote:
> > the Debian installer modifies the contents of the USB flash drive when
> > it runs.
Do you mean inside the range of the ISO image or outside by creating a
new partition ?
songbird wrote:
> if it is an iso image copied to the USB stick it should not
> be
David Christensen wrote:
> I thought about suggesting that in my last post, but did not want to
> complicate things. A key advantage of using a CD-R disc is that you can
> verify the disc contents and/or checksum against the ISO and/or checksum
> now and in the future. This is not true for a
On 4/1/24 11:35, DdB wrote:
Am 01.04.2024 um 18:52 schrieb David Christensen:
A bad USB flash drive would explain why you cannot boot the Debian
installer. Please buy a good quality USB 3.0+ flash drive and try again.
A friend of mine just let me use an external CD-Drive with the netboot
Am 01.04.2024 um 18:52 schrieb David Christensen:
> A bad USB flash drive would explain why you cannot boot the Debian
> installer. Please buy a good quality USB 3.0+ flash drive and try again.
A friend of mine just let me use an external CD-Drive with the netboot
image. This is already the
Hi,
thank you all for the fast response. It helped a lot and made everything
clear.
The problem is solved.
Have a nice eastern.
Best
Hans
Jeffrey Walton writes:
> On Mon, Mar 4, 2024 at 4:58 PM Greg wrote:
>>
>> On 2/26/24 18:52, Kamil Jońca wrote:
>> [...]
>> >
>> > What if:
>> > network = {
>> > ssid="ssid"
>> > key_mgmt=WPA-EAP
>> > eap=PEAP
>> > identity="uid"
>> > phase2="auth=MSCHAPV2"
>> >
On Mon, Mar 4, 2024 at 4:58 PM Greg wrote:
>
> On 2/26/24 18:52, Kamil Jońca wrote:
> [...]
> >
> > What if:
> > network = {
> > ssid="ssid"
> > key_mgmt=WPA-EAP
> > eap=PEAP
> > identity="uid"
> > phase2="auth=MSCHAPV2"
> > mesh_fwding=1
> >
On 2/26/24 18:52, Kamil Jońca wrote:
[...]
What if:
network = {
ssid="ssid"
key_mgmt=WPA-EAP
eap=PEAP
identity="uid"
phase2="auth=MSCHAPV2"
mesh_fwding=1
password="pas"
}
Bingo! Dzięki wielkie, ułatwiłeś mi życie.
Regards
Greg
On Mon, 26 Feb 2024, Andy Smith wrote:
Hi,
On Mon, Feb 26, 2024 at 06:25:53PM +, Tim Woodall wrote:
Feb 17 17:01:49 xen17 vmunix: [3.802581] ata1.00: disabling queued TRIM
support
Feb 17 17:01:49 xen17 vmunix: [3.805074] ata1.00: disabling queued TRIM
support
from
Hi,
On Mon, Feb 26, 2024 at 06:25:53PM +, Tim Woodall wrote:
> Feb 17 17:01:49 xen17 vmunix: [3.802581] ata1.00: disabling queued TRIM
> support
> Feb 17 17:01:49 xen17 vmunix: [3.805074] ata1.00: disabling queued TRIM
> support
>
>
> from libata-core.c
>
> { "Samsung SSD 870*",
>>> You should not be running trim in a container/virtual machine
>> Why not? That's, in my case, basically saying "you should not be running
>> trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
>> to understand why. Enabling thin_provisioning and fstrim works and gets
>>
On 2/26/24 16:31, Tim Woodall wrote:
On Mon, 26 Feb 2024, Gremlin wrote:
re running fstrim in a vm.
The Host system takes care of it
I guess you've no idea what iscsi is. Because this makes no sense at
all. systemd or no systemd. The physical disk doesn't have to be
something the host
On Mon, 26 Feb 2024, Gremlin wrote:
re running fstrim in a vm.
The Host system takes care of it
I guess you've no idea what iscsi is. Because this makes no sense at
all. systemd or no systemd. The physical disk doesn't have to be
something the host system knows anything about.
Here's a
On 2/26/24 14:40, Tim Woodall wrote:
On Mon, 26 Feb 2024, Gremlin wrote:
Are you using systemd ?
No, I'm not
You should not be running trim in a container/virtual machine
Why not? That's, in my case, basically saying "you should not be running
trim on a drive exported via iscsi" Perhaps I
On Mon, 26 Feb 2024, Gremlin wrote:
Are you using systemd ?
No, I'm not
You should not be running trim in a container/virtual machine
Why not? That's, in my case, basically saying "you should not be running
trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
to
On 2/26/24 13:25, Tim Woodall wrote:
TLDR; there was a firmware bug in a disk in the raid array resulting in
data corruption. A subsequent kernel workaround resulted in
dramatically reducing the disk performance. (probably just writes but I
didn't confirm)
Initially, under heavy disk load I
TLDR; there was a firmware bug in a disk in the raid array resulting in
data corruption. A subsequent kernel workaround resulted in
dramatically reducing the disk performance. (probably just writes but I
didn't confirm)
Initially, under heavy disk load I got errors like:
Preparing to unpack
On Tue, 2024-02-06 at 01:37 -0500, Brian Sammon wrote:
> On Mon, 05 Feb 2024 21:06:30 +0100
> hw wrote:
>
> > Yes, it's a misunderstanding: How can we change the keyboard layout?
>
> [...]
> https://medium.com/@canadaduane/key-remapping-in-linux-2021-edition-47320999d2aa
So this allowed me to
Good afternoon
Another option is to use a keyboard shortcut. My last laptop came with
this set up using a Fn key combo (eg fn-f5)
So I'm using a key that was set to answer MSteams calls - what?
Check keyboard - shortcuts - touchpad. cinnamon gives options of
toggle/switch on/ switch-off. I
On 25/01/2024 21:42, Max Nikulin wrote:
Try
lsusb --verbose --tree
I have received a private reply. Please, send messages to the mailing
list in such cases.
I intentionally combined -vt options and I find output more convenient
than for just "lsusb -t". The "-t" option changes
On 25/01/2024 20:42, Henning Follmann wrote:
The issue is a usb hub. Somehow GNOME thinks this hub is a mouse.
Try
lsusb --verbose --tree
perhaps somebody plugged in a tiny receiver for a wireless mouse and
forgot about it.
On Wed, Jan 24, 2024 at 03:30:23PM -0500, Henning Follmann wrote:
> Hello,
> for a while I am using
>
> gsettings set org.gnome.desktop.peripherals.touchpad send-events
> 'disabled-on-external-mouse'
>
> which really worked fine.
>
> But since last week this does not work anymore; in the way
On Wed, 24 Jan 2024 07:33:59 +
Tixy wrote:
> On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> [...]
>
> As you've already found out, that's not the latest one, and if I'm not
> mistaken is the one that introduce a wifi bug [1], so that could
> explain it getting stuck in the
On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> I went to shut down the machine, and it got stuck trying to shut down
> wpa_supplicant and Network Manager. Ten minutes into the shutdown, I
> finally pulled the plug. A few reboots and shutdowns later, I decided
> to try another kernel. I
On Wed, 24 Jan 2024 09:25:58 +0700
Max Nikulin wrote:
> On 24/01/2024 03:34, Charles Curley wrote:
> > So I purged the newer kernel, inux-image-6.1.0-15-amd64
>
> The current kernel is linux-image-6.1.0-17-amd64
>
> Perhaps you have not restored your sources.list or apt preferences
> after
On 24/01/2024 03:34, Charles Curley wrote:
So I purged the newer kernel, inux-image-6.1.0-15-amd64
The current kernel is linux-image-6.1.0-17-amd64
Perhaps you have not restored your sources.list or apt preferences after
the accidents with kernel bugs. Check that nothing extra is added and
run chromium, I get:
>
> charles@jhegaala:~$ chromium &
> [2] 33609
> charles@jhegaala:~$ libva error:
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
>
> charles@jhegaala:~$
I seem to have solved this problem, entirely by accident.
I went to shut down the
Hi all,
I could obviously solve the problem. It was not, as formerly guessed,
the /etc/hosts file, the reason was found in ~/.cache/*
In ~/.cache/* I found several old files of documents (*.odt, *.ods).
The customer told me, that not all files could be opened. Some opened fast,
others real
The following sources.list which I copied from
wiki.debian.org/SourcesList works perfectly for me
deb http://deb.debian.org/debian/ bookworm main non-free-firmware
contrib non-free
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
contrib non-free
deb
New sources.list file works perfectly
deb http://deb.debian.org/debian/ bookworm main non-free-firmware
contrib non-free
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
contrib non-free
deb http://deb.debian.org/debian/ bookworm-updates main
non-free-firmware contrib
1 - 100 of 10538 matches
Mail list logo
