/srv/irclogs.ubuntu.com/2010/03/12/#ubuntu-x.txt

brycehSarvatt, hey did you get an arsenal script to search through Xorg.0.log files?01:11
superm1Sarvatt, bug 53780101:51
ubottuLaunchpad bug 537801 in xf86-input-wacom "Touchscreen doesn't work after karmic->lucid upgrade" [Undecided,New] https://launchpad.net/bugs/53780101:51
superm1wait a minute, it asked me if i want to include my "sensitive" logs from gdm and then makes the bug public?01:51
superm1that doesn't seem right01:51
brycehsuperm1, it takes sudo privs to access them02:20
brycehsuperm1, but we're not going to manually eyeball the gdm scripts to sanitize them of any sensitive info02:20
brycehI'm not really even sure why they require su to look at them02:21
superm1ah i see02:22
Sarvattsuperm1: ohh boy..02:38
Sarvattthat device actually has a proprietary blob driver not in ubuntu02:39
Sarvattevtouch is whats supposed to support it for the basics, wacom is just taking control of it02:39
Sarvattthis is the driver for ubuntu btw - http://www.ideacom.com.tw/download/DRIVE/IDC_Linux_3_1_0.tar.gz 02:44
superm1Sarvatt, it worked without it though in karmic?02:44
superm1so i guess evtouch was grabbing it in karmic then based on what you're saying02:48
superm1but that appears to be in universe now in lucid?02:49
Sarvattyeah, I'm really unsure of the status of evtouch in lucid, it doesn't even look to be functional with a udev xserver at first glance?02:51
superm1it looks like it's depending on an old version of xserver-xorg-core02:51
superm1unstable looks to have a patch for x server 1.702:58
Sarvatthttp://packages.debian.org/squeeze/xserver-xorg-input-evtouch02:58
Sarvattyeah02:58
Sarvattbryce was looking into syncing it earlier02:58
superm1so is our delta droppable then?02:58
Sarvattthe delta is all fdi files it looks like which are not functional anymore and need translating into udev rules, that's going to need some serious work03:04
superm1is there a guide for doing that?03:07
superm1looking at th existing rules, it seems a lot of them are just setting the x driver, not any bits03:08
superm1oh synaptics seems to do options too03:09
superm1oh but what a disgusting init script it had03:11
superm1i am starting to think i dont want to commit to helping with this ;)03:11
brycehyeah I put in a sync request on -evtouch yesterday.  Waiting on an archive admin to flag it through03:12
Sarvattneed to be sure it'd actually even work before anyway, i'd start by grabbing the one from squeeze and adding your device to the udev rules it has to see if it even works03:12
brycehI don't know if the current evtouch driver works, but it certainly doesn't build against xserver03:12
brycehtjaalton didn't think the fdi's would need converted to udev03:13
brycehhowever I wrote a page explaiing how to do this on the ubuntu-x wiki, in the input config section03:13
Sarvatti need to find a really cheap evtouch device03:14
superm1Sarvatt, http://configure.us.dell.com/dellstore/config.aspx?oc=blcwwfp&c=us&l=en&s=bsd&cs=04&kc=vostro-v1303:15
superm1that's what i have03:15
Sarvatta bit out of my price range :) i think they sell cheapo usb digitizers people use to convert existing screens that work with evtouch though03:17
Sarvattso we need a udev rule that sets the symlink, port all our hal matches and quirks to it, and figure out how to not have wacom interfere with it and vice versa because it seems wacom is loading for everything that matches ID_INPUT_TABLET03:37
* Sarvatt wishes we had xorg.conf.d right about now03:37
brycehdon't we?03:37
Sarvattnope thats xserver 1.803:38
brycehI think tjaalton backported it03:40
brycehmaybe I'm wrong03:41
Sarvatthe was playing with it but i'm not sure its something sane to backport especially this late, he had to remove the input abi bump in that came with it and remove ifdef's for the higher input abi so wacom would work with it and i have no idea if other drivers have similar things03:45
Sarvattsuperm1: does your device work if you remove /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules ?03:49
Sarvattpackaging that blob ideacom driver seems like a good idea even if I just throw it in a PPA, asus and dell are both using that same device for their netbook touchscreens :D04:01
superm1Sarvatt, it would be best to get it in restricted tbh04:04
superm1Sarvatt, i just installed the debian package and things didn't work, i'll brb and try to remove that rule04:04
superm1Sarvatt, well without that rule wacom doesn't load, but evtouch isn't loading either04:08
superm1so i'm guessing it still needs some kind of udev rule04:08
Sarvattyeah evdev should be taking it without the wacom rule, I was wondering if evdev was working with it04:09
superm1http://pastebin.com/PCzdX3pV04:09
Sarvattdoes that device show up in lsusb?04:13
Sarvattif so can you pastebin lsusb -v?04:14
superm1http://pastebin.com/hFry6d9y04:14
superm1looks like yea04:15
Sarvattsuperm1: maybe something like this as say /lib/udev/rules.d/67-xorg-evtouch.rules -- http://pastebin.com/0FmeGQpm04:50
Sarvattor maybe just dropping lines 10-20 even if that doesn't work04:52
tjaaltonsuperm1, Sarvatt: yeah wacom shouldn't be the "catch-all" tablet driver, but evdev04:59
tjaaltonand xorg.conf.d doesn't really work for video drivers, because they need more than just the Driver section (in order to do fallbacks for instance)05:00
tjaaltonsuperm1: so try to get evdev load, it should match evtouch in functionality05:01
tjaalton+to05:01
superm1Sarvatt, that udev rule didn't do the trick05:05
superm1nor with removing lines 15-2005:05
tjaaltonmove the wacom rule away, does it load evdev then?05:07
superm1i posted the pastebin above with wacom out of the way05:09
superm1i'm a bit confused, it looked like it tried to load evdev for a joystick device05:09
tjaaltonheh, yeah it needs a patch to only load for event*05:13
tjaaltontype: MOUSE05:14
tjaaltonso probably got it wrong then05:14
Sarvattelographics seems to have fallen through the cracks too, lucid archive and debian git versions dont compile against xserver 1.705:24
Sarvattluckily theres http://cvs.fedoraproject.org/viewvc/devel/xorg-x11-drv-elographics/elographics-1.2.3-abi.patch?view=markup05:25
Sarvattsame with mutouch http://cvs.fedoraproject.org/viewvc/devel/xorg-x11-drv-mutouch/mutouch-1.2.1-abi.patch?view=markup05:27
tjaaltonluckily? those should just die :)05:28
libvtjaalton: about xorg.conf.d; it could've worked for graphics drivers06:47
libvbut the modesetting model adopted for RandR1.2 lacked the expressivity to do this properly06:48
libvand now people are all on kms anyway, so there is no point going there (as "relevant" drivers will not go close anyway)06:49
tjaaltonlibv: ok08:16
tjaaltonis the intel gpu lockup thingie a bit trigger happy perhaps?08:45
tjaaltonintel has 50 more bugs than nvidia-180, 509 and counting :)08:46
jcristaubryceh: xserver -1u3 is not in git?14:31
=== yofel_ is now known as yofel
=== radoe_ is now known as radoe
=== Sinnerman is now known as Cobalt
unggnuhi all17:19
unggnuI have some problems with font rendering and Intel since quite some time. Karmic is affected and Lucid too. It seems better since the 2.6.33 drm but lately I have seen it again. Some lines are just black or completly white and if I scroll them out of the view and back again they are fine. What's the best way to debug things like that?17:20
unggnuBut there definately seem to be less corruptions than before 2.6.33 drm17:21
unggnuOr does it might also be a Firefox problem?17:21
=== Sinnerman is now known as Cobalt
unggnuBtw. is the overlay support backported in the -intel driver for Lucid?17:23
sebnerbryceh: around by any chance?20:27
Sarvatthmm  ${SHA1_LIB} was removed from XSERVER_SYS_LIBS in the newest xserver 1.7.5.902 ( http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.7-branch&id=ff5fb43a4b38c707a1a9948ace621a62b5b2457a ), our xkb cache patch isn't working now and looks related to that20:30
Sarvatthttp://launchpadlibrarian.net/40884919/buildlog_ubuntu-lucid-i386.xorg-server_2:1.7.5.902~git20100312%2Bserver-1.7-branch.5a2b3f36-0ubuntu0sarvatt_FAILEDTOBUILD.txt.gz20:30
brycehSarvatt, hrm20:31
brycehSarvatt, was there a rationale for removing it?20:31
tjaaltonlooks like a mistake20:40
bjsniderok, why is nvidia-current creating libvdpau_nvidia.so.1 as a link to the .so version?20:45
bjsnidermy package creates the .so version as a link to the 19x.xx.xx file, which is the soname of the library. but why is a .so.1 link necessary too?20:48
superm1bjsnider, probably want to raise that again whenever tseliot is in the room20:49
bjsniderwhy are the old packaging scripts set up to create the links in the .links files as well as manually in the rules file?20:51
superm1They're old :)20:52
tjaaltonlooks like a mistake20:52
tjaalton(echo)20:52
bjsniderwhy isn't it sunny today...20:52
bjsniderok, i'm going to retire from the question asking business20:52
superm1haha20:52
bjsniderwhat i don't understand is, if a library has a soname of anything except 1, for example 52 like libavcodec, you have libavcodec.so.5220:55
bjsniderthen you have a link, libavcodec.so that points to it20:55
bjsnideri can understand that link20:55
bjsniderthe linker doesn't know for sure what the soname is, so you need that generic link20:55
bjsniderbut why create the .so.1 link?20:56
bjsnidereverything seems to need a .so.1 link even if the soname isn't actually 120:56
tjaaltonThe run-time library package should include the symbolic link that ldconfig would create for the shared libraries. For example, the libgdbm3 package should include a symbolic link from /usr/lib/libgdbm.so.3 to libgdbm.so.3.0.0. This is needed so that the dynamic linker (for example ld.so or ld-linux.so.*) can find the library between the time that dpkg installs it and the time that ldconfig is run in the postinst script20:59
tjaaltonfrom the debian policy21:00
jarekWho can build package with current openchrome trunk? It can resolve many bugs for via chips.21:01
jarekI can test it on my laptop21:02
tjaaltonjarek: what about the version on debian?21:02
tjaaltonit should be synced anyway21:02
jarekit's quite old for debian21:03
jarekSo, I need to contact with debian devs?21:04
tjaaltonhuh, old?21:04
jarekwithout latest commits ;)21:04
jarekcurrent svn is 840, but package is 81221:06
tjaaltonright21:06
jarekther is patch witch can fix problem with resolution on my laptop21:07
jarekI want test it, but I am not familiar with compilation that kind of stuff21:08
tjaaltonsvn ftl21:10
jarekI must force myself to do this some day21:13
jarekcurrently I'm using windows on this old crap21:14
jcristaubjsnider: ld -lfoo looks for libfoo.so21:18
jcristaubjsnider: and produces a binary with a reference to libfoo.so.N21:18
jcristaubjsnider: so at runtime ld.so sees that reference and loads libfoo.so.N21:18
tjaaltonjarek: what card/chip do you have?21:21
bjsniderjcristau, yes, that i understand perfectly. what i don't understand is creating the libfoo.so.1 link to libfoo.so.N21:23
jcristaueh, what?21:24
jcristauthere's no .so.1 link21:24
bjsniderhttp://bazaar.launchpad.net/~albertomilone/nvidia-drivers-ubuntu/nvidia-current/annotate/head:/debian/nvidia-current.links.in21:25
bjsnideryou can see them being created all over the place there21:26
bjsniderand they were in the previous packaging scripts too21:26
jcristauoh. nvidia.21:26
jarekIt's unichrome pro, Fujitsu Amilo L7310W21:28
jcristaubjsnider: for libGL, its SONAME *is* libGL.so.1.  the others i have no idea.21:28
jarekI'm not sure chipset name, can be CN400 or PM88021:29
bjsniderjcristau, so perhaps this is some sort of bizarro nvidia quirk?21:29
tjaaltonor just a packging goof21:31
jcristaubjsnider: anything related to nvidia is a bizarro quirk as far as i'm concerned :)21:31
bjsniderthe libs in here are named like this: libnvidia-compiler.so.190.5321:32
bjsniderso i don't see why a .so link to that isn't good enough21:32
jcristaudid you check what the soname is?21:33
bjsniderthat is the soname isn't it?21:33
jcristau?21:33
jcristauhow should i know21:33
bjsniderit's called 190.53 so isn't that the soname?21:33
jcristauno21:33
bjsnideri see21:34
jcristauthe soname is in the elf header.  it may be the same as the file name, or it may be different21:35
bjsniderhow am i supposed to check that?21:36
jcristauobjdump -p21:37
bjsniderjarek, there's another driver called unichrome that might work as well. the developer is in here21:38
bjsniderespecially if your hardware is "old crap" as you put it21:38
jarektjaalton: I googled for chipset name, and it saying PN800, but system information for windows showing pci names CN400/PM88021:39
jarekbjsnider, my laptop isn't working like I expected a years ago, since then I tested livecd without succes21:44
jarekI can't do testing on working alerdy system21:45
bjsniderhave you ever tried the unichrome driver?21:46
bjsniderjcristau, all of these sonames are 1, so perhaps the so.1 link is necessary for that reason?21:46
jcristauyes21:46
jarekI really don't remember, but I'm using older driver then openchrome, can be via or unichrome21:48
bjsnideryou don't know what driver you're currently using?21:48
jarekcurrently my laptop is windows land21:49
bjsnideroh right21:49
bjsniderso it didn't work off the livecd21:50
jarekit's started with wrong resolution21:50
bjsniderlibv, which driver would be best for this guy's hardware?21:50
jarekI see  1/4 of screen21:50
bjsniderthat ain't good21:51
jarekIt's known bug21:52
jarekbut the cure is propably in current trunk on openchrome21:52
jarekI hope to test it on lucid prime time21:52
bjsniderluc might not be here at the present time21:53
BUGabundobu noute21:56
jarekbjsnider: If it's too late for lucid, I will wait for daily 10.10 builds, hope my laptop will run without problems then21:58
bjsniderjarek, stick around in here until luc is here and then discuss it with him22:00
jarekok, thanks22:00

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