I want tmux to start on ssh login.
The typical advice is to add this to ~/.bashrc:
tmux attach-session -t mysession 2>/dev/null || tmux new-session -s mysession
But when I log in, I get this error:
lost server
I've have a look at this, but it does not solve the problem.
I have the following configuration:
Host: Ubuntu 18.04 Desktop
Guest: Ubuntu 18.04 Server
VM Software: VirtualBox
USB Drive: 500GB
I have connected the USB drive to the Host and configured the Guest VM as follows:
I then boot up ...
oneliner which should redirect
This is getting various close vote reasons I don't understand.
Currently tally is 4 close votes and it is one vote away from being closed.
No on has actually stated why they are voting but from comments one can "guess" who is.
Note I understand Windy's comment...
Here is an example of the problem in gnome. However, when I tried this in Xfce, the same problem occurs.
I have set up a Hyper key on the keyboard. It works fine for keyboard shortcuts and seems to be ok when checked with xev. However, applying these gsettings doesn't work:
org.gnome.desktop.w...
It looks like this issue (Wine won't install, Does not have valid release file) might have come back to life but I don't really understand why
` sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main' ` gives me `E: The repository "http://ppa.launchpad.net/wine/wine-builds/ubuntu bionic Release" does not have a Release file.` even though https://dl.winehq.org/wine-builds/ubuntu/dists/bionic/ clearly has a bionic Release filehttps://dl.winehq.org/wine-builds/ubuntu/dists/bionic/ `
oh... but http://ppa.launchpad.net/wine/wine-builds/ubuntu doesn't.... why is it trying to go there instead of dl.winehq.org?
nevermind, sudo apt-add-repository --remove http://ppa.launchpad.net/wine/wine-builds/ubuntu got rid of the error, though I don't know how the ppa got added?
seems like the existing posts / docs are a dead end for Wine 4.x, I ended up not being able to resolve the dependencies, I'm going to try building wine from source instead
a couple of times I've wondered how hard it would be to make a special Android build that would return gibberish data when something is accessed in a way that implies poor privacy practices
like if a (malicious / compromised) app attempted to access the microphone when it wasn't in focus and had special permission, return white noise instead of actual audio