On Wed, Apr 11, 2018 at 10:05 PM, Brandon Hall wrote:
> I am still getting the Seg fault after attempting to install it using git
> via the command git clone https://github.com/leo-editor/leo-editor.
>
In that case, the problem must lie in your installation of other python
tools.
Edward
--
Y
>> Hello, I installed Leo (5.7) without any issue through pip install leo,
>> but when I attempt to run Leo, the command line just tells me “Segmentation
>> fault”. Please help so that I may be able to try Leo out!
>>
> Thanks for this detailed report. My apologies for y
Hi Edward,
Thanks for Leo. Still trying to figure it out. I installed on Debian
GNU/Linux 9.3 (Stretch) from Git.
I also found a Segmentation Fault when I attempted to run PyLint from
the UI.
Here's the logs in the terminal (nothing stands out, just segmentation
fault at the end, and
On Mon, Apr 9, 2018 at 9:08 PM, Brandon Hall wrote:
> Hello, I installed Leo (5.7) without any issue through pip install leo,
> but when I attempt to run Leo, the command line just tells me “Segmentation
> fault”. Please help so that I may be able to try Leo out!
>
Thanks for t
Hello, I installed Leo (5.7) without any issue through pip install leo, but
when I attempt to run Leo, the command line just tells me “Segmentation
fault”. Please help so that I may be able to try Leo out!
>>> import leo#
>>> /home/brandon/anaconda3/lib/python3.6
I can run and load with python 3.5.2 and PyQt 4.8.7.
When attempting with python 3.5.2 and PyQt 5.7 it segfaults.
Running the latest Linux MInt, v18, KDE, which is based on Ubuntu 16.04.
Chris
On Monday, September 19, 2016 at 2:29:25 AM UTC-7, Edward K. Ream wrote:
>
> On Tue, Sep 6, 2016 at 10
On Tue, Sep 6, 2016 at 10:01 PM, Chris George wrote:
> Segmentation faults are not very frequent, at least when I search this
> forum.
>
> I receive one in the terminal window whenever I load Leo with python 3.5.2
> and PyQt 5.7.0 and the python_terminal plugin. I isolated it by disabling
> all o
On Wed, 14 Sep 2016 09:02:05 -0700 (PDT)
Chris George wrote:
> Would there be any benefit to have me go through and test all of the
> existing plugins against python 3.5.2 and PyQt 5.7?
I think that would be useful. I've always thought it would be useful
to store info. like this in tags in the
Would there be any benefit to have me go through and test all of the
existing plugins against python 3.5.2 and PyQt 5.7?
As I stated in a later post, I am learning python/PyQt etc. and I am sure
that with some direction I could even propose a few solutions to any
problems I find, but as a learn
On Tue, Sep 6, 2016 at 10:01 PM, Chris George wrote:
> Segmentation faults are not very frequent, at least when I search this
> forum.
>
> I receive one in the terminal window whenever I load Leo with python 3.5.2
> and PyQt 5.7.0 and the python_terminal plugin. I isolated it by disabling
> all o
os.getenv('USER'): 'chris'
reading settings in /working/leo/leo-editor/leo/config/leoSettings.leo
reading settings in /home/chris/.leo/myLeoSettings.leo
Segmentation fault
chris@quest ~/Working/leo/leo-editor $ gdb python3
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Cop
On Oct 26, 7:42 am, "Ville M. Vainio" wrote:
> On Mon, Oct 26, 2009 at 8:31 AM, loretta wrote:
> > gondorff# apt-cache policy python-sip4
> > python-sip4:
> > Installed: 4.9-1
> > Candidate: 4.9-1
>
> Alright, seem like ubuntu has packaged a different upstream version.
> As an interim masure,
On Mon, Oct 26, 2009 at 8:31 AM, loretta wrote:
> gondorff# apt-cache policy python-sip4
> python-sip4:
> Installed: 4.9-1
> Candidate: 4.9-1
Alright, seem like ubuntu has packaged a different upstream version.
As an interim masure, you might want to try manually installing the
.deb from karm
On Oct 25, 8:25 pm, "Ville M. Vainio" wrote:
> On Sun, Oct 25, 2009 at 8:50 PM, loretta wrote:
> > Oops, forgot to backtrace. Here's the bt:
>
> Alright, seems to be the same problem as I had with Karmic (and that was
> fixed).
>
> I suppose it'll be fixed in due time. For reference, my packa
On Sun, Oct 25, 2009 at 8:50 PM, loretta wrote:
> Oops, forgot to backtrace. Here's the bt:
Alright, seems to be the same problem as I had with Karmic (and that was fixed).
I suppose it'll be fixed in due time. For reference, my package versions:
vi...@ville-eee:~$ apt-cache policy python-sip
On Oct 25, 7:15 pm, loretta wrote:
> Seems to be too little information to be of any use. But wait, on top
Oops, forgot to backtrace. Here's the bt:
(gdb) bt
#0 PyDict_GetItem (op=0x4, key=0x8bf4700) at ../Objects/dictobject.c:
575
#1 0xb6af7954 in ?? () from /usr/lib/pymodules/python2.5/s
led plugin: nav_buttons
loadOnePlugin can not load enabled plugin: open_with
loadOnePlugin can not load enabled plugin: word_count
loadOnePlugin can not load enabled plugin: word_export
No word lists can be found for the language "en_US".
aspell checker not enabled
Program received signal SI
On Sun, Oct 25, 2009 at 5:14 PM, loretta wrote:
>> I think the offending package was sip.
>
> I seem to have the latest: python-sip 4.9.1. And python-qt4 is of
> 4.6.1. Any other idea, what I could do about this?
You need to get a traceback. Ensure all the relevant -dbg packaes are
installed (f
On Oct 25, 3:49 pm, "Ville M. Vainio" wrote:
> I think the offending package was sip.
I seem to have the latest: python-sip 4.9.1. And python-qt4 is of
4.6.1. Any other idea, what I could do about this?
Loretta
--~--~-~--~~~---~--~~
You received this message
On Sun, Oct 25, 2009 at 10:45 AM, loretta wrote:
> What am I supposed to do now now? If there are still some packages
> needed to be upgraded, they obviously didn't hit the repos yet. Where
> can I get them and which are those packages?
I think the offending package was sip.
> P.S.: Leo never
I'm on sidux (Debian SID, actually) and did a dist-upgrade. Now Leo
4.6. crashes. An upgrade to 4.6.3 didn't help and 4.7.beta crashes
too.
What am I supposed to do now now? If there are still some packages
needed to be upgraded, they obviously didn't hit the repos yet. Where
can I get them and w
On Tue, Oct 20, 2009 at 2:52 PM, znafets wrote:
>
> Okay, what branch do I have to checkout to get the running version ?
You need to apt-get upgrade your installation. Leo is ok, the problem
was in pyqt/sip packages of the distro.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~-
/
leoSettings.leo
using menus from: leoSettings.leo
reading /usr/local/home/.leo/.leoRecentFiles.txt
opening default_leo_file: /Users/sz93814/.leo/workbook.leo
@enabled-plugins found in leoSettings.leo
Segmentation fault (core dumped)
thanks for your patience
Stefan
On Oct 20, 12:31 pm, "Vi
On Tue, Oct 20, 2009 at 1:05 PM, znafets wrote:
>
> Wow, does that mean leo can't cope with the new pyqt version ?
No, leo works fine now (with new updates). It was a temporary problem
with Karmic beta.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~
Wow, does that mean leo can't cope with the new pyqt version ?
On Oct 14, 9:52 pm, "Ville M. Vainio" wrote:
> On Wed, Oct 14, 2009 at 9:32 PM, znafets wrote:
> > I just got the branch: bzr branch lp:leo-editor
> > I am getting this when I try to start leo on a ubuntu linux karmic
> > box:
>
>
On Wed, Oct 14, 2009 at 9:32 PM, znafets wrote:
> I just got the branch: bzr branch lp:leo-editor
> I am getting this when I try to start leo on a ubuntu linux karmic
> box:
See the thread about Karmic UNR, this is a known new issue with the
karmic (they pushed pyqt 4.6 which causes this).
--
opening default_leo_file: /Users/sz93814/.leo/workbook.leo
@enabled-plugins found in leoSettings.leo
Segmentation fault (core dumped)
except that ubuntu tries to create a bug report which fails with a
message that this is no genuine ubuntu package or so ...
Stefan
On 14 Okt., 20:32, znafets wrote
menus from: leoSettings.leo
reading /usr/local/home/.leo/.leoRecentFiles.txt
opening default_leo_file: /Users/sz93814/.leo/workbook.leo
@enabled-plugins found in leoSettings.leo
Segmentation fault (core dumped)
Can you give me a hint what's wrong ?
btw, launchLeo.py gui=tk does the same it segf
Settings.leo
> Using menus from myLeoSettings.leo
> reading /usr/local/home/.leo/.leoRecentFiles.txt
> Segmentation fault
>
>
> tk gui at least starts the app
There may be multiple problems here. Certainly, Leo/Python/Qt should never
segfault, but of course that is cold comfort :-)
In a
runk/leo/config/
leoSettings.leo
Using menus from leoSettings.leo
reading settings in /usr/local/home/.leo/myLeoSettings.leo
Using menus from myLeoSettings.leo
reading /usr/local/home/.leo/.leoRecentFiles.txt
Segmentation fault
The effect stays same.
No for the home :) ... I just share some config dirs which I
;
> SAXParseException: :12:1: not well-formed (invalid token)
Ensure your trunk is crean of conflict markers & such by doing "bzr revert".
> reading settings in /usr/local/home/.leo/myLeoSettings.leo
> Using menus from myLeoSettings.leo
> reading /usr/local/home/.leo/.leo
raise exception
SAXParseException: :12:1: not well-formed (invalid token)
reading settings in /usr/local/home/.leo/myLeoSettings.leo
Using menus from myLeoSettings.leo
reading /usr/local/home/.leo/.leoRecentFiles.txt
Segmentation fault
tk gui at least starts the app
--~--~-~--~--
32 matches
Mail list logo
