0

Good morning,

my Lubuntu 16.04.06 keeps rebooting unexpectedly. The machine in use is a laptop TOSHIBA Satellite L305, kernel 4.15.0-46-generic.

I also tried different distros (newer and older) but the issue still persists. I don't have such issue when I run Windows 7 on the same machine.

I checked on the logs and this is what I found:

Sun 10 07:40:09 daniele anacron[583]: Job `cron.daily' terminated
Sun 10 07:40:09 daniele anacron[583]: Normal exit (1 job run)
Sun 10 07:40:12 daniele com.canonical.indicator.application[927]: (process:1132): indicator-application-service-WARNING **: Application already exists, re-requesting properties.
Sun 10 07:41:45 daniele kernel: [ 441.173273] perf: interrupt took too long (3186 > 3180), lowering kernel.perf_event_max_sample_rate to 62750
Sun 10 07:42:12 daniele com.canonical.indicator.application[927]: (process:1132): indicator-application-service-WARNING **: Application already exists, re-requesting properties.

I already did sudo apt-get update and also the upgrade.

Any clues?

Regards

  • Please clarify what yo mean by 'reboot': Does the system go through the complete poweron cycle (manufacturer logo, boot messages, etc)? Or does the system merely flash a couple times and then return you to the login screen? – user535733 Mar 10 at 12:47
  • the first, complete poweron cycle – morpheus Mar 10 at 13:03
  • Check the previous day's syslog. The one you provided was a new stub. Look for the seconds before reboot. – user535733 Mar 10 at 13:09
  • if it can help I found this on apport.log: ERROR: apport (pid 3176) Sun Mar 10 14:08:45 2019: called for pid 1044, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 3176) Sun Mar 10 14:08:46 2019: executable: /usr/bin/xfce4-power-manager (command line "xfce4-power-manager") ERROR: apport (pid 3176) Sun Mar 10 14:08:46 2019: gdbus call error: Error connecting: Could not connect: Connection refused ERROR: apport (pid 3176) Sun Mar 10 14:08:46 2019: debug: session gdbus – morpheus Mar 10 at 14:12
  • Please edit the original question instead of burying new information (often unread) comments. If you believe the log is relevant, please tell us what time the reboot occurred. – user535733 Mar 10 at 18:10

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.