-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
QGIS 1.8 crashes when attempting to specify CRS #16343
Comments
Author Name: Maxim Dubinin (@simgislab) Do you use custom CRS? Try this:
|
Author Name: Maxim Dubinin (@simgislab) related #16349 |
Author Name: Maxim Dubinin (@simgislab)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Charles Petersen (Charles Petersen) Fix proposed by Maxim Dubinin: "1. open regedit solved the problem described in my original bug report 7370, 16 March 2013. Большое спасибо! |
Author Name: Sandro Santilli (@strk) Charles, do you mean the bug is now fixed in master ? |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Maxim Dubinin (@simgislab) Sandro, Giovanni, as I understood, no, Charles thanked me for the solution that involved editing registry. But the problem is still there. See #16349 I guess both this ticket and #16349 should be closed when it is fixed. Seems like an easy fix, btw) |
Author Name: Charles Petersen (Charles Petersen)
Original Redmine Issue: 7370
Affected QGIS version: master
When running QGIS 1.8 Lisboa, @QtCore4.dll@ causes program crash when attempting to specify CRS for layer or project on two separate Windows 7 platforms (one Win7 Professional and the other Win7 Home Premium). The problem does not occur when running QGIS 1.8 on a Windows XP Professional platform. Diagnostics already performed: disabled McAfee realtime scanning and reinstalled QGIS; deleted @.qgis@ folder and reinstalled QGIS with new @.qgis@ folder; searched for other versions of @QtCore4.dll@ on computer with negative results (i.e., the version in @C:/Program Files (x86)/Quantum GIS Lisboa/bin@ is the only one on my computer. Good luck!
Related issue(s): #16349 (duplicates)
Redmine related issue(s): 7377
The text was updated successfully, but these errors were encountered: