With more than two screens, Join Displays is the only mode available.
Is there any way around this? I want to "Join Displays" on every screen, but I have more than two. Ubuntu will only "Join" one, and then "Mirror[s]" the others.
The Windows equivalent would be changing "Extend desktop to this display" instead of "Duplicate."
I have a couple Debian based Linux distributions running on VMware Workstation Player on Windows 10. I used to be able to SSH in to the virtual machine from the host machine from a PowerShell or Ubuntu (WSL) terminal without any problem. But lately I have not been able to do so.
First I start the SSH service on the virtual machine.
service ssh start
Then I verify that the service is running.
service ssh status
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: e>
Active: active (running) since Sat 2021-06-26 11:30:42 PDT; 1min 14s ago
Docs: man:sshd(8)
man:sshd_config(5)
Process: 872 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 898 (sshd)
Tasks: 1 (limit: 9448)
Memory: 2.8M
CGroup: /system.slice/ssh.service
└─898 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
Jun 26 11:30:42 ubuntu systemd[1]: Starting OpenBSD Secure Shell server...
Jun 26 11:30:42 ubuntu sshd[898]: Server listening on 0.0.0.0 port 22.
Jun 26 11:30:42 ubuntu sshd[898]: Server listening on :: port 22.
Jun 26 11:30:42 ubuntu systemd[1]: Started OpenBSD Secure Shell server.
I verify the IP address.
hostname -I
192.168.75.129
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:a0:15:34 brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.75.129/24 brd 192.168.75.255 scope global dynamic noprefixroute ens33
valid_lft 1714sec preferred_lft 1714sec
inet6 fe80::98eb:dd0a:da24:92be/64 scope link noprefixroute
valid_lft forever preferred_lft forever
...but Ubuntu on Windows Subsystem for Linux cannot connect.
ssh 192.168.75.129
ssh -vvv 192.168.75.129
OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.75.129 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.75.129 [192.168.75.129] port 22.
debug1: connect to address 192.168.75.129 port 22: Resource temporarily unavailable
ssh: connect to host 192.168.75.129 port 22: Resource temporarily unavailable
...and PowerShell times out.
ssh -vvv 192.168.75.129
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/me/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.75.129 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.75.129 [192.168.75.129] port 22.
debug3: finish_connect - ERROR: async io completed with error: 10060, io:000001B003450380
debug1: connect to address 192.168.75.129 port 22: Connection timed out
ssh: connect to host 192.168.75.129 port 22: Connection timed out
NMAP returns the following scans.
nmap -Pn -p 22 192.168.75.129
Warning: Nmap may not work correctly on Windows Subsystem for Linux.
For best performance and accuracy, use the native Windows build from https://nmap.org/download.html#windows.
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-26 13:36 CDT
NSOCK ERROR [0.0460s] mksock_bind_device(): Setting of SO_BINDTODEVICE failed (IOD #1): Protocol not available (92)
NSOCK ERROR [0.0470s] mksock_bind_device(): Setting of SO_BINDTODEVICE failed (IOD #2): Protocol not available (92)
NSOCK ERROR [0.0470s] mksock_bind_device(): Setting of SO_BINDTODEVICE failed (IOD #3): Protocol not available (92)
Problem binding to interface , errno: 92
socket_bindtodevice: Protocol not available
Problem binding to interface , errno: 92
socket_bindtodevice: Protocol not available
Nmap scan report for 192.168.75.129
Host is up.
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.09 seconds
...and from nmap on Windows.
PS C:\Users\me> cd '\Program Files (x86)\nmap'
PS C:\Program Files (x86)\nmap> ./nmap.exe -Pn -p 22 192.168.75.129
Host discovery disabled (-Pn). All addresses will be marked 'up' and scan times will be slower.
WARNING: Could not import all necessary Npcap functions. You may need to upgrade to the latest version from https://npcap.org. Resorting to connect() mode -- Nmap may not function completely
Starting Nmap 7.91 ( https://nmap.org ) at 2021-06-26 13:36 Central Daylight Time
Nmap scan report for 192.168.75.129
Host is up.
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.17 seconds
What am I doing wrong?
I have been changing the /etc/alternatives/gdm3.css file to customize the colors of my desktop for a while now, but I believe it may be making my OS unstable. It even says on the top of the file "This stylesheet is generated, DO NOT EDIT".
So, where are the colors of this file derived? Am I able to modify the source of this color?
I was having trouble using SSH with my gnome shell, so I decided to upgrade (sudo apt upgrade)my operating system after an update (sudo apt update) did not work. Then my terminal output indicated that it was unable to upgrade gnome-shell and gnome-shell-common because the dependencies were not met.
An article online suggested that I remove the information after Depends: in /var/lib/dpkg/status for those two packages, and I was dumb enough to try that. That step allowed me to force the upgrade, but I must have broken something as the GNOME desktop no longer launches.
I am able to get in to the terminal, but not my desktop. How can I get GNOME to launch again?
When I try to start my computer now, I get the following messages after the desktop fails to start.
7.162243] Bluetooth: cdi0: command 0xfc8e tx timeout
then my login attempt is interrupted by the following messages.
[ 15.386381] Bluetooth: hci0: sending Intel patch command (0xfc8e) failed (-110)
[ 15.386557] Bluetooth: hci0: sending frame failed (-19)
[ 17.402388] Bluetooth: hci0: command 0xfc11 tx timeout
[ 17.386394] Bluetooth: hci0: Exiting manufacturer mode failed (-110)
After that I am able to reach a command prompt.
I would be fine with removing bluetooth from my computer; I never use it.
At one point, my computer was also returning an error about /etc/alternatives/gdm3.css being an invalid argument. I think that was after GNOME broke though. I copied the gdm3.css file from `/usr/share/gnome-shell/theme/gdm3.css to fix that error though.
Oh, and there was a message from the terminal about the /var/lib/dpkg/status file needing a colon after an attribute, but I believe that was before I broke the OS. I edited the file exactly as it asked me, and the error went away.
I tried to customize my Ubuntu 18 desktop colors by changing all of the purple and orange (hex and RGB) values in the gdm3.css to green, but I keep seeing purple when I sign out and sign back in and I keep seeing orange highlights when I switch 'directly' between applications! What am I missing? Is there a better way to change colors in this OS? It even says "This stylesheet is generated, DO NOT EDIT" on top, but I edited it because I could not find a better suggestion online. It is especially frustrating because the colors get reverted back by distribution upgrades sometimes. Should I be exporting different color environment variables instead? What does the Linux community know about customizing GNOME that I don't?
I recently installed KVM on Ubuntu 18.04 with requisite tools like virt-manager, libvirt, and qemu.
My problem is that the VMs I spin up are not connected to internet. Some give me an error message saying that my machine is not using DHCP, while other distributions just do not connect at all.
I set it up with the following article: https://linuxconfig.org/install-and-set-up-kvm-on-ubuntu-18-04-bionic-beaver-linux ...which says that I need to edit /etc/network/interfaces to create a bridge. If you read the comments on that same article, you will find that file is no longer being used and has been replaced with /etc/netplan/*
My current .yaml file in /etc/netplan looks like this:
network:
version: 2
renderer: NetworkManager
My network interfaces appear to be enp0s25 , wlp4s0 , and wwp0s20u4 .
How should I change my netplan configuration so that my virtual machines on KVM can have an internet connection?
I cannot get my Lenovo 100S ideapad to boot from my Ubuntu 18 LTS bootable USB. The laptop currently has Windows 10 32 bit on it. After disabling secure boot in the EFI BIOS so that I could change the boot order, Windows BitLocker has kicked in and locked the drive. Every time the computer boots now, it enters BitLocker drive recovery.
DEVICE SPECIFICATIONS=
Product Name: Lenovo ideapad 100S-11IBY
BIOS Version: E2CN13WW
EC Version: E2EC12WW
Lenovo SN: YD00S4Y4
CPU: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz
System Memory: 2048 MB
Storage: SanDisk DB4032
Preinstalled OS license SDK0J91117 WIN
OA3 Key ID 3259182586809
If I try to boot up the computer normally, it will first enter BitLocker drive recovery. I hit the "Skip this drive" button to proceed (because I don't care to get Windows back on the computer). Then it gives me the following options:
If I press the 'Novo' button then F1 key, I get a menu that says "Boot Option Menu" then "EFI Boot Devices" and then "Windows Boot Manager" is selected with a grey highlight. Underneath that it says [up] and [down] to change option, ENTER to select an option, ESC to exit" but it does not change the selection when I press up or down.
When I do get in to the BIOS using the 'Novo' button then F1 key, it shows me the "Information" I posted above under DEVICE SPECIFICATIONS, my "Configuration" options include "Secure Boot" (which I have off), "Reset to Setup Mode", and "BIOS Back Flash" (which is off). There are other options, but I don't believe they would be relevant to my problem here.
Any ideas?