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.puchm...@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
