-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hyperland panic when using --no-fork #2109
Comments
Could you shorten the title and put the information in the issue description instead? I will also need more information, could you run |
I did it because the title made me want to throw up ( : |
Wayland log
|
@real-mr-x, are you sure that log is from a startup that crashes. I'm not experienced in reading the wayland logs, but it looks like there was some keyboard input and finally Neovim was closed, so that does not quite match the description you gave that it crashed immediately at the start. But I could be wrong. I do however see one problem with the log, Once we have enough information, we should involve the winit and possibly hyperland team. I doubt the bug is in Neovide itself, so it needs to be further debugged and fixed in those. |
Also, if you are using |
The surface was automatically dropped due to new RAII type in SCTK when dropping the Window, which was not the case at some point with SCTK. Thus destroying objects associated with it where causing issues with some window managers. Links: neovide/neovide#2109
The surface was automatically dropped due to new RAII type in SCTK when dropping the Window, which was not the case at some point with SCTK. Thus destroying objects associated with it where causing issues with some window managers. Links: neovide/neovide#2109
@fredizzimo in general, if you have a |
Thanks @kchibisov, yes I will do, in this case I was just waiting to get a little bit more information, but glad that you managed to figure it out already with this information. @real-mr-x, do you think you can test against that fix? Or should we wait until it's merged and the next winit release is released? You should be able to add the following to the end of [patch.crates-io]
winit = { git = "https://github.com/kchibisov/winit/", rev="2422ea39d0e97fd43698391f84d9300cd169d8cd" } You also need to change the version of winit to 0.29.3 a few lines up, since we haven't updated it yet. You can find instructions for building from source here https://neovide.dev/installation.html#linux-source. If you don't want to actually install that version, you can just run it with |
The surface was automatically dropped due to new RAII type in SCTK when dropping the Window, which was not the case at some point with SCTK. Thus destroying objects associated with it where causing issues with some window managers. Links: neovide/neovide#2109
The surface was automatically dropped due to new RAII type in SCTK when dropping the Window, which was not the case at some point with SCTK. Thus destroying objects associated with it where causing issues with some window managers. Links: neovide/neovide#2109
The surface was automatically dropped due to new RAII type in SCTK when dropping the Window, which was not the case at some point with SCTK. Thus destroying objects associated with it where causing issues with some window managers. Links: neovide/neovide#2109
This was fixed by: |
I'm using arch linux with hyprland and when I run neovide It doesn't launch sometimes and the output of neovide --no-fork gives me: Neovide panicked with the message 'Failed to create Window: OsError { line: 208, file: "/home/x_user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.29.2/src/platform_impl/linux/wayland/window/mod.rs", error: WaylandError(Dispatch(Backend(Protocol(ProtocolError { code: 0, object_id: 9, object_interface: "wp_fractional_scale_manager_v1", message: "" })))) }'. (File: src/renderer/opengl.rs; Line: 92, Column: 10)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Please run
neovide --log
and paste the contents of the.log
file created in the current directory here:Wayland log
Additional context
sometimes it starts working normally and sometimes the problem happens
The text was updated successfully, but these errors were encountered: