Re: A recent update has broken my Leo installation

34 views
Skip to first unread message

Edward K. Ream

unread,
Oct 19, 2022, 7:01:35 AM10/19/22
to leo-e...@googlegroups.com
On Wed, Oct 19, 2022 at 1:38 AM Richard Twyning <service.manag...@gmail.com> wrote:


I'm getting...
*** Leo could not be started ***
 ...
Is there anything more specific I can look at that tells me exactly what's missing?

Excellent question.

The message comes from runLeo.py. I would do the following:

- Edit leo/core/runLeo.py in your favorite text editor.
- After line 39, insert these two lines (right before the 'try' statement):

import pdb
pdb.set_trace()

Now invoke `python runLeo.py` from the command line. You should drop into python's pdb debugger.

pdb will (eventually) show the exception that caused the message, so you can just type 'n' until you see the exception.  That may be enough of a hint.  If not, you can rerun `python runLeo.py`, choosing 's' instead of 'n' to trace into the import logic.

HTH. Please let me know if this strategy doesn't work.

Edward

Thomas Passin

unread,
Oct 19, 2022, 8:17:59 AM10/19/22
to leo-editor
The printout should have included the exception, according to the code in runLeo.  Does something else get printed before the message that you quoted?

Richard Twyning

unread,
Oct 19, 2022, 12:54:09 PM10/19/22
to leo-editor
That was the only thing that got printed.  I've deleted everything and done a full reinstall and that seems to have done the trick.  I suspect the culprit was my PyQt being the incorrect version.

Many thanks.

Kind regards,
Richard Twyning

Edward K. Ream

unread,
Oct 19, 2022, 12:59:00 PM10/19/22
to leo-e...@googlegroups.com
On Wed, Oct 19, 2022 at 11:54 AM Richard Twyning <service.manag...@gmail.com> wrote:
That was the only thing that got printed.  I've deleted everything and done a full reinstall and that seems to have done the trick.  I suspect the culprit was my PyQt being the incorrect version.

Glad to hear it.

Edward
Reply all
Reply to author
Forward
0 new messages