C. E.'s questions

I am trying to get awesome-terminal-fonts to work with gnome-terminal. I've tried various things. At this stage, the fonts show up if I run fc-list | grep Awesome:

fc-list | grep Awesome

/home/user/.fonts/Droid+Sans+Mono+Awesome.ttf: Droid Sans Mono Awesome:style=Regular
/home/user/.fonts/SourceCodePro+Powerline+Awesome+Regular.ttf: SourceCodePro+Powerline+Awesome Regular:style=Regular
/home/user/.fonts/Inconsolata+Awesome.ttf: Inconsolata Awesome:style=Medium
/home/user/.local/share/fonts/Unknown Vendor/TrueType/Inconsolata Awesome/Inconsolata_Awesome_Medium.ttf: Inconsolata Awesome:style=Medium
/home/user/.local/share/fonts/Ascender Corporation/TrueType/Droid Sans Mono Awesome/Droid_Sans_Mono_Awesome_Regular.ttf: Droid Sans Mono Awesome:style=Regular
/home/user/.local/share/fonts/Adobe/TrueType/SourceCodePro+Powerline+Awesome Regular/SourceCodePro+Powerline+Awesome_Regular_Regular.ttf: SourceCodePro+Powerline+Awesome Regular:style=Regular

The fonts also show up in LibreOffice. The fonts do not show up in gnome-terminal. I tried to make the terminal use one of the fonts using dconf-editor as in the answer here, but when looking in gnome-terminal the font used was then "None".

This answer suggests that the terminal will only show monospace fonts. I tried listing them as suggested here (fc-list :mono) and that does not show my fonts. However, they are monospace fonts.

My larger question is: how do I make these fonts selectable in the terminal options? Given my investigation into the issue, a more narrow question might be: how do I make Ubuntu recognize these fonts as monospace fonts?

I'm using ubuntu 20.04 and GNOME terminal 3.36.2.

I work at a company that uses Samba for file sharing, which means that I rely on it a lot throughout the day. Unfortunately, the service provider of the VPN has not been able to cope with the traffic that has resulted from everyone working from home, and so the Samba shares are frequently slow or unavailable. Even more unfortunate, when this happens, it causes Nautilus and Nemo, the two file managers for Ubuntu that I have tried, to freeze.

It's not just the current tab that freezes while it's trying to load. It's also the other tabs, the menu to the left and even other windows of that file manager. After a while I'm given the option to force quit. However, I often cannot start the file manager again until my access to the Samba share is restored because it will try to open it at startup and immediately freeze.

It's a bit like using a web browser that freezes all of its tabs and all of its windows if a website is down, offers you to force quit, and then hangs on startup until the website is available again. However (warning: snark ahead), web browsers have a brilliant solution to this problem called threads. Is there a file manager for Ubuntu that similarly solves this issue?

I have an Acer ET322QK monitor. It works with Windows 10, Ubuntu 18.04 and Linux4Tegra. However, when connecting my computer with newly installed Ubuntu 20.04, it cannot seem to use the monitor properly. In "joined" mode it is black. If I mirror it, it will show the desktop on one fourth of the monitor but I am not able to control anything with the mouse. When I tried to use it as the only display it put me in some kind of state where I had to restart the computer by pressing the power button to gain control again.

It should be noted that the settings recognizes the display just fine. It lists it as "Acer Technology 32 inch" and the list of resolutions I can choose from looks right.

I see that there are many posts about monitors not working and usually it is resolved by updating a driver or something. However, I am not good with these things. Could someone advise me what I should do in my situation? If it is a driver I need, how do I know which one?

As for the additional drivers in the settings:

The default was "Using X.Org X server" and that is the one that seems to work best. The one selected in the image didn't seem to recognize the monitor, as it wouldn't show up the displays menu.

Running dpkg -l *nvidia* in the terminal yields this:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                             Version                 Architecture Description
+++-================================-=======================-============-===============================================
un  libgldispatch0-nvidia            <none>                  <none>       (no description available)
rc  libnvidia-compute-450:amd64      450.66-0ubuntu0.20.04.1 amd64        NVIDIA libcompute package
un  libnvidia-ml1                    <none>                  <none>       (no description available)
un  nvidia-304                       <none>                  <none>       (no description available)
un  nvidia-340                       <none>                  <none>       (no description available)
un  nvidia-384                       <none>                  <none>       (no description available)
un  nvidia-common                    <none>                  <none>       (no description available)
rc  nvidia-compute-utils-450         450.66-0ubuntu0.20.04.1 amd64        NVIDIA compute utilities
rc  nvidia-dkms-450                  450.66-0ubuntu0.20.04.1 amd64        NVIDIA DKMS package
un  nvidia-dkms-kernel               <none>                  <none>       (no description available)
un  nvidia-kernel-common             <none>                  <none>       (no description available)
rc  nvidia-kernel-common-450         450.66-0ubuntu0.20.04.1 amd64        Shared files used with the kernel module
un  nvidia-kernel-source-450         <none>                  <none>       (no description available)
un  nvidia-legacy-304xx-vdpau-driver <none>                  <none>       (no description available)
un  nvidia-legacy-340xx-vdpau-driver <none>                  <none>       (no description available)
un  nvidia-libopencl1-dev            <none>                  <none>       (no description available)
un  nvidia-opencl-icd                <none>                  <none>       (no description available)
un  nvidia-persistenced              <none>                  <none>       (no description available)
rc  nvidia-prime                     0.8.14                  all          Tools to enable NVIDIA's Prime
rc  nvidia-settings                  440.82-0ubuntu0.20.04.1 amd64        Tool for configuring the NVIDIA graphics driver
un  nvidia-settings-binary           <none>                  <none>       (no description available)
un  nvidia-vdpau-driver              <none>                  <none>       (no description available)

This is the result of sudo lshw -C video:

  *-display                 
       description: VGA compatible controller
       product: NVIDIA Corporation
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:150 memory:c6000000-c6ffffff memory:b0000000-bfffffff memory:c0000000-c1ffffff ioport:5000(size=128) memory:c5000000-c507ffff
  *-display
       description: VGA compatible controller
       product: UHD Graphics
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 05
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:149 memory:c3000000-c3ffffff memory:a0000000-afffffff ioport:6000(size=64) memory:c0000-dffff

I've had a setup that's been working for several months. My laptop has been connected to a Dell dock that's been connected to two Dell monitors. The laptop has been running Ubuntu 18.04 with the lid closed.

As of some hours ago, when I connect the dock, first all three screens appear to work, but after a few seconds all of the three screens turn black. After that, the computer keeps running but the screens stay black. Even if I disconnect the dock the laptop screen will stay black, and I have to restart it by pressing its physical button.

I haven't done anything sophisticated recently AFAIK, the only thing I can think of is that I deleted some .gz files in the var/logs folder (`sudo rm *.gz), but that should be safe.

1. How can this be fixed?
2. Is there any way to regain control of the computer after disconnecting the dock without restarting it?

I can connect one of the monitors directly to the laptop via HDMI and that works, but I don't have ports enough to connect both of the monitors in that way.