[00:03] <jasonb> Hello.  I have some questions about the Canonical partner repository (just that repository).  I'm wondering what the new package acceptance process is, and what the acceptance criteria are.  So far I have not found any web pages about this.
[00:35] <asac> kees: please check with chrisccoulson .... if it involves patches we need to talk to upstream as usual. if there is something serious let me know
[01:42] <lamont> there.  gtk+2.0 now building on one of the new-n-good armel buildds
[01:45] <lifeless> \o/
[01:47] <kees> pitti: what do you think of a nautilus work-around for bug 543617 ?  (or in umount itself...)
[02:03] <RoAkSoAx> lamont, any word on bug #533601
[03:05] <seyacat> Hi ubuntu devel
[03:05] <seyacat> what is the name of package of text mode ubuntu installer? like ubiquity but in text mode
[03:16] <arand> seyacat: debian-installer, I would assume.
[03:38] <kees> pitti: cups> debian 572940 is about CVE-2010-0302, not CVE-2010-0393.
[05:22] <NinoScript> Hi! the other day, I updated Lucid, and a udev file in which I loaded an experimental driver for multitouch trackpads, changed and I am not able to load that driver again
[05:24] <NinoScript> the file is "/lib/udev/rules.d/66-xorg-synaptics.rules", the line I used was: ENV{x11_driver}="multitouch"
[05:28] <ScottK> NinoScript: Help for Lucid is in #ubuntu+1
[05:31] <NinoScript> ScottK: I asked there yesterday and the day before, but nobody knew (and I'm asking again, now)… as it has more to do with the actual development of the driver, I thought I could ask here :P
[05:32] <ScottK> You might ask in #ubuntu-x
[05:34] <NinoScript> Ok, that's useful, thanks! :D
[05:52]  * kirkland just gives up and assigns all of his bugs to pitti :-)
[06:01] <nbreen> I maintain a Debian package, grace, that fixed an annoying UI bug (can trap the cursor, have to kill from console; #567323, LP 552681) in the most recent Debian upload.  Any way I can nudge that past the freeze?
[06:01] <nbreen> (Apologies if I overlooked some documentation; my ubuntu-fu is weak, I only found the freeze exception instructions for new *upstream* versions, which this is not.)
[06:04] <ScottK> nbreen: That's because bug fix updates don't need a freeze exception.  You can request a sync using the requestcync script in ubuntu-dev-tools (which is in Debian now).
[06:05] <nbreen> Will do, thanks for the pointer.
[08:45] <apparle> what are the -dbg for?
[08:49] <apparle> how to use the xserver-xorg-video-ati-dbg package to check the internals of the driver
[10:34] <jackz> when will 10.04.1 be released normally?
[10:35] <pitti> ScottK: oh, I wasn't aware that you are blocking on me for the sync script; please add an appropriate license header, I'm really not legally attached to it at all :)
[10:36] <pitti> kirkland: give up? when you are always constantly beating me? :-)
[11:47] <fta> tseliot, fyi, jokey failed on a fresh install of lucid while installing nvidia-current: http://paste.ubuntu.com/408038/  i had to do it manually
[11:47]  * tseliot has a look
[11:48] <tseliot> fta: well, it's more correct to say that jockey interpreted a warning as an error and claimed to have failed
[11:49] <fta> tseliot, yep, but after a restart of X, it failed, the kernel module wasn't there
[11:50] <tseliot> fta: are you sure about that? the log says that the module was built and installed. Maybe it didn't set the correct alternative. Either way a reboot is required
[11:50] <fta> i had to --reinstall nvidia-current and reboot (as restart kept on using nouveau, probably due to DKMS
[11:52] <tseliot> fta: the problem is that nouveau was preventing nvidia from being loaded
[11:53] <tseliot> updating  the initramfs would have been enough
[11:54] <fta> tseliot, maybe. it's not a problem for me, i quickly managed to sort this out, but i assume lots of people will face this
[11:54] <tseliot> pitti: logging.error(err) in oslib.py (line 248) shouldn't cause jockey to fail, right? Is there anything else that could be causing this?
[11:56] <tseliot> fta: I think we have a bug report about it and it's definitely something I'll have to fix
[11:56] <fta> ok, good
[11:59] <tseliot> fta: I think it's bug #552653
[12:00] <fta> tseliot, yep, that's it
[12:00] <tseliot> ok
[12:00] <fta> tseliot, btw, why isn't libvdpau1 a dep of nvidia-current?
[12:02] <tseliot> fta: programs that use vdpau should have it as a dependency. It's not really specific to nvidia
[12:02] <fta> i thought vdpau was nvidia specific..
[12:03] <lifeless> no
[12:03] <lifeless> other implementations exist now
[12:04] <tseliot> the nvidia specific bits are in nvidia-current
[12:04] <fta> ok :)
[14:04] <Cheery> hi
[14:04] <Cheery> while ago I started to wonder.
[14:04] <Cheery> why does ubuntu have duplicate keyboard layouts?
[14:04] <Cheery> ones for xorg and others for terminal
[14:05] <cjwatson> it doesn't
[14:05] <cjwatson> the terminal layouts are automatically generated from the X layouts, and have been for over three years
[14:06] <cjwatson> any differences are simply because the Linux console's support for some things isn't quite as rich as X's
[14:07] <Cheery> so you already generate terminal layouts from X layouts.
[14:07] <Cheery> what prevents from using X layouts in terminal directly?
[14:07] <cjwatson> different file formats
[14:07] <cjwatson> why bother doing all the work to make the kernel support XKB, when we can just as well convert things on the fly in userspace?
[14:08] <cjwatson> some things are better done outside the kernel
[14:08] <cjwatson> and, honestly, what difference does it make?
[14:09] <Cheery> some apps ignore the X layouts.
[14:09] <Cheery> and switching layout from X doesn't switch the layout kernel is using
[14:09] <cjwatson> um.  what do applications have to do with it?  keyboard layouts are at a lower level
[14:10] <cjwatson> 'dpkg-reconfigure console-setup' changes both of them system-wide
[14:10] <ScottK> Would a buildd admin please rescore qscintilla2 and kde4libs.  The fact that they are lagging on ports is going to cause a number of other problems.
[14:10] <cjwatson> it's intentional that it's possible to have a different per-user layout - it's entirely possible on multi-user systems that different users might prefer different layouts
[14:11] <Cheery> aah. yet per-user layouts.
[14:11] <cjwatson> ScottK: done (insofar as it'll make much difference on ia64 :-/)
[14:12] <ScottK> cjwatson: thanks.
[14:13] <Cheery> cjwatson: though X is ancient, how come it has 'better' keyboard layout stuff than kernel?
[14:13] <cjwatson> XKB is not all that ancient; it's of approximately the same vintage as the kernel's keyboard layout handling, possibly even a little later
[14:14] <Cheery> likely older than unicode as well, right?
[14:14] <cjwatson> and one might expect XKB to support a wider variety of layouts, given that there are some complex scripts the kernel can't cope with displaying on the console
[14:14] <cjwatson> Cheery: incorrect
[14:15] <cjwatson> both XKB and the Linux kernel's keyboard layout support date from the early-to-mid-1990s, after Unicode started
[14:15] <cjwatson> first version of the Unicode standard was 1991, predating both of them
[14:15] <cjwatson> but I'm going out so I'm afraid you'll have to do the rest of the research yourself :-)
[14:17] <Cheery> cjwatson: thank you anyway. it was fun and interesting topic.
[14:35] <primes2h> tseliot: Hello, I reported a bug about plymouth bug #553954
[14:35] <primes2h> tseliot: you wrote that script, didn't you? :-)
[14:36] <primes2h> Is bug description correct?
[14:37]  * tseliot has a look
[14:39] <tseliot> primes2h: yes, it's correct. Plymouth isn't localised. Is mountall localised?
[14:40] <primes2h> tseliot: it has just been fixed bug 390740
[14:46] <primes2h> tseliot: what do you think about the bug?
[14:47] <tseliot> primes2h: each plymouth theme e.g. the one for ubuntu, kubuntu, etc. will have to be modified so as to allow localisation
[14:48] <ScottK> Sounds like step on is a bug on the relevant packages then
[14:48] <primes2h> tseliot: it would be better to put that string in an outer package, wouldn't it?
[14:48] <primes2h> like all others
[14:52] <tseliot> primes2h: I'm not really sure about how we should do this. I'll think about it
[14:54] <primes2h> tseliot: Ok, thank you. :-) unfortunately it's a annoying bug because the string is very visible (and quite big)
[14:57] <tseliot> I know, I'll see what I can do
[14:58] <primes2h> ScottK: what do you mean? are you talking about this bug?
[15:00] <primes2h> bug #553954
[15:01] <ScottK> Yes.
[15:01] <ScottK> If each plymouth theme needs updatiing, then there ought to be a bug against each one
[15:07] <primes2h> ScottK: Sure, or take the string out to another common package, like others.
[15:08] <cody-somerville> Why is Ubuntu's plymouth theme seeded in standard?
[15:24] <ari-tczew> please sponsor bug 421684
[15:30] <bdrung> ari-tczew: k
[15:41] <bdrung> ari-tczew: done
[15:50] <kirkland> pitti: around?
[15:55] <souffledev> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/513745
[15:55] <souffledev> that's my problem. anyone? :)
[15:57] <souffledev> damnit :/
[16:54] <kirkland> nice, "maverick", i dig it!
[16:54] <kirkland> http://www.markshuttleworth.com/archives/336
[17:05] <LaserJock> kirkland: although I have a hard time imagining a maverick meerkat
[17:05] <LaserJock> they seem almost borg-like on TV
[17:06] <LaserJock> warm and fuzzy borg, but still :-)
[17:26] <mdeslaur> Since my last dist-upgrade, plymouth now displays in text mode even though I have kms on my thinkpad T30
[17:26] <mdeslaur> how would I go about figuring out why?
[17:29] <slangasek> mdeslaur: are you missing the plymouth-theme-ubuntu-logo package?
[17:30] <slangasek> mdeslaur: themes were split out to a) discourage users from selecting themes that don't play well with mountall, b) let server team drop the graphical splash they don't want; ubuntu-standard currently Recommends: -theme-ubuntu-logo
[17:31] <mdeslaur> slangasek: let me check, hold on a sec
[17:31] <mdeslaur> slangasek: it's installed
[17:32] <mdeslaur> oh, I think I'm getting a kernel oops
[17:32] <mdeslaur> does plymouth fall back if there was en error?
[17:32] <slangasek> oh, splendid
[17:32] <slangasek> if it's an error it's able to catch, yes
[17:32] <mdeslaur> ok, let me investigate a bit
[17:35] <LaserJock> I noticed I've got a fair amount of boot funkiness after the last kernel
[17:40] <mdeslaur> yeah, I've got a kernel oops from an updated thinkpad bios warning...so I guess plymouth is falling back to display the error
[18:04] <jdstrand> slangasek: heh, I see the text mode on my T42 too. I don't have an 'WARNING's in my dmesg
[18:04] <jdstrand> s/heh/hey/
[18:05] <jdstrand> slangasek: I have plymouth-theme-ubuntu-logo installed
[18:05] <slangasek> jdstrand: the only time text mode is ever used is if you 1) boot without 'splash' (and then it's the 'details' plugin), 2) plymouth can't find a working drm or fb interface, 3) you don't have graphical themes installed/configured
[18:09] <jdstrand> slangasek: well, this is a fresh install from yesterday's daily. 1) [    0.000000] Kernel command line: ... quiet splash. 2) radeon/kms/compiz is working now with 19.28, so I drm is ok (at least for X) '[drm] radeon kernel modesetting enabled' 3) plymouth-theme-ubuntu-logo, plymouth-theme-ubuntu-text are installed
[18:09] <mdeslaur> slangasek: so, I have "splash"...my /proc/fb contains "0 radeondrmfb"
[18:09] <jdstrand> slangasek: I am unfamiliar with the 'details plugin'
[18:09] <mdeslaur> slangasek: how do I know if the graphical themes are configured?
[18:10] <jdstrand> $ cat /proc/fb
[18:10] <jdstrand> 0 radeondrmfb
[18:11] <jdstrand> mdeslaur: does it feel to you like we are ganging up on slangasek?
[18:11] <hyperair> hmm, maverick meerkat?
[18:11] <slangasek> jdstrand: the details plugin is the plymouth plugin that shows all the console text, in addition to any prompts that it needs for interaction
[18:11] <slangasek> mdeslaur: ls -l /etc/alternatives/default.plymouth
[18:11] <mdeslaur> jdstrand: yes, but I'm guessing he's gotten used to it by now
[18:12] <slangasek> jdstrand: what precisely do you see at boot time?
[18:12] <slangasek> jdstrand: do you see the "Ubuntu 10.04" text + *s below?
[18:12] <jdstrand> /etc/alternatives/default.plymouth -> /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
[18:12] <mdeslaur> slangasek: that points to /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth for me as well
[18:12]  * slangasek nods
[18:13] <jdstrand> slangasek: yes, but they seem like throbbing dots more than '*'s
[18:13] <jdstrand> (they are teeny though, so maybe I am blind-- I didn't get much sleep last night ;)
[18:13] <slangasek> close enough, we'll attribute the difference to my fallible memory :)
[18:14] <jdstrand> slangasek: does it help if when I see you name in irc all I see are stars?
[18:14] <slangasek> jdstrand, mdeslaur: is cryptsetup installed on these systems?
[18:14] <slangasek> heh
[18:14] <jdstrand> that *may* be unrelated
[18:15] <jdstrand> slangasek: not here, I am currently just using ecryptfs on this laptop
[18:15] <mdeslaur> slangasek: no cryptsetup...I'm not using any of that security crack :)
[18:16] <jdstrand> slangasek: I *do* see other text at the bottom of the screen, and it's line breaks aren't right (familiar stair-stepping), but they fade to almost gone just before gdm comes up
[18:16] <jdstrand> s/it's/its/
[18:16] <slangasek> jdstrand, mdeslaur: please try running: echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/plymouth  && sudo update-initramfs -u, and tell me if the behavior changes
[18:16] <jdstrand> I hate security. It's *always* in the way :P
[18:17] <slangasek> hmm. what version of plymouth, and what version of plymouth-theme-ubuntu-logo, do you have installed?
[18:17] <jdstrand> slangasek: 0.8.1-3 for all
[18:17] <slangasek> ok
[18:18]  * jdstrand reboots laptop
[18:18] <mdeslaur> I've got 0.8.1-4 for all
[18:18] <jdstrand> slangasek: no effect. shall I upgrade and try again?
[18:18] <mdeslaur> slangasek: no effect for me either, still text mode
[18:19] <slangasek> don't see that an upgrade would help
[18:19] <slangasek> is this with the -19 kernel?
[18:19] <jdstrand> 19.28, yes
[18:19] <jdstrand> $ cat /proc/version_signature
[18:19] <jdstrand> Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
[18:19]  * mdeslaur kicks plymouth in the face
[18:19] <slangasek> do you see the same problem if you boot an earlier kernel?
[18:19] <slangasek> I suspect radeondrm regressions
[18:20] <jdstrand> slangasek: is -18 early enough? (probably)
[18:20] <slangasek> maybe?  I don't know, I don't have radeon here to compare with
[18:20] <jdstrand> 19 had the drm radeon fixes for us
[18:20]  * jdstrand tries
[18:20] <LaserJock> this is where you go straight from grub to gdm without getting the boot splash?
[18:21] <jdstrand> LaserJock: no logo, but have some ascii
[18:21] <mdeslaur> slangasek: with -17 kernel, I still have text mode plymouth
[18:21] <jdstrand> slangasek: -18 too
[18:21] <jdstrand> (unsurprisingly)
[18:22] <LaserJock> I got something like that with -intel but only recently
[18:23] <mdeslaur> -16 gets text mode also...
[18:23] <jdstrand> slangasek: I know it did work for me a couple of weeks ago, but I can't be more specific-- like I said, I reinstalled yesterday
[18:24] <jdstrand> LaserJock: yeah, this is recent here too
[18:25] <LaserJock> mine flickers a few times like it's trying
[18:25] <LaserJock> but I end up with text stuff -> gdm
[18:26] <jdstrand> slangasek: fyi, the installer is the same-- text after the first (what I assume to be non-plymouth) bit
[18:34] <slangasek> LaserJock: the question is, what text stuff?  The bug they're having is that they see 'Ubuntu 10.04' in text when they should see the graphical splash; there are also known cases where the splash just never gets around to getting started before X starts
[18:34] <LaserJock> slangasek: ah, ok, that's what I was trying to figure out. Mine is the latter
[18:35] <slangasek> LaserJock: known bug, won't be fixed for lucid because the fix available in that timeframe is at odds with boot performance goals
[18:35] <LaserJock> I see
[18:36] <LaserJock> one of those "if we boot fast enough people won't notice" :-)
[18:36] <jcastro> LaserJock: you're too fast for plymouth dude
[18:36] <LaserJock> jcastro: the problem is booting keeps getting slower :(
[18:37] <LaserJock> earlier in Lucid it wasn't noticable much, but now it's taking a bit more time and I start to wonder if something happened
[18:37] <slangasek> for maverick, we'll tell *grub* to put up the splash, and if plymouth doesn't start before X, no big loss
[18:38] <ScottK> Maverick is going to take me a while.  I keep seeing Tom Cruise flying jets.
[18:38] <elmo> hahaha
[18:40] <LaserJock> ScottK: I keep thinking John McCain
[18:40] <LaserJock> at least it wasn't Rogue ;-)
[18:40] <james_w> with a silent M?
[18:41] <ScottK> I'm also old enough to remember the TV show with James Garner.
[18:41] <LaserJock> ScottK: oh heck yeah
[18:41] <LaserJock> one of the best ever
[18:41] <slangasek> james_w: oh, is that how you pronounce 'mbrola'?
[18:41] <ScottK> Yep.
[18:50] <mdeslaur> ScottK: because of you, I now have "Danger Zone" stuck in my head
[18:50] <ScottK> \o/
[18:50] <LaserJock> mdeslaur: thanks :/
[18:51] <mdeslaur> LaserJock: welcome :)
[18:52] <jcastro> mdeslaur: Is that why you fly the way you do? Trying to prove something?
[18:52] <mneptok> ICEMAN, CHECK SIX!
[18:52] <mdeslaur> jcastro: What's your problem, Kazanski?
[18:53]  * ScottK notes: productivity destruction goal for today met.
[18:53] <jcastro> heh, it's friday.
[18:53] <mneptok> mdeslaur: http://bit.ly/iQYS
[18:54] <mdeslaur> lol
[18:54]  * mneptok invents a new Ubuntu Community rickroll
[19:09] <jdstrand> mdeslaur, slangasek: is there a bug on the radeon/text boot issue?
[19:09] <mdeslaur> jdstrand: not yet (from me)
[19:09] <jdstrand> I don't see a reference in backscroll...
[19:09] <mdeslaur> jdstrand: I was attempting to downgrade plymouth to see where it started
[19:09] <mdeslaur> jdstrand: not a good idea, btw :)
[19:10] <jdstrand> mdeslaur: heh, I was just going to say 'good idea' :P
[19:10] <mdeslaur> jdstrand: newer mountall dies with older plymouth, so be warned :)
[19:11] <jdstrand> mdeslaur: I'm not looking at it atm
[19:11] <jdstrand> mdeslaur: so go with God
[19:11] <jdstrand> :)
[19:11] <jdstrand> of course, I'll complain if it isn't fixed, so don't worry about my feedback ;)
[19:12] <mdeslaur> jdstrand: would you mind opening the bug? my laptop is unbootable to do the ubuntu-bug
[19:12] <jdstrand> mdeslaur: sure
[19:30] <jdstrand> mdeslaur, slangasek: fyi file bug #554143
[19:31] <nigelbabu> james_w, hey got a minute for jcastro and me?
[19:31] <mdeslaur> jdstrand: thanks, I just confirmed it
[19:31] <jdstrand> s/file/filed/
[19:31] <jdstrand> thanks
[19:36] <Sarvatt> jdstrand: I had a similar issue with the text theme showing always on a native res inteldrmfb  in the past week and removing all of the extra themes and just reinstalling those two fixed it
[19:37] <mdeslaur> Sarvatt: which ones are "those two"?
[19:37] <mdeslaur> Sarvatt: plymouth-theme-ubuntu-logo and plymouth-theme-ubuntu-text?
[19:37] <jdstrand> Sarvatt: which extra themes? I've got plymouth-theme-ubuntu-logo and plymouth-theme-ubuntu-text. are there others I should be looking for, or are you suggesting I remove plymouth-theme-ubuntu-text?
[19:37] <Sarvatt> yep
[19:38] <jdstrand> Sarvatt: nm, I see the others, but the are already not installed
[19:39] <Sarvatt> in response to mdeslaur that is, I had solar and spinfinity installed as well and all I did was remove all of the themes and just install those two again and it was fixed afterwards
[19:39] <jdstrand> I could try to reinstall...
[19:40] <Sarvatt> it only happened when I packed plymouth in the initrd though so it might not be related :D
[19:41] <jdstrand> yeah, I already tried to update the initramfs
[19:41] <akk> I'm getting error messages in lucid from /etc/acpi/sleep.sh, missing files in /var/lib/acpi-support.
[19:41] <akk> In karmic those files were part of the acpi-support package, but they aren't in lucid any more (e.g. /var/lib/acpi-support/system-manufacturer)
[19:42] <akk> I'm having trouble figuring out what script is looking for those files.
[19:42] <jdstrand> Sarvatt: didn't work
[19:44] <Sarvatt> do you see the text renderer over vgacon for a split second before the screen changes resolution and then it's offset in the drmfb as well?
[19:48] <jdstrand> I see the underscore flash a few times before the text mode changes. there are 3 distinct flickers, then I see the underscore flash again (still unchanged), then text mode plymouth kicks in
[19:51] <Caesar> Hmm, is it too late to be trying to get a new debmirror into Lucid?
[19:51] <Caesar> I note that what's currently there predates all of the new work done to it
[19:56] <jdstrand> Caesar: you might want to talk to kees since he has been doing the bulk of the work for ubuntu (and I believe upstreamed almost all of it to Debian)
[19:56] <Caesar> jdstrand: thanks, kees, you around?
[19:57] <james_w> nigelbabu: of course
[19:58] <nigelbabu> jcastro, looks likes james is around after all :D
[19:58] <jcastro> james_w: we want to start scheduling patch days, where we collect people to look at pending patches in lp.
[19:59] <jcastro> james_w: when in the cycle do people generally start doing merges?
[19:59] <jcastro> james_w: we'd like to time it around that time
[19:59] <nigelbabu> right now, the date I've come up with in wed, may 5th
[19:59] <nigelbabu> (the day before toolchain release)
[19:59] <james_w> jcastro: pretty much as soon as lucid releases
[20:00] <james_w> it ramps up from when the archive opens
[20:00] <nigelbabu> archive opens on 6th right?
[20:00] <james_w> haven't looked
[20:01] <james_w> sounds about right
[20:01] <james_w> it's never an exact date, but it's pretty quick
[20:01] <nigelbabu> the next thu after release day ...
[20:01] <cjwatson> it's not that rigid
[20:01] <cjwatson> it's whenever we can get enough of the stuff on NewReleaseCycleProcess done
[20:02] <cjwatson> don't believe the release schedule pages on this, they're just a guideline/target this early
[20:02] <jcastro> cjwatson: yeah we just want to do it around the general time
[20:02] <nigelbabu> jcastro, but we dont want the archive open if you ask me
[20:02] <cjwatson> right, I'm just trying to help nigelbabu understand that it isn't a fixed thing
[20:02] <jcastro> ok
[20:02] <nigelbabu> cjwatson, I understand... now :)
[20:03] <nigelbabu> anyway, our first priority would be to send those patches upstream so they can integrate in
[20:03] <nigelbabu> and we can either just backport from the git or just get the new release some time later in the release cycle
[20:06] <nigelbabu> jcastro, so 5th sounds good enough or you want to move it?
[20:06] <nigelbabu> I was hoping to have something done before lucid, so we can brainstorm on either we're we need to change exiting workflow during lucid
[20:07] <ccheney> what was the default version of kde in hardy?
[20:07] <kees> Caesar: hi! yeah, it's behind.
[20:08] <kees> Caesar: upstream didn't take any of the rsync work I did, unfortunately.
[20:11] <kees> Caesar: was there a specific feature you needed from the more recent version?
[20:12] <kees> Caesar: this what needs merging: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455082
[20:16] <nigelbabu> bryceh, might want to take a look at http://pastebin.ubuntu.com/408255/
[20:17] <Caesar> kees: my concerns are that there was a lot of upstream work done last year, and none of that is going to be in Lucid
[20:17] <Caesar> In particular what I'm interested in is the ability to mirror the installer
[20:18] <kees> Caesar: I welcome a merge :)
[20:19] <ion> tjaalton: Yay for the backported InputClass stuff. :-)
[20:19] <Caesar> kees: I just wonder what's better, an already 3 year old debmirror, or a newer one sans your batching changes
[20:19] <ion> My xorg.conf with Wacom calibration. http://gist.github.com/353570
[20:19] <Caesar> It sounds like merging is going to be difficult (but I haven't looked yet)
[20:20] <kees> Caesar: the main issue is that the batching merge isn't easy.  the rest of the fixes I already broke out (though upstream seems to be ignoring) in that above debian bug
[20:20] <kees> Caesar: I haven't had time to get the rsync batching done, but I'd love it if someone could help.
[20:20] <bryceh> nigelbabu, ok what am I seeing?
[20:21] <kees> Caesar: the basic issue is: don't fetch one file at a time with rsync.  :)
[20:21] <nigelbabu> bryceh, list of packages with patches attached
[20:21] <nigelbabu> the number is the total of open bugs with patches per package
[20:21] <Caesar> kees: I'll see what I can do
[20:21] <bryceh> nigelbabu, ok, interesting
[20:21] <nigelbabu> bryceh, jcastro just got the good folks in #launchpad generate it
[20:22] <kees> Caesar: if I didn't have a stack of other work, I'd commit to spending time on it, but that seems unlikely at this point.  :P
[20:22] <bryceh> nigelbabu, fwiw the list of patches I'm working through is at http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/patches.html
[20:22] <Caesar> kees: Yeah yeah, join the club :-)
[20:22] <bryceh> nigelbabu, it's nicely been growing shorter and shorter :-)
[20:23] <nigelbabu> bryceh, oh great.  thats one team on top of their patches
[20:23] <kees> Caesar: heh :)
[20:23] <nigelbabu> bryceh, so we'll just skip the X bugs in review queue
[20:24] <bryceh> nigelbabu, strangely, it shows more patches than https://edge.launchpad.net/~ubuntu-x-swat/+patches does, but I think deryck has been looking into that
[20:24] <bryceh> nigelbabu, yeah the reason xserver-xorg-video-openchrome is at the top of the list is because upstream posts patches to our launchpad queue for folks to test
[20:24] <nigelbabu> bryceh, thats nice :)
[20:24] <nigelbabu> bryceh, I like https://edge.launchpad.net/~ubuntu-reviewers/+patches
[20:25] <bryceh> I found that it's not the case that they want those patches *in* ubuntu, they just want users to test them, then they can decide to include them upstream and we get them next time we sync
[20:25] <nigelbabu> they're using as lab rats? :D
[20:25] <bryceh> so a totally different patch workflow than everything else.  But it works for them I gather
[20:25] <jcastro> that's pretty handy though
[20:25] <bryceh> nigelbabu, that does look nice
[20:26] <nigelbabu> its the new code I guess since I see that only in edge
[20:28] <slangasek> jdstrand, mdeslaur: may be useful to boot with 'plymouth:debug=file:/var/log/plymouth-debug.log' and grab that log file (if plymouth succeeds in outputting it)
[20:36] <mdeslaur> slangasek: thanks, will try once laptop is reinstalled
[20:37]  * jdstrand will try now
[20:37] <mdeslaur> jdstrand: argh, you're always one step ahead :)
[20:38] <jdstrand> mdeslaur: heh, will you stepped 'ahead' of me by downgrading plymouth
[20:40]  * bjf is taking a break, my dad just walked in
[20:40] <jdstrand> slangasek: the text theme did not display with that invocation. is that expected?
[20:41] <jdstrand> this may be it:
[20:41] <jdstrand> ply_open_module:Could not load module "/lib/plymouth/renderers/x11.so": /lib/plymouth/renderers/x11.so: cannot open shared object file: No such file or directory
[20:41] <jdstrand> slangasek: ^
[20:42] <slangasek> jdstrand: unless you're setting 'export DISPLAY=:0.0' in your initramfs, that shouldn't matter :)
[20:42] <slangasek> jdstrand: you could try installing plymouth-x11 though, just to see what changes
[20:43] <slangasek> but - the text theme didn't display? what did you get instead, just text output?
[20:43] <jdstrand> slangasek: I got what looks like the output of the plymouth debug log. like it tee'd
[20:43] <jdstrand> slangasek: I have the debug log, shall I paste or attach to bug?
[20:44] <slangasek> jdstrand: attach to bug plz
[20:45] <jdstrand> slangasek: fwiw, plymouth-x11 is already installed
[20:45] <slangasek> jdstrand: oh, well, hum
[20:46] <slangasek> jdstrand: do you have /usr on a separate partition?
[20:46] <jdstrand> slangasek: nope. / and /home
[20:46] <slangasek> do you still have the FRAMEBUFFER=y line in /etc/initramfs-tools ?
[20:47] <jdstrand> $ cat /etc/initramfs-tools/conf.d/plymouth
[20:47] <jdstrand> FRAMEBUFFER=y
[20:47] <slangasek> yeah; so plymouth is in the initramfs, and we don't ever copy x11.so over
[20:47] <slangasek> 'cause if you've got an X server in your initramfs, yer doin it rong
[20:49] <jdstrand> slangasek: log added to bug
[20:50] <slangasek> ta
[20:51] <slangasek> mdeslaur: what's your radeon chip?
[20:51] <slangasek> I'm inclined to believe this is chip-specific, given that we've got a number of positive radeon tests from beta1
[20:52] <mdeslaur> slangasek: same, but 16mb
[20:52] <mdeslaur> slangasek: it used to work :(
[20:54] <jdstrand> yeah, it was workign when manoj gave it back to me, so that was packages from a couple weeks ago and a -17 with backported drm that he added (but mdeslaur demonstrated it is not kernel specific)
[20:54] <Sarvatt> actually, the drm renderer for plymouth wont work with a 8bpp framebuffer anyway will it?
[20:54] <Sarvatt> radeon uses a lower color one for cards with <=16MB ram
[20:55] <slangasek> jdstrand, mdeslaur: [./plugin.c]                                  query_device:Visual is FB_VISUAL_PSEUDOCOLOR; not using graphics
[20:55] <slangasek> kernel done you wrong
[20:56] <mdeslaur> slangasek: what's the difference between the drm.so renderer and the frame-buffer.so renderer?
[20:58] <Sarvatt> the framebuffer uses up a big chunk of the video ram always and its alot bigger if its the normal 24bpp mode, the alternative is not having enough video ram to do just about anything on the desktop if you want a pretty splash just for the few seconds during boot
[21:01] <slangasek> mdeslaur: one uses libdrm, the other uses /dev/fb0
[21:01] <mdeslaur> slangasek: so how come it's failing with drm.so, shouldn't that work?
[21:01] <slangasek> mdeslaur: the drm renderer is only used when you have more than one video output
[21:01] <slangasek> mdeslaur: plug in an external monitor and see if it works? :)
[21:01] <mdeslaur> ah, ok
[21:02] <Sarvatt> ^on nouveau and ati, intel doesnt have that limitation
[21:02] <slangasek> right
[21:03] <mdeslaur> hmm...I wonder what changed
[21:04] <Sarvatt> i think it was the -16 kernel that brought in the change to where drmfb's for low memory radeon GPU's use a lower color mode
[21:04] <Sarvatt> can't you bump the video ram in your bios?
[21:05] <Sarvatt> (or is it not integrated) sorry don't know which gpu you have
[21:05] <mdeslaur> radeon 7500
[21:07] <mdeslaur> okay, if it's because of low video memory, I guess we'll live with it
[21:08] <Sarvatt> whats the pci id?
[21:09] <mdeslaur> Sarvatt: 1002:4c57
[21:09] <mdeslaur> jdstrand: what's your pci id?
[21:09] <Sarvatt> ah not an IGP then :(
[21:09] <mdeslaur> nope
[21:11] <mdeslaur> ah, jdstrand's has the same pci id, but he has 32mb
[21:15] <Sarvatt>         /* select 8 bpp console on RN50 or 16MB cards */
[21:15] <Sarvatt>         if (ASIC_IS_RN50(rdev) || rdev->mc.real_vram_size <= (32*1024*1024))
[21:15] <Sarvatt>                 bpp_sel = 8;
[21:15] <Sarvatt> is it me or is that comment wrong and its using 8bpp for 32mb too? :D
[21:17] <Sarvatt> ah yep http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=47381156a8f0d793bacfa346cc4cc515399525f7
[21:21] <mdeslaur> yeah, the comment is wrong :)
[21:21] <mdeslaur> so <=32 Mb
[21:24] <mdeslaur> Thanks Sarvatt for the info, I've updated the bug
[21:25] <mdeslaur> so, it's not really an issue
[21:36] <slangasek> mdeslaur: it's not a release-critical issue, but this is clearly a suboptimal outcome
[21:37] <mdeslaur> yes
[21:37] <jdstrand> slangasek: yes, it is, especially since I still remember when it was working :)
[21:38] <mdeslaur> jdstrand: memories fade :)
[21:38] <jdstrand> slangasek: is there a workaround? do we expect it to get fixed?
[21:39] <slangasek> honestly, I'm not sure why Keybuk implemented the VGA16fb support as a separate renderer, instead of adding generic support to the fb renderer for downstepping the bit depth
[21:39] <jdstrand> well, radeon 7500 users (of which there are many), will have a nice usplash in all previous releases and then drop to text
[21:39] <slangasek> jdstrand: not likely to get fixed for release
[21:39] <jdstrand> :\
[21:39] <slangasek> unless you persuade the kernel team that this change was wrong?
[21:40] <jdstrand> I have no background or authority to say it is wrong
[21:40] <mdeslaur> and sacrifice desktop memory?
[21:40] <jdstrand> I can only say the outcome is poor
[21:40] <slangasek> you could install fglrx, then you'd have the VGA fb :-P
[21:40] <jdstrand> mdeslaur: this is what fixed our bug?
[21:40] <slangasek> (I don't recommend this, that looks even worse than the text right now :)
[21:40] <mdeslaur> slangasek: nice try, but fglrx doesn't support radeon 7500 any more :)
[21:41] <mdeslaur> jdstrand: it probably helped, yes
[21:41] <slangasek> heh
[21:41] <jdstrand> slangasek: well, taking the fact that I bought a 7500 to avoid the proprietary driver in the first place, I don't think fglrx supports this card anyway
[21:41] <slangasek> ok, you could boot with a vga= option
[21:41] <mdeslaur> oh!
[21:42] <slangasek> but that implies using a 32bpp fb, so I don't know how that interacts with your desktop problem
[21:42] <slangasek> (OTOH, if you pick a lower res fb, it's less of an issue than when it's at native res?)
[21:43] <mdeslaur> jdstrand: I know a work-around: doesn't your wife have a birthday coming up? :)
[21:43] <mcurrington> Who maintains the package irssi? In apt-cache show it tells me "Ubuntu Core Developers"
[21:43] <jdstrand> heh, sure she does, but not her business partner ;)
[21:44] <mdeslaur> jdstrand: let me know if you try with vga=
[21:45] <jdstrand> I'm trying to conjure up the magic for 1400x1050... it's been awhile
[21:45] <slangasek> alternative to vga= if you're using grub2 is to try gfx_payload=keep
[21:45] <slangasek> + setting a res in the grub config
[21:46] <jdstrand> btw, I'm fine with a workaround...
[21:46] <jdstrand> slangasek: gfx_payload-- is that kernel command line or grub's config?
[21:48] <jdstrand> nm, found it
[21:51] <cjwatson> if jdstrand is using a KMS graphics driver, then gfxpayload=keep will break virtual consoles, I believe
[21:52] <slangasek> ah
[21:52] <slangasek> nevermind then :)
[21:53] <slangasek> jdstrand: in that case, it's s/linux/linux16/ s/initrd/initrd16/ and add the vga= option; I have no idea about the maintainability of that
[21:54] <cjwatson> you'd probably have to edit /etc/grub.d/10_linux to avoid screwing yourself over on every update-grub
[21:54] <cjwatson> slangasek: FWIW I talked with pkern, I'm going to go with libparted0debian1 as you suggested.  I think I'll wait until ries comes back though
[21:55] <cjwatson> now that I have the odbcinst1debian1 precedent
[22:05] <jdstrand> linux16?
[22:05]  * jdstrand googles
[22:09]  * jdstrand gets it now
[22:14] <jdstrand> slangasek: booting without splash is nearly acceptable due to the fast boot
[22:14] <jdstrand> slangasek: seems some console output is still leaking through though...
[22:14] <jdstrand> (ie with just quiet)
[22:15] <jdstrand> bunch of 'Broken pipe' messages
[22:21] <slangasek> yes, with 'quiet' plymouth shows you console output
[22:21] <slangasek> (whatever console output there is)
[22:22] <highvoltage> anyone know perhaps (or have an idea) when we'll have daily builds again?
[22:36] <chrisccoulson> does anybody know what happened to this: https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa/+build/1596874 ?
[23:00] <kees> chrisccoulson: whoa.  I would ping lamont.
[23:01] <jpds> chrisccoulson: The machine died?
[23:02] <jpds> Actually, the upload log is interesting.
[23:11] <lex79> slangasek: in gdm.upstart there's "exec gdm-binary $CONFIG_FILE" and in kdm.upstart only "exec kdm", that change should be merged into kdm.upstart ?
[23:12] <slangasek> lex79: not unless you know of something that sets that variable for kdm
[23:13] <lex79> ok
[23:18] <wgrant> chrisccoulson: That's some DB glitch -- it looks like something went strange just after the upgrade finished. Hit Retry.
[23:18] <wgrant> That's no code bug.
[23:19] <chrisccoulson> wgrant - ok, thanks. i'll retry that now
[23:26] <lex79> slangasek: I merged your changes to kubuntu-members, thanks
[23:26] <slangasek> lex79: thank you!
[23:27]  * lamont grumbles at whoever gave back schroot/armel
[23:28] <slangasek> lamont: which time?
[23:28] <slangasek> 13:24 < doko__> hmm, who did give back schroot on armel? did give it back just 1h ago ...
[23:28] <lamont> well, it's knocking over the pegatrons
[23:28] <lamont> so I killed it with prejudice
[23:29] <lamont> speaking of which, could you (I'm EOD and busy ish) block glib2.0/sparc in PaS for me?
[23:29] <lamont> tired of stabbing sparc
[23:29] <lamont> and yeah, glib2.0 got both of them again
[23:30] <lamont> so nm... I'll deal with it when I get back to the computer in a couple hours/.
[23:30] <slangasek> hum, added to PaS, but why's it killing sparc?
[23:31] <lamont> dunno - there's a bug against glib2.0 for it
[23:31] <ScottK> That would be me retrying glib2.0 so I can get kdebindings to build.  I guess  we'll need some arch specific magic to get around that one.
[23:31] <lamont> on the bright side, we now have the log we can paste into the bug, on both sparc
[23:31] <lamont> buildds
[23:32] <ScottK> Is there any hope that sparc will actually work this release?
[23:32] <slangasek> if it's crashed 2 buildds, that counts as 'confirmed', right
[23:32] <lamont> big hint for would-be-helpful people who can give-back packages: if it looks like the build tree got nuked out from under the build?  there's a reason
[23:32] <lamont> slangasek: both sparc buildds, every upload since the last one that worked
[23:33] <ScottK> lamont: Is it time to think about sparc joining hppa?
[23:33]  * lamont continues playing dice with launchpad trying to put the pegatrons on manual so he can unleash schroot on a bbg3 instead
[23:34] <lamont> I choose not to join that discussion
[23:34] <doko__> lamont: ok can do that
[23:34] <lamont> doko__: do what?
[23:34] <doko__> trying to put the pegatrons on manual (gourd is the only new one?)
[23:35] <lamont> buttercup, gourd, and cushaw are bbg3
[23:35] <lamont> my issue is that 90% of the time, +edit gives me a timeout
[23:35] <lamont> in about 3 minutes, I'm gonna use a rock
[23:35] <lamont> there. jackfruit finally manual
[23:36] <doko__> ahh ...
[23:36] <lamont> ok.  now giving back schroot again
[23:37] <lamont> doko__: fwiw, when it looks like the build tree got ripped out from under the build, the most likely explanation is that I logged into the buildd and did exactly that, to kill the build hard before it did worse things
[23:37] <lamont> as in, please check before giving those back
[23:38] <doko__> lamont: hmm, I did check that the build log was from February and started ...
[23:38] <lamont> doko__: interesting
[23:38] <doko__> maybe just coincidence working at the same time
[23:38] <lamont> what happens in these cases is this:  build starts, kills the machine, and launchpad says "hrm... buildd went away, lets try it on another one"
[23:39] <lamont> lather, rinse, repeat
[23:39] <lamont> the build log, of course, disappears in that
[23:39] <lamont> when we add in that the pegatrons (and bbg3) boards are not remote rebootable, having a build go through and knock them all over is really sucky
[23:53] <lamont> doko__: I'll be afk for about an hour and then checking on buttercup.  then I'll make a decision about whether or not to throw the other pegatrons back into the pool