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

Crash for QGis MacOs #57925

Closed
2 tasks
Christophe-Wacheux opened this issue Jun 28, 2024 · 3 comments
Closed
2 tasks

Crash for QGis MacOs #57925

Christophe-Wacheux opened this issue Jun 28, 2024 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@Christophe-Wacheux
Copy link

What is the bug or the crash?

QGis crashes when you set up extremal values for visualisation of a raster file, using pseudo-color of a unique given band. If, during the set up, you put the same value for min and max values, QGis crashes immediately.

I am a MacOs user, so I hope this bug is only for MacOs, but in any case, if you can fix it for everyone (including MacOs ^^) this would be great !

Cheers

Steps to reproduce the issue

  1. Open a raster .tif file with QGis
  2. Right-click on it in the list of layers, and click on "Properties..."
  3. Go to symbology, and choose "Pseudo-color with unique band". You should get something like this :
    image
  4. In the image above, Min is set to 5, Max is set to 10. If the Min is set to 10, or the Max is set to 5, QGis crashes immediately. You don't even need to apply it to the raster.

Versions

Version de QGIS 3.34.7-Prizren Branche de code de QGIS Release 3.34
Version de Qt 5.15.12
Version de Python 3.12.4
Version de GDAL/OGR 3.9.0
Version de Proj 9.4.1
Version de la base de données du registre EPSG v11.006 (2024-03-13)
Version de GEOS 3.12.1-CAPI-1.18.1
Version de SQLite 3.46.0
Version de PDAL 2.7.1
Version du client PostgreSQL unknown
Version de SpatiaLite 5.1.0
Version de QWT 6.1.6
Version de QScintilla2 2.13.3
Version de l'OS macOS 14.3
       
Extensions Python actives
FreehandRasterGeoreferencer 0.8.3
SemiAutomaticClassificationPlugin 8.2.2
ee_plugin 0.0.6
profiletool 4.2.6
extractor 1.2
Serval 3.32.0
pointsamplingtool 0.5.4
qgis-maptiler-plugin 3.3
valuetool 3.0.19
raster_tracer 0.3.3
processing 2.12.99
grassprovider 2.12.99
db_manager 0.1.20
MetaSearch 0.3.6

Version de QGIS
3.34.7-Prizren
Branche de code de QGIS
Release 3.34
Version de Qt
5.15.12
Version de Python
3.12.4
Version de GDAL/OGR
3.9.0
Version de Proj
9.4.1
Version de la base de données du registre EPSG
v11.006 (2024-03-13)
Version de GEOS
3.12.1-CAPI-1.18.1
Version de SQLite
3.46.0
Version de PDAL
2.7.1
Version du client PostgreSQL
unknown
Version de SpatiaLite
5.1.0
Version de QWT
6.1.6
Version de QScintilla2
2.13.3
Version de l'OS
macOS 14.3

Extensions Python actives
FreehandRasterGeoreferencer
0.8.3
SemiAutomaticClassificationPlugin
8.2.2
ee_plugin
0.0.6
profiletool
4.2.6
extractor
1.2
Serval
3.32.0
pointsamplingtool
0.5.4
qgis-maptiler-plugin
3.3
valuetool
3.0.19
raster_tracer
0.3.3
processing
2.12.99
grassprovider
2.12.99
db_manager
0.1.20
MetaSearch
0.3.6

Supported QGIS version

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

New profile

Additional context

No response

@Christophe-Wacheux Christophe-Wacheux added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jun 28, 2024
@agiudiceandrea agiudiceandrea added the Feedback Waiting on the submitter for answers label Jun 29, 2024
@agiudiceandrea
Copy link
Contributor

@Christophe-Wacheux, thanks for reporting. The issue doesn't occur on my Windows 10 system using ether QGIS 3.34.8 or QGIS 3.38.0 using one of my raster layers.
How did you install QGIS on your macOS system? Did the crash generate a crash report?
Please try if the issue occur also using a new QGIS user profile and please provide a sample raster layer with which the issue occur.

Copy link

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 github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Jul 14, 2024
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

2 participants