On login screen, the keyboard looks like
But in user session, the emoji key is missing
Interestingly, emoji key is absent from Ubuntu GNOME too.
I'm using vanilla GNOME on Ubuntu 20.04.
I observed many times that some messages in Terminal or some part of them is enclosed in backtick and single inverted comma. For example, the output of type -a ls
generate
ls is aliased to `ls --color=auto'
I expect backticks and inverted commas to work in pairs but here, there is 1 backtick in the beginning and 1 single inverted comma in the end.
Why there is no closing backtick or starting inverted comma? Is it a standard?
On Ubuntu 19.04 and all its official flavors I observed that if I boot the LiveUSB in UEFI mode, there are options for live session and installation with safe graphics written beside them. However these options aren't available in legacy mode.
So, what is the purpose of this safe graphics mode? Is there any specific reason why they included in 19.04 and not on previous releases such as 16.04, 18.04 and 18.10?
When I run xkill
in terminal a X (cross sign) appears which seems to kill that GUI process (application) on which it is hovered and clicked. I expect the same behavior for GNOME Terminal (since in my understanding it is also a GUI application). But I get different behaviors under different display manager.
It seems xkill can't kill terminal in Wayland.
In the building where I am living is having a WiFi with two channels and same SSID. Whenever I connect to the WiFi, it always connects to the 2.4GHz band but I want to connect to 5GHz band. I have already tried this but all in vain. Also, I have tried linSSID app but it isn't even launching.
I am using Ubuntu 18.04 LTS and output of lshw -C network
:
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlp1s0
version: 83
serial: e4:02:9b:d2:65:c7
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-34-generic firmware=17.948900127.0 ip=172.21.126.136 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:128 memory:df100000-df101fff
Output of iwlist chan
:
wlp1s0 26 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 52 : 5.26 GHz
Channel 56 : 5.28 GHz
Channel 60 : 5.3 GHz
Channel 64 : 5.32 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
When I open VMWare player, I get a prompt to install VMWare Player tools. When I click on Download and Install, it shows this error:
Failed to run /usr/lib/vmware-installer/2.1.0/vmware-installer '--required' '--console' '--install-component=/home/dell/.cache/vmware/cds/cdstmp_tools-linux_10.2.5_9474260/vmware-tools-linux-10.2.5-8068393.x86_64.component' as user root.
Unable to copy the user's Xauthorization file.
I also have read that it is not recommended to launch GUI applications as root
or with sudo
. So is there any other option to install VMWare tools from Terminal/Bash?
This doubt is hitting me since 2-3 days, so I decided to test it myself. What I did is I installed Ubuntu 16.04.4 in VMWare and edited /etc/apt/sources.list
and replaced xenial
with bionic
using:
sudo sed -i 's/xenial/bionic/g' /etc/apt/sources.list
Then I ran
sudo apt-get update && sudo apt-get upgrade
I was able to upgrade to 18.04, confirmed by using lsb_release -a
. However, I encountered some problems like:
apt does not have a stable CLI interface. Use with caution in scripts.
unmet dependency of python3-aptdaemon.pkcompat
Release 'bionic-backports' for 'appstream' not found
Broken Unity
I solved all the errors and installed gnome
and gdm3
.
So, I just want to know is it a good idea to edit sources.list
? I know that my system might broke but is there any other specific reason not to use this.
Note: I tested this on Ubuntu 16.04 in VMWare to clear my doubts only.
These errors are showing while installing Visual Studio Code.
dell@Mittal:~/Downloads$ sudo dpkg -i "code_1.24.1-1528912196_amd64(1).deb"
Selecting previously unselected package code.
(Reading database ... 268063 files and directories currently installed.)
Preparing to unpack code_1.24.1-1528912196_amd64(1).deb ...
Unpacking code (1.24.1-1528912196) ...
Setting up code (1.24.1-1528912196) ...
/var/lib/dpkg/info/code.postinst: line 70: /etc/apt/sources.list.d/vscode.list: No such file or directory
dpkg: error processing package code (--install):
installed code package post-installation script subprocess returned error exit status 1
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Errors were encountered while processing:
code