We have a very bizarre situation that I can't seem to find a solution to online. When opening and using a terminal window on a Mac, a repetitive "~7" is being typed. I've attached a screenshot where I've tried to interrupt it with a Ctrl+C but to no avail. The same behavior does not occur if I open a text editor or any other program - just the terminal env has this problem. Does anyone have any idea what's happening?
Here's a screenshot of the OS and all other details:
Related
I'm currently writing a Snake in C++/ncurses, and my Ctrl+C has suddenly stopped working when inside the game. The fun thing, tho, is it still works outside of it (so when I'm just in the terminal) and it ALSO WORKS when I compile the code on another laptop.
It's just this pc that encountered this issue. Randomly.
What could it be?
Checked terminal settings and reverted code changes.
Tried using different terminals.
For reference (and screenshot): https://support.google.com/chrome/thread/60700949?hl=en
OS X 10.11, Macbook Air 2015. I just updated Chrome from a slightly earlier 84.x.x.x to 84.0.4147.89. Upon launching the app now, I get a completely blank gray window without even a URL bar. The death-wheel spins and then it crashes. I've never seen a legitimate app behave this way in 30 years.
Launching from terminal I see this:
[0723/152018.747279:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7fff54e1d000, 0x2000): (os/kern) invalid address (1)
[2084:34307:0723/152018.992135:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
From what I've read, the flags --no-gpu and/or --disable-gpu are no longer valid in the latest "stable" release. Here are the flags I've thrown at it so far:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --args --use-gl=swiftshader --disable-gpu --disable-software-rasterizer --no-sandbox --no-xshm --no-gpu --disable-accelerated-compositing --disable-gpu-compositing
Does anyone know if there's a config file I could modify or some way of getting it to launch without hardware acceleration? Not truly a coding question but it's driving me nuts. Filed this on the Chrome Help site and got no responses.
You may try to open chrome://settings/?search=hardware in your browser and then turn off Use hardware acceleration when available.
I have written an app for OSX (Sierra) in Go (lang) with the GUI powered by the Golang QT binding therecipe/qt. When I build the app and run it from the command prompt with command open $(pwd)/myapp.app I get a terminal output while its running, and everything works fine.
When I double click on the app in finder to run it, I obviously don't have access to the console to see debugging, but in parts of the app that work fine in the GUI when I run from console (clicking on things, etc), it crashes the app when run by clicking on it.
I realise people don't know what the app is, and without seeing where in the app it crashes, they can't help me. What I am after is some ideas about debugging it, for instance:
Outputting logs to a text file and tailing the text file to watch as it is written to
Connecting a debugger to the application by the process, perhaps I can discover where it crashes. This doesn't sound straight forward
Is there a way to attach to a console of an application run like this to see what it is outputting?
Any ideas appreciated.
Thanks
The little red 'stop' button is disabled in my Anaconda-installed RStudio: I cannot use it to stop either a running Shiny app or dashboard and I cannot use it to interrupt Sys.sleep(30). I already reported this to RStudio and they confirmed that this behavior is unexpected, here. Has anybody else run into this? Any workarounds?
I installed vmware on my Window 8.1 HP Envy x360 PC in early december. Late december I noticed it was difficult using it as help files of any application in use just keeps sprouting up. Even when there are no applications in the window help files window shows up few minutes after a restart.
I tried many suggestions online: removing HP redundant programs, Cleaning the system of malware and spyware, reviewing/disabling accessibility settings, still no luck. I later learnt from someone's comment on one forum that he noticed this happened on his pcs with vmware installedI finally had to display window key since the behaviour was as though the window key was perpetually pressed down such that typing letter "n", "e" or the "delete" key opens the help file of the program in use or those of windows.
Now with window key disabled the situation relatively better as I can read on the pc and do some programming task; but I still get the randow opening of help files when I click "n", "e" or "delete" keys (imagine how difficult it is to type in MSWord under this situation). The exception is that this doesn't occur while using Firefox.
Any idea what's going on?
I discovered the behaviour was a mimicking of window shotcuts involving the window key. So to temporarily solve this (since I didn't want to uninstall vmware) was to disable window key. I found some registry script at http://johnhaller.com/useful-stuff/disable-windows-key which I used.
This helped but when using certain programs (chrome and MSWord) typing any of n, b or delete key launches the help file so I used AutoHotKey - autohotkey.com to write lines of script to disable any SHIFT key shortcut combination