volfyd · GitHub

Describe the bug

Neovide panics on startup.

To Reproduce
Steps to reproduce the behavior:

  1. Run neovide, nothing visible happens.
  2. A file neovide_backtraces.log was created with these contents
2023-10-06 19:18:17 - Neovide panicked with the message 'Failed to create OpenGL context: Error { raw_code: Some(12297), raw_os_message: None, kind: BadMatch }'. (File: src/renderer/opengl.rs; Line: 101, Column: 10)
   0: neovide::main::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys_common::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: neovide::renderer::opengl::build_context
   8: neovide::window::window_wrapper::WinitWindowWrapper::new
   9: neovide::window::create_window
  10: neovide::main
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: main
  13: __libc_start_call_main
  14: __libc_start_main@GLIBC_2.17
  15: _start

Expected behavior
Neovide starts

Screenshots
No window to screenshot

Desktop (please complete the following information):

Please run neovide --log and paste the contents of the .log file created in the current directory here:

TRACE [neovide] Neovide version: 0.11.2
DEBUG [neovide::bridge::command] Starting neovim with: Command { std: "/home/lhuhn/.nix-profile/bin/nvim" "--embed" "-p", kill_on_drop: false }

Additional context

  1. I have tried different versions of Mesa with no success.
  2. I have tried both UTM and a brew version of QEmu (with the idea that their 3d acceleration might be different). There is no difference.
  3. Version 0.10.4 worked fine

Read the original on github.com ↗