[08:28] <achiang> hello, i was trying to fix my trackpad in 14.04 and it seems i broke it worse
[08:29] <achiang> i dropped in a 50-synaptics.conf into /usr/share/X11/xorg.conf.d/
[08:29] <achiang> it didn't have the effect that i wanted, namely it killed my trackpad
[08:29] <achiang> so I removed the file and rebooted
[08:29] <achiang> but now the trackpad still refuses to boot
[08:29] <achiang> question is: does X cache settings somewhere?
[08:30] <achiang> sorry, trackpad refuses to work, not boot
[08:30] <tjaalton> no
[08:31] <achiang> hm, then my only other theory is that i flipped some hw register or something, and now it's persisten?
[08:31] <achiang> the attempted changes, that is
[08:32] <achiang> does that sound plausible?
[08:32] <tjaalton> not to me
[08:32] <achiang> hm
[08:33] <achiang> fwiw, i was experiencing the symptoms here, and dropped in the linked conf file -- http://askubuntu.com/questions/657258/chrome-two-finger-scroll-then-right-clicks
[08:33] <achiang> any ideas on how to recover would be greatly appreciated...
[08:34] <achiang> clickpad still responds to clicks, but can't move the cursor around
[08:35] <tjaalton> shutdown, remove battery and wait for a bit?
[08:36] <achiang> ha. well, it's an xps13 so battery seems not removable
[08:38] <achiang> this is interesting... output from xinput list
[08:38] <achiang> achiang@twiga:~$ xinput list
[08:38] <achiang> ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
[08:38] <achiang> ⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
[08:38] <achiang> ⎜   ↳ ELAN Touchscreen                        	id=10	[slave  pointer  (2)]
[08:38] <achiang> ⎜   ↳ DLL0665:01 06CB:76AD                    	id=12	[slave  pointer  (2)]
[08:38] <achiang> ⎜   ↳ SynPS/2 Synaptics TouchPad              	id=14	[slave  pointer  (2)]
[08:38] <achiang> ⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
[08:39] <achiang> looks like i have 2 touchpads configured? 
[08:39] <achiang> maybe the 06CB:76AD device is conflicting with the TouchPad device?
[08:39] <tjaalton> i don't know
=== bigpet_ is now known as bigpet
[09:04] <tseliot> isn't one a touchscreen?
[09:52] <achiang> tseliot: the ELAN device is a touchscreen
[09:52] <achiang> the other two devices are both touchpads, I think
[09:53] <tseliot> messed up udev rules?
[09:54] <tseliot> if you change a property on one touchpad, what happens to the other one?
[09:54] <tseliot> (assuming they are the same device)
[09:57] <tjaalton> did you muck with bios settings?
[09:57] <tjaalton> or change the kernel
[10:02] <Sarvatt> achiang: did you install x-x-i-libinput at any point in time?
[10:03] <tjaalton> the only proper driver ;)
[10:04] <Sarvatt> unless you want to adjust settings in a gui
[10:04] <Sarvatt> that isnt gnome not in ubuntu yet :D
[10:22] <tjaalton> it's perfect, no need for that
=== JanC is now known as Guest27710
=== JanC_ is now known as JanC
[15:01] <jcastro> tseliot: those fixes for getting the krita snap to work, will those also make their way into the ppa drivers?
[15:30] <tseliot> jcastro: good point, mamarley, ricotz, the fix for LP: ##1588192 is in both yakkety and xenial-proposed. 361 and 340 are available. I haven't finished my work on 304 yet.
[15:57] <mamarley> I guess it also needs to be forward-ported to 367 then.
[15:57] <mamarley> Ooh, reported by SABDFL himself.
[16:05] <ricotz> tseliot, I see
[16:06] <mamarley> ricotz: I am on lunch break so I can go ahead and do 367 now.
[16:06] <mamarley> Did you want 364 done too?
[16:07] <ricotz> mamarley, go ahead :), I am busy currently
[16:07] <mamarley> OK
[16:13] <tseliot> thanks
[16:14] <mamarley> Argh, lots of failed hunks and fuzz.
[16:14]  * mamarley loves fixing patches.
[16:17] <mamarley> tseliot: I notice that the patch does not appear to have any support for i386 on amd64 systems.  Is that intentional?
[16:18] <mamarley> (Can 32-bit snaps even be installed on 64-bit systems?)
[16:19] <tseliot> mamarley: I'm not really sure, as I'm not familiar with snaps. mvo wrote the code
[16:20] <ricotz> of course this only applies to xenial/yakkety
[16:20] <mamarley> Correct.
[16:20] <tseliot> yep
[16:20] <tseliot> snaps are only for >= xenial
[16:36] <mamarley> tseliot: I get all sorts of "Could not find "var-lib-snapd-lib-gl.mount" in the /lib/systemd/system directory of nvidia-367-dev" when building.  Is that to be expected?
[16:37] <tseliot> mamarley: can I see the full output, please?
[16:37] <tseliot> 361 built fine here. I haven't tried 367 yet
[16:38] <mamarley> tseliot: It build fine, but displays a bunch of new warnings.  http://paste.ubuntu.com/16952010/
[16:40] <tseliot> mamarley: I think dh_systemd is calling the same thing on all the packages, whereas it should only be nvidia-367
[16:40] <tseliot> no -dev, etc.
[16:41] <mamarley> tseliot: Did it not display the same warning on 361?
[16:42] <tseliot> mamarley: yes, it did it even for transitional packages
[16:42] <tseliot> that should be easily fixed
[16:42] <mamarley> OK, so it isn't my refresh of the patch causing the problem.
[16:42] <tseliot> nope
[16:44] <mamarley> I don't know how to fix it though.
[16:47] <mamarley> tseliot: Should I just leave it for now since the same patch has already been uploaded into the main respository?
[16:48] <tseliot> mamarley: yes, go with what we have right now. I'll fix it myself next week
[16:48] <mamarley> OK
[18:52] <mamarley> ricotz: I have compiled and tested 367.18 with the snappy patch.  Any objection to me copying that to the main PPA?  I also have nvidia-settings 367 that I never copied.
[18:53] <mamarley> I got 364 patched too, but there is some old orig.tar.gz junk in my staging PPA that is preventing it from compiling unless I do a full source upload, so I propose to upload that directly to the main PPA.
[19:09] <mamarley> Nevermind, it was a dummy mistake on my part.  The 364 build should work this time.
[19:52] <mamarley> ricotz: OK, everything is published now.
[20:08] <ricotz> mamarley, checked and copied :)