Nixpkgs: Kitty does not start more

[shyim]

Describe the bug
Kitty does not start more

To Reproduce
Steps to reproduce the behavior:

1. Run nixos-unstable
2. Start Kitty
3. Does not start

Expected behavior
Its working

Screenshots

[055 09:05:46.416468] [glfw error 65542]: GLX: No GLXFBConfigs returned
[055 09:05:46.416497] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[055 09:05:46.416512] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

Additional context
Add any other context about the problem here.

Metadata

• system: "x86_64-linux"
• host os: Linux 5.5.5, NixOS, 20.09pre214390.ea79a830dcf (Nightingale)
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.3.3
• channels(shyim): "nixos-20.03pre208171.2e8fc97dbfa"
• channels(root): "nixos-20.09pre214390.ea79a830dcf"
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute: kitty
# a list of nixos modules affected by the problem
module:

[rnhmjoj]

What does nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL says?

[shyim]

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2) 
OpenGL core profile version string: 4.6 (Core Profile) Mesa 19.3.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

[rnhmjoj]

Try running kitty with env MESA_GL_VERSION_OVERRIDE=3.3 kitty

[shyim]

Still don't running

❯ env MESA_GL_VERSION_OVERRIDE=3.3 kitty
[055 16:02:21.181352] [glfw error 65542]: GLX: No GLXFBConfigs returned
[055 16:02:21.181372] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[055 16:02:21.181380] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

[rnhmjoj]

Are you using wayland/sway? Did a previous version of kitty work?

There are a couple issues upstream with this same error. One is about sway, which should have already been fixed in unstable. The other is simply saying that you really need OpenGL 3.3.
If it used to work I guess the lowest requried version has been raised in a recent release.

[shyim]

I am using I3. I guess it happend with Kernel update I will downgrade to test that :thinking:

[shyim]

Same with 5.4 kernel 🙈

[vcunat]

Could this be the same as https://github.com/NixOS/nixpkgs/issues/75868 ?

[rnhmjoj]

It may be but I can't reproduce it on the same machine where I tested #75868.

[vcunat]

I think it's worth trying LIBGL_DEBUG=verbose in any case (for those who can reproduce the issue).

[shyim]

❯ LIBGL_DEBUG=verbose kitty
[056 11:43:24.816491] [glfw error 65542]: GLX: No GLXFBConfigs returned
[056 11:43:24.816512] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[056 11:43:24.816535] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

Similar issue happends also with alacritty. I guess it's a general problem

[fionera]

I have the same issue after an upgrade. The whole gl context is missing and glxinfo also screams
name of display: :1
Error: couldn't find RGB GLX visual or fbconfig

This doesnt happen on the 19.09 channel

[rht]

Bump. I have accidentally spotted this issue, I also use kitty and have been hesitant in updating my unstable channel until this is resolved.

[shyim]

It's not only kitty. The whole gl context is broken in 20.03 / unstable.

[timokau]

I tried to bisect the problem, but for some reason it just vanished. Now I cannot reproduce it anymore on the same machine with the same configuration and the same pinned nixpkgs. Very weird.

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nix-bisect-bisect-nix-builds/5584/10

[fionera]

@timokau I just upgraded to master again but the issue is still there. I am trying your bisect package now

[rnhmjoj]

If it's hard to reproduce and seems to appear/disappear randomly maybe it has to do with the /run/opengl-driver impurity of the system and not much with nixpkgs itself.

[vcunat]

Right, I would not expect these issues to happen if you have this path matching (i.e. booted NixOS version) with the package version you are using. I suspect the culprit is glibc update done during the 20.03 cycle.

[timokau]

Right, I would not expect these issues to happen if you have this path matching (i.e. booted NixOS version) with the package version you are using. I suspect the culprit is glibc update done during the 20.03 cycle.

In an effort to test this, I wanted to go back to a revision before this error occurred (8130f3c1c2bb0e533b5e150c39911d6e61dcecc2), reboot into that and then switch back to a more recent one to see if the problem re-appears.

It turns out that the problem now actually occurs after rebooting into 8130f3c1c2bb0e533b5e150c39911d6e61dcecc2. That revision was definitely good before, and I did reboot. So that confirms that there is some impurity going on (that goes both directions), but rebooting does not fix it. Not sure what does, but apparently at some point some switch was flipped for me.

[fatpat]

I have the same issue here with kitty (but with others packages like glxinfo, compton, ...)

the solution was to remove the package and to reinstall it ... don't ask me why

[Fresheyeball]

@fatpat that worked for me as a work around. I removed kitty from my configuration.nix, and instead installed it with nix-env now it works. Go figure.

[shyim]

Same for me :)

[Fresheyeball]

@shyim please don't close this. We still need to be able to install it without nix-env. A workaround is not a bug fix!

[maxkrieger]

FWIW my kitty actually was failing in my ~/.config/nixpkgs/config.nix (installed with nix-env) but worked when I installed it in my user packages (/etc/nixos/configuration.nix).

[dustinlacewell]

On unstable, no matter how I install it, I get

fast_data_types.FreeTypeError: Failed to load face, with error: cannot open resource
[251 06:40:21.964670] Failed to convert descriptor to face for symbol_map font

[vcunat]

That error seems very different; best put that in a separate issue.

[omidmnz]

I have the same problem, but not with just Kitty. Picom, among others is problematic too. The output of nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL has only one change between the working and broken configurations:

-OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7
+OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.9

[kenranunderscore]

I have the same problem, but not with just Kitty. Picom, among others is problematic too. The output of nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL has only one change between the working and broken configurations:

-OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7
+OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.9

I am experiencing the same issues, and it's also just this diff. It's preventing me from upgrading my system at the moment. I might try installing it with nix-env instead of with home-manager, maybe that helps. But it's generally undesirable.

[tbenst]

I'm experiencing this with Julia / Makie.jl as well.

using ModernGL, GLFW
window = GLFW.Window(resolution = (10, 10), major = 3, minor = 3, visible = false, focus = false)