System freezes randomly after upgrading to ubuntu 17.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Expired
|
Undecided
|
Unassigned |
Bug Description
Since upgrading to ubuntu 17.04 from 16.10 my system will randomly freeze after a few hours. Initially the display will stop updating then audio will stop playing. Nothing but a hard reset can fix it. I have attempted to switch TTY and use alt+sysreq+1 then alt+sysreq+t still nothing.
I can't work out how to reproduce this issue but it happens seemingly randomly fairly often sometimes while the computer is not in use and locked. I tried switching from unity to gnome to solve the issue but I have the same problem.
Here are the lines in syslog right before the crash
Apr 26 14:55:01 desktop CRON[14753]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 14:58:27 desktop kernel: [17152.145453] usb 3-1: USB disconnect, device number 6
Apr 26 14:58:27 desktop gvfsd[2309]: PTP: reading event an error 0x05 occurred
Apr 26 14:58:28 desktop gvfsd[2309]: Android device detected, assigning default bug flags
Apr 26 14:58:28 desktop gvfsd[2309]: Received event PTP_EC_
Apr 26 14:58:28 desktop gvfsd[2309]: message repeated 10 times: [ Received event PTP_EC_
Apr 26 15:05:01 desktop CRON[14850]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:15:01 desktop CRON[14924]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:17:01 desktop CRON[14945]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 26 15:25:01 desktop CRON[14994]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:35:01 desktop CRON[15087]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:45:01 desktop CRON[15156]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:55:01 desktop CRON[15255]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:05:01 desktop CRON[15347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:15:01 desktop CRON[15440]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:17:01 desktop CRON[15457]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 26 16:25:01 desktop CRON[15532]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:35:01 desktop CRON[15612]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:45:01 desktop CRON[15689]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
I will also attach the output from lspci
Changed in ubuntu: | |
status: | Confirmed → Incomplete |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1686329/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]