Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

[Paul Leiber]

Am 25.01.2024 um 22:28 schrieb Paul Leiber:

Dear Debian user list members,

I am trying to run network related stuff (Samba, Zabbix) on a Raspberry 
Pi 4B in a virtualized environment using Debian Bookworm and Xen. I am 
running into reproducible complete system crashes/reboots due to a Xen 
watchdog triggering under certain, seemingly strange conditions (the 
number of VLANs involved seems to play a role, running tcpdump on 
certain interfaces prevents this issue, ...). If you are interested in 
the long version, you can find it here [1].


Some people on xen-devel pointed out to me two unhandled SMC calls in 
the boot logs which could be the root of the problem. I am now trying to 
find out where these calls come from to get closer to the root cause. 
The suspected calls are the following ones:


(XEN) d0v0 Unhandled SMC/HVC: 0x8450
(XEN) d0v0 Unhandled SMC/HVC: 0x8600ff01

These calls happen during the Dom0 boot process, so it's something from 
inside Linux and nothing Xen related, I've been told. The current 
working hypothesis is that the calls are trying to find some module not 
emulated by Xen and are therefore failing, leading to Linux waiting for 
the reply, and subsequently to the Xen watchdog triggering and rebooting.


 From what I could find out in ARM documentation, the unhandled SMC 
calls probably have the following purpose:


0x8450 = TRNG_VERSION, returns the implemented TRNG (True Random 
Number Generator) ABI version [2]
0x8600ff01 = Call UID Query for Vendor Specific Hypervisor Service, 
Returns a unique identifier of the service provider [3]


The more likely cause is the second call to the address 0x8600ff01.

Now I simply have no idea how to find out where in the Linux boot 
process these calls are made. I tried poking into the Linux sources a 
bit, and I couldn't find an exact match for these call addresses, so I 
assume these addresses are assembled from different parts. There are 
some matches for "0x8600" and for "ff01", but I couldn't identify if 
these matches are relevant.


I tried to find out if strace could help, but from what I understand, 
this is related to commands coming from userspace, so I am not sure that 
strace helps during the boot process.


I'd appreciate it if somebody more knowledgeable would point me in the 
right direction. If more information is needed, I can provide it.


Thanks,

Paul

[1] 
https://lists.xenproject.org/archives/html/xen-devel/2023-10/msg00796.html

[2] https://developer.arm.com/documentation/den0098/latest/
[3] 
https://documentation-service.arm.com/static/628b755ce3c4322a76af56de?token=




Hm, no reply so far. Is this maybe the wrong list? Should I post this 
rather somewhere else?


Paul

Re: Automatically installing GRUB on multiple drives

[tomas]

On Tue, Jan 30, 2024 at 09:47:35PM +0100, hw wrote:
> On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> > On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> > 
> > [...]
> > 
> > > Ok in that case, hardware RAID is a requirement for machines with UEFI
> > > BIOS since otherwise their reliability is insufficient.
> > 
> > The price you pay for hardware RAID is that you need a compatible controller
> > if you take your disks elsewhere (e.g. because your controller dies).
> 
> How often do you take the system disks from one machine to another,
> and how often will the RAID controller fail?
> 
> > With (Linux) software RAID you just need another Linux...
> 
> How's that supposed to help?  The machine still won't boot if the disk
> with the UEFI partition has failed.

We are talking about getting out of a catastrophic event. In such cases,
booting is the smallest of problems: use your favourite rescue medium
with a kernel which understands your RAID (and possibly other details
of your storage setup, file systems, LUKS, whatever).

[...]

> Maybe the problem needs to be fixed in all the UEFI BIOSs.  I don't
> think it'll happen, though.

This still makes sense if you want a hands-off recovery (think data
centre far away). Still you won't recover from a broken motherboard.

Cheers
-- 
t


signature.asc
Description: PGP signature

os-prober detects in wrong order and GRUB doesn't have enough options

[David Chmelik]

Earlier this or last year I tried to use Devuan to report os-prober 
detects in wrong order.  It may detect current OS partition first, but if 
you have more than 10, then it continues from 10, and (if this is all you 
have) goes to the last in the tens but then continues somewhere in single-
digit partitions, so then puts your OS all in wrong order in GRUB2, which 
should have more options about menu order like is easy to configure LILO  
exactly the way you want.  I have some entries I wrote myself, because 
even after a bug report over 10 years ago, os-prober didn't detect FreeBSD 
& NetBSD (reported) & DragonFlyBSD UNIXes, nor OpenSolaris/IllumOS UNIXes, 
nor does GRUB2 do some GNU/Linux right like SystemRescue and some obscure 
boot options some RedHat variants need or won't boot.  Seems like the bug 
maybe didn't get reported to the os-prober programmers.  Did it not get 
through or is there another way I could report this?

Re: How to insert symbols into emails

[David Wright]

On Wed 31 Jan 2024 at 02:46:22 (+), fxkl4...@protonmail.com wrote:
> On Tue, 30 Jan 2024, Franco Martelli wrote:
> > On 30/01/24 at 01:14, fxkl4...@protonmail.com wrote:
> >> so i defined my compose key
> >> in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
> >>   
> >> how do i type this
> >
> > I dunno if it's possible to type it using the COMPOSE key, however as
> > workaround you can install "gucharmap" if your desktop is GTK based or
> > "kcharselect" if your desktop is KDE, then search the character by name
> > (I-BEAM) then copy into the clipboard, finally create your own custom
> > ~/.XCompose and define your key sequence to associate i.e. 
> >   : "⌶" as explained in the Debian wiki:
> >
> > https://wiki.debian.org/XCompose
> 
> thanks
> that helps
> in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
>: "⌶"U2336 # ⊥ ⊤ APL FUNCTIONAL SYMBOL I-BEAM
> i can directly enter the symbol above using the U2336 value without a compose 
> key
> ctrl + shift + u and type 2336 and enter

I wasn't sure from you previous post why you wanted to type this
character. Is it something you often use, or was it just a random
example of an Compose definition involving codepoints rather than
more familiar letters and symbols?

I would assume that someone who was going to use a Compose sequence
to type the I-beam would already have their keyboard set up to make
APL symbols available with a shift level. AIUI they would likely
use the layout similar to the IBM 2741. On that keyboard, you could
therefore type Compose and shifted B and N; see:

  https://en.wikipedia.org/wiki/File:APL-keybd2.svg

For typing raw codepoints, your method will work in graphical
applications like FireFox and, presumably, Desktop environments
generally. In emacs, where I compose my emails, the sequence
is a little different:
  Esc x i n s Tab c Tab Return 2 3 3 6 Return
which stands for Meta-X insert-char (using Tab completion) followed
by the codepoint. Or one can type:
  Ctrl-X 8 Return 2 3 3 6 Return
or even:
  Ctrl-X 8 Return A P L Tab I - Tab
which uses Tab completion to type APL FUNCTIONAL SYMBOL I-BEAM,
the Sunday name of the symbol.

People who use vi may have different keystorkes. Horses for courses.

Cheers,
David.

Re: How to insert symbols into emails

[Max Nikulin]

On 30/01/2024 07:14, fxkl4...@protonmail.com wrote:

so i defined my compose key
in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
  
how do i type this


The 22a5 key presents in some apl and de layouts

grep -ri 22a5 /usr/share/X11/xkb/

You can either add another layout or to define custom compose sequence.

Re: Issues after upgrading 11 -> 12

[Charlie Gibbs]

On Tue, 30 Jan 2024 21:50:01 +0100
Michael =?utf-8?B?S2rDtnJsaW5n?= <2695bd53d...@ewoof.net> wrote:

> On 30 Jan 2024 10:14 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
>
>> VirtualBox, which I use heavily, has disappeard, so I'm going to
>> have to re-install some packages anyway.
>
> I'm pretty sure VirtualBox has not been shipped by Debian for quite a
> while because of its licensing status, so I guess you're relying on a
> third party package for that? (Probably Oracle's.) That's another
> thing that can easily cause complications during an upgrade, which is
> why the release notes recommend to disable third-party repositories
> before upgrading between releases and holding off on upgrading those
> packages until after the main system has been upgraded successfully;
> another detail that doesn't seem to be mentioned on the wiki page.

No worries, I'm used to installing VirtualBox afterwards.

> Semi-unrelated, but you might want to consider switching to KVM
> virtualization instead; it's supported by the stock kernel, making
> things easier. AQEMU is a fairly VirtualBox-like GUI front-end for it,
> and VMs can be converted (though especially if you're virtualizing
> Windows, I'm not sure how it takes to the changes in virtualized
> hardware). I switched from VirtualBox to KVM a while ago and haven't
> looked back.

I did some reading on KVM vs. VirtualBox.  For my application,
there didn't seem to be enough benefit to KVM to justify climbing
yet another learning curve.  As it turns out, re-installing
VirtualBox is now just a matter of going to Oracle's web site,
which contains one line you can add to /etc/apt/sources.list.
At this point you can just type
sudo apt install VirtualBox-7.0 (new version!)
Since its .vdi files (etc.) were already in $HOME, it came right up.
I told it to load guest extensions, and my Windows XP VM was up and
running again, complete with network and USB bridges.

>> Once I get this mess sorted out, I have one more machine to
>> upgrade.  I'll follow the release notes to the letter then,
>> and see whether I have better luck.
>
> For what it's worth, back when I upgraded my system from Bullseye to
> Bookworm (I think around the time 12.1 came out) closely following the
> release notes, the process was smooth, including Xfce and X11.

To be honest, most of my upgrades have gone smoothly too.  Maybe
I was becoming complacent and got careless - and if things go wrong,
they can go _very_ wrong.

For now, though, my laptop is happily running 12.4.  It occurs to
me that a full install from scratch isn't really that big a thing
if /home is intact.  I'll be occasionally finding a package that
isn't installed, but that's a matter of 30 seconds to install it;
it'll find its old configuration files in $HOME and all will be well.

Thanks, everyone, for your help.  Hopefully I'll remember some lessons
I can take to my next upgrade.

--
/~\  Charlie Gibbs  |  They don't understand Microsoft
\ /|  has stolen their car and parked
 X   I'm really at ac.dekanfrus |  a taxi in their driveway.
/ \  if you read it the right way.  |-- Mayayana

Re: How to insert symbols into emails

[fxkl47BF]

On Tue, 30 Jan 2024, Franco Martelli wrote:

> On 30/01/24 at 01:14, fxkl4...@protonmail.com wrote:
>> so i defined my compose key
>> in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
>>   
>> how do i type this
>>
>
> I dunno if it's possible to type it using the COMPOSE key, however as
> workaround you can install "gucharmap" if your desktop is GTK based or
> "kcharselect" if your desktop is KDE, then search the character by name
> (I-BEAM) then copy into the clipboard, finally create your own custom
> ~/.XCompose and define your key sequence to associate i.e. 
>   : "⌶" as explained in the Debian wiki:
>
> https://wiki.debian.org/XCompose

thanks
that helps
in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
   : "⌶"U2336 # ⊥ ⊤ APL FUNCTIONAL SYMBOL I-BEAM
i can directly enter the symbol above using the U2336 value without a compose 
key
ctrl + shift + u and type 2336 and enter

Re: Request about Boot Repair Disk

[Max Nikulin]

On 28/01/2024 01:03, fran...@libero.it wrote:
If I use SuperGrub cd by 
manual booting I can access to debian and boot it. So I used Boort 
Repair Disk 64 to try to repair, but it gave me a report advicing me to 
ask online with that report here under: (it is a long report)


I have no idea concerning these tools

sda1: 
File system: vfat

Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi


No efi/debian here despite it looks like an EFI System Partition


efibootmgr -v
No BootOrder is set; firmware will attempt recovery


It should be set and debian installer does it.


df480f092e56b632513b4616bdeade95 sda1/Boot/bootx64.efi


Either mangled output and really it is efi/boot/bootx64.efi, a boot file 
for removable device or some installer put files in a wrong folder. In 
the former case, some firmwares may give this option higher priority.



df480f092e56b632513b4616bdeade95 sda1/Microsoft/Boot/bootmgfw.efi
0a70ebdfe73694eb6188f70e81b47a79 sda1/Microsoft/Boot/bootmgr.efi



Can you help me to obtain to have Grub with the 2 OSes at booting?


Did you have grub-efi-amd64-signed and shim-signed installed? Looks like 
you installed Linux in legacy mode instead of UEFI one.

Re: How to insert symbols into emails

[Max Nikulin]

On 31/01/2024 03:36, Franco Martelli wrote:


It happens something strange, when I type "crocodile" into the search 
bar of "kcharselect" I get an empty square visualized, if I click to 
"Copy to clipboard" button and then paste to Thunderbird I can see the 
crocodile but not in "kcharselect" … does it depend on installed fonts? 
Any hints?


Certainly applications should have fallbacks to emoji fonts (depends on 
font rendering libraries) and you need to have fonts installed. Mozilla 
brings its own font. Do you have e.g. fonts-noto-color-emoji (dependency 
of fonts-recommended)?


Concerning the issue with Compose keys, it is a rather low level 
feature, so it should work for applications with proper support of 
Unicode. I have no issue with xterm. Diagnostics:


setxkbmap -print

and "xev"

Re: Issues after upgrading 11 -> 12; was: Is 12.4 safe, or should I wait for 12.5?

[Max Nikulin]

On 31/01/2024 01:14, Charlie Gibbs wrote:

[Sorry about the broken threads; I read this group on Usenet.]


I use a NNTP gateway as well.


That seems the obvious conclusion.  I was pretty gobsmacked, though,
when my system came up in a totally different graphical environment.


May it happen that you have GNOME and GDM3 installed before despite you 
usual session was xfce? Do you have xfce as an alternative to GNOME? You 
should still have dpkg and apt logs, so you may try to figure out what 
happened during upgrade.



The takeaway (for me, anyway) is that upgrading a system is a
complicated and hazardous process which requires a lot of study
before attempting it.


Do release notes fall into your "a lot" category? Skimming through 
package lists presented by apt may be tedious to some degree, but it 
allows to spot something unexpected.

Re: apt full-upgrade failed at marco-common package

[Miroslav Skoric]

On 1/30/24 1:43 PM, Michael Kjörling wrote:


https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#file-conflicts
should help.



Sure. Thanks!

Re: apt full-upgrade failed at marco-common package

[Miroslav Skoric]

On 1/30/24 1:40 PM, The Wanderer wrote:

/tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):

   trying to overwrite
'/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is
also in package gnome-themes-more 0.9.0.deb0.8


Where do you get 'gnome-themes-more' from? At least as far as I can tell
without more digging, it isn't in current stable or testing.

It *is* available on archive.debian.org and snapshot.debian.org, with
that version number, but based on the timestamps it doesn't seem to have
been updated since 2010.



Dunno ... probably it became orphaned after upgrading from some previous 
releases. I used apt-forktracer to get rid of some packages before 
upgrading to bullseye, but many packages were still listed there. I was 
cautious and did not want to remove all of those just like that ...




My first default would be to remove gnome-themes-more (possibly with
apt, possibly directly with dpkg), then try the '--fix-broken' step
again.

Assuming that works, I'd then follow it up by repeating the full-upgrade
step just to make sure, and then after that - if I really wanted
gnome-themes-more - try to reinstall it (preferably using an updated
package, if you can get your hands on one).



Thanks for advice. I tried to remove that package with apt at first, to 
no avail, but dpkg was successful. Then the '--fix-broken' step and the 
full-upgrade step performed without errors.


Misko

Re: apt full-upgrade failed at marco-common package

[Miroslav Skoric]

On 1/30/24 1:41 PM, Greg Wooledge wrote:

On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote:

Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
.[1mdpkg:.[0m error processing archive
/tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
  trying to overwrite
'/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also
in package gnome-themes-more 0.9.0.deb0.8


These two packages can't coexist, so you're going to have to pick
one to get rid of.

I did an "apt-cache show marco", and it's a window manager intended
to be used by MATE.

I did "apt-cache show gnome-themes-more" and it doesn't exist in
Debian 12 at all.  It must have been removed at some point, or else
it came from a third party source.  (That "*deb0.8" version string
looks a little odd to me, too.)

So... figure out which of these two packages you can live without,
get rid of it, and then retry the upgrade.

Two packages both trying to supply the same file, without a Conflicts:
line or something equivalent, should be considered a bug, if they're
both Debian packages.  If one of them's third-party, then of course
all bets are off.




Thank you. I removed gnome-themes-more as I mostly use MATE. (Did not 
check whether Gnome would suffer by any means :-)

Re: Possible cifs stuck in stable kernel (linux-image-6.1.0-17-amd64)

[Xiyue Deng]

Hi Sven,

Sven Joachim  writes:

> On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
>
>> (Please keep me in CC as I'm not subscribed to the users ML.)
>>
>> Hi,
>>
>> TL;DR I've been experience stuck file system operations on cifs mount on
>> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
>> like to see if other people are seeing similar issue before actually
>> filing a bug.
>
> It has been seen by other people: https://bugs.debian.org/1060005.
>
> The Linux kernel 6.1.73 contains a fix, but I don't know when it will
> reach the archive.
>
> Cheers,
>Sven

Looks like the exact issue.  Thanks for confirming, Sven!  Eagerly
waiting for the release of 6.1.73.

-- 
Xiyue Deng

Re: Can't list root directory

[hw]

On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
> I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability 
> to see the root directory even when I am logged in as root (su -).
> 
> This has been happening intermittently for several months. I initially 
> thought it might be related to failing NVME drive that was part of a 
> RAID1 array that is mounted as "/" but I replaced the device and the 
> problem is still happening.
> [...]

What happens when you put the device you replaced back?

Re: Automatically installing GRUB on multiple drives

[hw]

On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> Hi,
> 
> On Mon, Jan 29, 2024 at 05:28:56PM +0100, hw wrote:
> > On Sun, 2024-01-28 at 21:55 +, Andy Smith wrote:
> > > On Sun, Jan 28, 2024 at 09:09:17PM +0100, hw wrote:
> > > > On Sun, 2024-01-28 at 17:32 +, Andy Smith wrote:
> > > > > If someone DOES want a script option that solves that problem, a
> > > > > couple of actual working scripts were supplied in the link I gave to
> > > > > the earlier thread:
> > > > > 
> > > > > https://lists.debian.org/debian-user/2020/11/msg00455.html
> > > > > https://lists.debian.org/debian-user/2020/11/msg00458.html
> > > > 
> > > > Huh?  Isn't it simpler to use mdraid RAID1 to keep the UEFI partitions
> > > > in sync without extra scripts needed?
> > > 
> > > Could you read the first link above.
> > 
> > I did, and it doesn't explain why you would need a bunch of scripts.
> 
> I think you should read it again until you find the part where it
> clearly states what the problem is with using MD RAID for this. If
> you still can't find that part, there is likely to be a problem I
> can't assist with.

That there may be a problem doesn't automatically mean that you need a
bunch of scripts.

Re: Automatically installing GRUB on multiple drives

[hw]

On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> 
> [...]
> 
> > Ok in that case, hardware RAID is a requirement for machines with UEFI
> > BIOS since otherwise their reliability is insufficient.
> 
> The price you pay for hardware RAID is that you need a compatible controller
> if you take your disks elsewhere (e.g. because your controller dies).

How often do you take the system disks from one machine to another,
and how often will the RAID controller fail?

> With (Linux) software RAID you just need another Linux...

How's that supposed to help?  The machine still won't boot if the disk
with the UEFI partition has failed.  Look at Linux installers, like
the Debian installer or the Fedora installer.  Last time I used
either, none of them would automatically create or at least require
redundant UEFI partitions --- at least for instances when software
RAID is used --- to make it possible to boot when a disk has failed.
It's a very bad oversight.

Maybe the problem needs to be fixed in all the UEFI BIOSs.  I don't
think it'll happen, though.

Re: Issues after upgrading 11 -> 12

[Michael Kjörling]

On 30 Jan 2024 10:14 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
> [Sorry about the broken threads; I read this group on Usenet.]

At least you kept the Subject line intact and provided solid quotes,
making manual linking of threads manageable.


> VirtualBox, which I use heavily, has disappeard, so I'm going to
> have to re-install some packages anyway.

I'm pretty sure VirtualBox has not been shipped by Debian for quite a
while because of its licensing status, so I guess you're relying on a
third party package for that? (Probably Oracle's.) That's another
thing that can easily cause complications during an upgrade, which is
why the release notes recommend to disable third-party repositories
before upgrading between releases and holding off on upgrading those
packages until after the main system has been upgraded successfully;
another detail that doesn't seem to be mentioned on the wiki page.

Semi-unrelated, but you might want to consider switching to KVM
virtualization instead; it's supported by the stock kernel, making
things easier. AQEMU is a fairly VirtualBox-like GUI front-end for it,
and VMs can be converted (though especially if you're virtualizing
Windows, I'm not sure how it takes to the changes in virtualized
hardware). I switched from VirtualBox to KVM a while ago and haven't
looked back.


> The takeaway (for me, anyway) is that upgrading a system is a
> complicated and hazardous process which requires a lot of study
> before attempting it.  Often it goes smoothly, but when it
> doesn't I"m in for a world of hurt.  So it goes.

I don't think I would go that far. My experience is that generally
Debian upgrades are very smooth; what can cause complications is if
you're not running a pure Debian system, especially if you have
out-of-tree packages installed which integrate into the kernel
(graphics drivers, virtualization, file system support, ...). Not
closely following the upgrade instructions in the release notes is
then likely to further compound any issues.


> Once I get this mess sorted out, I have one more machine to
> upgrade.  I'll follow the release notes to the letter then,
> and see whether I have better luck.

For what it's worth, back when I upgraded my system from Bullseye to
Bookworm (I think around the time 12.1 came out) closely following the
release notes, the process was smooth, including Xfce and X11.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: How to insert symbols into emails

[Franco Martelli]

On 29/01/24 at 23:31, Charles Curley wrote:

On Mon, 29 Jan 2024 22:02:20 +0100
Franco Martelli  wrote:


I read that for custom sequence I've to create a ~/.XCompose file,
but where can I find the character to map i.e. Greek letters: "α" "β"
"γ" ?


Try the gucharmap package. You look a character up by name, and copy it
into place. E.g. crocodile, .


It happens something strange, when I type "crocodile" into the search 
bar of "kcharselect" I get an empty square visualized, if I click to 
"Copy to clipboard" button and then paste to Thunderbird I can see the 
crocodile but not in "kcharselect" … does it depend on installed fonts? 
Any hints?


Thanks again, kind regards.

--
Franco Martelli

Re: Automatically installing GRUB on multiple drives

[Nicolas George]

hw (12024-01-30):
> Yes, and how much effort and how reliable is doing that?

Very little effort and probably more reliable than hardware RAID with
closed-source hardware.

-- 
  Nicolas George

Re: Automatically installing GRUB on multiple drives

[hw]

On Mon, 2024-01-29 at 18:00 +0100, Nicolas George wrote:
> hw (12024-01-29):
> > Ok in that case, hardware RAID is a requirement for machines with UEFI
> 
> That is not true, you can still put the RAID in a partition and keep the
> boot partitions in sync manually or with scripts.

Yes, and how much effort and how reliable is doing that?

I didn't say it can't be done.

Re: Possible cifs stuck in stable kernel (linux-image-6.1.0-17-amd64)

[Sven Joachim]

On 2024-01-30 10:52 -0800, Xiyue Deng wrote:

> (Please keep me in CC as I'm not subscribed to the users ML.)
>
> Hi,
>
> TL;DR I've been experience stuck file system operations on cifs mount on
> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
> like to see if other people are seeing similar issue before actually
> filing a bug.

It has been seen by other people: https://bugs.debian.org/1060005.

The Linux kernel 6.1.73 contains a fix, but I don't know when it will
reach the archive.

Cheers,
   Sven

Re: How to insert symbols into emails

[Franco Martelli]

On 30/01/24 at 01:14, fxkl4...@protonmail.com wrote:

so i defined my compose key
in "/usr/share/X11/locale/en_US.UTF-8/Compose" file i see a definition
  
how do i type this



I dunno if it's possible to type it using the COMPOSE key, however as 
workaround you can install "gucharmap" if your desktop is GTK based or 
"kcharselect" if your desktop is KDE, then search the character by name 
(I-BEAM) then copy into the clipboard, finally create your own custom 
~/.XCompose and define your key sequence to associate i.e.  
  : "⌶" as explained in the Debian wiki:


https://wiki.debian.org/XCompose

Cheers,
--
Franco Martelli

Re: Issues after upgrading 11 -> 12; was: Is 12.4 safe, or should I wait for 12.5?

[Charlie Gibbs]

[Sorry about the broken threads; I read this group on Usenet.]

On Tue, 30 Jan 2024 08:50:01 +0100
Michael =?utf-8?B?S2rDtnJsaW5n?= <2695bd53d...@ewoof.net> wrote:

> On 29 Jan 2024 19:54 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
>
>> Today I took a thorough backup of my laptop and dove in, using the
>> instructions at https://wiki.debian.org/DebianUpgrade as a guide.
>
> Did you actually follow _that_ page, or did you read and follow the
> _release notes_ as it says near the top of that page?

Mea culpa.  I used the wiki.

> As a rule the release notes for a release should be considered the
> authoritative truth about upgrading to any given release from the
> immediately preceding release. (Skipping releases is not supported and
> strongly discouraged.) There are also meaningful differences in system
> setup between 11 and 12, not least non-free-firmware (which, were it
> just that, would be easy enough to add after the fact).

Noted.  Hopefully I'll remember to go there first the next time I do
an upgrade, rather than following the first page that comes up in my
search engine.

> A plain Debian release upgrade should not switch your desktop
> environment on its own, and last I looked Xfce wasn't yet compatible
> with Wayland, so although I haven't looked in detail, it seems likely
> that your issues are related to something which you did or did not do
> during the upgrade process.

That seems the obvious conclusion.  I was pretty gobsmacked, though,
when my system came up in a totally different graphical environment.
Even though I've had strange things happen in other upgrades, this one
takes it to a whole new level.  I'm obviously playing with dynamite.

> Do you have a "script" transcript of the upgrade session (as the
> release notes also strongly recommend [1] in case there are problems)?
>
> [1]: 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session


Alas, no.  Again, something to remember for next time.

Although just about everything seems to be there, I feel uneasy
enough about the whole thing that I think I'll just re-format the
root partition (while leaving the separate /home partition intact)
and install Bookworm from scratch.  VirtualBox, which I use heavily,
has disappeard, so I'm going to have to re-install some packages
anyway.  This isn't the first time I've had to do this; when
I tried to upgrade this same laptop from (IIRC) Stretch to Buster,
I was left with an unbootable machine.

The takeaway (for me, anyway) is that upgrading a system is a
complicated and hazardous process which requires a lot of study
before attempting it.  Often it goes smoothly, but when it
doesn't I"m in for a world of hurt.  So it goes.

Once I get this mess sorted out, I have one more machine to
upgrade.  I'll follow the release notes to the letter then,
and see whether I have better luck.

--
/~\  Charlie Gibbs  |  Life is perverse.
\ /|  It can be beautiful -
 X   I'm really at ac.dekanfrus |  but it won't.
/ \  if you read it the right way.  |-- Lily Tomlin

Re: How to insert symbols into emails

[Greg Wooledge]

On Tue, Jan 30, 2024 at 11:00:47AM -0800, Van Snyder wrote:
> I configured several different Compose keys, for example Right-Alt, one
> at a time, using the KDE settings -> input devices -> keyboard ->
> advanced widget.
> 
> If I use them in XTerm, for example Compose-'-e to try to produce é, it
> locks up.

I don't use any desktop environment, just fvwm.  Compose ' e and
Compose e ' both work for me in xterm.

I don't have multiple Compose keys, though, nor do I understand how KDE's
method differs from xmodmap (which is what I use).

Possible cifs stuck in stable kernel (linux-image-6.1.0-17-amd64)

[Xiyue Deng]

(Please keep me in CC as I'm not subscribed to the users ML.)

Hi,

TL;DR I've been experience stuck file system operations on cifs mount on
latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
like to see if other people are seeing similar issue before actually
filing a bug.

Longer story: recently after upgrading stable kernel version to the
latest one, there is a chance that when operating files on a cifs mount
(e.g. copying files from local FS to a cifs mount, renaming a file on a
cifs mount, moving files on cifs mount, etc.) using Nautilus it will
stuck: Nautilus will show that there are operation ongoing which will
never end.  You can cancel the operation which seems to work, but if you
close the Nautilus window it will send a notification saying that there
are operations still ongoing.  Also when this happens, any operation on
the file or folder you are copying to will stuck in both Nautilus or
through command line.  Initially I thought this was a Nautilus issue,
but then I switched to KDE and the same happened to Dolphin as well.  As
I don't remember seeing this issue with some older version of the stable
kernel (not quite sure when), I tried to switch to the backport kernel
(linux-image-6.5.0-0.deb12.4-amd64, 6.5.10-1~bpo12+1) last week, and I
haven't seen this issue since.  So it would seem to me that this issue
is somewhat related to the kernel.

So here I come to see whether anyone else is experiencing similar
issues before I actually file a bug in case it is actually something
only happening to me.  Any experience, tips, or suggestions are welcome.

TIA.
--
Xiyue Deng

Re: How to insert symbols into emails

[Van Snyder]

On Tue, 2024-01-30 at 10:21 +0700, Max Nikulin wrote:
> > > > Those symbols are very nice, which tool have you used to insert
> > > > them?
> > > 
> > > Easy. I configured my CAPSLOCK key (which is useless IMO) to bemy
> > > X compose key. So entering COMPOSE-4-5 does ⅘, and COMPOSE-<-
> > > 3does ♥. You can even define your own compose seqs, like I did
> > > with♀ (COMPOSE-o-+) and others.
> > 
> > This is documented at  by the
> > way.

I configured several different Compose keys, for example Right-Alt, one
at a time, using the KDE settings -> input devices -> keyboard ->
advanced widget.

If I use them in XTerm, for example Compose-'-e to try to produce é, it
locks up. If I use them in nedit, I get a two-character sequence. If I
use them in Evolution or Firefox, it works fine.
It also works in Konsole, but my fingers know XTerm and so does my
.Xdefaults.

Does this only work in programs that work in UTF-8 instead of ASCII?

Re: How to insert symbols into emails

[Franco Martelli]

On 29/01/24 at 23:31, Charles Curley wrote:

On Mon, 29 Jan 2024 22:02:20 +0100
Franco Martelli  wrote:


I read that for custom sequence I've to create a ~/.XCompose file,
but where can I find the character to map i.e. Greek letters: "α" "β"
"γ" ?


Try the gucharmap package. You look a character up by name, and copy it
into place. E.g. crocodile, .


Thanks, as I'm on KDE desktop I've installed "kcharselect" it does the 
same thing. It was a bit hard to find it, first I've looked for "Similar 
packages" section in the "gucharmap" web page ¹  but I didn't find 
nothing related to QT applications then I performed an "apt search kde 
char" and I found it.


There is a thing that it hurts me a little, if you look at the section 
"Similar package" in the "kcharselect" web page ²  you'll find 
"gucharmap" but this is *not* true vice-versa.


Which guys takes care of section "Similar packages" into packages web 
pages? I think "kcharselect" must be added to "Similar packages" section 
of "gucharmap"!


Cheers,

¹ https://packages.debian.org/bookworm/gucharmap
² https://packages.debian.org/bookworm/kcharselect
--
Franco Martelli

Re: listar paquetes desinstalados con configuración residual

[Gonzalo Rivero]

El 30/1/24 a las 12:30, Alfonso Camacho escribió:

Saludos:

- Mensaje original -

De: "Gonzalo Rivero" 
Para: "debian-user-spanish" 
Enviados: Martes, 30 de Enero 2024 16:15:36
Asunto: listar paquetes desinstalados con configuración residual
gu mornin todos,

lo que quiero averiguar es como debería buscar con apt los paquetes que
fueron desinstalados con

apt-get remove 

así puedo sacarlos con apt-get --purge remove 

normalmente hacía esto con synaptic, hacía click con el mouse y sabía
que paquetes me habían dejado "basura" en el disco, pero esta
instalación no estoy usando nada gráfico y no se me ocurre como hacer el
apt-cache search

# apt purge $(dpkg --get-selections | grep deinstall | awk '{ print $1 }')



genial, no se me había ocurrido bajar a dpkg, pero mostró (y purgó) el 
paquete que acababa de desinstalar para probar.



Gracias

Re: listar paquetes desinstalados con configuración residual

[Alfonso Camacho]

Saludos:

- Mensaje original -
> De: "Gonzalo Rivero" 
> Para: "debian-user-spanish" 
> Enviados: Martes, 30 de Enero 2024 16:15:36
> Asunto: listar paquetes desinstalados con configuración residual

> gu mornin todos,
> 
> lo que quiero averiguar es como debería buscar con apt los paquetes que
> fueron desinstalados con
> 
> apt-get remove 
> 
> así puedo sacarlos con apt-get --purge remove 
> 
> normalmente hacía esto con synaptic, hacía click con el mouse y sabía
> que paquetes me habían dejado "basura" en el disco, pero esta
> instalación no estoy usando nada gráfico y no se me ocurre como hacer el
> apt-cache search

# apt purge $(dpkg --get-selections | grep deinstall | awk '{ print $1 }')




-- 
Alfonso 

Re: Is 12.4 safe, or should I wait for 12.5?

[Anssi Saari]

Charlie Gibbs  writes:

> I followed the update steps exactly, accepting all defaults.

If that were true, and you followed the steps in *the release notes* you
could for example compare what packages you had before and after. But I
guess you mean you followed the extremely minimal steps in the wiki?

> Well, there was one thing: since I was already at a root
> prompt after doing my backup, I just typed "apt-get "
> rather than prefixing the commands with "sudo".  Could this
> cause such a drastic change?

I guess it's just one of those things nobody wants to cover in a minimal
wiki page. You can't say "if you're root, then don't need to type sudo"
because that leads to confusion about root. Based on some dev's
complaint that people don't understand "be root".

> I don't understand it - when I upgraded my main machine,
> everything went smooth as butter, and my desktop and all
> applications were left exactly as is.  But on my laptop,
> the only thing that appears intact is the contents of /home.
> Can anyone suggest what happened and how to fix it?

Did anything actually happen, other than you logged in to a Gnome
Wayland session instead of an XFCE X11 session? Or if you login
automatically, maybe the default changed? So log out, select a session
you prefer and log in again?

listar paquetes desinstalados con configuración residual

[Gonzalo Rivero]

gu mornin todos,

lo que quiero averiguar es como debería buscar con apt los paquetes que 
fueron desinstalados con


apt-get remove 

así puedo sacarlos con apt-get --purge remove 

normalmente hacía esto con synaptic, hacía click con el mouse y sabía 
que paquetes me habían dejado "basura" en el disco, pero esta 
instalación no estoy usando nada gráfico y no se me ocurre como hacer el 
apt-cache search

Re: Stop packagekitd from downloading updates

[Michael Biebl]

In case of GNOME, you might try the following

gsettings set org.gnome.software download-updates false

(gnome-software used packagekitd internally)


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: apt full-upgrade failed at marco-common package

[Michael Kjörling]

On 30 Jan 2024 13:19 +0100, from sko...@uns.ac.rs (Miroslav Skoric):
> Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ...
> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
> .[1mdpkg:.[0m error processing archive
> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
>  trying to overwrite
> '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also
> in package gnome-themes-more 0.9.0.deb0.8
> Errors were encountered while processing:
>  /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb

https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#file-conflicts
should help.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: apt full-upgrade failed at marco-common package

[Greg Wooledge]

On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote:
> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
> .[1mdpkg:.[0m error processing archive
> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
>  trying to overwrite
> '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also
> in package gnome-themes-more 0.9.0.deb0.8

These two packages can't coexist, so you're going to have to pick
one to get rid of.

I did an "apt-cache show marco", and it's a window manager intended
to be used by MATE.

I did "apt-cache show gnome-themes-more" and it doesn't exist in
Debian 12 at all.  It must have been removed at some point, or else
it came from a third party source.  (That "*deb0.8" version string
looks a little odd to me, too.)

So... figure out which of these two packages you can live without,
get rid of it, and then retry the upgrade.

Two packages both trying to supply the same file, without a Conflicts:
line or something equivalent, should be considered a bug, if they're
both Debian packages.  If one of them's third-party, then of course
all bets are off.

Re: apt full-upgrade failed at marco-common package

[The Wanderer]

On 2024-01-30 at 07:19, Miroslav Skoric wrote:

> Hi,
> 
> I [partially] upgraded buster to bullseye according to official "Release 
> Notes for Debian 11 (bullseye), 32-bit PC" (October 4, 2023). I did it 
> in two sessions as suggested:
> 
> "4.4.4 Minimal system upgrade" (# apt upgrade --without-new-pkgs). That 
> part performed without any issue, and cat /etc/debian_version reported 
> 11.8 (previously it was 10.x).
> 
> "4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until 
> some 20% or so, and then failed when handled marco-common package. Here 
> are the few last lines of that session:
> 
> ...
> Preparing to unpack .../6-mate-settings-daemon-common_1.24.1-1_all.deb ...
> Unpacking mate-settings-daemon-common (1.24.1-1) over (1.20.4-1) ...
> Preparing to unpack .../7-marco_1.24.1-3_i386.deb ...
> Unpacking marco (1.24.1-3) over (1.20.3-1) ...
> Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ...
> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
> .[1mdpkg:.[0m error processing archive 
> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
>   trying to overwrite 
> '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is 
> also in package gnome-themes-more 0.9.0.deb0.8

Where do you get 'gnome-themes-more' from? At least as far as I can tell
without more digging, it isn't in current stable or testing.

It *is* available on archive.debian.org and snapshot.debian.org, with
that version number, but based on the timestamps it doesn't seem to have
been updated since 2010.

> Errors were encountered while processing:
>   /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb
> 
> 
> A repeated # apt full-upgrade returned a list of unmet dependencies, 
> including this one:
> 
> marco : Depends: marco-common (= 1.24.1-3) but 1.20.3-1 is installed
> 
> At the end of the list it suggested: Try 'apt --fix-broken install' with 
> no packages (or specify a solution). I tried it and it seemed as if it 
> tried to process again the above lines (unpacking, preparing), to no avail.
> 
> What can I try to resolve that? After system reboot, I am able to reach 
> the rescue mode as root and type commands. (Green 'OK' follow all parts 
> of boot. GUI, startx fail. Shutdown, poweroff run properly.)

My first default would be to remove gnome-themes-more (possibly with
apt, possibly directly with dpkg), then try the '--fix-broken' step
again.

Assuming that works, I'd then follow it up by repeating the full-upgrade
step just to make sure, and then after that - if I really wanted
gnome-themes-more - try to reinstall it (preferably using an updated
package, if you can get your hands on one).

I suspect that files have been moved between packages since that version
was released, and (some of) the files which were previously in
gnome-themes-more are now in marco-common.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

apt full-upgrade failed at marco-common package

[Miroslav Skoric]

Hi,

I [partially] upgraded buster to bullseye according to official "Release 
Notes for Debian 11 (bullseye), 32-bit PC" (October 4, 2023). I did it 
in two sessions as suggested:


"4.4.4 Minimal system upgrade" (# apt upgrade --without-new-pkgs). That 
part performed without any issue, and cat /etc/debian_version reported 
11.8 (previously it was 10.x).


"4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until 
some 20% or so, and then failed when handled marco-common package. Here 
are the few last lines of that session:


...
Preparing to unpack .../6-mate-settings-daemon-common_1.24.1-1_all.deb ...
Unpacking mate-settings-daemon-common (1.24.1-1) over (1.20.4-1) ...
Preparing to unpack .../7-marco_1.24.1-3_i386.deb ...
Unpacking marco (1.24.1-3) over (1.20.3-1) ...
Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ...
Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
.[1mdpkg:.[0m error processing archive 
/tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
 trying to overwrite 
'/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is 
also in package gnome-themes-more 0.9.0.deb0.8

Errors were encountered while processing:
 /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb


A repeated # apt full-upgrade returned a list of unmet dependencies, 
including this one:


marco : Depends: marco-common (= 1.24.1-3) but 1.20.3-1 is installed

At the end of the list it suggested: Try 'apt --fix-broken install' with 
no packages (or specify a solution). I tried it and it seemed as if it 
tried to process again the above lines (unpacking, preparing), to no avail.


What can I try to resolve that? After system reboot, I am able to reach 
the rescue mode as root and type commands. (Green 'OK' follow all parts 
of boot. GUI, startx fail. Shutdown, poweroff run properly.)


Thank you.

Misko

Re: Q: Gnome network odd

[황병희]

Hellow David,

On Mon, 2024-01-29 at 23:49 -0600, David Wright wrote:
> On Tue 30 Jan 2024 at 10:13:34 (+0900), Byunghee HWANG (황병희) wrote:
> > On Mon, 2024-01-29 at 09:35 -0600, David Wright wrote:
> > > On Mon 29 Jan 2024 at 21:36:39 (+0900), Byunghee HWANG (황병희)
> > > wrote:
> > > > 
> > > > For months ago, i did upgrade Debian 12 to Debian Sid. At that
> > > > time,
> > > > Gnome network icon was odd. That appered as like question mark.
> > > > So
> > > > after i googling, i removed some file in /etc. Then OK! The
> > > > Internet is
> > > > started. (i did googling with smartphone).
> > > > 
> > > > 
> > > >  soyeomul@thinkpad-e495:/etc/network$ LANG=C.UTF-8 ls -l
> > > > total 24
> > > > drwxr-xr-x 2 root root 4096 Jan  7 18:51 if-down.d
> > > > drwxr-xr-x 2 root root 4096 Jan  8 19:45 if-post-down.d
> > > > drwxr-xr-x 2 root root 4096 Jan  8 19:45 if-pre-up.d
> > > > drwxr-xr-x 2 root root 4096 Jan  7 18:51 if-up.d
> > > > drwxr-xr-x 2 root root 4096 Jan 24  2023 interfaces.d
> > > > -rw-r--r-- 1 root root  433 Oct  4 17:23 interfaces.orig
> > > > soyeomul@thinkpad-e495:/etc/network$ 
> > > > 
> > > > 
> > > > As you see above, i removed /etc/network/interfaces file.
> > > > Anyway
> > > > now it
> > > > works everything! No problem!
> > > > 
> > > > Is this a bug? Or am i wrong?
> > > > 
> > > > Ref: 
> > > > https://unix.stackexchange.com/questions/457856/how-to-fix-debians-networkmanager-with-question-mark-even-though-network-is-wor
> > > 
> > > AIUI there are several network configuration tools that defer to
> > > configurations that are set up in /e/n/i, which would be handled
> > > by ifupdown preferentially. Generally, removing /e/n/i
> > > completely,
> > > as you have, is fine. One side effect is that any entries in
> > > /e/n/interfaces.d/ will also be disabled.
> > > 
> > > The only machine on which I keep /e/n/i and ifupdown is my
> > > travelling
> > > laptop, for tethering with my phone:
> > > 
> > >   allow-hotplug usb0
> > > 
> > >   iface usb0 inet dhcp
> > > 
> > > BTW I don't know why you're running sid, but it's generally
> > > expected
> > > that sid users would be familiar with stuff like this,
> > > particularly
> > > as your question is already answered in the reference.
> > 
> > In frankly, i don't know interface things and network tools.
> > Whenever I
> > use the default value, just as it is. So still i don't understand
> > your
> > reply message in technically.
> 
> You have Gnome installed, which implies you configure the network
> with
> something like NetworkManager.
> 
> You /had/ a file called /etc/network/interfaces, which implied you
> were
> configuring the network with ifupdown.
> 
> If you try to configure the same /interface/ (which could be called
> something like eth0) with both NetworkManager and ifupdown, then
> NetworkManager should back off and let ifupdown do the configuring.
> 
> I can't tell you whether that makes Gnome display a question mark,
> but
> others might know. (I don't use Gnome, NetworkManager, or ifupdown.)

You see here:
https://gitlab.com/soyeomul/stuff/-/commit/6796b4fcd3fb3b0e5228b20ecd3209d7d1de0af4
I reproduced the odd screenshot -- question mark. I restored the file
/e/n/i as you know.


> 
> When you renamed the file to /etc/network/interfaces.orig, then
> ifupdown can no longer read it, nor take priority over
> NetworkManager,
> and NetworkManager should be happy to configure the interface itself.
> The question mark should go away. (Do you get a happy face displayed
> instead, or is NetworkManager more boring than that?)
> 
> I would tend to think that:
> 
> . The debian-installer installs ifupdown by default when you don't
>   install a Desktop Manager like Gnome,
> 
> . The debian-installer installs NetworkManager by default if you do
>   install a Desktop Manager like Gnome,
> 
> . It shouldn't do both.
> 
> But, if you upgrade an ifupdown-system and add NetworkManager in
> whatever way, then it's up to you to remove/hide any ifupdown
> configuration that you want NetworkManager to perform. That's
> probably what you did by renaming the file.
> 

Thank you for your kind and detailed analysis, David! I will refer to
your analysis the next time i encounter a similar difficulty.


Sincerely, Byunghee

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

Re: cli64 CPU segfaults

[Adam Weremczuk]

Thanks everyone for useful feedback :)

On 29/01/2024 21:05, Gremlin wrote:

On 1/29/24 14:35, Michael Kjörling wrote:
On 29 Jan 2024 19:20 +, from ad...@matrixscience.com (Adam 
Weremczuk):

I have 2 bare metal Debian 12.4 servers with fairly new Intel CPUs and
plenty of memory.

On both, dmesg continuously reports:

(...)
[Mon Jan 29 12:13:00 2024] cli64[1666090]: segfault at 0 ip 
0040dd3b
sp 7ffc2bfba630 error 4 in cli64[40+18a000] likely on CPU 41 
(core

17, socket 0)
(...)


What's cli64? A package search comes up empty for me.

https://packages.debian.org/search?searchon=contents=cli64=exactfilename=bookworm=any 






https://www.advancedclustering.com/act_kb/what-is-cli64/