Comment # 3 on bug 981011 from
Is it plymouth quiting that is killing us here?

May 22 00:12:50 tp-yoga260 systemd[1]: Starting Login Service...
May 22 00:12:50 tp-yoga260 dbus[656]: [system] Successfully activated service
'org.freedesktop.login1'
May 22 00:12:50 tp-yoga260 systemd[1]: Started Login Service.
May 22 00:12:50 tp-yoga260 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-logind comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 22 00:12:50 tp-yoga260 systemd-logind[682]: New seat seat0.
May 22 00:12:50 tp-yoga260 systemd-logind[682]: Watching system buttons on
/dev/input/event5 (Power Button)
May 22 00:12:50 tp-yoga260 systemd-logind[682]: Watching system buttons on
/dev/input/event6 (Video Bus)
May 22 00:12:50 tp-yoga260 systemd-logind[682]: Watching system buttons on
/dev/input/event3 (Lid Switch)
May 22 00:12:50 tp-yoga260 systemd-logind[682]: Watching system buttons on
/dev/input/event4 (Sleep Button)
May 22 00:12:50 tp-yoga260 systemd-logind[682]: Watching system buttons on
/dev/input/event8 (ThinkPad Extra Buttons)
May 22 00:12:50 tp-yoga260 PackageKit[671]: new update-packages transaction
/1_deadaacc scheduled from uid 0
May 22 00:12:50 tp-yoga260 PackageKit[671]: uid 0 obtained auth for
org.freedesktop.packagekit.package-install-untrusted
May 22 00:12:50 tp-yoga260 pk-offline-update[644]: status wait
May 22 00:12:50 tp-yoga260 pk-offline-update[644]: status setup
May 22 00:12:50 tp-yoga260 systemd[1]: Received SIGRTMIN+20 from PID 225
(plymouthd).
May 22 00:12:51 tp-yoga260 audit[690]: ANOM_ABEND auid=4294967295 uid=0 gid=0
ses=4294967295 pid=690 comm="PK-Backend" exe="/usr/lib/packagekitd" sig=6
May 22 00:12:51 tp-yoga260 packagekitd[671]: packagekitd:
/usr/include/boost/smart_ptr/intrusive_ptr.hpp:174: T*
boost::intrusive_ptr<T>::operator->() const [with T = zypp::ui::Selectable]:
Assertion `px != 0' failed.
May 22 00:12:51 tp-yoga260 systemd[1]: packagekit.service: Main process exited,
code=killed, status=6/ABRT
May 22 00:12:51 tp-yoga260 systemd[1]: packagekit.service: Unit entered failed
state.
May 22 00:12:51 tp-yoga260 systemd[1]: packagekit.service: Failed with result
'signal'.
May 22 00:12:51 tp-yoga260 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=packagekit comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
May 22 00:12:53 tp-yoga260 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-rfkill comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 22 00:13:19 tp-yoga260 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-hostnamed comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 22 00:13:19 tp-yoga260 kernel: audit_printk_skb: 33 callbacks suppressed
May 22 00:13:19 tp-yoga260 kernel: audit: type=1131 audit(1463868799.954:91):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
May 22 00:13:25 tp-yoga260 systemd-coredump[696]: Process 671 (packagekitd) of
user 0 dumped core.


You are receiving this mail because: