Closed postsolar closed 5 months ago
have you checked ~/.hyprland
?
If there are no crash reports, this is not a crash but a regular, user-triggered exit.
Does this happen on the default config?
have you checked ~/.hyprland?
I don't have this directory at all.
If there are no crash reports, this is not a crash but a regular, user-triggered exit.
Is it more of a terminology thing? Hyprland crashes with a freeze and visual defects, which doesn't look like normal exit at all.
Does this happen on the default config?
I'm now going to test that too, but in the meanwhile, here's what I get with Hyprland 2> hypr.log
DRI driver not from this Mesa build ('24.0.2' vs '24.0.1') failed to bind extensions DRI driver not from this Mesa build ('24.0.2' vs '24.0.1') failed to bind extensions DRI driver not from this Mesa build ('24.0.2' vs '24.0.1') failed to bind extensions
That's definitely bad.
These lines are coming immediately after the launch, and then Hyprland can run fine for anywhere between a few minutes and an hour so before crashing again.
My nvidia card is GeForce 940MX and the driver version is 550.54.14, and it's on an optimus laptop, with Intel being the iGPU. NixOS is currently configured in offload mode. I currently don't set any graphics-related env vars in my Hyprland config.
Currently running with almost no config (kept just the keybindings), will report when/if it happens again.
Yeah same with almost empty config
DRI driver not from this Mesa build ('24.0.2' vs '24.0.1')
failed to bind extensions
DRI driver not from this Mesa build ('24.0.2' vs '24.0.1')
failed to bind extensions
DRI driver not from this Mesa build ('24.0.2' vs '24.0.1')
failed to bind extensions
Environment variable $QT_QPA_PLATFORMTHEME not set, ignoring.
Environment variable $QT_QPA_PLATFORMTHEME not set, ignoring.
ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
109826
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
This time there appeared a crash report:
yeah this is a problem on your end, possibly due to the mismatched drivers.
If anyone comes here from google, I got it resolved by rebuilding Hyprland. It didn't work when I updated to 0.36 because that did not involve a full rebuild.
Hyprland Version
System/Version info
```sh Hyprland, built from branch at commit f115ba94d2ec6e093c94f425535b027bc570185e (). Date: 2024-03-01 Tag: flags: (if any) System Information: System name: Linux Node name: nixos Release: 6.8.0 Version: #1-NixOS SMP PREEMPT_DYNAMIC Sun Mar 10 20:38:09 UTC 2024 GPU information: 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) os-release: ANSI_COLOR="1;34" BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues" BUILD_ID="24.05.20240312.cfd86f9" DOCUMENTATION_URL="https://nixos.org/learn.html" HOME_URL="https://nixos.org/" ID=nixos IMAGE_ID="" IMAGE_VERSION="" LOGO="nix-snowflake" NAME=NixOS PRETTY_NAME="NixOS 24.05 (Uakari)" SUPPORT_URL="https://nixos.org/community.html" VERSION="24.05 (Uakari)" VERSION_CODENAME=uakari VERSION_ID="24.05" plugins: hy3 by outfoxxed ver 0.1 ```Bug or Regression?
Regression
Description
No idea what could've caused it, but after a reboot today I'm experiencing crashes all the time. I neither updated nor changed anything in my configuration.
There is no pattern to the crashes. They happen after 1-30 minutes of using Hyprland. I tried the following (in no particular order):
How to reproduce
.
Crash reports, logs, images, videos
There are no recent logs in
~/.cache/hyprland
, and the logs in/tmp/hypr
do not contain actual errors or crash reports, they stop atUsing config ...
line.The error printed on the TTY contains something along the lines of
Exiting due to channel error
. Sorry for so little info, I will try to grab the whole output and attach it the next time it happens.