From Newsgroup: comp.sys.raspberry-pi

bp@www.zefox.net wrote:

bp@www.zefox.net wrote:

Daniel James <daniel@me.invalid> wrote:

On 07/12/2025 18:55, bp@www.zefox.net wrote:

WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module

Have you done that?

After a fashion, yes. I tried appending
--enable-native-access=ALL-UNNAMED
on the command line, but it made no difference.

Clearly, the restriction is new(ish) and there's no obvious reason to
think that's the right place put the option. The references I found on-line >> to this change date from 2025, the application was last updated in 2022 IIRC.

Thanks for writing!

bob prohaska

It turns out there's a problem report that resembles mine at https://github.com/florentbr/OWON-VDS1022/issues/76
but it doesn't offer an explicit resolution.

At this point I have Trixie and Bookworm installs that don't connect
and a somewhat older Bookworm install that worked out of the box. So
far, the one that works is on a 33 bit Pi2.

I made a copy of the working microSD, booted that and verified it could communicate with the 'scope. Then I invited the system to upgrade and
it made about 350 changes to packages. After that, the 'scope couldn't
be connected to.

So, clearly, an incompatibility has been introduced by the upgrade.

Is there some way to selectively update and revert when trouble strikes?
It isn't something I _have_ to fix, but it might be useful to know now.

Thanks for reading,

bob prohaska

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On Mon, 8 Dec 2025 17:31:14 -0000 (UTC), bp wrote:

Sudo lsof is loquatious, but not obviously informative.

Try lsfd as an alternative <https://manpages.debian.org/lsfd(1)>.

Some other possibilities here <https://list.wlug.org.nz/hyperkitty/list/wlug@list.wlug.org.nz/thread/O6DBNZP3EDBQUZ6JQ6Z6AQAPCYEMMXSJ/>.
--- Synchronet 3.21a-Linux NewsLink 1.2