rmin's questions

I would like to tweak my system so that the window under focus stands out more. The contrast in the title bar between active and inactive windows is quite hard to see.

I hit this issue the most when I have a lot of terminals open across many 30" monitors and have no idea which one currently has focus.

An ideal solution would be that the window is obvious just from the brightness of the title bar without needing to reach for the mouse or do fiddly alt-tabbing.

I've found some related questions:

How do I efficiently find my terminal window in GNOME Shell?

Gnome-terminal tabs: no contrast between active and inactive tabs

Visually recognise active window

but these are either for unity/compiz, require a mouse or are just for terminals (and it would be nice to solve this for all apps).

I have tried the "Windows Blur Effects" add on (see How to change color of the active/inactive window?) but it makes gnome very slow under its default settings and I'm unable to open the settings from the "Extensions" tab in gnome-tweak-tools to make it less heavy.

Thanks in advance.

I have a USB-AC56 Wireless-AC1300 wireless adapter and kernel version 4.4.0-92-generic on a standard ubuntu 16.04 installation.

I downloaded version 4.3.1.4 of the driver from the official asus site. The installation process involves unpacking and compiling the driver source code using make. When I do that I get:

In file included from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/include/drv_types.h:95:0,
                 from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/core/rtw_cmd.c:22:
/home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/include/hal_com.h:412:13: error: ‘file_path’ redeclared as different kind of symbol
 extern char file_path[PATH_LENGTH_MAX];
             ^
In file included from include/linux/seq_file.h:10:0,
                 from include/linux/pinctrl/consumer.h:17,
                 from include/linux/pinctrl/devinfo.h:21,
                 from include/linux/device.h:24,
                 from include/linux/dmaengine.h:20,
                 from include/linux/netdevice.h:38,
                 from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/include/osdep_service_linux.h:35,
                 from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/include/osdep_service.h:41,
                 from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/include/drv_types.h:32,
                 from /home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/core/rtw_cmd.c:22:
include/linux/fs.h:2610:14: note: previous declaration of ‘file_path’ was here
 extern char *file_path(struct file *, char *, int);
              ^
scripts/Makefile.build:258: recipe for target '/home/han/downloads/RTL8812AU_linux_v4.3.13_14061.20150505/driver/rtl8812AU_linux_v4.3.13_14061.20150505/core/rtw_cmd.o' failed

I have also tried using chili555's answer which uses open source drivers but they don't seem to work for the newer kernel versions giving an error like:

Module 8812au not found in directory /lib/modules/4.10.0-28-generic

I found people hit similar compilation problems here with a TP-link wifi adapter and they suggest that the driver is not supported for newer kernels and use some rtl8192cu-fixes. On their github page they say:

As a rule of thumb, this driver generally works with devices that use the RTL8192CU chipset, and some devices that use the RTL8188CUS, RTL8188CE-VAU and RTL8188RU chipsets too, though it's more hit and miss.

My device is an RTL8812au chipset though.

Any help much appreciated! Thanks!

I have a desktop with 3 monitors running Ubuntu 16.04 with graphics card: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-72-generic, LLVM 3.8.0).

One monitor is a Chimei CMV221D connected via a DVI cable. After I resume from a suspend it takes around 5-10 minutes to come back on. The other 2 monitors work properly.

If I run the "Screen Display" program and slightly move one of the monitor's positions, and hit "Apply" then the Chimei monitor will wake up sometimes (not always).

The issue doesn't happen if the computer just sleeps from inactivity or if I lock the screen. It also seems to require a long suspend to reproduce it.

All 3 monitors are at an anti-clockwise rotation with the Chimei on the right. The Chimei monitor is at 1680x1050 (16:10) resolution.

I've seen this related question but it's not clear how to use xset for my particular monitor.

I ran xrand --query when the monitor was working and not working and the output is the same.

This is my xrandr output for just the Chimei monitor:

$ xrandr --query
...
DVI-0 connected 1050x1680+2340+370 left (normal left inverted right x axis y axis) 408mm x 511mm
   1680x1050     59.95*+
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
...

This is the complete xrandr output:

$ xrandr --query
Screen 0: minimum 320 x 200, current 3390 x 2560, maximum 16384 x 16384
DisplayPort-0 connected primary 1440x2560+900+0 left (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     59.95*+
   1920x1080     60.00    60.00    50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1440x576      50.00  
   1024x768      75.08    70.07    60.00  
   1440x480      60.00    59.94  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    66.67    60.00    59.94  
   720x400       70.08  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1050x1680+2340+370 left (normal left inverted right x axis y axis) 408mm x 511mm
   1680x1050     59.95*+
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
DVI-1 connected 900x1600+0+453 left (normal left inverted right x axis y axis) 443mm x 249mm
   1600x900      60.00*+
   1440x900      74.98    59.90  
   1280x800      74.93    59.91  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.08    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08 

Thanks in advance!

I'm running Ubuntu 16.04, 64 bit, 11.7GB ram, Intel i7-3770 processor, 2TB rotating disk. I've got 3 monitors and I use 6 virtual work spaces and I'm using unity.

On a reboot, the desktop loads very slowly after I log in and the visual layout of panels gets "stuck" for a while with fragmented panels. The mouse is trapped inside one monitor and unity is partially responsive with a lot of lag. After about 20-30 seconds it fixes itself and my desktop becomes normal. Could this slowness be related to having a rotating disk?

I get the usual "System Program Problem Detected" pop up after my first login. I cleaned out my /var/crash/ dir and rebooted and I still get the error so I don't think it's stale crash logs.

There is one crash file (which I've elided):

_usr_lib_xorg_Xorg.0.crash:

ProblemType: Crash
Architecture: amd64
Date: Tue May 16 09:11:00 2017
DistroRelease: Ubuntu 16.04
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1485390561
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcCwd: /
ProcEnviron: 
ProcMaps:
 ...
ProcStatus:
 Name:  Xorg
 Umask: 0022
 State: S (sleeping)
 ...
 voluntary_ctxt_switches:   4088352
 nonvoluntary_ctxt_switches:    204945
Signal: 6
Uname: Linux 4.8.0-49-generic x86_64
UserGroups: 
CoreDump: base64
 ...

I've done a couple of reboots clearing the crash logs each time and consistently get the same ProcCmdline:

/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

Here is the output of systemd-analyze blame | head:

8.827s docker.service
7.404s dev-sda2.device
3.171s apparmor.service
2.087s ModemManager.service
1.893s dev-loop2.device
1.864s accounts-daemon.service
1.710s thermald.service
1.667s NetworkManager.service
1.569s plymouth-start.service
1.408s systemd-timesyncd.service

Thanks in advance!