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 when clicking on magnifier spinbox #23489

Closed
qgib opened this issue Sep 14, 2016 · 7 comments
Closed

Crash when clicking on magnifier spinbox #23489

qgib opened this issue Sep 14, 2016 · 7 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Sep 14, 2016

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 15566
Affected QGIS version: 2.16.3
Redmine category:unknown
Assignee: Sandro Santilli


This happens when starting with --configpath, also on a clean dir.
Confirmed on 2.16.2 and 2.17, Debian. See https://lists.osgeo.org/pipermail/qgis-developer/2016-September/044628.html for details and gdb output.

@qgib
Copy link
Contributor Author

qgib commented Sep 15, 2016

Author Name: Denis Rouzaud (@3nids)


Fatal: ASSERT failure in Job::startRender(): "pre-set DPI not equal to
painter's DPI (10 vs 9.6)", file
/tmp/buildd/qgis-2.17.0+git20160806+cb02b9f+13jessie/src/core

The DPI in QgsMapSettings is a double to allow small magnification scale
(i.e. zoom out) while QPaintDevice::logicalDpiX is an integer.

https://github.com/qgis/QGIS/blob/master/src/core/qgsmaprenderercustompainterjob.cpp#L73
This means that the application will crash if in Debug mode (not in
Release mode)

I am not sure if we can safely remove this.
Martin, may you have a look here?

@qgib
Copy link
Contributor Author

qgib commented Sep 17, 2016

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Just as input: when I do NOT use the --configpath option (so using the 'normal' settings from ~/.qgis2 and Qt stuff from ~/.config/QGIS
all is ok, and I can use the magnifier ok.

Looks like something is set in the 'normal' config, which apperently is not avaialbe in a fresh config?

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2016

Author Name: Nyall Dawson (@nyalldawson)


  • priority_id was changed from Normal to Severe/Regression

@qgib
Copy link
Contributor Author

qgib commented Oct 18, 2016

Author Name: Sandro Santilli (@strk)


How about rounding to closest integer ?


  • assigned_to_id was configured as Sandro Santilli
  • fixed_version_id was configured as Version 2.18

@qgib
Copy link
Contributor Author

qgib commented Oct 18, 2016

Author Name: Sandro Santilli (@strk)


I could reproduce in final-2_16_3-97-gb779a6a and 2.17+ (f289ef3).
Could not reproduce in 2.14 branch, althought eh assertion is there too (maybe DPIMaxSetting was not a double back then?)


  • version was changed from 2.16.2 to 2.16.3

@qgib
Copy link
Contributor Author

qgib commented Oct 18, 2016

Author Name: Sandro Santilli (@strk)


Fixed in changeset "acf74a6539a015dc5ae3e948c43163e01dde2d3d".


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Sep 22, 2017

Author Name: Jürgen Fischer (@jef-n)


  • category_id was configured as Unknown

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 25, 2019
@qgib qgib added this to the Version 2.18 milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
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!
Projects
None yet
Development

No branches or pull requests

1 participant