Am Sonntag, 10. März 2013, 16:46:08 schrieb Detlev Offenbach: > Can you test latest sources from source code repository?
If tested the current svn version and that seems fine again. I enabled the "use monospaced font by default" option in editor->stile. Unfortunately, eric crashes all the time on exit: Application: eric4 (python2.7), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x00007f937488841a in QWidgetPrivate::deleteTLSysExtra (this=0x4e41560) at kernel/qwidget_x11.cpp:2884 #7 0x00007f937484011e in QWidgetPrivate::deleteExtra (this=this@entry=0x4e41560) at kernel/qwidget.cpp:1834 #8 0x00007f937484034d in QWidgetPrivate::~QWidgetPrivate (this=0x4e41560, __in_chrg=<optimized out>) at kernel/qwidget.cpp:361 #9 0x00007f9374c357f9 in ~QMenuPrivate (this=0x4e41560, __in_chrg=<optimized out>) at widgets/qmenu_p.h:171 #10 QMenuPrivate::~QMenuPrivate (this=0x4e41560, __in_chrg=<optimized out>) at widgets/qmenu_p.h:183 #11 0x00007f9376fc619c in cleanup (pointer=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:62 #12 ~QScopedPointer (this=0x4e3e798, __in_chrg=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:100 #13 QObject::~QObject (this=0x4e3e790, __in_chrg=<optimized out>) at kernel/qobject.cpp:816 #14 0x00007f9374842440 in QWidget::~QWidget (this=0x4e3e790, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1556 #15 0x00007f93757450e9 in sipQMenu::~sipQMenu (this=0x4e3e790, __in_chrg=<optimized out>) at sipQtGuiQMenu.cpp:316 #16 0x00007f9375743e16 in release_QMenu (sipCppV=0x4e3e790) at sipQtGuiQMenu.cpp:2785 #17 0x00007f9375d8ebee in forgetObject (sw=sw@entry=0x7f934c297440) at siplib.c:10427 #18 0x00007f9375d90549 in sipWrapper_dealloc (self=0x7f934c297440) at siplib.c:9979 #19 0x00007f9378971c76 in subtype_dealloc (self=0x7f934c297440) at Objects/typeobject.c:1014 #20 0x00007f937896ba78 in dict_dealloc (mp=0x4d7e7f0) at Objects/dictobject.c:985 #21 0x00007f9375d8e033 in sipSimpleWrapper_clear (self=self@entry=0x7f934c2929e0) at siplib.c:9559 #22 0x00007f9375d904c2 in sipWrapper_clear (self=0x7f934c2929e0) at siplib.c:9940 #23 0x00007f93789c717d in delete_garbage (old=0x7f9378c4af60 <generations+96>, collectable=0x7fff75a1a610) at Modules/gcmodule.c:769 #24 collect (generation=2) at Modules/gcmodule.c:930 #25 0x00007f93789c7661 in PyGC_Collect () at Modules/gcmodule.c:1386 #26 0x00007f93789bc724 in Py_Finalize () at Python/pythonrun.c:444 #27 0x00007f93789bc248 in Py_Exit (sts=0) at Python/pythonrun.c:1760 #28 0x00007f93789bc33f in handle_system_exit () at Python/pythonrun.c:1134 #29 0x00007f93789bc3f5 in PyErr_PrintEx (set_sys_last_vars=set_sys_last_vars@entry=1) at Python/pythonrun.c:1144 #30 0x00007f93789bc69a in PyErr_Print () at Python/pythonrun.c:1047 #31 0x00007f93789bca2b in PyRun_SimpleFileExFlags (fp=<optimized out>, fp@entry=0xf54450, filename=<optimized out>, filename@entry=0x7fff75a1c267 "/usr/lib64/python2.7/site-packages/eric4/eric4.py", closeit=closeit@entry=1, flags=flags@entry=0x7fff75a1a840) at Python/pythonrun.c:947 #32 0x00007f93789bcd33 in PyRun_AnyFileExFlags (fp=fp@entry=0xf54450, filename=filename@entry=0x7fff75a1c267 "/usr/lib64/python2.7/site-packages/eric4/eric4.py", closeit=closeit@entry=1, flags=flags@entry=0x7fff75a1a840) at Python/pythonrun.c:747 #33 0x00007f93789c626d in Py_Main (argc=<optimized out>, argv=0x7fff75a1a9f8) at Modules/main.c:639 #34 0x00007f9378328455 in __libc_start_main (main=0x400730 <main>, argc=2, ubp_av=0x7fff75a1a9f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff75a1a9e8) at libc-start.c:226 #35 0x0000000000400761 in _start () at ../sysdeps/x86_64/elf/start.S:113 Thanks, Pete > On Sunday 10 March 2013, 11:14:06 Hans-Peter Jansen wrote: > > Dear Detlev, > > > > Am Samstag, 9. März 2013, 17:09:16 schrieb Detlev Offenbach: > > > Hello, > > > > > > that issue will be fixed in the next release. Sorry that it took so > > > long, > > > but I was busy doing some eric5 stuff. > > > > Since an workaround exists, there's no reason to hurry. What I found out > > meanwhile: the editor in sql mode doesn't play well: no matter, what > > settings are given (including the trick from below), it renders documents > > in variable spaced fonts. > > > > Thanks, > > Pete > > > > > Regards, > > > Detlev > > > > > > On Sunday 17 February 2013, 23:36:26 Hans-Peter Jansen wrote: > > > > Hi Detlev, > > > > > > > > this turned out to be a plain eric issue: > > > > > > > > Am Dienstag, 22. Januar 2013, 01:09:20 schrieb Hans-Peter Jansen: > > > > > with current qscintilla snapshots and eric4. It might be related to > > > > > any > > > > > of > > > > > sip, PyQt4 snapshots, too. > > > > > > > > > > I was in a hurry, hence had to revert to the latest release > > > > > versions, > > > > > and > > > > > got my monospaced fonts back this way.. > > > > > > > > I lost monospaced fonts within eric, although I've set: > > > > > > > > Editor->Style: Use monospaced as default > > > > > > > > and > > > > > > > > Highlighters->Styles: Python -> Monospaced Font (Bitstream Vera Sans > > > > Mono) > > > > > > > > but get them back, if I *deselect* "Use Monospaced Font" in editors > > > > context > > > > menu (of a python file), and loose them the other way around. This > > > > behavior > > > > is reproducible here with: > > > > > > > > python: 2.7.3 > > > > sip: 4.14.3 > > > > qt4: 4.8.4 > > > > pyqt4: 4.9.6 > > > > eric4: 4.5.8 > > > > > > > > BTW, shouldn't this option just toggle the related Editor->Style > > > > setting? > > > > > > > > Cheers, > > > > Pete > > > > > > > > > > > > _______________________________________________ > > > > QScintilla mailing list > > > > qscinti...@riverbankcomputing.com > > > > http://www.riverbankcomputing.com/mailman/listinfo/qscintilla--> > > > > > > > *Detlev Offenbach* > > > det...@die-offenbachs.de-- > > *Detlev Offenbach* > det...@die-offenbachs.de _______________________________________________ Eric mailing list Eric@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/eric
