@Ken: right, that probably is related to the bug in my code, but may or may not be part of this bug which is referring to that fact that python seg faults when trying to print the error (I think).
I'm next to useless for this, but looking at symbols from the core dump: #0 0x00000000004b0ebf in PyErr_Format () #1 0x00000000004a0558 in PyEval_EvalFrameEx () #2 0x00000000004a3dae in PyEval_EvalFrameEx () #3 0x00000000004a3dae in PyEval_EvalFrameEx () #4 0x00000000004a3dae in PyEval_EvalFrameEx () #5 0x00000000004a4649 in PyEval_EvalCodeEx () #6 0x00000000005329ad in ?? () #7 0x000000000041d3bd in PyObject_Call () #8 0x0000000000424f48 in ?? () #9 0x000000000041d3bd in PyObject_Call () #10 0x000000000049cd46 in PyEval_CallObjectWithKeywords () #11 0x00000000004d3b3d in ?? () #12 0x00007fec5fbcd3ba in start_thread () from /lib/libpthread.so.0 #13 0x00007fec5f095fcd in clone () from /lib/libc.so.6 #14 0x0000000000000000 in ?? () it appears that the function "PyErr_Format ()" is crashing. ** Summary changed: - credentials.get_request_token function causes a segmentation fault + PyErr_Format () Seg Faults -- PyErr_Format () Seg Faults https://bugs.launchpad.net/bugs/384643 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
