Hi Peter, thanks a lot for your reply! I will file the bug as soon as I am able to reproduce it. I have the feeling that it has something to do with scrolling when I am using my touchpad for it.
Cheers, Philipp Peter Hutterer <peter.hutte...@who-t.net> writes: > On Tue, Sep 25, 2018 at 12:09:53PM +0200, Philipp Arras wrote: >> Hi everyone, >> >> since I have upgraded xorg a few days ago on my arch linux system the >> xorg server crashes approximately twice a day. I have attached my >> Xorg.0.log. >> >> My system logs tell me: >> >> Sep 25 11:51:41 santiago audit[13540]: ANOM_ABEND auid=4294967295 uid=0 >> gid=0 ses=4294967295 pid=13540 comm="Xorg" exe="/usr/lib/Xorg" sig=6 res=1 >> Sep 25 11:51:41 santiago kernel: audit: type=1701 audit(1537869101.043:138): >> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=13540 comm="Xorg" >> exe="/usr/lib/Xorg" sig=6 res=1 >> Sep 25 11:51:41 santiago kernel: audit: type=1130 audit(1537869101.067:139): >> pid=1 uid=0 auid=4294967295 ses=4294967295 >> msg='unit=systemd-coredump@3-26694-0 comm="systemd" >> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' >> Sep 25 11:51:41 santiago audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 >> ses=4294967295 msg='unit=systemd-coredump@3-26694-0 comm="systemd" >> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' >> Sep 25 11:51:41 santiago systemd[1]: Started Process Core Dump (PID >> 26694/UID 0). >> -- Subject: Unit systemd-coredump@4-26697-0.service has finished start-up >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit systemd-coredump@4-26697-0.service has finished starting up. >> -- >> -- The start-up result is RESULT. >> Sep 25 11:51:42 santiago systemd-logind[432]: Session 5 logged out. Waiting >> for processes to exit. >> Sep 25 11:51:43 santiago systemd-coredump[26695]: Process 13540 (Xorg) of >> user 0 dumped core. >> >> Stack trace of thread >> 13540: >> #0 0x00007fc84263dd7f >> raise (libc.so.6) >> #1 0x00007fc842628672 >> abort (libc.so.6) >> #2 0x000055f6b8ba9cca >> OsAbort (Xorg) >> #3 0x000055f6b8ba9dbf >> FatalError (Xorg) >> #4 0x000055f6b8bb734e n/a >> (Xorg) >> #5 0x00007fc84263de00 >> __restore_rt (libc.so.6) >> #6 0x00007fc84263dd7f >> raise (libc.so.6) >> #7 0x00007fc842628672 >> abort (libc.so.6) >> #8 0x00007fc842628548 >> __assert_fail_base.cold.0 (libc.so.6) >> #9 0x00007fc842636396 >> __assert_fail (libc.so.6) >> #10 0x00007fc83cb9947b n/a >> (libinput.so.10) >> #11 0x00007fc83cb99e78 n/a >> (libinput.so.10) >> #12 0x00007fc83cba197c n/a >> (libinput.so.10) >> #13 0x00007fc83cba137f >> libinput_dispatch (libinput.so.10) > > this indicates an assert in libinput, which indicates that there's a bug in > libinput. Please file a bug here: > https://gitlab.freedesktop.org/libinput/libinput/issues, following the > steps here: > https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html > > ideally you could try to figure out what input sequence triggers the bug and > record it, should be easy to fix if reproducible. > > Cheers, > Peter _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
