Bug 194049 - Parley doesnt start segmentation fault
Summary: Parley doesnt start segmentation fault
Status: RESOLVED FIXED
Alias: None
Product: parley
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Parley Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-25 17:28 UTC by sam vimes
Modified: 2009-06-15 15:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sam vimes 2009-05-25 17:28:05 UTC
Version:            (using KDE 4.2.85)
OS:                Linux
Installed from:    Unlisted Binary Package

When i want to start Parley throug Lancelot or from the Bash,  i get the Message "Applikation Crashed" from the KDE-Crashmanager. 
gdb shows:


"tarting program: /usr/bin/parley                                                                                               
[Thread debugging using libthread_db enabled]                                                                                   
[New Thread 0xb52a3710 (LWP 14195)]
parley(14195) KEduVocDocument::KEduVocDocument: constructor done
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
parley(14195) VocabularyView::reset: reset
Object::connect: No such slot VocabularyModel::setLeitnerBox(KEduVocLeitnerBox*)
Object::connect: No such slot LeitnerView::setTranslation(KEduVocExpression*, int)
[New Thread 0xb356cb70 (LWP 14198)]
parley(14195) Script::activate: Activating Script "/usr/share/apps/parley/plugins/wiktionary_sound.py"
parley(14195) Script::activate: Script file given does not exist
parley(14195) Script::activate: Activating Script "/usr/share/apps/parley/plugins/google_images.py"
parley(14195) Script::activate: "Parley"
Kross: "Loading the interpreter library for python"
Kross: "Successfully loaded Interpreter instance from library."
Kross: "PythonScript::Constructor."
Kross: "PythonScript::execute"

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb52a3710 (LWP 14195)]
0xb5a742ab in strlen () from /lib/libc.so.6"

typing bt shows this:

"(gdb) bt                           
#0  0xb5a742ab in strlen () from /lib/libc.so.6
#1  0xb111dd99 in PyString_FromFormatV () from /usr/lib/libpython2.6.so.1.0
#2  0xb117b639 in PyErr_Format () from /usr/lib/libpython2.6.so.1.0
#3  0xb126b981 in ?? () from /usr/lib/python2.6/site-packages/sip.so
#4  0xb11e0f00 in ?? () from /usr/lib/libpython2.6.so.1.0
#5  0xb126e32c in ?? () from /usr/lib/python2.6/site-packages/sip.so
#6  0x00000004 in ?? ()
#7  0x61b3a7ea in ?? ()
#8  0x00000003 in ?? ()
#9  0x00000008 in ?? ()
#10 0xb0f226d4 in ?? ()
#11 0xb11da570 in ?? () from /usr/lib/libpython2.6.so.1.0
#12 0x61b3a7ea in ?? ()
#13 0xb0ea3a40 in ?? ()
#14 0xbfd72518 in ?? ()
#15 0xb10de53f in PyCObject_AsVoidPtr () from /usr/lib/libpython2.6.so.1.0
#16 0xb0852baf in initQtGui () from /usr/lib/python2.6/site-packages/PyQt4/QtGui.so
#17 0xb1185e21 in _PyImport_LoadDynamicModule () from /usr/lib/libpython2.6.so.1.0
#18 0xb1183aeb in load_module () from /usr/lib/libpython2.6.so.1.0
"
Comment 1 Frederik Gladhorn 2009-06-11 23:50:23 UTC
Could you install debug packages to get a good backtrace.
What distribution/python/qt versions are you using?
Comment 2 sam vimes 2009-06-15 15:20:52 UTC
It works now with Beta 2.