Gaijin not even bothering to fix linux bug reports?

[brick2928]

So there has been a bug on the native Linux client that hasnt been fixed for around 2 months, or 3 months if you count the WIP client.

https://community.gaijin.net/issues/p/warthunder/i/DHtd4gDRHbGZ

The issue is scrolling on the map Spams “Attention to the grid square”. It happens each scroll tick and its extremely annoying. This has been accepted around 2 months ago but from what I can tell Bug reporting manager 1 is not the devs themselves but some other people who simply check the issues website for valid reports. I think this is a pretty big issue and I am not the only one affected as you can tell from the count of people who have clicked “You have the same issue” (40 as of now)

Is this bug never going to be fixed…? People say using proton compatibility layer fixes it but if we are going to use proton why have a native client in the first place?? Native client has tons more issues like the exception error which crashes the game like 6 times through out a 8 hour gameplay run.

https://community.gaijin.net/issues/p/warthunder/i/2j3qayijZ8Qy

This is a good example of a bug that is still yet to be fixed as you can see its still a issue:

(for people who dont understand, war thunder isnt supposed to appear as X at the bottom, its supposed to have the war thunder logo)

I think i kind of screwed over the bug report by stating “this does not happen with the production client” in the original post, as when i posted this i was on the WIP client but after the major update it also moved onto the production client. I fear devs might have seen that and just thought that this issue only exists with dev client and nevermind it.
Can we have some mods contact devs about this maybe to take a look??? I know linux community is way too smal to put any meaningful resources on but at least regular bug fixes shouldnt be a too big of a hassle…

[Timo_YT]

An accepted report normally means the issue passed initial validation; it does not necessarily mean a fix has been scheduled or that an ETA can be published. However, if the report still says it affects only a development/WIP client while the same behavior now occurs on production, that is important new evidence.

I would update the existing report with a fresh .clog, system information, desktop environment/display protocol, GPU driver version and exact production-client build. Keep the map-scroll issue and the exception/crash issue in separate reports because they may have unrelated causes. For crashes, include the crash ID and terminal output where available. Confirming whether native Linux still fails while the same installation works through Proton is useful diagnostic evidence, but it should be documented as a workaround rather than proof of the root cause.