-
Notifications
You must be signed in to change notification settings - Fork 299
Black screen #890
Comments
Hi @dimascyriaco , Thanks for trying out Oni! Sorry you're hitting this issue. It looks like some sort of rendering problem (unfortunately I haven't tested on Kubuntu). Couple things to try:
We also send an option to electron to force hardware rendering - we set this option here: Line 64 in d4fb694
I wonder if disabling the |
I'll try to change the options and build it. |
Wow, that's pretty crazy looking! Thanks for trying that out. I see one interesting thing in the logs:
It seems the version is reported as |
That was it. I've updated neovim and it's working fine now! Thanks! |
Excellent! I'm planning on bundling Neovim with Oni, so that sort of thing won't happen in the future. Otherwise, it'd make sense to invest in a better error message / experience than a black screen... (#875) Thanks for troubleshooting with me - I'll close this out now |
@bryphe Can you confirm that linux distros won't have to keep track of neovim versions of packaging? If true, I'll remove dependencies on neovim for the next release (for AUR) |
Personally, I think we should keep neovim as a dependency in AUR. It seems more to be the "linux way" to explicitly declare your dependencies rather than bundling them in. It makes sense to bundle binaries in Windows and Mac, just not Linux. That's my opinion anyway. |
@keforbes I agree, however that requires having to add a check not to include and not to use the bundled neovim binary on linux systems. If neovim for ubuntu is not working for you, then I am not sure it will work for most people, ideally the package from the distro should be working and using a recent stable version. If neovim keeps being bundled for linux, keeping the dependency will make no difference as it will use the bundled one anyway. The distinction to be made is:
Not sure what @bryphe's plan is for this. I prefer (1) as most linux users that care about neovim should be power users that understand that if there's no package for their distro they'll have to pay attention to this. Ideally we should provide not only AUR packages, but .deb, .rpm, etc. But that's a lot of work for one person to do, and I am not sure if the automated builds we have are capable of this. Ubuntu/Debian/Mint/... users that care about this could take this work and maintain the packages, that's how it usually works and should happen with Oni as it gains popularity over time (before it is taken to the official repositories) |
@badosu, I think we're in agreement. I'd rather leave the neovim packaging and installing to the neovim folks and we would just declare it as a dependency. Even .deb and .rpm can declare dependencies and all package managers today can automatically download and install those dependencies before installing a package. With that said, I don't think Windows and Mac have good dependency resolution managers so it still makes sense to bundle the binaries on those platforms. But I'm just repeating myself and I think we're agreeing with each other. 😄 |
Even if we agree on this issue, currently the next version will bundle neovim, so that's why I need @bryphe's confirmation on his plan for this. |
Sorry I'm late to the party here - thanks for the discussion @keforbes and @badosu I'll defer to your judgement since you both know Linux better than I do 😄 The biggest pain point for me are issues like these where The current version actually doesn't download the Linux binary, so I think we're okay there @badosu . The latest
Given both your points, here are the two next steps in my mind for Linux:
Thanks again for your thoughts! |
I'm trying Oni, but I only get a black screen.
The editor seems to work, but it don't show anything on the UI. If I type
:q CR
blindly it exits and all. I tried opening both a file and a folder, and it shows nothing on the UI.If I enter insert mode and start typing it shows an weird scrollbar.
I'm on Kubuntu 17.04, and I use nvim normally everyday. Electron apps usually work fine in this computer.
The text was updated successfully, but these errors were encountered: