crashed again this afternoon. attached is another prevboot file.
On Wed, Jun 17, 2020 at 8:11 AM DavidJr.
wrote:
> Crashed again overnight. Went to wake the screen (the computer doesnt
> sleep, just turns off the screen) and got no response from the mouse or
> keyboard. When i pressed the pow
Here are a couple other links from errors.ubuntu.com today. There were
three from temviewer as well, but i did not list those here.
https://errors.ubuntu.com/oops/5f1c4638-b0a5-11ea-af49-fa163e983629
https://errors.ubuntu.com/oops/69a6aac2-b0a4-11ea-9cf2-fa163e102db1
https://errors.ubuntu.com/oop
Crashed again overnight. No response from mouse, keyboard, or power
button. Hard rebooted. Dont see any new error links. I have reinstalled
TeamViewer and disabled dash to dock to see if that does anything
different.
On Wed, Jun 17, 2020 at 9:50 PM Daniel van Vugt <1880...@bugs.launchpad.net>
another crash yesterday no new error links, ran another prevboot.
On Thu, Jun 18, 2020 at 7:57 AM DavidJr.
wrote:
> Crashed again overnight. No response from mouse, keyboard, or power
> button. Hard rebooted. Dont see any new error links. I have reinstalled
> TeamViewer and disabled dash to
Public bug reported:
was logged in through team viewer and got kicked out. when i was able
to physically access the machine the screens were on, but was not able
to move the mouse or interact with the computer. performed hard reboot
to get it back on.
ProblemType: Bug
DistroRelease: Ubuntu 20.0
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
**NO LOG**
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you fin
Here are the links to the errors from step #2(I did it wrong the first time
so these may have been there then as well):
https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
https://errors.ubuntu.com/oops/53690272-95
attached is the file requested. I have unplugged the viewsonic monitor
from the GPU and will run for a while to see if it still has issues.
On Mon, Jun 15, 2020 at 9:00 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:
> Thanks. Certainly gnome-shell is crashing so we should focus on those:
Crashed again overnight. Went to wake the screen (the computer doesnt
sleep, just turns off the screen) and got no response from the mouse or
keyboard. When i pressed the power buttonit woke the screen, but it was
just a black screen with the mouse cursor displayed, but not able to be
moved. The
9 matches
Mail list logo
