[00:00] heh, doubt it; the sequence leading up to it was non-trivial (and was a result of bugs) [00:00] mdz: well, i could be just impatient [00:00] mdz: its still doing stuff [00:00] I've tended to see that before with "expect daemon" and SIGCHLD handlers [00:00] e.g. avahi [00:01] mdz: dd, specifically [00:01] I guess you could get it with "expect fork" as well in that situation [00:01] actually, if you had expect fork, the service daemonised instead of just forking, and put a SIGCHLD handler in - you could probably get that [00:01] mmk [00:02] Keybuk: gdm is stopped due to a runlevel change; it would be nice if that information were passed on [00:02] let me reboot (I /think/ I haven't broken my own boot sequence... :) and try again [00:02] cjwatson: I'm just trying to figure out in my head whether "export RUNLEVEL" in gdm.conf would work ;) [00:03] happy to try it at some point [00:03] I don't think it would [00:03] I think you can only export start environment [00:03] so you could know the runlevel gdm was in when it started ;) [00:03] useful ;) [00:04] mdz: keeping a chronicle in https://bugs.edge.launchpad.net/ubuntu/+source/eucalyptus/+bug/439288 [00:04] Launchpad bug 439288 in eucalyptus "1.6~bzr854-0ubuntu13 fails to run instances" [High,Triaged] [00:04] though the stop environment stuff is all a bit broken [00:04] it seemed like a good idea at the time [00:05] (e.g. upstart doesn't even pass the exit code to the post-stop script) [00:05] actually, is there any reason why all events shouldn't just come with the current runlevel attached? [00:06] yes [00:06] upstart doesn't implement runlevels [00:06] ;) [00:06] you can get the information anyway in a script, but it would allow you to match on them ... [00:06] by that, I mean that the init daemon doesn't implement them [00:06] it never knows what the runlevel is [00:06] or even what *a* runlevel is [00:06] yeah [00:07] oh well. awkward. [00:07] it's all done by the passing of events [00:07] I suppose I want to be able to match on runlevel [06] as a state [00:07] right, exactly! [00:07] and that's definitely going to happen [00:07] * cjwatson remembers an old spec with edge-triggered and level-triggered events ... ;-) [00:08] it's funny you say that [00:08] I remarked only last week how most of the work for upstart 0.10 is putting back in all the things we dropped out of the original design [00:08] you're going to tell me I argued you out of including level-triggered events now, aren't you [00:08] which is entirely possible, although I've forgotten it if I did :) [00:08] no, I think that was mdz [00:09] they "confused" people at the original Wiesbaden demo [00:09] of course, in practice, we removed the wrong ones [00:10] running runlevel is an adequate hack for now, anyway, it's just inefficient [00:11] yeah, it is ineffecient - but that's basically all upstart would be doing itself [00:11] (until we get a runlevel state to replace the event) [00:11] right, until it remembers the state of course === yofel_ is now known as yofel [00:18] hmm [00:19] Keybuk: how is 'env' supposed to work? Is there a document I should be looking at that tells me the available commands? [00:20] man 5 init ? [00:20] heh [00:21] doesn't show up under 'man -k upstart', does it :) [00:21] debmany upstart [00:27] mdz: \o/ \o/ \o/ [00:27] slangasek: no, but if you read the upstart(7) overview page, it'd tell you :p [00:27] mdz: RESERVATION r-31500705 admin default [00:27] INSTANCE i-3BEB06F3 emi-D5871527 192.168.0.250 172.19.1.2 running mykey 0 m1.xlarge [00:27] 2009-09-30T22:37:49.042Z canyonedge eki-8F0A139D eri-E64F14E8 [00:28] Processes managed by init are known as jobs and are defined by files in [00:28] the /etc/init directory. See init(5) for more details. [00:28] heh [00:32] just saying [00:32] * Keybuk rofls [00:32] I just did apropos -h [00:33] cjwatson: I think you may have a gettext bug there ;) [00:33] _("") does not do what you might think [00:34] ooo [00:34] I want to translate that now [00:34] lifeless: it's the header of the .po file I assume [00:35] probably done [00:35] printf ("%s\n, _("")); [00:35] ^" [00:35] damn, one space off [00:47] Keybuk: ho-hum, seems to be reproducible with both 'fork' and 'daemon'; continuing to debug [00:47] (in the meantime, fixed my terribly-wrong rpc_pipefs job) [00:50] Keybuk: however, the same thing doesn't happen without langpacks in Debian, even with remarkably similar-looking .mo files [00:50] Keybuk: so I think it may actually be a bug in our langpack integration [00:51] (anyway, the code that's doing _("") is in gnulib, I think, rather than code I wrote directly) [00:54] I've seen that before, it was a while back - never got round to tracing it all the way down though [00:54] fr.po [00:54] msgid "" [00:54] msgstr "le " [00:59] cjwatson: maybe we're accidentally ending up with that string in the .mo file [00:59] dunno whether you ordinarily do or don't [01:00] I msgunfmt'ed the two .mo files, it's there in both langpack and non-langpack cases [01:05] I do know what's causing it, it's that I have argp doc strings that start with a \v (\v is a separator for pre- and post- doc strings in argp-ese) [01:05] but I consider it a bug in the argp implementation in gnulib that it doesn't deal with that properly [01:05] one day I'll get round to sending them a fix for that [01:06] still mystifying that it only happens with langpacks, though [01:07] hmm, though I think I see a workaround [01:07] yeah, there we go [01:09] Keybuk: aha, got it; upstart isn't happy with me if my script spawns a number of short-lived subprocesses, then execs the daemon, which forks [01:09] so a pre-script fixes this [01:09] hah [01:09] yes [01:10] this is probably user error, but OTOH, it would be good for init to not get wedged [01:10] indeed [01:10] there's no solution to that using ptrace() though [01:10] that's why I plan to switch to using proc_connector [01:11] Keybuk: worked around, http://bzr.savannah.gnu.org/lh/man-db/trunk/revision/1148 [01:23] Keybuk: ok, and in the case of statd, the daemon itself spawns a subprocess before it detaches [01:24] Keybuk: how do I make /that/ work? [01:24] meh [01:24] I don't think you can\ [01:24] not without patching the code [01:24] you could make statd raise (SIGSTOP); [01:25] and use "expect stop" [01:25] instead of making it fork [01:25] whee [01:25] or I could pass the -L argument to tell it not to call sm-notify [01:26] ;) [01:26] so yeah, it probably got fixated on sm-notify [01:26] and then never got SIGCHLD for it [01:27] anyone have an Ubuntu CD/USB, a SD card, and a willingness to destroy whatever data is on it? [01:30] evand: sure [01:30] evand: usb stick [01:31] kirkland: cool. Can you boot from the USB stick and try to install to the SD card with ubiquity? [01:31] I probably should've mentioned you'll need at least a 2.3GB SD card [01:31] it may explode when it gets to grub-installer. Either way I'm happy. [01:32] the SD card may explode? [01:32] evand: hmm, all i have is 2GB cards [01:32] damn [01:32] thanks the same [01:32] evand: sorry [01:32] no worries. Worst case I head to argos/currys tomorrow [01:36] err actually, that won't work [01:41] pitti: ping [01:42] yuriy: He is likely not around at the moment. I suggest either emailing him or simply leaving a message for him on IRC and waiting till he responds. [02:06] nevermind about the SD card. I found a machine that can read SDHC. [02:27] what's the magic rune for changing the privacy of a bug in the new Launchpad UI? [02:28] edit icon next to "This report is private", top right? === cjwatson_ is now known as cjwatson [02:33] hrm, if you build a custom kernel via https://wiki.ubuntu.com/KernelTeam/GitKernelBuild, you do not see /proc/filesystems show usbfs.. yet ubuntu's kernels do even using ubuntu's .config what gives? [02:34] is there something broken in make-kpkg? [02:34] spstarr: Do your kernels have an initramfs? That might be whats responsible for mounting usbfs, however I am not entirely sure. [02:34] they do, i do not know what default modules it uses though [02:35] i can explode the ramfs to check [02:35] i may need to explicitly mention --added-modules usbcore (even though ubuntu compiles this into kernel anyway) [02:36] * spstarr looks at the debian/* dir [02:37] oooh [02:37] wait a second [02:38] yes i do have one, initrd.img-2.6.31.1-custom it wouldn't boot otherwise [02:38] but how this is getting built is what im curious about [02:38] where can I find the default fakeroot for the initramfs images? [02:41] * spstarr gets source of ubuntu deb kernel [02:45] spstarr: The pieces that get put into the initramfs as well as scripts to copy binaries over are found in /usr/share/initramfs-tools [02:45] * spstarr looks [02:46] aha that's the init i was looking for [02:46] however.. /proc/filesystems only gets usbfs if usbcore is loaded [02:46] afaik [02:48] since usbcore has to register the filesystem to /proc/filesystems [02:48] so this is why im confused :) [02:48] spstarr: Not sure why things aren't working for you sorry [02:49] if i compile usbcore or leave it compiled into kernel [02:49] you'd assume /proc/filesystems would have usbfs [02:49] unless its depending on the machine im building the deb on [02:53] * spstarr examines both initramfs [02:54] and sings the little song "one of these ramdisks is not like the other" [02:57] my initramfs has usbcore in it [02:58] even more odd is i did see [02:58] [ 0.229755] usbcore: registered new interface driver usbf] [02:58] usbfs [03:16] hmmmmmmmm [03:16] bug #417748 [03:16] Launchpad bug 417748 in linux "Please enable CONFIG_USB_DEVICEFS" [Medium,Fix released] https://launchpad.net/bugs/417748 [03:16] * spstarr looks at this [03:17] ewwwww [03:18] it seems everyone is using the WRONG PATH for usbfs [03:18] you should be using /sys/bus/usb/drivers now not /proc for it anymore [03:20] if you do not enable CONFIG_USB_DEVICEFS doesn't it defer to both /sys/bus/usb/drivers AND /proc/bus/usb?? [03:21] "everyone"? I'm not aware of anything in Ubuntu using the /proc path anymore [03:21] aha [03:21] # CONFIG_USB_DEVICEFS is not set [03:21] thats why my custom kernel fails [03:21] karmic has this turned OFF [03:21] which thus disables usbfs period [03:22] aha [03:22] damint [03:22] config-2.6.31-10-generic:CONFIG_USB_DEVICEFS=y [03:22] config-2.6.31.1-custom:# CONFIG_USB_DEVICEFS is not set [03:22] config-2.6.31-9-generic:# CONFIG_USB_DEVICEFS is not set [03:22] I took -9 :D [03:22] ahahahaha fsck me [03:22] you just fixed this issue [03:23] slangasek: don't you love it when a bug happens JUST like this? [03:23] :) [03:25] * spstarr adds to the bug for anyone else looking [03:30] there [03:30] but since buntu enabled the option, nobody will run into this issue again === slangase` is now known as slangasek [03:37] I provided the missing information which caused an LP bug to be marked incomplete. Can I change its status? To what? [03:39] The previous status was Fix Committed. [03:40] I switched it to confirmed. [03:40] Darxus: if it was fix committed, then the bug was fixed, wasn't it ? [03:41] lifeless: I was told that fix committed doesn't mean a new package was uploaded. And, in fact, a new package was not uploaded. [03:41] That would be Fix Released. [03:41] LaserJock: do you have anything you'd like to highlight about Edubuntu 9.10 in https://wiki.ubuntu.com/KarmicKoala/BetaAnnouncement ? [03:42] #410933 [03:42] https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/410933 [03:42] Launchpad bug 410933 in alsa-utils "No sound in fresh jaunty install until disabling "external amplifier"" [Low,Confirmed] [03:43] cody-somerville: are there particulars to Xubuntu 9.10 that you'd like highlighted on https://wiki.ubuntu.com/KarmicKoala/BetaAnnouncement ? [03:43] superm1: ^^ mythbuntu [03:43] * cody-somerville nods. [03:43] luisbg, TheMuso: ^^ ubuntu studio :) [03:43] * cody-somerville grabs the edit lock. [03:44] * slangasek grabs the dinner lock [03:45] * superm1 doesn't have any locks left to grab [03:49] Just read through launchpad's definitions of status and I'm happy with "confirmed". [03:57] slangasek: Not really, this cycle has not been big for us at all, due to a lack of participation in general from the team. [03:58] TheMuso: ok; I'll omit the break-out section for US then, rather than asking people to make things up :) === Whoopie_ is now known as Whoopie [04:08] A "backtrace" is only available after something crashes, right? [04:09] slangasek: maybe let's do the same for Edubuntu. We haven't really changed anything since Alpha6 [04:31] LaserJock: what about changes since jaunty? [04:32] slangasek: well, the whole DVD thing is a pretty radical change [04:33] slangasek: perhaps also ltsp-cluster might be of note, beyond the usual fixes and updated packages [04:46] 6/c [04:55] LaserJock: I think you have to write for the audience that didn't notice until the beta release. [05:01] indeed [05:06] slangasek: ok, I'll take a crack at it then [05:16] The version of Debian that will be merged into Karmic is.. what? [05:16] None [05:17] karmic is frozen [05:17] specific packages can be merged by special request, and they can come from anywhere [05:18] Sorry, I should have used past tense. Sid / unstable is the answer. [05:19] Shame, the reasonably current version of hugin didn't make karmic :/ [05:19] I guess there's nothing for me to do though, it'll get merged for Lucid. [05:20] Ah, the bug wasn't even opened until 2 days after Debian import freeze. [05:20] Darxus: For a game, a freeze exception is quite possible. [05:24] It's not a game, it's a photo stitching program. [05:24] Is that possible? [05:24] Why is debian import freeze 4 months before final release? [05:25] automatic debian import freeze is so, to start the process of stabilizing things [05:25] during that phase sync requests are quite generously granted IMO [05:27] https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/416101 [05:27] Launchpad bug 416101 in pulseaudio "Ubuntu's switch to pulseaudio broke accessibility for the blind." [Undecided,New] [05:27] Seems like that should be high priority for karmic. [05:27] jdong: Cool, thanks. [05:31] Darxus: Right. I got my packages mixed up. [05:31] TheMuso: Do you have an opinion on 416101? [05:33] cody-somerville: hmm, was hoping for something a bit shorter on Xubuntu; can you pick one or two key features and link off to the Xubuntu page for the rest, please? [05:34] slangasek, aye [05:49] * TheMuso looks [05:50] PA should be pulled, period :p [05:50] even the PPA builds still spectacularly fail [05:50] ScottK: Oh right, will take care of that. Unfortunately pulse still causes a11y issues, but I have work-arounds in place to at least try and lessen the problems. [05:50] spstarr: How do they fail? Please file a bug. [05:50] ALSA finally works with my multiple audio apps [05:50] TheMuso: i did, but is marked as incomplete and nobody has changed it [05:51] i gave all the debug crash info [05:52] spstarr: Bug number? [05:52] spstarr: Its likely because we have been too busy with other bugs. [05:52] getting [05:52] TheMuso: well I pulled PA out and now Second Life works, VirtualBox works sharing same audio input/output [05:52] using ALSA only [05:53] spstarr: THats a work around, but it would be good to fix pulseaudio. [05:53] spstarr: You have tried the absolute latest version in the ubuntu-audio-dev PPA? [05:54] well, yeah, but we should be asking, why can't we fix ALSA to do most of what PA wants to do and strip PA down to just a network audio daemon? [05:54] well, not the newest PPA bug # is [05:54] bug #424551 [05:54] Launchpad bug 424551 in pulseaudio "Pulseaudio crashes if you repeat audio too much" [Undecided,Incomplete] https://launchpad.net/bugs/424551 [05:55] spstarr: This discussion has bene covered many times and in many different places. I can't remember where such discussions are on the web atm, but I'll see what I can dig up. [05:55] TheMuso: well, if ALSA has deficiencies (and it does) time for another audio rewrite for kernel? [05:56] i mean, we can replace the scheduler subsystem, etc, why not sound? :) [05:56] IANAKD [05:57] Hrm regarding this bug, dtchen is much better at working out whats going on than I am. Feel free to change the status back to new, so it is more likely to be noticed again. [05:58] the problem i have with PA is the fact it is a userspace daemon [05:58] spstarr: As for your arguments re audio, again, I know why, but I am not very good at expalining it ni an understandable way, so I'll have to find you some discussion references. [05:58] if it keels over there goes ALL your audio [05:58] spstarr: Well floating point maths is not allowed in the kernel PERIOD. [05:58] that's right [05:58] spstarr: And other OSs are doing something similar, i.e audio processing in userspace. [05:59] but PA seems so not ready for production [05:59] it cannot handle heavy loads [05:59] i can count how many times PA has burned me so much i ripped it out, now I am not willing to put it back for a least a few years [05:59] spstarr: Perhaps you want to take this up with upstream. I suggest going into #pulseaudio and chatting with mezcalero/Lennart when he is around. [05:59] now that ALSA is cooperating with me finally [06:00] TheMuso: that could get very messy :) [06:00] spstarr: Have you tried other distros, to see if they behave the same? [06:00] spstarr: Only if you let it. [06:00] yep [06:00] I used Fedora prior, Debian prior that (with a splash of buntu in 2006) [06:01] now (k)buntu [06:01] Well pulse has come a long way since then, so if you can't reproduce these problems in Fedora for example, then we are doing somethnig wrong and need to address it. [06:01] or as I call it, buntu :) [06:01] I can reproduce them in Fedora :) [06:01] Ok then. [06:01] My suggestino still stands. Chat to Lennart on IRC in #pulseaudio when he is around, or email the mailing list. [06:01] suggestion even [06:02] yes [06:02] but for now, ALSA is working for my needs (amazingly) [06:04] brb === hunger_t_ is now known as hunger [06:38] Good morning! [06:44] good morning [06:51] hey dholbach [06:56] hi rgreening === asac_ is now known as asac [07:20] Good morning [07:20] hey yuriy [07:22] james_w: looks like we should be quick for UOW if we don't want a 23 UTC slot for our session: https://wiki.ubuntu.com/UbuntuOpenWeek/Prep - shall we do a double session? [07:22] james_w: maybe we can still move things around a little bit :) === cjwatson_ is now known as cjwatson [08:12] cjwatson: how can I run ubiquity on an installed system just to do a few screenshots? [08:13] I'm not going to give advice on that because I consider it very unwise! [08:13] oh ok [08:13] you can install the package and run it, but it may make changes to your system even before the summary screen [08:13] ok, I see [08:13] since it assumes that it's OK to make changes to the live environment [08:13] I'll use a VM then - no worries [08:13] it's just to update a few screenshots [08:13] yeah, that's much safer and easier [08:14] example-content still speaks about "espresso" ;-) [08:15] hey guys... Florian from France. Does anyone know when exactly the beta will be released ? [08:15] * dholbach fixes that :) [08:15] dholbach: hah [08:15] florian__: please don't ask that sort of thing [08:15] florian__: the people with specific information on exactly what time are also critical-path to getting it out [08:15] so we do not encourage bugging them [08:16] it will happen at some point, go and enjoy yourself in the meantime :) [08:16] if you're a mirror operator, then #ubuntu-mirrors might have more information, or you could arrange to have yourself set up as a push mirror [08:17] * cjwatson -> breakfast [08:17] cjwatson: I'm not... I guess i just can't wait... :) [08:17] cjwatson: what do you mean by critical-path ? === tkamppeter_ is now known as tkamppeter === SuBmUnDo__ is now known as Guest4010529 === dholbach_ is now known as dholbach [10:09] pitti: uploading an updated example-content now - it should free up 1M! :-) [10:09] accept whenever it seems suitable === dpm__ is now known as dpm [10:16] yay you! [10:16] dholbach: we'll flush the queue after beta release [10:16] cool === yofel is now known as yofel_ === mthaddon changed the topic of #ubuntu-devel to: Codehost/Codebrowse down 10:00 UTC - 10:30 UTC | Karmic Alpha-6 released | Archive: frozen for beta; FeatureFreeze, UIFreeze | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [11:05] hrmpf gdm == GodDammit Bugpile === slangasek changed the topic of #ubuntu-devel to: Codehost/Codebrowse down 10:00 UTC - 10:30 UTC | Archive: frozen for beta; FeatureFreeze, UIFreeze | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [11:29] Keybuk: shouldn't upstart have respawn rate limiting that would prevent bug #431166? [11:29] Launchpad bug 431166 in gdm "karmic gdm restarts X infinitely when video driver fails to load" [Low,Confirmed] https://launchpad.net/bugs/431166 [11:29] hello, help check bug #427725, whether we can sync ibus-m17n from debian? [11:29] Launchpad bug 427725 in ibus "Typing "lian" in py-b5 makes ibus-m17n crash" [Undecided,Confirmed] https://launchpad.net/bugs/427725 === mthaddon changed the topic of #ubuntu-devel to: Codehost/Codebrowse down 10:00 UTC - 10:40 UTC | Archive: frozen for beta; FeatureFreeze, UIFreeze | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs === cjwatson_ is now known as cjwatson [11:32] slangasek: gdm restarts X indefinitely [11:32] it's not gdm that's restarting [11:32] oh [11:32] doh [11:32] excuse my wayward task opening, then [11:32] the previous gdm had code to avoid that [11:33] yet another thing the new codebase does in a buggy way compared to the previous one === mthaddon changed the topic of #ubuntu-devel to: Karmic Alpha-6 released | Archive: frozen for beta; FeatureFreeze, UIFreeze | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [11:40] Slightly related to this, I eventually abandoned trying to get XDMCP connections to work for connecting to Karmic's gdm... I added a /etc/gdm/custom.conf with [xdmcp]/Enable=true, and added an appropriate entry in hosts.allow, but that isn't adequate. [11:40] I also found I had to set [xdmcp]/DisplaysPerHost > 1 for the querying host to be able to connect at all, and even then I just get a blank display, with gdm appearing to do nothing after the initial connection. [11:40] Any thoughts? I'm using Cygwin/X here, which may be part of the problem. Worked with Jaunty though. [11:41] seb128: a side conversation at plumbers was that you can *almost* entirely replace gdm with upstart [11:41] since new gdm has gotten so basic [11:42] oh, can I stop fiddling with this gdm keyboard mess then? :-) [11:43] heh [11:44] seb128: ugh, the new gtk theme for gdm is pretty ugly; I already thought I broke something.. [11:44] until I realized that bzr head had a newer version [11:44] pitti, hey, rick was wondering if it was not better with the standard one [11:44] bubble help has no contrast any more and looks buggy [12:26] afernoon everyone [12:26] do we have a beta yet ? [12:26] no [12:27] :-( [12:27] when is it expected ? [12:27] any time indication ? [12:31] mdke: lp:~vorlon/gnome-user-docs/ubuntu-karmic/ - I can't commit directly to the ubuntu-core-doc branch, so please merge [12:32] Dennis-Beekman: just await the announcement === MacSlow is now known as MacSlow|lunch [12:59] https://wiki.ubuntu.com/KarmicKoala/BetaAnnouncement [12:59] it's here !! [13:00] none off the mirror's have the actual image yet though :-( [13:00] that's an email draft. [13:01] slangasek: I wanted to ask you something about that draft, but didn't want it to make to the maillist... [13:01] yeah.. but it's the actual announcement [13:01] no, it's not the "actual announcement", it's an email draft. [13:01] alourie: oh? [13:01] in the "under the hood" section you mentioned python version [13:02] * slangasek nods [13:02] slangasek: is it that basic that it should be mentioned? What about, say, perl? [13:02] I mean, is it on the level of kernel/gcc ? [13:03] alourie: python is central to Ubuntu's development environment; perl less so :) [13:03] Dennis-Beekman, when it is announced, there will be an e-mail on ubuntu-devel-announce; until then, it is not announced and it is not released, please be patient [13:03] slangasek: yea, that's what I thought. That's why I didn't send this to the maillilst... [13:03] liw: ubuntu-announce, actually [13:04] slangasek: thanks, that answers my question. Besides that, I think it's perfect :-)0 [13:04] alourie: ok, great :) [13:08] Dennis-Beekman: we appreciate your enthusiasm, but rushing around like this actually consumes time from the people who are responsible for preparing the release, so please don''t [13:08] Dennis-Beekman: and when the release manager tells you that something isn't the actual announcement, he probably actually knows better than you ... :-) [13:10] pitti: any ideas on bug 419501? I'm finding a lot of dupes, and most of them are in apport, but a few in other apps [13:11] Launchpad bug 419501 in libxcb "apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed." [High,Triaged] https://launchpad.net/bugs/419501 [13:12] yuriy: I'm afraid not; I tried it in Kubuntu as well, but coulnd't reproduce [13:14] yeah I haven't seen it myself, but was concerned because I was finding so many reports === slangase` is now known as slangasek [13:16] seb128, about #421318 (totem python crash): I've attached a patch, could you upload once the beta freeze is over? [13:17] liw: oh cool, you caught that bug? [13:18] slangasek, I asked upstream, upstream replied with patch [13:18] ah [13:18] :) [13:18] * liw is totally innocent of any actual bug fixing here [13:18] liw, thanks, will do, the change is quite easy which is good [13:18] I was not sure if you were going to rewrite half of the code yesterday ;-) [13:19] seb128, I still maintain that the proper fix is to not use the combinations gtk+threads or python+threads (or gtk+python+threads), but I'm happy this particular bug got fixed easy :) [13:19] seb128, I don't see a bug about this in Debian, but if I missed one, I assume you'll take care of it there as well [13:20] liw, debian doesn't have the bbc change, it's an ubuntu one, it's still being discussed upstream and not accepted there yet [13:20] liw, I will update the upstream bug though [13:20] liw, but nice to see it fixed so quickly ;-) [13:20] seb128, ah; otoh, the bug was actually generic for all Python plugins [13:21] liw, right, I was expecting something like that but not sure, contacting upstream was a good idea there [13:21] liw, is there any other python one in the default set? [13:22] seb128, coherence_upnp, dbus-service, opensubtitles? [13:23] liw, ok, I didn't look to those, just weird that they didn't crash [13:23] anyway that's fixed so all good now [13:35] The switch to pulse audio took place in jaunty? [13:35] Ah, looks like Hardy. [13:36] what do you call switch? [13:36] it's installed since hardy === korn_ is now known as c_korn [13:53] when will 9.10 beta be out? [13:53] please don't ask that here [13:53] for every question like this it'll release an hour later :) [13:53] for that matter, please just don't ask it - wait :) [13:54] ok :P consider it not asked [13:54] BTW, nice work ;) [13:55] Guest87434: If you want somewhere to wait, #ubuntu+1 will be abuzz when its actually released. [13:58] Pici: Thnks [14:01] Keybuk: for bug 397734, do you think we can/should change the default in our kernel for karmic? [14:01] Launchpad bug 397734 in procps "can't eject unmounted cdrom with hardware button" [Medium,In progress] https://launchpad.net/bugs/397734 [14:01] Keybuk: default -> CD tray locking state, I mean === MacSlow|lunch is now known as MacSlow [14:18]