MATLAB Answers

log in with keyboard on matlab R2018a not working no keys show on dialog

18 views (last 30 days)
Edwin Miller
Edwin Miller on 27 Apr 2018
Commented: Dale Ang on 17 Mar 2019
bring up matlab gui and click log in link in top left corner and dialog comes up but can't use keyboard?
running ubuntu 17.10

  3 Comments

Walter Roberson
Walter Roberson on 27 Apr 2018
What login link is that? The MATLAB GUI does not have a login link. Perhaps you are using MATLAB Mobile or MATLAB Online?
Dale Ang
Dale Ang on 13 Sep 2018
The login option is clearly visible at the top-right of the main matlab window. I'm having the same problem with not being able to type in the log in fields. Same problem is happening in appdesigner.

Sign in to comment.

Answers (10)

Damien S
Damien S on 18 Jul 2018
Have same problem, solution above does not work. Need help

  0 Comments

Sign in to comment.


Si Zhang
Si Zhang on 20 Jul 2018
my matlab couldn't even show the login and add-ons dialog. After I follow the https://www.mathworks.com/matlabcentral/answers/364551-why-is-matlab-unable-to-run-the-matlabwindow-application-on-linux, it was fixed. But the new problem is that I cant type anything in the login dialog. I'm using ubuntu 18.4 and matlab 2018a.

Edwin Miller
Edwin Miller on 27 Apr 2018
"log in" link in very top right corner shows this dialog box , but can't type into either input field, however the sign-in button works

  1 Comment

Sign in to comment.


Edwin Miller
Edwin Miller on 27 Apr 2018
yup that worked and now i can type into either username or password via the keyboard after the initial cntl-shift V into username

  1 Comment

Walter Roberson
Walter Roberson on 28 Apr 2018
I have a vague memory that I encountered a similar situation before, but unfortunately I do not remember the cause.

Sign in to comment.


Edwin Miller
Edwin Miller on 28 Apr 2018
i'm having problems also in help browser but just do shift-ctrl V and then you can imput in the editbox

  0 Comments

Sign in to comment.



Samuel Bechara
Samuel Bechara on 19 Aug 2018
I am having the same problem. This is especially frustrating when trying to use Appdesigner. It won't let me type using the keyboard. I can sometimes work around this by opening the help dialogue, typing a few letters in THAT input box, then going back to Appdesigner. It doesn't ALWAYS work though. Super frustrating.
This seems to be a Linux problem. I am using Manjaro 18 (I know it isn't supported) and MATLAB R2018a

  0 Comments

Sign in to comment.


Evgenii Semenov
Evgenii Semenov on 11 Sep 2018
I'm experiencing the same problem on archlinux. The workaround I have found is rather odd: I forgot about the open login window and after a while I was able to type in.

  0 Comments

Sign in to comment.


Rogier Delporte
Rogier Delporte on 13 Mar 2019
I'm having the same problem, I do sometimes get a fluke where I can add a couple of letters, but it's so intermittent that I cannot log in.
I've tried setting aside the libraries mentioned in https://nl.mathworks.com/matlabcentral/answers/364551-why-is-matlab-unable-to-run-the-matlabwindow-application-on-linux, but that did not help at all.
I'm running Ubuntu 18.10, kernel 4.18.0-16-generic, MATLAB version 9.5.0.944444 (R2018b).
I suspect that the following console output may be a clue:
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://assets.adobedtm.com/d0cc0600946eb3957f703b9fe43c3590597a8c2c/mbox-contents-95c6a4d9c82a8d20476522984666120b54192e9b.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://assets.adobedtm.com/d0cc0600946eb3957f703b9fe43c3590597a8c2c/mbox-contents-95c6a4d9c82a8d20476522984666120b54192e9b.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://assets.adobedtm.com/d0cc0600946eb3957f703b9fe43c3590597a8c2c/scripts/satellite-5672ffbd64746d5bd3002853.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://assets.adobedtm.com/d0cc0600946eb3957f703b9fe43c3590597a8c2c/scripts/satellite-5672ffbd64746d5bd3002853.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
It's something to do with slow connections. I am, however, on a very stable and broadband connection here at my university.
Does anyone get a similar output when running the following?
cd(matlabroot)
cd bin/glnxa64
!./MATLABWindow -url=http://mathworks.com --disable-gpu

  1 Comment

Rogier Delporte
Rogier Delporte on 13 Mar 2019
I also took a peek in my log files (using the gnome logs application, it's actually the /var/log/syslog file) and I found the following log message concerning matlab:
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6e00003 (MATLABWind)

Sign in to comment.


Rogier Delporte
Rogier Delporte on 13 Mar 2019
OK, I have a, admittedly VERY buggy workaround/symptom: as long as the addon explorer or the sign in window are not the top window, you can type in the textboxes.
So you open the sign in window with the button, put your cursor in the textbox, click on a different window and then you can type in or copy paste in your text.
Can anyone confirm that the bug has this quirky behaviour for them as well?

  1 Comment

Dale Ang
Dale Ang on 17 Mar 2019
My workaround sounds similar.
Setup: I use focus follows cursor I set a small gedit window set to Always on Top at the bottom of the screen approximately 2/3 from the left, mostly just showing the top bar of the window. This seems to be the best place for quick access and keeping out of the way.
Workaround:
  1. Click where the text will be
  2. Move the cursor over the gedit window until focus is obtained, then back to App Designer
  3. Type away. Use the cursor keys to navigate.
Text/keyboard input will until I need to use the mouse again. Rinse and repeat.

Sign in to comment.

Sign in to answer this question.