On Sat, 15 Jul 2017 04:18:07 -0000 "Sudhir Khanger" <ml@xxxxxxxxxxxxxxxxx> wrote: > I just installed 4.11.10-300.fc26.x86_64. And the problem continues. > > I am getting the following messages every second. > > We're sorry, it looks like > BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed. Please > contact the developer if you want to report the issue. We're sorry, > it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.10-300.fc26.x86_64 > crashed. Please contact the developer if you want to report the > issue. We're sorry, it looks like a problem occurred. If you'd like > to help resolve the issue, please send a report. Well, there is the big hammer that puts a band-aid on this. systemctl stop abrt-oops.service systemctl mask abrt-oops.service It doesn't solve anything, but it stops the messages from being generated. You lose any abrt-oops functionality, though. Are the messages really appearing as they did above? For both kernel images, 11.9 and 11.10? You can only be running one kernel, how can oops be generating for both? I wonder if there is some configuration that your user has that is causing the issue. Could you create a new user, and then log in as that user instead of your current user to see if the issue continues. You would have to do this before you stopped and masked the service. I know little about abrt, and why it would be generating these oops, and why it isn't paying attention to its configuration file settings. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
