/srv/irclogs.ubuntu.com/2016/06/03/#ubuntu-x.txt

achianghello, i was trying to fix my trackpad in 14.04 and it seems i broke it worse08:28
achiangi dropped in a 50-synaptics.conf into /usr/share/X11/xorg.conf.d/08:29
achiangit didn't have the effect that i wanted, namely it killed my trackpad08:29
achiangso I removed the file and rebooted08:29
achiangbut now the trackpad still refuses to boot08:29
achiangquestion is: does X cache settings somewhere?08:29
achiangsorry, trackpad refuses to work, not boot08:30
tjaaltonno08:30
achianghm, then my only other theory is that i flipped some hw register or something, and now it's persisten?08:31
achiangthe attempted changes, that is08:31
achiangdoes that sound plausible?08:32
tjaaltonnot to me08:32
achianghm08:32
achiangfwiw, i was experiencing the symptoms here, and dropped in the linked conf file -- http://askubuntu.com/questions/657258/chrome-two-finger-scroll-then-right-clicks08:33
achiangany ideas on how to recover would be greatly appreciated...08:33
achiangclickpad still responds to clicks, but can't move the cursor around08:34
tjaaltonshutdown, remove battery and wait for a bit?08:35
achiangha. well, it's an xps13 so battery seems not removable08:36
achiangthis is interesting... output from xinput list08:38
achiangachiang@twiga:~$ xinput list08: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:38
achianglooks like i have 2 touchpads configured? 08:39
achiangmaybe the 06CB:76AD device is conflicting with the TouchPad device?08:39
tjaaltoni don't know08:39
=== bigpet_ is now known as bigpet
tseliotisn't one a touchscreen?09:04
achiangtseliot: the ELAN device is a touchscreen09:52
achiangthe other two devices are both touchpads, I think09:52
tseliotmessed up udev rules?09:53
tseliotif you change a property on one touchpad, what happens to the other one?09:54
tseliot(assuming they are the same device)09:54
tjaaltondid you muck with bios settings?09:57
tjaaltonor change the kernel09:57
Sarvattachiang: did you install x-x-i-libinput at any point in time?10:02
tjaaltonthe only proper driver ;)10:03
Sarvattunless you want to adjust settings in a gui10:04
Sarvattthat isnt gnome not in ubuntu yet :D10:04
tjaaltonit's perfect, no need for that10:22
=== JanC is now known as Guest27710
=== JanC_ is now known as JanC
jcastrotseliot: those fixes for getting the krita snap to work, will those also make their way into the ppa drivers?15:01
tseliotjcastro: 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:30
mamarleyI guess it also needs to be forward-ported to 367 then.15:57
mamarleyOoh, reported by SABDFL himself.15:57
ricotztseliot, I see16:05
mamarleyricotz: I am on lunch break so I can go ahead and do 367 now.16:06
mamarleyDid you want 364 done too?16:06
ricotzmamarley, go ahead :), I am busy currently16:07
mamarleyOK16:07
tseliotthanks16:13
mamarleyArgh, lots of failed hunks and fuzz.16:14
* mamarley loves fixing patches.16:14
mamarleytseliot: I notice that the patch does not appear to have any support for i386 on amd64 systems.  Is that intentional?16:17
mamarley(Can 32-bit snaps even be installed on 64-bit systems?)16:18
tseliotmamarley: I'm not really sure, as I'm not familiar with snaps. mvo wrote the code16:19
ricotzof course this only applies to xenial/yakkety16:20
mamarleyCorrect.16:20
tseliotyep16:20
tseliotsnaps are only for >= xenial16:20
mamarleytseliot: 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:36
tseliotmamarley: can I see the full output, please?16:37
tseliot361 built fine here. I haven't tried 367 yet16:37
mamarleytseliot: It build fine, but displays a bunch of new warnings.  http://paste.ubuntu.com/16952010/16:38
tseliotmamarley: I think dh_systemd is calling the same thing on all the packages, whereas it should only be nvidia-36716:40
tseliotno -dev, etc.16:40
mamarleytseliot: Did it not display the same warning on 361?16:41
tseliotmamarley: yes, it did it even for transitional packages16:42
tseliotthat should be easily fixed16:42
mamarleyOK, so it isn't my refresh of the patch causing the problem.16:42
tseliotnope16:42
mamarleyI don't know how to fix it though.16:44
mamarleytseliot: Should I just leave it for now since the same patch has already been uploaded into the main respository?16:47
tseliotmamarley: yes, go with what we have right now. I'll fix it myself next week16:48
mamarleyOK16:48
mamarleyricotz: 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:52
mamarleyI 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.18:53
mamarleyNevermind, it was a dummy mistake on my part.  The 364 build should work this time.19:09
mamarleyricotz: OK, everything is published now.19:52
ricotzmamarley, checked and copied :)20:08

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!