Top of screen empty after upgrading to 0.53

More or less what the title says. Some 30px are just empty.
Any open clients will not draw on that part of the screen.
My monitor config is

monitorv2 {
    output = DP-1
    addreserved = 0,0,0,0
    mode = 2560x1440@75
    position = 0x0
    scale = 1
    }

Removing waybar which is located on top, makes no difference.

I can rectify it by issuing
hyprctl keyword monitor DP-1, addreserved 0,0,0,0

Is it some sort of a glitch or am I missing something from my part?

uhhh that sounds like your wallpaper being somehow pushed with reserved, which shouldn’t happen.

Are you sure you dont have some rogue addreserved somewhere? Check hyprctl monitors

I tried converting wallpaper from png to jxl. No dice.
I removed the wallpaper completely (disabling the system user service). Nada.

hyprctl monitors output

Monitor DP-1 (ID 1):
[email protected] at 0x0
description: Philips Consumer Electronics Company PHL 275V8 UK02236015959
make: Philips Consumer Electronics Company
model: PHL 275V8
physical size (mm): 600x340
serial: UK02236015959
active workspace: 1 (1)
special workspace: 0 ()
reserved: 0 74 0 0
scale: 1.00
transform: 0
focused: yes
dpmsStatus: 1
vrr: false
solitary: 0
solitaryBlockedBy: windowed mode,missing candidate
activelyTearing: false
tearingBlockedBy: next frame is not torn,user settings,missing candidate
directScanoutTo: 0
directScanoutBlockedBy: user settings,missing candidate
disabled: false
currentFormat: XRGB8888
mirrorOf: none
availableModes: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
colorManagementPreset: srgb
sdrBrightness: 1.00
sdrSaturation: 1.00
sdrMinLuminance: 0.20
sdrMaxLuminance: 80

I can see the

reserved: 0 74 0 0

No clue from my side.
This occurred after the 0.53 upgrade. No issues before.
Waybar is set to 40px. Changing to auto makes no difference. Removing waybar still produces the same gap at screen top.

What a puzzle !

Edit:
To make it more challenging.
Toggling the output to my Samsung TV, works just fine.
Toggling once again to the monitor works properly with no reserved space on top.

well something surely must put that 74 there.

It is actually 34. The size of waybar is 40.

I checked, rechecked, β€œgrep-ed”, you name it. I hit the wall.

I don’t want to bother you anymore with that. The workaround in autostart works just fine. If I find the culprit, I 'll post it.

Thanks for the suggestions, be well.
Wishing you Happy New Year.

@vaxry

Happy New Year.

After today’s update of plugins, one failed to build (don’t really remember which one, I think hyprexpo). It strike me that the cause of the reserved space on top is a plugin.
Disabling all plugins eliminates the reserved area.

I had enabled 3 plugins. Namely
hyprexpo
hyprfocus
xtra-dispatchers (this one works just fine)

And one more major thing came up.
I am using uwsm to login (from .profile). No display manager.
Terminating the session with

uwsm stop
or

loginctl terminate-user β€œβ€

returns a core dump.

systemd-coredump[1717]: [πŸ‘•] Process 1111 (Hyprland) of user 1000 dumped core.

                                             Stack trace of thread 1111:
                                             #0  0x00007f029c321106 _ZN10Aquamarine7CLogger3logENS_16eBackendLo>
                                             #1  0x00007f029c35008d _ZN10Aquamarine13SDRMConnector10disconnectE>
                                             #2  0x00007f029c350216 _ZN10Aquamarine13SDRMConnectorD1Ev (libaqua>
                                             #3  0x00007f029c3623cb _ZN9Hyprutils6Memory14CSharedPointerIN10Aqu>
                                             #4  0x00007f029c342a60 _ZN10Aquamarine11CDRMBackendD1Ev (libaquama>
                                             #5  0x00007f029c35a9ae _ZN9Hyprutils6Memory14CSharedPointerIN10Aqu>
                                             #6  0x00007f029c315be2 _ZN10Aquamarine8CBackendD1Ev (libaquamarine>
                                             #7  0x00007f029c31649b _ZN9Hyprutils6Memory14CSharedPointerIN10Aqu>
                                             #8  0x00007f029c330df5 n/a (libaquamarine.so.9 + 0x8fdf5)
                                             #9  0x00007f029b4406bc __cxa_finalize (libc.so.6 + 0x406bc)
                                             #10 0x00007f029c2fb048 n/a (libaquamarine.so.9 + 0x5a048)
                                             #11 0x00007f029c456012 n/a (ld-linux-x86-64.so.2 + 0x2012)
                                             #12 0x00007f029c45a16e n/a (ld-linux-x86-64.so.2 + 0x616e)
                                             #13 0x00007f029b440c71 n/a (libc.so.6 + 0x40c71)
                                             #14 0x00007f029b440d4e exit (libc.so.6 + 0x40d4e)
                                             #15 0x00007f029b42763c n/a (libc.so.6 + 0x2763c)
                                             #16 0x00007f029b4276e9 __libc_start_main (libc.so.6 + 0x276e9)
                                             #17 0x00005645911f4b65 _start (/usr/bin/Hyprland + 0x243b65)
                                             
                                             Stack trace of thread 1144:
                                             #0  0x00007f029b51872d syscall (libc.so.6 + 0x11872d)
                                             #1  0x00007f029ac7582e g_cond_wait (libglib-2.0.so.0 + 0x8f82e)
                                             #2  0x00007f029ac0c1cd n/a (libglib-2.0.so.0 + 0x261cd)
                                             #3  0x00007f029ac7e487 n/a (libglib-2.0.so.0 + 0x98487)
                                             #4  0x00007f029ac7d8bc n/a (libglib-2.0.so.0 + 0x978bc)
                                             #5  0x00007f029b49698b n/a (libc.so.6 + 0x9698b)
                                             #6  0x00007f029b51a9cc n/a (libc.so.6 + 0x11a9cc)
                                             
                                             Stack trace of thread 1143:
                                             #0  0x00007f029b51872d syscall (libc.so.6 + 0x11872d)
                                             #1  0x00007f029ac7582e g_cond_wait (libglib-2.0.so.0 + 0x8f82e)
                                             #2  0x00007f029ac0c1cd n/a (libglib-2.0.so.0 + 0x261cd)
                                             #3  0x00007f029ac0c23d g_async_queue_pop (libglib-2.0.so.0 + 0x262>
                                             #4  0x00007f029b2a051c n/a (libpangoft2-1.0.so.0 + 0xc51c)
                                             #5  0x00007f029ac7d8bc n/a (libglib-2.0.so.0 + 0x978bc)
                                             #6  0x00007f029b49698b n/a (libc.so.6 + 0x9698b)
                                             #7  0x00007f029b51a9cc n/a (libc.so.6 + 0x11a9cc)
                                             
                                             Stack trace of thread 1145:
                                             #0  0x00007f029b49f002 n/a (libc.so.6 + 0x9f002)
                                             #1  0x00007f029b49316c n/a (libc.so.6 + 0x9316c)
                                             #2  0x00007f029b4931b4 n/a (libc.so.6 + 0x931b4)
                                             #3  0x00007f029b50d9f6 ppoll (libc.so.6 + 0x10d9f6)
                                             #4  0x00007f029ac46784 n/a (libglib-2.0.so.0 + 0x60784)
                                             #5  0x00007f029ac46865 g_main_context_iteration (libglib-2.0.so.0 >
                                             #6  0x00007f029ac468b2 n/a (libglib-2.0.so.0 + 0x608b2)
                                             #7  0x00007f029ac7d8bc n/a (libglib-2.0.so.0 + 0x978bc)
                                             #8  0x00007f029b49698b n/a (libc.so.6 + 0x9698b)
                                             #9  0x00007f029b51a9cc n/a (libc.so.6 + 0x11a9cc)
                                             
                                             Stack trace of thread 1147:
                                             #0  0x00007f029b49f002 n/a (libc.so.6 + 0x9f002)
                                             #1  0x00007f029b49316c n/a (libc.so.6 + 0x9316c)
                                             #2  0x00007f029b4931b4 n/a (libc.so.6 + 0x931b4)
                                             #3  0x00007f029b50d9f6 ppoll (libc.so.6 + 0x10d9f6)
                                             #4  0x00007f029ac46784 n/a (libglib-2.0.so.0 + 0x60784)
                                             #5  0x00007f029ac46a17 g_main_loop_run (libglib-2.0.so.0 + 0x60a17)
                                             #6  0x00007f029bd522e4 n/a (libgio-2.0.so.0 + 0x11a2e4)
                                             #7  0x00007f029ac7d8bc n/a (libglib-2.0.so.0 + 0x978bc)
                                             #8  0x00007f029b49698b n/a (libc.so.6 + 0x9698b)
                                             #9  0x00007f029b51a9cc n/a (libc.so.6 + 0x11a9cc)
                                             
                                             Stack trace of thread 1146:
                                             #0  0x00007f029b49f002 n/a (libc.so.6 + 0x9f002)
                                             #1  0x00007f029b49316c n/a (libc.so.6 + 0x9316c)
                                             #2  0x00007f029b4931b4 n/a (libc.so.6 + 0x931b4)
                                             #3  0x00007f029b50d9f6 ppoll (libc.so.6 + 0x10d9f6)
                                             #4  0x00007f029ac46784 n/a (libglib-2.0.so.0 + 0x60784)
                                             #5  0x00007f029ac46865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865)
                                             #6  0x00007f02880347be n/a (libdconfsettings.so + 0x77be)
                                             #7  0x00007f029ac7d8bc n/a (libglib-2.0.so.0 + 0x978bc)
                                             #8  0x00007f029b49698b n/a (libc.so.6 + 0x9698b)
                                             #9  0x00007f029b51a9cc n/a (libc.so.6 + 0x11a9cc)
                                             ELF object binary architecture: AMD x86-64

β–‘β–‘ Subject: Process 1111 (Hyprland) dumped core
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: systemd-devel Info Page
β–‘β–‘ Documentation: man:core(5)
β–‘β–‘
β–‘β–‘ Process 1111 (Hyprland) crashed and dumped core.
β–‘β–‘
β–‘β–‘ This usually indicates a programming error in the crashing program and
β–‘β–‘ should be reported to its vendor as a bug.
~

How would you like me to proceed?

expo was just fixed.

loginctl thing will be fixed in the next aquamarine release iirc. Oh well, that dump isn’t critical, you were exiting anyways.

Can you check which plugin causes this?

@vaxry

hyprpm list
β†’ Repository hyprland-plugins (by hyprwm):
β”‚ Plugin borders-plus-plus
└─ enabled: false

β”‚ Plugin csgo-vulkan-fix
└─ enabled: false

β”‚ Plugin hyprbars
└─ enabled: false

β”‚ Plugin hyprexpo
└─ enabled: Plugin failed to build

β”‚ Plugin hyprfocus
└─ enabled: false

β”‚ Plugin hyprscrolling
└─ enabled: false

β”‚ Plugin hyprtrails
└─ enabled: false

β”‚ Plugin hyprwinwrap
└─ enabled: false

β”‚ Plugin xtra-dispatchers
└─ enabled: true

As you can see hyprexpo fails to build (tried that repeatedly).

And hyprfocus is causing the reserved space on top of the screen.

No issues with xtra-dispatchers.

huh, expo should’ve been fixed. I’ll look into why focus does this.

both build and work fine for me. Are you sure you ran hyprpm update and restarted hyprland?

Yes I ran hyprpm update.
Yes restarted rebooted.

I even purged cache and rebuild the plugins.

I will give it another shot again tomorrow and let you know.
It’s kinda late now in my part of the world.

@vaxry

Updated once again to the latest plugins build.
xtra-dispatchers
–Works fine

hyprfocus still with addreserved 34
–Works fine

hyprexpo builds with no errors.
–Works fine and surprise once enabled the addreserved vanishes.
If disabled the addreserved issue, caused by hyprfocus, returns.

at this point I feel like you just have ghosts in your computer

1 Like

Hyprwitchcraft.

The x11 curse for abandoning it.