After installing macOS Big Sur beta my terminal behaves weirdly.
If I start terminal after PC restart I can start terminal just fine, however if I close it and try to start again I find myself at blank terminal saying "login".
I get the same problem with iTerm and native Terminal.
I'm having this issue as well.
This discussion from the Apple Developer Forums explains the issue and the solution.
Found the trigger, it's an iTerm2 thing.
Disable Enable session restoration under Preferences > Advanced > Session, after that you shouldn't have a problem.
Raised an issue with iTerm's developers. Not sure if there's something here on the OS side as well.
I had this issue on Mojave as well, both on iTerm and Terminal. The solution was to restart my machine.
Related
Before I updated both QT and Xcode on my mac, my computer just stopped opening up the terminal when I went to run my code. It had worked for months and is still enabled as my default on QT. I Tried uninstalling and reinstalling both QT and Xcode, but my terminal still will not open when I run the code. When I disable terminal as my default, I can see my output at the bottom of my screen in QT, but I would like it to open in terminal. Any suggestions?
Someone on https://forum.qt.io found the solution, thank's so much to him !
A .dmg archive with a corrected QtCreator version 7.0.1 from the snapshot downloads is available here: https://download.qt.io/snapshots/qtcreator_qt5/7.0/7.0.1/134/
After installation, the terminal opens correctly
I have a bit of a technical question here. Since upgrading to OS Catalina I have tried running my Xpress Workbench files and a warning pops up saying "It can't be opened because Apple cannot check for malicious software." When bypassing this and opening it anyway it produces an error whenever I run some code:
"spawn mosel ENOENT"
Has anyone else experienced this? and what does the error mean? I have been in touch with Apple support but they weren't that helpful, I have also been in touch with FICO (the developer of the programme) and they haven't experienced the problem before but are getting in touch with their dev team.
Any help would be much appreciated.
Ben.
I also got this issue when i upgraded my macOS to Catalina. I couldn't run my mosel programs successfully.
In Catalina, any software installed outside of the Mac App Store is now checked every time it runs for malware and other problems. You can solve this by un-quarantining the Xpress workbench application.
Run this code on terminal of your mac - xattr -r -d com.apple.quarantine "/Applications/FICO Xpress" (specify the location of the application in the quote).
It should be fine after this.
I am using Oracle vm with windows as host machine and linux on VM. I had everything working, but once i used 'power off' when it took time to start. Since i am not able to start the OS on VM. I am getting errors as below.
Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment RedHat_Linux_64bit_4GB --startvm 42e4c558-83d4-431c-a971-71ca9e1f4112 --no-startvm-errormsgbox "--sup-hardening-log=C:\Users\bhargav.vijay.desai\VirtualBox VMs\RedHat_Linux_64bit_4GB\Logs\VBoxHardening.log"' (rc=-104)
where: supR3HardenedWinReSpawn
what: 5
VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
I am able to see a file in snapshots folder which is large in size. (2016-08-16T05-57-16-295692800Z.sav). Have uploaded an image. I am on lookout for solutions.
Restart of the system helped me resolve the issue. Also the snapshot files (.sav extensions) are of no use in this case.
This ref https://forums.virtualbox.org/viewtopic.php?f=6&t=82277 fixed issue for me for VB version 5.2.x on Windows 10.
I had tried other approaches like installing earlier versions of VB but nothing else worked for me.
I had the same problem on a new HP Elitebook with Windows 10 preinstalled.
Install Virtualbox and import applience worked fine, and can be startet.
But after next restart of the System Virtualbox always shows an Error...
... supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
I tryed 4 Days to fix the Problem inclusive deactivate preinstalled hp client security, windows defender etc.
Nothing worked until I found the Link of the latest post.
I had to reinstall Virtualbox and deactivate the VBoxdrv sevice in the registry.
After every Windows start i need to start the service manualy or over shedule...
After that Virtualbox starts correctly!
I tested a lot. Windows seems to destroy the Virtualbox installation while driver was loading on startup.
If the error occures once, one has to reinstall Virtualbox and deactivate the service... deactivate after the Error has already showen dosent work.
I was struggling with this one on HP Elite Book for some time and I found solution here.
The solution is to go to
HP Sure Sense -> Settings -> Advanced Settings
and turn off Enhanced Thread Protection.
It's not my solution, but I hope it's good to have here for someone in the future.
a) Clear AppData/Local/Temp
b) Completely uninstall any VirtualBox currently installed
c) Restart the computer
d) Install the latest version of VirtualBox
e) After install completes do not restart the computer
f) Open the registry editor. Start > Run > regedit
Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
Edit the key called Start. Change it's value from 1 to 3
g) Close the registry editor and restart your computer. After your computer restarts you should be able to use VirtualBox without any issues.
I see the following error whenever I try to debug "Cross Platform" under "C++" category: "Unable to start debugging. Unexpected GDB output from command "-target-select remote :5039". Remote connection closed"
I've installed all of the contents when I downloaded Visual Studio 2015 community and I ran it on Windows 10 Pro which supports Hyper-V.
I've been searching a solution for this and I've found an assumption:
"What is your debug target, the VS Android Emulator? When we saw this before it turned out to be a bad emulator image. Do you have this problem with all targets (e.g. if you try a physical device) or just one?"
In my case, I just tried this via Emulator(VS Emulator 5" Lolipop (5.0) XXHDP Phone (0x86 -...)
So I've sent an Email to VS 2015.
And the answer was like this:
"Sorry for the delay in responding we were looking at an emulator image of another user that ran into this problem so I was waiting until we had the results of that investigation to report back. We actually were not able to find anything wrong the emulator itself, our current hypothesis is that it is a network or adb problem interfering with GDB’s ability to connect to GDB server on the remote machine. Do you see this error every time you try to debug, or if you reboot the emulator will it work sometimes right after the reboot? Next time you see the error, can you open the emulator’s console mode by going go the Hyper-V manager and double clicking the emulator. Then find the location your app installed to and run “gdbserver --version" from the app path and let me know what it says? This will validate if the correct version of gdbserver is on the device."
So we are trying to solve this problem but I'm also asking here just in case.
Is there anyone who has magical solution for this problem?
I'll put a comment on this if I figure out how to solve this.
Thanks in advance.
** Following answer is from the manager of Visual Studio 2015:
You are only the second person who has run into this issue, and the first person that ran into it provided their everything works correctly when we run their .vhd on our machines so it appears to be some strange problem where gdbserver (which comes from the Android NDK provided by Google) crashes only when running on certain machines. Unfortunately the .vhd you provided does not appear to be the correct one it won’t boot for me. You can see the .vhd file being used by the emulator if you look under the settings of the emulator in your Hyper-V manager. .However given we got the other person’s .vhd you can hold off providing any additional information at this point. I’m waiting to hear back from the emulator team on if they have any ideas since this appears to be an issue only on specific machines since.
If you don’t mind my asking, if you don’t have a background in computers what inspired you to try C++ on Android? That scenario will be significantly more complicated than doing Java on Android.
It's been almost two months since I got this answer but I haven't got any additional response from them yet. So, I ended up quitting developing an application by using VS2015.
If you run into this problem, there are only two ways to go. Change your computer or stop developing application via VS2015.
If the project name contains spaces, the whole remote debugging fails. Visual Studio also creates weird paths. When checking out the "Blink1 for Raspberry Pi" template, I named the Project "Blink1 for Pi", which resulted in a path like this:
~/projects/Blink1?/for/pi/PI/for/pi....
And all the debugging failed. When I recreated this keeping the project name "Blink1", everything worked fine. It's a pity, that spaces aren't handled here...
I'm trying to debug a crash in a full-screen Mac game I'm working on, but when I have LLDB attached it just causes the game to freeze when the crash happens, and I can't get away from the game - I need to do a hard reset on the computer. Is there any kind of tool or preference for doing this? The computer I'm using to reproduce the crash doesn't have multiple monitors.
Can you do two-computer debugging? Set up an ssh account on the game-running machine, log in to it remotely (command line in Terminal) from your not-game-running machine, run command line lldb on your game. (process attach -n <appname>)
In the past, with gdb, Xcode had support for "remote debugging" which was this arrangement (Xcode running on one Mac, your full-screen game on the other) assuming you already had ssh configured correctly. I don't believe Xcode currently supports remote debugging with lldb - I'd encourage you to file a bug report at http://bugreport.apple.com/ registering your need for this feature if it's something you need in your workflow.
I'm afraid I can't think of any answers for you off-hand if you're doing single-machine debugging.