For Nvidia Optimus owners only, with Bumblebee and proprietary Nvidia video driver installed.
Beware: do not - repeat, do not - upgrade virtualgl package from 2.5.1-1 to 2.5.2-1. An upgrade will result in kernel panic on next boot. The system will be unusable.
The package was already installed during Bumblebee and prop Nvidia driver installation. Its files already exist in filesystem. Fortunately, thanks to this fact, a simple upgrade does not not succeed. Like in example below:
┌──[just]@[alexarc]:~$ └─> sudo pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date antergos is up to date apricity-core is up to date nurunner is up to date nurunner-extra is up to date netrunner is up to date bluestar is up to date bluestar-plasma is up to date :: Starting full system upgrade... warning: cinnamon: ignoring package upgrade (3.0.7-2 => 3.2.8-1) resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change Download Size community/virtualgl 2.5.1-1 2.5.2-1 0.02 MiB 0.66 MiB Total Download Size: 0.66 MiB Total Installed Size: 2.72 MiB Net Upgrade Size: 0.02 MiB :: Proceed with installation? [Y/n] Y :: Retrieving packages... virtualgl-2.5.2-1-x86_64 677.5 KiB 3.82M/s 00:00 [-------] 100% (1/1) checking keys in keyring [-------] 100% (1/1) checking package integrity [-------] 100% (1/1) loading package files [-------] 100% (1/1) checking for file conflicts [-------] 100% error: failed to commit transaction (conflicting files)virtualgl: /usr/bin/glxinfo exists in filesystem virtualgl: /usr/lib64 exists in filesystem virtualgl: /usr/lib64/libdlfaker.so exists in filesystem virtualgl: /usr/lib64/libgefaker.so exists in filesystem virtualgl: /usr/lib64/libvglfaker-nodl.so exists in filesystem virtualgl: /usr/lib64/libvglfaker.so exists in filesystem Errors occurred, no packages were upgraded. ┌──[just]@[alexarc]:~$ └─>
Do not try to install virtualgl 2.5.2-1. It is possible, but I intentionally don’t say how to do it. If you insist and install it, the system will most probably break on shutdown, and for sure will end up in kernel panic on the next boot.
Verified it three times here.
Without a doubt it’s a serious bug. I know nothing about it yet - except the fact that it breaks the system. It’s late here, will start to investigate tomorrow morning.
Do not install virtualgl 2.5.2-1.