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.
Related
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
I am using the applayout and OneUI 3.0.2 theme. I have pulldown menus in the banner (application and utility links) but the menu won't show up. Instead I get this JS error:
Uncaught lang.hitch: scope["_onKeyPress"] is null (scope="[Widget extlib.dijit.OneUIv302Menu, extlib_dijit_OneUIv302Menu_2]")
I have a Windows 9.0.1FP1 where these do work. On a 9.0.1FP1 Linux / 9.0.1FP2 Windows it doesn't work. The Linux machine had FP2 installed before I just downgraded it to FP1 (it was a test to see if this is the cause). But I noticed before that even after downgrading some files are still available - so a next test should be installing the machine completely from the scratch.
Double checked it this morning: another 9.0.1FP1 Win machine - everything working fine.
I also checked out that this only a OneUIv3.0.2 problem.
Do you know this issue?
A fix for this issue has been included in the latest XPages Extension Library (901v00_10.20141105-0922) on OpenNTF.
However, another issue was found in the dropdown mneu once it does appear successfully. Unfortunately a fix was not found for this secondary issue in time for the above ExtLib release. It has been logged as SPR# BGLN9PXG53.
Sometimes when running IntelliJ it completely blocks all keyboard inputs in the program. E.g. I can click around a document with the mouse, I can even right click + paste. I cannot, however write anything through the keyboard or navigate with the arrows inside a document or between documents for that matter.
The only keyboard related actions that work seem to be system related; alt + tab, ctrl + alt + delete, caps lock etc. also when tabbing to another window the keyboard works fine, so it is not a hardware issue.
This seem to occur when a popup is active and I tab out of IntelliJ and back in, but I am not certain that this is the case.
I would like to stress that it is not merely the currently open document that I cannot modify, since I CAN insert text and remove it using mouse commands only (the file is not write protected or anything like that), it seem to be a complete block of all keyboard inputs in IntelliJ.
The only workaround I have found is to restart IntelliJ.
I am running Ubuntu 13.10. More or less all projects I work with in IntelliJ are maven projects. It happens roughly once a day when using IntelliJ as main IDE.
This seems to be an IBus issue. The bug is not localized yet but it's clear it is not in IDEA - rather in IBus or possibly in Java X events handling code.
Workarounds:
IBus can be disabled for IDEA by unsetting env. variable XMODIFIERS. So, add the following lines to $IDEA_HOME/bin/idea.sh at almost the end of the file:
...
XMODIFIERS=idea.sh
export XMODIFIERS
# ---------------------------------------------------------------------
# Run the IDE.
# ---------------------------------------------------------------------
...
Have been reported that run ibus-daemon -rd is not recommended as it may cause JVM crash. However, it also seems to work.
http://youtrack.jetbrains.com/issue/IDEA-78860
I ran into the same issue with Ubuntu 14.04 LTS and IDEA 14+. I'm currently running IDEA 14.1.3.
The XMODIFIERS fix seemed to work for a while, but then the issue returned.
Changing Setup->Language->Keyboard input method system from iBus to none did not fix it for me.
What finally worked was switching JDKs from
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.14.04.2)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
to
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)
using
export IDEA_JDK=/home/don/apps/jdk1.7.0_75/
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.
I am having problems getting the GTK designer to work with MonoDevelop. I tried 2.4 on Arch Linux and it gave this problem. Then I tried 2.2 on OpenBSD and it gives the exact same problem. Both machines are 64bit.
Instead of having a window to drag things on I just have a blank square:
alt text http://img96.imageshack.us/img96/4766/monodevelop.png
The tutorials I've seen look similar to this though:
alt text http://monodevelop.com/#api/deki/files/142/=Stetic_Tutorial_06.jpg?size=bestfit&width=700&height=425
So what gives? With my blank square I can't drag anything onto it, not a VBox or other container even. It will not react to anything.
Am I missing some sort of GTK# configuration or what? I find it highly improbable that both OSs' packages I tried are broken. Also, I've attached a (huge) bounty to this because this is a pretty big issue for me.
The console output from the starting of Mono and including me trying to drag an element onto the gray box is here
Update
Ok, so I've finally gotten a bit closer to solving the mystery. I use Fluxbox as my window manager usually. Well I tried using both KDE and Gnome-Session and both of them cause MonoDevelop to work properly(though still missing the window border, you could at least drag components onto it). Now my question is what makes Fluxbox not work for it?
I have the same problem in openSUSE 11.3 x64 KDE using Mono JIT compiler version 2.6.7 (tarball Wed Jul 14 18:00:23 UTC 2010) downloaded from here
type -a monodevelop returns:
monodevelop is /usr/bin/monodevelop
monodevelop is /usr/bin/X11/monodevelop
Running monodevelop from terminal gives the following output
1)
WARNING: Cannot find Mozilla directory
containing libgtkembedmoz.so. Some
Addins may not be able to function.
Please set MOZILLA_FIVE_HOME to your
Mozilla directory.
This can be solved by adding an environment variable in your .bashrc file from your home directory.
export MOZILLA_FIVE_HOME='/path/to/libgtkembedmoz.so/directory/'
To find if that library exists on your systems use:
sudo find / -name libgtkembedmoz.so
-print
(from this bug report this library is contain in the Mozilla's XUL Runner package, but in newer versions I don't know if it's still there, I had to use libgtkembedmoz.so provided by Slickedit which was installed in /opt/slickedit/bin/mozilla/)
2)
WARNING [2010-07-29 20:22:37Z]: Inotify watch limit is too low (8192).
To resolve this problem read Inotify Watches Limit
3)
WARNING [2010-07-29 20:22:37Z]: Error creating composed icon gtk-execute___asm0__debug-overlay-22.png__SmallToolbar at size SmallToolbar. Icon __asm0__debug-overlay-22.png__SmallToolbar is 22x22, expected 16x16.
I get the exact same error using Monodevelop 2.4, and I think this could be either from a broken GTK# installation or from a bug in Monodevelop,
Your result is the same as mine, see here. I suggest compiling MonoDevelop from Github and/or using a newer version of gtk-sharp/gdk-sharp
This part
ERROR [2010-07-29 20:22:37Z]: GdkPixbuf-Critical: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed
appears in GTK and GDK crashes,
If this does not resolve the problem submitting a bug report is the next option. Although this is somehow strange, since I managed to complete the same tutorial using Kubuntu 10.04 LTS 64 bit a few weeks ago.
Uh, that is the designer. If the toolbox didn't show up, go to View->Pads->Toolbox to bring it up.
Note that this Gtk, you can't just drop a button or textbox on the design surface. You have to drop a container control first, and then can place buttons and such inside the container.
set global gtk theme to default
check all bindings depends
try start monodevelop from console and post output on pastebin
"Now my question is what makes Fluxbox not work for it? " remember the GTK protect was made for GNOME project, all the libraries are made to work on that Desktop. so need to see all the dependencies to run it property