Sorry, this is solved, I just had to set
git config --global https.proxy
why this was not retained when upgrading from 16.04 or why it needs now
to be set (the $https_proxy environment variable is correctly set) is
still a problem though.
--
You received this bug notification because you are a
Public bug reported:
I just updated from 16.04 to 18.04 beta.
This is the error message I get when I try to clone a repo:
fatal: unable to access 'https://github.com/xxx/y.git/':
gnutls_handshake() failed: An unexpected TLS packet was received.
I cannot clone repositories on intern
As a matter of fact, I just checked the bug happens with scilab,
available in universe. Scilab returns some interesting debug info in the
standard output, which O copy in the attached text file.
NEW INFO.
I didn't see before that matlab was generating a crash log for this. This log
confirms that
I will try. For the moment I double boot 16.04 because I need to have it
working, but I can run tests on spare time. Because I couldn't find
problems when not running the java machine of Matlab I will focus on
applications relying heavily on java. If you have any suggestion it
would help. Thanks a
1- Yes Matlab works as expected without going through ssh.
2- Repeat the above but first do a "ssh -X localhost" triggers the
problem.
3- Both scenarios hold regardless of how I login ("Ubuntu", "Ubuntu on
Xorg" or "Unity").
As you mentionned the DISPLAY variable I checked the following (maybe i
Dear Andreas,
It was tried in all three modes.
Furthermore how do I enforce Xorg when I log from another machine (in my case a
windows running Xming) to this one ?
I suspect once I connect through ssh with X11 forwarding, the session is Xorg.
Thanks for your time.
--
You received this bug n
Public bug reported:
OBSERVED BEHAVIOR:
Matlab stays in busy state when using some functions like "plot" or even
"exit", while executing through a ssh tunnel with X11 forwarding.
REPRODUCE THE BUG:
You need matlab (my version is R2017a) to reproduce the bug. I suspect
any version >= 2014b woul
I actually managed to get it working by calling:
gksudo gedit
After that, I can't reproduce the bug anymore.
Calling gedit (without gksudo and through any launcher or in terminal) works
perfectly now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
I am running Ubuntu 16.10, with gedit 3.22.0 on it. Whenever I try to
have gedit running, I obtain the following output:
ViolaciĆ³n de segmento (`core' generado)
Which is spanish for "Segmentation fault (core dumped)" I guess.
dmesg returns:
[ 1596.185619] gedit[11005]: segf