Raster Calculator not working 3.34.10

[Pippo-90]

What is the bug or the crash?

Starting from today I am experiencing a series of problems with the raster calculator, even for the simplier task.
The final output has wrong values, geometry and geolocalization.
This is how it looks now:

This is how it should look/be

Steps to reproduce the issue

1. Go to "raster calculator" under the toolbar
2. write the formula to calculate the Top of Atmosphere radiance (TOA): 0.0003345 * Band 10 +0.10000 -0.29
3. Either click or not to "Use Selected Layer Extent" --> it gives problem in both cases
4. Save output layer as "TOA"

Versions

3.34.10

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[DelazJ]

@Pippo-90 it may help to share your dataset, so that people can reproduce the error.

[agiudiceandrea]

@Pippo-90, you reported that the issue occurs "starting from today": have you update to a new version or installed a different version of QGIS or have you installed / uninstalled / updated any external plugin, or have you made other changes to your QGIS installation configuration, or have you changed the tool (there are various raster calculator tools, which one have you used exactly?) or the parameters or the input layer used?

Moreover, other than providing a sample layer and exact parameters and detailed steps in order to replicate the issue, as requested in the previous comment, please try if the issue does occur also using a new QGIS user profile and please provide the QGIS full version info ("In the QGIS Help menu -> About, click in the table, Ctrl+A and then Ctrl+C. Finally paste here. Do not make a screenshot.")

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.