User1: morning
User2: Howdie.
User1: still talking to danvet, before I really woke up this time, not a good idea :)
User1: but the alternatives are worse, heatwave here :/
User1: Anything i can work on that doesn't require much logical thought today?
User1: oh right, could look at vdpau blobs again :)
User3: oh duh, libglsl.so is merged into libdricore.so..
User1: :>
User3: hmm, debian hasn't installed it
User1: User3 oh hey we're again a intel version behind
User3: yup
User1: git merge debian-experimental seems to be enough
User1: I guess jcristau beat us this time :)
User4: haven't tested at all
User3: we can do that for you :)
User3: or the quantal test puppies can
User4: i wanted to remove /etc/modprobe.d/i915-kms.conf in this version
User4: since it's not needed post wheezy
User1: hm does that mean sync to debian again?
User3: nah the apport hook is the only dif
User3: f
User3: after that change
User3: but close
User4: i'm going to need some maintainer scripts love to get the conffile removed properly
User3: those are always icky..
User1: yeah
User4: it's written, just not tested yet :)
User1: blegh I need some work that's not dma-buf related for a change :)
User1: anything i could work on for a while?
User3: well..
User3: there's the crasher on precise due to synaptics upgrade in -updates
User3: so figuring out why going to 1.6.2 triggered it would be cool
User3: or is the server missing something
User1: likely server related sadly
User1: and i don't have the faintest clue what is differing between x1.12 and 1.11 in ubuntu
User1: User3 it's not a problem in quantal right?
User3: User1 some dupes of 956071 at least have been reported on quantal
User3: bug 956071
User5: Launchpad bug 956071 in xserver-xorg-input-synaptics (Ubuntu) "Xorg crashed with SIGSEGV in XIGetDeviceProperty()" [High,Confirmed] https://launchpad.net/bugs/956071
User3: there's also a similar bug on debian
User3: and upstream
User3: well, forwarded upstream by the same guy
User1: quantal added on 2012-07-18, did we already have the x1.12 stack then? *looks*
User3: there's one filed 7h ago
User1: aw looks that way, ok I'll take a look
User1: User3 I think I might have seen that bug when I was playing with valgrind :)
User3: oh good
User1: or at least some bug during synaptics probing, but it was a weird one and didn't make much sense, maybe it will show up again under more paranoid settings
User3: suspend/resume testing should reveal that before too long
User3: also, it can crash seconds after typing the password, which is kinda late in the resume cycle..
User1: yeah I get some weird erorr during a log output
User1: which didn't make sense
User1: I'll just increase the tracking that valgrind does
User3: the sigsafe logging patches should be in 1.13 though..
User3: if that's related
User1: valgrind worked fine without on x1.11
User3: k
User3: -synaptics was probably the old version too
User1: but I'll update quantal first :)
User6: tseliot, tjaalton, mlankhorst, User12 hey, what's the status on nvidia binary drivers on quantal then? did the driver update work?
User1: User6 from ubuntu-devel, it is updated to document it's not compatible, unless there has beeen an update since :)
User6: do we have an ETA on compatible driver?
 * mlankhorst doesn't know nvidia's plans
User3: no eta
User3: "next release"
User6: :-(
User1: but at least it's not fglrx
User7: User6 the update doesn't work therefore I simply made sure that the driver conflicts with the new X abi
User6: well, ati works fine so fglrx is less of an issue
User6: nouveau is suboptimal still though :-(
User1: sadly
User6: tseliot, ok, thanks
User1: maintainer has spent a lot of time turning every line of code upside down..
User1: hopefully we'll start seeing fixes again soon
User7: :)
User1: (there's even some lines of code that haven't changed \o/)
User3: single-threaded mesa build on top of a nfs share via wifi is.. surprisingly slow :)
User1: no what's surprisingly slow is apt-get install over nfs on a gigabet network with a ssd backing..
User1: gigabit*
User1: what you described is unsurprisingly slow :)
User3: hehe
User3: yeah
User3: preseeded netboot install over gigabit is like 15min here
User3: full desktop
User1: I just use debootstra plocally
User1: usually for apt-get updates in chroot too
User3: oh well, I know the build passes, now it's just finding the right files for dh_install
User1: brb
User1: User3 oh great.. same bug as another one I was hitting
User1: updatetouchstate overflows
User1: cnd: ^ seems to happen on quantal 1.13rc4 too
User3: User1 woo, thanks
User1: well I fear it could be a dup of the other synaptics bug then
User3: hmm libdricore is now versioned
User3: libdricore8.1.0.so.1.0.0
User1: great..
User3: probably no point in splitting it from libgl1-mesa-dri though
User1: true just leave it in :)
User3: wha.. the gallium dri's are huge, over 41MB apiece
User1: debug symbols enabled?
User1: User3 oh btw https://bugs.launchpad.net/oem-priority/+bug/956071/comments/59
User5: Launchpad bug 956071 in xserver-xorg-input-synaptics (Ubuntu) "Xorg crashed with SIGSEGV in XIGetDeviceProperty()" [High,Confirmed]
User1: the crasher backtrace i hadnt seen before
User3: ahh
User3: right, the binaries haven't been stripped yet, oops
User3: no libgallium.so then, the patch would need to be reworked
User8: Hi folks, could some one please advise as to against what this bug should be reported...http://pastebin.com/SRLnr5fB
User3: the kernel
User8: User3 thanks!
User3: although
User3: what does "get live session working" mean
User3: ?
User8: it means that the tester has to insert nomode to get it to run?
User8: In my distinctly amateur opinion I'd suspect nvidia-graphics-drivers since it could well be fallout from the new X stack.
User3: no
User3: you don't have that on a live-cd
User9: User3 --with-llvm-shared-libs saves a bunch of space but needs the patch on https://bugs.freedesktop.org/show_bug.cgi?id=52167 still
User5: Freedesktop bug 52167 in Mesa core "llvmpipe test programs link fails when ld --as-needed option is used" [Normal,New]
User3: User9 i'll whine again after seeing what they look like after dh_strip :)
User8: okies, so it is a kernel regression?
User3: User8 not necessarily
User3: is there a boot splash? does X start but hang later?
User8: I'm surmising from the tester that he needs to alter the boot sequence to get X to actually run. Once he knows where to file the bug, he will be able to give more information. He's an experienced tester, just unsure as to what to report this one against.
User3: ubuntu-bug xorg
User8: thanks.
User3: that's a good place to start..
User8: it can always be re-assigned later.
 * mlankhorst recovers from brain thermal cutout
User1: User10 you added 217_revert_bgnonevisitwindow.patch, is it still needed?
User1: similar to some other patches, for example some old workarounds in xorg-server should probably be upstreamed or dropped entirely..
User3: yes, there was a task about it but it got marked as done, though I think we should be more aggressive about them..
User1: agreed
User1: i dropped a 0->null change now, since it really doesn't add anything to keep it
User1: User12 ping?
User3: head hurts trying to fix 116_use_shared_galliumcore.diff
User3: got to give up for now
User1: next person to make a cd can fix it? :p
User3: User1 hehe, exactly. or maybe RAOF_ :)
User1: brr, fighting ttm is no fun :(
User1: screw it, most common case will be re-using local reservation object anyhow *does ugly hack*
User3: btw, virtualbox is broken with the new server :)
User3: reportedly
User1: sigh :s
User4: when is vbox not broken
User3: whemn it's not installed i guess..
User10: mlankhorst, 217_revert_bgnonevisitwindow.patch is not actually enabled, it was dropped a year ago because it was included in 1.11.0.  But looks like raof left the patch itself in place for some reason
User1: hm suppose we ought to get rid of all the patches not in series to clean up confusion then :)
User10: definitely
 * mlankhorst just created a very scary patch
User1: http://cgit.freedesktop.org/~mlankhorst/linux/log/?h=v10-wip makes reservations sort of global, scared to test if it boots..
User3: wth, "configure: error: --with-driver=dri is deprecated"
User3: built just fine earlier today
User3: oh, with --enable-osmesa it fails that way.. nice
User3: if it's forced
User3: ahah, --enable-dri
User1: User3 yay obsolete packages gone :)
User3: User1 they got removed the same time when the stack got copied
User3: oh bloody osmesa
User3: doesn't find glapi/glapitable.h
User3: -I$(top_srcdir)/src/mapi \
User3: probably should be top_builddir
User3: no
User3: well, needs both :)
User3: 726f534bbb3f is similar for glx
User3: ffs, "libdricore*" is not enough to get all the links to be copied to the package dir
User11: howdy folks.  over in #ubuntu-devel i've been chatting with tjaalton and bryceh about today's big problems with 12.10 in a vmware fusion 4.1 host.  is there a vmware dev here who would like to help me debug the problem?
User11: bug 1039157
User5: Launchpad bug 1039157 in xorg (Ubuntu) "X problems in Fusion guest" [Undecided,New] https://launchpad.net/bugs/1039157
User10: pst Prf_Jakob ^
User3: User13 ^ vmware-tools needs some love for newer kernels
User3: so that it would build :)
User11: User13 hi.  i'm using 12.10 in fusion 4.1.3 (730298).  i know i'm bleeding edge but perhaps i can help test vmware-tools for 12.10?
User3: right, helps if you copy from the right directory, *sigh*
User3: at long last.. mesa debs created, without libgallium.so though
User3: User12 updated mesa git to build, if libgallium.so is commented out from libgl1-mesa-dri.install.linux.in.. if you have time to look at the patch and what it needs to make it work again, that would be great
User3: I started but after the trivial bits it was unclear what was needed, since some bits have been automakeified
User3: like libdricore build
User12: Yay.
User3: "have fun" :)
User9: "thank you so much" :)
User3: if you're up for it that is ;)
User13: User3 ugh seems like a lot of things are broken in 12.10
User13: User3 have you guys forgotten to enable the vmwgfx kernel module?
User13: User11 still around
User13: ?
User11: User13 yep!
User13: lsmod | grep vmwgfx ?
User13: yeah its using the old driver for some reason.
User11: @resist[~:1001]% lsmod | grep vmwgfx
User11: @resist[~:1002]%
User11:
User13: I'm guessing its because vmwgfx isn't loaded.
User11: User13 yeah, i've tried installing both open-vm-tools and building vmware-tools from the "cd"
User13: We don't ship vmwgfx kernel driver or X drivers in tools for newer distros.
User13: cat /boot/config-`uname -r` | grep VMWGFX
User11: CONFIG_DRM_VMWGFX=m
User11:
User13: okay
User13: modprobe vmwgfx
User13: sudo service lightdm restart
User13: should sudo modprobe as well.
ubuntu-x
Ubuntu IRC