Issue metadata
Sign in to add a comment
|
Issue 619303 - not necessarily isolated issue to updated version only
Reported by
cpr.hear...@gmail.com,
Jun 14 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8172.47.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Platform: 8172.47.0 (Official Build) stable-channel falco Steps to reproduce the problem: 1. Issue 619303 occurred on my HP Chromebook yesterday BEFORE I updated to v.51. (see below for details) 2. 3. What is the expected behavior? What went wrong? I experienced " issue 619303 " yesterday BEFORE I updated to lastest Chrome OS (v.51). I've had my HP Chromebook for more than 18 months and have had no problems until yesterday when out of nowhere my cursor froze. I tried to reboot several times, thinking that would fix it. No luck there. Then I decided to update from v. 50 to v. 51 thinking that would fix the problem. When it didn't work, that's when I searched in the forum for answers and tried the Powerwash. That didn't help either. As of yesterday, the only way I can use the cursor is to have an external mouse via USB connection. I tried posting this message in the original issue report but it is restricted. I just wanted to ensure the tech gurus working on this problem know it is not necessarily isolated to the latest Chrome update, because I was having the same problem BEFORE I updated and the problem definitely occurred out of nowhere yesterday, June 13. Did this work before? Yes Since September of 2014 until yesterday, June 13, 2016. Chrome version: 51.0.2704.79 Channel: stable OS Version: 8172.47.0 Flash Version: Shockwave Flash 21.0 r0 Good luck with this and let me know if you need more information.
,
Jun 17 2016
Does updating to the latest dev-channel release fix things? Other users are reporting it does fix them, however you may be hitting a different issue.
,
Jun 17 2016
Unfortunately, no it does not. Additionally disappointing is that AFTER I updated to the latest dev-channel, someone then posted the instructions to save all files before doing the update so as not to lose data when switching back. Sure wish that information had been provided BEFORE the dev-channel instructions were posted.
,
Jun 17 2016
Hey, I'm sorry to hear you were surprised by the data wipe! The system is supposed to give you a warning when you go backwards in version number (e.g. dev->beta or dev->stable). If it didn't, that's a bug. Can you try (and likely fail) to use the touchpad and then file feedback (you can hit alt-shift-i to pop the window). If you include system logs, I can take a look and see if there's anything suspicious in there.
,
Jul 16 2016
,
Apr 6 2018
Please reopen if you are still seeing this bug. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by thestig@chromium.org
, Jun 15 2016