Want to contribute, Found two Bugs.

[TimaDub]

Repos I am interested in contributing to

I am ready to contribute to every bug I will find myself.
I already fixed a bug for window gestures once. It did get merged.
So I know how this ecosystem works, and I am always ready to test some builds on my hardware and on different processor architectures.
I want to proceed with contributing, because I am a true supporter and fan of Hyprland !
I am also interested in contributing to xdg-desktop-portal-hypland because I see some issues, and this is what matters for me.
Could also look into fixing bugs and developing aquamarine.
And if one day u will consider adding Vulkan backend, I am in. (Yes, I saw what you said about it. I am just saying)

I am also sad how I can't use my C/C++ knowledge, because I love some low level stuff and I do a lot of Esp32 programming, but I think I am more into Kernels, Modules and so on.

What I want to contribute right now

I want to fix a bug I encountered for a past few weeks. It's about compositor crashing while screen sharing. The logic is completely described in PR. Also as I'll say bellow, I will also fix the blur bug I found.

Why the above bug / feature specifically?

Hi !

This fix is about a crash I couldn't ignore, my whole session dies every time I power-cycle my monitors while sharing a window, six times in the last two weeks, so I dug into the code to find out why. The code I wrote is supposed to fix it.

hyprwm/Hyprland#15782

I explained the issue in the PR, Also I must mention, that screen share will be dropped any ways, the fix is only about the compositor not crashing.

I also found another major issue that no one has been talking about, it's about blur effect, found it while updating my packages.

So, I already grant one major fix, and the crashing issue fix

I acknowledge that:

• I have read the AI Usage Policy and agree to follow it.

• I have read the Code of Conduct and agree to follow it.

• I wrote this request with my own hands, my own keyboard, and in my own words.

[vaxerski]

the linked MR is clearly AI generated, this is what the vouching system was desgined to prevent.

[vaxerski]

You are nuking your trust by doing this. In a world of AI slop, I can no longer take your word for "I understand it", especially when you have no outside credibility. I see clearly AI generated code and I have to shoot it down, because at this point you will just try to hide AI.

You clearly did not read the AI policy, and you broke it. Thus, I have no choice but to be assertive and say: no.

[TimaDub]

Ok.. Ahh.. I hate that, cuz it will take longer to close the issues but ok. Thanks

[TimaDub]

How is the code AI generated.. than pls just fix the issue, I'll also make an issue on the forum about issues I found in blur logic, I will just write purposal code there.

[TimaDub]

@vaxerski Tell me, what if I do get some proves like projects on GitHub, which are made without AI, and maybe some day later may I reapply ? Cuz I could just make another account, but what's the point of lying.

[vaxerski]

you can partake in the community, help others, or start by actually reading the ai policy and following it. You can also simply open bug report discussions for your problems or upvote if there already is one for the issue.