I was starting Leo. This is the exact same thing that happens every time I enable this plugin. I have seen this when using three different distributions over the past six months or so.
The startup process never completes. I never see a widget or the mainwindow. Luckily I am getting real good at editing myLeoSettings.leo with kwrite. This would hit me every time I downloaded a clean install of Leo after installing a fresh OS. So I was not doing anything to trigger it other than try to start Leo. Chris On Wednesday, June 19, 2019 at 8:44:31 AM UTC-7, Edward K. Ream wrote: > > > > On Wed, Jun 19, 2019 at 10:38 AM Chris George <[email protected] > <javascript:>> wrote: > >> chris@technatica:~/leo-editor$ python3 ./launchLeo.py --trace=startup >> > > >> KCrash: crashing... crashRecursionCounter = 2 >> ... >> [1]+ Stopped python3 ./launchLeo.py --trace=startup >> > > Well, that's too bad. Lot's of problems remain, but segfaults don't > happen for me. > > The detailed segfault messages don't help. > > Please describe what you were doing when the segfault happened. > > Previously, just entering a blank line caused the crash. > > Really, python should *never* segfault outside of Qt and other C modules. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1a5a5ac6-dc28-4141-bac4-8dbd21f1a212%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
