Crouton: xiwi screen painting broken in chromeos beta channel

[mark-hahn]

name: roo
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/roo...
crouton: version 1-20160715134041~master:0dc76a22
release: precise
architecture: amd64
xmethod: xiwi
targets: xiwi,keyboard
host: version 8350.60.0 (Official Build) beta-channel samus 
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Jul 20 21:30:42 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

The windows in xiwi are screwed up. Random sections of the window will scroll and update and other parts will not paint. Also I can't get the UI to respond whether I try in the working part of the window or outside. This happens with all apps.

This occured after I upgraded my chromeos channel to beta from stable. I will try going back to stable.

Edit: Said dev channel but meant beta.

[divx118]

@mark-hahn Just in case you didn't know. Going back to stable means a power wash. So remember to backup your chroots before doing it.

[mark-hahn]

When I went back to stable the problem went away.

Isn't this going to be a big problem when the chrome bug/change gets to stable? Can someone fix this now using the beta channel so we don't have to scramble later?

BTW, I can describe the problem better now. Only the upper left of any pane will paint until you click anywhere in the pane. Then the whole pane will paint. This happens no matter what is requesting the repaint. I noticed this upper left is the same area that shows when the xiwi window opens but before it resizes to the correct size. So something doesn't get updated when the size is increased.

[plee3]

Just updated to latest stable channel and this problem is now occurring on my Pixel 2.
Here is the current version info:

crouton: version 1-20160715134041~master:0dc76a22
release: trusty
architecture: amd64
xmethod: xiwi
targets: xiwi,xorg,audio,core,cli-extra,extension,keyboard,touch,xfce
host: version 8350.60.0 (Official Build) stable-channel samus
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Jul 20 21:30:42 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

[mark-hahn]

Ouch, I can't live without xiwi but I can't stop a stable update, can I?

On Wed, Jul 27, 2016 at 9:33 PM, plee3 [email protected] wrote:

Just updated to latest stable channel and this problem is now occurring on
my Pixel 2.
Here is the current version info:

crouton: version 1-20160715134041~master:0dc76a22
release: trusty
architecture: amd64
xmethod: xiwi
targets: xiwi,xorg,audio,core,cli-extra,extension,keyboard,touch,xfce
host: version 8350.60.0 (Official Build) stable-channel samus
kernel: Linux localhost 3.14.0 #1
https://github.com/dnschneid/crouton/issues/1 SMP PREEMPT Wed Jul 20
21:30:42 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/2692#issuecomment-235798513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxhv28fe9QWPw3EOpuUYKkQ6rS5zLR5ks5qaDEpgaJpZM4JTfut
.

[jaduncan]

Confirmed on Pixel 2/Samus stable channel with both old abd newly created chroots. Looks like it is a ChromeOS issue.

[mark-hahn]

Does this only happen with xiwi? I only run with xiwi now and I wonder what the alternatives are. What is the Xorg option? I've never understood the difference. And does the problem happen with full-screen xiwi alternatives?

[plee3]

Xorg seems to work OK, but you need to deal with the issue of Xfce not handling HiDPI well on the Pixel. You can refer to the wiki about using crouton on Pixel for some options on handling the high resolution.

[jaduncan]

Xorg opens in a separate screen, so it's full screen and independent - you can't window it. I'd heavily recommend Gnome hidpi wise, it resizes things.

[mark-hahn]

Stable got to me so goodbye xiwi. I'm installing xfce and xorg now. This will make the experience of using crouton much worse. I have always run xiwi by itself with no linux desktop and was very happy.

Edit: I jumped the gun on this comment. When I first reported this it was happening for all xiwi windows no matter what app or file was open. Today I opened up my editor (atom) and saw almost the same symptoms where only part of a page was updating. Since then I have discovered it was only that app and only that one file (???). So apparently I am not seeing the original problem with my version of the stable channel. I think it was a coincidence.

[bodil]

Things started breaking for me too with the latest stable upgrade on my Pixel 2. Xiwi windows seem to work fine until I resize them, after which only the top left quadrant seems to be updating.

For reference, these are the relevant version numbers:

Version 52.0.2743.85 (64-bit)
Platform 8350.60.0 (Official Build) stable-channel samus
Firmware Google_Samus.6300.174.0

[drinkcat]

Does changing the internal panel resolution fix the problem? e.g. change to 1280x850?

Looks like there is an issue with hidpi handling...

[ryanphjohnson]

Just here to pile on: I'm on Chromebook Pixel 2, updated to ChromeOS v52, now Xiwi is behaving differently. I use it to run eclipse. The first pop up asking for which workspace I want works fine. The moment I select a workspace the window goes black (as it always has) but never repaints (window remains black) once eclipse opens the workspace. Hope this helps

[drinkcat]

2 workarounds for now:

• Enabling "debugging" mode in extension fixes the issue (then there is then a bar on top of the screen).
• Switching resolution to native 2560x1700 (instead of hi-dpi "fake" 1280x850), also fixes the problem.

[drinkcat]

Looks like a Chrome (OS) bug: Filed https://bugs.chromium.org/p/chromium/issues/detail?id=633806, feel free to star, but please refrain from commenting unless you have something important to add.

[sethml]

The Chromium bug is marked fixed, so hopefully on the next upgrade this'll be fixed.
https://bugs.chromium.org/p/chromium/issues/detail?id=633806

[phedders]

As of the last reboot, seems to be fixed here (Dev channel) Yey!

[tabatkins]

Fixed on Aug 24, and it's trying to get backported to the 53 release coming out now. Worst case it'll be in the 54 release in six weeks!