While running Chakra GNU/Linux on a desktop system I have been having some system crashes happen. This post will describe the troubleshooting steps taken to find and resolve the issue. Since finding the issue was done mostly in the terminal via log files I am going to describe that process instead of showing it via screenshots, since not every system crash is caused by the same thing, It’s best to use the following information as a reference in how to find a kernel issue and a guide to fixing this specific issue.
After looking in /var/log and scanning the files Xorg.0.log, kernel.log and everything.log for any errors around the time that the system crash occurred.
I found no valid information within Xorg.0.log, eliminating the possibility that it is an Xorg issue.
The next file I checked was kernel.log and here is what I found.
Sep 28 12:37:51 localhost kernel: [132471.112749] backlighthelper[21910] trap divide error ip:4034be sp:7fffd5105130 error:0 in backlighthelper[400000+6000]
Sep 28 12:37:51 localhost kernel: [132471.168828] backlighthelper[21914] trap divide error ip:4034be sp:7fffd9b38290 error:0 in backlighthelper[400000+6000]
When comparing this to the entry around that time in everything.log I notice a coincidence, There are backlighthelper entries in that too!
Sep 28 12:37:51 localhost dbus[634]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Sep 28 12:37:51 localhost org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 28 12:37:51 localhost dbus[634]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Sep 28 12:37:51 localhost kernel: [132471.112749] backlighthelper[21910] trap divide error ip:4034be sp:7fffd5105130 error:0 in backlighthelper[400000+6000]
Sep 28 12:37:51 localhost dbus[634]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Sep 28 12:37:51 localhost org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 28 12:37:51 localhost dbus[634]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Sep 28 12:37:51 localhost kernel: [132471.168828] backlighthelper[21914] trap divide error ip:4034be sp:7fffd9b38290 error:0 in backlighthelper[400000+6000]
Sep 28 12:37:51 localhost dbus[634]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Sep 28 12:37:52 localhost org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 28 12:37:52 localhost dbus[634]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Sep 28 12:38:09 localhost dbus[634]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Sep 28 12:38:09 localhost org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 28 12:38:09 localhost dbus[634]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aha! I have been pointed in the right direction, I had assumed that powerdevil controlled the power management in the system. Doing a quick internet search led me to an article that verified my assumption. This page is located here.
Now that we know what is causing the issue we can move on to resolving the issue.
Open your launcher and then the KDE system settings.
Click on Startup and Shutdown.
Go to the Service Management section, Then look through the Startup Services on the bottom half of the window for Power Management. Uncheck the box next to Power Management to stop the service from running at boot up, Stop the current service if it is presently Running in the Status Field. Click on Apply then click on Overview in the right hand corner of the window to return to the base menu for System Settings. We are now going to verify that the changes have been applied successfully.
Click on Power Management.
You should see a screen similar to this when you enter power management however KDE often requires a logout for major system changes to show up in the interface, If you do not see the red X with the error message above and would like to make sure the changes were applied and no residual power management services are running you can always reboot your computer, However this was not necessary for me.
Cutting Edge Linux 