External monitor does not connect after last night's updates

nvidia
dual-gpu
dual-monitor

#1

I have a Xiaomi Notebook Pro with a Geforce MX 150. It’s been running perfectly without issue for about 6 months. After running Manjaro updates last night, my external display suddenly doesn’t show any video. I’ve tried disconnecting and reconnecting, and rebooting, but neither brought my video back.


#2

A few other thoughts:
nvidia bumblebee is still installed as it was before.
lspci is only making one reference to nvidia:

[brad@merlin-xiaomi-1 ~]$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation Device 1d12 (rev ff)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


#3

What application do you use for the video?
Does the same application show video on the laptop display?
Also some info

inxi -SGxxz

And check the logs (journalctl) for errors and when starting your app from terminal


#4

hi Petsam,

I think there may be a misunderstanding. I’m saying that my laptop isn’t recognizing the external monitor at all. When I plug it into my laptop’s HDMI port, the monitor powers on and says “No Signal.” There’s no video on it, regardless of application.

Here’s the output of that command:

[brad@merlin-xiaomi-1 ~]$ inxi -SGxxz
System:
  Host: merlin-xiaomi-1 Kernel: 4.14.30-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 7.3.1 Desktop: Gnome 3.26.2 dm: gdm 
  Distro: Manjaro Linux 17.1.7 Hakoila 
Graphics:
  Card-1: Intel UHD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:5917 
  Card-2: NVIDIA Device driver: N/A bus ID: 01:00.0 chip ID: 10de:1d12 
  Display Server: N/A driver: intel compositor: gnome-shell tty: 80x24 
  Message: Advanced graphics data unavailable in console. Try -G --display 


#5

Nothing happens in journalctl -f when I connect and disconnect my monitor:

[brad@merlin-xiaomi-1 ~]$ journalctl -f
-- Logs begin at Wed 2017-11-22 11:24:02 CST. --
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #2 0x7ffd83945690 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7f17380df098 @ 52)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #3 0x7ffd839465b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f17380e9cd0 @ 54)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #4 0x7ffd83946700 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f17380e9d58 @ 1626)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #5 0x7ffd839467b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f17380e9de0 @ 100)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #6 0x7ffd83946840 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f17380e9e68 @ 10)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #7 0x7ffd839468c0 I   resource:///org/gnome/gjs/modules/signals.js:126 (0x7f17380e2b38 @ 386)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #8 0x7ffd83946970 b   resource:///org/gnome/shell/ui/tweener.js:208 (0x7f17380df808 @ 159)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #9 0x7ffd839469d0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f17380c2bc0 @ 71)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #10 0x7ffd839469d0 I   resource:///org/gnome/shell/ui/tweener.js:183 (0x7f17380df780 @ 20)
Mar 30 14:28:46 merlin-xiaomi-1 org.gnome.Shell.desktop[1077]: #11 0x7ffd83946a70 I   self-hosted:917 (0x7f17380ee5e8 @ 394)
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:28:54 merlin-xiaomi-1 gnome-terminal-[12070]: Allocating size to GtkScrollbar 0x5606be53e230 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Mar 30 14:29:10 merlin-xiaomi-1 signal-tray.desktop[1306]: {"name":"log","hostname":"merlin-xiaomi-1","pid":1311,"level":30,"msg":"Sending a keepalive message","time":"2018-03-30T19:29:10.881Z","v":0}


#6

Check what was upgraded to have a possible hint on the source of the problem.


#7

I’m actually not sure where to view that. Could you point me to that?


#8

I think I found that list:

cat /var/log/pacman.log | grep -i upgraded

[2018-03-28 14:57] [ALPM] upgraded adapta-maia-theme (3.93.0.174-1 -> 3.93.0.193-1)
[2018-03-28 14:57] [ALPM] upgraded libsystemd (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded docker (1:18.02.0-1 -> 1:18.03.0-1)
[2018-03-28 14:57] [ALPM] upgraded grub (2.03.0-2 -> 2.03.0-4)
[2018-03-28 14:57] [ALPM] upgraded libmagick (7.0.7.27-1 -> 7.0.7.27-2)
[2018-03-28 14:57] [ALPM] upgraded imagemagick (7.0.7.27-1 -> 7.0.7.27-2)
[2018-03-28 14:57] [ALPM] upgraded systemd (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded libpsl (0.20.1-1 -> 0.20.1-2)
[2018-03-28 14:57] [ALPM] upgraded hplip (3.18.3-1 -> 3.18.3-2)
[2018-03-28 14:57] [ALPM] upgraded inxi (2.9.02-2 -> 2.9.08-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-expat (2.2.2-1 -> 2.2.5-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-icu (60.1-1 -> 60.2-1)
[2018-03-28 14:57] [ALPM] upgraded libdrm (2.4.91-2 -> 2.4.91-3)
[2018-03-28 14:57] [ALPM] upgraded lib32-libdrm (2.4.91-2 -> 2.4.91-3)
[2018-03-28 14:57] [ALPM] upgraded lib32-libgcrypt (1.8.1-1 -> 1.8.2-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-llvm-libs (5.0.1-1 -> 6.0.0-1)
[2018-03-28 14:57] [ALPM] upgraded llvm-libs (5.0.1-2 -> 6.0.0-4)
[2018-03-28 14:57] [ALPM] upgraded linux414 (4.14.29-1 -> 4.14.30-1)
[2018-03-28 14:57] [ALPM] upgraded pacman-mirrors (4.8.3-2 -> 4.9.1-3)
[2018-03-28 14:57] [ALPM] upgraded xf86-input-libinput (0.26.0-1 -> 0.27.0-2)
[2018-03-28 14:57] [ALPM] upgraded mesa (17.3.7-0 -> 17.3.7-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-mesa (17.3.7-0 -> 17.3.7-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-systemd (238.0-6 -> 238.51-1)
[2018-03-28 14:57] [ALPM] upgraded linux414-bbswitch (0.8-26 -> 0.8-27)
[2018-03-28 14:57] [ALPM] upgraded linux414-nvidia (1:390.42-3 -> 1:390.42-4)
[2018-03-28 14:57] [ALPM] upgraded linux414-virtualbox-host-modules (5.2.8-6 -> 5.2.8-7)
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-extension-settings (20180224-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-maia-theme (20180118-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded qt5-base (5.10.1-5 -> 5.10.1-6)
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-settings (20180312-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded manjaro-release (17.1.6-1 -> 17.1.7-1)
[2018-03-28 14:57] [ALPM] upgraded nautilus-admin (1.1.3-1 -> 1.1.4-1)
[2018-03-28 14:57] [ALPM] upgraded netctl (1.15-1 -> 1.16-1)
[2018-03-28 14:57] [ALPM] upgraded nodejs (9.9.0-1 -> 9.9.0-2)
[2018-03-28 14:57] [ALPM] upgraded os-prober (1.76-1 -> 1.76-2)
[2018-03-28 14:57] [ALPM] upgraded pamac (6.2.5-1 -> 6.2.6-1)
[2018-03-28 14:57] [ALPM] upgraded systemd-sysvcompat (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded uget (2.2.0-1 -> 2.2.1-1)
[2018-03-28 14:57] [ALPM] upgraded update-notifier (0.7.4-1 -> 0.7.5-1)
[2018-03-28 14:57] [ALPM] upgraded xdg-user-dirs (0.16-1 -> 0.17-1)
[2018-03-28 15:02] [ALPM] upgraded gitkraken (3.4.1-1 -> 3.5.0-1)

#9

So we are talking about this update?

It would be great to have the full snippet of transactions happening during the update to see what the reason might be. Therefore post the content of /var/log/pacman.log for the given timeframe.

Also I noticed that the Intel driver is currently used on your device. Based on the snippet only the Kernel and Systemd got updated. Others are only needed rebuilds. At first glance I couldn’t find any driver related updates in the Kernel Changelog. Also nothing special pops out in Systemd Changelog. To check if the current package-set has any regression created, you may get the latest v17.1.7 ISO and simply boot it to live-mode. It holds all packages the update 2018-03-27 also had.

To check which graphical driver currently is used, you may use the following script:

#!/bin/bash

if [ -z "$1" ]; then
    logfile=/var/log/Xorg.0.log
else
    logfile="$1"
fi

sed -n 's@.* Loading .*/\(.*\)_drv.so@\1@p' "$logfile" |
    while read driver; do
        if ! grep -q "Unloading $driver" "$logfile"; then
            echo "Currently used Graphical-Driver: $driver"
            break
        fi
    done

In regard of the Monitor issue I recommend to install xorg-xrandr to double-check your connectors:

phil@development ~ $ xrandr
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 340mm x 270mm
   1280x1024     75.02*+  60.02  
   1152x864      75.00    60.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)

On my example the monitor is connected to DVI-I-1. If I have now however a monitor also connected to DVI-I-0, I may force the output like this: sudo xrandr --output DVI-I-0 --auto. It is also possible to turn 0 off and 1 on: sudo xrandr --output DVI-I-0 --off --output DVI-I-1 --auto

More about it you may read in the Arch Wiki.


#10

Thanks so much for your assistance, Phil. I’m just starting on working through your notes, but I wanted to share those logs from /var/log/pacman.log first:

[2018-03-28 13:08] [PAMAC] synchronizing package lists
[2018-03-28 13:08] [ALPM] transaction started
[2018-03-28 13:08] [ALPM] upgraded archlinux-keyring (20180302-1 -> 20180322-1)
[2018-03-28 13:08] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2018-03-28 13:08] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2018-03-28 13:08] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2018-03-28 13:08] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2018-03-28 13:08] [ALPM-SCRIPTLET]   -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
[2018-03-28 13:08] [ALPM-SCRIPTLET] ==> Updating trust database...
[2018-03-28 13:08] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2018-06-01
[2018-03-28 13:08] [ALPM] transaction completed
[2018-03-28 13:08] [ALPM] running 'systemd-update.hook'...
[2018-03-28 14:57] [ALPM] transaction started
[2018-03-28 14:57] [ALPM] upgraded adapta-maia-theme (3.93.0.174-1 -> 3.93.0.193-1)
[2018-03-28 14:57] [ALPM] upgraded libsystemd (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded docker (1:18.02.0-1 -> 1:18.03.0-1)
[2018-03-28 14:57] [ALPM] upgraded grub (2.03.0-2 -> 2.03.0-4)
[2018-03-28 14:57] [ALPM] upgraded libmagick (7.0.7.27-1 -> 7.0.7.27-2)
[2018-03-28 14:57] [ALPM] upgraded imagemagick (7.0.7.27-1 -> 7.0.7.27-2)
[2018-03-28 14:57] [ALPM] upgraded systemd (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded libpsl (0.20.1-1 -> 0.20.1-2)
[2018-03-28 14:57] [ALPM] upgraded hplip (3.18.3-1 -> 3.18.3-2)
[2018-03-28 14:57] [ALPM] upgraded inxi (2.9.02-2 -> 2.9.08-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-expat (2.2.2-1 -> 2.2.5-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-icu (60.1-1 -> 60.2-1)
[2018-03-28 14:57] [ALPM] upgraded libdrm (2.4.91-2 -> 2.4.91-3)
[2018-03-28 14:57] [ALPM] upgraded lib32-libdrm (2.4.91-2 -> 2.4.91-3)
[2018-03-28 14:57] [ALPM] upgraded lib32-libgcrypt (1.8.1-1 -> 1.8.2-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-llvm-libs (5.0.1-1 -> 6.0.0-1)
[2018-03-28 14:57] [ALPM] upgraded llvm-libs (5.0.1-2 -> 6.0.0-4)
[2018-03-28 14:57] [ALPM] upgraded linux414 (4.14.29-1 -> 4.14.30-1)
[2018-03-28 14:57] [ALPM] upgraded pacman-mirrors (4.8.3-2 -> 4.9.1-3)
[2018-03-28 14:57] [ALPM] upgraded xf86-input-libinput (0.26.0-1 -> 0.27.0-2)
[2018-03-28 14:57] [ALPM] upgraded mesa (17.3.7-0 -> 17.3.7-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-mesa (17.3.7-0 -> 17.3.7-1)
[2018-03-28 14:57] [ALPM] upgraded lib32-systemd (238.0-6 -> 238.51-1)
[2018-03-28 14:57] [ALPM] upgraded linux414-bbswitch (0.8-26 -> 0.8-27)
[2018-03-28 14:57] [ALPM] upgraded linux414-nvidia (1:390.42-3 -> 1:390.42-4)
[2018-03-28 14:57] [ALPM] upgraded linux414-virtualbox-host-modules (5.2.8-6 -> 5.2.8-7)
[2018-03-28 14:57] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-extension-settings (20180224-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-maia-theme (20180118-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded qt5-base (5.10.1-5 -> 5.10.1-6)
[2018-03-28 14:57] [ALPM] upgraded manjaro-gnome-settings (20180312-1 -> 20180323-1)
[2018-03-28 14:57] [ALPM] upgraded manjaro-release (17.1.6-1 -> 17.1.7-1)
[2018-03-28 14:57] [ALPM] upgraded nautilus-admin (1.1.3-1 -> 1.1.4-1)
[2018-03-28 14:57] [ALPM] upgraded netctl (1.15-1 -> 1.16-1)
[2018-03-28 14:57] [ALPM] upgraded nodejs (9.9.0-1 -> 9.9.0-2)
[2018-03-28 14:57] [ALPM] upgraded os-prober (1.76-1 -> 1.76-2)
[2018-03-28 14:57] [ALPM] upgraded pamac (6.2.5-1 -> 6.2.6-1)
[2018-03-28 14:57] [ALPM] upgraded systemd-sysvcompat (238.0-6 -> 238.51-1.1)
[2018-03-28 14:57] [ALPM] upgraded uget (2.2.0-1 -> 2.2.1-1)
[2018-03-28 14:57] [ALPM] upgraded update-notifier (0.7.4-1 -> 0.7.5-1)
[2018-03-28 14:57] [ALPM] upgraded xdg-user-dirs (0.16-1 -> 0.17-1)
[2018-03-28 14:57] [ALPM] transaction completed
[2018-03-28 14:57] [ALPM] running '60-linux414.hook'...
[2018-03-28 14:57] [ALPM] running '90-linux414.hook'...
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Starting build: 4.14.30-1-MANJARO
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Starting build: 4.14.30-1-MANJARO
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-03-28 14:57] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-03-28 14:57] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-03-28 14:57] [ALPM] running '99-grub.hook'...
[2018-03-28 14:57] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2018-03-28 14:57] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2018-03-28 14:57] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.14-x86_64
[2018-03-28 14:57] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
[2018-03-28 14:57] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-03-28 14:57] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2018-03-28 14:57] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2018-03-28 14:57] [ALPM-SCRIPTLET] done
[2018-03-28 14:57] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-03-28 14:57] [ALPM] running 'disable-gdm-night-light.hook'...
[2018-03-28 14:57] [ALPM-SCRIPTLET] 
[2018-03-28 14:57] [ALPM-SCRIPTLET] Night-light feature is enabled also in GDM screen, see
[2018-03-28 14:57] [ALPM-SCRIPTLET] here : https://bugzilla.gnome.org/show_bug.cgi?id=785273
[2018-03-28 14:57] [ALPM-SCRIPTLET] for more info.
[2018-03-28 14:57] [ALPM-SCRIPTLET] If you want to disable it please type this command:
[2018-03-28 14:57] [ALPM-SCRIPTLET] 
[2018-03-28 14:57] [ALPM-SCRIPTLET] sudo -u gdm dbus-launch --exit-with-session gsettings set org.gnome.settings-daemon.plugins.color night-light-enabled false
[2018-03-28 14:57] [ALPM-SCRIPTLET] 
[2018-03-28 14:57] [ALPM] running 'gdm-theme-maia-install.hook'...
[2018-03-28 14:57] [ALPM] running 'glib-compile-schemas.hook'...
[2018-03-28 14:57] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-03-28 14:57] [ALPM] running 'manjaro-extensions.hook'...
[2018-03-28 14:57] [ALPM] running 'manjaro-gnome-messages.hook'...
[2018-03-28 14:57] [ALPM-SCRIPTLET] 
[2018-03-28 14:57] [ALPM-SCRIPTLET] Printing support installed
[2018-03-28 14:57] [ALPM-SCRIPTLET] 
[2018-03-28 14:57] [ALPM] running 'no-tray-icon-install.hook'...
[2018-03-28 14:57] [ALPM] running 'pacman-mirrors-upgrade.hook'...
[2018-03-28 14:58] [ALPM-SCRIPTLET] .: e[1;37mINFOe[1;m Downloading mirrors from repo.manjaro.org
[2018-03-28 14:58] [ALPM-SCRIPTLET] hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.
[2018-03-28 14:58] [ALPM] running 'systemd-catalog.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-hwdb.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-sysctl.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-sysusers.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-udev-reload.hook'...
[2018-03-28 14:58] [ALPM] running 'systemd-update.hook'...
[2018-03-28 14:58] [ALPM] running 'texinfo-install.hook'...
[2018-03-28 14:58] [ALPM] running 'update-desktop-database.hook'...
[2018-03-28 14:58] [ALPM] running 'update-mime-database.hook'...
[2018-03-28 15:02] [ALPM] transaction started
[2018-03-28 15:02] [ALPM] upgraded gitkraken (3.4.1-1 -> 3.5.0-1)
[2018-03-28 15:02] [ALPM] transaction completed
[2018-03-28 15:02] [ALPM] running 'systemd-update.hook'...
[2018-03-28 15:02] [ALPM] running 'update-desktop-database.hook'...
[2018-03-28 17:15] [ALPM] transaction started
[2018-03-28 17:15] [ALPM] installed qt5-imageformats (5.10.1-1)
[2018-03-28 17:15] [ALPM] installed telegram-desktop (1.2.14-2)
[2018-03-28 17:15] [ALPM] transaction completed
[2018-03-28 17:15] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-03-28 17:15] [ALPM] running 'systemd-update.hook'...
[2018-03-28 17:15] [ALPM] running 'update-desktop-database.hook'...

#11

Update! Today’s updates resolved the issue. I’m not sure exactly which package did it, but I’m attaching the list of what was updated for reference.

[2018-04-02 12:24] [ALPM] transaction started
[2018-04-02 12:24] [ALPM] removed gitkraken (3.5.0-1)
[2018-04-02 12:24] [ALPM] transaction completed
[2018-04-02 12:24] [ALPM] running 'systemd-update.hook'...
[2018-04-02 12:24] [ALPM] running 'update-desktop-database.hook'...
[2018-04-02 12:25] [PAMAC] synchronizing package lists
[2018-04-02 12:25] [ALPM] transaction started
[2018-04-02 12:26] [ALPM] upgraded linux414 (4.14.30-1 -> 4.14.31-1)
[2018-04-02 12:26] [ALPM] upgraded linux414-bbswitch (0.8-27 -> 0.8-28)
[2018-04-02 12:26] [ALPM] upgraded linux414-nvidia (1:390.42-4 -> 1:390.42-5)
[2018-04-02 12:26] [ALPM] upgraded linux414-virtualbox-host-modules (5.2.8-7 -> 5.2.8-8)
[2018-04-02 12:26] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2018-04-02 12:26] [ALPM] upgraded pamac (6.2.6-1 -> 6.2.7-1)
[2018-04-02 12:26] [ALPM] upgraded udisks2 (2.7.6-1 -> 2.7.6-1.1)
[2018-04-02 12:26] [ALPM] transaction completed
[2018-04-02 12:26] [ALPM] running '60-linux414.hook'...
[2018-04-02 12:26] [ALPM] running '90-linux414.hook'...
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Starting build: 4.14.31-1-MANJARO
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Starting build: 4.14.31-1-MANJARO
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-04-02 12:26] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-04-02 12:26] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-02 12:26] [ALPM] running '99-grub.hook'...
[2018-04-02 12:26] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2018-04-02 12:26] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2018-04-02 12:26] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.14-x86_64
[2018-04-02 12:26] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
[2018-04-02 12:26] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-04-02 12:26] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2018-04-02 12:26] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2018-04-02 12:26] [ALPM-SCRIPTLET] done
[2018-04-02 12:26] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-04-02 12:26] [ALPM] running 'no-tray-icon-install.hook'...
[2018-04-02 12:26] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-04-02 12:26] [ALPM] running 'systemd-udev-reload.hook'...
[2018-04-02 12:26] [ALPM] running 'systemd-update.hook'...
[2018-04-02 12:26] [ALPM] running 'update-desktop-database.hook'...
[2018-04-02 12:26] [ALPM] running 'update-mime-database.hook'...
[2018-04-02 12:26] [ALPM] transaction started
[2018-04-02 12:26] [ALPM] installed qt5-xmlpatterns (5.10.1-1)
[2018-04-02 12:26] [ALPM] installed qt5-declarative (5.10.1-3)
[2018-04-02 12:26] [ALPM] installed qt5-webchannel (5.10.1-1)
[2018-04-02 12:26] [ALPM] installed qt5-location (5.10.1-1)
[2018-04-02 12:26] [ALPM] installed qt5-webengine (5.10.1-1)
[2018-04-02 12:26] [ALPM] installed qt5-quickcontrols2 (5.10.1-1)
[2018-04-02 12:26] [ALPM] transaction completed
[2018-04-02 12:26] [ALPM] running 'systemd-update.hook'...
[2018-04-02 12:37] [ALPM] transaction started
[2018-04-02 12:38] [ALPM] upgraded android-studio (3.0.1.0-1 -> 3.1.0.16-1)
[2018-04-02 12:38] [ALPM] transaction completed
[2018-04-02 12:38] [ALPM] running 'systemd-update.hook'...
[2018-04-02 12:38] [ALPM] running 'update-desktop-database.hook'...
[2018-04-02 12:40] [ALPM] transaction started
[2018-04-02 12:40] [ALPM] upgraded zoom (2.0.115900.1201-1 -> 2.0.123086.0330-1)
[2018-04-02 12:40] [ALPM] transaction completed
[2018-04-02 12:40] [ALPM] running 'systemd-update.hook'...
[2018-04-02 12:40] [ALPM] running 'update-desktop-database.hook'...
[2018-04-02 12:40] [ALPM] running 'update-mime-database.hook'...

#12

Update, rebooted today and the issue has returned…

Nothing in pacman.log appears to be related. Perhaps the issue was never resolved in the first place and is actually intermittent?

[2018-04-02 12:40] [ALPM] running 'update-mime-database.hook'...
[2018-04-02 16:19] [PAMAC] synchronizing package lists
[2018-04-04 11:40] [PAMAC] synchronizing package lists
[2018-04-04 11:40] [ALPM] transaction started
[2018-04-04 11:40] [ALPM] upgraded mesa (17.3.7-1 -> 17.3.8-1)
[2018-04-04 11:40] [ALPM] upgraded lib32-mesa (17.3.7-1 -> 17.3.8-1)
[2018-04-04 11:40] [ALPM] transaction completed
[2018-04-04 11:40] [ALPM] running 'systemd-update.hook'...
[2018-04-04 11:41] [ALPM] transaction started
[2018-04-04 11:41] [ALPM] installed qt5-sensors (5.10.1-1)
[2018-04-04 11:41] [ALPM] installed qt5-webkit (5.212.0alpha2-12)
[2018-04-04 11:41] [ALPM] installed qt5-quickcontrols (5.10.1-1)
[2018-04-04 11:41] [ALPM] installed lib32-libxrandr (1.5.1-1)
[2018-04-04 11:41] [ALPM] transaction completed
[2018-04-04 11:41] [ALPM] running 'systemd-update.hook'...
[2018-04-04 11:42] [ALPM] transaction started
[2018-04-04 11:42] [ALPM] upgraded teamviewer (12.0.90041-7 -> 13.1.3026-9)
[2018-04-04 11:42] [ALPM-SCRIPTLET] The Teamviewer daemon must be running for Teamviewer to work.
[2018-04-04 11:42] [ALPM-SCRIPTLET] Execute 'sudo systemctl enable teamviewerd' in a terminal.
[2018-04-04 11:42] [ALPM] transaction completed
[2018-04-04 11:42] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-04-04 11:42] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-04-04 11:42] [ALPM] running 'systemd-update.hook'...
[2018-04-04 11:42] [ALPM] running 'update-desktop-database.hook'...
[2018-04-06 16:07] [PAMAC] synchronizing package lists
[2018-04-06 16:08] [ALPM] running 'firefox-pre.hook'...
[2018-04-06 16:08] [ALPM] transaction started
[2018-04-06 16:08] [ALPM] upgraded firefox (59.0.1-1 -> 59.0.2-0)
[2018-04-06 16:08] [ALPM] transaction completed
[2018-04-06 16:08] [ALPM] running 'firefox-post.hook'...
[2018-04-06 16:08] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-04-06 16:08] [ALPM] running 'systemd-update.hook'...
[2018-04-06 16:08] [ALPM] running 'update-desktop-database.hook'...