I used version 24.3.1 before. Some my script run emacsclient -c by the schedule when monitor is off to save power: everything was ok. But there is a problem with new version 24.4.1 - emacs freezes until the monitor is on (by keboard or mouse) and only after that it wakes up and creates frame.
GNU Emacs 24.4.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.4.2) of 2014-10-21 on kairos
Linux kairos 3.7.0-030700-generic #201212102335 SMP Tue Dec 11 04:36:24 UTC 2012
Ubuntu 12.04 64 bit
Related
I am trying to launch jconsole on Ubuntu 18.04 installed on WSL(Windows 10).
But it is just hanging there, like waiting for another input or argument.
/usr/lib/jvm/java-8-openjdk-amd64/bin$ ls -lrt jconsole
-rwxr-xr-x 1 root root 6336 Apr 16 02:48 jconsole
/usr/lib/jvm/java-8-openjdk-amd64/bin$ file jconsole
jconsole: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=ca8e0f8d1da13af7e272d6ac57781cab9d197b95, stripped
/usr/lib/jvm/java-8-openjdk-amd64/bin$ jconsole
<cursor blinking>
/usr/lib/jvm/java-8-openjdk-amd64/bin$ sudo jconsole
<cursor blinking>
Windows version:
C:\Users\username>ver
Microsoft Windows [Version 10.0.17763.1158]
Any help is appreciated, thanks!
Attempting remote development with VSCode 1.43.2 hosted on Darwin 18.7.0.
SSH target is a Raspberry Pi3 running raspbian jesse.
uname -a reports "Linux 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux"
gcc version is gcc version 4.9.2 (Raspbian 4.9.2-10+deb8u2)
The remote server code installed automatically but fails to start with the following error messages.
> Server did not start successfully. Full server log at /home/pi/.vscode-server/.0ba0ca52957102ca3527cf479571617f0de6ed50.log >>>
> /home/pi/.vscode-server/bin/0ba0ca52957102ca3527cf479571617f0de6ed50/node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /home/pi/.vscode-server/bin/0ba0ca52957102ca3527cf479571617f0de6ed50/node)
> /home/pi/.vscode-server/bin/0ba0ca52957102ca3527cf479571617f0de6ed50/node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /home/pi/.vscode-server/bin/0ba0ca52957102ca3527cf479571617f0de6ed50/node)
> <<< End of server log
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6 exists on the Pi.
What do I need to do to get it working?
The version of your C++ standard library (libstdc++.so.6) is simply too old, a newer version is required to run VSCode Server.
You could probably add some backports or third-party repositories to upgrade it, but IMHO, it's not worth the hassle.
Raspbian Jessie is old, and Debian Jessie will no longer be supported after June 30, 2020.
The best thing to do is just upgrading to Raspbian Buster.
I have installed Atom and the platformio-atom-ide-terminal package.But the terminal screen is blank and I not getting "Windows powershell prompt" or directory path.I am running a simple Python code.
Python Version: Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)] on win32
Atom version:1.34.0
I tried changing the setting.
Map Terminal:File.Working directory:Active file.PFB
Screenshots:
I have txt file like this one:
Linux Mint 17
Ubuntu 14.04
Debian GNU/Linux 7.0
Mageia 4
Fedora 20
openSUSE 13.1
Arch Linux
CentOS 7.0-1406
PCLinuxOS 2014.07
Slackware Linux 14.1
FreeBSD
I need to take version numbers and put it to the beginning of a line.
Whit awk you can do some like this:
awk '$NF~/[0-9\.]+/ {f=$NF;$NF="";$0=f FS$0}1' file
17 Linux Mint
14.04 Ubuntu
7.0 Debian GNU/Linux
4 Mageia
20 Fedora
13.1 openSUSE
Arch Linux
7.0-1406 CentOS
2014.07 PCLinuxOS
14.1 Slackware Linux
FreeBSD
If last field contain any number, move it to front position.
I'm trying to use Eclipse with CDT to debug a 64 bit binary. The binary is built outside of Eclipse, and runs fine. I start up the binary outside of eclipse, and then attempt to attach to the process using the 'C/C++ Attach to Application' debug configuration type.
I can choose the process from the list that pops up when you run the debug configuration, however, I get the following error message:
Error in final launch sequence
Failed to execute MI command:
attach 22014
Error message from debugger back end:
"program.x64": not in executable format: File format not recognized
Everything works fine if I build for an i386 target.
I'm not quite sure where to go with this, I've read that it might have something to do with the binary parsers in Eclipse:
This link mentions parsers, and this link describes a bug with the PE parser that is fixed.
I am running Eclipse Indigo with Eclipse CDT 8.0.0 on Linux x64. I have tried the 'Elf Parser' and 'GNU Elf Parser' under project_properties/c++_build/settings with no luck.
File information:
hostmachinea:file program.x64
programs.x64: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
GDB and gdbinit files are the Eclipse defaults
It sounds as if the GDB that Eclipse is using was built for i386, and thus can't debug 64-bit binaries. You likely need to install 64-bit capable GDB.
Here what the error message from current GDB looks like:
$ ./gdb --version
GNU gdb (GDB) 7.3.50.20110809-cvs
Copyright (C) 2011 Free Software Foundation, Inc.
...
This GDB was configured as "i686-linux".
...
$ ./gdb -q /bin/date
"/bin/date": not in executable format: File format not recognized
GDB and gdbinit files are the Eclipse defaults
Did you install 32-bit or 64-bit version of CDT?
In the shell, GDB I believe is 64 bit:
~:gdb --version
GNU gdb (GDB) 7.0.1
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Loading date:
~:gdb -q /bin/date
Reading symbols from /bin/date...(no debugging symbols found)...done.
Typing which gdb, and after putting that path explicitly into the debug configuraiton in Eclipse, I no longer get the error message.
As a bit of a side note, how can you find out which GDB Eclipse uses by default?
I downloaded 64-bit version Eclipse Indigo, which came pacakged with CDT.