/srv/irclogs.ubuntu.com/2008/06/21/#ubuntu-x.txt

pwnguintjaalton: you have an opinion on backporting intrepid wacom to LTS?00:01
pwnguinor anyone else for that matter00:02
pwnguinwell at least kees agrees with me00:36
brycepwnguin: I at least wouldn't DISagree ;-)00:37
pwnguincody-somerville: did you ever figure out the process on the other side of the socket?00:37
cody-somervillepwnguin, X00:38
brycejcristau, tjaalton: cody and other xubuntu users are seeing a pretty widespread deadlock apparently triggered by a libxcb call in dbus-launch called from the xfce4 scripts.  fdo #1642000:38
brycejcristau, tjaalton: I was hoping you might have some insights or debugging/workaround suggestions00:38
pwnguincody-somerville: what's X up to at that point?00:39
pwnguinanother select?00:39
cody-somervillepwnguin, X is wait4()00:40
pwnguinwhich arguments?00:41
Q-FUNKbryce: hiya00:42
bryceQ-FUNK: hi00:42
cody-somervillepwnguin, I'm not sure00:42
bryceQ-FUNK: btw I had a question on if we should remove the -amd source package in intrepid?00:42
cody-somervillepwnguin, it just said pwait4() in ...00:42
cody-somervilleerr00:42
cody-somervillefrom, not in00:42
Q-FUNKbryce: there's no amd source package.  we only have an -amd transitional package that is provided by -geode.00:43
bryceQ-FUNK: ah cool ok00:43
Q-FUNKbryce: to my knowledge, everything is now back to normal for Intrepid.  Hardy is what remains unresolved.00:44
bryceok00:45
Q-FUNKand unless I'm mistaken, this dragged on long enough that we missed it for hardy.1 already.00:45
bryceyep00:46
bryceQ-FUNK: do you care to still try to get it in?00:47
Q-FUNKwe have to. it's an LTS.00:47
Q-FUNKand geode is completely broken for the next 5 years, unless we act quickly00:47
Q-FUNKwell... 3 to 5 years00:47
brycewhy "quickly" if we've already missed .1 (which I think was effectively missed several weeks ago tbh)00:48
Q-FUNKI have sorf-of figured out a way to get hardy users to make this work, but most people are not reading my blog and will simply decide that what used to work in gutsy no longer works, so the hell with ubuntu00:49
Q-FUNKit's not for my lack of trying to push this SRU. I was on this issue since even before UDS.00:49
cody-somervilleThere will be another point release00:50
Q-FUNKcody-somerville: we all know this.  users won't wait that long.00:51
Q-FUNKthey'll grab CD #2, install LTSP and notice that it doesn't work for them. 00:51
Q-FUNK.1 was a golden opportunity to fix this right after the release.00:52
Q-FUNKagain, those who are patient enough to google will find my two blog posts on the issue and could fix it.00:52
cody-somervilleDon't feel bad. Xubuntu users can't login half the time with Hardy. :(00:53
Q-FUNK:(00:53
Q-FUNKhttp://q-funk.blogspot.com/2008/06/howto-make-geode-thin-clients-work-on.html00:53
Q-FUNKhttp://q-funk.blogspot.com/2008/06/howto-build-clean-ltsp-boot-image-that.html00:53
cody-somervilleQ-FUNK, Is your blog on the planet?00:53
Q-FUNKno, since I'm not an Ubuntu member.00:54
Q-FUNKit's on the debian planet, though00:54
Q-FUNKor is an ubuntero a sufficient status to end up on the ubuntu planet?00:54
cody-somervilleIt is limited to Ubuntu Members.00:54
cody-somervilleHowever, I'd be happy to blog about your blog :)00:55
bryceQ-FUNK: I wish we had taken the time at UDS to sit down and experiment with it.  When I asked about that you seemed pretty optimistic that everything was sorted out, so it's a shame we didn't just prove it and get everything finalized right there and then.00:55
Q-FUNKbryce: I really wanted us to sit with ogra and go over this.  ogra was taken 100% by intel sales reps and the rest of us were just jumping from one session to the next.00:56
* cody-somerville thinks UDS should go back to being longer than a week.00:56
Q-FUNKcody-somerville: the sessions are too packed.  there should be plenty of slack between for people to actually hack on the issues they just discussed.00:56
bryceQ-FUNK: well if it makes you feel any better, I also feel bad.  I think I put in more energy for -amd during 8.04.1 than I did for any other driver, and I'm disappointed to hear no progress was made00:57
bryceanyway, /me -> lunch.  bbiab00:57
Q-FUNKbryce: the main issue that prevents 2.9.0-1-ubuntu2.1 from doing what it's intended is that pitti didn't like the idea of backporting the complete solution. he insisted on fitting the framework used for 2.8.0-7.00:58
Q-FUNKbryce: yes and it helpped a lot getting the issue heard by Steve and Martin for the SRU00:59
Q-FUNKbryce: unfortunately, there's too many bugd and too many SRU to audit, right after the .0 release, and with an UDS to conduct in the midst of it all.00:59
pwnguini have to wonder if ubuntu really has the resources for SRU in practice01:00
Q-FUNKI think that the next UDS should be conducted after release+1.1 is done, in the future01:00
Q-FUNKpwnguin: it mostly does, but the fact that people who are empowered to review SRU are also canoncal employees going from one plane to the next for their next canonicla event doesn't make this easier.01:01
Q-FUNKthe same problme happens at debian:  too few people are empowered to review and approve freeze exceptions.01:02
pwnguinwell i mean, you said the problem was requiring backported patches01:02
Q-FUNKand those people usually happen to have several other hats to wear, so their time for any given item is really limitted.01:03
pwnguinits a hell of an effort01:03
* cody-somerville nods.01:03
Q-FUNKnot if the backport is done and sitting in someone's PPA for weeks.01:03
Q-FUNKat that point, all it requires is for someone to review and either ack or nack the backport.01:04
pwnguinare we talking about sru or backport here?01:04
pwnguinthey're different things01:04
Q-FUNKboth01:04
Q-FUNKnew upstream and backported package of it from debian, with hardy-specific changes.01:05
Q-FUNKSRU for newly suported hardware and important fixes.  backport of the debian packaging, with small changes to compensate for e.g. older dpkg-dev in hardy.01:06
pwnguinin related news01:07
pwnguini hate cvs01:07
Q-FUNK:)01:07
Q-FUNKCVS is showing its age.01:07
pwnguinwhoever thought independent file versions made sense should be shot01:07
Q-FUNKit's a different philosohpy01:08
Q-FUNKcommit-based, versus file verison based01:08
pwnguinwell when im trying to see where upstream fixed wacom going crazy bugs01:09
pwnguincommit based is what i want01:09
Q-FUNKright, thta would be git01:09
pwnguinssh01:09
pwnguinyou mean bzr ;)01:09
Q-FUNKouch01:10
Q-FUNKplease gimme my cathedral back!01:10
pwnguinive no allegience to either git or bzr01:11
pwnguinbut theres a storm a comin01:11
Q-FUNKoho01:11
Q-FUNKcody-somerville: but, sure, if you wanna blog about the above two posts, please do so :)01:11
cody-somervilleQ-FUNK, will do :)01:12
bryceback01:17
cody-somervillewb01:40
brycecody-somerville: I don't know if I got all the deps straight, but I've put together a libx11 with xcb disabled for you.  I'm uploading the debs presently.01:50
brycecody-somerville: they'll be appearing at http://people.ubuntu.com/~bryce/Testing/libx11/01:52
pwnguinanyone ever heard of a VTBook?02:20
pwnguinits this crazy video card on a PC card02:23
pwnguinsomeone in -laptop went asking about it02:23
brycepwnguin: wild02:31
pwnguinhttp://www.villagetronic.com/ftp/vtbook/Linux/LinuxReadMe.html02:31
pwnguinyou should forward that to canonical's OEM support salesmen ;)02:31
brycepwnguin: ok, but why?  (I may be dense)02:32
pwnguinwell, they clearly need help02:32
pwnguinthe provided driver is a patch to the kernel02:33
pwnguin"    *  Fedora Core 1"02:34
pwnguin    * Suse 9.1 (Thanks to Gil Spencer for important help)02:34
bryce* No kernel patch needed for systems with Kernel 2.6.22 or later02:35
brycebut yeah that looks like a painful setup process02:35
bryce"    *  Kernel 2.6.10 or newer02:35
bryce    Edit the setup-bus.c file in linux-2.6.y/drivers/pci/.02:36
bryce    Locate the following definition: #define CARDBUS_MEM_SIZE (32*1024*1024)02:36
bryce    Replace it with the following:  #define CARDBUS_MEM_SIZE (128*1024*1024)"02:36
pwnguinim checking to see if that's actually in kernel.org right now02:36
bryceusing the 'trident' driver02:36
pwnguinyea02:37
* bryce loves OEMs that use gfx drivers he has little experience with02:37
brycepwnguin: <wince> yeah I think I'll pass on showing this to the OEM folks ;-) 02:37
pwnguinheh02:38
brycealthough it wouldn't surprise me if with ubuntu it all "just worked" since we have a new enough kernel and it sounds like it works with stock trident and stuff02:38
pwnguini dont own one but ive seen a couple reports of it not just working02:39
pwnguinhttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fe0e5c4d947d34f10002b4cf272f0ebf110305b702:39
pwnguinthe commitlog is hilarious at least02:40
brycecody-somerville: hey there's a reply from bart02:44
* cody-somerville nods.02:44
cody-somerville:)02:50
bryceok so like I said in the email I'm starting to think the disable-xcb option is sounding more like the direction we'll need to go, esp. given the mounting evidence and bart's confirmation this pretty much a known issue02:51
brycehopefully over the weekend someone can verify the non-xcb libx11 package I did; if not I'll finish building a xubuntu test rig monday02:53
bryceI envision this will be a painful SRU though.02:53
cody-somervilleIndeed.02:53
cody-somervilleCan you send off an e-mail to ubuntu-devel and techboard to let them know whats up?02:54
brycesure02:54
brycewhy techboard?02:54
cody-somervilleThey're supposed to be notified of regressions02:54
pwnguinwhat?02:54
pwnguinregressions in what?02:54
brycecody-somerville: "techboard@lists.ubuntu.com" ?02:55
pwnguinif techboard is the place to get attention about regressions02:57
pwnguini have some email to send02:57
cody-somervilletechnical-board@lists.ubuntu.com02:57
brycecody-somerville: url for this policy?02:57
cody-somervilleI'm not looking at it right now02:58
cody-somervillebut I know they're supposed to be notified of serious regressions02:58
cody-somervilleand all regressions introduced by SRUs02:58
pwnguinmicrorelease exception?03:00
pwnguinhttps://wiki.ubuntu.com/StableReleaseUpdates03:01
pwnguinn the event of a regression, immediately notify the [WWW] Ubuntu Technical Board via email, and ask for help on #ubuntu-devel in making urgent contact with a member of the Board or the SRU team: state the problem, the bug number, and ping "slangasek, Riddell, Hobbsee, pitti, mdz, Keybuk, cjwatson, keescook, jdstrand, BenC, dendrobates, davidm". For SRU in universe/multiverse, contact the [WWW] Universe SRU Team team or ask for help on #ubuntu-motu in03:01
bryceahh03:27
brycethat doesn't apply in this case - that's for if there is a huge regression due to an SRU release03:28
bryceI think that's so people can have a chance to pull the update from the mirrors before it goes out to everyone03:28
brycein this case the issue is already fully deployed03:28
cody-somervilleI think we should delay the point release03:29
brycecody-somerville: ok I've emailed ubuntu-devel@; you can feel free to forward to techboard and/or request point release delayment as you see fit03:38
bryceto be honest, I'd prefer to see my libx11~noxcb package verified first.03:41
cody-somervilleI'll be sure to test it after I get some sleep :]03:47
bryceok, I'm done too.  have a nice weekend.03:51

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