[00:00] <slangasek> TheMuso: no, only mounting LVs if you're using non-canonical names for them in /etc/fstab
[00:00] <TheMuso> oh ok
[00:01] <LaserJock> hmm, so software-store is going to replace gai for Karmic?
[00:01]  * Laney stabs launchpad
[00:01] <Laney> what's the query string? no-redirect or so
[00:02] <Laney> got it
[00:03] <kees> slangasek: but where are these coming from?  that's not our kernel: ubuntu 2.6.30.5-ep0
[00:04] <slangasek> kees: oh, huh
[00:04] <cjwatson> the most recent bug says easypeasy
[00:04] <cjwatson> which is an eee variant of ubuntu
[00:04] <slangasek> kees: is that consistent with the others also?
[00:04] <cjwatson> I don't know whether that's the case for all of them
[00:04]  * kees goes to find the others
[00:05] <slangasek> kees: I've probably closed them as invalid
[00:05] <kees> 426914?
[00:07] <slangasek> kees: that's one, yes
[00:08] <kees> I'm baffled how debconf could be running and apt didn't scream about locks first.
[00:10] <Laney> slangasek: 431064
[00:12] <cjwatson> kees: sudo debconf-communicate?
[00:12] <cjwatson> (or similar)
[00:13] <kees> cjwatson: yeah, that would certainly do it...
[00:15] <cjwatson> kees: I dunno, maybe some bonkers wrapper or a package management frontend that starts debconf outside apt but doesn't pass through the fds etc. or ...
[00:16] <kees> cjwatson: yeah.  though 426914 doesn't show any signs of weird-3rd-party-ness
[00:23] <slangasek> kees: well, pam-auth-update can be run standalone
[01:11] <kees> pitti: is the retracer still doing source traces?  seems missing from 427714, for example.
[01:14]  * lamont notes that his daughter is DJ for the next 2 hours at www.klikradio.org.  </blatant plug>
[01:14] <TheMuso> What sort of music/
[01:15] <lamont> high school radio
[01:15] <lamont> webcast only
[01:16] <lamont> she's 11th grade
[01:18]  * lamont afk for a while,sadly
[01:19] <virtuald> q
[02:28] <e-jat> can this bug 398214 assign to some one?
[02:34] <Hobbsee> e-jat: that's probably a part of the boot stuff changing (ie, /topic), and should already be known.  That may well be a dupe
[02:34] <Hobbsee> er, or not, looking at the report date
[02:35] <slangasek> mathiaz: ubuntu-server candidates published (finally)
[02:36] <mathiaz> slangasek: awesome - my dinner will have to wait *for* *ever* now
[02:36] <slangasek> mathiaz: dinner first, testing after? :)
[02:37] <mathiaz> slangasek: well - 1. sync, 2. start automated installs then eat, drink, party 42. do testing
[02:37] <slangasek> kees: bug #431042> oh awesome, he's running update-manager and ubiquity at the same time
[02:37] <slangasek> mathiaz: if that's what works for you :)
[02:48]  * ccheney should have a fast i7 860 system by later next week, to build OOo on :-)
[02:49] <Hobbsee> ccheney: ah yes.  is OO.o supposed to work on karmic?
[02:49] <Hobbsee> hm, writer works now.
[02:50] <ScottK> Has KDE4 integration too.
[02:50] <Hobbsee> oh, it's just presentatoin that seems to be broken with opening files
[02:51] <ScottK> I'll try that when I get my netbook back from middle daughter later tonight (she's doing homework)
[02:52] <Hobbsee> 90+% cpu when opening a pptx, or a ppt file, it appears
[02:52] <ccheney> Hobbsee: under kubuntu?
[02:53] <Hobbsee> ccheney: unr
[02:53] <ccheney> oh no idea about unr :-\
[02:53] <Hobbsee> ccheney: i haven't run kubuntu in ages
[02:53] <Hobbsee> ccheney: well, it shouldn't be much different?
[02:53] <ccheney> kubuntu has some issues with new kde4 integration but roman is planning on having that fixed by end of week
[02:53] <Hobbsee> i don't have a standard ubuntu karmic machine to test on, atm
[02:53] <ccheney> hmm it might just be a function of the netbook being really slow
[02:54] <ccheney> i noticed that even starting OOo takes ~ 4x as long on a netbook
[02:54] <Hobbsee> i'd wondered that
[02:54] <Hobbsee> but i don't see the same problem with opening a word doc, for eg
[02:54] <ccheney> hmm if you want to you can file a bug report and attach the slow files
[02:57] <Hobbsee> mmm, i might do that
[03:06] <LaserJock> slangasek: what does Edubuntu need to do to get an Alpha 6, if possible?
[03:07] <slangasek> LaserJock: I'll schedule a rebuild of the edubuntu DVD this evening; will someone be available to test that it works?
[03:07] <LaserJock> slangasek: I believe so, I've got 2-3 people who've been testing recently
[03:07] <slangasek> ok
[03:07] <slangasek> there's a backlog of image builds, so it'll be at least 2-3 h before there's anything to test
[03:07] <LaserJock> slangasek: we got over-sized because I added all the edu apps to the livefs
[03:08] <LaserJock> slangasek: I'm committing a seed update now that should get us back down
[03:08] <slangasek> ok, great
[03:42] <kees> slangasek: hah, cool
[03:46] <ccheney> hmm i hope p55 works with karmic, heh forgot to even check
[03:50] <ScottK> ccheney: Is it known that OOo 3.1 doesn't know something is a .doc file unless it actually ends in .doc?
[03:57] <LaserJock> slangasek: was there a specific decision/reason why software-store replaced g-a-i so soon (i.e. for karmic)?
[04:01] <nixternal> oi oi, kdm init -> upstart v1 complete and working \o/
[04:01] <nixternal> now to clean it up, make it pretty, and add some of the Keybuk love that he snuck into GDM for some extra splash lovin!
[04:01] <ccheney> ScottK: wouldn't be surprised
[04:02]  * ScottK 's daughter about had a heart attack tonight when she reopened her homework and OOo showed an empty file.
[04:02] <nixternal> I love when that happens!
[04:02] <ccheney> heh
[04:02] <nixternal> ScottK: quit being lazy and teach her LaTeX already
[04:03] <ScottK> She needs .doc for interoperability with school.
[04:03] <ccheney> ScottK: there is a bug wrt kde4 integration not appending extensions properly (if that is what she saw)
[04:03] <ScottK> ccheney: OK, but when I manually added the extension, writer opened it fine.
[04:03] <nixternal> ScottK: .txt files then :p
[04:03] <ccheney> ScottK: yea
[04:04] <ScottK> I thought depending on file extensions was the Windows way ...
[04:04] <ccheney> i seriously doubt OOo tries to do anything fancy to detect what kind of file you are trying to have it open
[04:04] <nixternal> ahh, ya I noticed that same problem...glad you said 'added the extension' :)  now I can open up my buddies resume
[04:05] <ccheney> ScottK: its Sun we are talking about... not a regular floss application ;-)
[04:05] <ScottK> Well, I suppose.
[04:06] <ccheney> but even gnome claims a 0 byte .doc file is a msword file
[04:06] <ccheney> so i doubt that shared-mime-info does much better
[04:08] <ccheney> files have to sufficient magic to not get confused for other things
[04:08]  * ccheney isn't sure if doc files have it, but many file types don't
[04:09] <TheMuso> We need resource forks in the Fs. :)
[04:09] <ccheney> yep
[04:13] <ion> Resource forks or not, we need to get everything to ignore the filename when determining the file type. :-) The filename only exists for humans. For all the computer cares about, files could be looked up by their inode or equivalent ID just fine.
[04:22] <TheMuso> slangasek: according to the report for the latest studio candidate, ubuntustudio-desktop is uninstallable, which during the install, shows up as tango-icon-theme being uninstallable.
[04:22] <ccheney> ion: yea that works in theory... until you get a file whose type can't be _easily_ determined from the contents
[04:22]  * TheMuso digs to see what the problem is.
[04:23] <TheMuso> Oh and the previous candidate was prefectly ok.
[04:24] <ion> ccheney: Then call is aplication/octet-stream and blame the format. ;-)
[04:24] <ion> it
[04:25] <ion> Alternatively, determine it the hard way and cache the result. :-)
[04:32] <ccheney> if you end up trying to be too smart you end up not printing on tuesdays :)
[04:41] <astronut> so the 9.04 NBR installer somehow ate both my windows and recovery partitions
[04:41] <astronut> neither will boot correctly
[04:41] <TheMuso> Ok cannot reproduce uninstallability with chroot using archive.ubuntu.com, looks like it was transient.
[05:17] <rgreening> ever since last update, my usb thumb drives are not autodetected anymore. Any ideas?
[05:17] <ScottK> rgreening: Autodetected here on a fresh install.
[05:18] <rgreening> hmm... strange indeed.
[05:18] <slangasek> TheMuso: should I respin and see if the installability problem is fixed?
[05:18] <slangasek> ScottK: kubuntu alternate also posted, finally
[05:18] <slangasek> I believe we're just waiting now for DVDs and ARMs
[05:19] <ScottK> slangasek: OK. It's getting late here.  I'll be able to get through several KNE tests, but that's it for tonight.
[05:19]  * slangasek nods
[05:19] <ScottK> Hopefully Riddell will be awake soon and start cranking through stuff.
[05:21]  * spstarr_desk gasps at topic.. now someone tells me
[05:21] <spstarr_desk> I cant boot my fsckin laptop now :)
[05:21]  * spstarr_desk thinks something broke bad
[05:21] <ScottK> Actually I think things are mostly back to good.
[05:21] <TheMuso> slangasek: please
[05:22] <spstarr_desk> The dreaded "Waiting for root file system" problem
[05:22] <ScottK> spstarr_desk: If you look in today's backscroll, you'll find discussion on how to work through it.
[05:22] <spstarr_desk> i dont have it..
[05:22] <spstarr_desk> is this logged
[05:22] <ScottK> spstarr_desk: irclogs.ubuntu.com
[05:22] <spstarr_desk> looking now
[05:22] <slangasek> TheMuso: spinning
[05:23] <spstarr_desk> ScottK: this channel's log?
[05:23] <ScottK> It's in htere.
[05:23] <ScottK> htere/there
[05:23] <spstarr_desk> oh udev crap
[05:23] <spstarr_desk>  <maxb> Something weird is happening with karmic for me - supposedly clean shutdowns don't seem to be unmounting my root partition cleanly, and ext3 journal recovery happens on boot <-- yep
[05:24]  * spstarr_desk begins from here
[05:26] <spstarr_desk> oh its the blkid i need now in fstab?
[05:27] <spstarr_desk> why was this changed *now* ??
[05:27] <spstarr_desk> this is a horrible time to break thnigs
[05:28] <spstarr_desk> ugh i have to go wired to fix this wifi + single user == death
[05:31] <ScottK> It was supposed to land a couple of days ago.  I think better now than after Alpha 6 and before the Beta.
[05:31] <spstarr_desk> the workaround isn't working for me
[05:31] <spstarr_desk> it drops me to a busybox shell
[05:32] <spstarr_desk> not bash
[05:32] <spstarr_desk> idea #2, boot rescue CD mount /boot inside / inside a /fakeroot
[05:32] <spstarr_desk> chroot; get network and dist-upgrade...
[05:33] <spstarr_desk> and mount /proc
[05:33] <slangasek> TheMuso: uninstallables fixed
[05:36] <TheMuso> slangasek: So I see, thanks.
[05:38] <spstarr_desk> now let's apt dist-upgrade
[05:39] <spstarr_desk> is it mountall thats just broken?
[05:40] <ScottK> Depends on exactly when you upgraded.
[05:40] <ScottK> That was the last bit to get sorted.
[05:40] <spstarr_desk> that's the last thing i see.. i upgraded a few hours ago
[05:41] <ScottK> Probably that's it then.
[05:41]  * spstarr_desk laughs, bad timing indeed!
[05:42]  * spstarr_desk is glad the *buntu cds respect 'single' mode 
[05:42] <spstarr_desk> drops me to a root prompt
[05:45] <spstarr_desk> yay
[05:45] <spstarr_desk> thanks :)
[05:45]  * spstarr_desk goes back to wifi 
[06:04] <spstarr> ScottK: is there a PPA for kernel? or nightly builds?
[06:04] <spstarr> i want to test the radeon 3D support on karmic but the kernel is too old
[06:04] <ScottK> There is, but I don't know where.
[06:04]  * ScottK is off to bed.
[06:09] <mathiaz> slangasek: allright - -server amd64/i386 tests completed and successful
[06:09] <slangasek> mathiaz: yay!
[06:10] <mathiaz> slangasek: 15/17 for amd64 and 14/17 for i386
[06:10]  * slangasek nods
[06:14] <spstarr> http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/ ?
[06:17] <dholbach> #canonical-2009-09-17-07h16
[06:19] <mneptok> dholbach: fail.
[06:19] <dholbach> mneptok?
[06:20] <mneptok> dholbach: was that paste meant to be meaningful?
[06:20]  * mneptok is confuzzled.
[06:21] <dholbach> which paste?
[06:21] <dholbach> oops
[06:21] <dholbach> no
[06:22] <dholbach> good morning
[06:22] <dholbach> lalala :)
[06:22] <mneptok> moin :)
[06:22] <Treenaks> dholbach, good morning :)
[06:22] <dholbach> ouch ouch ouch
[06:22] <dholbach> errr.... more coffee!
[06:22] <mneptok> don't worry, i make mistakes, too.
[06:22] <dholbach> mneptok: probably less than I do ;-)
[06:22] <mneptok>  /m sabdfl yes, i think Daniel is sexy, too. but i never asked if he likes you. ask him to dinner and a movie at UDS.
[06:23] <mneptok> oops.
[06:23]  * Treenaks is still wondering about the blinking-while-typing Scroll Lock led
[06:23] <slangasek>  /lickban mneptok
[06:23] <mneptok> slangasek: give me a few hours in New Mexico heat and i make my own gravy.
[06:49] <jussi01> o.O strange things int this channel (mind, mneptok is here...)
[06:50]  * mneptok bursts into flame
[07:12] <slangasek> kirkland, ttx: does bug #430820 need to be documented in the errata for a6?
[07:12] <kirkland> slangasek: i think it should
[07:12] <kirkland> slangasek: network will be broken on -nc install first boots
[07:13] <slangasek> kirkland: is there a straightforward workaround?  (If the bridge isn't configured right, how do you access the node to reconfigure it, via a virtual console?)
[07:13] <slangasek> or is the node the physical cluster node?
[07:13] <kirkland> slangasek: yes; login to tty1, edit /etc/network/interfaces
[07:14] <slangasek> ok
[07:14] <kirkland> slangasek: the specific line of sed is in that bug
[07:14]  * slangasek nods
[07:14] <ttx> slangasek: I would also mention bug 430758. I'll do some more testing this morning to confirm problem/workaround
[07:15] <kirkland> ttx: welcome back
[07:15] <ttx> I'll doublecheck that logging in by ssh/tty2 and rebooting somehow works around it.
[07:15] <kirkland> ttx: i didn't get that problem
[07:16] <kirkland> ttx: note that there have been another set of iso's since you went to sleep
[07:16] <ttx> that's why I meant by doublechecking :)
[07:16]  * ttx rsyncs
[07:19] <ttx> nurmi: ping
[07:31] <teknico> superm1, hi, we've been exchanging emails right now
[07:34] <pitti> Good morning
[07:34] <pitti> pochu: oh, nice; yes, will do
[07:38] <slytherin> Can someone please give back empathy on powerpc?
[07:41] <soren> slytherin: Done.
[07:47] <pitti> pochu: bug updated, uploading now
[07:48] <pitti> kees: no, currently disabled because of xulrunner wreaking havoc
[07:52] <pochu> pitti: \o/ thanks!
[07:55] <pitti> pochu: do you need this in sid, or is experimental ok for now?
[07:57] <pochu> pitti: exp is ok until libgudev is in sid
[07:57] <pochu> pitti: I can poke you when that happens
[07:58] <pochu> or if it can go to unstable directly, why not upload there?
[07:58] <pitti> pochu: well, just in case the new rb doesn't make it into squeeze, I rather not have it in a stable release
[07:59] <pitti> pochu: but once it's through NEW, I can upload it to sid with a snap of a finger, so just poke me
[07:59] <pochu> ok, that's fine then :)
[07:59] <pitti> pochu: also, feel free to add yourself to Uploaders: and just do it
[08:00] <pitti> pochu: meh, Debian's udev missing .pc file
[08:00] <ttx> kirkland: confirming bug 430758 is avoided by one recent fix from Colin in the initscript.
[08:03] <pochu> pitti: does it? it has /usr/lib/pkgconfig/libudev.pc, isn't that enough?
[08:03] <pitti> pochu: that's for the library
[08:04] <pitti> pochu: we need /usr/share/pkgconfig/udev.pc
[08:04] <pitti> pochu: I'll hack around it
[08:05] <slytherin> are there going to be mass give back for ia64? There are many FTBFS because of chroot problems.
[08:06] <pochu> pitti: oh
[08:11] <soren> ttx: Oh, cool.
[08:13] <ttx> soren: it is still not displaying the eucalyptus initscripts messages, but that's more cosmetic
[08:13] <ttx> I'll file a separate bug for that.
[08:23] <Dyllan> Hi all. I have a script that uses zenith to provide the user with an easy to use interface other than the command line. But now I would like to transform it into a fully functional program for ubuntu/gnome, what devel tools are default/recommended for ubuntu, eg. glade etc?
[08:30] <evand1> the buildds install recommends by default, so a hard dependency on something recommended by a dependency is not required, right?
[08:35] <dholbach> evand: afaik they don't install recommends
[08:36] <slytherin> evand: buildd don't install recommends.
[08:37] <slytherin> Dyllan: AFAIK, glade is deprecated.
[08:38] <Dyllan> slytherin, what would you recommend then?
[08:38] <evand> dholbach: slytherin: ah, thanks!  I was completely unaware of that.
[08:38] <slytherin> Dyllan: I haven't done much UI programming from scratch in gnome. the replacement for glade is something called gtkbuilder. But I never used it.
[08:41] <Dyllan> slytherin, hmm ok. So can i write the program in any language then use gtkbuilder to design the front-end, is that the idea?
[09:04] <spstarr> the topic can be changed  to karmic boots again ;-)
[09:20] <bdrung_> do i need a FFe for bug #430658?
[10:00] <pitti> evand: hm, I think usb-creator now works without root privs, but its .desktop file still seems to run it through gksu?
[10:00] <evand> pitti: whoops
[10:00] <evand> fixing now
[10:01] <pitti> evand: while you are at it, could you please fix this: /tmp/usb-creator.log
[10:01] <pitti> evand: static file name in world-writable directory -> security vuln
[10:01] <pitti> I can also report it as a bug, if you prefer
[10:01] <evand> indeed, I'll move it to a more sane location
[10:01] <evand> please do
[10:04] <pitti> evand: need a bug about dropping gksu as well, or are just just doing it in bzr?
[10:04] <evand> hrm, actually the desktop file in trunk just launches usb-creator-gtk.  Is this launching through gksu bug via bzr trunk or the package in the archive?
[10:08] <pitti> evand: bug 431266
[10:08] <pitti> evand: hm, that's right, weird; I started it from the menu and it asked me for password (gksu)
[10:10] <evand> are you sure it was gksu and not the pk authentication agent (though I'm not sure why that would come up either)
[10:10] <pitti> evand: yes
[10:10] <evand> very odd then
[10:11] <pitti> hm, who knows
[10:11] <pitti> ignore this for now, please
[10:13] <evand> okay
[10:18] <sebner> pitti: yeah it seems I can continue working on the main bug report! Bus 001 Device 007: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp.
[10:18] <sebner>   I'll do the necessary debugging now :)
[10:24] <dholbach> sistpoty|work, slangasek, geser: thanks guys! announced your session!
[10:25] <sistpoty|work> dholbach: thanks (but slangasek won't be around for this session though)
[10:25] <dholbach> sistpoty|work: oh ok
[10:25] <sistpoty|work> geser: would you like to help out again this Friday?
[10:25] <geser> dholbach: good to let me know that I volunteered for that session too :)
[10:25] <dholbach> sorry
[10:25] <geser> sistpoty|work: yes
[10:25] <dholbach> I misread that email
[10:25] <dholbach> excusez-moi
[10:25] <sistpoty|work> thanks a lot geser :)
[10:26] <dholbach> geser: sometimes you need to help people to find their luck :)
[10:26] <geser> dholbach: no problem, I planned to be round for the session anyway
[10:29] <dholbach> sistpoty|work: updated :)
[10:29] <sistpoty|work> dholbach: excellent, thanks!
[10:29]  * sebner is sooo happy. This is going to be an awesome session :D
[10:34] <tkamppeter> pitti, CUPS does not start automatically on boot any more. Does it need to get converted to Upstart?
[11:18] <al-maisan> Hmm .. upon reporting bugs against pulseaudio one is prompted to try the packages from the ubuntu-audio-dev PPA .. once installed though ubuntu-bug declines to co-operate: ".. This is not a genuine Ubuntu package .."
[11:19] <lool> haha
[11:19] <lool> That's a good trick; I'll do that for more packages
[11:19] <lool> al-maisan: You want to ping davidchen and/or TheMuso about it I guess
[11:20] <al-maisan> lool :)
[11:21] <pitti> sebner: right, seems that will cover your case as well then
[11:22] <pitti> tkamppeter: no, it should still work
[11:22] <pitti> ugh, that was hard to recover from; with the latest cryptsetup and today's updates, my machine is completely busted
[11:22] <sebner> pitti: did you see my comment (with the debug information?), anyways. would you mind leading a helping hand in blacklisting that stuff?
[11:22] <pitti> it hangs forever on "starting sad crypto disks..."
[11:22] <pitti> (I don't have any)
[11:22] <pitti> and purging cryptsetup causes it not to boot at all any more
[11:23] <pitti> kirkland: hey
[11:23] <pitti> kirkland: seb128 just pointed out a change which will fix the ecryptfs/gdm problem: gnome bug 565151
[11:25] <pitti> evand1: hm, trying to boot an usb-creator usb stick with current karmic on my machine fails; it just gives me tons of "init line 1: /dev/sr0 not found" lines and then throws me into the initramfs prompt
[11:25] <pitti> it works on my wife's machine
[11:25] <sebner> pitti: I also wouldn't mind if you upload the blacklist-version the next days (what you'll do, as stated in the bug report)
[11:26] <pitti> can it be that it needs a longer timeout or something? did you hear this before?
[11:26] <evand1> pitti: does /casper.log have anything of note?
[11:26] <pitti> sebner: the bug report has the instructions how to blacklist; you need the ATTRS line with the GOTO, and the LABEL="...."
[11:26] <pitti> evand1: is that accessible from the initramfs prompt?
[11:26] <evand1> yes
[11:26] <evand1> cat /casper.log
[11:27] <pitti> ok
[11:27] <pitti> I need to reinstall this machine anyway, booting is completely busted
[11:27] <sebner> pitti: ah, just saw it. thx
[11:27] <pitti> I'm writing a CD now, but before I run that, I'll try the usb stick again
[11:36] <tkamppeter> pitti, thanks, then it seems that it is an upstart bug that all non-converted services (cups, mysql, sshd) did not start for me on boot.
[11:37] <pitti> tkamppeter: right, seems so; init.d scripts need to work, for at least the next decade
[11:37] <ogra> decade ? OMG !
[11:38] <pitti> ogra: well, there's tons of third-party and proprietary software out there
[11:38] <pitti> and even converting our own entire universe will last a while
[11:38] <ogra> pfft, just ignore them ...
[11:38] <ogra> :)
[11:39]  * ogra hides from the wrath of MOTU
[11:40] <highvoltage> :)
[11:41] <ogra> more Alka-Seltzer for karmic !!
[11:43] <ior3k> have you guys considered creating something like debian unstable for people who like to keep living on the (very bleeding) edge?
[11:45] <joaopinto> ior3k, that's called karmic right now :)
[11:45] <ogra> ior3k, we call it karmic
[11:45] <ior3k> right, that's not what I mean
[11:45] <ior3k> I mean a permanent name
[11:45] <ior3k> so we don't have to change sources.list
[11:45] <ogra> is it really that hard to adjust your sources.list twice a year ?
[11:46] <ior3k> no, it isn't hard at all, I'm just asking
[11:47] <ior3k> if there is some kind of rationale behind it
[11:47] <ogra> yes, our unstable is a snapshot of debians
[11:48] <ior3k> ah, so you keep an unmodified unstable branch that is exactly like debian's, then 'fork' it over to form the next distro's branch?
[11:49] <ogra> which goes hand in hand for about half a release cycle and then gets into stabilization ... due to that stabilization phase our "unstable" diverges frome debians and requires a new snapshot at the beginning of the next release cacle
[11:49] <Laney> we fork the stable branch at release and then merge debian into that
[11:49] <ogra> *cycle
[11:50] <ior3k> got it, thanks
[11:57] <cjwatson> ior3k: we don't have developer bandwidth to maintain a separate unstable as *well* as karmic; we did think about it early on, but decided against it
[11:57] <cjwatson> (indeed I was a proponent of a separate unstable, but was convinced otherwise)
[11:59] <ior3k> cjwatson: makes sense, I guess everyone is mostly busy working on the *current* future stable version
[11:59] <ior3k> cjwatson: thanks for the clarification
[12:20] <amitk> gah! dist-upgrade seems to have broken compiz. No window manager for me :-/
[12:21] <ogra> there is that ancient metacity thingie ;)
[12:21] <amitk> right click doesn't work on the desktop and there is not gnome-panel
[12:21] <amitk> *no
[12:22] <ogra> doesnt actually sound like a windowmanager issue
[12:58] <lamont> Error: Descriptions do not match: <-- where in debbuild's world to those errors come from, I wonder?
[13:03] <evand1> are we expected to stick things (specifically, log files) in .cache these days?
[13:04] <evand1> or is it okay to hate the XDG base directory specification
[13:07] <slytherin> evand1: You shouldn't use .cache name hard coded
[13:07] <evand1> slytherin: indeed, I was just doing that for brevity
[13:21] <MacSlow> seb128, what valgrind command-line did you use to obtain the log you attached here https://bugs.edge.launchpad.net/ubuntu/+source/notify-osd/+bug/430722
[13:23] <seb128> MacSlow, G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck --leak-check=full --num-callers=38 /usr/lib/notify-osd/notify-osd
[13:24] <seb128> MacSlow, why?
[13:25] <MacSlow> seb128, just wondering
[13:25] <seb128> MacSlow, you don't get the issue?
[13:25] <MacSlow> seb128, I added a possible fix and now try to reproduce it
[13:26] <seb128> ok
[13:26] <seb128> MacSlow, want me to try the fix?
[13:26] <MacSlow> seb128, would be cool... one sec
[13:29] <MacSlow> seb128, http://paste.ubuntu.com/272784
[13:29] <MacSlow> seb128, if that fixes it, it would mean the purging of old bubbles is messed up
[13:30] <MacSlow> which would need further investigation
[13:34] <pitti_reinst> evand1: hm, now that you told me about /casper.log, the usb stick booted; I love race conditions :)
[13:34] <evand1> haha, hooray
[13:35] <pitti_reinst> I tried it three times before..
[13:35] <evand1> I thought upstart was going to fix all boot race conditions, and give us ponies ;)
[13:36] <evand1> if you do manage to reproduce it at some point, a bug report with the casper log attached would be greatly appreciated
[13:36] <ogra> ponie races probably :)
[13:36] <ogra> *pony
[13:36] <evand1> haha
[13:36] <pitti_reinst> evand1: yes, should be easy to reproduce, I'll just try it a couple of more times
[13:37] <pitti_reinst> evand1: how does the USB stick booting work, is it "faked" to become /dev/sr0?
[13:37] <pitti_reinst> evand1: since it seems to loop over getting /dev/sr0
[13:40]  * lamont finds his answer: mergechanges
[13:44] <ScottK> lamont: I listened to your daughter on the radio last night.  Would you please fix the IA64 chroots?
[13:44] <ScottK> :-)
[13:46] <lamont> ScottK: the debian ones?
[13:46] <ScottK> No, our buildds
[13:46] <lamont> so totally frustrated at those damn things
[13:46] <lamont> oh ours?  what's b0rked?
[13:46] <ScottK> (or did you do that already today)
[13:46] <lamont> (build log somewhere?  or just any and all?)
[13:46] <ScottK> chrootwait.
[13:46] <ScottK> Any/All
[13:46] <lamont> ah, ok
[13:47] <cjwatson> ScottK: the necessary fix is to port dbus to ia64
[13:47] <lamont> taking kids to school in about 2 seconds, will look at that once I'm back online
[13:47] <ScottK> ouch
[13:47] <cjwatson> it's not something that can be fixed on the buildd side before that
[13:47] <cjwatson> look a couple of revisions back in dbus and you'll see the failure - missing clock_getres and clock_gettime IIRC
[13:48] <ScottK> OK, that'll probably have to wait until after lamont takes his kids to school.
[13:48] <lamont> oh. that.  nowI remember
[13:50] <lamont> where are those funcs defined on other architectures
[13:50] <evand1> pitti: lp:casper in scripts/casper, see find_livefs
[14:05] <Keybuk> ok, that's five minutes ... and nobody's pounced on me
[14:05]  * ogra pounces on Keybuk 
[14:05] <ogra> just for fun
[14:06]  * Keybuk rolls around on the floor with ogra
[14:06] <ogra> cuddly :)
[14:06] <ion> aaww
[14:07] <Keybuk> :-)
[14:09] <cjwatson> Keybuk: now, the question is, is that because there are no problems or is it the onset of despair? ;-)
[14:09] <Keybuk> cjwatson: that was exactly what I was thinking
[14:09] <Keybuk> but then I figured that either is a win
[14:10] <Keybuk> now, onto the critical bugs
[14:10] <Keybuk> *why* has compiz lost all my key bindings *again* :-(
[14:18] <pitti> yay, finally; a working machine again
[14:26] <pitti> Keybuk: would you mind if I re-add the check for "text" to /etc/init/gdm.conf? It's quite useful for broken drivers and debugging
[14:27] <ogra> pitti, oh, please do !
[14:27]  * ogra didnt know that was gone
[14:27] <pitti> how could I not, now? :-)
[14:28] <rgreening> any ideas on how I can debug why usb autodetection is broken? It worked in alpha5 but updating yesterday broke it.
[14:28] <ogra> i often make use of it
[14:28] <Keybuk> pitti: check for text?
[14:28] <pitti> Keybuk: yes, in /proc/cmdline, like the old init script
[14:28] <ogra> Keybuk, gdm didnt start with text on cmdline
[14:29] <pitti> rgreening: usb drives?
[14:29] <ogra> its very helpful if you want to debug stuff
[14:29] <Keybuk> oh, I missed that
[14:29] <Keybuk> sure
[14:29] <Keybuk> you might want to add single in too ;)
[14:29] <Keybuk> and all the -s and S synonyms of that
[14:29] <pitti> rgreening: ubuntu-bug, and select "storage devices"
[14:29] <rgreening> pitti: yeah. dmesg shows them.. but they do not autodetect for me to automount
[14:29] <rgreening> pitti: ok.
[14:29] <pitti> yay, apport symtoms :)
[14:35] <pitti> Keybuk: "-s and S synonyms"?
[14:36] <ion> pitti: See /etc/init/rc-sysinit.conf, everything that leads to DEFAULT_RUNLEVEL=S
[14:36] <pitti> aah
[14:36] <pitti> thanks
[14:38] <Keybuk> ion: I still need to find out whether there's a better way of doing that
[14:38] <Keybuk> I have a vague memory that the kernel actually passes all kernel command-lines to init
[14:38] <Keybuk> (it must do, because adding --debug works :p)
[14:38] <ion> :-)
[14:38] <Keybuk> so it must pass the -b, -s, etc. to init too
[14:38] <Keybuk> then I wonder whether it passes things that don't begin with -
[14:39] <Keybuk> so maybe init gets "single" in argv[1]
[14:39] <Keybuk> even "quiet", "splash", etc.
[14:39] <Keybuk> so I could put those into the startup event in some meaningful way
[14:39] <Keybuk> start on startup SINGLE=no
[14:39] <Keybuk> or something
[14:39] <darkham> please, tell me more about UserInterfaceFreeze
[14:39] <darkham> of 10-09
[14:40] <pitti> darkham: see https://wiki.ubuntu.com/UserInterfaceFreeze
[14:40] <Keybuk> darkham: it's the point in our release cycle that, after which, changes to the user interface need to be approved
[14:40] <darkham> yes, but nothing more about features?
[14:41] <Keybuk> darkham: Feature Freeze happens before UI Freeze (a couple of weeks ago)
[14:42] <darkham> what's was decided?
[14:42] <cjwatson> Keybuk: init/main.c:unknown_bootoption
[14:42] <Keybuk> darkham: what do you mean?
[14:42] <Keybuk> cjwatson: hmm?
[14:43] <darkham> features inside the featurefreeze
[14:43] <Keybuk> darkham: is there a specific question you want an answer for?
[14:43] <darkham> yes, i would have an answer about
[14:44] <Keybuk> cjwatson: where are you looking?
[14:45] <cjwatson> Keybuk: in the kernel
[14:45] <Keybuk> cjwatson: ah, right; yes that's what I mean
[14:45] <cjwatson> as I read it, it passes unknown foo=bar in init's environment, and unknown foo in init's argv
[14:46] <Keybuk> *nods*
[14:46] <Keybuk> that was my understanding too
[14:46] <rgreening> pitti: ubuntu-bug is taking an awfully long time to collect info... been running since you told me to try it... I suspect its not working
[14:46] <pitti> rgreening: did it ask you questions?
[14:47] <rgreening> pitti: first time I tried it, I selected the storage option, and it complained about missing package or PID.
[14:47] <pitti> uh
[14:48] <pitti> rgreening: I never actually tried it on Kubuntu
[14:48] <rgreening> pitti: second time I passed "storage devices" as text on cmdline.. and now its collecting forewver.
[14:48] <pitti> it assumes devicekit-disks and everything
[14:48] <pitti> not hal
[14:48] <rgreening> pitti:  have that
[14:48] <pitti> rgreening: ubuntu or kubuntu?
[14:48] <rgreening> kubuntu with devicekitdisks
[14:48] <Keybuk> cjwatson: nice to have that confirmed from kernel code though, saves me looking
[14:49] <Keybuk> is a matter of figuring out how to pass them to jobs as well
[14:49] <Keybuk> e.g. how does "-b" gets passed
[14:50] <pitti> rgreening: does top say whether there's a busy process?
[14:50] <cjwatson> yeah, seems like it makes sense to define more spellable names
[14:50] <rgreening> pitti: 5% cpu... doesn't appear hung
[14:51] <rgreening> loadavg if fine
[14:51] <rgreening> is
[14:51] <rgreening> strange
[14:51] <ion> keybuk: http://heh.fi/tmp/init-args (i diverted /sbin/init and created a /sbin/init that prints $* and /proc/cmdline and execs the diverted init)
[14:52] <Keybuk> cjwatson: the idea for upstart 1.0 is that words there get converted to jobs
[14:52] <Keybuk> so if you had "single" on the command-line, you'd have a "single" job/state active
[14:52] <Keybuk> then you could do:
[14:52] <Keybuk>   while single
[14:52] <Keybuk> &
[14:52] <Keybuk>   while not single
[14:52] <ion> keybuk: Some parameters seem to get passed as init args, some don’t. Dunno what determines that.
[14:52] <rgreening> pitti: I suspect nixternal has a bug in the code wrt text on cmdline enclosed in quotes :)
[14:52] <slytherin> Does anyone know where can I find Daniel Chen?
[14:52] <Keybuk> ion: ones the kernel knows don't
[14:52]  * rgreening tries again anothe rway
[14:53] <Keybuk> ion: "ro" and "quiet" are for the kernel, likewise root
[14:53] <Keybuk> ion: can you dump "env" as well and try a few things like foo=bar
[14:53] <ion> Ok
[14:55] <ion> keybuk: Indeed, those do get added to the environment.
[14:56] <Keybuk> but not the root= and stuff?
[14:56] <rgreening> nixternal: apport-kde does not allow you to enter bug details without specifying a packge.
[14:56] <rgreening> nixternal: apport-gtk does...
[14:57] <rgreening> pitti: ^ so trying again with gtk version installed :)
[14:59] <ion> keybuk: http://heh.fi/tmp/init-args
[14:59] <ion> keybuk: The ROOT env variable might come from initramfs.
[15:01] <Keybuk> yes, I think that gets a bit leaked
[15:01] <Keybuk> the initramfs tends to export its environment randomly
[15:02] <Keybuk> cf. MODPROBE_OPTIONS
[15:02] <Keybuk> and break= ;)
[15:02] <ion> Yeah
[15:03] <Keybuk> it's arguable that the initramfs shouldn't use "export" at all
[15:03] <Keybuk> since it sources everything
[15:12] <pitti> Keybuk: can/should upstart scripts use log_warning_msg and similar LSB functions?
[15:12] <pitti> or just echo? or nothign at all?
[15:12] <Keybuk> no
[15:12] <Keybuk> they shouldn't
[15:12] <Keybuk> imo upstart scripts should freely output warnings, errors, etc.
[15:13] <Keybuk> and not use things like 2>/dev/null
[15:13] <Keybuk> so in karmic+1, those logs will be available and contain useful information
[15:13] <pitti> so just echo "Not starting GNOME Display Manager (gdm); found 'text' in kernel commandline." is okay?
[15:13] <pitti> to stdout
[15:13] <Keybuk> pitti: tbh, i tend to just make it fail :)
[15:13] <Keybuk> the text won't go anywhere
[15:13] <Keybuk> so it's not worth making it descriptive just yet
[15:13] <Keybuk> but sure, that's fine
[15:13] <pitti> you don't see it on the VT?
[15:13] <pitti> ok
[15:13] <Keybuk> no
[15:14] <Keybuk> that's a TODO
[15:14] <Keybuk> what I actually want is for things to be a bit more like, well, cron actually
[15:14] <Keybuk> if you do "# start gdm" yourself
[15:14] <Keybuk> you should see the output on your VT
[15:14] <Keybuk> but if gdm starts, you shouldn't get random dumpings across your VT
[15:14] <Keybuk> just if it fails, you see the output as part of the "gdm failed" notification
[15:14] <Keybuk> but if gdm is automatically started
[15:14] <Keybuk> the failure log should go somewhere useful
[15:14] <Keybuk> maybe /var/log
[15:15] <Keybuk> maybe sent via e-mail
[15:15] <Keybuk> etc.
[15:15] <rgreening> pitti: bug 431878
[15:16] <rgreening> pitti: I suspect udev rules clutter.. just do not know 1) for certain and 2) how to debug
[15:16] <pitti> Keybuk: so I think "if egrep -wqs 'text|single|s|S|-s'; then exit 0; fi" should do
[15:17] <Keybuk> pitti: oh, I'd just do
[15:17] <pitti> those are the combinations I found in /etc/init/rc-sysinit.conf
[15:17] <Keybuk>   egrep -wqs 'text|single|s|S|-s' /proc/cmdline
[15:17] <Keybuk> ;)
[15:17] <Keybuk> though iirc, you'll get slapped with a "root=something-s always enters single user mode" bug ;)
[15:18] <cjwatson> mm, you need for x in $(cat /proc/cmdline); do ...; done really
[15:18] <Keybuk> indeed
[15:18] <cjwatson> (or </proc/cmdline if that actually works)
[15:18] <pitti> Keybuk: no, -w only matches whole words ast it seems
[15:18] <Keybuk> pitti: it doesn't
[15:18] <cjwatson> pitti: - is a word boundary though
[15:18] <pitti> $ echo "root-something" | grep -wqs -- '-s'
[15:18] <pitti> -> code 1
[15:18] <Keybuk> grep's "whole word" is done on a boundary
[15:18] <cjwatson> pitti: now try root-s
[15:18] <pitti> $ echo "root-s" | grep -wqs -- '-s' || echo no
[15:19] <pitti> no
[15:19] <cjwatson> oh, hmm
[15:19] <cjwatson> but:
[15:19] <cjwatson> $ echo "root-s" | grep -wqs -- 's'; echo $?
[15:19] <cjwatson> 0
[15:19] <pitti> magic
[15:19] <Keybuk> right just "s" not "-s"
[15:19] <pitti> so I really want a WORD not a word (in Perlspeak)
[15:20] <Keybuk> pitti: just copy the logic from rc-sysinit.conf
[15:20] <ion> case " $(cat /proc/cmdline) " in *' -s '*|*' single '*|...) :-P (Or just for arg in $(cat /proc/cmdline)...)
[15:20] <pitti> Keybuk: *nod*
[15:22] <pitti> Keybuk: while I'm at it, I kill the gdm-cdd.conf stuff; it doesn't work any more
[15:26] <Keybuk> pitti: I'm tending strongly towards killing off untested options and configs
[15:26] <Keybuk> (as part of the sysvinit -> upstart migration)
[15:26] <Keybuk> on the basis that if we let someone change something, we should continually test both settings
[15:27] <Keybuk> and that upstart jobs are supposed to be a billion percent more readable than init scripts
[15:27] <Keybuk> plus some config options are silly
[15:27] <pitti> Keybuk: I take that as an "ok" for removing gdm-cdd.conf? :-)
[15:27] <Keybuk> pitti: yup!
[15:27] <Keybuk> TMPFS_SIZE ?!  ... which tmpfs? and why not just put it in /etc/fstab where it's supposed to go
[15:33] <pitti> ogra: it's back in bzr, will upload after alpha freeze
[15:33] <ogra> cool
[15:34] <Keybuk> pitti: bug #431176 btw (for changelog)
[15:34] <pitti> ah, nice
[15:38] <hyperair> what's the difference between /etc/init and /etc/event.d?
[15:38] <ogra> hyperair, one upstream release of upstart
[15:38] <pitti> hyperair: the former exists :)
[15:39] <ogra> well, depends where you look :)
[15:39] <pitti> event.d is the deprecated name of older upstarts
[15:39] <hyperair> ogra: meaning /etc/event.d can be effectively purged now?
[15:39] <ogra> the latter exists too :)
[15:39] <ogra> just not in recent versions
[15:39] <ogra> hyperair, yes
[15:39] <hyperair> i see
[15:42] <Madkiss> hi all
[15:42] <pitti> Keybuk: btw, "sad" crypto drives and "weak" partitions? :-)
[15:42]  * pitti can imagine the mood under which Scott produced all that
[15:42] <Madkiss> with todays updates, my system hangs after "starting sad crypto disks"
[15:42] <Madkiss> what's wrong with it?
[15:42] <pitti> happened to me as well
[15:42] <Keybuk> yeah cryptsetup is fucked
[15:42] <pitti> bug 430496
[15:42] <Keybuk> it probably needs rewriting using udev properly
[15:43] <Laney> al-maisan: I think you mistakenly credited me with the php-suhosin sync somehow
[15:43] <pitti> well, it might not exactly be that particular bug
[15:43] <pitti> but it's a placeholder for "fix it"
[15:44] <hyperair> hmm can upstart handle pm-utils hooks?
[15:44] <hyperair> like start on resume or something
[15:44] <hyperair> =D
[15:44] <kirkland> Keybuk: hey, i'm looking at https://bugs.edge.launchpad.net/ubuntu/+source/sysvinit/+bug/427277
[15:44] <Keybuk> hyperair: eventually
[15:44] <kirkland> Keybuk: happy to fix that
[15:44] <hyperair> Keybuk: that's nice
[15:45]  * hyperair needs to get round to switching my phc init script to an upstart job
[15:45] <Keybuk> kirkland: I guess the right way would be that if /etc/init/$ARG.conf exists, use "start", "stop", etc. rather than invoke-rc.d
[15:45] <kirkland> Keybuk: how would service tell if its being called in an upstart job
[15:45] <pitti> unfortunately I can't reproduce the hang on "sad crypto drives" in a VM
[15:45] <kirkland> Keybuk: ah, cool
[15:45] <kirkland> Keybuk: so the "fix" is really *not* to use invoke-rc.d
[15:45] <Keybuk> kirkland: you still need to use invoke-rc.d if it's an init script ;)
[15:46] <kirkland> Keybuk: of course.  i meant "conditions permitting"
[15:46] <al-maisan> Laney: you ack'ed it
[15:46] <Keybuk> right
[15:46] <yuriy> pitti: hi. what should i do to get the patch for bug 405378 into karmic as fast as possible? debdiff or commit to bzr? if the latter, what branch?  this bug is kind of critical now that +filebug doesn't work anymore, so i'd like to get this fix in and can work on a more complete fix later
[15:47] <Laney> al-maisan: bug 429531 ?
[15:47] <kirkland> Keybuk: what is the total set of actions you provide?  (start, stop, status) ?
[15:47] <al-maisan> Laney: there was another bug, let me dig out the number..
[15:48] <Laney> al-maisan: anyway if I only acked it then the requester should have had it
[15:48] <al-maisan> Laney: bug #424789
[15:48] <Laney> if I actually requested the sync then ...
[15:48] <al-maisan> Laney: hmm .. "Replace LPUID with the Launchpad username of the sync requester, or the acknowledger if the requester is not an active developer"
[15:49] <pitti> yuriy: I don't particularly mind, what's easiest for you; I'll commit it to bzr right away and upload right after the freeze
[15:49] <Laney> I don't see myself on that bug
[15:49] <pitti> yuriy: I don't think it's ubuntu specific, so I'll commit it to trunk (lp:apport) and cherrypick to the ubuntu branch
[15:49] <james_w> Laney: I think you set it confirmed
[15:49] <pitti> yuriy: thanks a lot for figuring this out; what was it?
[15:49] <yuriy> pitti: ok, thanks!
[15:50] <al-maisan> Laney: yep (Iain Lane  on 2009-09-14)
[15:50] <Laney> Oh that was just status fiddling
[15:50] <simon-o_> al-maisan: Did you sync awesome, bug 427767
[15:51] <Laney> not a big deal really anyway
[15:51] <al-maisan> Laney: great, thanks!
[15:51] <al-maisan> simon-o: yes.
[15:51] <yuriy> pitti: a couple different things. simple bug where it's just canceling when the complete/reduced report radios aren't visible (the patch fixes this). hanging is a problem with how the app is excecuted/exited to work around bug 403361. need to figure out that one and come up with a more complete fix.
[15:52] <simon-o_> al-maisan: You synced 3.3.4-1 and not 3.3.2-1. Was this on purpose?
[15:52] <al-maisan> simon-o_: no .. let me have a look.
[15:53] <simon-o> al-maisan: 3.3.4-1 is missing libxcb-event1-dev (>= 0.3.6)
[15:53] <simon-o> https://edge.launchpad.net/ubuntu/+source/awesome/3.3.4-1
[15:53] <Laney> too late now, you need to either fix 3.3.4 or do a sourceful upload of 3.3.2
[15:53] <al-maisan> simon-o: I see. Sorry, I did not pay attention there.
[15:54] <pitti> or a newer version of xcb-util
[15:54] <pitti> if that just fixes bugs, it's okay
[15:54] <Laney> yeah that's covered by "fix" :)
[15:56] <simon-o_> Laney, pitti, al-maisan: It fixes some bugs: http://lists.freedesktop.org/archives/xcb/2009-August/004994.html
[15:56] <simon-o> I'll request a sync
[15:57] <pitti> looks fine
[15:57] <al-maisan> yep
[15:57] <al-maisan> simon-o: thanks!
[15:57] <Laney> cool beans
[15:57] <pitti> just note the freeze for main packages (so perhaps don't sync it right now)
[15:58] <pitti> al-maisan: ^
[15:58] <al-maisan> pitti: because of the pending A6?
[15:58] <pitti> right; just in case it breaks stuff
[15:58] <al-maisan> pitti: noted.
[15:59] <al-maisan> hmm .. there seems no way to sync a specific version .. or is there?
[16:00] <cjwatson> it's possible if you can get hold of the package, but ask yourself whether it's a good idea
[16:00] <cjwatson> you have to mess around by hand with dpkg-scansources to do it
[16:00] <al-maisan> cjwatson: I see.
[16:01] <Laney> There's no -t testing or so?
[16:01] <james_w> yes, you can sync from testing
[16:01] <james_w> but a version that isn't in unstable or testing or ... is harder
[16:02] <Laney> ah, well in this case it was a squeeze sync
[16:03] <Madkiss> since today's updates, my ubuntu netboot client with karmic won't boot anymore
[16:03] <Madkiss> this is a total regressino compared to yesterday :(
[16:03] <hyperair> how does upstart stop tasks? kill them?
[16:04] <simon-o> I requested the sync in bug 431914
[16:04] <al-maisan> simon-o: thanks again.
[16:05] <simon-o> al-maisan: your welcome, thanks for syncing :)
[16:05] <al-maisan> simon-o: :)
[16:06] <Madkiss> the last thing i see is "b43-phy: UNSUPPORTED PHY FOUND" or some such
[16:07] <Madkiss> and after that
[16:07] <Madkiss> it will just not do anything.
[16:07] <Madkiss> could that have something to do with the upstart-update that apparently happened last night?
[16:07] <Laney> more than likely
[16:08] <slytherin> Madkiss: Does it really not do anything? How long did you wait?
[16:09] <Pici> 22
[16:11] <kees> goood morning
[16:12] <kees> pitti: ah, okay, dang.  can xulrunner be perhaps blacklisted or something?  I find the source traces very helpful.
[16:12] <pitti> kees: yes, certainly; I just quickly disabled it back then, and then forgot about it, since nobody complained
[16:12] <kees> pitti: heh, okay.
[16:18] <Madkiss> slytherin: ten minutes. after downgradingh upstart, it gets faster, but it does not mount /dev/pts and some such
[16:19] <slytherin> Madkiss: hmm, then surely it is some problem with upgrades. Are you sure the mirror you are using has all the upgrades available?
[16:21] <Madkiss> slytherin: yes
[16:27] <ttx> nurmi: mail sent, happy testing
[16:27] <Madkiss> it tells me that mountpoints /dev/pts and /dev/shm do not exist
[16:29] <Madkiss> invoke-rc.d: unknown initscript, /etc/init.d/udev not found.
[16:29] <Madkiss> wtf.
[16:30] <cjwatson> it's an upstart job now
[16:30] <kirkland> Keybuk: pitti: http://paste.ubuntu.com/272918/
[16:30] <cjwatson> 'start udev'
[16:30] <kirkland> Keybuk: i think that should do it; working here on my end
[16:31] <kirkland> Keybuk: pitti: would you guys apply that patch to your /usr/sbin/service and make sure it works as expected?
[16:32] <Madkiss> cjwatson: this  whole upstart-thing is utterly broken.
[16:33] <pitti> kirkland: exec env -i LANG="$LANG" PATH="$PATH" TERM="$TERM"
[16:33] <Madkiss> cjwatson: it left my system behind in a completely unusable state; i am not sure if this is supposed to happen round about one month before final release.
[16:33] <cjwatson> Madkiss: we're two days into a transition to a new init system. I'm sure all your code works first time. ;-)
[16:33] <pitti> kirkland: out of interest, what does that do? looks like a no-op to me?
[16:33] <Madkiss> cjwatson: err. where was that announced?
[16:33] <cjwatson> Madkiss: do please file bugs about breakage
[16:33] <sebner> Madkiss: still alpha status though :P
[16:34] <Keybuk> Madkiss: we're actually six weeks before release, which is quite a bit longer than "one month"
[16:34] <Madkiss> cjwatson: "Hangs at boot. Does not do anything. Produces no output. Lets me not boot with init=/bin/sh"
[16:34] <Keybuk> six weeks is a *quarter* of our release cycle
[16:34] <pitti> Madkiss: are you on intel?
[16:34] <Madkiss> amd64-.
[16:34] <kirkland> pitti: which part?  the exec?  or the env sanitizing?
[16:34] <pitti> Madkiss: I mean graphics
[16:34] <Madkiss> no. nvidia.
[16:34] <pitti> kirkland: env with TERM="$TERM" etc.
[16:34] <Keybuk> Madkiss: you're saying that if you put init=/bin/bash on your kernel command-line, your system doesn't even boot to a shell?
[16:35] <Madkiss> Keybuk: so you've had three quarters of time for breaking everything whatsoever.
[16:35] <Madkiss> Keybuk: yes.
[16:35] <Keybuk> Madkiss: then you don't have an Upstart problem
[16:35] <pitti> kirkland: "sanitizing"? by setting variables to themselves?
[16:35] <Madkiss> well, after downgrading upstart, i at least get to *somewhere*
[16:35]  * Madkiss feels snipered
[16:35] <kirkland> pitti: we inherited that from the original Red Hat service script
[16:36] <kirkland> pitti: let me investigate
[16:36]  * ogra wonders what could break that init=/bin/bash doesnt work anymore
[16:36] <pitti> kirkland: it looks like a weird NOP to me
[16:36] <Keybuk> Madkiss: what happens when you do use init=/bin/bash
[16:36] <kirkland> pitti: oh, it's the -i
[16:36] <pitti> aah
[16:36] <kirkland> pitti: env -i, --ignore-environment
[16:36] <ion> madkiss: You installed karmic. As long as it’s in development, you can feel lucky if it ever boots. :-P
[16:36] <Madkiss> Keybuk: Right nothing after the br0-phy-message I posted earlier.
[16:36] <pitti> kirkland: gotcha
[16:36] <kirkland> pitti: so it clears all env variables, except those
[16:36] <Madkiss> ion: it did so for almost two weeks.
[16:37] <cjwatson> certainly, if you use init=/bin/bash, upstart is *not called*
[16:37] <cjwatson> that's the point of init=
[16:37] <kirkland> pitti: perhaps that not desired in upstart .... Keybuk ?
[16:37] <Madkiss> ion: I would expect breakage to *reduce* the closer we get to point of release, instead, it's increasing.
[16:37] <Keybuk> kirkland: doesn't make much difference, I don't think
[16:37] <Keybuk> kirkland: "start" itself doesn't do anything, Upstart will run the service itself in an already safe environment
[16:37] <Keybuk> (this is one of the big decision choices)
[16:37] <ion> madkiss: It’s still a development release.
[16:37] <kirkland> Keybuk: okay, then i'll drop that bit from the upstart call
[16:38] <pitti> kirkland: tried with "sudo service cups" (init.d) and "sudo service hal" (upstart), both work fine
[16:38] <Madkiss> ion: I can not remember a point in time where Debian unstable was broken like this.
[16:38] <Keybuk> Madkiss: I can remember lots of times
[16:38] <pitti> kirkland: and /etc/init.d/hal stop rightfully complains
[16:38] <pitti> kirkland: works for me
[16:38] <Madkiss> whatsoever.
[16:38]  * Keybuk thinks back to the libc5->libc6 transition
[16:38] <Keybuk> and the shadow transition
[16:38] <Madkiss> yeah, that was like 400 years ago.
[16:38] <Keybuk> and the apt transition
[16:38] <kirkland> +         exec ${ACTION} ${SERVICE} ${OPTIONS}
[16:39] <kirkland> pitti: i changed the upstart call to that
[16:39] <kirkland> pitti: i left the sysvinit one as is
[16:39] <Madkiss> thing is, this need fixage.
[16:39] <pitti> kirkland: oh, I wasn't saying that you should throw it out
[16:39] <Keybuk> whenever you change any major component, you'd expect breakage
[16:39] <Keybuk> at least for some people
[16:39] <pitti> kirkland: I was just curious what it's supposed to do, since it looked like a noop to me; I missed the -i
[16:39] <ion> madkiss: Sure. It will probably be fixed within the next six weeks. :-P
[16:39] <kirkland> pitti: heh, well i don't think it's necessary if we're calling upstart; in the traditional case, i'll leave it
[16:40] <pitti> kirkland: *nod*
[16:40] <Madkiss> ion: given the attitude i'm confronted with, i am kinda left with a doubt about it :)
[16:40] <kirkland> pitti: Keybuk: okay, i'll upload this as soon as the archive unfreezes
[16:40] <pitti> kirkland: so, thumbs-up for me
[16:40] <kirkland> speaking of ... has it unfroze?
[16:40] <pitti> thank you
[16:40] <kirkland> pitti: no problem, thanks for reporting
[16:40] <Madkiss> do i need any special boot parameters for upstart?
[16:40] <pitti> kirkland: realistically I don't think we'll re-roll, but not officially yet
[16:40] <kirkland> pitti: right-o
[16:41] <Keybuk> Madkiss: the only attitude is coming from you
[16:41] <ion> madkiss: It’s kind of funny you talk to us about attitude. :-)
[16:41] <kirkland> pitti: i'll wait, i have a stack of uploads building now ;-)
[16:41] <seb128> would be nice to lift the freeze soon
[16:41] <seb128> I would like to sponsor os and dx changes before going for dinner
[16:42] <Madkiss> Keybuk, ion: Listen, lads. Is anyone of you two into helping me debugging this thing?
[16:43] <Keybuk> Madkiss: after everything you've said about my work, do you want me to help you?
[16:43] <Madkiss> Keybuk: yes.
[16:43] <Keybuk> really, you think I'm competent enough to help you?
[16:44] <Keybuk> because what you were saying above really doesn't make me feel like you do
[16:44] <Madkiss> If you claim that the situation I am in now was created by some bugs introduced by your changes, I have no reason to believe that there is anyone else who might rather be able to help me than you, eh?
[16:45] <Madkiss> and furthermore, i am tempted to assume you want bugs in your stuff to be fixed, so here's one willing debian developer who might be able to help.
[16:45] <Keybuk> well, you've just been ranting on how I should never have introduced my changes, and how other developers would have never broken things
[16:45] <Madkiss> just tell me what to do. How do I make the boot process more verbose? Do I need some special switch?
[16:45] <Keybuk> so how's that supposed to be make me feel like helping you?
[16:45] <soren> kees: At some point you were interested in stuff that worked with sun-java-6, but not with openjdk. Are you still interested?
[16:45] <Keybuk> I've already asked you a question, and suggested something to try
[16:45] <Keybuk> that would be a good start
[16:46] <Madkiss> I oversaw that, can you repeat the corresponding lines please?
 Madkiss: what happens when you do use init=/bin/bash
[16:47] <Madkiss> Keybuk: the last thing I see is "the last thing i see is "b43-phy: UNSUPPORTED PHY FOUND"
[16:47] <Madkiss> Keybuk: and then nothing else happens.
[16:47] <ion> Try with debug=yes init=/bin/bash
[16:47] <Keybuk> ok, try taking "quiet" and "splash" off the kernel command line as well
[16:47] <ion> Let’s see what the initramfs is doing.
[16:47] <kees> soren: only if there's either a bug report for it, or direct code examples.  :)
[16:48] <soren> kees: It's my homebanking thingie. I can file a bug, I gues.
[16:48] <soren> guess, even.
[16:48] <kees> soren: check your .xsession-errors for tracebacks, too.
[16:51] <soren> kees: dead silent. I'll file a bug.
[16:52] <Madkiss> well, erm.
[16:55] <pitti> jdong, cody-somerville: in the light of the archive permissions reorg, are you fine with obsoleting ~motu-sru and getting added to ~ubuntu-sru ?
[16:56] <pitti> jdong, cody-somerville: I'll care about the membership shuffling and updating the process page, but wanted to give you a heads-up
[16:57] <jdong> pitti: sounds like a logical migration path; I'm good with that
[16:57] <Madkiss> booting the box after having been on the grub shell leads to a lockup.
[16:59] <Keybuk> it sounds a lot like you have a kernel problem
[17:01] <Madkiss> *SIGH*
[17:01] <slytherin> kees: There are many bugs open in launchpad about the stuff that doesn't work with openjdk, or simply crases openjdk.
[17:02] <Madkiss> okay. last debug message I see is
[17:02] <kees> slytherin: yup.  I'm trying to improve the quality of said reports.  instead of "it doesn't work", I'm trying to get "this code below, fails this way or that way..."
[17:02] <Madkiss> "exec run-init /mnt/sbin/init"
[17:03] <Madkiss> then a whole lot of "according to mtab blabla foobar is already mountred" messaged
[17:03] <Keybuk> Madkiss: that's not trying with "/bin/bash" now, is it?
[17:03] <Madkiss> no.
[17:03] <Madkiss> wait a second.
[17:03] <slytherin> kees: In any case at this point of time I don't think we should remove sun java6 from archives. We could target that for karmic +1 but I am not sure how good openjdk will be by that time.
[17:04] <kees> slytherin: yup, I would tend to agree now
[17:04] <slytherin> But sure openjdk is in far better shape now than it was in jaunty. It doesn't eat CPU when running javadoc on powerpc. :-)
[17:05] <ogra> Keybuk, is sreadahead running nice'd ? it produces quite some load on the first few boots on armel
[17:05] <Madkiss> the kernel reproducibly just hangs after having been on the grub shell
[17:05] <Madkiss> jeez.
[17:05] <slytherin> ogra: it does on i386 also. :-)
[17:06] <Keybuk> ogra: it runs in more interesting priorities than nice is capable of
[17:06] <ogra> slytherin, i'm lacking experience ... my world is full of arms in karmic :)
[17:07] <Madkiss> hooray for this, i guess.
[17:07] <Madkiss> Keybuk, ion, i am going to report back for duty tomorrow. I actually might slam a screwdriver into this computers display, I am tired as hell.
[17:08] <Keybuk> Madkiss: np.
[17:10] <Madkiss> oh, well
[17:10] <Madkiss> hm.
[17:10] <Madkiss> now I am on a bash at least.
[17:10] <Madkiss> Keybuk: ^^
[17:10] <Keybuk> what did you change to get there?
[17:11] <Madkiss> i edited grub.cfg
[17:12] <Madkiss> mount point /dev/pts does not exist.
[17:12] <Keybuk> what says that?
[17:13] <Madkiss> "mount -a"
[17:13] <Madkiss> and indeed there is no /dev/pts
[17:14] <Madkiss> and the reason for why it might hang during the normal boot process
[17:14] <Madkiss> is that starting nfs-common just fails
[17:14] <Madkiss> or rather
[17:14] <Madkiss> does never come to an ende
[17:14] <Madkiss> well. ttyl.
[17:16] <dee> Hello.
[17:16] <sebner> hihu dee :D
[17:16] <dee> hi sebner. good you're here. :)
[17:17] <dee> do you know what packages in brackets <...> mean if I do "apt-cache depends xutils-dev"?
[17:17] <dee> And how are you btw.
[17:19] <sebner> dee: I'm fine and you? Depends, Conflicts ,..?
[17:20] <dee> Just test the command and you will see what I mean.
[17:20] <dee> And yes. I'm fine too. Are you on Ubucon this year?
[17:22] <sebner> dee: naaah, starting with university. You see the package it Conflicts/Replaces
[17:22] <sebner> huhu jonbo
[17:22] <sebner> *jono
[17:22] <dpm> lool: lool: all UNR karmic translations have been imported into rosetta, and future import won't require manual interaction -> https://lists.ubuntu.com/archives/ubuntu-translators/2009-September/002750.html (sorry for the delay in coming back to you, I've just noticed i didn't CC you on that e-mail)
[17:22] <sebner> jono: HAPPY BIRTHDAY!
[17:22] <sebner> dee:   Replaces: <imake> means it replaces the package image
[17:23] <jono> thanks sebner :)
[17:23] <lool> dpm: cool thanks
[17:23] <dee> sebner: I know the Meaning of replaces, but not for the brackets.
[17:23] <ogra> Keybuk, mind to comment on bug 431963 (i suspect calling sreadahead from cmdline is a bit different than what actually happens during boot profiling)
[17:24] <sebner> dee: ah, wondering now too. Maybe a special feature for Conflicts and Replaces. :P
[17:24] <dee> jono: it's your birthday? so good luck for the future, nice evening (every day of course), have fun and rock on. :)
[17:25] <dee> sebner: no, there are packages with Depends that have brackets.
[17:25] <jono> thanks dee!
[17:25] <Keybuk> ogra: not sure what you want me to comment on?
[17:25] <Keybuk> ogra: his disk is clearly dying
[17:26] <Keybuk> (or his SATA controller)
[17:26] <ogra> difference between running sreadahead and the actual boot
[17:26] <ogra> Keybuk, neither is, thats the prob
[17:26] <ogra> its very likely the kernerl driver we got from freescale
[17:26] <Keybuk> I disagree, he's getting I/O errors from particular sectors
[17:26] <ogra> its reproducable by others with proven good HDs
[17:26] <Keybuk> it could be the SATA driver, yes
[17:27] <sebner> dee: then it may be a bug O_o
[17:27] <Keybuk> sreadahead will cause more I/O in a shorter space of time than a normal boot
[17:27] <Keybuk> is that what you mean?
[17:27] <ogra> Keybuk, fun is, there is no SATA driver :)
[17:27] <dee> sebner: no, ixel has the resolution. this are virtual packages.
[17:27] <Keybuk> ogra: sure there is
[17:27] <sebner> dee: ah good to know
[17:27] <ogra> Keybuk, well, compared to me running sreadahead on a tty i guess there is a difference to what the bootprocess does
[17:27] <Keybuk> ogra: no, not really
[17:28] <ogra> Keybuk, nope, its a hardware bridge
[17:28] <Keybuk> ogra: cat /etc/init/sreadahead.conf
[17:28] <ogra> its SATA->USB
[17:28] <Keybuk> ogra: you'll still have a driver for it
[17:28] <ogra> and the kernel drives it with the special freescale ehci driver
[17:29] <Keybuk> it's still a driver ;)
[17:29] <ogra> sure i do, but its exposed as USB disk to the whole system
[17:29] <ogra> by the HW
[17:29] <ogra> fun is that its even exposed as /dev/sdb if no disk is attached
[17:30] <nixternal> so what is the trick for today in order to get my encrypted /home working again? seems to have changed since yesterday
[17:30] <nixternal> freezes at * Starting sad crypto disks...
[17:33] <jpds> nixternal: bug #430496
[17:33] <nixternal> jpds: ya, yesterday I was able to /etc/init.d/cryptdisks start
[17:33] <nixternal> and all was good
[17:34] <nixternal> today, I can do it, but as soon as I start KDM no keyboard/mouse
[17:34] <nixternal> it doesn't kick off everything like it did yesterday
[17:34] <nixternal> sure there is something else that needs to be started first
[17:35] <pitti> @all: freeze is lifted, go ahead and upload; a6 isn't released yet officially, but we won't re-roll
[17:36] <robbiew> heh
[17:38] <dee> bye
[17:40] <slangasek> ttx: does the errata entry for 430758 look accurate?
[17:43] <slangasek> kirkland: please check the errata text for bug #430820
[17:44] <nixternal> Keybuk: anything I can do on the debug front to help out with anything? I have 2 busted machines waiting for some loving :)
[17:45] <Keybuk> nixternal: I basically think I have to rewrite cryptsetup ;)
[17:45] <nixternal> oooh now that sounds fun :)
[17:45] <kirkland> slangasek: sure ...
[17:46] <kirkland> slangasek: where is this errata text?
[17:50] <nixternal> Keybuk: if i reformat/reinstall with latest release, and don't encrypt, I should be fine right?
[17:50] <nixternal> I might r/r my lappy and leave my desktop broken for debugging purposes
[17:51] <nixternal> i need something other than this netbook up and running right now, otherwise no work gets done :)
[17:51] <Keybuk> nixternal: yeah
[17:51] <siretart> nixternal: FYI, I've just updated my karmic vbox that uses root on crypted lvm and that VM still boots without any problems..
[17:51] <Keybuk> the problems at the moment are cryptsetup and NFS
[17:51] <Keybuk> cryptsetup because it really needs to decrypt devices when udev knows about them, not at an arbitrary point in the boot process
[17:52] <nixternal> ya, I have /, /home, and swap encrypted...can't figure out how to work around it today
[17:52] <Keybuk> (that'd give you big plus points anyway - plug in a USB stick a week after, and it can be still decrypted and mounted from fstab)
[17:52] <Keybuk> NFS because I'm a dolt and didn't upload the portmap/rpc.*d upstart jobs
[17:52] <Keybuk> on the cryptsetup front, if you do fancy finding out why my kludge doesn't work. I'd appreciate it
[17:53] <jdstrand> slangasek: does bug #431804 require an FFe? it is fixing a bug by introducing a feature (upstart script)
[17:53] <jdstrand> slangasek: hi btw
[17:53] <Keybuk> I can't see why the /etc/init/cryptdisks-enable.conf thing doesn't work
[17:53] <nixternal> Keybuk: I am looking at it now...the only thing i can see is "sad" as that is mentioned when the machine freezes
[17:54] <siretart> Keybuk: I see some udev warnings (or errors, not sure) about udev rules during bootup. are you aware of them or are you interested in reports about them? the VM still boots fine, though.
[17:54] <Keybuk> siretart: they are already reported
[17:54] <Keybuk> and I'm aware of them ;P
[17:54] <Keybuk> nixternal: silly question, what happens if you add "console owner" to the top of that job file somewhere
[17:54] <siretart> ok
[17:55] <nixternal> let me try
[17:55] <pitti> siretart, Keybuk: btw, I checked udev trunk, it has the warnings fixed
[17:55] <pitti> we just need to fix the NAME="%k" in the kvm rules
[17:55] <pitti> (/lib/udev/rules.d/45-qemu-kvm.rules)
[17:56] <nixternal> rebooting to try the new change...will let you know
[17:56] <Keybuk> pitti: I know, I talked with kay about it yesterday
[17:56] <Keybuk> the SYMLINK{unique} thing is an actual bug in udev ;)
[17:56] <nixternal> Keybuk: whoa, that did it dude
[17:56] <Keybuk> but that's fixed in git too
[17:56] <Keybuk> nixternal: ...
[17:56] <Keybuk> nixternal: !!!
[17:56] <nixternal> console owner
[17:56] <Keybuk> nixternal: maybe I should just not be allowed to use computers
[17:56] <nixternal> lol
[17:57] <nixternal> damnit, i owe you a big hug!
[17:57]  * nixternal logs into KDE
[17:57] <hyperair> Keybuk: what's wrong with cryptsetup?
[17:58] <Keybuk> hyperair: broken by design
[17:58] <hyperair> Keybuk: meaning?
[17:58] <Keybuk> well
[17:58] <Keybuk> everything else has changed so that the way it's designed is no longer the way other things work
[17:58] <Keybuk> hyperair: it acts on block devices, and creates new block devices
[17:59] <hyperair> right.
[17:59] <hyperair> and what's wrong with that?
[17:59] <hyperair> LVM does the same too
[17:59] <Keybuk> it *should* be designed such that individual block devices are decrypted as a result of uevents
[17:59] <Keybuk> ie. a udev rule calls out to cryptsetup to do its thing
[17:59] <Keybuk> and cryptsetup creates new block devices
[17:59] <Keybuk> which udev then picks up through the kernel again
[17:59] <hyperair> then cryptsetup's initscript is screwed, isn't it?
[17:59] <Keybuk> instead, it expects there to be a single point in the entire boot where "all block devices are visible, and should all be decrypted in one pass"
[17:59] <Keybuk> exactly
[18:00] <hyperair> well then patch it =p
[18:00] <Keybuk> yeah that's what I said
[18:00] <Keybuk> I'm convinced that I already did this a couple of years ago
[18:00] <nixternal> Keybuk: what exactly does 'console owner' provide? I have an idea, just want to know if I am close
[18:00] <Keybuk> at the same time that we moved lvm and mdadm to be called from udev
[18:00] <Keybuk> nixternal: something more useful than /dev/null as stdin
[18:00] <hyperair> well this kind of thing is not going to hit me in any case... my /dev/sda2 *needs* to exist before cryptsetup can decrypt it, and my root's sitting on it so it's done in initrd
[18:00] <nixternal> Keybuk: oh, then I wasn't even close :)
[18:01] <Keybuk> nixternal: what was your idea?
[18:01] <Keybuk> hyperair: right
[18:01] <rgreening> should hal return my unmounted usb drive with this command? hal-find-by-capability --capability storage
[18:01] <hyperair> hal's deprecated isn't it?
[18:01] <nixternal> oh jeesh, put me on the spot, now I will sound/look even more stupid than I already am...I figured it was something like superuser status...the whole owner thing is what got me
[18:01] <Keybuk> ah
[18:01] <hyperair> we're not supposed to not have hal and have to find some other way to dig devices out
[18:02] <Keybuk> console output => connect stdin/out to /dev/console instead of /dev/null
[18:02] <rgreening> hyperair: hmm... what's the correct command for karmic then? hyperair
[18:02] <hyperair> which either doesn't exist or is all over the place so you can't find it anyway
[18:02] <Keybuk> console owner => as output, but invoke secret magic rituals to make ^C work
[18:02] <hyperair> rgreening: look at what i just said
[18:02] <nixternal> gotcha....
[18:02]  * nixternal jots that down to remember it
[18:02] <rgreening> useless commentary
[18:02] <rgreening> lol
[18:02] <hyperair> but it's true!
[18:03] <hyperair> well almost completely true anyway
[18:03] <rgreening> can someone who has something useful to say? :) pitti :)
[18:03]  * hyperair predicts that some years down the road, udev will be deprecated for the same reason hal was. and then we have to populate our /dev manually
[18:04] <siretart> hyperair: that would be a step back
[18:04] <rgreening> well, devkit-disks --enumerate doesn't show my /dev/sdc or /dev/sdc1
[18:05] <kirkland> slangasek: yo?
[18:05] <rgreening> so, what's below hal and devkit-disks (i.e. common)
[18:05] <slangasek> kirkland: https://wiki.ubuntu.com/KarmicKoala/TechnicalOverview
[18:05] <hyperair> siretart: and hal disappearing without some new way of listing all types of hardware isn't a step back?
[18:05] <slangasek> (usual place)
[18:06] <hyperair> i mean come on, i'm still figuring out information from my hard disk using hal-device.
[18:06] <slangasek> jdstrand: I think that's covered by the existing FFe for boot work; you might want to just drop a comment in that bug (and/or open a task)
[18:06] <jdstrand> slangasek: cool, thanks
[18:06] <hyperair> where in udev do i get my hard disk's serial number?
[18:07] <siretart> hyperair: sysfs does still exist, no? writing some graphical voodoo should that hard...
[18:07] <kirkland> slangasek: made two minor modifications to the command to be run; added 'sudo' and the networking service restart
[18:07] <zyga> mvo: ping
[18:07] <hyperair> siretart: yeah, so i'm going to have to spend some time figuring out exactly what all the cryptic names in sysfs mean
[18:08] <hyperair> siretart: it's still a step back. sysfs isn't much better from when hal started imo.
[18:08] <siretart> hyperair: try systool
[18:08] <rgreening> hyperair: udevadm info --query=all --name=/dev/sda
[18:09] <rgreening> switch /dev/sda for your drive
[18:09] <rgreening> hyperair: ID_SERIAL is there
[18:09] <slangasek> mr_pouit, NCommander: cody doesn't appear to be around today; either of you in a position to round up some more xubuntu testing for alpha 6?  we only have tests on 1 of 4 images, which is precisely enough to permit publishing 1 of 4 images with the milestone
[18:10] <slangasek> superm1: mythbuntu doesn't show any test results since the OMGkittens respin; prospects of getting tests in some time today?
[18:10] <hyperair> rgreening: point taken
[18:11] <rgreening> now, if only I could get some help with debugging why my usb drives do not show up in hal nor devkit-disks, but the udev link is there.
[18:11] <rgreening> :)
[18:12] <NCommander> slangasek, I can probably do testing in a little bit, I need to try and force some food down
[18:12] <Daviey> slangasek: yes, i think we can get some done today.
[18:13] <nixternal> note to self: make sure you remove shell.conf after adding 'console owner' to cryptdisks-enable.conf :)
[18:13] <NCommander> slangasek, and w.r.t. to last night, your right, I'm not sure why i was posting a kernel panic that bug; it was a separate issue.
[18:14] <nixternal> NCommander: careful forcing that food down, you might choke :p
[18:15] <nixternal> interesting...I have 3 intel machines, with damn near the same hardware....my netbook is perfect, my lappy I have to do the encrypted work around as with my desktop...my netbook and lappy have compisiting enabled and rocking, my desktop will not do compositing unless I add 'nomodeset' to grub
[18:24] <Laney> this is *weird*
[18:24] <Laney> looks like my fstab is being wiped out on boot
[18:26] <sivang> nice :)
[18:26] <sivang> leaving the system unusable ?
[18:26] <Laney> naturally
[18:26] <sivang> :)
[18:27] <Laney> so I get kicked to this bash prompt, remount the drive rw and my changes in /etc don't stick
[18:28] <Laney> but I can save stuff in /root which is on the same partition
[18:29] <jono> I am trying to upgrade my karmic machine by booting from my USB stick, chrooting my local disk and doing the upgrade, but apt-get doesnt see the repos - any idea why?
[18:30] <MsMaco> jono: can the chroot reach the net?
[18:30] <jono> MsMaco, it seems not
[18:31] <jono> any idea how I make it do that?
[18:31] <MsMaco> jono: maybe make an aptoncd iso and loop mount it over a spot below your chroot'd ?
[18:31] <MsMaco> chroot'd /?
[18:31] <MsMaco> (too much that key)
[18:32] <jono> hmmm
[18:33] <jono> is there a way to get the chroot to the see the net?
[18:33] <zyga> jono: mount proc?
[18:33] <Daviey> jono: you need to bind proc ?
[18:33] <jono> how do I do that?
[18:33] <zyga> jono: and remember /etc/passwd
[18:33] <Laney> mount -o bind /proc proc
[18:34] <jono> still no net
[18:34] <jono> also:
[18:34] <jono> root@ubuntu:/# ifconfig
[18:34] <jono> Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
[18:34] <zyga> jono: sdhh.. /etc/resolv
[18:34] <zyga> jono you need to use mount -o bind from _outside_
[18:34] <zyga> not from the chroot itself
[18:34] <jono> ahhh
[18:34] <Laney> I don't need to do that to be able to aptitude update from a chroot, fwiw
[18:34] <Daviey> jono: where is the disk mounted?
[18:35] <jono> buntu@ubuntu:~$ sudo mount -o bind /proc proc
[18:35] <jono> mount: mount point proc does not exist
[18:35] <chrisccoulson> i normally do "mount -t proc proc /mnt/chroot/proc" rather than bind mount
[18:35] <jono> Daviey, /media/disk
[18:35] <Daviey> sudo mount -t proc none /media/disk/proc
[18:35] <zyga> jono: mount -o bind /proc /path/to/chroot/proc
[18:35] <Laney> all works ;)
[18:35] <jono> ok now ifconfig gives me output
[18:35] <Daviey> \o/
[18:35] <jono> but still no net in the chroot
[18:36] <Daviey> jono: ping 74.125.127.100
[18:36] <jono> Daviey, pings fine
[18:36] <Daviey> jono: you need to sort out your resolv.conf
[18:37] <Daviey> jono: cp contents of /etc/resolv.conf to inside chroot.
[18:37] <Daviey> host to chroot.
[18:37] <chrisccoulson> this is why i use schroot - you can make it dynamically copy files like that in to the chroot automatically
[18:38] <jono> Daviey, so copy my host resolv.conf to the /etc/resolv.conf in the chroot?
[18:38] <chrisccoulson> and also automatically mount all the important filesystems
[18:38] <chrisccoulson> jono - yes
[18:38] <Daviey> jono: yeah.
[18:39] <Laney> this is so weird
[18:39] <chrisccoulson> Laney - ?
[18:39] <jono> yay!
[18:39] <Laney> I made /etc/fstab and /etc/fstab.bak from a live cd
[18:39] <jono> thanks folks
[18:39] <Laney> then rebooted, and now they are both empty
[18:39] <Laney> but the files are there
[18:39] <jono> lets see if this fixes karmic now
[18:39] <chrisccoulson> Laney - did you unmount the filesystem properly?
[18:39] <Laney> yeah
[18:39] <jono> erk
[18:39] <chrisccoulson> that is wierd
[18:39] <jono> root@ubuntu:/etc# apt-get update
[18:39] <jono> Get:1 http://archive.ubuntu.com karmic Release.gpg [189B]
[18:39] <jono> Ign http://archive.ubuntu.com karmic/main Translation-en_US
[18:39] <jono> Ign http://ppa.launchpad.net karmic Release.gpg
[18:39] <jono> 89% [Working]FATAL -> Could not set non-blocking flag Bad file descriptor
[18:39] <jono> E: Method http has died unexpectedly!
[18:39] <Laney> this happens when I do it from the rescue shell too
[18:40] <Laney> i'll try again to be sure
[18:40] <jono> any idea what that is?
[18:41] <jono> Daviey, have you seen that before?
[18:42] <chrisccoulson> jono - not sure. but did you mount /dev and /sys in your chroot too?
[18:42] <chrisccoulson> (i'm not sure if that would cause your issue though)
[18:42] <jono> reading http://michael-prokop.at/blog/2007/10/27/could-not-set-non-blocking-flag/ now
[18:44] <Daviey> jono: no :)
[18:45] <Daviey> sudo mount -o bind /dev /media/disk/dev
[18:45] <jono> I think I have it fixed
[18:45] <Daviey> win
[18:45] <jono> I did a: sudo mount -o remount,dev /dev/sda1
[18:45] <jono> managed to update the package list
[18:46] <jono> now downloading updates
[18:46] <jono> hopefully this won't bugger anything up
[18:47] <Laney> spammed sync
[18:47] <Laney> lets try again
[18:48] <jono> hmmm it says Can not write log, openpty() failed (/dev/pts not mounted?)
[18:48] <Daviey> jono: see the line above, you need to bind /dev to /media/disk/dev
[18:49] <jono> just done that
[18:49] <cjwatson> openpty message is harmless
[18:49] <cjwatson> it just means dpkg's terminal output won't be logged properly
[18:50] <jono> ok here we go :)
[18:50] <Laney> Well fstab exists now but still get kicked to this dodgy shell
[18:50] <cjwatson> I don't think bind-mounting /dev automatically binds mounts on subdirs too
[18:50] <cjwatson> you need --rbind for that
[18:51]  * hyperair takes note of rbind
[18:52] <Laney> http://launchpadlibrarian.net/31955810/17092009299.jpg if anyone wants to poke
[18:53] <Daviey> cjwatson: "all possible submounts", does that mean locations mounted are also bound?
[18:55] <cjwatson> well, /dev/pts is a separate mount on a subdirectory of /dev, you see
[18:57] <chrisccoulson> Laney - does your machine just boot to that without you doing anything?
[18:57] <Laney> yes
[18:58] <Laney> I thought it was because of the empty fstab, but apparently not
[18:58] <nixternal> Laney: you added '/etc/init/shell.conf' I take it?
[18:58] <chrisccoulson> hmmm, this might sound like a really silly question, but you're not booting with "init=/bin/bash" by any chance are you? it just looks like its starting a bash shell without trying to do anything else
[18:59] <Laney> chrisccoulson: ... well I tried that once
[18:59] <Laney> if grub saves it, then maybe
[18:59] <nixternal> init=/bin/bash wouldn't give you @hostname and would give you @(none)
[18:59] <nixternal> iirc
[18:59] <Laney> and I'll feel like an idiot
[18:59] <Laney> nixternal: I don't know what that is
[18:59] <Laney> chrisccoulson: nah, no doing
[18:59] <Laney> ...wait
[19:00] <Laney> slangasek had me add "bash" to the mountall config last night
[19:00] <nixternal> well there you go (I think) :)
[19:00] <Laney> lets try
[19:02] <skatteola> My boot dies (possibly unrelated for all I know) after I get a bunch of "mountall: <afewcharsofgarbage>: Read-only file system", "mountall: <afewcharsofpuregarbage>/sndstat: No such file or directory".. Where is it getting the broken paths?
[19:02] <Daviey> "no job control in this shell", i normally see when someone has screwed their permissions/ownership of ~
[19:03] <Laney> nope, the bash thing was it
[19:03] <Laney> nixternal, chrisccoulson: Thanks for the inspiration :)
[19:03] <skatteola> (actually it gets a bit further than that, mounting some fs's and then dies.)
[19:04] <chrisccoulson> Laney - you're welcome
[19:04] <nixternal> aww, I am inspiring \o/
[19:04] <chrisccoulson> did it boot ok now?
[19:04] <Laney> yeah
[19:04] <nixternal> groovy :)
[19:04] <chrisccoulson> Laney - you just need some more updates to break it again now;)
[19:05] <Laney> this is only a bandaid system anyway - hit on a udev/util-linux bug yesterday which meant I couldn't have / on an mdadm array :)
[19:05] <Laney> the fun of testing
[19:05] <jono> back up and running
[19:05] <jono> thanks folks :)
[19:05] <jono> seb128, still have the issue with no window manager and panels
[19:05] <chrisccoulson> hey jono - are they not running, or just running but frozen?
[19:05] <nixternal> jono: kde is working fine...ahh the good ol' days, remember them birthday boy?
[19:05] <nixternal> ;p
[19:06] <jono> chrisccoulson, panels are running, but not showing - when I killall them they show
[19:06] <jono> I have to run metacity --replace to get a window manager
[19:07] <chrisccoulson> hmmm, i've not seen that issue before
[19:07] <jono> interestingly, I clicked the button in the startup apps window to save current opened apps, one of which is tomboy which keeps loading but I don't see it in the list of startup apps anymore
[19:07] <robbiew> jono: i had this after my first reboot (no panels)...but it was magically fixed in subsequent reboots
[19:11] <Laney> what will happen to the UUID if I resize a partition?
[19:12] <robbiew> has anyone with boothchart installed, noticed an 'sreadahead -t0' process running after the machine is up? on every reboot?
[19:12] <cjwatson> Laney: ought to be preserved
[19:12] <Laney> cool
[19:12] <Laney> seems windows 7 still wants to be the first partition :(
[19:13] <chrisccoulson> heh, i don't have the hassle of dual-boot any more:)
[19:14] <Laney> I only dual for l4d and tf2
[19:14]  * Laney donates to wine
[19:14] <chrisccoulson> Laney - you're in to gaming are you?
[19:15] <Laney> chrisccoulson: only casually - I'm really not very good :)
[19:15] <chrisccoulson> i thought i would try gaming when i purchased my graphics card, but then i never bothered with it;)
[19:16] <chrisccoulson> so its a bit wasted now
[19:16] <Laney> CUDA!
[19:21] <hyperair> frets on fire!
[19:21] <hyperair> that runs on my intel =D
[19:22] <pitti> pochu_: wow, that was fast: http://packages.qa.debian.org/m/media-player-info.html
[19:26] <hyperair> huh what happened to debhelper?
[19:26] <hyperair> http://launchpadlibrarian.net/31978323/buildlog_ubuntu-karmic-amd64.banshee_1.5.1%2Bgit20090916.r2.2d2d42f-0ubuntu1_FAILEDTOBUILD.txt.gz
[19:27] <hyperair> it isn't supposed to add a debian/tmp to debian/<blah> paths is it?
[19:27] <hyperair> dh_install, that is
[19:29] <pitti> hyperair: it only does that in compat level 6 and above, I think
[19:29] <hyperair> i've never had this with compat level 7
[19:29] <pitti> sorry, from 7 on
[19:29] <hyperair> for starters, i've been using this debian directory for several weeks now, and a cronjob preparing builds
[19:29] <hyperair> or rather, alarm-clock-applet
[19:30] <cjwatson> hyperair: man debhelper, look at the "Debhelper compatibility levels" section
[19:30] <hyperair> cjwatson: i'm familiar with those.
[19:30] <cjwatson> "dh_install, will fall back to looking for files in debian/tmp if it doesn't find them in the current directory (or wherever you tell it look using --sourcedir). This allows dh_install to interoperate with dh_auto_install, which installs to debian/tmp, without needing any special parameters."
[19:30] <hyperair> cjwatson: but it's not supposed to prepend debian/tmp unless it can't find them in the current directory.
[19:30] <cjwatson> is it possible that in this case perhaps it can't?
[19:30] <hyperair> why wouldn't it be able to?
[19:31] <cjwatson> maybe something failed to compile, but the build system didn't notice?
[19:32] <hyperair> http://launchpadlibrarian.net/31974709/banshee_1.5.1%2Bgit20090915.r1.ba07145-0ubuntu1_1.5.1%2Bgit20090916.r2.2d2d42f-0ubuntu1.diff.gz <-- behold the existence of debian/Banshee.GStreamer.dll.config
[19:32] <cjwatson> is that file really meant to be in debian/ ?
[19:32] <cjwatson> oh
[19:32] <hyperair> no wait
[19:32] <cjwatson> err, no
[19:32] <hyperair> lemme stare at it again
[19:32] <cjwatson> I DON'T behold its existence
[19:33] <cjwatson> I behold a patch that explicitly and specifically *removes* it
[19:33] <cjwatson> @@ -1,3 +0,0 @@
[19:33]  * hyperair groans
[19:33]  * hyperair bangs head on wall
[19:34] <Laney> haha
[19:35] <hyperair> what went wrong with my script?
[19:36] <hyperair> hmph. it's still in the git repository..
[19:36] <jcole> we have hundreds of network printers.. and with ubuntu jaunty, i could go to add printer to see all the network printers and easily select the one i want... but with karmic, it *only* shows the model now and no longer the ip, so i have no idea which printer im selecting since the same model is all throughout the network... how do i show the ip like jaunty used to do so i can select the right printer?
[19:37] <hyperair> ...aha. damn you, you stupid .gitignore
[19:39] <jcole> ive browsed every option in the printer configuration gui and cant seem to find it out how to re-enable the ip... do i have to dtrop to a prompt and edit cups config files? or is there something hidden in gconf?
[19:44] <tkamppeter> jcole, I did not change anything, seems to be a problem of the new CUPS 1.4.
[19:47] <jcole> tkamppeter: ok, thanks for the update... i got it working by walking over to the printer, writing down its info, and manually adding it to the gui
[19:47] <jcole> tkamppeter: if this doesnt get fixed, there is really no use of having a dropdown of scanned network printers if you are on a large network (since you cant determine which printer you are selecting)
[19:47] <tkamppeter> jcole, I do not see any difference between Jaunty and Karmic, for me the printers in the list show without IP in both versions. If it is a non_HP printer, you should see the IP on the right when you click on the printer.\
[19:48] <jcole> tkamppeter: i work for hp and they are *all* hp printers, lol
[19:48] <jcole> tkamppeter: perhaps i need to install an hplip lib?
[19:49] <tkamppeter> If it is an HP printer you have to click on "Connection", then choose AppSocket you see also the IP, but this is awkward.
[19:49] <jcole> tkamppeter: jaunty used to show the ip
[19:49] <tkamppeter> jcole, I have also only HP printers, as I get them from HP for testing.
[19:50] <jcole> tkamppeter: i just look on my laptop which is jaunty, it shows the ip... want a screenshot?
[19:50] <tkamppeter> jcole, does the web interface (localhost:631) or hp-setup show the IPs?
[19:51] <jcole> tkamppeter: on which? my karmic or jaunty install?
[19:51] <tkamppeter> On Karmic
[19:52] <tkamppeter> jcole, by the way, are you working together with David Suffield or Shiyun Yie?
[19:52] <rent0n> hello
[19:52] <jcole> tkamppeter: im not sure where i go here to scan for network printers...
[19:53] <rent0n> I've got one question: how do i understand wich verion of a specific package will be present in karmic?
[19:54] <rent0n> *which version
[19:54] <jcole> tkamppeter: heh, yes, david and shiyun both work for hp in vancouver, wa .. ive seen them in our internal linux irc rooms
[19:55] <tkamppeter> jcole, the web interface also scans the network, you must go to "Administration", then click "Find new printers".
[19:55] <jcole> rent0n: packages.ubuntu.com/packagename
[19:55] <rent0n> I mean in jaunty the tint2 package is 0.6, so i expected to find 0.7 in karmic but if i look for tint2 on packages.ubuntu.com it says tint2 will be 0.6 in karmic
[19:55] <tkamppeter> jcole, where are you located?
[19:56] <rent0n> so i just wanted to know if this is a defintive choice
[19:56] <jcole> tkamppeter: hp corporate in palo alto, ca
[19:56] <jcole> tkamppeter: it says no printers found
[19:56] <blueyed> Keybuk: I'm experiencing bug 432052 - how can I help debug this? are you working on (another) cryptsetup fix?
[19:56] <rent0n> or maybe it is possible that you will put the 0.7 version before releasing karmic
[19:56] <Keybuk> busybox?  that's in the initramfs then?
[19:56] <blueyed> yes
[19:56] <Keybuk> nothing to do with me, then :p
[19:57] <jcole> tkamppeter: localhost:631 looks different in jaunty... looks like the old school cups web in jaunty
[19:57] <blueyed> Keybuk: ? cryptsetup fails to mount the root device?!
[19:57] <Keybuk> blueyed: yes, but it's before init gets started
[19:57] <Keybuk> so nothing I touched could break that
[19:57] <tkamppeter> jcole: I get the same in Karmic, in Jaunty it works, and even shows IPs. but it does not automatically use the HPLIP backend.
[19:57] <Keybuk> unless it was already broken in some way
[19:58] <tkamppeter> Seems that in CUPS 1.4 they broke the web interface completely.
[19:58] <jcole> tkamppeter: yep, same here, jaunty finds the printers in the web interface with the ips
[19:59] <blueyed> Keybuk: uh.. it asked for a passphrase until yesterday.. I'd say until your cryptsetup upload. But good to know that init isn't started yet there. OTOH: you might have broken the initramfs then.. :P
[19:59] <rent0n> uh?
[19:59] <rent0n> someone can tell me how the thing works?
[19:59] <Keybuk> blueyed: don't see how
[19:59] <blueyed> Keybuk: it does not ask for a passphrase anymore.
[19:59] <hyperair> how do you not have init started?
[19:59] <debfx> blueyed: maybe it's fixed by https://edge.launchpad.net/ubuntu/+source/cryptsetup/2:1.0.6+20090405.svn49-1ubuntu4
[19:59] <blueyed> Keybuk: lemme check.
[19:59] <Keybuk> hyperair: he's still in the initramfs
[20:00] <hyperair> Keybuk: isn't init started there?
[20:00] <Keybuk> hyperair: no
[20:00] <hyperair> Keybuk: i mean, isn't udev started there even?
[20:00] <hyperair> =O
[20:00] <tkamppeter> jcole, hp-setup in Karmic does not show IPs, as it uses DNS-SD for identifyinmg and distinguishing network printers.
[20:00] <blueyed> debfx: maybe.. I do not have ubuntu4 here yet. Thanks!
[20:01] <tkamppeter> jcole, in Jaunty is shows IPs.
[20:02] <jcole> tkamppeter: yes, same here
[20:02] <pochu_> pitti: it seems the new ftp assistants are doing their job ;)
[20:03] <jcole> tkamppeter: im installing the hplip-gui to see if that has network scanning
[20:03] <tkamppeter> jcole, you should report a bug on system-config-printer about displaying IPs.
[20:03] <blueyed> will try that. b"r"b.
[20:08] <smoser> slangasek, are you around ?
[20:08] <rent0n> ok thank you in any case
[20:09] <rent0n> maybe it's a too difficukt question
[20:11] <jcole> rent0n: if you really need it, download it from packages.debian.org/tint2 and take your chances
[20:12] <rent0n> jcole: i just wanted to know if there is a chance of getting an upgrade in tint2 package before karmic release of it's confirmed that the version will be 0.6
[20:12] <rent0n> just to know
[20:16] <blueyed> Keybuk: ubuntu4 fixed the keyphrase input. Unfortunately, it still fails. I'll upload screenshots. (Thanks, debfx)
[20:24] <jcole> karmic got angry and was running slow... hopefully this reboot will make it happy
[20:33] <stgraber> Keybuk: attached mountall --debug output
[20:34] <Keybuk> to?
[20:34] <stgraber> Keybuk: bug 431204
[20:35] <Keybuk> huh
[20:41] <blueyed> Bug 432070 is my current state.. still not booting. I'll look into manually fscking in the chroot, but would like to have some feedback before trying the does-not-boot-back-to-LiveCD mambo.
[20:42] <slangasek> smoser: hi
[20:46] <LaserJock> slangasek: how long do we have to confirm testing for Alpha6?
[20:46] <slangasek> LaserJock: < 1.5h if it's going to be included in the announcement mail
[20:47] <LaserJock> ok then
[20:47] <LaserJock> slangasek: I've got a good review for i386 but haven't confirmed amd64 yet
[20:47] <slangasek> < 1h13, actually
[20:50] <jcole> tkamppeter: i downgraded cups to what is in jaunty-updates and it works perfectly :)
[20:52] <jcole> tkamppeter: not sure if this is useful, but this is the cups.conf diff -> http://pastebin.ca/1570037
[20:56] <Keybuk> stupid question of the week
[20:56] <Keybuk> but how the hell do you file a bug?
[20:56] <seb128> Keybuk, ubuntu-bug component
[20:56] <cjwatson> +filebug?no-redirect if you don't want to use ubuntu-bug
[20:56] <Keybuk> ugh
[20:56] <cjwatson> it's an "experiment"
[20:57] <Keybuk> can't they just check whether you're a bug contact and let you file bugs on your own damned packages?
[20:57] <cjwatson> you'd think
[20:57] <Laney> One of the proposals is to let bug-control members file bugs directly but redirect for others
[20:57]  * Keybuk files a bug on malone
[20:57] <Keybuk> Laney: if I'm a bug contact, I should be able to file bugs on my own packages for my own reasons
[20:58] <Laney> of course, launchpad shouldn't get in the way
[21:02] <robmur> Hi everyone
[21:02] <robmur> When is alpha 6 due to be released?
[21:04] <robbiew> about an hour
[21:05]  * davmor2 giggles about an hour pff
[21:05] <robbiew> :D
[21:06] <robmur> Great, thanks.
[21:06] <slangasek> davmor2: things not done in an hour may not get included, our website support goes home for the day then
[21:06] <jcole> tkamppeter: what is interesting is line 29 and lines 87-116
[21:08] <davmor2> slangasek: mostly done now last 2 tests on xub
[21:08] <jcole> robmur: https://wiki.ubuntu.com/KarmicReleaseSchedule
[21:10] <davmor2> slangasek: beside in an hour I want to be in bed :)
[21:10] <slangasek> davmor2: then it's perfect timing! :)
[21:11] <LaserJock> if anybody feels like some last minute testing the Edubuntu DVD needs testing on amd64
[21:14] <tkamppeter> jcole: I have found the origing of the problem, it is not your config, simply run
[21:14] <tkamppeter> /usr/lib/cups/backend/snmp
[21:15] <tkamppeter> on Jaunty and on Karmic and compare the output.
[21:15] <tkamppeter> Try the same with
[21:15]  * Keybuk chuckles with delight
[21:15] <tkamppeter> /usr/lib/cups/backend/dnssd
[21:15] <Keybuk> that's made my day
[21:15] <Keybuk> The 'status' command expects any of the following arguments:
[21:15] <Keybuk> new, incomplete, invalid, wontfix, confirmed, triaged, inprogress, fixcommitted, fixreleased
[21:15] <Keybuk> Failing command:
[21:15] <Keybuk>     status udev
[21:15] <Keybuk> bwahahaha
[21:16] <ion> Hehe
[21:16] <cjwatson> I'm pretty sure I remember warning that the "prefix commands with spaces" approach to e-mail commands would go wrong
[21:16] <cjwatson> in about 2004
[21:16] <cjwatson> or maybe 2005
[21:17] <Keybuk> ;)
[21:17] <tkamppeter> jcole: Both backends have put the IP into the human-readable output string (second string in quotes) in CUPS 1.3 (Jaunty) and not any more in CUPS 1.4 (Karmic). -> Regression.
[21:19] <jcole> tkamppeter: ah, does this apply to all the backends?
[21:19] <jcole> tkamppeter: s/does this/does this bug/
[21:20] <jcole> $ ls /usr/lib/cups/backend/
[21:20] <jcole> beh bluetooth cups-pdf dnssd hp hpfax http ipp lpd parallel scsi serial smb snmp socket usb
[21:23] <jcole> $ apt-file search /usr/lib/cups/backend
[21:23] <jcole> bluez-cups cups cups-dbg cups-pdf foomatic-filters hal-cups-utils hplip hplip-dbg hpoj mtink smbclient
[21:35] <jcole> tkamppeter: thank you for looking into this for me
[21:40] <jcole> tkamppeter: should i still submit the bug? or are you going to create a more detailed bug report
[21:54] <superm1> slangasek, sure can ask the guys to try to get some in today.  we've been holding up with all the archive churn
[21:54] <slangasek> superm1: sorry for the churn; we settled that all out yesterday evening, though, and the good candidates have been posted and waiting for testing
[21:54] <superm1> ok
[21:55] <slangasek> everything is ready to publish except mythbuntu, actually
[21:58] <superm1> slangasek, i assume everyone else just went out without a usplash then?
[21:59] <slangasek> superm1: yes
[21:59] <pitti> sebner: still here?
[21:59] <sebner> pitti: yep, but not for long
[21:59] <slangasek> (and usplash seems kinda generally broken right now in my own testing, so I don't think you should sweat that)
[21:59] <pitti> sebner: building a new libatasmart with the blacklisting now
[21:59] <pitti> sebner: do you have amd64 or i386?
[21:59] <sebner> pitti: i386
[22:00] <pitti> sebner: uploaded a fix to karmic now
[22:00] <pitti> sebner: I'd be grateful for testing feedback
[22:00] <pitti> sebner: ok, then we need to wait for the buildds :)
[22:02] <sebner> pitti: I happily test the fix but tomorrow if you don't mind
[22:02] <sebner> pitti: it's also late in germany AFAIK :P
[22:02] <pitti> sebner: oh, you aren't in .de?
[22:03] <sebner> pitti: hmm, I know that you have loads of stuff to do and get to know many people but I told you pretty often that I'm from .at :P
[22:03] <pitti> oh, you did? sorry
[22:03] <pitti> well, timezone wise that doesn't matter
[22:04] <sebner> pitti: np. yeah I know ;-P
[22:04] <pitti> sebner: https://edge.launchpad.net/ubuntu/+source/libatasmart/0.14-1ubuntu1/+build/1247755 -> building now
[22:04] <pitti> in a few minutes you can grab the .deb from there
[22:04] <pitti> sebner: but nevermind, if you are about to go to bed, you can just as well dist-upgrade tomorrow morning :)
[22:05] <sebner> pitti: heh, yeah. I'm really sorry. The first thing I'll do is a dist-upgrade (after getting up in the morning), what kind of feedback do you need then?
[22:06] <pitti> sebner: just whether it works normally, with all local hacks removed
[22:06] <pitti> you shouldn't get USB resets any more
[22:06] <sebner> pitti: no difference between blacklisting and moving rule 95 aside :P
[22:07] <pitti> sebner: right, but it's supposed to work in a default install without messing with the rules :)
[22:07] <sebner> pitti: We'll see. gn8 for now!
[22:08] <mneptok> g'nate?
[22:08] <pitti> sebner: gute Nacht!
[22:09] <slangasek> mneptok: no, g'nhuit
[22:09] <cjwatson> hey, that nearly works in French
[22:09] <cjwatson> do French people say bn8?
[22:09] <slangasek> they say n8
[22:10] <superm1> cjwatson, has the upstart ubiquity job actually been checked?  at least for mythbuntu, it's looking like at the end of ubiquity when pressing restart there is an endless loop of what looks like the gdm and ubiquity jobs fighting to spawn,stop and restart themselves over and over
[22:10] <cjwatson> I checked that it worked on startup; I didn't get far enough to check it on restart, because it was obscenely late
[22:10] <mneptok> slangasek: in sebner's case, i imagine "gute n'acht"
[22:12] <cjwatson> the ubiquity job could check whether it's already run once, but that feels like a massive hack. I'm sure upstart has a better way to do that
[22:14] <cjwatson> maybe it needs 'normal exit 1' or something?
[22:14] <cjwatson> or 'normal exit 0 1', not quite sure from the docs
[22:14] <cjwatson> Keybuk: ^- any thoughts?
[22:15] <superm1> cjwatson, http://imagebin.org/64289 trying to pause virtualbox inbetween runs it looks like its not just ubiquity constantly respawning, but gdm too
[22:16] <cjwatson> superm1: gdm respawning would kick off ubiquity
[22:16] <superm1> ah
[22:16] <cjwatson> and we know gdm is set to respawn
[22:17] <cjwatson> though switching to runlevel 0/6 should stop it
[22:20] <tkamppeter> jcole, simply report the bug, I will add what is missing.
[22:20] <jcole> tkamppeter: cool beans
[22:50] <robbiew> whoohoo!
[23:04] <c_korn> is karmic in a happy state again ?
[23:05] <robbiew-afk> happy as it will be for this release ;)
[23:06] <c_korn> have those upstart bugs been fixed? I was not able to boot the last time. then I purged the virtual machine completely
[23:14]  * mneptok takes the plunge and runs update && upgrade && dist-upgrade for the first time in a week
[23:14] <Lure> mneptok: coward ;-)
[23:16]  * Laney hopes it gets at least two bugs happier...
[23:51] <Amaranth> as long as you don't have file systems on a network it should work great
[23:51] <Amaranth> if you do I think the answer is "maybe"
[23:51] <Amaranth> same with encrypted disks, from what I hear
[23:51] <Laney> and booting from mdadm
[23:52] <Amaranth> yeah, basically you better only have things ubiquity lets you setup during install