[09:13] <tjaalton> meh, installing nvidia kinda blacklists nouveau but not exactly
[09:16] <tjaalton> nouveau still gets loaded here
[09:20] <tjaalton> nvidia-352_hybrid.conf is not included in the initrd
[09:20] <tjaalton> etc/modprobe.d/nvidia-352_hybrid.conf
[09:20] <tjaalton> where's tseliot.. :)
[09:24] <tjaalton> with that fixed, hybrid on current xenial is totally busted, yes
[09:57] <tjaalton> tseliot: hi, so nvidia hybrid is broken here too with stock xenial
[09:58] <tjaalton> now the question is, what changed since wily, where I assume it worked
[09:58] <tjaalton> xserver didn't
[09:59] <tseliot> modesetting?
[09:59] <tseliot> or maybe some options are default now?
[09:59] <tjaalton> builtin
[10:00] <tjaalton> have you tried xenial?
[10:00] <tseliot> since that's common, I need to debug this myself here
[10:00] <tseliot> yes but I haven't tried the PPA
[10:00] <tjaalton> no this is stock xenial
[10:01] <tjaalton> doesn't need the ppa to trigger
[10:01] <tjaalton> also, first boot after installing the driver nouveau blacklist wasn't effective
[10:01] <tjaalton> enabled it via the additinal drivers thing
[10:01] <tjaalton> +o
[10:05] <tjaalton> and it didn't have the restart button
[10:05] <tjaalton> after the driver was installed
[10:07] <tseliot> ah
[10:07] <tseliot> ok, I'll try stock xenial again then
[10:08] <tseliot> I always use apt-get to install nvidia BTW
[10:08] <tjaalton> dunno what users use
[10:09] <tjaalton> but this is available, and I remember seeing crasher bugs where the system hadn't been restarted but just logged out and back in
[10:09] <tseliot> it should be the same though
[10:09] <tseliot> I'm not sure about the restart notification
[10:14] <tjaalton> vivid seems fine, but prime-switch segfaults
[10:14] <tjaalton> when run as user
[10:16] <tjaalton> as root it complains "/etc/modprobe.d is not a file"
[10:16] <tjaalton> and "no alternatives for x86_64-linux-gnu_gfxcore_conf"
[10:17] <tjaalton> upgrading this to wily then
[10:26] <tseliot> those two are just warnings
[10:27] <tjaalton> but why?-)
[10:27] <tseliot> the latter is expected, as only fglrx has that alternative
[10:28] <tseliot> the former is just for debugging
[10:28] <tseliot> prime-switch requires root privileges
[10:28] <tseliot> also the version of gpu-manager in vivid is old
[10:28] <tjaalton> which one should a noob user run?
[10:29] <tseliot> switching between profiles is done through nvidia-settings
[10:29] <tseliot> with a nice UI
[10:29] <tjaalton> ok
[10:29] <tseliot> assuming the driver works correctly
[10:30] <tjaalton> right
[10:32] <tseliot> let me update my xenial installation
[10:32] <tseliot> BTW if nouveau wasn't blacklisted, either the alternative was not set or the initramfs hadn't been updated yet
[10:34] <tjaalton> well driver installation didn't run update-initramfs then
[10:35] <tseliot> the package should have (in the postinst)
[10:39] <tseliot> mamarley: "The NVIDIA Linux OpenGL driver added support for GLVND with the release of the 361.16 beta driver. During the beta test phase, it was discovered that several applications relied on behaviors or attributes of the NVIDIA OpenGL driver that fall outside of the Linux OpenGL ABI [2]. As the GLVND-based libGL.so.1 library does not share these behaviors or attributes with the NVIDIA OpenGL driver, this resulted in incorrect behavior from applications 
[10:40] <tseliot> "Please contact the vendors of any applications that are not compatible with GLVND to ensure that their applications be updated for compatibility with GLVND."
[10:41] <tjaalton> har har
[10:46] <tseliot> mamarley: "We have heard back from NVIDIA. They have confirmed this is a driver bug impacting the libglvnd-enabled driver (nobody but Archlinux at the moment). The driver bug will be fixed in a future release. For now, they recommend setting __GLVND_DISALLOW_PATCHING=1 as a workaround, although also setting __GL_THREADED_OPTIMIZATIONS=0 will work (although potentially more perf impact)." https://github.com/ValveSoftware/Dota-2/issues/756
[10:47] <tseliot> (that's in Steam, I suppose)
[11:05] <mamarley> Thanks!
[11:46] <soee> mamarley: will you be able to rebuild the package to make it work ?
[11:46] <soee> or do we have to wait for next release ?
[11:47] <mamarley> soee: NVIDIA confirmed it is a bug in the driver.  There is a workaround, however, which is to launch the application with the __GLVND_DISALLOW_PATCHING=1 environment variable set.
[11:56] <soee> mamarley: how can i set his variable ?
[11:56] <soee> *this
[12:11] <mamarley> soee: It might work to do "export __GLVND_DISALLOW_PATCHING=1" in a terminal window before launching Steam from that terminal window.  Like I said, I don't have Steam, so I can't test it.