[00:16] <YokoZar> Why does my launchpad PPA keep an all time failure log for me.  Did I really need to know that I had 424 successful uploads and 37 build failures?
[00:16] <YokoZar> This is going to turn into a vanity stat very soon
[00:16] <crimsun> ...or you could not consider it a mark of vanity.
[00:17] <YokoZar> crimsun: If launchpad published userid numbers I'd use that as a mark of vanity too
[00:28] <jfb_h2o> is there a reference for how to create a package like science-engineering for an organization to use for deployment?
[00:57] <jdong> kees: *defers to siretart* probably in debian's VCS?
[00:58] <kees> cool
[01:05] <psusi> damnit!  shit's complicated.
[01:21] <mdziczkowski> hello
[01:22] <mdziczkowski> are here any developers from Ubuntu 10.04 ?
[02:22] <slangasek> superm1: mythtv 0.23.0+fixes24158-0ubuntu2 - no bug numbers referenced in this log?  what's critical about making the shutdown/reboot commands *not* configurable?
[02:26] <slangasek> superm1: also, bug #550100 has been targeted to 10.04; if that's correct, presumably we should wait for that to land as well so we only have to build it once?
[03:14] <slangasek> ArneGoetje: export generated empty gv language packs again; I've rejected them from the new queue
[04:27] <YokoZar> oh goody gwibber is crashing on startub
[06:39] <hdon> when was the last time istanbul worked on ubuntu?
[06:40] <hdon> it seems that it's been like 8 months, and i've tried on a bunch of different ubuntu installs on several machines with no success
[06:40] <hdon> it always freezes hard
[06:40] <hdon> i filed a bug a loong time ago
[06:40] <hdon> very shameful. screencapture is important for the ubuntu generation of computer users
[06:48] <hyperair> is it? i've only used it like.. once?
[07:34] <gartral> hello all, i figured here is the best place to post this: ubuntu 10.04 is NOT supplying proper power over usb, as my droid no longer charges after upgrading to the RC
[07:37] <gartral> also the tigerjet device known as magicjack causes x too fail on load if the device is plugged in when i boot lucid
[07:41] <mantiena> hi all
[07:42] <mantiena> ev: Hi, thanks for updating ubiquity translation after Release Candidate - now Lithuanian users will see correct and easy to understandable translation without errors
[07:43] <mantiena> maybe someone knows if today will be new daily build at cdimage.ubuntu.com/daily-live/ ?
[08:15] <mantiena> nobody knows if today will be new daily build at cdimage.ubuntu.com/daily-live/ ?
[08:18] <Mirv> ccheney: could you push your OOo to bzr so that I could see the code changes in the last upload?
[08:57] <mantiena> Maybe someone knows if today will be new daily build at cdimage.ubuntu.com/daily-live/ ?
[11:53] <egalia> hey peops
[11:54] <egalia> where should I look for the final artwork for lucid?
[11:55] <egalia> would like to print some flyers for an upcoming lucid lynx party.
[12:00] <egalia> https://wiki.ubuntu.com/Brand
[12:00] <egalia> thx
[12:00] <hyperair> crimsun: are pulseaudio sinks always physical devices?
[12:00] <egalia> bye
[12:01] <persia> hyperair: No: see http://pulseaudio.org/wiki/Modules for a list of sink types.
[12:02] <hyperair> persia: i see. that makes things harder..
[12:02]  * hyperair should probably start with filing a bug
[12:02] <persia> hyperair: What are you trying to do?
[12:03] <hyperair> persia: see, if you have multiple pulseaudio instances running on the same computer... and you put the computer to sleep.. the hook will record the state of, and mute each sink.
[12:04] <ogra_cmpc> i dont think you can put the computer to sleep if multiple people are logged in
[12:04] <hyperair> ogra_cmpc: can't you?
[12:04] <hyperair> ogra_cmpc: well in my case i had a gdm session and my own session.
[12:04] <ogra_cmpc> i remember lamont complaining about that a week ago or so
[12:04] <hyperair> so there was a gdm pulseaudio, and my own pulseaudio session.
[12:04] <hyperair> the problem was... the sinks on both instances were both mapped to the same physical device
[12:04] <ogra_cmpc> yeah, thats different
[12:05] <hyperair> so it went like this: it muted the sink of gdm's pulseaudio, and recorded that state. then it queried the state of my pulseaudio's sink, and then also muted it.
[12:05] <hyperair> the problem is: regardless of the state of the sink, it is now muted after recording gdm's pulseaudio's state.
[12:05] <hyperair> when resuming, the states are restored in the same order
[12:05] <ogra_cmpc> yeah, sounds like a bug
[12:05] <hyperair> i know, i wrote that script >_>
[12:08] <persia> hyperair: So, you need to find a way to serialise and track each instance separately.
[12:08] <hyperair> persia: yep.
[12:09] <hyperair> persia: but i don't have the time to do it now. i wonder if it counts as a SRU..
[12:10] <persia> hyperair: It needs fixing anyway.  Fix it as soon as you can: if you get it before release, ask the Release Team if it can be in lucid.  If it's after, ask the SRU team if it can be backported.  Either way, make sure it's fixed in maverick.
[12:12] <hyperair> persia: no problem.
[12:13] <hyperair> persia: it's really a corner case though, so i wonder what priority to assign it
[12:17] <persia> Ask for guidance in -bugs, really.  I'd probably call it "Medium" offhand, but I'm not entirely confident, and not a good candidate to have an opinion since I mute audio all the time, and rarely suspend.
[12:45] <hyperair> weird, is launchpad's email interface not working?
[12:52]  * hyperair kicks launchpad
[12:57] <hyperair> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/569395 for anyone who was listening earlier
[13:23] <directhex> can we release note the "proprietary NVIDIA driver nvidia-current installed on non-nvidia systems during upgrade which previously had libmyth-0.22-0 on them" issue?
[13:24] <directhex> had it happen again, on wife's netbook this time
[13:26] <directhex> well, either release note it, or actually add a conflicts/replaces on nvidia-185-libvdpau in libvdpau1, since that's the cause?
[14:50] <ScottK> directhex: open a bug task against the ubuntu-release-notes project and provide proposed text for the note.
[16:26] <simon-o> james_w, the lucid branch for system-config-printer is outdated. https://code.edge.launchpad.net/~ubuntu-branches/ubuntu/lucid/system-config-printer/lucid Do you have an idea why?
[16:27] <james_w> simon-o: package-import.ubuntu.com/status/system-config-printer.html
[16:27] <james_w> so it's hit a bug in the importer and so failed to import the most recent versions
[16:29]  * james_w heads out
[16:29] <simon-o> james_w, I see. thanks
[17:11] <bgamari> How exactly does mountall fit into the boot process?
[17:11] <bgamari> All but one of the kernels on my Lucid test machine will not boot
[17:11] <ion> It does the fsck, mount and swapon when devices appear.
[17:11] <bgamari> Instead they get stuck waiting for mountall
[17:11] <bgamari> I can't seem to coax any useful debugging output from it
[17:12] <bgamari> It emits upstart events as devices come up (i.e. root partition)
[17:13] <bgamari> ?
[17:13] <ion> I take it your kernels are new enough (≥ 2.6.32 IIRC) and not missing important configuration options?
[17:13] <bgamari> The only kernel that does work is my self-built 2.6.34-rc
[17:13] <bgamari> Even the -ubuntu kernels are failing
[17:15] <ion> Please provide the --debug output from mountall with a working kernel and a failing ubuntu kernel.
[17:15] <bgamari> ion, alright, give me a few minutes
[17:16] <bgamari> ion: It's --verbose, not --debug?
[17:16] <bgamari> vice versa rather
[17:16] <bgamari> --debug doesn't seem to be documented
[17:17] <ion> Add --debug >/dev/mountall.log 2>&1 to the ‘exec mountall ...’ line in /etc/init/mountall.conf
[17:18] <bgamari> yep
[17:18] <ion> Dunno why --help doesn’t list --debug.
[17:18] <bgamari> It would be helpful if --debug were reported in --help
[17:18] <bgamari> yeah
[17:19] <bgamari> I can open a bug for that if that would help
[17:19] <bgamari> I think libnih handles --help
[17:20] <bgamari> ion: I just realized, piping the output to a file might not be the beste idea
[17:20] <bgamari> I won't be able to read the file in the case of the non-working kernels
[17:20] <bgamari> I can put a serial console on the machine
[17:21] <ion> mkay, nih/option.c says --debug is deliberately hidden from --help.
[17:22] <bgamari> arg
[17:22] <ion> Do as you seem best, but you could always use sulogin.conf from http://upstart.ubuntu.com/wiki/OMGBroken to get a command line.
[17:22] <ion> deem
[17:26] <kirkland> is it really, actually impossible to boot 10.04 with plymouth entirely disabled?
[17:27] <akk> kirkland: I've tried moving plymouth* out of /etc/init on two machines and it made no noticeable difference.
[17:27] <akk> both machines still boot fine, though I haven't tried with a gnome desktop after that
[17:31] <ScottK> kirkland: I think it's best described as not reliable.  plymouth handles some I/O serialization tasks (IDK the specifics), so it may work, but shouldn't be dependend on.
[17:31] <ScottK> </parrot mode>
[17:35] <kirkland> ScottK: hmm, okay;  that's make pure text-style server consoles impossible now?
[17:35] <ion> akk: Just wait until mountall really, really needs to interact with you. :-P
[17:35] <bgamari> ion: Well, it actually seems thata my hypothesis was wrong
[17:36] <bgamari> it's not mountall
[17:36] <bgamari> It seems I don't even get to mountall
[17:36] <bgamari> The working configuration gave me quite a bit of output
[17:36] <ScottK> kirkland: That's my recollection of how I've seen it explained.  IDK the details.
[17:36] <ScottK> I'm not saying you're at all wrong.
[17:36] <bgamari> the dead configuration doesn't produce much of anything
[17:37] <ion> bgamari: Did you try sulogin.conf? Do you get a command line in a virtual console?
[17:38] <bgamari> I do get a command line
[17:38] <bgamari> yes
[17:38] <bgamari> and root has been mounted
[17:39] <ion> Does mountall start at all?
[17:39] <bgamari> I really don't think so
[17:39] <bgamari> I didn't get any debugging output
[17:39] <ion> /dev/mountall.log doesn’t exist?
[17:41] <bgamari> one moment
[17:41] <bgamari> I wasn't redirecting to a file
[17:46] <bgamari> ion: Nope, mountall.log doesn't exist
[17:47] <ion> Ok, some job that has ‘start on starting mountall’ seems to block mountall then.
[17:48] <bgamari> ion, alright
[17:48] <ion> hwclock, plymouth, ureadahead on my system. Try commenting out the ‘start on...’ line from each job that starts on ‘starting mountall’. If that lets mountall start, try reverting that change one by one.
[17:49] <akk> Are there any programs for showing the upstart event tree, or for asking questions like "what jobs might block mountall" ?
[17:49] <ion> grep 'starting mountall' /etc/init/*.conf
[17:50] <akk> Works as long as it's only 1 level deep.
[17:50] <ScottK> persia: Congratulations.  You resolved the last non-sparc depwait in Main.
[17:50] <bgamari> akk, that would be nice
[17:50] <akk> bgamari: I've been idly thinking about trying to write something like that but was hoping it already existed. :)
[17:54] <akk> The upstart docs are still pretty sketchy, though.
[17:58] <bgamari> ion, akk: the problem was one of hwclock, plymount or ureadahead
[17:59] <bgamari> Enabling hwclock still works
[17:59] <bgamari> plymouth*
[18:01] <bgamari> the problem appears to be plymouth
[18:01] <ccheney> Mirv: ok will get that done soon
[18:02] <bgamari> ion, akk, yep, reverting plymouth.conf makes the machine unbootable again
[18:06] <ion> I’m not familiar enough with plymouth to give specific debugging tips, but you might try e.g. strace -s100000 -f -o/dev/plymouthd.strace /sbin/plymouthd --mode=boot --attach-to-session.
[18:06] <ion> Anyone here familiar with the inner workings of plymouth?
[18:07] <ion> plymouthd --mode=boot --attach-to-session --debug --debug-file=/dev/plymouthd.log might also be helpful.
[18:18] <bgamari> ion: alright
[18:21] <bgamari> ion: well, not much happened
[18:21] <bgamari> plymouth took control of the VT after producing some pretty generic debugging output
[18:22] <bgamari> mostly about it deciding whether or not to log
[18:23] <ion> Keybuk and slangasek have done a lot of work on plymouth, they should be able to help debug the issue.
[18:23] <bgamari> ion: alright
[18:23] <bgamari> thanks for your help!
[18:23] <bgamari> slangasek: ping
[18:42] <crimsun> hyperair: no, not always.
[18:43] <crimsun> hyperair: also, regarding that bug, the real fix is (I think, noted, but I'm not sure given my phone's acting oddly) to remove the pm-utils hook altogether
[18:44] <ion> bgamari: You should report a bug with all the information you have so far, asking for instructions for debugging further.
[18:55] <hyperair> crimsun: remove the hook? are all the audio drivers fixed well enough for it to be removed?
[19:04] <bgamari> Will Lucid really make it's scheduled release date?
[19:04] <bgamari> its*
[19:04] <bgamari> If I'm not mistaken, it's set to release in less than a week
[19:05] <hyperair> why wouldn't it?
[19:06] <bgamari> Yet several pretty important bugs remain unsolved (the IPv6 name resolution issue, a few boot issues I've heard people experiencing, the GEM memory leak was only solved a few days ago)
[19:06] <bgamari> just seems like there's been a lot of flux for being so late in the cycle
[19:06] <hyperair> there's an IPv6 issue?
[19:06] <hyperair> i haven't heard any boot issues
[19:06] <ScottK> As Ubuntu releases go, this is pretty calm.
[19:07] <hyperair> lol
[19:07] <bgamari> hyperair: https://bugs.launchpad.net/fedora/+source/glibc/+bug/417757
[19:07] <bgamari> ubottu: The Fix released is for Karmic
[19:08] <bgamari> oops, wrong nick
[19:08] <bgamari> hyperair: Still no fix for lucid
[19:08] <bgamari> yet we're in freeze
[19:08] <crimsun> hyperair: no, hence the comment in the bug report
[19:09] <bgamari> I'm having trouble digging up the boot issue
[19:09] <crimsun> hyperair: we discussed this upstream; ultimately we want the suspend notification over dbus instead of using pm-utils hooks.
[19:09] <hyperair> crimsun: hmm interesting. looks like there are a lot of things which want suspend notification over dbus, but upower isn't moving.
[19:10] <hyperair> that makes.. pulseaudio, gnome-screensaver, gnome-power-manager..
[19:11] <crimsun> lennart usually gets his way :)
[19:11] <hyperair> who's lennart?
[19:11] <crimsun> the creator of avahi and pulseaudio
[19:11] <hyperair> oh cool
[19:11] <hyperair> well, if he gets upower to budge, everyone will be happy =)
[19:12] <ScottK> bgamari: I don't think that ipv6 bug is valid for Lucid.  When I ping a new site via ipv4 I get an almost instant response.
[19:12] <hyperair> ScottK: i think you need a sucky DNS server.
[19:13] <ScottK> It was via a D-Link router, so I suspect that would qualify
[19:13] <ScottK> but OK
[19:13] <bgamari> ScottK: yeah, our network on campus is administered by a whole department of idiots
[19:13] <bgamari> and it is absolutely abysmal
[19:14] <bgamari> In Karmic it was fine
[19:14] <hyperair> bgamari: oh you too? =p
[19:15] <bgamari> hyperair: It seems to be a pattern
[19:15] <hyperair> we have a bunch of idiots who occasionally decide that the network needs to be restarted, thereby bringing the whole university network crashing down.
[19:15] <bgamari> Universities seem to have an aversion to hiring intelligent, competent people for IT roles
[19:15] <hyperair> agreed.
[19:16] <hyperair> "okay, we'll put your server in the DMZ." "oh hey all my ports are still blocked. only 80 seems to be opened." "we recommend that you do not host ___ and ___ and __ services"
[19:16] <hyperair> so that's what a DMZ means -- opening port 80.
[19:16] <bgamari> hah
[19:17] <bgamari> well, ath9k seems to be completely broken on my machine with the stock kernel
[19:17] <bgamari> locks up the machine hard
[19:18] <ScottK> Did you try linux-backports modules?
[19:18] <bgamari> A deadlock perhaps, Sysrq-W does nothing but output "SysRq : Show Blocked State
[19:18] <bgamari> ScottK: Nope, not yet
[19:18] <bgamari> I'll give it a try
[19:18] <ScottK> That may not be the exact package name.
[19:18]  * ScottK can never remember
[19:18] <bgamari> yeah, I know what you mean
[19:21] <akk>  /sbin/alsa-utils in lucid has comments explaining how to disable storing on an sysv-rc system, but not on upstart.
[19:21] <hyperair> ScottK: tab completion ftw
[19:22] <akk> The upstart file has start on starting rc RUNLEVEL=[06] and always calls exec /sbin/alsa-utils stop
[19:22] <akk> which looks like it's calling stop on boot, and nothing on shutdown, but actually it seems to be saving on shutdown and restoring on boot.
[19:23] <akk> I'm having trouble understanding how that works from the docs I've found (man 5 init and the upstart getting-started guide).
[19:28] <crimsun> akk: err?
[19:29] <crimsun> akk: if you want to disable storing, either move the upstart job out of the way, or comment out the invocation in the stop target
[19:30] <akk> crimsun: There doesn't seem to be a stop target. That's what I'm trying to understand -- why it gets called on shutdown at all.
[19:30] <akk> (and also how alsa-utils ever gets called with anything besides "stop" on startup)
[19:30] <crimsun> akk: I'm quite certain that /sbin/alsa-utils does have a stop target.
[19:30] <crimsun> line 376
[19:31] <akk> Yes, but it also has a start target. Don't they do different things?
[19:31] <crimsun> yes, and the start target is only invoked from the udev rule.
[19:31] <akk> Ah! So the upstart job is only for shutdown, not for startup?
[19:31] <crimsun> that's correct.
[19:32] <akk> And "start on starting rc RUNLEVEL=[06]" happens any time runlevel is changed?
[19:33] <crimsun> no, only when entering runlevels 0 or 6
[19:33] <akk> (so in this shutdown case, going from 2 to 0)
[19:33] <akk> Oh, right, sorry, I was thinking there was a dash there.
[19:34] <akk> Is that the recommended way to do something at shutdown -- "starting rc RUNLEVEL=[06]" ?
[19:35] <crimsun> "it depends." For that particular use case, it needed to be serialized, so starting rc RUNLEVEL is correct
[19:40] <akk> I'd like to understand this stuff better, and understand why starting rc is better here -- but I don't want to be a pest (you've already answered my main questions).
[19:41] <akk> If you have time to explain it (or know of good docs to read) I'd appreciate it, but if you don't have time, I quite understand.
[19:50] <jdong> *giggles* lucid RC's installer was at 884% of contacting NTP server
[19:51] <jdong> I'm using VMWare's magical autoinstaller though, so I don't know whose glitch that is, at ubiquity's startup
[20:06] <Sarvatt> jdong: if you're using the vmware autoinstaller be aware you'll probably have to mess with the xkb settings since it sets screwed up ones - https://bugs.edge.launchpad.net/ubuntu/+source/console-setup/+bug/548891
[20:06] <jdong> Sarvatt: yup, just did that.
[20:06] <jdong> thanks for the heads up
[20:07] <Sarvatt> pointed it out to a vmware guy yesterday and he said he can't reproduce with the beta versions - http://communities.vmware.com/community/beta/ws
[20:08] <jdong> ok so probably their beta version no longer uses SKIP
[20:36] <superm1> slangasek, it's a problem that we discussed in #ubuntu-mythtv-dev due to a change upstream in the behavior that broke upgraders.  re bug 550100, the fix is targetted, but that patch still isn't blessed - but we're hoping it will make it and be good to go
[20:36] <superm1> it causes some lipsync problems still
[22:06] <hdon> hi all. where is the repository for this project? https://launchpad.net/game
[22:12] <kklimonda> lp:game ?
[22:15] <hdon> kklimonda, lp?
[22:15] <hdon> that doesn't look like a url to me :(
[22:15] <rafl> hi there. i've wrote a couple of patches for the linux kernel to fix the issues #418282 and #512192 and put them in the elantech_fw41 branch at git://github.com/rafl/linux-2.6.git - however, i don't particularly feel like creating a launchpad account just to comment on the tickets. it'd be much appreciated if one of you guys, who presumably already have an account, would add that repo url to the tickets.
[22:16] <kklimonda> hdon: you can use it with bzr like bzr clone lp:game
[22:18] <hdon> kklimonda, oh... i'm very unfamiliar with bzr.. and it seems kind of like magic to me that "lp:game" could actually reference something on the internet!
[22:24] <kklimonda> hdon: you can use http://launchpad.net/game instead - the lp: is just a shortcut for the convienience of people using lp every day.
[22:48] <Brimstones> Some dick has banned my ip in #ubuntu
[22:50] <Brimstones> Going back to dumbing myself up and watching some tv then.
[22:52] <Brimstones> Hmm, ill just change ip and then do both things! :)
[22:54] <Brimstones> There
[23:23] <hdon> kklimonda, ahh
[23:27] <hdon> that's a cool feature