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