Stop keyboard becoming unresponsive on Pycharm startup - ssh

Symptoms:
When starting Pycharm:
the keyboard seems completely unresponsive
the cursor disappears
menu items with keyboard bindings are greyed out
text selection still works with the mouse, but the cursor is not visible
This may be related to another SO question "pycharm with ideavim occasionally makes the keyboard unresponsive" but ideavim is not involved.
Set-up:
remote desktop connection to a Windows 7 64-bit computer
Windows machine has Xming running as a X-window server
Using PuTTy to ssh tunnel into a Linux box running SuSE 11.3
Pycharm v4.0.5
JRE 1.7.0
Further Details
switching between tabs in Pycharm doesn't fix this
no cursor is visible in the console, python, or editor windows
switching to another X-window (xclock) doesn't help
switching to another non-X-window doesn't help either
re-starting Pycharm doesn't help
sudo ibus restart, see issue 78860 on my flavor of linux doesn't do anything

Working fix:
Turn off the 'Tip of the day' start-up dialogue box, then re-start Pycharm.
I can confirm that it works as a fix to my specific problem.
It sounds like there's a known problem with the cursor disappearing: see issue 65637 and issue 79312. Based on my experience it seems that this problem can also be caused when Pycharm pop-up windows steal focus.
Hope this is useful to some other folks out there.

I am using pycharm in ubuntu and this thing worked for me. Just run this command in terminal. I don't even restarted. It worked.
$ ibus-daemon -rd

Related

x2go issue with XFCE and Ubuntu 20.04

When I connect x2go with XFCE Ubuntu 20.04 (KVM VM) after ~10 minutes of idle time, x2go will lose its mouse focus and keyboard focus and there is no way to grab control of the session. Even restarting x2go will not bring the focus back.
The XFCE VM is still running because I can see the top output in the console.
I tried several key combinations to bring the focus back but it does not. I tried LXDE and it does not have this issue. I tried XFCE desktop 20.04 on its running in a KVM VM. I also tried installing Ubuntu server 20.04 and load Xubuntu-desktop (KVM VM) - the same issue. After ~10 minutes the x2go session-focus is lost.
What brings the session focus back is if I reboot the VM and then connect to the VM again using x2go. as I mentioned just restarting x2go will not bring the session focus back.
I tried uninstalling the screensaver and the power management features in XFCE but that did not fix this issue.
Update: this x2go bug report log suggests its screensaver related. Using the applications/settings/screensaver allowed me to turn off anything related to the screensaver, solving the problem for me. Issue appears to be solved here similarly: askubuntu forum
I've been having the same issue w/ XFCE and LXDE both after an idle period (10-15 minutes), and only on Ubuntu 20.04, not on 18.04 or earlier. In either desktop env, the session was not recoverable and required termination of the session either from the client side or via a separate terminal ssh session to kill <PID> the x2gocleansessio process on the server side (after seeing it was running using top). For a short period, I regained control in the new session until the cycle recurred.
Seems like a major problem for x2go in Ubuntu 20.04.
Just to save everyone the time of digging through the AskUbuntu forum... run this + restart and you should be good to go on Ubuntu 20.04 -
sudo apt-get remove xfce4-screensaver
If your are login via x2go and don't want to uninstall xfce4-screensaver, it's hard to solve the problem because there are intern script of xfce who launch xfce4-screensaver whatever you told him to do. I found my own workaround WITHOUT root privilege:
First activate screensaver on start-up :settings-manager -> Session and Startup->check screensaver(that sound weird but by this way you are sure to launch your xfce4-screensaver localy otherwise it's the root user who launch it which this own startup file which you can't edit without root)
Second : in ~/.config/autostart/xfce4-screensaver.desktop (if it doesn't exist uncheck then check screensaver in first step). Add to the end of this file:
Exec=sh -c "kill $(pgrep -u <YOUR-USERNAME> screen)"
This will launch it but auto-kill it after OnLogin
Edit: it's better than uninstall it because in my case that was the administrator that install for every user xfce4-screensaver so I can't uninstall it because the computer need a screensaver on the real sessions (I mean not in ssh on the physique machine). Maybe switch to Xscreensaver or other screensaver will solve this problem

Shift+Enter not working in edit mode in JupyterLab

When in edit mode in JupyterLab on my Win 10 machine, the Shift+Enter shortcut to execute the current cell does not work. The shortcut still works in command mode and no other keyboard shortcuts seem to suffer from this issue. The problem appeared overnight and I can't think of anything that could have caused it (the only change I have made to my system since yesterday was to uninstall my antivirus). I have tried disabling my extensions in Chrome, but that did not solve the problem.
The issue is limited to JupyterLab -- in Jupyter Notebook, Shift+Enter works in both edit and command mode.
Would appreciate any input.

VSCode through Mobaxterm cannot be moved, resized or maximized

I'd like to try out VSCode. I code usually on Qt Creator on a remote machine with Ubuntu/Debian, which I access through Mobaxterm (ssh) with X11 forwarding on Windows. I installed the latest VSCode (code_1.30.1-1545156774_amd64.deb), and I ran it with code, but I can't maximize the window or move it in anyway. The maximize button is completely unresponsive and doesn't do anything. Trying to drag the window or resize it by hand also doesn't do anything.
Is there some configuration to do to make it do these things?
Just found the answer:
https://github.com/Microsoft/vscode/issues/65232#issuecomment-449010667
in ~/.config/Code/User/settings.json
"window.titleBarStyle": "native"
if the file doesn't exist, create a new one with this line:
{ "window.titleBarStyle": "native" }

Using Enthought Canopy over SSH+Putty Fails to Start

I have Enthought Canopy installed on a machine running RedHat Enterprise Linux 5. I installed it successfully and can verify it runs.
I would like to be able to use it remotely from a windows computer, I have installed putty + xming for X11 forwarding. I can use regular applications like gedit and firefox fine. However when I try using canopy by launching ~/Canopy/canopy an empty gray box for the welcome screen appears, disappears after a few moments, and canopy exits with no return error without having started.
When I ssh with X forwarding from another linux computer, I can use canopy just fine.
There is no error code, I don't see any debug flags and I can't find any log files. I really have no idea why I cant access canopy with putty and xming.
I am trying this as a solution for interns so they can use a machine with access to our datafiles from their windows computers.
I highly appreciate any and all help.
Canopy needs some features not provided by XMing and a few other X server implementation on windows. See the following article for more details:
https://support.enthought.com/entries/21873380-Running-Canopy-Linux-via-remote-display-VNC-remote-X-display-
In short, use MobaXterm ( http://mobaxterm.mobatek.net/ ) or VcXSrv ( http://sourceforge.net/projects/vcxsrv/ )
EDIT: newer versions of Canopy have fixed this bug and should work fine with XMing

Ubuntu 12.04 key bindings not working in IntelliJ Idea 12

I've installed the latest version of IntelliJ Idea Community Edition (12.0.1) and I have problems with key bindings there. I am using Ubuntu 12.04 LTS with Unity.
None of them, where a letter is involved (ctrl-a, ctrl-c, ctrl-v) are working in Idea. And they are working in all other applications.
I can copy/paste text in Idea with mouse and it shows me that key bindings for this are ctrl-c/ctrl-v, but they are just not working.
I have no idea what is the problem, so any help will be appreciated.
Usually such kind of problem is because of non-English keyboard layout being first in a list of layouts in OS settings. Try to reorder them.
I just experienced the same problem after installed 14.0.3. It seemed due to Tools > Vim Emulator was checked. The problem was resolved after uncheck it.