[09:31] hiho [09:31] mamarley: so far we had version 415.18 now i see update to 415.18.02 [09:32] wasn't those 2 parts verison mubered for vulkan version only? [09:32] *3 parts [11:11] soee_: Yes, 415.18.02 was released. The only advertised improvement was Vulkan stuff, but there is no way of knowing if they changed anything else. The driver is already packaged in my staging PPA though. [14:03] ricotz, mamarley: hey, did you have the chance to look into the vulkan issue with multi-arch? (the empty changelog on i386) [14:04] I didn't even know that was a thing. [14:04] https://www.linuxuprising.com/2018/11/fix-nvidia-graphics-drivers-ppa.html [14:05] mamarley: I discussed it briefly with ricotz yesterday [14:07] tseliot: Oh, that. I had a user complaining to me about that. I figured it had something to do with us rebasing our 410 and 415 drivers on the 410 you uploaded to disco, but I couldn't figure out what had happened and I couldn't reproduce the issue myself. [14:07] I also didn't know it had to do anything with i386 specifically, because I never tested Vulkan in 32-bit mode. [14:10] mamarley: actually, I've just noticed that the amd64 deb is the problem, not the i386 one [14:10] mamarley: libnvidia-gl-410_410.78-0ubuntu1_amd64/data/usr/share/doc/libnvidia-gl-410/changelog.Debian.gz is not a valid gz file [14:11] What does that have to do with Vulkan not working? [14:11] mamarley: I think it's a problem if the two files from both architectures don't match [14:12] do you know exactly when this started? (in terms of git commit)? [14:12] Git commit to what? [14:12] mamarley: in my repository [14:13] as you said you were rebasing your code on mine [14:14] I didn't mean a git rebase, I meant I just abandoned what we had been using for 410 and 415 and updated the 410 release you uploaded to Disco to 415. [14:14] Isn't that file generated automatically as part of the build anyway? [14:18] mamarley: yes, I was just wondering if we could pin the regression down to a change of mine