/srv/irclogs.ubuntu.com/2010/11/25/#ubuntu-x.txt

bryceh# Classic DRI and Gallium DRI are mixed up together here00:57
bryceh# Remove the whole tree to avoid false-positives in --list-missing, and00:57
bryceh# install the right files manually.00:57
brycehrm -r debian/tmp/dri/usr/lib/dri00:57
brycehdh_install -s --list-missing00:57
brycehcp: cannot stat `debian/tmp/dri/usr/lib/egl/st_GLESv1_CM.so': No such file or directory00:57
brycehdh_install: cp -a debian/tmp/dri/usr/lib/egl/st_GLESv1_CM.so debian/libgles1-mesa/usr/lib/egl/ returned exit code 100:57
brycehmake: *** [binary-arch] Error 200:57
brycehthat's after disabling gles overlay and openvg, which krh recommended for mesa to be compatible with wayland00:57
brycehRAOF_, would it be wrong of me to drop GLESv1* from mesa's .install's?00:58
bryceh( http://launchpadlibrarian.net/59576070/buildlog_ubuntu-maverick-i386.mesa_7.10.0%2Bgit20101118.3dcc3153-0ubuntu1~bryce6_FAILEDTOBUILD.txt.gz )00:58
brycehI'm going to comment out  dri/usr/lib/egl/st_GLESv1_CM.so usr/lib/egl  in  libgles1-mesa.install00:59
brycehRAOF_, btw, I found that even though the wayland server started working after our changes last night, the clients now fail to launch01:01
bryceh 01:02
bryceherrors look like:01:02
brycehMesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable01:02
brycehInternal error:   Could not resolve keysym SunProps01:02
brycehInternal error:   Could not resolve keysym SunFront01:02
brycehInternal error:   Could not resolve keysym SunOpen01:02
brycehfailed to create cairo drm surface01:02
brycehlibEGL debug: Display 0x87f89f8 is destroyed with resources01:02
brycehdisconnect from client 0x993db0801:02
bryceh 01:02
brycehI'm wondering about the libtxc_dxtn.so bit - that looks odd01:02
brycehhowever it's the keysym errors that directly precede the termination so I wonder if something's wrong on the input side of things01:03
brycehRAOF_, can you confirm that we definitely do want --enable-glx-tls ?01:03
brycehIt looks like we have that on in xorg-server so presumably we want it in mesa too01:04
RAOF_I think we do want --enable-glx-tls, yes.01:12
Sarvatt...this is just going in the PPA right? you're building cairo-drm? yeah we want --enable-glx-tls, no disabling gles and openvg isn't an option in the archive01:12
RAOF_Because ARM at least wants GL|ES & OpenVG, and we probably don't want to drop those libraries anyway.01:14
brycehSarvatt, yeah just the PPA for now01:15
brycehI'm not building cairo-drm, that's not needed anymore afaik01:15
brycehinstead doing cairo-gl01:15
=== RAOF_ is now known as RAOF
brycehhm ok01:15
brycehwonder why krh suggested disabling them?01:16
RAOFI don't know.  Except that it'll probably take less build time.01:17
RAOFI don't see why they would interfere with EGL/GL.01:17
bryceh<bryceh> krh, will --enable-openvg cause troubles if it is on?01:20
bryceh<krh> bryceh: it wont wroth with --disable-gallium-egl01:20
bryceh<krh> s/wroth/work01:20
bryceh<bnf> there is --enable-openvg01:21
bryceh<Darxus> Hehe.01:21
bryceh<krh> yeah, but I'm pretty sure that require gallium egl01:21
Sarvattbecause he's only made things work on intel with what fedora uses and it gets complicated once you start enabling gallium stuff? :)01:21
RAOFRight.  But didn't our little expedition into the wonderful world of libudev fix the egl_dri2 problem anyway?01:21
brycehRAOF, yes-ish01:22
brycehit fixed it for the server, which now launches properly01:22
brycehbut the clients don't work01:22
Sarvattwe have things build-depping on our mesa gles/vg dev packages, I think most of it is arm/linaro specific though outside of mesa-utils01:22
brycehbryce@lynmouth:~/src/Wayland/wayland$ wsmoke 01:23
brycehlibEGL warning: failed to create DRM screen01:23
brycehMesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable01:23
brycehInternal error:   Could not resolve keysym SunProps01:23
brycehInternal error:   Could not resolve keysym SunFront01:23
brycehInternal error:   Could not resolve keysym SunOpen01:23
brycehso I'm poking around for what else needs fixed01:23
Sarvattattach gdb and get a backtrace?01:23
RAOFDoes it work if you run as root?01:23
Sarvattmight just be harmless error spam and its stuck doing something else01:24
RAOFIt could be a simple failure to authenticate the DRM connection.01:24
brycehRAOF, nope01:24
RAOFSarvatt: I wouldn't think so: “libEGL warning: failed to create DRM screen” looks likely to be fatal :)01:24
Sarvattyeah somehow parsed that out and meant the keysym errors :)01:25
brycehgdb doesn't help as it's not segfaulting01:25
RAOFStrace might?01:25
brycehstrace:  http://pastebin.com/f4qA4nKg01:26
RAOFAnd can EGL be a little more verbose? :)01:26
brycehyes01:26
Sarvattif you attach it should stop the execution until you cont, you can just bt full after attaching?01:26
brycehwait no that's all EGL gives01:26
Sarvattyeah theres tons of egl debug env vars01:26
brycehhere's the full run log, showing both server output and client:  http://pastebin.ubuntu.com/536116/01:27
SarvattEGL_LOG_LEVEL=debug01:27
brycehthis is with:01:27
brycehexport MESA_DEBUG=101:27
brycehexport EGL_LOG_LEVEL=debug eglinfo01:27
Sarvattbryceh: do you have X open?01:29
Sarvattdid you sudo service gdm stop first I mean?01:29
RAOFHm.  Looks like it's correctly opening egl_dri2, which is correctly opening i965_dri01:29
brycehSarvatt, I have X open01:29
brycehI might have stopped gdm and restarted once since last reboot, I don't remember01:30
Sarvattalmost positive you can't have X running when you start it?01:30
brycehuntrue; I've had that working fine01:30
brycehin fact I've not yet gotten it running outside X01:31
brycehalthough I've not yet tried very hard01:31
* bryceh tries01:31
brycehwhoa that's weird01:32
brycehscreen went tie-died and then wiped to black01:32
RAOFI suspect the cairo-drm message is the problem01:32
brycehlibEGL debug: the best driver is DRI2 (score 100)01:33
brycehMesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable01:33
brycehfailed to add socket: Address already in use01:33
brycehlibEGL debug: Display 0x88999c8 is destroyed with resources01:33
brycehsame thing whether running as user or root01:33
RAOFFailed to add socket?01:33
Sarvattare you in the video group?01:34
brycehvideo:x:44:bryce01:34
brycehRAOF, yeah haven't seen that error before01:35
Sarvattyou got that error in a paste earlier01:35
Sarvatthttp://pastebin.ubuntu.com/536116/01:35
RAOFSo, I don't particularly think this is a mesa problem; it's loading egl_dri2 properly which is then loading the correct dri driver.01:36
brycehoh wait, socket error just meant I had a stray wayland server process01:36
RAOFAnd it doesn't work, even without a stray wayland? :)01:37
Sarvatttried EGL_PLATFORM=drm EGL_DRIVER=egl_dri2 ./wstart with no X running?01:40
Sarvattwell your strace says libEGL warning: failed to create DRM screen is from /usr/lib/egl/pipe_i915.so not existing01:41
RAOFSarvatt: Yeah, but if you read the strace it then goes on to load egl_dri2 and i965_dri.01:41
brycehok, without a stray wayland it does launch the server, but still no clients01:41
brycehactually fairly cool, I can set a background and get a movable mouse cursor01:41
brycehSarvatt, yeah those env vars don't seem to make a difference01:43
brycehwhat generates pipe_i915?01:43
Sarvattare your binaries setuid?01:43
Sarvatti915g01:44
brycehit sounded like from krh that the pipe stuff is used only in certain situations unrelated to this01:44
brycehI haven't fiddled with that at all, should I?01:44
Sarvattyeah just saying you can ignore that warning it looks like01:44
RAOFYeah.  The pipe_* drivers are the gallium hardware drivers; they'd be used if egl_gallium was happening.01:45
brycehRAOF, where did you see the cairo-drm bit?01:45
brycehafaik that shouldn't make an appearance anywhere01:45
RAOFwrite(2, "failed to create cairo drm surfa"..., 35failed to create cairo drm surface01:45
Sarvatt<bryceh> failed to create cairo drm surface01:45
brycehoh right01:46
RAOFYou could play with i915g; I understand that it's not entirely broken, like i965g is :)01:46
brycehthat's an error message from the client that it gets after trying to create a surface using cairo01:46
brycehhrm01:46
brycehok if you guys are out of clue on this too, I'll just shelve it until next week01:47
brycehhappy to try more idea though if you got 'em01:47
RAOFI think the interesting question is why cairo's failing to create a drm surface.01:48
Sarvattyeah looks like the problems in the way cairo is built to me even though cairo-drm isn't enabled01:49
brycehhm ok01:53
brycehalright, lastly, gonna try newer wayland in case recent git changes fixed something02:00
brycehWHOA02:00
brycehthat did it02:00
brycehsweetness02:00
RAOFHeh02:00
brycehshoulda tried that earlier!02:00
Sarvatthttp://cgit.freedesktop.org/wayland/commit/?id=32ff69017ab003911b754982772d0644b1cd23d402:01
RAOFSo that sounds like we can use the archive mesa configuration and still have everything work.02:01
Sarvatthah was my  next idea02:01
Sarvatt(are you *sure* the udev rules are getting used?)02:01
brycehfor the record I still see these warnings when firing up the clients:  http://pastebin.ubuntu.com/536127/02:02
brycehSarvatt, I express certainty on nothing02:02
brycehoh02:02
brycehon that, I had been forcing install of the udev rules in debian/rules anyway02:03
brycehI can probably clean some of that up now02:03
RAOFYeah; the dxtn library warning is totally harmless.  I guess unless a wayland client wants to upload DXT-compressed textures :)02:04
brycehwould be nice to suppress that02:04
brycehI've a pet peeve about harmless-but-technobabbly warnings02:05
Sarvattyou could install it :)02:05
brycehactually not sure that I can02:05
RAOFYou know what would be a good fix?  Show that warning when something tries to fiddle with a DXT texture!02:06
Sarvattyeah you can I just did on a new install a few days ago02:06
brycehbryce@blumonc:~/src/Wayland/wayland/wayland-0.1~git20101124.32ff6901/debian$ apt-cache search dxtn02:06
brycehbryce@blumonc:~/src/Wayland/wayland/wayland-0.1~git20101124.32ff6901/debian$ 02:06
brycehis it a natty package?02:06
Sarvattits patent encumbered, have to do it manually02:06
brycehoh, well I don't count that ;-)02:06
brycehwell, I'd say either quell the warning or add the installation directions to it02:07
brycehanyway, task for another day02:07
brycehSarvatt, where do you get the package?02:07
Sarvattdo you have LIBGL_DEBUG=verbose exported maybe?02:08
Sarvattdigging around for it now, it was on people.freedesktop.org that got nuked awhile back and had to grab it off bugzilla somewhere02:10
brycehno, but I do have MESA_DEBUG=1 exported02:10
Sarvattoh thats why ya got it i bet02:10
brycehexport MESA_DEBUG=102:10
brycehexport EGL_DRIVER=egl_dri202:10
brycehexport EGL_PLATFORM=drm x1102:10
brycehexport EGL_LOG_LEVEL=debug eglinfo02:10
Sarvattexport EGL_LOG_LEVEL=debug eglinfo ?02:11
brycehhmm commenting out both MESA_DEBUG and EGL_LOG_LEVEL but still prints it02:12
Sarvatthttp://debian-multimedia.org/pool/main/libt/libtxc-dxtn/libtxc-dxtn.php02:13
Sarvattdebs!02:13
brycehok thanks02:14
* Sarvatt wonders if he can get away uploading that to xorg-edgers :)02:14
brycehif I get around to it I'll isolate where the warning comes from and add that link, if I don't just quell it outright02:14
RAOFSarvatt: It's free software, right?02:14
brycehis debian-multimedia.org part of Debian?02:14
Sarvattheavily patent encumbered and not suitable for debian :)02:15
Sarvattits debian's medibuntu02:15
Sarvatthttp://dri.freedesktop.org/wiki/S3TC02:16
ScottKSarvatt: only with lower quality packaging.02:18
Sarvattlower quality?02:19
ScottKThe debian-multimedia packaging quality is not well thought of in Debian.02:19
* Sarvatt can't even count how many times he's had broken ffmpeg libs screw up his system from medibuntu02:19
brycehgotcha02:20
ScottKAFAIK, most of the people working on medibuntu are actual Ubuntu devs so I think it's similar to Ubuntu package quality wise02:20
ScottKIt's been quite some time since I actually paid attention to medibuntu though.02:20
brycehokie dokie guys, get your wayland on:  https://launchpad.net/~xorg-edgers/+archive/wayland02:22
brycehIN THEORY, you should be able to just add the ppa, update, install wayland, and then run wayland as described02:22
brycehif not, it's something I should fix02:23
Sarvattppa-purge no workie in natty, but at least there aren't many packages involved :)02:23
brycehno?  why not?02:23
brycehanyway, this is only tested on maverick so far02:23
Sarvattsources are stored compressed now, haven't had a chance to make ppa-purge work with that02:24
Sarvatt/var/lib/apt/lists/ppa.launchpad.net_xorg-edgers_wayland_ubuntu_dists_natty_main_binary-i386_Packages.gz02:25
brycehah02:26
bjsniderthe medibuntu ffmpeg is almost exactly the same as the ubuntu ffmpeg. hard to believe it could have broken anything02:35
tjaaltonbryceh: tried the ppa, but looks like wayland needs to depend on libgles2-mesa07:52
tjaaltonsince it can't find libGLESv2.so.2 without it07:53
RAOFAnd it's looking for GLESv2?  I thought it was strictly a desktop GL affair.07:53
vishRAOF: hi, alacarte upstream is unmaintained.. spoke to Amaranth earlier, he said we can just upload the patch in natty.. re: Bug 39569207:54
tjaaltonah07:54
ubot4`Launchpad bug 395692 in alacarte (Ubuntu) (and 2 other projects) "Drag-and-Drop behavior in the menu editor is inconsistent and confusing (affects: 3) (heat: 28)" [Low,Triaged] https://launchpad.net/bugs/39569207:54
RAOFAlso, I guess that's a bug in mesa.07:54
tjaaltonRAOF: yeah I'm trying to run it with the hints from the ppa07:54
vishs/natty/ubuntu07:54
tjaaltonnow the compositor runs, but how do I fire up the clients?-)07:54
RAOFvish: Yeah, I guessed as much.  I was going to go sponsor hunting this evening.07:55
vishRAOF: neat! thx :)07:55
tjaaltonis there a way to launch wayland without X08:04
tjaalton?08:04
brycehtjaalton, there may be a /usr/bin/wstart script08:04
tjaaltonbryceh: yeah, it just says "no drm device found"08:05
brycehtjaalton, and there are clients named wayland-* you can run if you have the server up08:05
tjaaltonso maybe something else is wrong08:05
brycehyeah likely08:05
tjaaltonbryceh: also, it didn't pull libxkbcommon08:05
brycehok08:05
* bryceh makes notes08:05
tjaaltonthe ppa description has old client names, btw (wterminal..)08:05
brycehoh thanks, yeah just redid the naming today08:06
brycehtjaalton, updated08:08
* bryceh -> bed08:08
tjaaltonyeah, night08:08
=== JanC_ is now known as JanC
=== yofel_ is now known as yofel
=== |Alexia_Death| is now known as Alexia_Death
RAOFWell, launchpad indicates that mesa doesn't appear to be on fire.  That's nice :)21:50
brycehRAOF, should it?22:05
RAOFNo, of course not :)22:06
brycehRAOF, oh btw I wanted to ask, you mentioned you'd pulled some of the changes for wayland-enabled mesa into the archive... 22:06
brycehRAOF, which changes exactly did you pull, and was that into the main archive or the xorg-edgers archive?22:06
RAOFI pulled the libudev-dev build-dep into the main archive packages.22:07
RAOFSo egl_dri2 should actually work. :)22:07
RAOFThe reasons why Mesa might have caught fire are the switch to r300g by default and libdricore shared linking.22:08
brycehah gotcha22:09
brycehI've been watching all incoming natty bug reports fairly carefully the last couple weeks22:09
brycehthe sense I get is that very few people are running natty at the moment, cause there's hardly any bug reports coming in22:09
brycehhttp://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg22:10
brycehthere's 1 natty bug against -evdev and one against nvidia-17322:10
RAOFAh.  Mesa hasn't caught fire on people's systems because it's failed to build on the buildds.  Thanks, crappy mesa build system!22:39

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