Skip to content
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

[BUG] hyprland 2.9.7.0 crashing after todays update #515

Open
Koushikg88 opened this issue Dec 6, 2024 · 8 comments
Open

[BUG] hyprland 2.9.7.0 crashing after todays update #515

Koushikg88 opened this issue Dec 6, 2024 · 8 comments
Assignees
Labels
bug Something isn't working to be confirmed Issue is currently under review and has not been released

Comments

@Koushikg88
Copy link

Describe the bug
after doing system update if rebooted, hyprland is not openning and sending bck to login screen

To Reproduce
Steps to reproduce the behavior:

  1. get latest update
  2. reboot the system
  3. loging to hyprland
  4. See error

Expected behavior
A clear

Distribution (please complete the following information):

  • Arch Linux
@Koushikg88 Koushikg88 added the bug Something isn't working label Dec 6, 2024
@Koushikg88
Copy link
Author

hyprlandCrashReport28295.txt
thiss is the crash report

@Haraven
Copy link

Haraven commented Dec 7, 2024

Tl; dr: If you have this line in your Hyprland config:
env = LIBGL_ALWAYS_SOFTWARE,1
try removing it.

In ML4W, it's a configuration option found under the ~/.config/hypr/conf/environments/kvm.conf. If you're using the KVM environment preset or parts taken from it, that might be the culprit.


I had the same issue: after updating, I could no longer boot into Hyprland.

I found no real solutions online, but a Reddit post mentioned trying to run Hyprland without a config to see if it works that way. For me, running without a config meant commenting out everything in ~/.config/hypr/hyprland.conf.

I did that, and surprisingly, Hyprland launched. So, what I did was to go back to ~/.config/hypr/hyprland.conf and to uncomment the configs, line by line, until I found the issue. In my case, the issue was caused by an environment variable from the KVM preset that ML4W comes with (~/.config/hypr/conf/environments/kvm.conf). The line causing the crash was:
env = LIBGL_ALWAYS_SOFTWARE,1

I commented that line and Hyprland launched just fine after that.

@Koushikg88
Copy link
Author

Yes, thats right, I did the same you did and its working for me too. Thanks for help.

@mylinuxforwork
Copy link
Owner

@Haraven @Koushikg88 Thanks for testing. So, you’re running the dotfiles in KVM and you removed this environment variable and then it works again?

@mylinuxforwork mylinuxforwork added the to be confirmed Issue is currently under review and has not been released label Dec 7, 2024
@Koushikg88
Copy link
Author

@Haraven @Koushikg88 Thanks for testing. So, you’re running the dotfiles in KVM and you removed this environment variable and then it works again?

Yes, I have commented that particular line in kvm.conf inside environments folder and its working fine.

@Haraven
Copy link

Haraven commented Dec 9, 2024

@Haraven @Koushikg88 Thanks for testing. So, you’re running the dotfiles in KVM and you removed this environment variable and then it works again?

I have ML4W installed on bare metal. I was using the environment variables from kvm.conf, under the assumption that it helps with performance when I need to run my W11 VM inside Hyprland. When I removed the environment variable, Hyprland started working again.

Are we supposed to only use the KVM variables when we're running ML4W inside a VM? 🤔

@degobbis
Copy link

Nice Info!
Solved my issue on Hyprland: hyprwm/Hyprland#8666

@mylinuxforwork
Copy link
Owner

@Haraven @Koushikg88 Thanks for testing. So, you’re running the dotfiles in KVM and you removed this environment variable and then it works again?

I have ML4W installed on bare metal. I was using the environment variables from kvm.conf, under the assumption that it helps with performance when I need to run my W11 VM inside Hyprland. When I removed the environment variable, Hyprland started working again.

Are we supposed to only use the KVM variables when we're running ML4W inside a VM? 🤔

Yesm The KVM environment should only be used in a VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working to be confirmed Issue is currently under review and has not been released
Projects
None yet
Development

No branches or pull requests

4 participants