[03:18] <LLStarks> just spent an hour with a llano laptop
[03:18] <LLStarks> probably the first person to publicly test linux on it
[03:19] <LLStarks> won't boot because no updated ddx and no mesa 7.11
[03:19] <LLStarks> oh well
[03:59] <LLStarks> sarvatt, is there any way to roll my own iso with edgers? i'm feeling a bit daring.
[03:59] <LLStarks> would i have to do something like a persistent image with oneiric nightly and ppa the drivers into the persistence?
[04:32] <DanaG> Okay, I've made a more coherent comment on this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/546697
[04:32] <ubot4> Launchpad bug 546697 in xserver-xorg-input-synaptics (Ubuntu) "enable multitouch support on older touchpads, as supported by driver v15.0.9.0 (affects: 3) (heat: 14)" [Medium,Confirmed]
[04:32] <DanaG> Would somebody mind taking a look at it?  It'd be a killer feature to be able to use multi-finger detection on systems that have never supported it.
[04:47] <LLStarks> i think cnd wants it disabled in ubuntu
[04:48] <LLStarks> i have my laptop manually set up to use 2-finger middle click and 2-finger scrolling
[04:50] <LLStarks> btw danag, you can do it with the current drivers
[04:51] <LLStarks> it's just disabled by ubuntu because it screws up some touchpads
[04:51] <DanaG> One big gripe: you can no longer do "synclient -m"
[04:51] <DanaG> So you can't even tell how many fingers it sees!
[04:51] <LLStarks> you can use xinput commands
[04:51] <DanaG> Really?  Can it give you this?
[04:52] <DanaG>      time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy    0.000     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
[04:52] <DanaG> er
[04:52] <DanaG> That was two lines.
[04:52] <DanaG> It spews the current state.
[04:52] <LLStarks> xinput set-prop 'SynPS/2 Synaptics TouchPad' 'Synaptics Two-Finger Pressure' 29
[04:52] <DanaG> That's not what I want.
[04:53] <DanaG> What I want is real two-finger support.
[04:53] <DanaG> There's exactly one magic Windows driver that gives me it.
[04:53] <DanaG> Real.  Not fake.
[04:53] <DanaG> It must patch the firmware, or ignore the reported capabilities, or something.
[04:53] <LLStarks> well, that command permits amazing 2-finger scrolling
[04:53] <DanaG> I get that shmconfig for settings changing was insecure... but we still need the "monitor" mode.
[04:54] <DanaG> Still not real.
[04:54] <DanaG> If "monitor" is insecure, then make it root-only!
[04:54] <DanaG> You can't get that log of touchpad data with xinput.
[04:54] <LLStarks> can you give me the vendor string for the touchpad?
[04:55] <DanaG> "SynPS/2 Synaptics TouchPad"
[04:55] <DanaG> i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[04:55] <DanaG> It's a 7.2 or 7.0 or something.
[04:56] <LLStarks> can you link the driver in question?
[04:56] <DanaG> I also have a TouchStyk that's recognized as a "PS/2 Generic Mouse".
[04:56] <LLStarks> lenovo?
[04:56] <DanaG> Nope, HP.
[04:56] <LLStarks> hp does nubs? O_o
[04:56] <DanaG> Lenovo calls it TrackPoint; Synaptics calls it TouchStyk.
[04:56] <DanaG> Yup, the business laptops do.
[04:56] <DanaG> I don't use mine, so it's not a big deal... but you can't set sensitivity or "press to click".
[04:57] <DanaG> http://www.mydigitallife.info/unlock-and-enable-multitouch-gestures-on-synaptics-touchpad-or-trackpad-driver-download/
[04:57] <DanaG> Direct URL: Win7: ftp://ftp.hp.com/pub/softpaq/sp47501-48000/sp47815.exe   XP: ftp://ftp.hp.com/pub/softpaq/sp47501-48000/sp47816.exe
[04:57] <DanaG> It also unlocks the nice "ChiralMotion" scrolling.
[04:58] <DanaG> Picture circular scrolling where you don't have to go all the way around the center of the pad.  You can do a tiny circle starting in the scroll area, instead.
[04:58] <DanaG> And you can start vertical circle from right edge, or horizontal circle from bottom.
[04:59] <DanaG> A bit of HP fail: the stick buttons don't belong to the stick.
[04:59] <DanaG> So you can't have stick scrolling AND have working touchpad middle button.
[04:59] <DanaG> (Yup, the 15" and above (now workstation only) EliteBooks have 3 buttons.
[04:59] <DanaG> )
[05:00] <DanaG> You know you're a programmer when you're obsessive-compulsive about parentheses.
[05:00] <DanaG> Handy trick: open Mouse control panel, and press alt-shift-i
[05:01] <DanaG> So either the driver is patching the firmware, or it's ignoring the capabilities and assuming full capabilities.
[05:02] <DanaG> It's worked on an Athlon XP-M laptop that before could do only basic two-finger in Linux, as well as my 8530w that only ever did 1 finger.
[05:16] <DanaG> Magic trackpad: why the heck does a touchpad need to be wireless?  That's like having a cordless drill press.
[05:17] <DanaG> ANd it makes it a no-go for places that don't allow bluetooth due to security concerns.
[05:37] <LLStarks> hey bryceh, i think the plymouth bug that causes x to crash upon an enter keypress is back in the daily images
[05:38] <bryceh> LLStarks, hrm
[05:38]  * bryceh thinks
[05:39] <bryceh> wasn't that one something where plymouth was waiting for the user to enter something, and then resetting X once it detected a return?
[05:39] <bryceh> LLStarks, try downgrading plymouth and see if it resolves
[05:40] <anymouse> accidentally pressed enter
[05:40]  * anymouse sighs
[05:41] <LLStarks_> anyway, i've only observed it in the live session
[05:41] <LLStarks_> but enter will crash x
[05:41] <LLStarks_> pretty sure it's the same plymouth bug
[05:42] <LLStarks_> finally ghostkilled
[05:42] <LLStarks> anyway bryceh, didn't catch anything after hrm
[05:43] <LLStarks> using the onscreen keyboard is maddening
[05:45] <bryceh> * bryceh thinks
 wasn't that one something where plymouth was waiting for the user to enter something, and then resetting X once it detected a return?
[05:45] <bryceh>  LLStarks, try downgrading plymouth and see if it resolves
[05:46] <LLStarks> will do
[05:48] <bryceh> looks like there's been some recent commits to plymouth to handle tty keyboard output
[05:50] <LLStarks> this is going to be a pain to test since it's a live environment, i can't press enter, and reinitializing plymouth under said circumstances is tough
[05:51] <LLStarks> the strangest thing is that the bug has been present since at least alpha 1 images
[05:52] <LLStarks> and oneiric plymouth is in natty-updates
[05:53] <LLStarks> would a text boot negate plymouth?
[05:53] <bryceh> yep
[05:53] <LLStarks> just get rid of quiet from the kernel line, right?
[05:53] <bryceh> quiet and splash I think
[05:54] <bryceh> hmm, 0.8.2-2ubuntu23 appears to be the latest plymouth version, which was on 21 Apr
[05:55] <bryceh> so maybe it isn't a plymouth regression
[05:55] <bryceh> LLStarks, pastebin your /var/log/dpkg.log
[05:57] <LLStarks> i would if i didn't wipe my ubuntu partition yesterday <_<
[05:58] <LLStarks> but like i said, i've worked around this bug since the first oneiric images
[05:59] <bryceh> oh right, it's with the daily images anyway
[06:00] <LLStarks> lemme reboot and test splashless booting of the iso
[06:04] <LLStarks> well, it's not plymouth. text boot didn't help. still crashing to tty upon first enter keypress.
[06:05] <LLStarks> and still no error messages
[06:08] <bryceh> hmm
[06:15] <bryceh> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/532047
[06:15] <ubot4> Launchpad bug 532047 in xorg-server (Ubuntu) (and 2 other projects) "Plymouth text-mode splash causes X to crash on first run due to shared tty7 (affects: 199) (dups: 44) (heat: 660)" [Undecided,Invalid]
[06:16] <bryceh> *** A temporary workaround is to disable the plymouth-splash upstart job ***
[06:16] <bryceh> sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth-splash.conf.disabled
[06:16] <bryceh> LLStarks, if it is indeed the bug we had before, see if that workaround works around it
[06:17] <LLStarks> is this something that needs to be done with a persistence so that the live session can be "rebooted" to test it
[06:24] <bryceh> LLStarks, probably
[06:26] <LLStarks> if it works, it'll make my bacon-tester stick much more useful
[06:28] <LLStarks> here we go
[07:10] <LLStarks> bryceh, no luck disabling plymouth or updating drivers
[07:15] <LLStarks> sounds like bug 787821
[07:15] <ubot4> Launchpad bug 787821 in plymouth (Ubuntu) "Random X server crashes on keypress using natty (affects: 3) (heat: 127)" [Undecided,New] https://launchpad.net/bugs/787821
[07:15] <LLStarks> i'm getting 8's and diamonds when i crash to tty
[07:16] <LLStarks> i'm going to try removing plymouth altogether
[07:17] <LLStarks> brb
[07:39] <LLStarks> bryceh, confirming all symptoms of bug 787821. x starts on tty2 and crashes on 2 or enter
[07:39] <ubot4> Launchpad bug 787821 in plymouth (Ubuntu) "Random X server crashes on keypress using natty (affects: 3) (heat: 127)" [Undecided,New] https://launchpad.net/bugs/787821
[07:40] <LLStarks> screen drops to a tty (not sure which) with nonsense output a few characters long
[07:54] <LLStarks> *starts on tty1
[09:37] <bryceh> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/787821
[09:37] <ubot4> Launchpad bug 787821 in plymouth (Ubuntu) "Random X server crashes on keypress using natty (affects: 3) (heat: 127)" [Undecided,New]
[09:41] <tjaalton> i've actually seen that on lucid too
[09:41] <tjaalton> recently
[09:41] <tjaalton> not my machine but friends
[09:48] <tjaalton> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/579313/comments/19
[09:48] <ubot4> Launchpad bug 579313 in plymouth (Ubuntu) "X crashes after pressing enter or 2 in 10.04 final release (affects: 3) (heat: 14)" [Undecided,Triaged]
[11:41] <RAOF> Shiny new mesa, now with working Unity!
[11:42] <tjaalton> 7.11 snapshot?
[11:42] <RAOF> Yeah.
[12:08] <Sarvatt> RAOF: awesome
[12:09] <RAOF> Running a parallel build on the e62thingy to check that I haven't broken it.
[12:12] <RAOF> It looks like it's faster to build mesa on it than to upgrade to oneiric :)
[12:42] <seb128> bug #803012 has an upstream commit backport waiting for sponsoring if somebody wants to have a look it
[12:42] <ubot4> Launchpad bug 803012 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "Intel driver incorrectly renders some UI elements (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/803012
[12:46] <tjaalton> RAOF: push the intel release to git
[12:46] <RAOF> :(
[12:47] <tjaalton> not on your lappy?-)
[12:47] <RAOF> Am on my lappy, but URGH!  Sorry.
[12:47] <RAOF> Pushed
[12:47] <tjaalton> ah nice, thought that the branch was not, but good
[12:48] <tjaalton> seb128: I can take care of that
[12:50] <Sarvatt> RAOF: built fine parallel=8 here
[12:51] <RAOF> Did here, too.
[12:51] <RAOF> Checking that it actually works on the e6420, then uploading.
[12:55] <seb128> tjaalton, thanks
[12:56] <tjaalton> uploaded
[14:03] <ScottK> Sarvatt: I just had a complete X freeze (it didn't crash completely, but just froze - couldn't even move the cursor) on my Sandybridge laptop (Natty).  The only error I can find matches the error message in Bug 761065.  How can I file a useful bug/add information that woud be helpful?
[14:03] <ubot4> Launchpad bug 761065 in xserver-xorg-video-intel (Ubuntu Natty) (and 4 other projects) "[Sandybridge] Spurious "*ERROR* Hangcheck timer elapsed... blt ring idle" messages in dmesg when using compiz (affects: 52) (dups: 5) (heat: 298)" [Undecided,Invalid] https://launchpad.net/bugs/761065
[14:04] <Sarvatt> ScottK: that's fixed already and sitting in natty-proposed kernel hell unfortunately
[14:04] <Sarvatt> wont be released until 2.6.38-11
[14:04] <ScottK> Sarvatt: OK.  So just patience then.  Thanks.
[14:07] <tjaalton> RAOF: whoa, SRU team, and soon archive admin :P
[14:26] <ScottK> Pretty soon he'll be useless for real work.
[14:30] <RAOF> Heh.
[16:04] <tjaalton> hmm so do we tag every bug we pass on to the kernel?
[16:04] <tjaalton> input related too
[16:09] <tjaalton> "no"
[16:40] <tjaalton> lightdm doesn't seem to restart the xserver on logout
[16:40] <lilstevie> lightdm is also uglier
[16:41] <lilstevie> well not so much uglier, just doesn't feel right
[16:41] <RAOF> tjaalton: I'm not sure about input :)
[16:41] <jcristau> it feels NIH.
[16:42] <tjaalton> RAOF: Sarvatt said that no :)
[16:43] <tjaalton> lightdm also starts on the current vt if you start it from one, and user switching b0rked atm
[16:46] <tjaalton> since it tries to run gdmflexiserver
[16:46] <tjaalton> well, the applet
[16:50] <tjaalton> heh, the new gdm is in depwait, needs libaudit-dev in main
[16:50] <tjaalton> kees: ^ :)
[16:51] <tjaalton> or maybe gdm will end up in universe
[16:53] <ScottK> tjaalton: kdm doesn't restart the xserver on logout either, IIRC.
[16:53] <lilstevie> but kdm is also a whore for getting on screen keyboards up :(
[16:54] <tjaalton> ScottK: right, so in order to test updates you need to either reboot or restart it by hand :)
[16:55] <jcristau> sudo killall Xorg ftw
[16:55] <ScottK> lilstevie: That's true, but a separate issue.
[16:55] <lilstevie> ScottK: heh
[16:55] <tjaalton> there's also a bug where cursor up doesn't work after a logout, but works if the server is restarted, and he's using kde ;)
[16:56] <jcristau> bad keymap reset on regen?
[16:56] <tjaalton> probably the cache playing tricks
[16:56] <tjaalton> dunno
[16:59] <tjaalton> hm, something to rule out though
[17:10] <RAOF> Oh, goddamn you PowerPC.  Why do we even build for you?
[17:25] <tjaalton> ok so -evdev wasn't pushed to git either
[17:26] <tjaalton> -1u12 upload
[17:27] <RAOF> Is that me again? :(
[17:27] <tjaalton> not sure :)
[17:27] <tjaalton> not blaming anyone yet, except me for not checking the current version earlier
[17:27] <tjaalton> I already pushed my changes
[17:28] <tjaalton> actually it was cnd this time :)
[17:29] <tjaalton> I'll fix the changelog
[17:30] <cnd> tjaalton, likely wasn't me
[17:30] <cnd> I can't actually upload
[17:30] <cnd> well, maybe it was...
[17:30] <cnd> I might have built a src package and had bryce sign and upload
[17:30] <cnd> but likely not :)
[17:30] <cnd> I'm too lazy :)
[17:30] <tjaalton> hehe :)
[17:36] <tjaalton> hmm, no xauth with lightdm
[17:47] <Sarvatt> lost all my indicators in todays upgrade, had to install the -gtk2 indicator packages
[17:48] <tjaalton> i lost the sound one
[17:48] <tjaalton> the battery indicator has been gone longer
[17:48] <Sarvatt> yeah true, networks gone too though
[17:49] <Sarvatt> wonder if nm just needs a rebuild
[17:51] <bryceh> tjaalton, in talking with ogasawara what they want is for us to tag 'kernel-handoff-graphics' for issues we think are worth the kernel team's attention, so not every bug we forward
[17:51] <tjaalton> bryceh: ah, hehe
[17:52] <bryceh> tjaalton, also, for really important ones (like ones with patches that are ready to go), also ping them on #ubuntu-kernel
[17:52] <tjaalton> yeah quirky mice that scroll too fast clearly don't fall under that category..
[17:53] <bryceh> RAOF, congrats on SRU-hood.  You can help us get more X fixes out :-)
[17:53] <RAOF> bryceh: Surch is the plan :)
[17:55] <bryceh> I was poking around in lightdm to figure out how to hook in failsafe-x.  There isn't a way to do it yet, but I proposed something to Robert; waiting back on that.
[17:55] <RAOF> Cool.
[17:56] <tjaalton> can't find where the server auth file should be stored
[17:56] <RAOF> Robert was asking about what failsafe X actually tries to do.
[17:58] <bryceh> RAOF, ah, did you set him straight on it?
[17:59] <RAOF> Yup.
[17:59] <RAOF> At least, I think so :)
[18:00] <bryceh> tjaalton, the X session seems to be called from /etc/lightdm/Xsession but for the auth file itself, should it go into /run?  or should it still live at $HOME/.Xauthority ?
[18:01] <bryceh> I'm feeling like I'm missing out on all the good chats :-/
[18:01] <bryceh> but with it so quiet I'm getting lots done
[18:01] <tjaalton> bryceh: actually, ligthdm puts it in /var/run/lightdm/authority/NUM
[18:01] <bryceh> makes sense
[18:01] <tjaalton> at least that's where $XAUTHORITY is pointing, but doesn
[18:01] <tjaalton> 't  work
[18:03] <bryceh> permissions?
[18:03] <bryceh> seems to be owned/writable only by root
[18:03] <tjaalton> nah, owned by me
[18:03] <bryceh> hmm, on my machine the directory exists, owned by root, but is empty
[18:04] <tjaalton> Attempting to break locks on authority file /var/run/lightdm/authority/2
[18:04] <tjaalton> there
[18:04] <tjaalton> xauth -v -b list
[18:04] <bryceh> # xauth -v -b list
[18:04] <bryceh> Attempting to break locks on authority file /home/bryce/.Xauthority
[18:04] <bryceh> Using authority file /home/bryce/.Xauthority
[18:05] <bryceh> wait
[18:05] <tjaalton> you are using gdm :)
[18:06] <bryceh> no, running the command from an ssh session
[18:06] <bryceh> ok, yeah running from the machine itself get the same error you do
[18:07] <bryceh> and then it times out after 30 sec or so
[18:07] <tjaalton> yep
[18:07] <tjaalton> filed bug 803546
[18:07] <ubot4> Launchpad bug 803546 in lightdm (Ubuntu) "Xauthority locked up (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/803546
[18:11] <bryceh> added a bit more for the gpu lockup hook:  http://paste.ubuntu.com/635185/