[08:39] <tjaalton> wgrant: ok, I'll do that
[09:34]  * Ng boggles, this morning my scrollwheel emulation came back when i re-ran the xinput stuff after suspend
[09:34] <Ng> I tested multiple suspend cycles and it was definitely not doing that!
[10:12] <seb128> hey there
 seb128: my mouse wheel doesn't work anymore... is it a known thing? I cannot find anything relevant on launchpad
[10:12] <seb128> is there some known issue on the topic since the xinput changes?
[10:13] <tjaalton> seb128: shouldn't be
[10:13] <seb128> hum ok
[10:15] <wgrant> xinput shouldn't be doing much mouse wheel stuff...
[10:18] <wgrant> tjaalton: How would you feel about applying a syndaemon patch of mine to make it work without SHMConfig? I've had positive reports from others, and it will still work with SHMConfig if properties aren't available or -S is given.
[10:20] <tjaalton> wgrant: sure
[10:20]  * wgrant locates a diff.
[10:20] <wgrant> Is out -synaptics in git somewhere?
[10:20] <wgrant> s/out/our/
[10:21] <tjaalton> yes, git.debian.org
[10:21] <wgrant> I also think we need to revert that two-finger-scrolling disentanglement patch, as it certainly doesn't click as easily as it used to.
[10:21] <tjaalton> ubuntu-branch
[10:21] <wgrant> Hmm, couldn't see it there.
[10:21] <tjaalton> hmm, I'll check
[10:21] <wgrant> The only branch I could see was debian-unstable... or is it in another location?
[10:21] <tjaalton> it is there for sure
[10:22] <wgrant> Not branch in the normal git sense?
[10:22] <tjaalton> you cloned it?
[10:22] <tjaalton> origin/ubuntu
[10:22] <jcristau> wgrant: 'git branch -r' lists remote branches
[10:22]  * tjaalton is hung over..
[10:22] <wgrant> Haha.
[10:23] <tjaalton> not the best day to work
[10:23] <tjaalton> :P
[10:23] <wgrant> Probably not, no.
[10:24] <wgrant> jcristau: On which URL should I be trying that?
[10:24]  * wgrant has very limited git skills.
[10:24] <jcristau> in your local repo
[10:25] <wgrant> Oh.
[10:25] <wgrant> I see.
[10:25] <wgrant> So clone only grabbed the default branch?
[10:25] <wgrant> Right, there we go.
[10:26] <jcristau> clone grabbed all branches, but only created a local branch for the default
[10:27] <jcristau> 'git checkout -b ubuntu origin/ubuntu' to create a local ubuntu branch
[10:27] <wgrant> That worked.
[10:27] <wgrant> Thanks.
[10:27] <wgrant> I often wonder if some features of git were designed to be completely counter-intuitive.
[10:54] <wgrant> Am I meant to use git-buildpackage to build it, or do you X people use some other setup?
[10:55] <tjaalton> dpkg-buildpackage works
[10:55] <wgrant> Won't that leave a .git?
[10:56] <jcristau> not with -i
[10:56] <wgrant> True.
[10:56] <elmargol> is it normal that the nvidia driver from jockey works. and the driver from nvidia.com has huge issues?
[10:57] <elmargol> the kwin effects are all totally broken:(
[10:58] <elmargol> I guess there are some special patches ubuntu is using?
[11:22] <tseliot> elmargol: define what you mean by "works"
[11:22] <tseliot> and specify the version of the driver you're using, please
[11:24] <elmargol> tseliot: 177.80 from nvidia.com does not work.
[11:24] <elmargol> 177.80 from ubuntu does work
[11:24] <elmargol> If I enable Desktop effects. The window manager does not work anymore. (I can not switch properly between windows)
[11:25] <elmargol> Show desktop etc. does not work too
[11:25] <tseliot> elmargol: please don't use the driver from nvidia.com or you might break some symlinks
[11:25] <elmargol> Some problem using 177:76
[11:25] <elmargol> tseliot: well If I use the ubuntu drivers I get a hard freeze
[11:26] <elmargol> thats the bug I'm complaining for weeks now
[11:26] <tseliot> elmargol: it's the same driver
[11:27] <wgrant> tjaalton: Any changes that you want for -synaptics?
[11:27] <tseliot> elmargol: therefore I think that you're not getting the hard freeze with the one from nvidia.com simply because that driver is not loaded
[11:27] <elmargol> what else to do.. noone from nvidia/ubuntu cares. experimenting is the only thing left to do i think
[11:28] <tseliot> elmargol: what's the bug report again?
[11:28] <elmargol> bug #270617
[11:30] <elmargol> next think I try is reverting to a old kernel. if this does not help :( i have to downgrade to hardy
[11:32] <tseliot> elmargol: the log doesn't show the problem. Maybe it's a bug in the nvidia driver that affects kernel 2.6.27 and it's triggered by some module which is specific to your hardware
[11:33] <tseliot> nothing that we can fix
[11:33] <tseliot> did you try updating the BIOS?
[11:33] <elmargol> This is a dell inspiron 9400 there have to be 1000 users out there
[11:34] <elmargol> tseliot: it worked just fine using hardy and vista
[11:35] <tseliot> elmargol: yes, you mentioned that
[11:36] <elmargol> i check if there is a newver bios
[11:43] <tseliot> elmargol: if that doesn't work you can try to underclock your card: http://www.phoronix.com/scan.php?page=article&item=197&num=1
[11:44] <tjaalton> wgrant: nope
[11:45] <wgrant> tjaalton: OK, see http://people.ubuntuwire.com/~fujitsu/git/xserver-xorg-input-synaptics
[11:48] <wgrant> Hmm, there's a bug reference I should have in there.
[11:48] <tjaalton> wgrant: what should I be looking at?-)
[11:48] <wgrant> tjaalton: The ubuntu branch there. It has some changes.
[11:57] <tjaalton> wgrant: ok, pulled and merged
[11:58] <wgrant> tjaalton: Thanks.
[12:05] <jcristau> eww. somebody made shmconfig default to true?
[12:05] <tjaalton> jcristau: yeah, for some model
[12:05] <wgrant> jcristau: Yes...
[12:05] <wgrant> In the fdi file.
[12:06] <wgrant> I'm considering reverting all of the changes there except the edges and maxtapmove, but I presume there's a reason for them.
[12:06] <tjaalton> hm, should I be able to build the source package even though I'm not the one who touched the changelog?
[12:06] <wgrant> tjaalton: Yes, with -kyourkeyid
[12:06] <tjaalton> wgrant: cool
[12:07] <tjaalton> that was.. obvious
[12:07] <jcristau> wgrant: yeah, i don't think the fdi should set any options, really. if the defaults are wrong, that should be fixed in the driver itself imo
[12:07] <jcristau> but, shmconfig on by default is.. weird.
[12:07] <tjaalton> I think those were dropped upstream
[12:07] <wgrant> jcristau: They are largely now, but this particular model had strange dimensions. The driver autodetects it now.
[12:08] <wgrant> They were.
[12:08] <jcristau> ok. cool.
[12:09] <wgrant> tjaalton: Did you mean to leave the xinput, -synaptics and -evdev tasks of the property API update bug open?
[12:11] <wgrant> tjaalton: Thanks.
[12:13] <wgrant> jcristau: Did you end up looking into that GetDeviceProperty issue any further?
[12:13] <jcristau> wgrant: no
[12:15] <wgrant> OK.
[12:20] <tjaalton> wgrant: nope, will close now
[12:23] <wgrant> tjaalton: Great.
[13:04] <elmargol> ok have a new bios version now
[13:04] <elmargol> lets see if this helps
[13:12] <elmargol> nothing about this in the bios changelog...
[13:29] <tseliot> elmargol: of course you won't find anything relevant in the changelog
[13:31] <elmargol> 30 min uptime now
[13:31] <elmargol> while true; do kate&kate&kate&kate&kate&kate&kate&kate&sleep 5;killall kate; done
[13:31] <elmargol> :D
[13:33] <elmargol> stresstest
[13:36] <tseliot> elmargol: if the problem is solved, please add the solution to the bug report
[13:37] <elmargol> tseliot: i crashed after 2 hours once :/
[13:37] <elmargol> I have to try this 1-2 days to be sure
[13:37] <tseliot> elmargol: yes, of course
[13:40] <Ng> tjaalton: http://picasaweb.google.co.uk/cmsjtenshu/Misc#5256616902573945746 - ever seen something like that on boot?
[13:40] <tjaalton> Ng: I believe so, yes
[13:41] <elmargol> yes thats wenn your nvidia card is broken
[13:41] <elmargol> at least my was gone after this :(
[13:41] <tjaalton> the X300 has intel gfx
[13:41] <elmargol> no idea then
[13:41] <Ng> I don't even think it's X that's doing it (I just asked tjaalton because his laptop has similar guts to mine)
[13:44] <tjaalton> heh, just got that screen
[13:44] <Ng> it seems fairly early in the boot to me
[13:44] <tjaalton> I wonder if it's the kernel crashing
[13:45] <Ng> I've had it once or twice when booting without usplash and I didn't see an oops on the console :/
[14:00] <tseliot> tjaalton: did you apply the patches which are mentioned here? https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/146859
[14:03] <tjaalton> nope
[14:05] <tseliot> tjaalton: too bad. Those patches should get around the current limitations of the intel driver
[14:05] <tseliot> for some models
[14:11] <elmargol> ok crashed again
[14:27] <tseliot> elmargol: if it has to do with overheating then you might try what I suggested ^^
[14:40] <elmargol> tseliot, I can play an hour quake4 on this machine (vista) and have no issues
[14:41] <tseliot> elmargol: ok but you're using a different kernel and a different driver
[14:54] <Ng> while I'm throwing problems around all over the place, Compose doesn't seem to be working since I upgraded to Intrepid
[14:54] <Ng> I don't use it very often, so I can't say exactly when it broke
[14:55] <Ng> (I have the gnome keyboard capplet set to make Alt-GR a compose key)
[14:57] <jcristau> what keysym does xev report when you press that key?
[14:58] <Ng>     state 0x0, keycode 108 (keysym 0xff20, Multi_key), same_screen YES,
[14:59] <jcristau> so that part works
[14:59] <superm1> Ng, i've been seeing that a lot 
[14:59] <superm1> Ng, on a variety of Dell boxes.  it only happens on intrepid usplash 
[15:00] <Ng> superm1: I get it on a seemingly random basis with or without usplash
[15:00] <superm1> Ng, have you caught a kernel trace then without the usplash?
[15:00] <Ng> superm1: no, there doesn't seem to be one :/
[15:01] <superm1> Ng, well when it freezes up like that though, you would think you would have one available :(
[15:01] <Ng> superm1: unless it hangs so deep inside the kernel that it can't trigger the bits that write an oops
[15:01] <Ng> also even if it did, the display corruption would make it impossible to read
[15:01] <superm1> Ng, does your thinkpad have a serial port then perhaps?
[15:02] <superm1> all of my dell boxes exhibiting it are serial free
[15:02] <Ng> superm1: nope :/
[15:02] <Ng> I have vga and ethernet and nothing else ;)
[15:02] <superm1> Ng, have you brought this to the attention of the kernel team yet?
[15:02] <Ng> yeah
[15:02] <superm1> what'd they say?
[15:02] <Ng> that they'd like me to try and get more information
[15:02] <Ng> I'm going to disable usplash tonight and do a few boot loops to trigger it and hopefully be able to tell from the timing, where it happens
[15:03] <Ng> I filed bug 282700 but I suspect it may end up being a duplicate of bug 263782
[15:03] <superm1> Ng, I didn't realize it happened without usplash ever, so I'll be glad to set up a reboot loop today too then on at least one of the boxes that exhibited the behavior
[15:04] <Ng> that would be handy :)
[15:05] <seb128> I've a similar crash on boot often too
[15:06] <Ng> seb128: what kinda hardware?
[15:06] <Ng> mine is all-intel
[15:06] <seb128> dell D630
[15:06] <seb128> which is basically all intel too
[15:09] <superm1> hum come to think of it, the other platforms i've seen this, I think they were all intel, but i'd have to double check one of them
[15:10] <superm1> Ng, http://picasaweb.google.co.uk/cmsjtenshu/Misc#5256006922907903138 mmm btw :)
[15:11] <Ng> I'm on a weird baking trip at the moment ;D
[15:29] <tseliot> superm1: I'm dealing with the bug about nvidia-xconfig and nvidia-glx-173. Do you think it would be ok if I added python-xkit to "Recommends" of nvidia-glx-173?
[15:30] <superm1> tseliot, I would think it should be depends
[15:30] <tseliot> and do I need a FFE for this?
[15:30] <superm1> tseliot, since you can't use nvidia-xconfig without it
[15:30] <tseliot> ok
[15:31] <tseliot> FFE or not?
[15:31] <superm1> it wouldn't hurt just to be safe.
[15:31] <superm1> it is indeed a new feature
[15:31] <superm1> i'd attach the changes to one of the existing bugs talking about the issues
[15:32] <superm1> and subscribe ubuntu-release to that
[15:33] <tseliot> ok, thanks
[16:17] <superm1> Ng, ah I have reproduced it on a d630 as well now without usplash turned on.
[16:17] <Ng> superm1: and you get a garbled mess with the characters flickering?
[16:18] <superm1> Ng, yeah
[16:18] <Ng> superm1: out of interest, did the machine spontaneously reboot/powercycle after a few seconds?
[16:18] <superm1> Ng, hard drive light flickering when it happens, nothing useful in syslog post reboot.  
[16:19] <superm1> Ng, no, I did that myself after a few seconds though
[16:19] <Ng> I was trying to take a picture and mine power cycled itself
[16:19] <superm1> I don't know a picture would have been that helpful, couldn't make much sense of everything on the screen
[16:21] <Ng> yeah :/
[16:21] <Ng> wish I had a video camera, but I think I'm going to have to try and guess what it is from the timings
[16:24] <superm1> I would have thought it was S90console-scren.kbd.sh, but that's a little too late in the boot process.  this happens far earlier
[16:24] <Ng> yeah
[16:24] <Ng> oh that's still in rcS.d
[16:25] <Ng> superm1: hmm, so one clue would be if it's before or after the font changes
[16:25] <superm1> perhaps settings the console font itself then.  you tried removing console-setup from your boot and see if it goes away?
[16:28] <Ng> not yet, but I suspect that is a prime candidate
[18:11] <Ng> superm1: could you maybe confirm https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/282700 and add your hardware details?
[18:12] <Ng> I think it's pretty clear we're talking about the same thing and that others are seeing it too
[18:14] <tormod> hi, I am trying to build intel in a PPA, but it looks for /usr/lib/libdrm_intel.so - what gives?
[18:14] <jcristau> tormod: you have libdrm from git?
[18:15] <tormod> jcristau: not really, it's from git20080926
[18:15] <jcristau> libdrm_intel was probably introduced later than that
[18:16] <tormod> is there a way to easily disable it? I need to check an upstream 2D fix.
[18:16] <jcristau> no
[18:16] <jcristau> hmm the change was made on 20080910
[18:17] <tormod> I see in the libdrm build log it was built...
[18:18] <jcristau> maybe it was built and then not added to the package :)
[18:23] <tormod> maybe the file is there after all, the build fails with:
[18:23] <tormod> dpkg-shlibdeps: failure: no dependency information found for /usr/lib/libdrm_intel.so.1
[18:24] <jcristau> missing shlibs file
[18:25] <tormod> what is an shlibs file? what would the name be?
[18:26] <jcristau> also i think libdrm_intel should be in its own package, so i (or chris) will update drm-snapshot packaging soonish
[18:29] <tormod> should the shlibs file be in the libdrm-dev package?
[18:29] <jcristau> no
[18:29] <jcristau> it's part of the metadata of the package containing the lib
[18:30] <tormod> metadata like in /var/lib/dpkg stuff?
[18:30] <jcristau> yes
[18:31] <jcristau> see dh_makeshlibs
[18:33] <tormod> I have dh_makeshlibs in debian/rules though
[18:34] <jcristau> but libdrm2.shlibs doesn't say anything about libdrm_intel.so.1
[18:37] <tormod> right. but that file is autogenerated if I understand man dh_makeshlibs
[18:38] <jcristau> no. maybe it should be, but right now it isn't
[18:40] <tormod> doesn't "dh_makeshlibs" create the shlibs file? or does it just create contents and you have to copy it in?
[18:44] <jcristau> it creates debian/$package/DEBIAN/shlibs
[18:45] <jcristau> but then that's overwritten by dh_installdeb copying debian/$package.shlibs afaict :)
[18:46] <tormod>  I think I understand. So I have to edit ﻿debian/$package.shlibs. what's the syntax for adding drm_intel?
[18:47] <jcristau> 'libdrm_intel 1 libdrm-intel1' and then add the package in debian/control, fix debian/*.install, ...
[18:47] <tormod> thanks
[18:47] <jcristau> or 'libdrm_intel 1 libdrm2 (>= foo)'
[18:48] <tormod> add which package?
[18:49] <jcristau> libdrm-intel1
[18:51] <tormod> aha the clean way of making a new package I suppose. but if I just want to hack the old packages, that would be your second option ﻿'libdrm_intel 1 libdrm2 (>= foo)' ?
[18:51] <jcristau> yup
[18:51] <jcristau> replace foo with the actual version number, obviously :)
[18:52] <tormod> yeah I got that, but I hope the rest was rather verbatim :)
[18:53] <jcristau> yeah. the format is '$libname $somajor $dependency'
[18:54] <jcristau> in this case the soname is libdrm_intel.so.1 -> shlibs contains 'libdrm_intel 1 $whatever'
[18:55] <tormod> $whatever should be >= my libdrm version?
[18:57] <jcristau> $whatever is what goes in the Depends field of anything linked against libdrm_intel (through ${shlibs:Depends})
[18:57] <jcristau> so in this case 'libdrm2 (>= yourversion)'
[20:02] <tormod> jcristau: thanks a lot, it built successfully. now to see if it runs...
[21:01] <nellery> Hi, which package should I file a bug about my capslock light on my laptop not turning on when enabled by an external keyboard
[21:02] <nellery> it does turn on when X is disabled
[21:02] <nellery> and it worked in previous versions
[22:39] <Ng> superm1: so, I had an idea of what this crash could be.... intel_agp
[22:40] <Ng> I just reproduced it twice and looking at the text I can just about see in the console, it gets a little way past the point where that loads
[22:40] <Ng> and I guess it's an obvious choice for something which would immediately mess up the display
[22:48]  * wgrant takes votes on who uses multi-finger tapping and finds it somewhat broken in Intrepid.