On Wednesday 03 Jun 2015 00:15:56 Christian Boltz wrote:
Hello,
Am Dienstag, 2. Juni 2015 schrieb ianseeks:
Jun 02 14:32:35 LinuxMachine QXcbEventReader[7889]: <audit-1701> auid=1004 uid=1004 gid=100 ses=18 pid=7889 comm="QXcbEventReader" exe="/usr/bin/kactivitymanagerd" sig=11 Jun 02 14:32:35 LinuxMachine kernel: QXcbEventReader[7889]: segfault at 7fde85ed3c69 ip 00007fde85ed3c69 sp 00007fde8397fe60 error 14 in icudt55l.dat[7fde8615e000+18b6000] Jun 02 14:32:35 LinuxMachine kernel: audit: type=1701 audit(1433251955.534:2724): auid=1004 uid=1004 gid=100 ses=18 pid=7889 comm="QXcbEventReader" exe="/usr/bin/kactivitymanagerd" sig=11
Signal 11 means segfault, and the second log message also explicitely mentions "segfault".
The interesting question is why it is crashing ;-)
Can you reproduce the segfault by manually trying to start /usr/bin/kactivitymanagerd ? (BTW: Is it running after login? I doubt, but please check nevertheless.) it does seem to be running on this login session, it didn't segfault this time.
Maybe your ~/.xsession-errors also contains some hints about the segfaults. xsession-errors doesn't seem very helpful unless you know what you are looking for, you can't link lines in this file to the journal to see an order of events as the lines in ~/.xsession-errors-:0 do not have any time stamp what soever. I do get lots of lines like this "Battery No file queue: suspended or on battery" even though i'm on a tower machine.
Why is ~/.xsession-errors a zero length file but ~/.xsession-errors-:0 is the file that contains the log, i would have thought it would be the other way round and the ~/.xsession-errors-:0 file becomes the log containing the data from the previous session.
Regards,
Christian Boltz
thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org