Bug 283173

Summary: synaptiks-0.7 crashed after suspend with ALPS touchpad
Product: [I don't know] kde Reporter: Sven Eden <sven>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UPSTREAM    
Severity: crash CC: alanm, andrewciffone, arnaudfrezet, atalanttore, benj.talbi, bteuthorn, cfeck, chainsaw55, claudiu.cismaru, complaw, damar.v1.0, henkboswijk, hugo, jhauser, johnnyl33, jplello, kalyany4, kdebugs, kevin, kh.sora.1993, lampshade, luke, magelkyc, marko.gabriel.cz, micc1988, monirkohi2006, nick, pablcorr, pentiumburn, robert, secretcode343, shubham.chaudhary, terencejgolightly, tomas.rendl
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi

Description Sven Eden 2011-10-02 12:49:51 UTC
Application: python2 (0.7.0)
KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.0.4-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
This crash happens every first time the system wakes up from suspend. If synaptiks is then restarted, I can suspend the laptop and wake it up without a problem. It only happens after the first suspend after a reboot of the machine

- Custom settings of the application:
I am using a 3.0.4 kernel with gentoo patches and the ALPS-enabling patch from here: http://people.canonical.com/~sforshee/alps-touchpad/ (version 0.7) discussed here: https://bugs.gentoo.org/show_bug.cgi?id=318567 making the system to accept the ALPS touchpad as if it were a synaptics tp.

Although this is a custom patch not accepted upstream (yet), it might be a chance for the synaptiks author to share their experience with the patch author to eventually make ALPS touchpads, which gain on relevance these days, work as well on linux as synaptics touchpads do. Therefore I decided to file this report.

The crash can be reproduced every time.

-- Backtrace:
Application: synaptiks (python2.7), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f02c80ac700 (LWP 4137))]

Thread 2 (Thread 0x7f02b0570700 (LWP 4238)):
#0  0x00007f02c7632173 in poll () from /lib64/libc.so.6
#1  0x00007f02bf24c6ba in _xcb_conn_wait (c=0x2350790, cond=<optimized out>, vector=0x0, count=0x0) at /var/tmp/portage/x11-libs/libxcb-1.7/work/libxcb-1.7/src/xcb_conn.c:313
#2  0x00007f02bf24dce7 in xcb_wait_for_reply (c=0x2350790, request=12, e=0x7f02b056f0a0) at /var/tmp/portage/x11-libs/libxcb-1.7/work/libxcb-1.7/src/xcb_in.c:378
#3  0x00007f02bf8d5a5d in _XReply (dpy=0x234f540, rep=0x7f02b056f110, extra=0, discard=0) at /var/tmp/portage/x11-libs/libX11-1.4.4/work/libX11-1.4.4/src/xcb_io.c:601
#4  0x00007f02bd13db60 in XRecordEnableContext (dpy=0x234f540, context=<optimized out>, callback=0x7f02c80e2010, closure=0x0) at /var/tmp/portage/x11-libs/libXtst-1.2.0/work/libXtst-1.2.0/src/XRecord.c:849
#5  0x00007f02bc4a0d50 in ffi_call_unix64 () from /usr/lib64/libffi.so.5
#6  0x00007f02bc4a06d4 in ffi_call (cif=0x7f02b056f410, fn=0x7f02bd13daa0 <XRecordEnableContext>, rvalue=<optimized out>, avalue=<optimized out>) at src/x86/ffi64.c:484
#7  0x00007f02bc6b4005 in _call_function_pointer (argcount=4, resmem=0x7f02b056f300, restype=<optimized out>, atypes=<optimized out>, avalues=0x7f02b056f2d0, pProc=0x7f02bd13daa0 <XRecordEnableContext>, flags=4353) at /var/tmp/portage/dev-lang/python-2.7.2-r2/work/Python-2.7.2/Modules/_ctypes/callproc.c:827
#8  _ctypes_callproc (pProc=0x7f02bd13daa0 <XRecordEnableContext>, argtuple=<optimized out>, flags=4353, argtypes=<optimized out>, restype=0x1e54ef0, checker=0x0) at /var/tmp/portage/dev-lang/python-2.7.2-r2/work/Python-2.7.2/Modules/_ctypes/callproc.c:1174
#9  0x00007f02bc6adb58 in PyCFuncPtr_call (self=<optimized out>, inargs=<optimized out>, kwds=0x0) at /var/tmp/portage/dev-lang/python-2.7.2-r2/work/Python-2.7.2/Modules/_ctypes/_ctypes.c:3911
#10 0x00007f02c7b55062 in PyObject_Call (func=0x1ecec80, arg=<optimized out>, kw=<optimized out>) at Objects/abstract.c:2529
#11 0x00007f02c7becda6 in do_call (nk=<optimized out>, na=<optimized out>, pp_stack=0x7f02b056f680, func=0x1ecec80) at Python/ceval.c:4231
#12 call_function (oparg=<optimized out>, pp_stack=0x7f02b056f680) at Python/ceval.c:4036
#13 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2666
#14 0x00007f02c7bef229 in PyEval_EvalCodeEx (co=0x1eeec30, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=4, kws=0x234f500, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3253
#15 0x00007f02c7bed9ad in fast_function (nk=<optimized out>, na=4, n=<optimized out>, pp_stack=0x7f02b056f8a0, func=0x1ef7b18) at Python/ceval.c:4109
#16 call_function (oparg=<optimized out>, pp_stack=0x7f02b056f8a0) at Python/ceval.c:4034
#17 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2666
#18 0x00007f02c7bef229 in PyEval_EvalCodeEx (co=0x1eda330, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=1, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3253
#19 0x00007f02c7b7af91 in function_call (func=0x1f5f0c8, arg=0x1c7a0d0, kw=0x0) at Objects/funcobject.c:526
#20 0x00007f02c7b55062 in PyObject_Call (func=0x1f5f0c8, arg=<optimized out>, kw=<optimized out>) at Objects/abstract.c:2529
#21 0x00007f02c7b6408d in instancemethod_call (func=0x1f5f0c8, arg=0x1c7a0d0, kw=0x0) at Objects/classobject.c:2578
#22 0x00007f02c7b55062 in PyObject_Call (func=0x1e35370, arg=<optimized out>, kw=<optimized out>) at Objects/abstract.c:2529
#23 0x00007f02c7be7cd6 in PyEval_CallObjectWithKeywords (func=0x1e35370, arg=0x7f02c806b050, kw=<optimized out>) at Python/ceval.c:3882
#24 0x00007f02c2c4b9db in sip_api_call_method () from /usr/lib64/python2.7/site-packages/sip.so
#25 0x00007f02c28698f7 in sipVH_QtCore_11(PyGILState_STATE, _object*) () from /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so
#26 0x00007f02c289d5d0 in sipQThread::run() () from /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so
#27 0x00007f02c4c6ae95 in QThreadPrivate::start (arg=0x2343740) at thread/qthread_unix.cpp:331
#28 0x00007f02c78f5d4c in start_thread () from /lib64/libpthread.so.0
#29 0x00007f02c763aded in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f02c80ac700 (LWP 4137)):
[KCrash Handler]
#6  0x00007f02c297bbda in pyqtBoundSignal_emit () from /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so
#7  0x00007f02c7bed626 in ext_do_call (nk=0, na=0, flags=<optimized out>, pp_stack=0x7fff4b9f8dc0, func=0x20e2c68) at Python/ceval.c:4323
#8  PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2705
#9  0x00007f02c7bedd81 in fast_function (nk=<optimized out>, na=<optimized out>, n=<optimized out>, pp_stack=0x7fff4b9f8f30, func=0x2057cf8) at Python/ceval.c:4099
#10 call_function (oparg=<optimized out>, pp_stack=0x7fff4b9f8f30) at Python/ceval.c:4034
#11 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2666
#12 0x00007f02c7bef229 in PyEval_EvalCodeEx (co=0x204b3b0, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=2, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3253
#13 0x00007f02c7b7af91 in function_call (func=0x20591b8, arg=0x238bc68, kw=0x0) at Objects/funcobject.c:526
#14 0x00007f02c7b55062 in PyObject_Call (func=0x20591b8, arg=<optimized out>, kw=<optimized out>) at Objects/abstract.c:2529
#15 0x00007f02c7b6408d in instancemethod_call (func=0x20591b8, arg=0x238bc68, kw=0x0) at Objects/classobject.c:2578
#16 0x00007f02c7b55062 in PyObject_Call (func=0x1e351e0, arg=<optimized out>, kw=<optimized out>) at Objects/abstract.c:2529
#17 0x00007f02c7b55868 in PyObject_CallFunctionObjArgs (callable=0x1e351e0) at Objects/abstract.c:2760
#18 0x00007f02ba39569b in DBusPyConnection_HandleMessage (conn=<optimized out>, msg=<optimized out>, callable=<optimized out>) at conn.c:79
#19 0x00007f02ba396451 in _filter_message (conn=<optimized out>, message=<optimized out>, user_data=0x1e351e0) at conn-methods.c:197
#20 0x00007f02c2e6ee6c in dbus_connection_dispatch (connection=0x233ae10) at /var/tmp/portage/sys-apps/dbus-1.4.14/work/dbus-1.4.14/dbus/dbus-connection.c:4603
#21 0x00007f02b9d5ff55 in message_queue_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /var/tmp/portage/dev-libs/dbus-glib-0.94-r1/work/dbus-glib-0.94/dbus/dbus-gmain.c:90
#22 0x00007f02c332a83e in g_main_dispatch (context=0x21aafc0) at gmain.c:2441
#23 g_main_context_dispatch (context=0x21aafc0) at gmain.c:3014
#24 0x00007f02c332b028 in g_main_context_iterate (context=0x21aafc0, block=1, dispatch=1, self=<optimized out>) at gmain.c:3092
#25 0x00007f02c332b2bd in g_main_context_iteration (context=0x21aafc0, may_block=1) at gmain.c:3155
#26 0x00007f02c4d7f8ef in QEventDispatcherGlib::processEvents (this=0x21a7cf0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#27 0x00007f02c117d3ce in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x00007f02c4d53ce2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#29 0x00007f02c4d53f24 in QEventLoop::exec (this=0x7fff4b9f97c0, flags=...) at kernel/qeventloop.cpp:201
#30 0x00007f02c4d583ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#31 0x00007f02c209f00b in meth_QApplication_exec_ () from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#32 0x00007f02c7bed558 in call_function (oparg=<optimized out>, pp_stack=0x7fff4b9f9930) at Python/ceval.c:4013
#33 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2666
#34 0x00007f02c7bef229 in PyEval_EvalCodeEx (co=0x1c56e30, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=0, kws=0x1971bf8, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3253
#35 0x00007f02c7bed9ad in fast_function (nk=<optimized out>, na=0, n=<optimized out>, pp_stack=0x7fff4b9f9b50, func=0x2128488) at Python/ceval.c:4109
#36 call_function (oparg=<optimized out>, pp_stack=0x7fff4b9f9b50) at Python/ceval.c:4034
#37 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2666
#38 0x00007f02c7bef229 in PyEval_EvalCodeEx (co=0x7f02c7fefa30, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3253
#39 0x00007f02c7bef342 in PyEval_EvalCode (co=<optimized out>, globals=<optimized out>, locals=<optimized out>) at Python/ceval.c:667
#40 0x00007f02c7c0918c in run_mod (mod=<optimized out>, filename=<optimized out>, globals=0x18e6f60, locals=0x18e6f60, flags=<optimized out>, arena=<optimized out>) at Python/pythonrun.c:1346
#41 0x00007f02c7c09fa2 in PyRun_FileExFlags (fp=0x1978de0, filename=0x7fff4b9fb380 "/usr/bin/synaptiks", start=<optimized out>, globals=0x18e6f60, locals=0x18e6f60, closeit=1, flags=0x7fff4b9f9ea0) at Python/pythonrun.c:1332
#42 0x00007f02c7c0ab7f in PyRun_SimpleFileExFlags (fp=0x1978de0, filename=0x7fff4b9fb380 "/usr/bin/synaptiks", closeit=1, flags=0x7fff4b9f9ea0) at Python/pythonrun.c:936
#43 0x00007f02c7c1bd96 in Py_Main (argc=<optimized out>, argv=<optimized out>) at Modules/main.c:606
#44 0x00007f02c7582ebd in __libc_start_main () from /lib64/libc.so.6
#45 0x00000000004007d9 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2011-10-03 02:47:56 UTC
Bugs for synaptiks are not tracked at the KDE bug tracker. Please report it directly to synaptiks developers via http://synaptiks.lunaryorn.de/
Comment 2 Sven Eden 2011-10-03 11:28:09 UTC
Ah, sorry, I didn't realize that as DrKonqi doesn't make any proposal at all. However, the issue is fixed upstream by the patch set 0.9. Seth Forshee, the author of the ALPS kernel patch has released a new version that mimics synaptics so well, that everything works like with a synaptics touchpad now.
Comment 3 Sven Eden 2011-10-11 06:58:31 UTC
No, the issue is not fixed. I'll report at the site you mentioned then.
Comment 4 Christoph Feck 2011-10-17 09:53:55 UTC
*** Bug 284236 has been marked as a duplicate of this bug. ***
Comment 5 Jekyll Wu 2011-10-18 02:26:55 UTC
*** Bug 284317 has been marked as a duplicate of this bug. ***
Comment 6 Sven Eden 2011-10-18 19:18:51 UTC
The bug is said to be fixed in synaptiks version 0.8.0. I have updated to that version and had no crash the last few days.
Comment 7 Benjamin 2011-10-31 09:14:14 UTC
Created attachment 65059 [details]
New crash information added by DrKonqi

python2 (0.7.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed : i had a mouse connected to my laptop, so my touchpad was turned-off. When I put my computer to sleep and turned it on again, the crash notification appeared.

-- Backtrace (Reduced):
#8  0x0384346b in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9  0x080fade1 in ext_do_call (nk=0, na=152571984, flags=<optimized out>, pp_stack=0xbfafe6e4, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x989f788>) at ../Python/ceval.c:4331
#10 PyEval_EvalFrameEx (f=Frame 0x9c27a9c, for file /usr/lib/python2.7/dist-packages/dbus/connection.py, line 214, in maybe_handle_message (self=<SignalMatch at remote 0x9a4c1ac>, message=<dbus.lowlevel.SignalMessage at remote 0x9a2f1e0>, args=[], kwargs={}), throwflag=0) at ../Python/ceval.c:2705
#11 0x080f7e20 in fast_function (nk=<optimized out>, na=152571984, n=<optimized out>, pp_stack=0xbfafe7b4, func=<function at remote 0x95c6cdc>) at ../Python/ceval.c:4107
#12 call_function (oparg=1, pp_stack=0xbfafe7b4) at ../Python/ceval.c:4042
Comment 8 Christoph Feck 2011-11-01 17:02:09 UTC
*** Bug 285343 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Feck 2011-11-04 00:31:50 UTC
*** Bug 285687 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Feck 2011-11-15 08:23:54 UTC
*** Bug 286648 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2011-11-16 09:14:40 UTC
*** Bug 286747 has been marked as a duplicate of this bug. ***
Comment 12 Jekyll Wu 2011-11-28 10:45:11 UTC
*** Bug 287668 has been marked as a duplicate of this bug. ***
Comment 13 Jekyll Wu 2011-12-01 07:50:45 UTC
*** Bug 287960 has been marked as a duplicate of this bug. ***
Comment 14 William Teuthorn 2011-12-09 18:21:36 UTC
Created attachment 66560 [details]
New crash information added by DrKonqi

python2 (0.7.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

I opened lid of laptop and restored fron suspend.

-- Backtrace (Reduced):
#8  0x03a8f46b in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9  0x080fade1 in ext_do_call (nk=0, na=162689104, flags=<optimized out>, pp_stack=0xbf9378f4, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0xa5494a0>) at ../Python/ceval.c:4331
#10 PyEval_EvalFrameEx (f=Frame 0xa2cd9dc, for file /usr/lib/python2.7/dist-packages/dbus/connection.py, line 214, in maybe_handle_message (self=<SignalMatch at remote 0x9f71f8c>, message=<dbus.lowlevel.SignalMessage at remote 0xa3e19b0>, args=[], kwargs={}), throwflag=0) at ../Python/ceval.c:2705
#11 0x080f7e20 in fast_function (nk=<optimized out>, na=162689104, n=<optimized out>, pp_stack=0xbf9379c4, func=<function at remote 0x9f66cdc>) at ../Python/ceval.c:4107
#12 call_function (oparg=1, pp_stack=0xbf9379c4) at ../Python/ceval.c:4042
Comment 15 Jekyll Wu 2011-12-10 14:21:59 UTC
*** Bug 288655 has been marked as a duplicate of this bug. ***
Comment 16 Jekyll Wu 2011-12-11 18:09:26 UTC
*** Bug 288743 has been marked as a duplicate of this bug. ***
Comment 17 Sven Eden 2011-12-19 17:04:47 UTC
Just a note for the duplicates:

This issue is tracked here: https://github.com/lunaryorn/synaptiks/issues/21 but there doesn't seem to be a fix, yet.
Comment 18 Jekyll Wu 2012-01-22 05:35:11 UTC
*** Bug 292160 has been marked as a duplicate of this bug. ***
Comment 19 Jekyll Wu 2012-01-30 04:55:31 UTC
*** Bug 292828 has been marked as a duplicate of this bug. ***
Comment 20 Jekyll Wu 2012-02-12 13:11:13 UTC
*** Bug 293890 has been marked as a duplicate of this bug. ***
Comment 21 Arnaud Frézet 2012-03-23 20:16:32 UTC
Created attachment 69837 [details]
New crash information added by DrKonqi

python2 (0.7.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed: Resume from sleep, just open the laptop and login

- Unusual behavior I noticed: Synatpiks crash.

-- Backtrace (Reduced):
#8  0xb5fd846b in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9  0x080fade1 in ext_do_call (nk=0, na=141107280, flags=<optimized out>, pp_stack=0xbfd97d64, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x8f3c698>) at ../Python/ceval.c:4331
#10 PyEval_EvalFrameEx (f=Frame 0x8d255dc, for file /usr/lib/python2.7/dist-packages/dbus/connection.py, line 214, in maybe_handle_message (self=<SignalMatch at remote 0x8ad8f8c>, message=<dbus.lowlevel.SignalMessage at remote 0x8f3aeb0>, args=[], kwargs={}), throwflag=0) at ../Python/ceval.c:2705
#11 0x080f7e20 in fast_function (nk=<optimized out>, na=141107280, n=<optimized out>, pp_stack=0xbfd97e34, func=<function at remote 0x8accd4c>) at ../Python/ceval.c:4107
#12 call_function (oparg=1, pp_stack=0xbfd97e34) at ../Python/ceval.c:4042
Comment 22 Jekyll Wu 2012-03-28 14:49:16 UTC
*** Bug 296956 has been marked as a duplicate of this bug. ***
Comment 23 Ron 2012-04-19 15:04:43 UTC
Created attachment 70503 [details]
New crash information added by DrKonqi

python2 (0.7.0) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

Synapiks crashed after resuming from sleep.  This has happened with other users.  In this case, it is with Ubunutu 11.10, 64-bit on an HP Pavilion dv7 laptop.  Note, however, that in this case, I was logged in using the Gnome 3.x window manager.  The Gnome settings did not enable me to disable the touchpad, and Synaptiks did.  The problem may be in the interaction between Gnome and KDE.  The real problem came from the inability of using the touchpad's disable feature (which works under Win7 but not) under Linux (with Unity or Gnome).  For whatever reason, the touchpad does not disable by double-clicking the upper-left corner as it does under Win7 (per HP's instructions).

-- Backtrace (Reduced):
#7  0x00007f9db0edb48d in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#8  0x00000000004ba151 in ext_do_call (nk=0, na=0, flags=<optimized out>, pp_stack=0x7fffe28ed970, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x214a9f0>) at ../Python/ceval.c:4331
#9  PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at ../Python/ceval.c:2705
#10 0x00000000004b6d77 in fast_function (nk=<optimized out>, na=<optimized out>, n=<optimized out>, pp_stack=0x7fffe28edab0, func=<function at remote 0x192da28>) at ../Python/ceval.c:4107
#11 call_function (oparg=<optimized out>, pp_stack=0x7fffe28edab0) at ../Python/ceval.c:4042
Comment 24 Albert Astals Cid 2012-10-02 17:22:49 UTC
*** Bug 307695 has been marked as a duplicate of this bug. ***
Comment 25 Christoph Feck 2013-01-29 20:47:25 UTC
*** Bug 314088 has been marked as a duplicate of this bug. ***
Comment 26 Christoph Feck 2013-02-02 21:15:50 UTC
*** Bug 314282 has been marked as a duplicate of this bug. ***
Comment 27 Christoph Feck 2013-02-17 22:44:41 UTC
*** Bug 315280 has been marked as a duplicate of this bug. ***
Comment 28 Marko 2013-03-08 18:01:56 UTC
Created attachment 77871 [details]
New crash information added by DrKonqi

python2 (0.8.1) on KDE Platform 4.9.5 using Qt 4.8.3

- What I was doing when the application crashed:
i put the system to sleep befor the crash and when i wake up the system the synaptick crash

-- Backtrace (Reduced):
#6  0x00007f5b124cbd20 in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7  0x0000000000463ea7 in ext_do_call (nk=391004240, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fff3767ef70, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x3271d50>) at ../Python/ceval.c:4331
#8  PyEval_EvalFrameEx (f=<optimized out>, throwflag=throwflag@entry=0) at ../Python/ceval.c:2705
#9  0x00000000004602b7 in fast_function (nk=<optimized out>, na=<optimized out>, n=<optimized out>, pp_stack=0x7fff3767f140, func=<function at remote 0x29dc6e0>) at ../Python/ceval.c:4107
#10 call_function (oparg=<optimized out>, pp_stack=0x7fff3767f140) at ../Python/ceval.c:4042
Comment 29 Jekyll Wu 2013-04-08 12:02:57 UTC
*** Bug 318013 has been marked as a duplicate of this bug. ***
Comment 30 Jekyll Wu 2013-05-02 13:54:39 UTC
*** Bug 319028 has been marked as a duplicate of this bug. ***
Comment 31 Kevin Goeser 2013-05-05 08:27:21 UTC
Created attachment 79711 [details]
New crash information added by DrKonqi

python2 (0.8.1) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:

Synaptik always crashes when waking from hibernation or standby (here using a Macbook Pro 6.2)

-- Backtrace (Reduced):
#6  0x00007f2404e77123 in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7  0x000000000047d80a in ext_do_call (nk=163631184, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fff6802c250, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x13ecf30>) at ../Python/ceval.c:4331
#8  PyEval_EvalFrameEx (f=<optimized out>, throwflag=throwflag@entry=0) at ../Python/ceval.c:2705
#9  0x000000000047c357 in fast_function (nk=<optimized out>, na=<optimized out>, n=<optimized out>, pp_stack=0x7fff6802c420, func=<function at remote 0x12ea488>) at ../Python/ceval.c:4107
#10 call_function (oparg=<optimized out>, pp_stack=0x7fff6802c420) at ../Python/ceval.c:4042
Comment 32 Christoph Feck 2013-05-07 11:40:45 UTC
*** Bug 319457 has been marked as a duplicate of this bug. ***
Comment 33 Johnny Lee 2013-05-15 01:50:25 UTC
Created attachment 79889 [details]
New crash information added by DrKonqi

python2 (0.8.1) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed: put the laptop in suspend mode

- Custom settings of the application:

changed some configuration in synaptiks

-- Backtrace (Reduced):
#5  0x00007fe468b86123 in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#6  0x000000000047d80a in ext_do_call (nk=1839362128, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fffd74e6100, func=<built-in method emit of PyQt4.QtCore.pyqtBoundSignal object at remote 0x35bdaa8>) at ../Python/ceval.c:4331
#7  PyEval_EvalFrameEx (f=<optimized out>, throwflag=throwflag@entry=0) at ../Python/ceval.c:2705
#8  0x000000000047c357 in fast_function (nk=<optimized out>, na=<optimized out>, n=<optimized out>, pp_stack=0x7fffd74e62d0, func=<function at remote 0x2f7ccf8>) at ../Python/ceval.c:4107
#9  call_function (oparg=<optimized out>, pp_stack=0x7fffd74e62d0) at ../Python/ceval.c:4042
Comment 34 Jekyll Wu 2013-07-15 00:37:34 UTC
*** Bug 322367 has been marked as a duplicate of this bug. ***
Comment 35 Jekyll Wu 2013-09-14 16:46:31 UTC
*** Bug 324911 has been marked as a duplicate of this bug. ***
Comment 36 Christoph Feck 2013-11-09 20:00:29 UTC
*** Bug 327270 has been marked as a duplicate of this bug. ***
Comment 37 Christoph Feck 2013-11-30 17:59:03 UTC
*** Bug 327970 has been marked as a duplicate of this bug. ***
Comment 38 Shubham Chaudhary 2014-01-19 13:20:20 UTC
Created attachment 84731 [details]
New crash information added by DrKonqi

synaptiks (0.8.1) on KDE Platform 4.11.3 using Qt 4.8.4

- What I was doing when the application crashed:
Woke up from sleep and synaptik crashed after login

-- Backtrace (Reduced):
#6  0x00007fe10b34aae5 in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7  0x00000000005313b5 in ext_do_call (nk=<optimized out>, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fff99aa4020, func=0x16110e0) at ../Python/ceval.c:4331
#8  PyEval_EvalFrameEx (f=f@entry=0x1ce97d0, throwflag=throwflag@entry=0) at ../Python/ceval.c:2705
#9  0x000000000052e672 in fast_function (nk=<optimized out>, na=<optimized out>, n=2, pp_stack=0x7fff99aa41a0, func=0x159af50) at ../Python/ceval.c:4107
#10 call_function (oparg=<optimized out>, pp_stack=0x7fff99aa41a0) at ../Python/ceval.c:4042
Comment 39 Kevin Goeser 2014-02-02 08:59:15 UTC
Created attachment 84942 [details]
New crash information added by DrKonqi

synaptiks (0.8.1) on KDE Platform 4.11.5 using Qt 4.8.4

- What I was doing when the application crashed:

Still there with 4.11.5, crash after wakeup from standby.

-- Backtrace (Reduced):
#7  0x00007fd67e723ae5 in pyqtBoundSignal_emit () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#8  0x00000000005313b5 in ext_do_call (nk=<optimized out>, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fff5037c110, func=0x1d4edd0) at ../Python/ceval.c:4331
#9  PyEval_EvalFrameEx (f=f@entry=0x25b5c10, throwflag=throwflag@entry=0) at ../Python/ceval.c:2705
#10 0x000000000052e672 in fast_function (nk=<optimized out>, na=<optimized out>, n=2, pp_stack=0x7fff5037c290, func=0x1cd0668) at ../Python/ceval.c:4107
#11 call_function (oparg=<optimized out>, pp_stack=0x7fff5037c290) at ../Python/ceval.c:4042