[Eric] Seg Fault On Opening Dialog Box

Helen Ready plunozero at gmail.com
Tue May 30 15:52:24 BST 2017


Hi Pete,

Sorry about the long delay.  Thank you for taking the time to share your
wisdom, especially about the insight on Qt and QScin being immune to venv
fencing!  Next time, I'll be sure to install Eric and dependencies under
the Python install directory (usr/local/python/3.6.1/)  instead of one of
its sub virtual environments (usr/local/python/3.6.1/venv/myvenvproject/).

In your opinion, from a Linux security point-of-view, is it optimal to just
execute and use the Eric IDE from a sudo elevation off of my user account
or is the recommendard expectation for me to run Eric from my standard
account?  Put another way, am I wasting my time trying to make this work as
"./eric6" when I should be running the Eric IDE as "sudo ./eric6" for
security and/or functionality reasons?

"it looks, it crashes, where the native Gtk file dialog is bent into Qt"
 << Yes, this is exactly what is happening when I attempt to open a File
Dialog box within the Eric IDE.  Specifically, I click on a File Open icon,
a separate window opens for the Gtk Dialog Box with the border but a blank,
black screen and then the app crashes hard with a seg fault to the command
line.

"Please try to execute python examples/dialogs/standarddialogs.py (from
PyQt5), and check, if the QFileDialog functions behave."  <<  Sure, no
problem!  I will get back with you with the info today and let you know how
it goes.

Thanks!
Ben


On Tue, May 23, 2017 at 4:18 AM, Hans-Peter Jansen <hpj at urpla.net> wrote:

> Hi Ben,
>
> On Freitag, 19. Mai 2017 16:27:08 Helen Ready wrote:
> > Let me start by saying Thank You for the amazing IDE, Eric, and its
> > community.
>
> Welcome to the club.
>
> > Recently, I decided to take the plunge into Linux with CentOS 7
> > as my first. After installing Python 3.6.1 from source and setting up a
> > virtual enviroment, I naturally went to install the Eric IDE as my next
> > step.
>
> Installing Python from source need some careful considerations about
>  * what _other_ versions of Python are installed in the system?
>  * which Python(s) are qscintilla, sip, PyQt build on..
> because some parts of it (Qt, qscintilla) cannot be fenced in the VE,
> they're
> pure C++...
>
> OTOH; your traceback, although missing symbols, points to some interference
> between Qt and Gtk (it looks, it crashes, where the native Gtk file dialog
> is
> bent into Qt...).
>
> Please try to execute python examples/dialogs/standarddialogs.py (from
> PyQt5),
> and check, if the QFileDialog functions behave.
>
> Pete
> _______________________________________________
> Eric mailing list
> Eric at riverbankcomputing.com
> https://www.riverbankcomputing.com/mailman/listinfo/eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/eric/attachments/20170530/c0d0fb77/attachment.html>


More information about the Eric mailing list