Using strace, the freeze corresponds to a poll command for fd33, which
appears to be a docker function. In this case the test file is an
AppImage, orcaslicer-2.3.0, but any AppImage will work for this. I have
quite a few, as its the only way to get the latest and greatest given
debians penchant for dragging feet about projects that s/b debs but for
some reason don't fit the debian POV.

But while there is a call to docker on an ipv4 address starting with 172
in the trace output, I don't recall ever setting up docker on this
system.  So who can help me check to see if its missing and this freeze
is the timeout while its waiting for docker to reply to the poll?


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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:

Hi Gene,

I'm probably going to regret this - let's see if I can help you
fault-find :)

Questions:

1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a on this machine,
please.

2. Do you actually *have* orcaslicer 2.3.0 installed - or is it left
over from some previous attempt at installing something you later
removed?

3. What does the command

ip a

show on your system?

4. Do you have docker (or podman or buldah) on your system?

5. Can you *show* us the output from strace, please - capture a few
lines.

None of us are mind readers - none of us are sat looking over your
shoulder. Without something to go on, every message from you about
problems involves significant guesswork. Share information, please,
about what you are *actually* seeing on screen in front of you and
make it easier for the rest of us. The Sherlock Holmes approach is
fun the first few times, but you're making it hard for us to eliminate
the impossible and work on the problems in hand.

[If this helps, imagine this was a problem at a TV station that someone
you didn't know well was reporting to you over the phone. You'd be asking questions and noting down the responses to be able to narrow down on what
the issue was. You're expecting all of us to *know* the answers from zero information given: it's frustrating as anything.]

Using strace, the freeze corresponds to a poll command for fd33, which appears to be a docker function. In this case the test file is an AppImage, orcaslicer-2.3.0, but any AppImage will work for this. I have quite a few,
as its the only way to get the latest and greatest given debians penchant
for dragging feet about projects that s/b debs but for some reason don't fit the debian POV.

But while there is a call to docker on an ipv4 address starting with 172 in the trace output, I don't recall ever setting up docker on this system.  So who can help me check to see if its missing and this freeze is the timeout while its waiting for docker to reply to the poll?

Cheers, Gene Heskett, CET.

Thanks, all the best, as ever,

Andy
(amacater@debian.org)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 4/13/25 14:07, Andrew M.A. Cater wrote:

On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:

Hi Gene,

I'm probably going to regret this - let's see if I can help you
fault-find :)

Questions:

1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a on this machine, please.

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"

BUG_REPORT_URL="https://bugs.debian.org/"

Linux coyote 6.1.0-33-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.133-1
(2025-04-10) x86_64 GNU/Linux

2. Do you actually *have* orcaslicer 2.3.0 installed - or is it left
over from some previous attempt at installing something you later
removed?

All of these AppImages run just fine, once the freeze has timed out. Orcaslicer, PrusaSlicer, OpenSCAD, everything runs normally except for
dim to invisible for /some/ of the teeny little 8x8 menu icons.

3. What does the command

ip a

gene@coyote:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UP group default qlen 1000
    link/ether 40:b0:76:5b:11:3c brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 192.168.71.3/24 brd 192.168.71.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::42b0:76ff:fe5b:113c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default

    link/ether 02:42:94:fc:f4:45 brd ff:ff:ff:ff:ff:ff

gene@coyote:~$ ip r
default via 192.168.71.1 dev eno1 proto static metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.71.0/24 dev eno1 proto kernel scope link src 192.168.71.3 metric
100 net 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

show on your system?

4. Do you have docker (or podman or buldah) on your system?

5. Can you *show* us the output from strace, please - capture a few
lines.

the possibly interesting part involves docker:

here is all of >strace.stderr

[2025-04-13 16:24:12.508497] [0x00007efc1da0e540] [trace]  Initializing StaticPrintConfigs
add font of HarmonyOS_Sans_SC_Bold returns 1
add font of HarmonyOS_Sans_SC_Regular returns 1
add font of NanumGothic-Regular returns 1
add font of NanumGothic-Bold returns 1
loading network module at /home/gene/.config/OrcaSlicer/plugins/libbambu_networking.so
after dlopen, network_module is 0x560ef8e3ede0
1. lo    : 127.0.0.1
2. eno1  : 192.168.71.3
3. docker0: 172.17.0.1

This is probably 20k lines into the strace.comb  output by running "OrcaSlicer  &>strace.comb":

ioctl(65, SIOCGIFCONF, {ifc_len=2048 => 120 /* 3 * sizeof(struct ifreq)
*/, ifc_buf=[{ifr_name="lo", ifr_addr={sa_family=AF_INET,
sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}}, {ifr_name="eno1", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.71.3")}}, {ifr_name="docker0", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("172.17.0.1")}}]}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="lo",
ifr_netmask={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("255.0.0.0")}}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="eno1",
ifr_netmask={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("255.255.255.0")}})

I should advise since its Sunday I just updated with synaptic to a new
kernel and rebooted then installed a couple more pieces of docker so the
error output isn't exactly the same.

None of us are mind readers - none of us are sat looking over your
shoulder. Without something to go on, every message from you about
problems involves significant guesswork. Share information, please,
about what you are *actually* seeing on screen in front of you and
make it easier for the rest of us. The Sherlock Holmes approach is
fun the first few times, but you're making it hard for us to eliminate
the impossible and work on the problems in hand.

[If this helps, imagine this was a problem at a TV station that someone
you didn't know well was reporting to you over the phone. You'd be asking questions and noting down the responses to be able to narrow down on what
the issue was. You're expecting all of us to *know* the answers from zero information given: it's frustrating as anything.]

Chuckle, BTDT for nearly half a century Andy, I'm quite used to using
somebody else's hands over the phone. Probably, as you have seen, not so
good letting somebody else run my hands.

Using strace, the freeze corresponds to a poll command for fd33, which

appears to be a docker function. In this case the test file is an AppImage, >> orcaslicer-2.3.0, but any AppImage will work for this. I have quite a few, >> as its the only way to get the latest and greatest given debians penchant
for dragging feet about projects that s/b debs but for some reason don't fit >> the debian POV.

That 2.3.0 version is the latest, not a leftover. PrusaSlicer switched
from AppImage to a snap for the newest version  and the install and is
nearly 50k files.  This freeze I'm looking for started just as I figured
out how to stuff a pan of hot mashed potatoes in orca's mouth and still
reboot. Orca had only one volume, wide open and its announcing every key
I pressed was close to me using my venison collector to put it out of
its misery.   Thanks Andy.

But while there is a call to docker on an ipv4 address starting with 172 in >> the trace output, I don't recall ever setting up docker on this system.  So >> who can help me check to see if its missing and this freeze is the timeout >> while its waiting for docker to reply to the poll?


Cheers, Gene Heskett, CET.

Thanks, all the best, as ever,

Andy
(amacater@debian.org)

.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Apr 13, 2025 at 05:32:29PM -0400, gene heskett wrote:

On 4/13/25 14:07, Andrew M.A. Cater wrote:

On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:

Hi Gene,

I'm probably going to regret this - let's see if I can help you
fault-find :)

Questions:

1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a on this machine, please.

<snip>

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

Linux coyote 6.1.0-33-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.133-1 (2025-04-10) x86_64 GNU/Linux

So, Debian 12.10 and right up to date with the latest kernel, not self-compiled.

2. Do you actually *have* orcaslicer 2.3.0 installed - or is it left
over from some previous attempt at installing something you later
removed?

OK - you do have it installed as you mention below.

All of these AppImages run just fine, once the freeze has timed out. Orcaslicer, PrusaSlicer, OpenSCAD, everything runs normally except for dim
to invisible for /some/ of the teeny little 8x8 menu icons.

3. What does the command

ip a

gene@coyote:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 40:b0:76:5b:11:3c brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 192.168.71.3/24 brd 192.168.71.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::42b0:76ff:fe5b:113c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

    link/ether 02:42:94:fc:f4:45 brd ff:ff:ff:ff:ff:ff

gene@coyote:~$ ip r
default via 192.168.71.1 dev eno1 proto static metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.71.0/24 dev eno1 proto kernel scope link src 192.168.71.3 metric 100 net 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

show on your system?

At last, some output :) OK - docker0 interface is not up. It looks as if docker0 would be on 172.* network - again, non-routable outside the machine
if I'm right. Bring up docker0 ?

4. Do you have docker (or podman or buldah) on your system?

Ah, you obviously do have docker installed / had it installed :)

5. Can you *show* us the output from strace, please - capture a few
lines.

the possibly interesting part involves docker:

here is all of >strace.stderr

[2025-04-13 16:24:12.508497] [0x00007efc1da0e540] [trace]  Initializing StaticPrintConfigs
add font of HarmonyOS_Sans_SC_Bold returns 1
add font of HarmonyOS_Sans_SC_Regular returns 1
add font of NanumGothic-Regular returns 1
add font of NanumGothic-Bold returns 1
loading network module at /home/gene/.config/OrcaSlicer/plugins/libbambu_networking.so
after dlopen, network_module is 0x560ef8e3ede0
1. lo    : 127.0.0.1
2. eno1  : 192.168.71.3
3. docker0: 172.17.0.1

This is probably 20k lines into the strace.comb  output by running "OrcaSlicer  &>strace.comb":

ioctl(65, SIOCGIFCONF, {ifc_len=2048 => 120 /* 3 * sizeof(struct ifreq) */, ifc_buf=[{ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}}, {ifr_name="eno1", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.71.3")}}, {ifr_name="docker0", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("172.17.0.1")}}]}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="lo", ifr_netmask={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("255.0.0.0")}}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="eno1", ifr_netmask={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("255.255.255.0")}})

I should advise since its Sunday I just updated with synaptic to a new
kernel and rebooted then installed a couple more pieces of docker so the error output isn't exactly the same.

OK - that's understood.

None of us are mind readers - none of us are sat looking over your shoulder. Without something to go on, every message from you about
problems involves significant guesswork. Share information, please,
about what you are *actually* seeing on screen in front of you and
make it easier for the rest of us. The Sherlock Holmes approach is
fun the first few times, but you're making it hard for us to eliminate
the impossible and work on the problems in hand.

[If this helps, imagine this was a problem at a TV station that someone
you didn't know well was reporting to you over the phone. You'd be asking questions and noting down the responses to be able to narrow down on what the issue was. You're expecting all of us to *know* the answers from zero information given: it's frustrating as anything.]

Chuckle, BTDT for nearly half a century Andy, I'm quite used to using somebody else's hands over the phone. Probably, as you have seen, not so
good letting somebody else run my hands.

This is a heck of a lot better though, Gene, because at least you're
showing us relevant output.

Using strace, the freeze corresponds to a poll command for fd33, which

appears to be a docker function. In this case the test file is an AppImage,
orcaslicer-2.3.0, but any AppImage will work for this. I have quite a few,
as its the only way to get the latest and greatest given debians penchant for dragging feet about projects that s/b debs but for some reason don't fit
the debian POV.

That 2.3.0 version is the latest, not a leftover. PrusaSlicer switched from AppImage to a snap for the newest version  and the install and is nearly 50k files.  This freeze I'm looking for started just as I figured out how to stuff a pan of hot mashed potatoes in orca's mouth and still reboot. Orca
had only one volume, wide open and its announcing every key I pressed was close to me using my venison collector to put it out of its misery.   Thanks Andy.

But while there is a call to docker on an ipv4 address starting with 172 in
the trace output, I don't recall ever setting up docker on this system.  So
who can help me check to see if its missing and this freeze is the timeout
while its waiting for docker to reply to the poll?

Cheers, Gene Heskett, CET.

Thanks, all the best, as ever,

Andy
(amacater@debian.org)

Stay well - all the best,

Andy
(amacater@debian.org)

.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 4/14/25 01:55, Andrew M.A. Cater wrote:

On Sun, Apr 13, 2025 at 05:32:29PM -0400, gene heskett wrote:

On 4/13/25 14:07, Andrew M.A. Cater wrote:

On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:

Hi Gene,

I'm probably going to regret this - let's see if I can help you
fault-find :)

Questions:

1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a on this machine,
please.

<snip>

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

Linux coyote 6.1.0-33-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.133-1
(2025-04-10) x86_64 GNU/Linux

So, Debian 12.10 and right up to date with the latest kernel, not self-compiled.

correct.

2. Do you actually *have* orcaslicer 2.3.0 installed - or is it left
over from some previous attempt at installing something you later
removed?

OK - you do have it installed as you mention below.

yes

All of these AppImages run just fine, once the freeze has timed out.
Orcaslicer, PrusaSlicer, OpenSCAD, everything runs normally except for dim >> to invisible for /some/ of the teeny little 8x8 menu icons.

3. What does the command

ip a

gene@coyote:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP >> group default qlen 1000
    link/ether 40:b0:76:5b:11:3c brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 192.168.71.3/24 brd 192.168.71.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::42b0:76ff:fe5b:113c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state >> DOWN group default

    link/ether 02:42:94:fc:f4:45 brd ff:ff:ff:ff:ff:ff

gene@coyote:~$ ip r
default via 192.168.71.1 dev eno1 proto static metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.71.0/24 dev eno1 proto kernel scope link src 192.168.71.3 metric 100 >> net 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

show on your system?

At last, some output :) OK - docker0 interface is not up. It looks as if docker0 would be on 172.* network - again, non-routable outside the machine if I'm right. Bring up docker0 ?

I've never before had any experience with docker. I am behind a new
router with brainslayers dd-wrt a/o about 6 weeks ago. I don't worry
about security too much when that guard dog is controlling outside access.

So the next question is How do I get docker running?  Data point: There
are quite a few "polls" in the strace output for fd's at lower numbers,
giving me a feeling that docker has a limit to the number of times/paths
it can service. But since I've no experience with docker, what do I do
to fix it?   And is it a system problem, or AppImage problem?  AIUI
docker is a vPN workalike. Please correct me.

4. Do you have docker (or podman or buldah) on your system?

Ah, you obviously do have docker installed / had it installed :)

Do ack synaptic.

5. Can you *show* us the output from strace, please - capture a few
lines.

the possibly interesting part involves docker:

here is all of >strace.stderr

[2025-04-13 16:24:12.508497] [0x00007efc1da0e540] [trace]  Initializing
StaticPrintConfigs
add font of HarmonyOS_Sans_SC_Bold returns 1
add font of HarmonyOS_Sans_SC_Regular returns 1
add font of NanumGothic-Regular returns 1
add font of NanumGothic-Bold returns 1
loading network module at
/home/gene/.config/OrcaSlicer/plugins/libbambu_networking.so
after dlopen, network_module is 0x560ef8e3ede0
1. lo    : 127.0.0.1
2. eno1  : 192.168.71.3
3. docker0: 172.17.0.1

This is probably 20k lines into the strace.comb output by running
"OrcaSlicer  &>strace.comb":

ioctl(65, SIOCGIFCONF, {ifc_len=2048 => 120 /* 3 * sizeof(struct ifreq) */, >> ifc_buf=[{ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr("127.0.0.1")}}, {ifr_name="eno1",
ifr_addr={sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr("192.168.71.3")}}, {ifr_name="docker0",
ifr_addr={sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr("172.17.0.1")}}]}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="lo", ifr_netmask={sa_family=AF_INET,
sin_port=htons(0), sin_addr=inet_addr("255.0.0.0")}}) = 0
ioctl(65, SIOCGIFNETMASK, {ifr_name="eno1", ifr_netmask={sa_family=AF_INET, >> sin_port=htons(0), sin_addr=inet_addr("255.255.255.0")}})

I should advise since its Sunday I just updated with synaptic to a new
kernel and rebooted then installed a couple more pieces of docker so the
error output isn't exactly the same.

OK - that's understood.

None of us are mind readers - none of us are sat looking over your
shoulder. Without something to go on, every message from you about
problems involves significant guesswork. Share information, please,
about what you are *actually* seeing on screen in front of you and
make it easier for the rest of us. The Sherlock Holmes approach is
fun the first few times, but you're making it hard for us to eliminate
the impossible and work on the problems in hand.

[If this helps, imagine this was a problem at a TV station that someone
you didn't know well was reporting to you over the phone. You'd be asking >>> questions and noting down the responses to be able to narrow down on what >>> the issue was. You're expecting all of us to *know* the answers from zero >>> information given: it's frustrating as anything.]

Chuckle, BTDT for nearly half a century Andy, I'm quite used to using
somebody else's hands over the phone. Probably, as you have seen, not so
good letting somebody else run my hands.

This is a heck of a lot better though, Gene, because at least you're
showing us relevant output.

Using strace, the freeze corresponds to a poll command for fd33, which

appears to be a docker function. In this case the test file is an AppImage,
orcaslicer-2.3.0, but any AppImage will work for this. I have quite a few, >>>> as its the only way to get the latest and greatest given debians penchant >>>> for dragging feet about projects that s/b debs but for some reason don't fit
the debian POV.

That 2.3.0 version is the latest, not a leftover. PrusaSlicer switched from >> AppImage to a snap for the newest version  and the install and is nearly 50k
files.

So PrusaSlicer is an older version and has a couple warts but my printer
needs heavy mods to the print startup gcode I've not yet incorporated
into OrcaSlicer. I have made a motorized nozzle cleaner that needs
additional gcode to enable it.  No other printer on the planet can do
that.  It is a cobble job of printed parts and 2 more motors, but it
Just Works.

  This freeze I'm looking for started just as I figured out how to
stuff a pan of hot mashed potatoes in orca's mouth and still reboot. Orca
had only one volume, wide open and its announcing every key I pressed was
close to me using my venison collector to put it out of its misery.   Thanks
Andy.

But while there is a call to docker on an ipv4 address starting with 172 in
the trace output, I don't recall ever setting up docker on this system.  So
who can help me check to see if its missing and this freeze is the timeout >>>> while its waiting for docker to reply to the poll?


Cheers, Gene Heskett, CET.

Thanks, all the best, as ever,

Andy
(amacater@debian.org)

Stay well - all the best,

Thank you Andy.  That, at 90 yo, is beginning to be a problem, my
diabetes is getting harder to control.

Andy
(amacater@debian.org)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 4/14/25 09:18, Pocket wrote:

On 4/14/25 8:35 AM, gene heskett wrote:

But while there is a call to docker on an ipv4 address starting
with 172 in
the trace output, I don't recall ever setting up docker on this
system.  So
who can help me check to see if its missing and this freeze is
the timeout
while its waiting for docker to reply to the poll?

Docker is a systemd-nspawn want to be.

It is nothing more that a container/virtual manager.

Don't know why you need it.

All I suspect true, and now that I've considered it overnight, doesn't
appear to be related to the freeze. That continues w/o abatement and has
been the since the bookworm install. I continue to look for ways to troubleshoot this, but lack the knowledge and tools to proceed.
Suggestions as to how to proceed, will be checked. Thank you Andy. Take
care of #1, yourself.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 4/14/25 11:51, Pocket wrote:

On 4/14/25 11:04 AM, gene heskett wrote:

On 4/14/25 09:18, Pocket wrote:

On 4/14/25 8:35 AM, gene heskett wrote:

But while there is a call to docker on an ipv4 address starting >>>>>>>> with 172 in
the trace output, I don't recall ever setting up docker on this >>>>>>>> system.  So
who can help me check to see if its missing and this freeze is >>>>>>>> the timeout
while its waiting for docker to reply to the poll?

Docker is a systemd-nspawn want to be.

It is nothing more that a container/virtual manager.

Don't know why you need it.

All I suspect true, and now that I've considered it overnight,
doesn't appear to be related to the freeze. That continues w/o
abatement and has been the since the bookworm install. I continue to
look for ways to troubleshoot this, but lack the knowledge and tools
to proceed. Suggestions as to how to proceed, will be checked. Thank
you Andy. Take care of #1, yourself.

Cheers, Gene Heskett, CET.

To be of any help I would need to know what is fd33.

the only info I can obtain is that fd33 is some kind of file descriptor.

ls -l /proc/$$/fd will list all open file descriptors.

Here are two copies of that, first is with PrusaSlicer runnin, 2nd its
been stopped and OrcaSlicer is running.

gene@coyote:~/AppImages$ ls -l /proc/$$/fd
total 0
lrwx------ 1 gene gene 64 Apr 13 15:32 0 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 1 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 2 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 255 -> /dev/pts/12 gene@coyote:~/AppImages$ ls -l /proc/$$/fd
total 0
lrwx------ 1 gene gene 64 Apr 13 15:32 0 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 1 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 2 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 255 -> /dev/pts/12

No change OrcaSlicer stopped

gene@coyote:~/AppImages$ ls -l /proc/$$/fd
total 0
lrwx------ 1 gene gene 64 Apr 13 15:32 0 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 1 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 2 -> /dev/pts/12
lrwx------ 1 gene gene 64 Apr 13 15:32 255 -> /dev/pts/12

So I see no connection to an AppImage

lsof -a -p $$ another way of listing file descriptors

also gives 3 identical results.

lsof -i -a -p $$ lists onlt network file descriptors

shows nothing with OrcaSlicer running

lsof -p $$ 2>/dev/null | awk '$NF ~ /\/pts\//' will list file
descriptors that are attached to any terminal

gene@coyote:~/AppImages$ lsof -p $$ 2>/dev/null | awk '$NF ~ /\/pts\//'
bash    3607 gene    0u   CHR 136,12      0t0       15 /dev/pts/12 bash    3607 gene    1u   CHR 136,12      0t0       15 /dev/pts/12 bash    3607 gene    2u   CHR 136,12      0t0       15 /dev/pts/12 bash    3607 gene  255u   CHR 136,12      0t0       15 /dev/pts/12

ls /proc/$$/fd/* will list the fieldescriptors directly

https://www.golinuxcloud.com/linux-file-descriptors/

gene@coyote:~/AppImages$ ulimit -n (in the shell that was running the apps
1024

So a limit of 32 theory is a false alarm.

Next idea, this one is dead IMO. And apparently removes docker from the suspects lineup. next is the missing fonts.  IDK if they are even
available from debian.

this is stdout to the screen from:

gene@coyote:~/AppImages$ strace OrcaSlicer 2>strace.stderr
[2025-04-14 14:26:44.187448] [0x00007ff206efd540] [trace]  Initializing StaticPrintConfigs
add font of HarmonyOS_Sans_SC_Bold returns 1
add font of HarmonyOS_Sans_SC_Regular returns 1
add font of NanumGothic-Regular returns 1
add font of NanumGothic-Bold returns 1
loading network module at /home/gene/.config/OrcaSlicer/plugins/libbambu_networking.so
after dlopen, network_module is 0x55ff9c53cb60
1. lo    : 127.0.0.1
2. eno1  : 192.168.71.3
3. docker0: 172.17.0.1

A 1 return is failure?

Thank you Pocket.

Cheers, Gene Heskett, CET.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)