Re: Segmentation fault when run Leo on Linux

[Edward K. Ream]

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

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation fault when run Leo on Linux

[Brandon Hall]

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.

On Tuesday, April 10, 2018 at 6:03:19 AM UTC-7, Edward K. Ream wrote:


>
> 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 this detailed report. My apologies for your troubles.
>
> The work-around is to install git and then use git to install Leo.  Please 
> feel free to ask questions about how to do this.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation fault when run Leo on Linux

[Sebastian Silva]

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 crash).

(...)
:2: (WARNING/2) Inline substitution_reference start-string
without end-string.
:5: (WARNING/2) Block quote ends without a blank line;
unexpected unindent.
:3: (ERROR/3) Unexpected indentation.
no pylint configuration file found in
/home/icarito/.leo/pylint-leo-rc.txt
/home/icarito/Proyectos/leo-editor/leo/test/pylint-leo-rc.txt
Violación de segmento (`core' generado)

Regards and Thanks,

Sebastian


On 10/04/18 08:03, Edward K. Ream wrote:
>
>
> 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 this detailed report. My apologies for your troubles.
>
> The work-around is to install git and then use git to install Leo. 
> Please feel free to ask questions about how to do this.
>
> 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 leo-editor+unsubscr...@googlegroups.com
> .
> To post to this group, send email to leo-editor@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation fault when run Leo on Linux

[Edward K. Ream]

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 this detailed report. My apologies for your troubles.

The work-around is to install git and then use git to install Leo.  Please
feel free to ask questions about how to do this.

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation Fault

[Chris George]

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: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 other plugins and then enabling it.
>>
>
> ​I can run (not just load) the python_terminal.py plugin successfully with 
> the latest Leo sources on Python 3.5.1, PyQt version 5.7.0 on both Windows 
> 10 and Ubuntu 16.04 LTS.
>
> EKR
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation Fault

[Edward K. Ream]

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 other plugins and then enabling it.
>

​I can run (not just load) the python_terminal.py plugin successfully with
the latest Leo sources on Python 3.5.1, PyQt version 5.7.0 on both Windows
10 and Ubuntu 16.04 LTS.

EKR

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation Fault

['Terry Brown' via leo-editor]

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 plugins' docstring...

py: +2.7 -3.5

for something that runs in 2.7 but not 3.5, maybe, just top of head,
can probably do better than that.

also info. about maintenance status etc. etc.

Cheers -Terry

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Segmentation Fault

[Chris George]

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 learner of this toolkit I am not the authority. I 
am still puzzling out the best practises for writing plugins.

Chris

On Wednesday, September 14, 2016 at 8:13:58 AM UTC-7, Edward K. Ream wrote:
>
>
>
> 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 other plugins and then enabling it.
>>
>
> ​Sorry you are having trouble.  There are several sources of segfaults.
>
> 1. Installation problems.
> ​2​
> . Passing the wrong kind of pointer to Qt widgets.
> ​3. Rare, but possible: actual bugs in Qt or OS code.
>
> As an example of 3, there was, iirc, a Linux bug that caused the scroll 
> wheel to hard crash Leo.
>
> There have been several reports of problems with later Qt releases.  In 
> the past, Qt has seen fit to change their API's between releases so that 
> old code breaks.  The leoQt module is intended to paper over these 
> differences so that the rest of Leo doesn't have to worry about such 
> things.  Not all plugins use the leoQt module, so this is not a perfect 
> solution.
>
> In particular, changes to the Qt API could cause Leo to pass the wrong 
> kind of pointer to Qt, and that could cause a segfault.  Testing Leo on all 
> recent versions of Qt has top priority.
>
> The traceback you give is better than most core dumps.  It may be useful 
> in tracking down the problem.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: segmentation fault

[loretta]

On Oct 25, 8:25 pm, Ville M. Vainio vivai...@gmail.com wrote:
 On Sun, Oct 25, 2009 at 8:50 PM, loretta lore...@vol.at 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-sip4
 python-sip4:
   Installed: 4.9.1-snapshot-20091015-0ubuntu1

 vi...@ville-eee:~$ apt-cache policy python-qt4
 python-qt4:
   Installed: 4.6-1

 --
 Ville M. Vainiohttp://tinyurl.com/vainio

Thank you, Ville.

gondorff# apt-cache policy python-sip4
python-sip4:
  Installed: 4.9-1
  Candidate: 4.9-1
  Version table:
 *** 4.9-1 0
500 http://ftp.us.debian.org sid/main Packages
100 /var/lib/dpkg/status

gondorff# apt-cache policy python-qt4
python-qt4:
  Installed: 4.6-1
  Candidate: 4.6-1
  Version table:
 *** 4.6-1 0
500 http://ftp.us.debian.org sid/main Packages
100 /var/lib/dpkg/status
gondorff#

Loretta

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Mon, Oct 26, 2009 at 8:31 AM, loretta lore...@vol.at 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 karmic (and complaining to debian people ;-).

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[loretta]

On Oct 26, 7:42 am, Ville M. Vainio vivai...@gmail.com wrote:
 On Mon, Oct 26, 2009 at 8:31 AM, loretta lore...@vol.at 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

Works! Thanks a lot, Ville, you've taken a load off my mind!

 .deb from karmic (and complaining to debian people ;-).

I'll file a bug report to the sidux team first, as I'm on their
plattform.


 --
 Ville M. Vainiohttp://tinyurl.com/vainio

Loretta

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Sun, Oct 25, 2009 at 10:45 AM, loretta lore...@vol.at 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 ever let me down since I use it (2003). Now, since it
 uses Qt as its GUI, Leo has become faster. But I'd prefer a GUI, that
 just works: Tkinter. Sure, Tkinter is still there. But a s znafets
 stated: btw, launchLeo.py gui=tk does the same it segfaults too. .
 Strange.

I don't think it's strange. Using development versions of non-dead
technology leads to speedbumps like this occasionally. But, that's the
life we've chosen ;-).

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[loretta]

On Oct 25, 3:49 pm, Ville M. Vainio vivai...@gmail.com 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 because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Sun, Oct 25, 2009 at 5:14 PM, loretta lore...@vol.at 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 (for python, pyqt, sip, qt), and run leo in gdb:

gdb python

(gdb) run launchLeo.py

.. wait for crash ...

(gdb) bt

... copy-paste the backtrace here, or pyqt mailing list.

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[loretta]

On Oct 25, 5:31 pm, Ville M. Vainio vivai...@gmail.com wrote:
 On Sun, Oct 25, 2009 at 5:14 PM, loretta lore...@vol.at 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 (for python, pyqt, sip, qt), and run leo in gdb:

 gdb python

 (gdb) run launchLeo.py

 .. wait for crash ...

 (gdb) bt

 ... copy-paste the backtrace here, or pyqt mailing list.

 --
 Ville M. Vainiohttp://tinyurl.com/vainio

Everything seems to be in place, but I'm nevertheless sure if this is
it already:

(gdb) run /usr/local/bin/launchLeo.py
Starting program: /usr/bin/python /usr/local/bin/launchLeo.py
[Thread debugging using libthread_db enabled]
[New Thread 0xb74b7b70 (LWP 5817)]
Leo 4.7 beta 1, build 2404, September 8, 2009
Python 2.5.4, qt version 4.5.3
linux2
reading settings in /usr/lib/python2.5/site-packages/leo/config/
leoSettings.leo
using menus from: leoSettings.leo
reading settings in /media/truecrypt13/.leo/leoSettings.leo
using menus from: leoSettings.leo
reading /media/truecrypt13/.leo/.leoRecentFiles.txt
loadOnePlugin no init() leo_to_rtf
Can not import win32com.client
opening default_leo_file: /home/fgeiger/.leo/workbook.leo
@enabled-plugins found in leoSettings.leo
loadOnePlugin can not load enabled 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 SIGSEGV, Segmentation fault.
PyDict_GetItem (op=0x4, key=0x981d700) at ../Objects/dictobject.c:575
575 ../Objects/dictobject.c: No such file or directory.
in ../Objects/dictobject.c
(gdb)


Seems to be too little information to be of any use. But wait, on top
it reads Python 2.5.4, qt version 4.5.3. However, on my computer
PyQt 4.6.1 is installed, while libqt4 is of version 4.5.3.

The Python sources seem missing on my machine (just the dev files,
i.e. headers and static libs are there).

Loretta

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[loretta]

On Oct 25, 7:15 pm, loretta lore...@vol.at 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/sip.so
#2  0xb5eb1db9 in ?? () from /usr/lib/pymodules/python2.5/PyQt4/
QtGui.so
#3  0xb5332a94 in QApplicationPrivate::notify_helper (this=0x8a14ba0,
receiver=0x96575e0, e=0xbfffd818) at kernel/qapplication.cpp:4065
#4  0xb533acc2 in QApplication::notify (this=0x8754610,
receiver=0x96575e0, e=0xbfffd818) at kernel/qapplication.cpp:4030
#5  0xb600f755 in ?? () from /usr/lib/pymodules/python2.5/PyQt4/
QtGui.so
#6  0xb646c1eb in QCoreApplication::notifyInternal (this=0x8754610,
receiver=0x96575e0, event=0xbfffd818)
at kernel/qcoreapplication.cpp:610
#7  0xb6483e0e in QCoreApplication::sendEvent(QObject*, QEvent*) ()
from /usr/lib/libQtCore.so.4
#8  0xb647b87a in QObjectPrivate::setParent_helper (this=0x9659228,
o=0x96575e0) at kernel/qobject.cpp:1889
#9  0xb647b957 in QObject::setParent (this=0x9658498,
parent=0x96575e0) at kernel/qobject.cpp:1833
#10 0xb647bb9f in QObject (this=0x9658498, dd=..., parent=0x96575e0)
at kernel/qobject.cpp:710
#11 0xb532d496 in QAction (this=0x9658498, text=..., parent=0x96575e0)
at kernel/qaction.cpp:292
#12 0xb5771b8e in QMenu::addAction (this=0x96575e0, text=...) at
widgets/qmenu.cpp:1393
#13 0xb5e5845c in ?? () from /usr/lib/pymodules/python2.5/PyQt4/
QtGui.so
#14 0x080cd10a in call_function (f=0x9659084, throwflag=0) at ../
Python/ceval.c:3612
#15 PyEval_EvalFrameEx (f=0x9659084, throwflag=0) at ../Python/ceval.c:
2304
#16 0x080ce41d in PyEval_EvalCodeEx (co=0x8aa1e78, globals=0x8a9a824,
locals=0x0, args=0x8bf4558, argcount=1, kws=0x9658cf0, kwcount=4,
defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:2875
#17 0x0811419e in function_call (func=0x88d6e2c, arg=0x8bf454c,
kw=0x896579c) at ../Objects/funcobject.c:517
#18 0x0805d2a7 in PyObject_Call (func=0x0, arg=0x8bf454c,
kw=0x896579c) at ../Objects/abstract.c:1861
#19 0x080cba01 in ext_do_call (f=0x9658f14, throwflag=0) at ../Python/
ceval.c:3892
#20 PyEval_EvalFrameEx (f=0x9658f14, throwflag=0) at ../Python/ceval.c:
2344
#21 0x080ce41d in PyEval_EvalCodeEx (co=0x85b56e0, globals=0xb7ab7f0c,
locals=0x0, args=0x9658b18, argcount=2, kws=0x9658b20,
kwcount=4, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:
2875
#22 0x080ccdc4 in fast_function (f=0x965896c, throwflag=0) at ../
Python/ceval.c:3708
#23 call_function (f=0x965896c, throwflag=0) at ../Python/ceval.c:3633
#24 PyEval_EvalFrameEx (f=0x965896c, throwflag=0) at ../Python/ceval.c:
2304
#25 0x080ce41d in PyEval_EvalCodeEx (co=0x85f72f0, globals=0x83872d4,
locals=0x0, args=0x96588a4, argcount=3, kws=0x96588b0, kwcount=0,
defs=0x85be4b8, defcount=1, closure=0x0) at ../Python/ceval.c:2875
#26 0x080ccdc4 in fast_function (f=0x965873c, throwflag=0) at ../
Python/ceval.c:3708
#27 call_function (f=0x965873c, throwflag=0) at ../Python/ceval.c:3633
#28 PyEval_EvalFrameEx (f=0x965873c, throwflag=0) at ../Python/ceval.c:
2304
#29 0x080ce41d in PyEval_EvalCodeEx (co=0x85f43c8, globals=0x83872d4,
locals=0x0, args=0x9656e68, argcount=3, kws=0x9656e74, kwcount=1,
defs=0x85be258, defcount=1, closure=0x0) at ../Python/ceval.c:2875
#30 0x080ccdc4 in fast_function (f=0x9656d0c, throwflag=0) at ../
Python/ceval.c:3708
#31 call_function (f=0x9656d0c, throwflag=0) at ../Python/ceval.c:3633
#32 PyEval_EvalFrameEx (f=0x9656d0c, throwflag=0) at ../Python/ceval.c:
2304
#33 0x080cdc25 in fast_function (f=0x96568e4, throwflag=0) at ../
Python/ceval.c:3698
---Type return to continue, or q return to quit---

#34 call_function (f=0x96568e4, throwflag=0) at ../Python/ceval.c:3633
#35 PyEval_EvalFrameEx (f=0x96568e4, throwflag=0) at ../Python/ceval.c:
2304
#36 0x080cdc25 in fast_function (f=0x965678c, throwflag=0) at ../
Python/ceval.c:3698
#37 call_function (f=0x965678c, throwflag=0) at ../Python/ceval.c:3633
#38 PyEval_EvalFrameEx (f=0x965678c, throwflag=0) at ../Python/ceval.c:
2304
#39 0x080cdc25 in fast_function (f=0x9656614, throwflag=0) at ../
Python/ceval.c:3698
#40 call_function (f=0x9656614, throwflag=0) at ../Python/ceval.c:3633
#41 PyEval_EvalFrameEx (f=0x9656614, throwflag=0) at ../Python/ceval.c:
2304
#42 0x080ce41d in PyEval_EvalCodeEx (co=0xb67172f0,
globals=0xb7ab9b54, locals=0x0, args=0x90084f0, argcount=2,
kws=0x90084f8,
kwcount=0, defs=0xb7abac18, defcount=1, closure=0x0) at ../Python/
ceval.c:2875
#43 0x080ccdc4 in fast_function (f=0x9008384, throwflag=0) at ../
Python/ceval.c:3708
#44 call_function (f=0x9008384, throwflag=0) at ../Python/ceval.c:3633
#45 PyEval_EvalFrameEx (f=0x9008384, throwflag=0) at ../Python/ceval.c:
2304
#46 0x080ce41d in PyEval_EvalCodeEx (co=0xb67172a8,
globals=0xb7ab9b54, locals=0x0, args=0x9008354, argcount=2,
kws=0x900835c,
kwcount=0, defs=0xb673f880, defcount=3, closure=0x0) at ../Python/
ceval.c:2875
#47 

Re: segmentation fault

[Ville M. Vainio]

On Sun, Oct 25, 2009 at 8:50 PM, loretta lore...@vol.at 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-sip4
python-sip4:
  Installed: 4.9.1-snapshot-20091015-0ubuntu1

vi...@ville-eee:~$ apt-cache policy python-qt4
python-qt4:
  Installed: 4.6-1

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[znafets]

Wow, does that mean leo can't cope with the new pyqt version ?

On Oct 14, 9:52 pm, Ville M. Vainio vivai...@gmail.com wrote:
 On Wed, Oct 14, 2009 at 9:32 PM, znafets znaf...@googlemail.com 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).

 --
 Ville M. Vainiohttp://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Tue, Oct 20, 2009 at 1:05 PM, znafets znaf...@googlemail.com 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

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[znafets]

Okay, what branch do I have to checkout to get the running version ?

bzr branch lp:leo-editor

gives me a version that still segfaults like this

Leo 4.7 devel, build 2277, August 28, 2009
Python 2.6.4, qt version 4.5.2
linux2
reading settings in /usr/local/src/PYTHON/leo-editor/leo/config/
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, Ville M. Vainio vivai...@gmail.com wrote:
 On Tue, Oct 20, 2009 at 1:05 PM, znafets znaf...@googlemail.com 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. Vainiohttp://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Tue, Oct 20, 2009 at 2:52 PM, znafets znaf...@googlemail.com 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

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[znafets]

Installed the deb package with the same result:

Leo 4.7 beta 1, build 2404, September 8, 2009
Python 2.6.4, qt version 4.5.2
linux2
reading settings in /usr/share/python-support/leo/leo/config/
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)

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 znaf...@googlemail.com wrote:
 Hi,

 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:

 Leo 4.7 devel, build 2277, August 28, 2009
 Python 2.6.4, qt version 4.5.2
 linux2
 reading settings in /usr/local/src/PYTHON/leo-editor/leo/config/
 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)

 Can you give me a hint what's wrong ?
 btw, launchLeo.py gui=tk does the same it segfaults too.

 Stefan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault

[Ville M. Vainio]

On Wed, Oct 14, 2009 at 9:32 PM, znafets znaf...@googlemail.com 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).

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault ?

[Edward K. Ream]

On Sun, Jun 14, 2009 at 9:20 AM, znafets znaf...@googlemail.com wrote:


  File /usr/lib/python2.6/xml/sax/handler.py, line 38, in fatalError
raise exception

 SAXParseException: unknown: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


There may be multiple problems here.  Certainly, Leo/Python/Qt should never
segfault, but of course that is cold comfort :-)

In any case, I would remove the invalid token at line 12, character 1 of the
file and try again.  Continue until sax is happy. If there is still a
segfault we know the problem is unrelated to sax.

Edward

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault ?

[znafets]

Hi Ville,

thanks for coming back that fast.
I did a bzr revert, the only M was with leoSettings.leo I ddn't
think I changd anything there.
Anyways the output when starting leo changed to:
./launchLeo.py --
gui=qt
reading settings in /usr/local/src/PYTHON/leo-bzr/trunk/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 placed
in /usrl/local/home to share them from two different linux partitions
by links to the dir. That way I always keep one stable and one
bleeding edge ubuntu on my system with pretty much the same data
files.

best regards
Stefan

On 14 Jun., 14:34, Ville M. Vainio vivai...@gmail.com wrote:
 On Sun, Jun 14, 2009 at 5:20 PM, znafetsznaf...@googlemail.com wrote:
   File /usr/lib/python2.6/xml/sax/expatreader.py, line 211, in feed
     self._err_handler.fatalError(exc)

   File /usr/lib/python2.6/xml/sax/handler.py, line 38, in fatalError
     raise exception

  SAXParseException: unknown: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/.leoRecentFiles.txt
  Segmentation fault

 Your home is in /usr/local? Sounds weird, is that the way it should be?

 I'm wondering whether pyqt in karmic is in unstable stage still. You
 may want to make it dump core ('ulimit -c unlimited' on term before
 launching) and then analyze the core (gdb /usr/bin/python core).

 --
 Ville M. Vainiohttp://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: segmentation fault ?

[Ville M. Vainio]

On Sun, Jun 14, 2009 at 5:20 PM, znafetsznaf...@googlemail.com wrote:


  File /usr/lib/python2.6/xml/sax/expatreader.py, line 211, in feed
    self._err_handler.fatalError(exc)

  File /usr/lib/python2.6/xml/sax/handler.py, line 38, in fatalError
    raise exception

 SAXParseException: unknown: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/.leoRecentFiles.txt
 Segmentation fault

Your home is in /usr/local? Sounds weird, is that the way it should be?

I'm wondering whether pyqt in karmic is in unstable stage still. You
may want to make it dump core ('ulimit -c unlimited' on term before
launching) and then analyze the core (gdb /usr/bin/python core).

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---