/srv/irclogs.ubuntu.com/2012/07/03/#ubuntu-x.txt

brycehanyone know if NVIDIA put out a new -96 yet?00:22
Sarvattseems pretty safe to say nvidia-96 is dead, its been a year since the last release03:13
bjsniderthat's too bad, as it's such a great driver03:19
mlankhorstmorning06:36
mlankhorstAw my keyboard died, one of the support legs snapped of. Finally enough motivation to buy a new one since this was a really damn good logitech keyboard. :)07:21
mlankhorstRAOF: just xf86-modesetting was added right?07:42
RAOFmlankhorst: Between Precise and Quantal? I think so, yes.07:45
tjaaltonhas the renaming postfix been decided? or do we just use what the kernel has? (-lts-q)07:48
tjaalton* -lts-quantal07:48
mlankhorstthink we just follow lts-quantal07:48
tjaaltonyeah, good07:48
tjaaltonshorter names :)07:48
mlankhorstit was just s/backport-// anyhow07:49
tjaaltonyup07:49
tjaaltonwonder if we can just sync libx11 now07:50
mlankhorstI'm really hoping.. can we make libdrm-nouveau1 be separately installable so we could upgrade libdrm instead of needing a rename?07:51
mlankhorstI could make the package for it07:51
tjaaltonremember that this would need to be done for every backport series07:52
tjaaltonsru'ing libdrm07:52
RAOFWe always need to upgrade/rename libdrm anyway; we only test the *whole* stack in ubuntu+107:53
mlankhorstyeah I know07:54
RAOFIf we cherry-pick bits of the stack we lose some of the benefit of that testing.07:54
RAOFThinking of libdrm, why aren't we on 2.4.35 again?07:54
mlankhorstnouveau07:54
RAOFChanges ABI. Does it bump SONAME, or do we need to beat someone with a seal?07:54
RAOFA *baby* seal.07:55
RAOFMy quick ls suggests that it does the sensible thing and is now libdrm_nouveau.so.2.07:55
RAOFWhich is entirely parallel installable with libdrm_nouveau.so.1, right?07:56
RAOFI guess we don't get to rebuild mesa, though.07:56
mlankhorstand that would really be the problem07:57
mlankhorstdon't get to rebuild libdrm_nouveau1a either07:59
tjaaltoncnd: I'm syncing both libx11 and libxi, looks like the upstream versions have everything we need08:00
mlankhorstcnd: yay synaptics 1.6.2 is in -proposed finally08:04
SarvattRAOF: it bumps soname but it doesnt ship the old version anymore which our mesa needs until august08:06
RAOFSarvatt: Right. The first would be fine; we'd just keep libdrm-nouveau1a around in the archive until everything had settled down. It's the latter bit that's the problem.08:07
Sarvattgive it a few days, airlied already bugged darktama about that08:08
Sarvattthey need to update f17 :)08:08
mlankhorsti think they added a hack there for it though :\08:08
RAOFThere's always the option of embedding libdrm-noueveau1a's source in mesa. :)08:09
Sarvattoh speak of the devil08:09
Sarvatt1 hour ago http://pkgs.fedoraproject.org/gitweb/?p=libdrm.git;a=shortlog;h=refs/heads/f1708:09
mlankhorstoh so it did land08:10
mlankhorstSarvatt: Well do you want to update libdrm or shall I?08:11
tjaaltonnice little patch :)08:11
Sarvattmlankhorst: 4am and whisky o'clock here, safe to assume the latter unless tomorrow :)08:12
mlankhorstheh sure08:13
=== yofel_ is now known as yofel
mlankhorstok uploaded renamed base packages, if they work I'll upload drivers again :)10:17
mlankhorstRAOF: can you upload 'xorg'? I updated the git tree for x1.1213:02
tjaaltonhe's probably asleep by now13:04
mlankhorstah k, can you?13:04
tjaaltonyep13:04
mlankhorstI verified the synaptics sru, uploaded libdrm to a local ppa for testing tomorrow, renamed xorg-server seems to have built succesfully, so I'm uploading all the renamed drivers and call it a day. :-)14:43
erapplemanis there any easy way to deal with libdrm-nouveau1a/2 collisions?17:06
erapplemanthe packages don't play nice if i use oibaf's ppa17:06
jcristauwho's oibaf17:08
mlankhorsterappleman: working on it :\17:17
mlankhorsthttps://launchpad.net/~mlankhorst/+archive/ppa didn't test yet17:17
mlankhorsttomorrow17:17
ricotzmlankhorst, i dont think that's what he is talking about, this is just a messed up packaging while putting nouveau.2 in nouveau1a package17:25
ricotzhttps://launchpad.net/~oibaf/+archive/graphics-drivers/+sourcepub/2495386/+listing-archive-extra17:26
mlankhorstoh17:48
mlankhorstthat should really not be attempted, even17:49
`rand`Bug: I upgraded to 12.04 and was disappointed to learn that the Sticky Keys feature has lost some functionality.  Specifically, pressing a modifier key twice no longer "locks" it, in Xkb terms; latching still works, but it's much more tedious.  Which package (or packages) would I need to look at to correct this?20:13
`rand`I guess, more generally, which package (or packages) control the core keyboard functionality for X and/or Ubuntu?  It's not just Unity, but even Awesome--which could enable sticky keys through the use of the xkbset package in prior versions--no longer works.  The regression is frustrating and I would love to help fix it.20:28
tjaaltonit's in the accessibility features20:32
tjaaltonsystem settings, a11y, writing..20:33
tjaaltonseems to work just fine20:34
tjaalton`rand`: ^20:34
tjaaltonpretty sure we would've heard about it by now if it was generally broken20:35
`rand`check bug 998877 on launchpad.20:38
ubottuLaunchpad bug 998877 in Ubuntu "Sticky keys disabled when pressed twice" [Undecided,Confirmed] https://launchpad.net/bugs/99887720:38
tjaaltonok20:41
brycehjust shoved in xdiagnose 2.9.  This changes the gpu lockup udev rule to hopefully eliminate false lockup reports.  but not entirely sure what it'll do, so keep an eye out for oddities with freeze bug reporting and let me know.20:47
tjaaltonokie20:48
`rand`bryceh: Was that to me?20:50
brycehno20:50
`rand`ah, thanks.20:51
`rand`tjaalton: which WM are you using?20:53
brycehI'm not really sure what exactly does the sticky keys thing.  xkeyboard-config is the source package for keyboard mapping issues, but haven't run across anything about sticky keys there.  I'd suggest asking one of the accessibility folks who deal with that functionality more regularly.20:53
=== Amaranthus is now known as Amaranth
`rand`Thanks bryceh.  It has something to do with modifying XkbStateRec, but I'm not sure where I would need to do that.20:55
tjaalton`rand`: i misread your description, sticky keys work but not that particular use case I guess20:56
`rand`I tried apt-get source xkbset, but it only gives me the .h files for the helper functions that modify it. :/20:57
`rand`tjaalton: it's all good, I just want to fix it.  I'm using 10.10 now until I can.20:58
tjaaltonso it happens with plain Awesome, ie. no gnome bits running?20:59
`rand`It no longer works in Awesome, sadly--no Gnome bits.21:00
tjaaltonthen it's probably something in the xserver that changed21:01
`rand`emacs is my preferred editor, so the regession was obvious immediately.21:02
tjaaltonamazing, no changes to the package since 200621:03
`rand`Is X hosted on git?21:03
tjaaltoncgit.freedesktop.org21:03
`rand`thanks!21:03
tjaaltonamong many other bits21:03
`rand`I'll clone the xserver repo and look through it.  What was the last commit for 11.10?  12.04?  That'll help me narrow my search.21:11
`rand`Hah--just saw my "hosted on git?"  Meant github. :)21:13
mlankhorstoh just 1 package failed to build in q-lts-backport21:13
tjaaltonso works on 11.10, not on 12.04?21:14
`rand`correct.21:14
mlankhorsthttps://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport/+build/3627065 yuck :S21:18
tjaaltonhmm, well it too had at least some version of the multitouch work21:18
tjaaltonmlankhorst: oh, did it build on quantal?21:18
mlankhorsttjaalton: probably, was using the source package from quantal21:19
mlankhorstbut it might have been copied over..21:19
mlankhorsttjaalton: I'm going to investigate tomorrow at least21:20
tjaaltonright, since the input drivers weren't rebuilt against the new server, since the abi should be the same. could be something else too21:20
tjaaltoni might just as well update wacom, though there aren't that many changes21:21
tjaalton0.16 should be out soon21:21
mlankhorstbut yeah nice point that it didn't build with quantal too, should have come up with that if i was more awake :)21:27
Sarvatt101_fix_build_against_frankenserver.patch just needs to be disabled, same thing that happened in synaptics21:42
tjaaltonah21:42
=== `rand` is now known as `rand`-AFK
mlankhorstSarvatt: sure will do that tomorrow, I guess I'm just the first to rebuild it :)21:44
tjaaltoni'll upload it to quantal now21:49
tjaaltonthere is xf86-input-wacom-0.15.99.1 but i've not time to test it before vacation, so dropping the patch will have to do21:50
tjaaltonmlankhorst: wait, where did you get -0ubuntu3?21:51
tjaaltonI only see -0ubuntu221:52
mlankhorstits a rebuild which bumps it21:52
mlankhorstiirc21:52
tjaaltonit's not in quantal21:53
tjaaltonmy git has 221:53
mlankhorsttjaalton: I mean I think the rename script bumped it21:53
tjaaltonahh ok21:53
tjaaltonthat's wrong :)21:53
mlankhorstyeah but i dont feel like clicking 50 times to rename it once more, next version21:54
tjaaltonwell it'll be messy if it stays like that21:55
mlankhorstit won't, just on the list of things to fix with x1.1321:56
cndbryceh: whot said we need to update our keyboard driver to 1.6.122:12
cndhttps://bugs.freedesktop.org/show_bug.cgi?id=5068322:12
ubottuFreedesktop bug 50683 in Server/General "Black screen with "AutoAddDevices" "Off"" [Major,Resolved: notourbug]22:12
tjaaltonin precise?22:13
tjaaltonquantal has it22:13
cndyeah, I think in precise22:14
tjaaltonit has 1.6.022:14
cndthe bug report is from a lubuntu 12.04 user22:14
brycehcnd, is there a ubuntu bug for that?  we'd need one for SRU22:16
brycehcnd, is there a specific patch I could pull, in case a point release update is not in the cards?22:17
tjaalton20beb15d24b5f8ab194b94f7e29f49e91ea38a8b probably22:18
tjaaltononly five commits there22:18
cndwhot said something about unresolve symbol xf86IsPC9822:24
tjaalton"Remove calls to xf86IsPc98()"22:24
tjaaltonsame :)22:24
cndyeah, that looks right :)22:25
brycehok22:25
cndwhot said we may also need http://cgit.freedesktop.org/xorg/driver/xf86-input-keyboard/commit/?id=38e4defe795776479594825859e101cd7cb5aa1722:28
cndit's the commit right before22:28
cndnm, he says not to worry about it22:28
tjaaltoncnd: hey, there was some talk about a sticky key regression since 11.10.. think it could be due to the input changes?22:29
cnddunno22:29
tjaaltonok, just a thought22:32
`rand`-AFKtjaalton: still here--I'm checking it now. :)22:43
=== `rand`-AFK is now known as `rand`
`rand`Be back tomorrow--hopefully with a solution!22:57
brycehumm23:26
brycehtjaalton, looking closer now at the upstream bug report, the guy saw his failure after enabling xorg-edgers on precise23:26
brycehso SRUing this to precise is not the right solution23:27
brycehthis needs to have -keyboard 1.6.1 added to xorg-edgers23:28
brycehcnd, ^^23:29
cndbryceh: ahh, ok, thanks :)23:30
cndbryceh: do we have warnings to tell people to file bugs in LP and not upstream when they use edgers?23:31
cndI don't know where we would put a warning like that though...23:31
cndmaybe in the ppa description23:31
cndsince that is shown when you want to add the ppa now23:31
brycehcnd, no in fact we do the opposite23:31
cndwe ask people to file upstream bugs?23:31
brycehyup.  purpose of edgers is to track upstream and provide packages of the upstream stuff to make testing easier23:32
brycehwe close out bugs about edgers problems if filed in LP.23:32
cndwell, that commit in xf86-input-keyboard was from last october23:33
cndif we're going to tell people to file bugs upstream, we probably need to keep in sync better23:33
* bryceh nods23:33
bryceh-keyboard in edgers is 1:1.6.1+git20120703.dd6f110c-0ubuntu0sarvatt~precise 23:34
cndhmm...23:34
cndthen what's going on...23:34
brycehupdated 47 min ago23:34
cndoh, just updated :)23:34
cndyay23:34

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