[gentoo-user] kde-misc/synaptiks crashes immediately

[gentoo-user] kde-misc/synaptiks crashes immediately

[Alexander Puchmayr]

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

Hi there,

since the last world upgrade last week synaptiks no longer works on my laptop.

x11-drivers/xf86-input-synaptics-1.7.1
kde-misc/synaptiks-0.8.1-r2
kde-base/kde-meta-4.11.5
dev-lang/python-2.7.5-r3
dev-lang/python-3.3.3

Symptom:
Start synaptiks configuration module, get immedeately DrKonqi crash report 
(trace attached, likely not much useful since I disabled debug flags)
Start either from kde systemsettings or konsole; the latter gives

alex@prometheus /datadisk/home/alex $ synaptiks
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading 
configurations from ~/.fonts.conf is deprecated.
KCrash: Application 'synaptiks' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0
unnamed app(17763): Communication problem with  "synaptiks" , it probably 
crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not 
receive a reply (timeout by message bus)" " 

Any ideas what could go wrong?

Thanks,
	Alex

[-- Attachment #2: synaptiks-20140322-164210.kcrash.txt --]
[-- Type: text/plain, Size: 5485 bytes --]

Application: synaptiks (synaptiks), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fca426060fb in ?? () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007fca4260bb53 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007fca3a8c3f44 in KActionCollection::addAction(QString const&, QAction*) () from /usr/lib64/libkdeui.so.5
#8  0x00007fca3b208855 in ?? () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so
#9  0x00007fca46533dae in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#10 0x00007fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#11 0x00007fca46533af1 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#12 0x00007fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#13 0x00007fca464c107c in ?? () from /usr/lib64/libpython2.7.so.1.0
#14 0x00007fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0
#15 0x00007fca464aa11f in ?? () from /usr/lib64/libpython2.7.so.1.0
#16 0x00007fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0
#17 0x00007fca464f1aa6 in ?? () from /usr/lib64/libpython2.7.so.1.0
#18 0x00007fca464f1708 in ?? () from /usr/lib64/libpython2.7.so.1.0
#19 0x00007fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0
#20 0x00007fca4653282a in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#21 0x00007fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#22 0x00007fca464c107c in ?? () from /usr/lib64/libpython2.7.so.1.0
#23 0x00007fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0
#24 0x00007fca464aa11f in ?? () from /usr/lib64/libpython2.7.so.1.0
#25 0x00007fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0
#26 0x00007fca4652e517 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.7.so.1.0
#27 0x00007fca401fee82 in ?? () from /usr/lib64/python2.7/site-packages/sip.so
#28 0x00007fca3fdfbfdd in ?? () from /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so
#29 0x00007fca3b060aa6 in sipKUniqueApplication::newInstance() () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so
#30 0x00007fca3a9d4712 in ?? () from /usr/lib64/libkdeui.so.5
#31 0x00007fca3a9d4788 in ?? () from /usr/lib64/libkdeui.so.5
#32 0x00007fca3a9d48c9 in ?? () from /usr/lib64/libkdeui.so.5
#33 0x00007fca41edda41 in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#34 0x00007fca41ede47f in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#35 0x00007fca41edee03 in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#36 0x00007fca41edeefb in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#37 0x00007fca4260fd6e in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#38 0x00007fca3e545864 in QApplication::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#39 0x00007fca3b06b3a3 in sipKUniqueApplication::event(QEvent*) () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so
#40 0x00007fca3e53bccc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#41 0x00007fca3e53fa91 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#42 0x00007fca3a9d12c6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#43 0x00007fca3b06b44e in sipKUniqueApplication::notify(QObject*, QEvent*) () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so
#44 0x00007fca425f2a6e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#45 0x00007fca425f5e11 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#46 0x00007fca42626c23 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#47 0x00007fca408f43f5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#48 0x00007fca408f4748 in ?? () from /usr/lib64/libglib-2.0.so.0
#49 0x00007fca408f4804 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#50 0x00007fca42627066 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#51 0x00007fca3e5ef7be in ?? () from /usr/lib64/qt4/libQtGui.so.4
#52 0x00007fca425f118f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#53 0x00007fca425f1418 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#54 0x00007fca425f6eb8 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#55 0x00007fca3f611fb8 in ?? () from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#56 0x00007fca46533dae in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#57 0x00007fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#58 0x00007fca46533af1 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#59 0x00007fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#60 0x00007fca46535662 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0
#61 0x00007fca4654f74c in ?? () from /usr/lib64/libpython2.7.so.1.0
#62 0x00007fca46550580 in PyRun_FileExFlags () from /usr/lib64/libpython2.7.so.1.0
#63 0x00007fca4655100d in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.7.so.1.0
#64 0x00007fca465629ab in Py_Main () from /usr/lib64/libpython2.7.so.1.0
#65 0x00007fca45eabbf5 in __libc_start_main () from /lib64/libc.so.6
#66 0x000000000040091d in _start ()

Re: [gentoo-user] kde-misc/synaptiks crashes immediately

[Tom Wijsman]

On Sat, 22 Mar 2014 16:47:23 +0100
Alexander Puchmayr <alexander.puchmayr@linznet.at> wrote:

> Symptom:
> Start synaptiks configuration module, get immedeately DrKonqi crash
> report (trace attached, likely not much useful since I disabled debug
> flags) Start either from kde systemsettings or konsole; the latter
> gives
> 
> alex@prometheus /datadisk/home/alex $ synaptiks
> Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14:
> reading configurations from ~/.fonts.conf is deprecated.
> KCrash: Application 'synaptiks' crashing...
> KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from
> kdeinit sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0
> unnamed app(17763): Communication problem with  "synaptiks" , it
> probably crashed. 
> Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message
> did not receive a reply (timeout by message bus)" " 
> 
> Any ideas what could go wrong?

The crash would reveal what is wrong; therefore, I suggest you to
recompile the libraries of those packages with debug flags.

See http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces

Besides that, you might be able to use strace and/or ltrace (with -f
parameter; if needed, increase the -s parameter) to see what happens
under the hood.

I'm suspecting you'll find the cause by inspecting both; because as
the trace mixes in evaluation of a Python script, you might need to use
strace and/or ltrace to discover which Python script this is.

A next step could be to use a debugger on that Python script if the
trace, strace and/or ltrace are insufficient to reveal the cause.

When you have found the cause, can you file the details in a bug at
https://bugs.gentoo.org such that the maintainers are aware of this?

Thank you very much in advance.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

Re: [gentoo-user] kde-misc/synaptiks crashes immediately [SOLVED]

[Alexander Puchmayr]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="US-ASCII", Size: 3247 bytes --]

Thanks for the reply.

strace showed very detailed the last syscalls before the SIGSEV:

[pid 21801] sendmsg(9, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\4\1\1\0\0\0\0\3\0\0\0X\0\0\0\1\1o\0\23\0\0\0/StatusNotifierItem\0\0\0\0\0\2\1s\0\32\0\0\0org.kde.StatusNotifierItem\0\0\0
\0\0\0\3\1s\0\7\0\0\0NewIcon\0", 104}, {"", 0}], msg_controllen=0, 
msg_flags=0}, MSG_NOSIGNAL) = 104
[pid 21801] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8} 
---

and file descriptor 9 was connected to dbus. Well, but this did not show WHERE 
it crashed.

Next try was ltrace, but ltrace cannot be applied on python scripts (no ELF).

Finally, I checked the dependencies, and starting with pykde4 seemed to be a 
good idea. Recompiled it with "USE=debug" and "CXXFLAGS=-O2 -g", and voila, 
synaptiks worked without a problem. Hmmm. 

So, recompiled pykde with the normal options, and it still worked.
Very strange, since I ran revdep-rebuild and pyhton-updater after the world 
upgrade ... 
Note@self: Maybe updating/re-emerging PyQt4 and pykde4 is worth the time, even 
if its not neccessary.

However, it seems to work now. 

Best regards
	Alex





Am Samstag, 22. März 2014, 17:19:14 schrieb Tom Wijsman:
> On Sat, 22 Mar 2014 16:47:23 +0100
> 
> Alexander Puchmayr <alexander.puchmayr@linznet.at> wrote:
> > Symptom:
> > Start synaptiks configuration module, get immedeately DrKonqi crash
> > report (trace attached, likely not much useful since I disabled debug
> > flags) Start either from kde systemsettings or konsole; the latter
> > gives
> > 
> > alex@prometheus /datadisk/home/alex $ synaptiks
> > Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14:
> > reading configurations from ~/.fonts.conf is deprecated.
> > KCrash: Application 'synaptiks' crashing...
> > KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from
> > kdeinit sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0
> > unnamed app(17763): Communication problem with  "synaptiks" , it
> > probably crashed.
> > Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message
> > did not receive a reply (timeout by message bus)" "
> > 
> > Any ideas what could go wrong?
> 
> The crash would reveal what is wrong; therefore, I suggest you to
> recompile the libraries of those packages with debug flags.
> 
> See http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
> 
> Besides that, you might be able to use strace and/or ltrace (with -f
> parameter; if needed, increase the -s parameter) to see what happens
> under the hood.
> 
> I'm suspecting you'll find the cause by inspecting both; because as
> the trace mixes in evaluation of a Python script, you might need to use
> strace and/or ltrace to discover which Python script this is.
> 
> A next step could be to use a debugger on that Python script if the
> trace, strace and/or ltrace are insufficient to reveal the cause.
> 
> When you have found the cause, can you file the details in a bug at
> https://bugs.gentoo.org such that the maintainers are aware of this?
> 
> Thank you very much in advance.
-- 
Dipl. Ing. Alexander Puchmayr
Grundbachstraße 36
4060 Leonding, Österreich