Crostini: Atom/Nuclide has several issues |
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10575.17.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.19 Safari/537.36 Platform: 10575.17.0 (Official Build) dev-channel eve Steps to reproduce the problem: 1. Start crostini VM 2. Install Atom 3. Install nuclide package in Atom(as of this time v300 has a breaking bug so use 299 instead via apm) 4. Install minimap package in Atom 5. Open a large(> 1000 line) file 6. Simply try to use things Note: I have my chromebook pixel set to 2400x1600 and 125% page zoom What is the expected behavior? Editor works properly What went wrong? 1. With minimap enabled there is a lot of flickering in the minimap panel as well as around the mouse cursor. When actually performing actions in the editor pane the flickering can cause more permanent obfuscation. 2. The editor pane randomly scrolls all the way to the bottom and trying to move the editor cursor with the mouse no longer functions. This all worked properly before the latest dev channel update. Did this work before? N/A Chrome version: 67.0.3396.19 Channel: dev OS Version: 10575.17.0 Flash Version:
,
Apr 27 2018
This is likely a WontFix. As I think you might be hitting some window or buffer size limits. I'll investigate if these are general limits or specific to Atom. 2400x1600 and 125% page zoom is a really bad way to run Crostini. It will be terrible for performance as the X11 resolution will be twice that. It might have worked with the old version of crostini as we used to run X11 at half resolution. To avoid these issues, run chrome os at close to the optimal density setting (1280x800 on pixelbook). If you want optimal performance then 1280x800 is the way to go. Atom should look great in this mode after the last update with HiDPI support. If you really want to be running chrome at 2400x1600 and 125% page zoom. then you need to turn off hidpi by reducing the X11 density scale to 0.5. I'll post some instructions for this to the list later.
,
Apr 27 2018
Tried your suggestion but still hit problem 2 as described. Did not retry problem 1.
,
Apr 27 2018
These issues are not related afaict. What I suggested will only help with problem 1. What I suggested is not going to do anything about problem 2, which sounds like the 'end' key repeat issue someone else reported. If you can reproduce that from a fresh boot with an exact set of steps then please let me know.
,
Apr 27 2018
Out of curiosity.. how does the framebuffer comment effect using an external monitor. Certainly folks will be using higher resolutions on those.
,
Apr 27 2018
External monitors should work fine in general. There can always be applications that have issues when the resolution is too high. Above 4096x4096 is often a problem. There's no hard limit to the resolution in Crostini though. 8k monitor should work fine if the device can drive it. What you did by changing internal display to 2400x1600, is that you made the resolution for X11 apps 4800x3200. That's not an issue with external monitors as a 2400x1600 display setting is also 2400x1600 native resolution.
,
May 23 2018
,
Sep 6
<triage>I believe both of these issues should be fixed by now, but please re-open if not.</triage> |
|||
►
Sign in to add a comment |
|||
Comment 1 by tbuck...@chromium.org
, Apr 27 2018Components: OS>Systems>Containers
Labels: Proj-Containers Restrict-View-Google
Owner: reve...@chromium.org
Status: Assigned (was: Unconfirmed)