Bug#885775: It seems it is not related to apparmor

2018-01-11 Thread Laszlo KERTESZ
On Thu, 11 Jan 2018 13:27:00 +0100 intrigeri wrote: > Control: reassign -1 linux-image-4.14.0-2-amd64 > Control: found -1 4.14.7-1 > > Laszlo KERTESZ: > > So it happened again with no apparmor loaded.Twice. > > Thanks for reporting! I'm therefore reassigning this bug to the > affected Linux kernel

Bug#885775: It seems it is not related to apparmor

2018-01-11 Thread intrigeri
Control: reassign -1 linux-image-4.14.0-2-amd64 Control: found -1 4.14.7-1 Laszlo KERTESZ: > So it happened again with no apparmor loaded.Twice. Thanks for reporting! I'm therefore reassigning this bug to the affected Linux kernel package. Cheers, -- intrigeri

Bug#885775: [pkg-apparmor] Bug#885775: It seems it is not related to apparmor

2018-01-02 Thread Seth Arnold
On Sun, Dec 31, 2017 at 08:19:06AM +0200, Laszlo KERTESZ wrote: > So it happened again with no apparmor loaded.Twice. Thanks for the bug report. Are you in a position where you can run memtest86 or memtest86+ on this system? If nothing else it might be something useful to do while hoping someone

Bug#885775: It seems it is not related to apparmor

2017-12-30 Thread Laszlo KERTESZ
So it happened again with no apparmor loaded.Twice. I had some packages to update, i believe it was kodi, and the system froze. Restarted, it froze again when i ran dkg --configure -a and aptitude upgrade again. Every time the logs show systemd reloading before the freeze. Difference is that now t