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

Screen not rendering on Intel graphics #8541

Closed
1 task done
themonglord opened this issue Nov 22, 2024 · 10 comments
Closed
1 task done

Screen not rendering on Intel graphics #8541

themonglord opened this issue Nov 22, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@themonglord
Copy link

Already reported ? *

  • I have searched the existing open and closed issues.

Regression?

Yes

System Info and Version

Hyprland 0.45.0 built from branch at commit dirty ().
Date:
Tag: , commits:
built against aquamarine 0.5.0

flags set:
debug

System Information:
System name: Linux
Node name: FreakyArchBTW
Release: 6.11.9-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Sun, 17 Nov 2024 16:06:17 +0000

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: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:
unknown: not runtime

Description

This has started happening after I updated hyprland to 0.45.1. Whenever I start hyprland (either via tty or sddm), the screen turns off and stays off. When I switch ttys and go back to the hyprland tty, it shows one frame and it freezes. I am running an Intel I5-6300u with a 520 integrated gpu.

How to reproduce

Start Hyprland (either via sddm or tty) on the cpu specified on v0.45.1 and above

Crash reports, logs, images, videos

No response

@themonglord themonglord added the bug Something isn't working label Nov 22, 2024
@vaxerski
Copy link
Member

@themonglord
Copy link
Author

ok, between 0.45.0 and 0.45.1 (where this started happening), it output:
[c4a77b8da7783d95345935cd2468d83cd54d182b] core: guard pmonitor in focuswindow

@vaxerski
Copy link
Member

I don't think you did it correctly if that's the output. Check the git head (latest git) and if it's bad, select that as bad and put 0.45 as good

@themonglord
Copy link
Author

between 0.45.0 and head
[83be2480c45bdead9110fdf137a1cd2f5a203378] workspace: fix missing name via focusworkspaceoncurrentmonitor (#8484)

@MightyPlaza
Copy link
Contributor

are you sure this couldn't be a aquamarine regression?
https://gitlab.archlinux.org/archlinux/packaging/packages/hyprland/-/commit/a6f593168059910617ec760ff3e49f9fbafdc787 was released a day before 0.45 on arch

@themonglord
Copy link
Author

themonglord commented Nov 23, 2024

it is aquamarine. i installed that version of hyprland and it still isn't rendering. pacman doesn't wanna downgrade aquamarine because it apparently breaks this "libaquamarine" dependency that hyprland uses.

edit: bisect for aquamarine between 0.4.5 and head
[3b00e96f90cb0040de6d88ad99bf5f4d443f0c59] drm: scan only cards and not outputs, safeguard against null renderer (#106)

@m4rch3n1ng
Copy link
Contributor

what version of mesa are you using @themonglord? i noticed the same, also on intel, when upgrading mesa to version 24.3.0 (and reported it to upstream mesa), and the fix for me was downgrading mesa to 24.2.7 (by, in my case, disabling the arch testing repos and running pacman -Syuu)

@themonglord
Copy link
Author

what version of mesa are you using @themonglord? i noticed the same, also on intel, when upgrading mesa to version 24.3.0 (and reported it to upstream mesa), and the fix for me was downgrading mesa to 24.2.7 (by, in my case, disabling the arch testing repos and running pacman -Syuu)

well i guess it was my mesa version. i was using amber instead of the main build. thank you

@m4rch3n1ng
Copy link
Contributor

i think it's still worth keeping this issue open, because hyprland is the only wayland compositor (that i tested) that is affected by this mesa issue, niri, sway, cosmic all work fine for me

@vaxerski
Copy link
Member

unless mesa can point to a culprit being hyprland doing something wrong, I disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants