On 04 Apr, David Higton <dave@davehigton.me.uk> wrote:
> In message <g4wacql5n6npzdrjcgdjuslz7kvokfjqyh3gwky6cwywkgbvr7@5le2zo43v3z7>
> Rob Kendrick <rjek@rjek.com> wrote:
> > On Thu, Apr 04, 2024 at 10:53:38AM +0100, Bob Latham wrote:
> > > Latest development version 6696 fails to start on RISC OS.
> > >
> > > Immediate error: "Still watching sockets; can't be killed yet."
> > >
> > > A machine re-boot does not change this.
> >
> > My /guess/ is that SocketWatch (or similar) is running via an
> > application launched at boot and it is an earlier version than
> > NetSurf requires, so NetSurf's !Run's RMEnsure tries to replace
> > it with a newer version?
> >
> > What other software is running, and does quitting any of it (or
> > not running it at boot) help at all?
> I've been running 6696 since March 19 with no problem, so it must
> be something to do with the OP's particular system.
> (Mine is a RasPi 3B+, RO from 26-Mar-24).
The issue seems to be Hermes and UniPrint which both load SocketWatch
0.04y(02 Dec 2002). The "y" is not an error.
I can see several fixes now but I emailed Andrew Rawnsley to see what
he advises.
Thanks...
Bob.
--
Bob Latham
Stourbridge, West Midlands
No comments:
Post a Comment