Quick & EASY Solution:
I have had the same issue, several times. Do NOT do sudo apt-get dist-upgrade first. Very important. ****NOTE: This solution is for Debian based machines but will not work on KDE Neon. To update KDE Neon, you must use sudo pkcon update.****
It can make your system very unstable, programs can crash and you can lose a lot ...
By default, at least for POSIX compliant systems, running a command in background, with &, only detaches stdin, so you'll be able to run other commands. stdout and stderr are still attached to the parent shell.
If you don't want to see stdout and/or stderr you can just redirect them to a file or /dev/null:
command &>log.txt & #...
What does this mean?
The following packages have been kept back:
The answer is here
This means that there are new versions of these packages which will not be installed for some reason. Possible reasons are broken dependencies (a package on which it depends doesn't have a version available for download) or new dependencies (the package has come to ...
certbot-auto uses its own installed virtual environment, including its own build of python. This was (naturally) not updated in the dist-upgrade to Jessie. certbot-auto did not detect that it needed a rebuild, thinking that all the dependencies were satisfactorily already installed.
So the fix was:
rm -rf /opt/eff.org
Whether stdout of a background process is shown on the terminal is up to you. You can change the behavior with the stty utility.
The default allows a background process to write to terminal:
$ echo Hello &
That behavior can be changed with the stty command:
$ stty tostop
$ echo Hello &
+ Stopped ...
The error has nothing to do with Amazon or with your CircleCI configuration.
Jessie's repos have moved to debian's archive and you need to update the following file:
The new content needs to be:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://security.debian.org ...
Well, I decided to take a punt on installing it direct from VideoLAN
and add the line:
deb http://download.videolan.org/pub/debian/stable/ /
Then add their key:
wget -O - http://download.videolan.org/pub/debian/videolan-apt.asc|sudo apt-key add -
Now update the system
sudo apt-get update
And install libdvdcss2
sudo apt-get ...
Using macOS, I come to a different conclusion. The key is IPv6. localhost resolves to both IPv6 and IPv4. However, the following command line will cause nc to listen on IPv4:
nc -l -u 6900
$ lsof -n -i:6900
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nc 63923 fuzzy 3u IPv4 0xad7f669b928a178b 0t0 UDP *:...
I just got this working in Iceweasel 38.3.0 on Jessie.
Mozilla says that 'Firefox Hello' is not available in ESR versions of Firefox but it seems that it's just disabled by default.
To enable Hello go to the 'about:config' page and set the preference called 'loop.enabled' to 'true'. 'Loop' was a previous name for the 'Hello' feature. It seems that you also ...
You don't mount the swap partition or swapfile with mount, you use the swapon command. (The swap partition or file isn't really a filesystem that can be mounted and hold files, it's an area of the disk the kernel uses directly).
swapon -a will enable all swaps from /etc/fstab.
The /usr/bin/curl commandline executable is not the same as the php-curl library.
Both link to libcurl.so, the DLL/shared library which provides the functionality under the hood.
But you would need to install the curl package to get the CLI binary.
This seems to be a driver issue.
First, you should reinstall the video drivers.
sudo apt-get install xserver-xorg-video-intel
Use the legacy driver (Version 304.125) as it supports your NVIDIA® NVS 5400M graphics card as listed here and described below.
1) Add "contrib" and "non-free" components to /etc/apt/...
The last I heard, Debian did not support Secure Boot. If that's changed with Debian 8, it should simplify things greatly. If Debian does not support Secure Boot, though, I suggest you take one step back from your question about Shim and make the question about Secure Boot generally. With that step back, there are three solutions, broadly speaking:
You can ...
The reason why adding a stanza to /etc/networking/interfaces solves your problem is that you have the networking.service enabled. If you look at the networking.service file, you will see (partly edited):
Description=LSB: Raise network interfaces.
Your error message simply means that your status file has been corrupted.
You should first remove it,
then recreate it,
then do an update plus an upgrade.
If this does not work, check the permissions and ownership of both status file and its directory tree, and, possibly, check whether the disk is ...
As the last column shows, that device (apparently a LVM volume) corresponds to /, the main filesystem on which the OS is stored. The largest parts are likely to be:
/usr, installed software;
/var/log, system logs;
/var/cache, cached files.
Often a lot of space is occupied by /var/cache/apt, which contains packages temporarily downloaded by apt-get before ...
The "working directory is not writable" message is a warning, not really related to the fatal errors that follow. You can silence that message by fixing the permissions on the base directory (which appears to be set to /var/bind9/chroot/var/cache/bind by the directions on that wiki page) but there's no real need to and it's safer to NOT fix it.
The fatal ...
I included this answer in my blog. If you want to see that you can go there from this link.
The above error is very common in Ubuntu terminal when you try to upgrade (apt-get upgrade). This usually happens because dependencies of one package you install has changed. In order to upgrade you need to upgrade those as well first. So it is very straightforward ...
From this Unix SE answer:
Firstly as mentioned above please DO NOT dist-upgrade any production system! While dist-upgrading will "solve" kept back packages it is definitely not the solution to this issue and will quite likely cause you more grief than good if you run it without knowing the implications on your system.
If upgrading a package requires ...
See conclusions at the very end.
I can explain your results. I use Kubuntu, not Debian, still I believe the main points are common. To fully understand what happens it's good to analyze TCP case, then compare to UDP.
If you want to replicate my research, do not terminate nor kill nc unless I say so or it terminates by itself. Kill ncs when I ...
First download the package dpkg:
apt-get download dpkg
Now you see the .deb package in your current working directory. This can be unpacked manually by:
ar x dpkg_<package_version>.deb
That package containes, amongst other things, a file called data.tar.gz. In there are the executables. Unpack it within the current directory:
tar xf data.tar.gz
You need to use Tools > Configuration Files > filetypes.common menu item.
It will automatically create .config/geany/filedefs/filetypes.common file for you.
You can also copy it manually from /usr/share/geany/filetypes.common.
In order to set the caret shape you'll have to change caret=caret line to caret=caret;;true.
It is Postfix.
Postfix is a very popular open source Mail Transfer Agent (MTA) that can be used to route and deliver email on a Linux system.
Port 25: SMTP
Port 465: SMTPS
Port 587: mail submission agents (MSAs)
Add the user to netdev group : The members of this group can manage network interfaces through the network-manager and wicd:
adduser user_name_here netdev
This right is gained by adding the user to the netdev group:
On Debian, the "netdev" group gains access to using Network Manager. On Ubuntu, ...
It seems my hypothesis, below, had merit: here you will find a recent guide on how to correct the 8168 behaviour by installing the appropriate drivers, and how to make them stick after a kernel upgrade/reboot.
Using a protocol such as SFTP implies adding encryption and compression. Compressing a file means that you hit the CPU, but ...
You are likely running systemd as your inint system. To configure your service, you need to create the necessary unit file for example /etc/systemd/system/jenkins.service.
ExecStart=/usr/java/jre1.8.0_131/bin/java -jar /usr/local/jenkins/jenkins.war
This isn't a definitive answer, but an answer is the only way to post an image.
It looks like the system font, or at least the one used by LibreOffice, has been changed, or is missing and another font has been substituted. From the menu, click on Tools | Options | View and look at whether Use system font for user interface is checked:
If LibreOffice is ...
It depends on the type of filesystem you're mounting.
Native Unix/Linux filesystems, such as ext4, store ownership information on disk. There's really no such thing as mounting a filesystem "as" a user; the files are owned by whoever the data on disk says they are. Different files can be owned by different people.
Non-Unix filesystems, such as FAT, ...
Intel graphics is ok. The ***** firmware unavailable can be fixed during installation.
Go to this link and download firmware.zip file. Extract its contents to a folder named firmware on fat32 formatted pen drive (be sure the individual files need to be in folder firmware). Connect this pen drive during installation and it loads the missing firmware.