LASTools doesn't run in QGIS 3.2 on WIN because of encoding - qgis

I have a problem with LASTools in QGIS 3.2. I installed plugin, activated it in processing menu with correct path.
I tried to run lasview (I did the same process a day ago on ubuntu with WINE and everything was good), but I got only errormessage now. I check path for strange signs, but I can't seee nothing. In picutre you can see where error occure.
Picture of error log:

I encountered the same problem.
I changed paths: in options\treatments\treatment providers\LASTools peak default to C:\LASTools; I point back to ..\qgis\python\processing\plugins\processing\lidar (lidar : folder created by myself where extracting the original file lastools.zip).
Then everything worked.
Qgis 3.8 zanzibar ; lastools 201909

Related

SQL Developer 4.2.0 does not load

Jeez, how hard is it to get SQL Developer to work.
Last month I downloaded the latest version and kept getting the cannot find ‘msvcr100.dll’ file error.
So I reverted back to an old version I had installed.
Now I have downloaded the latest version 4.2.0.
1 The first time I tried to launch it I was asked to set the JDK path. So I set it to ‘C:\Program Files\Java\jdk1.8.0_121’. Is this correct??
2 When I launch SQL Developer I get the initial splash screen, the progress bar does not get half way, and then it vanishes.
3 I went into the folder sqldeveloper\sqldeveloper\bin and amended the file ‘sqldeveloper.conf’ i.e. SetJavaHome C:/Program Files/Java/jdk1.8.0_121
I still get the splash screen and then it vanishes.
Anyone with any ideas.
Cheers
I experienced the same problem with the version with the built-in JDK and finally got it to work by:
1) Removing all other versions of Java from the system
2) Commenting the line under the #Set our usage tracking URI line in the sqldeveloper.conf file (sqldeveloper/sqldeveloper/bin)
Not sure which one did the trick but hoping this helps someone else.

mscorlib.dll is an invalid CIL image

I downloaded the new beta version of Unity (5.5.0b2) and when I open any project I always get an exception in the console that says:
The file C:\Program Files\Unity 5.5.0b2\Editor\Data\MonoBleedingEdge\lib/mscorlib.dll is an invalid CIL image
I really don't have any clue to what this means and what to do about it, I can't even enter play mode, any advice on how to solve this?
I'm currently on Windows 7 64 bit, the Unity version installed is 64 bit, too, I tried installing it on the main hard drive and the secondary but the error is still there.
I installed version 5.4.0f3 and replaced the folder MonoBleedingEdge of the version 5.5.0b2 with the one found in the previous version.
The folder is located at Unity 5.5.0b2\Editor\Data.

Getting "Error: Failed to connect to OmniSharp"

I'm trying to get VSCode working with my Unity projects, and every time I select the Project icon (the little fire at the bottom) I get the following error:
Error: Failed to connect to OmniSharp
Is anyone else getting this?
You need to download the most recent version of "mono". Open up terminal and pass in brew install mono. Then "Pick a project" and select the ..-csharp.sln file and you should be up and running.
Ok, made some progress and gotten a few Unity projects working. It seems that you need some prerequisites installed, a clean up of your Unity project folder, and possibly some hand editing of your .sln and .csproj files.
I posted a (possibly) better answer over on Reddit. Hope that's not breaking stack etiquitte.
http://www.reddit.com/r/Unity3D/comments/34d6gc/visual_studio_for_mac_help_us_vote_for_unity/
i get this on windows when my project directory has a space in it
i removed the space and removed the error
i expect it will be fixed soom
I have a completely different answer: it's the runtime that VSCode is using. It doesn't match up with what it thinks it needs. I have to remember that we're still in beta and that things are changing rapidly. I had my dnvm running beta 7, but VSCode (and OmniSharp, by extension) is looking for beta 6, so it was failing. I updated my runtime using this this post as a clue. Now I have VSCode 0.7.0 using the beta 6 runtime. I have no idea how to tell what it's looking for...I just guessed based on when they were both released. HTH

Pydev 3.0 + Eclipse + Google App Engine Debugging not working

I've been having problems getting debugging working with this setup for the past year. Supposedly, this is fixed in the latest versions, but I just can't seem to get it to work.
I'm using Mac OSX 10.8.5, Eclipse Keplar, PyDev 3.0.0, and Google App Engine 1.8.8.
I set up a run configuration to point to dev_appserver.py, running my project. That works fine. My python version is 2.7.3, and everything works in normal mode. When I try to run in debug mode, however, the app runs, the output specifically states:
pydev debugger: starting
pydev debugger: google app engine integration enabled
But after 20 seconds, the python process terminates with this error message:
'Launching New_configuration' has encountered a problem.
Timed out after 20.0 seconds while waiting for python script to connect.
Accept timed out
Execution works during those 20 seconds, because I can hit URLs connected to my app and see an effect. Breakpoints do not work, though. Is there something I need to do to get python to 'connect'?
Also - I should note that switching back to using 'old_dev_appserver.py' fixes this problem - debugging works fine when I do this. But, this is not really a solution, because I need to use the latest socket additions in the newer releases.
Thanks for any advice.
temporary solution:
edit the pydev_app_engine_debug_startup.py file:
eclipse/plugins/org.python.pydev_${VERSION}/pysrc/pydev_app_engine_debug_startup.py
change the line that reads:
if ':' not in config.version_id:
to:
if ':' not in config.version_id or config.version_id.startswith('default:'):
Looks like this is fixed in 1.9.0. I also had to make sure to update PyDev to the latest (3.3.3 at the time of this writing).
One more thing to add, and this one really tripped me up (on MacOS) -
In Eclipse, under Run -> Run Configurations, set the Main Module to point to this location:
/usr/local/google_appengine/dev_appserver.py
NOT the symlink:
/usr/local/bin/dev_appserver.py
Well, finally I found the answer. It is a Google's bug.
It has been reported and acknowledged.
see Debug is not working with PyDev again 1.8.8!
Update: Until the bug is fixed I am using PyCharm. The pro version has 30 days trial and works with GAE. It works like, well, a charm. I may even consider switching to it from Elicpse/PyDev
But I am used to JetBrains tools with Android Studio recnetly, and WebStorm and Resharper in the past, so I know to find my way around their IDEs. Your milage may and will vary.
Since the question, a new GAE has been released 1.8.9
Running GAE 1.8.9 with PyDev3.3.3 on Windows8.
This timeout issue still occurred.
When I entered the temporary workaround changes to pydev_app_engine_debug_startup described in the earlier answer, then the browser could not connect to the app.
However, on backing out this change, not only did the 'Launching New_configuration' not appear, but the breakpoints worked.
More info on the Python Tool Support for the App Engine Development Server is here
https://docs.google.com/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit

phpmyadmin blank screen after installing Zend server

I installed LAMP on Ubuntu 12.0.4 LTE. Then I installed phpmyadmin. Everything was good. I used phpadmin to do lots of DB administration....
Then I installed Zend CE server. Now, phpmyadmin throws a blank page. No login screen.
So, I reinstalled my VPS in the same sequence again. No luck. Same behavior.
This time, I installed Apache, Mysql, PHP and Zend server in that order. Then I installed phpmyadmin....Unfortunately, still blank page on phpmyadmin.
Any help?...Thanks in advance.
First, for all those that posted their suggestions to my above issue, thanks!.
Of course, I had to dig deeper into forums and threads to find the specific root cause and solution for this issue.....and after spending few hours...finally, I resolved it!. Thanks to the following bug discussion link on php.net.
https://bugs.php.net/bug.php?id=25876
I tired many suggested fixes there but they didn't help. The suggestion that finally fixed the problem was pasted below ( so that let the credit go to the right owner):
[2011-03-03 12:18 UTC] comments at htmlcompressor dot com
If you are gettin the following error:
"Fatal error: session_start(): Failed to initialize storage module: files (path: ) in...."
Make sure that you have setup the session save path in your php.ini:
session.save_path = "/tmp"
which seems to be disabled by default.
I swear using Open Source software is tough!. I have spent whole day on this issue alone. My goal was to build some software and I have yet to get to it!!.