How to Install Nvidia Drivers: problems with keyboard - console

I'm trying to install Nvidia drivers on an old version of Linux: CentOS 6.4. When I exit the X server with 'init 3', it puts me into a login prompt. However whenever I type anything, the keyboard input is messed up. 'r' becomes '^R', o becomes '^O', etc. Does this sound familiar?
If I modify /etc/inittab to boot into run level 3, I get the same problem. How can I fix this?

I have figured out a workaround for the problem. I had a few other USB devices on this PC. I disconnected those devices and the problem went away. I don't know exactly what caused the problem, but it works for me.

Related

Problem when deploying Qt app on Raspberry Pi 4 (Could not queue DRM page flip on screen HDMI1 (Invalid argument))

I've compiled Qt5.15.0 and set up cross-compiler on my host machine (Ubuntu 20.04) and managed to cross-compile a simple Hello World app for my Raspberry Pi 4, however, when I deploy and run it (tried both on Qt Creator and in terminal) I get Could not queue DRM page flip on screen HDMI1 (Invalid argument) I use latest Raspbian image and tried both with lite and full desktop versions.
There are some solutions suggesting to set the environment variables;
QT_QPA_EGLFS_ALWAYS_SET_MODE=1
QT_QPA_EGLFS_KMS_ATOMIC=1
But I had no luck with setting them.
I don't know where the problem is, I'm very new to Qt.
For those who has the same problem here is how I solved;
Somehow I discovered that Raspberry Pi does not set the environment variable QT_QPA_EGLFS_ALWAYS_SET_MODE. You can check that by typing
printenv QT_QPA_EGLFS_ALWAYS_SET_MODE
or
echo $QT_QPA_EGLFS_ALWAYS_SET_MODE
in both cases, you should see 1 as a result if you've set it so.
However I got no response when I typed them.
Then I went and opened .profile and added
QT_QPA_EGLFS_ALWAYS_SET_MODE=1
at the end of the file and rebooted the system. Finally there it was, when I echoed the variable it returned 1, and my programs now work pretty well.
The variables should be set in:
/etc/default/qt
See QTBUG-72539 in the Qt bug tracking.

Cannot find Arduino IDE VS Code

I am using windows and I installed the Arduino IDE from Microsoft store, but I wanted to code everything in VS Code. When I want to run the program or select the board it just says this:
Cannot find Arduino IDE. Please specify the "arduino.path" in the user settings. Requires a restart after change.
How can I fix this, where can I find the arduino.path?
Install PlatformIO extension for VS Code. It has Arduino framework and it works with all possible boards, and then some.
For me nothing could make Arduino IDE.app (2.0 beta) work. Switching to 1.8.6 (Arduino.app), putting that into my Applications folder (so the path is /Applications/Arduino.app) and setting the VSCode setting to:
"arduino.path": "/Applications/Arduino.app"
Fixed this error (and got me to select a board, which I was able to do with the command palette. Make sure to open the new non-beta Arduino.app and add any existing board manager jsons, such as esp32 in my case, that might have already been added to the beta Arduino. The libraries appear to already be in place.)
I also had to add this to my C/C++ settings for includePath:
${workspaceFolder}/**
/Users/<owen>/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/**
At this point "verify" began working. It was still pretty slow, and flashes the Arduino splash screen while running, so I'm now going to follow the platformIO advice and see if it's any better.
P.S. At first I also got an error about [Warning] Failed to generate IntelliSense configuration but think I fixed this by clicking the "don't show again" or similar on the popup that appeared in the lower left. (Similar errors show up on syntax issues, so could be related to that instead.)

LispWorks cannot open in OS X El Capitan

The app icon just keeps bouncing for a few minutes after I click it, and then stop and nothing is show. The app then becomes “Not Responding.”
According to the document, I should be asked to select GUI options, but that didn't happen during the installation process.
I think it has to do with GUI.
So I installed/updated X11, but it's still not working even after that.
I'm using the LispWorks 6.1.1 Personal Edition.
I contacted Lispworks' support team.
It turned out it's because my mac name has a non-ASICC char ' (it was XXX's Macbook Pro).
Changing the computer's name using sudo scutil --set HostName name-you want fixed the issue.

X Error: BadDrawable (invalid Pixmap or Window parameter) when launching Spyder on GNOME

sorry if this question is not as detailed and focused as it should be.
I am a Linux user (so no admin privileges of any sort) and just installed Anaconda3 from here and followed the instructions.
Note that my Linux machine is not connected to the internet, so I had to transfer the file through other means and just run bash Anaconda... as instructed in the Continuum site.
I have then succesfully launched IPython and tried to plot inline, without problems. However, when I tried to use plotting in windows, I got this kind of output from the terminal:
X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea)
And the created graph window was just blank.
I then tried to start Spyder and basically saw the same behaviour: a lot of those errors reported above, and the Spyder window just popped up blank.
Google search for the error gives results reported for Qt, which makes sense since when plotting "offline" (as opposed to inline) then QtAgg is used.
However, I have no clue as to where to look for the version of these libs, how to install/compile new ones, whether that is really the issue or not. I am just to ignorant about Linux.
Anybody can hint on what to look for and how to try to debug this behaviour?
I had the same error. What worked for me is to add this line in /etc/environment.
sudo nano /etc/environment
Add this line
QT_X11_NO_MITSHM=1
Source : https://github.com/P0cL4bs/WiFi-Pumpkin/issues/53#issuecomment-309120875
Note that in my case the fix didn't take effect until I rebooted my machine.
you may simply run on the terminal:
export QT_X11_NO_MITSHM=1
I had this same error, so I'll tell you what worked for me.
I think it is a permissions issue, based on the following:
I was logged in through a VNC server window through my account, but within the VNC server was setting up a user profile for "user2". In a 'user2' console I installed anaconda in user2's directory. When I typed spyder in the user2 console, I got the exact error you describe. I guessed the VNC desktop didn't like user2 trying to open a window on user1's profile. I then logged out of my VNC server window, logged into the user2 vnc server window, and in a console typed 'spyder' and it opened perfectly.
I think for some reason it is trying to open but is installed in a directory that you don't have permissions for or trying to open in a window that you don't have access to.

The Simulator can't be launched because it is already in use. Every run

I know this is an issue that was already discussed here many times before, But there is now solution for my problem and its really serious.
Every second time I try to run the simulator i get get this bothering message:
"The Simulator can't be launched because it is already in use."
Closing the simulator does not help.
I need to quit Xcode every single time this happens!
I trying restarting my computer several times.
Please help me, I find my self restarting Xcode 50 times a day. This is totally frustrating.
Very simple, to avoid further problems we will do "complete" procedure.
On iOS Simulator, you must force quit.
In Xcode, press COMMAND + SHIFT + "K" (letter k) keys; to empty the cache of the application and ensure that all works out.
On then quit Xcode (I recommend that you restart your Mac after this procedure done, if the problem persists)
Good luck
I had the same issue. Turned out that the developer tools path was set to a different location than the Xcode I was using. So check with
xcode-select -p
that your dev tools path is set correctly. If not, fix with
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer/
if you're using the current AppStore version of Xcode (or the appropriate path to your alternate Xcode).
I think it a bug in Xcode 5.1. Update your Xcode and it will resolve your issue
and i use this solution for this issue. "Close all application from background and then run"
To close application from background use
Select simulator then press "Ctrl+Shift+H+H" So it open background task screen in this close all application from background and then run your application from Xcode.
i hope this will solve you lots of time of restarting the Xcode.
Solution that seems to be working :
double press CMD+Shift+H (in simulator )
close All other apps on
sim.
Works for me. Let me know!:)

Resources