[02:15] <DrCheese> Linux and Ubuntu is cancer that attaches itself in an intellectual property sense to everything it touches.
[02:16] <DrCheese> Linux and Ubuntu is cancer that attaches itself in an intellectual property sense to everything it touches.
[02:16] <ScottK> !ops
[02:16] <Hobbsee> damn lag.
[02:16] <ScottK> Thanks.
[02:16] <Hobbsee> \o/ win!
[02:16] <ajmitch> wasn't even a very creative troll
[02:17] <cjwatson> beat me to it
[02:17]  * Hobbsee ^5 cjwatson
[02:17] <jdong> is today official troll day?
[02:17] <Hobbsee> seems so
[02:17] <ScottK> He could of at least claimed we were insecure or something.
[02:18] <Hobbsee> well, now he's claiming that i can't see him, so...
[02:19]  * TheMuso wonders whether DrCheese created #windows, however I can't seem to see the topic or names without going in there.
[02:19] <jdong> why does that IP look familiar.
[02:19] <Hobbsee> TheMuso: highly unlikely.  People who create large channels are usually too busy to petty troll.
[02:19] <Hobbsee> @btlogin
[02:20] <infinity> Hobbsee: It's not a large channel, he's in ##windows, not #windows.
[02:20] <infinity> Hobbsee: Although, even that's moderately large, actually.
[02:21] <Hobbsee> infinity: ah, i didn't do a whois to check.
[02:21] <jdong> Hobbsee: part of the big MA Comcast DHCP pool; identifying him is probably hopeless.
[02:21] <Hobbsee> jdong: ah yes, you should recognise that IP.  check the BT.
[02:22] <jdong> Hobbsee: I don't have access to it, do I?
[02:22] <jdong> ah I see it.
[02:22] <jdong> yeah I should've recognized that indeed.
[02:22] <Snova> ?
[02:22] <jdong> frequent customer.
[02:22] <Snova> Heh.
[02:22] <jdong> Snova: ubuntu-ops log 4/13 and 4/08
[02:23] <emgent> hallo
[02:23] <Hobbsee> and under the other aliases.  Here's a cross-channel hammer
[02:23] <ScottK> Comcast generally gives you the same IP for each lease renewal, so unless he knows how to ask for a new one, it should ~work.
[05:46] <jturek> has anybody found that the ATI Mobilitiy cards (X2300) doesn't detect in restricted drivers in jaunty
[05:46] <jturek> i seem to not be able to get ubuntu to use the restricted driver manager for teh ati x2300
[05:50] <jturek> clear
[06:19] <dholbach> good morning
[06:34] <Amaranth> dholbach: wow you're up early
[06:35] <dholbach> hiya Amaranth - it's 7:34 - and I was out running already! :-)
[06:35] <Amaranth> ah, right, dang daylight savings
[06:44] <siretart> bryce_: wiki edited
[06:52] <bryce> siretart: great
[07:19] <superm1> slangasek, i've got a resolution for bug 355242 that involves only a 2 line diff
[07:20] <superm1> mythbuntu rc disks will need a re-roll with it
[07:46] <slangasek> superm1: it's a patch to mesa?  That implies invalidating all the ISOs
[07:47] <superm1> slangasek, perhaps can you just reroll mythbuntu after the others have been verified then?
[07:49] <slangasek> we can consider that.  it does effectively mean we don't get jigdo support for the RC, but if we time it fairly close then we can at least get some jigdo benefit
[08:04] <tjaalton> slangasek: there's also a candidate for the wacom crashes, but it's still untested so not meant for RC
[08:04] <slangasek> ok
[08:06] <pitti> Good morning
[08:07]  * slangasek waves
[08:08]  * siretart bounces happily through the channel - finally working intel driver..  :-)
[08:09] <pitti> siretart: oh, what did you change?
[08:09] <siretart> pitti: see my latest post to ubuntu-devel. I've reverted to the 2.4 branch
[08:09] <pitti> siretart: interesting; that still works with current X then?
[08:10] <siretart> pitti: you need to compile it against jaunty's X and libdrm, which works with some patching.. :-)
[08:10] <siretart> working packages can be found in my ppa
[08:11] <siretart> well, at least WFM
[08:15] <Mirv> cody-somerville: hi, do you have plans to fetch xubuntu-docs translations from rosetta and upload a new xubuntu-docs with those included?
[08:16] <wgrant> Is there a non-historical reason for USNs to list Xubuntu but not other unofficial flavours as affected?
[08:40] <RAOF> Has anyone else recently seen dbus-daemon go crazy, consume a core, and all available memory (it's up to 1.6GiB, and still rising)?
[08:41] <Keybuk> RAOF: something sending it a lot of timing out messages?
[08:41] <Keybuk> dbus-monitor is your friend
[08:42] <RAOF> Hello, tracker!
[08:42] <RAOF> Hm.  Apparently tracker would like to tell me that my index is corrupted.
[08:43] <liw> does tracker work for anyone else? it's never done anything useful for me :(
[08:45] <lifeless> liw: using all your cpu is useful
[08:45] <Keybuk> we don't even install it by default now
[08:45] <lifeless> liw: it tests your cpu
[08:45] <Keybuk> and I'm pretty sure it's removed by update-manager on upgrade
[08:46] <directhex> ta dholbach
[08:46] <siretart`> Keybuk: I can confirm that update-manager didn't remove it on my amd64 desktop last week when I upgraded from intrepid->jaunty
[08:46] <mvo> I can ensure that it gets removed if thats what we want
[08:47] <siretart`> +1
[08:47] <mvo> (sorry, I have not followed the state of tracker)
[08:48] <seb128> mvo: we decided again doing that in a systematic way because some users are using it
[08:48] <liw> Keybuk, it didn't get removed from my laptop, actually
[08:48] <mvo> ok
[08:48] <RAOF_> Keybuk: Thanks; looks like the bug is tracker spamming "OMGINDEXCORRUPTED" messages into the void.
[08:49] <liw> I'd love to have something like tracker, if it didn't hog my computer and actually found things when I search
[08:49] <seb128> tracker will probably be better next cycle
[08:49] <liw> good to hear
[08:49] <seb128> the jaunty version is basically a rewrite, it still has some issue but gets lot of work
[08:50] <siretart`> RAOF_: where does it spam to?
[08:50] <seb128> nokia is paying to get it working fine on their device apparently
[08:51] <Keybuk> seb128: is there going to be a rewrite to use fsnotify instead of inotify?
[08:52] <liw> fsnotify?
[08:53] <liw> ah, some new kind of implementation, good
[08:53] <Keybuk> liw: lwn.net/Articles/311350
[08:54] <seb128> Keybuk: that I don't know, but now it's possible to have applications pushing datas rather than the indexer going through the disk all the time
[08:54] <seb128> Keybuk: ie your mailed can send datas to tracker when receiving emails rather than relying on inotify to go through the disk emails
[08:55] <seb128> mailed -> mailer
[08:55] <RAOF_> seb128: Do we actually have the evolution side of that system in jaunty?
[08:55] <seb128> no ;-)
[08:55] <seb128> the new version is still new, I expect it to work better
[08:55] <seb128> I would not bother too much with the jaunty version
[08:55] <seb128> there is frequent db corruptions and still issues
[08:55] <Keybuk> ah
[08:56] <cody-somerville> wgrant, Xubuntu *is* an official flavour :)
[08:56] <cody-somerville> Mirv, I'd like to, yes.
[08:56] <liw> evolution db corruptions? never :)
[08:56] <Keybuk> one of the neat features of fsnotify/fanotify is that a watching application gets a file descriptor to the data just written/read
[08:56] <Keybuk> so you don't need to stat(), open(), etc. massively saving on overhead
[08:57] <seb128> liw: no, tracker db corruptions ;-)
[08:57] <wgrant> cody-somerville: It's no more official ('supported', I suppose the correct term is) than Mythbuntu or UbuntuStudio, is it?
[08:57] <liw> Keybuk, can fsnotify do things like "show me everything that ever changes in this filesystem" or "...inside this directory tree"?
[08:57] <seb128> liw: btw have you seen this bug about computer-janitor using update-manager as translation domain?
[08:58] <Keybuk> liw: in theory, yes
[08:58] <liw> seb128, I have; I haven't investigated yet, I'll have to discuss the gettext domain issue with mvo
[08:58] <Mirv> wgrant: not supported by Canonical, but official (like Mythbuntu, Ubuntu Studio)... it's good to refer to those as official as there are also unofficial Ubuntu variants like Eeebuntu, Ubuntu ME etc..
[08:58] <Keybuk> liw: fanotify is by-filesystem rather than by-file/directory
[08:59] <seb128> ok
[08:59] <liw> Keybuk, übercool!
[08:59] <wgrant> Mirv: True. But my point is that it's odd to single out Xubuntu.
[08:59] <liw> I'm going to have to add support for that in my backup program
[08:59] <Mirv> wgrant: yes, regarding your actual point, it's probably just historical, there have been other such cases as well
[08:59] <Keybuk> liw: inside-this-directory-tree is harder, in that you'd have to read the filename and strncmp or something ;)
[09:00] <liw> Keybuk, that'd be one way; I'd have to benchmark whether it'd be faster to scan the directory tree and remember all inodes and then compare with indoes that change
[09:01] <Keybuk> liw: I can't imagine that it wouldn't be faster ;)
[09:01] <Keybuk> though the overhead for a smaller directory of processing and discarding unwanted events could be high, I guess
[09:01] <cody-somerville> wgrant, I'm not sure what their status is
[09:01] <liw> Keybuk, depends on size of tree and number of changes, but I'm too stupid to know which is faster without benchmarking
[09:08] <pitti> lool: you'll upload the fix for bug 339466 to the queue?
[09:23] <slangasek> pitti: bug #361543 for you :(
[09:23] <pitti> owch
[09:25] <slangasek> cody-somerville: is there a technical-overview-esque page for Xubuntu to link from https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview for RC?
[09:25] <slangasek> Riddell: will there be an RC technical overview for Kubuntu as well?
[09:26] <tseliot> mvo: are you around?
[09:26] <mvo> tseliot: yes
[09:27] <tseliot> mvo: any ideas on this? https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/351394
[09:27] <mvo> tseliot: let me have a look
[09:28] <tseliot> mvo: also, what driver version do you migrate to "nv" in Jaunty?
[09:28] <tseliot> s/version/versions/
[09:34] <lool> pitti: I was waiting for some ubuntu-release ack
[09:34] <lool> pitti: (I sub-ed the team yesterday)
[09:35] <pitti> lool: you got it
[09:36] <pitti> cjwatson, evand: yay, thanks for fixing the default grub target; in the beta I still had to change it from (hd0) to my USB stick (sdc), now it automatically DTRT
[09:37] <lool> pitti: Yup, uploaded
[09:42] <cody-somerville> slangasek, There shall be.
[10:11] <slangasek> Riddell: https://wiki.ubuntu.com/JauntyJackalope/RCAnnouncement is up for consideration, pulling in the same kubuntu text from the beta; please let me know if changes are needed
[10:13] <Riddell> slangasek: good with me
[10:38] <pitti> seb128: did you have any problems with the retracers last week? they seem surprisingly stable now
[10:38] <pitti> seb128: I remember some weird HTTP errors, but no real crashes any more
[10:39]  * pitti -> offline, CD testing
[10:40] <AstralJava>  /join #ubuntustudio
[10:40] <AstralJava> bah
[10:47] <sabdfl> gosh, reading scrollback for martinw
[10:47] <sabdfl> how is everyone here today?
[10:48] <ogra> busy testing ;)
[10:50] <slangasek> up at strange hours, right on schedule :)
[10:50] <ogra> slangasek, i see no 14.2 respin for armel desktop, did you forget us ?
[10:51] <slangasek> sabdfl: martinw == Patrick Frank, fwiw; he has Issues with Authority :/
[10:51] <slangasek> ogra: didn't forget, just got caught up getting other things squared away - I'll do the ports run now
[10:51] <sabdfl> me too! i'll try and chat privately with him when he comes online
[10:51] <ogra> thanks, i'll test it ;)
[10:55] <seb128> pitti: no, good work ;-)
[11:09] <lool> cjwatson: What would be the right seed to list redboot-imx51-babbage
[11:09] <lool> cjwatson: We use it to build the official images, but it's not pulled by any package and the package itself is not included in any media, only its contents
[11:10] <cjwatson> lool: I'd say platform.jaunty/supported-installer-common then
[11:11] <lool> Ok, thanks
[11:11] <ScottK> siretart: I gather your adventure in Intel bleeding edge stuff did not have a happy ending?
[11:16] <siretart`> ScottK: for my laptop, yes, I'm happy with the 2.4 branch on my laptop
[11:17] <ScottK> siretart: Weren't you also testing the latest 2.6?
[11:18] <siretart`> ScottK: jaunty ships some later revision of the 2.6 branch. I've tried the 2.6 HEAD, 2.7 HEAD and 2.4 HEAD
[11:18] <siretart`> ScottK: I got the best results from the 2.4.1 package with bryce's patches as found in intrepid
[11:19] <siretart`> ScottK: having said this, I'd suggest to include my package in universe for people like me.
[11:19] <ScottK> I see.  Some Gentoo guy was recently telling me that his had recently gotten better with the bleeding edge stuff.
[11:19] <ScottK> siretart: As long as you're willing to support it for the life of Jaunty, I think it's a great idea.  Otherwise a PPA might be better.  What do you think?
[11:20] <siretart`> yes, 2.7 is a big improvment on my laptop compared to 2.6. but still hasn't acceptable performance
[11:20] <seb128> siretart: where do you notice those slowness issues?
[11:20] <siretart`> ScottK: I'm willing to integrate updates from intrepid-updates to the package, yes.
[11:20] <siretart`> ScottK: I'm not familiar with the code to actually start hacking on
[11:21] <siretart`> seb128: compiz and planet-pengiun-racer are not usable at all.
[11:21] <ScottK> siretart: OK.  The only issue then would be any -security issues that come up after Intrepid eol
[11:21] <seb128> what in compiz?
[11:21] <seb128> normal actions, ie alt-tab switch
[11:22] <siretart`> seb128: resizing windows, the expose effect, alt-tab switch, etc.
[11:22] <seb128> hum ok
[11:22] <seb128> I guess it's not that slow on my card
[11:22] <siretart`> seb128: alt-tab switch was unnaceptable in metacity with compositing as well
[11:22] <seb128> I was just wondering if people were using extra features which showed the issue
[11:23] <ScottK> siretart: Did you try Option "MigrationHeuristic" "greedy"?  While it's still not up to Intrepid, I find it usable.
[11:24] <siretart`> ScottK: err - I'm not suggesting to put it in main but universe. and for universe we don't promise security (or other) updates at all
[11:24] <ScottK> siretart: True.
[11:24] <siretart`> ScottK: no, I haven't tried that option
[11:25] <ScottK> siretart: You might.  I understand it makes some people have crashes so is not suitable for a default, but it made a huge difference for me.
[11:25] <ScottK> For me it's like uxa without crashes.
[11:25] <siretart`> is that option for the 2.4 branch or 2.6 branch?
[11:25] <ScottK> Either as I understand it.
[11:26] <siretart`> hm
[11:26] <ScottK> siretart: Bug #359600 has some information
[11:26] <siretart`> I've been testing the 2.6 and 2.7 branches both with UXA
[11:26] <ScottK> We had it for default for a while in Intrepid, but didn't keep it, so it must be for both.
[11:27] <siretart`> so I cannot really comment on EXA. EXA was more than unacceptable for me in 2.6, and I didn't even bother trying it in 2.7
[11:27] <ScottK> I see.  It made a huge difference for me with exa.
[11:27] <ScottK> siretart: For a new package you'll need two motu-release acks.  You have mine to get you started.
[11:29] <siretart`> ScottK: okay. who else from motu-release is around here? :-)
[11:29] <slangasek> ScottK: I don't know of any reports of crashes due to greedy migration being enabled, but the patch to xserver-xorg-video-intel to /try/ to enable it by default for those chips causes crashes
[11:30] <slangasek> the only issue I've found with greedy migration here is pixmap lossage
[11:30] <slangasek> (firefox in particular likes to go black in patches)
[11:31] <Lure> slangasek: I have also noticed some black areas with greedy (but not to the level that I would go back to non-greedy ;-))
[11:39] <pochu> to which package should I reassign a bug in the nvidia binary driver?
[11:41] <directhex> which version?
[11:44] <tseliot> pochu: nvidia-graphics-drivers-$VERSION (where VERSION is 180, 173 or 71)
[11:49] <directhex> tseliot, there are only three nvidia-graphics-drivers now?
[11:50] <tseliot> directhex: I forgot 96
[11:50] <directhex> that's better ;)
[11:51] <directhex> tseliot, so, anything worth having in the 185 betas, that you know of?
[11:52] <pochu> tseliot: ty
[11:52] <tseliot> np
[11:53] <pitti> Keybuk: nice, the current c't (famous German computer magazine) has a 3-page article about upstart
[11:53] <tseliot> directhex: mainly fixes for VDPAU and support for new cards: http://www.nvnews.net/vbulletin/showthread.php?p=1976912
[11:55] <directhex> tseliot, neat
[11:56] <tseliot> directhex: only for Karmic and/or backports to Jaunty though
[11:56] <directhex> tseliot, my main issue currently is trying to get actual audio out the hdmi port on an nvidia 9300 motherboard. it appears non-trivial
[11:56] <tseliot> directhex: isn't that something that alsa/pulseaudio should deal with?
[11:57]  * tseliot > lunch
[11:57] <directhex> tseliot, oh, yeah, sure. but i can't get a bloody thing via speaker-test. and it's hell trying to get sound out of assorted command-line alsa utils which all use totally different device naming syntax
[12:00] <Keybuk> pitti: got a url/translation?
[12:00] <pitti> Keybuk: it's not online, just in the paper magazine
[12:01] <pitti> Keybuk: http://www.heise.de/ct/inhalt/2009/09/176/
[12:25] <dholbach> soren: ever used kvm for testing images and ran into "kvm: 27711: cpu0 unhandled wrmsr 0xc0010117 data 0"?
[12:25] <dholbach>  amd64 dvd ubiquity install hanging at 78% "System locale is being configured" (or something like that)
[12:33] <soren> dholbach: That could very well be unrelated.
[12:33] <soren> dholbach: I consider those messages debug messages more than anything.
[12:33] <dholbach> soren: ok, I'll re-test and see what happens
[12:34] <soren> dholbach: The guest kernel sometimes pokes at various MSR's to see if there's something there, and that gets logged by the host kernel. Most of the time, it's benign.
[12:34] <soren> Most of the time.
[12:35] <slangasek> ScottK, Riddell: does the Kubuntu KDE4 remix warning on https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes still apply in the case of upgrades to 9.04?
[12:42] <ogra> hmm, so 24h later i see my system starting to eat my swapspace again ... it went from 0M to 264M within the last 30min, without me doing anything special or additional to what i did 1h before
[12:43] <ogra> (i have htop running constantly since i ran out of swap yesterday )
[12:43] <ogra> heh, and between me starting to type the above and now it went to 379M swap usage
[12:45]  * ogra closes evo and firefox
[12:45] <ogra> (only xchat and two terminals are open now, system is at 429M swap usage)
[12:48] <slangasek> ogra: how's the armel candidate ISO looking, BTW?
[12:48] <ogra> livesession is fine, install is at 57%
[12:48] <ogra> no unknown bugs seen yet
[12:49] <ogra> sabdfl, good push for the new TZ map, it looks a lot better now
[12:49] <Riddell> slangasek: I think that can go
[12:49] <sabdfl> ogra: thanks to kwwii and evand's work, i agree
[12:50] <Riddell> evand: know anything about this?  http://pastebin.ubuntu.com:80/151367/  when running OEM mode
[12:51] <evand> Riddell: not until now.
[12:51]  * evand digs
[12:51] <evand> thanks sabdfl
[12:54] <Riddell> evand: davmor2 says that didn't happen yesterday
[12:54] <Riddell> has anything changed since then?
[12:55] <evand> it happened in 1.12.5
[12:55] <evand> fix incoming
[12:56] <Riddell> evand: does this affect kubuntu only?  or ubuntu desktop too?
[12:56] <evand> kubuntu only
[12:56] <davmor2> Riddell: I just done ubuntu oems
[12:57] <slangasek> Riddell: it can go because 8.04->9.04 is only a supported path for kde, not kde4 remix?
[12:57] <Riddell> slangasek: right
[12:57] <slangasek> ok
[12:57] <Riddell> slangasek: OEM broken on Kubuntu desktop CDs ^^
[12:58] <slangasek> waah
[12:59] <Riddell> evand: also reboot didn't seem to be working at the end of a Kubuntu install
[12:59] <evand> Riddell: where did it break?  Did pressing the button not do anything, or did the computer fail to restart after shutting down?
[13:00] <Riddell> evand: ubiquity quit, desktop sits there being itself
[13:01] <evand> hrm, ok.  I'll pull down the latest Kubuntu daily-live and see if I can reproduce it.
[13:01] <cjwatson> sorry about the OEM breakage, apparently my fault way back in 1.12.0
[13:01] <cjwatson> I have the Kubuntu image here, I can have a look ...
[13:01] <evand> ah great
[13:01] <evand> should I go ahead and upload this change and we'll deal with the reboot issue as another upload?
[13:02] <cjwatson> my instinct is to batch it up for post-RC, since we have some other changes for then anyway
[13:02] <cjwatson> Riddell,slangasek: what do you think?
[13:02] <davmor2> slangasek: get it in now before there are many tests on it :)
[13:02] <Riddell> I'm tempted to upload the OEM fix and respin that for RC
[13:02] <cjwatson> I'd kind of like to fix the colours on the Kubuntu partition bars too
[13:02] <davmor2> cjwatson: I though that got fixed
[13:03] <cjwatson> not to my knowledge
[13:03] <slangasek> I don't like shipping the RC with broken OEM mode, but doing a respin now cuts into our testing time and our image prepublishing time
[13:03] <cjwatson> Riddell: is #133d80 a plausible Kubuntu-blue colour to use for the partition bars?
[13:03] <Riddell> kwwii's area really ^^
[13:05] <kwwii> erm, where?
[13:05] <davmor2> slangasek: there aren't that many test on kubuntu are there
[13:06] <kwwii> cjwatson: that is a pretty kubuntu-ish color, but it might be too dark bepending on where/how it is used
[13:07] <slangasek> davmor2: rerolling kubuntu includes rerolling DVDs, which takes > 1.5h just for the livefs rebuild
[13:08] <Riddell> slangasek: toss a coin :)
[13:08] <slangasek> Riddell: is it acceptable to you to ship the RC without a usable OEM mode?
[13:08] <Riddell> yes, it's not the end of the world
[13:09] <slangasek> ok, then that's my preference
[13:09] <Riddell> I'm just mindful that it's not well tested so if there's further problems (and davmor2 had issues yesterday) they won't be picked up
[13:09] <slangasek> we can make images available immediately post-RC for testing, then?
[13:09] <Riddell> we can indeed
[13:10] <Riddell> and we have alternate OEM to test
[13:12] <cjwatson> kwwii: bug 348461, though I don't have a screenshot to hand unfortunately
[13:12] <Riddell> evand: bug 361668
[13:12] <cjwatson> I can explicitly test Kubuntu OEM immediately post-RC, since we need to update the oem-config timezone map anyway
[13:13] <cjwatson> or, indeed, I can test it now with evand's fix
[13:14] <kwwii> cjwatson: ouch, without seeing the problem it is pretty hard for me to just suggest a color :(
[13:15] <cjwatson> let me see if I can produce a screenshot
[13:15] <kwwii> cjwatson: the blue you suggested fits well with kubuntu colors so testing it can't hurt
[13:15] <kwwii> I could download a CD and test it myself but that would take a bit
[13:16] <cjwatson> nggh, partition bars are still invisible in Kubuntu?
[13:17] <kwwii> I have to take my son to the dentist, bbiab...I'll read the log when i return
[13:18] <robbiew> doko: do you think we can fix bug 353704?
[13:20] <robbiew> doko:   it breaks Skype on amd64, is it feasible to fix in an SRU of 9.04
[13:20] <doko> robbiew: I think Bo is fixing this
[13:20] <davmor2> Riddell, slangasek: right so the out come is we can carry on testing the images that are up, and you'll do a respin friday (or something) for us to nail all the oem issues is that correct?
[13:20] <ogra> argh
[13:21] <slangasek> davmor2: yes
[13:21] <ogra> slangasek, gdm sudeenly crashes on babbage/imx51
[13:21] <davmor2> slangasek: Cool :)  Cause I just finishe ubuntu desktop :)
[13:21] <ogra> install went flawless
[13:22]  * ogra checks what seb128_ changed between beta and now in gdm :/
[13:22] <seb128_> no
[13:22] <slangasek> looks like Robert's the one who changed it
[13:22] <ogra> no ?
[13:22] <seb128> what changed?
[13:22] <ogra> ah
[13:22] <slangasek> though it could be a library regression, rather than the gdm change
[13:23] <ogra> seb128, i get the "greeter is crashing, trying with another greeter" message in gdm suddenly
[13:23] <seb128> slangasek: the change he did was a one line boolean logic for the hours format combo
[13:23] <ogra> yeah, that doesnt really look like it could cause anything
[13:23] <seb128> ogra: that means the greater is crashing, could be any library gdm is using or xorg
[13:24] <slangasek> that patch doesn't touch the greeter, so probably not
[13:24] <seb128> do you get apport triggering? anything in the logs about a crash?
[13:24] <ogra> noting in Xorg.0.log ... inspecting the rest atm
[13:24] <ogra> i see 7usr/bin/gdm in the processlist
[13:26] <pitti> slangasek, bryce: I updated the "known issues" bits on https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview#Known%20issues with the workarounds known to me (we have a few more crashers, but they involve patching the driver, which is a bit out of scope for release notes); does that look okay to you, or is it too technical?
[13:26] <ogra> gdm log only has xkbcomp messages ...
[13:26] <ogra> nothing in /var/crash
[13:26] <slangasek> pitti: it's the wrong place for it; bugs that aren't fixed for final should be documented at https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes
[13:27] <slangasek> pitti: I can take care of porting that over, though
[13:27] <pitti> slangasek: ah, I'll move it over
[13:27] <pitti> slangasek: I guess it doesn't hurt to also keep it on TechOverview, for the RC?
[13:28] <slangasek> if the tech overview will go up on the ubuntu.com website again, then we should have it ready for final, i.e., eliminate duplication w/ the release notes
[13:29] <pitti> slangasek: your lock on ReleaseNotes timed out, are you still working on it?
[13:29] <slangasek> pitti: no
[13:31] <lool> I am suspicious that this gdm issue might be cause by the gtk+2.0 issue
[13:31] <lool> we'll confirm soon
[13:31] <pitti> slangasek, bryce: okay, put on https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes now
[13:31] <slangasek> thanks
[13:32] <slangasek> lool: right, I wondered...
[13:33] <ogra> what irritates me here is that i indeed get a gtk window telling me the greeter cant start
[13:34] <dholbach> soren: can you join #ubuntu-testing?
[13:34] <ogra> lool, slangasek same thing with new gtk
[13:35] <lool> ogra: Could you try moving away your /usr/lib/vfp?
[13:35] <dholbach> soren: I'm having the same issue again (amd64 jaunty host, jaunty guest): freeze during the installation - how best to debug it?
[13:35] <lool> ogra: sudo mv /usr/lib/vfp /usr/lib/vfp.bak
[13:37] <ogra> same thing
[13:38] <lool> ogra: Does dbus run?
[13:38] <lool> On my install it doesn't
[13:39] <ogra> yes
[13:39] <lool> Can't start Hardware abstraction layer - please ensure dbus is running
[13:39] <seb128> if you log in, can you run gdmthemetester?
[13:39]  * ogra tries startx
[13:39] <seb128> or gdmflexiserver
[13:39] <ogra> one sec, just installing sshd
[13:40] <ogra> btw, i cant stop gdm with the initscript
[13:41] <dholbach> kirkland: hiya - can you join #ubuntu-testing so we can chat a bit about kvm on amd64 jaunty? I'm having hangs during test installations
[13:42] <kirkland> dholbach: during language pack en ?
[13:42] <ogra> hmm, startx does nothing now
[13:43] <ogra> ah, its just slow
[13:43] <ogra> ~/.xsession-errors has nothing special
[13:43] <ogra> no panel though
[13:44] <seb128> your install seems to be busted
[13:44] <ogra> my live session runs flawless
[13:45] <ogra> and my install i did from beta was upgraded yesterday
[13:45] <ogra> and worked flawless as well
[13:46] <seb128> so what is not working?
[13:47] <ogra> my desktop doesnt come up with startx
[13:47] <ogra> gdm pops up the "greeter is dying, trying another one" msg
[13:48] <ogra> hmm, and avahi doesnt seem to work, i cant ssh into the .local address ...
[13:48] <seb128> you say it waorsk flawless and that it crashes and doesn't run at normal speed
[13:48] <seb128> I'm confused now
[13:48] <ogra> i just did an install from a fully working livesession
[13:48] <ogra> after reboot i hang at the greeter message
[13:49] <ogra> killing gdm and running startx only gets me a wallpaper
[13:49] <ogra> the testinstall i did with the beta image was upgraded yesterday and didnt show any issues
[13:50] <seb128> ok, so maybe that new install is busted in some way
[13:50] <ogra> i see nothing in the gdm or xorg logs
[13:51] <ogra> the .xsession-errors file looks fine as well
[13:51] <seb128> that's not gdm specific apparently if you get only the desktop and no normal session
[13:51] <ogra> yes
[13:51] <seb128> is your lo interface working correctly?
[13:51] <seb128> ping localhost
[13:51] <bigon> slangasek: hi, could you please accept my new telepathy-mission-control upload? (I've rerun libtoolize to fix FTBFS)
[13:51] <seb128> ping 127.0.0.1
[13:51] <ogra> works fine
[13:51] <seb128> ok so that's not that
[13:52] <ogra> nope
[13:52] <slangasek> bigon: a bit occupied at the moment
[13:52] <seb128> if you run a non GNOME session and try running nautilus or something there, what happens?
[13:52] <ogra> whats that, startx --xterm ?
[13:53]  * ogra totally forgot how to do that manually
[13:54] <ogra> ah, well ... i'll create an .xsession file
[13:54] <ogra> aha, running nautilus from the xterm segfaults
[13:54]  * ogra tries gnome-session
[13:55] <ogra> hmm
[13:56] <seb128> can you get a nautilus stacktrace?
[13:56] <ogra> x-session-manager[7681]: WARNING: Application 'gnome-wm.desktop' failed to register before timeout
[13:56] <ogra> x-session-manager[7681]: WARNING: Application 'gnome-panel.desktop' failed to register before timeout
[13:56] <ogra> doe that look ok ? ^^^
[13:58] <seb128> those are only warnings but that's nor normal
[13:58] <seb128> can you get the nautilus stracktrace?
[13:58] <ScottK> slangasek: The release not on does not boot with Intel D945 is still relevant, but needs rewording as the problem is much more widespread than we knew at Intrepid release time.  It needs to be generalized, but I'm not at all certain how to word it.
[13:58] <ogra> will try to
[13:58] <ScottK> not/note
[13:58] <ogra> i dont get a metacity either though
[13:59] <slangasek> ScottK: right, I remembered that was why the release-notes bug was open; I don't know how to word it, either
[14:00] <ScottK> slangasek: My recommendation would be: "It's a kernel bug, give it to the kernel team to figure out how to word it".
[14:00] <ScottK> After all, an action passed is an action completed. ;-)
[14:00] <slangasek> heh
[14:00] <pitti> slangasek, ScottK: is universe frozen as well? I'm currently sponsoring bug 340085 (fatal issue), and I'd like to shepherd it through the queue
[14:01] <ScottK> pitti: motu-release is reviewing stuff.  If you're happy, I'll give it an advance ack and go for it.
[14:01] <jussi01> hrm, Ive found a bug in usb-creator, can someone tell me which package is missing from the deps? http://paste.ubuntu.com/151418/
[14:01] <ScottK> siretart: Are you still around?
[14:02] <siretart`> ScottK: yes
[14:02] <ebroder> ScottK (or other motu-release types) - if I ask for an FFE to sync openafs 1.4.10 from Debian (bug #356861), am I likely to get it?
[14:03] <ScottK> siretart`: One other issue I thought of for Intel 2.4 is the Fedora compiz hack will be an issue for KDE users of your package.
[14:03] <ScottK> siretart`: http://www.kitterman.org/ScottK/2009/01/bug_254468_momentary_video_gar.html for details.
[14:03]  * siretart` looks
[14:04] <ScottK> siretart`: Do you think it might be possible to provide two binaries (one with/one without) in your package?
[14:04] <ScottK> ebroder: Assuming the title of the bug is accurate, yes.
[14:04] <pitti> ScottK: motu-release sub'ed
[14:04] <ebroder> ScottK - Version 1.4.9 was released to fix the security vulnerabilities. We're asking for 1.4.10 because it has other bugfixes in addition to the security patch
[14:05] <ScottK> ebroder: Is it just bugfix and have you tested it?
[14:06] <ebroder> ScottK: I haven't tested it personally; I believe Anders has. I can check with him
[14:06] <siretart`> ScottK: according to your blog, the patch is in xorg-server. I'm touching the intel driver only, not the xserver
[14:06] <ScottK> siretart: Right.  Nevermind then.  I got confused.
[14:06] <ScottK> Sorry for the distraction.
[14:07] <ebroder> ScottK: I can do testing before asking for the FFE; I just wanted some sense of if it was likely to be granted before I put the work in
[14:08] <ScottK> ebroder: My sense it that if you move quickly a favorable response is likely.
[14:08] <ScottK> it/is
[14:08] <ebroder> ScottK: Ok. I'll do that then. Thanks
[14:08] <siretart`> ScottK: aah, but thanks for the pointer. I've encountered it in intrepid when unlocking gnome-screensaver as well, but couldn't really describe the issue.
[14:08] <ScottK> pitti: He's a motu, so I've ack'ed it and he can upload it.  Thanks for pointing it out.
[14:08] <siretart`> now things are more clear
[14:09] <ScottK> The good news it the patch it dropped in Jaunty, so case closed.
[14:09] <ogra> lool, you bumped the version numbers in the arm p3a ?
[14:09]  * ogra tries to get back to the original gtk libs before giving seb128 qa stacktrace
[14:12]  * ogra doesnt get why the livesession works fine 
[14:15] <lool> ogra: i should have
[14:15] <lool> ogra: But if you moved /usr/lib/vfp away it doesn't make any difference
[14:15] <ogra> hmm
[14:15] <ogra> still, why does the livesession run flawless ?
[14:15] <pitti> ScottK: oh, great
[14:17] <ogra> lool, its also weird that avahi doesnt seem to function even though i see it in the processlist
[14:17] <lool> ogra: You mean on your network?
[14:17] <ogra> yes
[14:18] <lool> ogra: I think it relies on multicast, and I don't trust that too much with our current network drivers
[14:18] <ogra> ssh babbage.local doesnt work
[14:18] <ogra> it worked before
[14:18] <ogra> i *only* use it
[14:18] <ogra> and never had any probs
[14:18] <ogra> in this install i can only ssh in by IP
[14:20] <ogra> seb128, here is an strace output for you ... http://people.ubuntu.com/~ogra/nautilus-stacktrace.txt
[14:20] <seb128> ogra: I meant gdb backtrace
[14:20] <ogra> yes, i know
[14:20] <ogra> coming next
[14:23] <cjwatson> kwwii: http://people.ubuntu.com/~cjwatson/tmp/kde-partitioner.png
[14:27] <kwwii> cjwatson: that is easy, let me pick the color from the current kde4 theme
[14:28] <ogra> seb128, http://people.ubuntu.com/~ogra/gdb-nautilus.txt not really nuch
[14:29] <seb128> #0  0x40bed6e8 in memcpy () from /lib/vfp/libc.so.6
[14:29] <seb128> #1  0x40f9c1c8 in ?? () from /usr/lib/libpng12.so.0
[14:29] <seb128> ogra: seems to be a libpng issue
[14:29] <seb128> lool: ^
[14:29] <seb128> ogra: you might want to install the corresponding -dbg and get a valgrind log
[14:29] <kwwii> cjwatson: #509de8
[14:30] <lool> ogra: Could you move /lib/vfp out of the way to be sure?
[14:30] <ogra> it is moved
[14:30] <kwwii> Riddell: I took that from the Oxygen theme, it should fit fine, or?
[14:30] <lool> ogra: /lib, not /usr/lib
[14:30] <rgreening> cjwatson: ping
[14:30] <cjwatson> rgreening: yes?
[14:30] <lool> ogra: Cause the backtrace shows /lib/vfp above and I want to exclude it
[14:30] <ogra> oh, ok
[14:30] <cjwatson> kwwii: ok, thanks
[14:31] <rgreening> cjwatson: it appears that during the alt install (using daily cd) that the lpia image fails to detect dhcp during install
[14:31] <cjwatson> rgreening: can I see logs please?
[14:31] <kwwii> cjwatson: I added that to the bug as well, for clarity
[14:31] <rgreening> cjwatson: any suggestions?
[14:31] <cjwatson> rgreening: go back to the installer main menu and select "save debug logs"; you'll be able to extract it to a USB stick
[14:31] <rgreening> cjwatson: ah. ok.,
[14:32] <ogra> lool, ergh ... moving /lib/vfp now tells me "nautilus command not found"
[14:32] <cjwatson> syslog is the one I need
[14:32] <lool> ogra: run ldconfig as root, ubt I don't see why it would matter
[14:32] <lool> ogra: Perhaps you have some I/O issues
[14:32] <ogra> lool, using the full path gets me the segfault again though
[14:32] <ogra> i indeed did run ldconfig first
[14:33] <seb128> install the libpng dbg and get a valgrind log?
[14:33] <lool> It shouldn't matter too much, it's just a cache
[14:33] <rgreening> cjwatson: ok, I don't have my lpia system here.. I have to run home to get. But I have another user with same issue... jussi01.
[14:33] <ogra> why the heck does it run in the livesession
[14:33] <ogra> with identical libs and apps
[14:33] <rgreening> jussi01: are you able to help get the logs from the lpia during install?
[14:33] <cjwatson> my guess is a missing network module
[14:34] <seb128> ogra: your install might be corrupted somewhere, disk issue, ram issue, install glitch
[14:34] <rgreening> cjwatson: ok, I may have to run home... so I can check back in an hour or so if thats the case.
[14:34] <ogra> well, it worked flawless, no errors
[14:34]  * ogra checks installer logs
[14:36] <ogra> nothing there ...
[14:36] <lool> ogra: So without /lib/vfp and /usr/lib/vfp it still segfaults?
[14:36] <ogra> yes
[14:36]  * lool is relieved that it's not late breakage by these changes
[14:36] <ogra> i wonder if it has to do with langpacks
[14:36] <lool> German?
[14:37] <seb128> I doubt of it
[14:37] <ogra> its the actual only difference between a live session and the installed one i can think of
[14:37] <seb128> why would the locale trigger a crash in libpng?
[14:37] <ogra> the avahi think is also very very strange
[14:37] <ogra> *thing
[14:37] <seb128> I would rather think local corruption
[14:38] <ogra> ok, i'll try a reinstall to a clean device ... its 1h max that i lose by it
[14:39] <ogra> i would expect some error in the installer logs with corruption though
[14:40] <ogra> the last libpng upload i see on -changes predates beta
[14:42] <ogra> md5 of the image is correct ...
[14:42] <seb128> did you get a valgrind log?
[14:43] <ogra> no
[14:43] <ogra> but i have both SD cards still here
[14:44] <ogra> just want to make sure its not a worn out SD or something
[14:44] <ogra> logging out in the live session properly gets me to a gdm screen btw
[14:45]  * ogra runs the installer and leaves it in english
[14:45] <lool> ogra: I just ran nautilus in a ssh -X session on my babbage, just fine
[14:45] <lool> Using gtk+2.0 2.16.1-0ubuntu2 though
[14:46] <ogra> lool, an installed one from today =
[14:46] <ogra> ?
[14:46] <lool> ogra: No, an up-to-date dev environment
[14:46] <ogra> my upgraded system didnt show any issues
[14:46] <ogra> its only this install
[14:46] <lool> Ok; I need to try an install then
[14:46] <ogra> the fun thing is that i just overwrote the upgraded system
[14:47] <ogra> which makes seb128's theory of a corruption a weird idea
[14:47] <ogra> since the target device is known to work reliable
[14:47] <seb128> ok, so get a valgrind log ...
[14:47] <ogra> let me finish the install first
[14:47] <seb128> stop talking until then ;-)
[14:47] <ogra> heh
[14:53] <ogra> doko, you dont know which exact image you tested on your babbage, do you ?
[15:02] <directhex> bah. just for pitti, i'll go hunting in intrepid-proposed
[15:07] <doko> ogra: it was the daily, the day I tested
[15:07] <doko> and sent the email
[15:07] <mdz> is it known/intended that the Examples icon changed on the desktop CD?
[15:07] <ogra> doko, so saturdays build then i guess
[15:09] <philwyett> pitti, You just commented on https://bugs.launchpad.net/bugs/344710
[15:12] <dholbach> mdz: it's a .desktop file now which can be translated as opposed to a symlink it was before
[15:16] <ogra> doko, do you remember anything from the SD related messages you mentioned in your mail ?
[15:17] <DnaX> slangasek: hi, I'm the boy that working on irda-utils package
[15:17] <DnaX> ogra: ping, read up
[15:19] <ogra> doko, and do you have by chance your installation logs ?
[15:19] <ogra> hi DnaX
[15:19] <DnaX> MAKEDEV script is deprecated?
[15:20] <pitti> philwyett: yes, I did
[15:20] <ogra> yes, since a while already
[15:20] <philwyett> pitti, I have previously done what you commented https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/283175 and it has sat wishlisted for a long time now.
[15:20] <liw> mvo, I need to talk to you about translations
[15:21] <mvo> liw: ok
[15:21] <DnaX> instead of using it (and deactivate udev) i can insert on modprobe config file the modules ircomm-tty, irlpt and irnet
[15:21] <DnaX> ogra: ok?
[15:22] <liw> mvo, it's my understanding that the computer-janitor code located in update-manager/Janitor should use "update-manager" as the gettext domain; is this correct?
[15:24] <mvo> liw: yes, we have it in the update-manager.pot
[15:24] <mvo> liw: isn't that the case already? I was sure it was using gettext with the right args/setup
[15:24] <DnaX> ogra: I've made a patch for postrm (#340873)
[15:25] <liw> mvo, it should be the case, yes; I was just checking to make sure I know what the situation is supposed to be
[15:25] <ebroder> mvo: Oh - I finally got a chance to test your third-party sources.list config option. It works perfectly. Thanks again for putting that together
[15:26] <mvo> ebroder: execllent, thanks for testing it!
[15:26] <ogra> DnaX, just attach it, i'm way to busy with RC issues atm
[15:26] <DnaX> ogra: ok
[15:37] <mdz> davidm,lool: I see there are no test results yet for the UNR candidate; is everything OK?  do you need help?
[15:42] <davmor2> mdz: I can look at it after the cds, when I pick up tests that are left :)
[15:43] <liw> many years ago there used to be /etc/locale.gen, but it seems no more; has that been replaced by something else?
[15:44] <ogra> liw, /etc/default/locale ?
[15:44] <ogra> and/or /etc/environment
[15:44] <liw> ogra, that sets the locale to use, I am talking about what locales the system generates (or is that even a current concept?)
[15:45] <pitti> philwyett: right, we should probably just be honest and close it as wontfix; it's really not worth breaking existing installs for this
[15:45] <ogra> well, locale-gen but with the name of the locale as arg
[15:46] <liw> ogra, that would generate locales, but I want to know where the list of locales to generate is stored
[15:46] <ogra> well, i think thats read from one of the above files
[15:47] <liw> ogra, I don't think it is...
[15:48] <lool> mdz: I've reminded everybody that we need to test all flavours we care about, but didn't come to test it myself yet, I've been fighting issues with various other flavours so far
[15:48] <lool> mdz: Happy if you can test UNR though :)
[15:48] <lool> mdz: Before reinstalling the AA1 please test notify-osd though
[15:48] <pitti> ScottK: do you think the testing in bug 306889 was correct? should you still get bounces from invalid filenames?
[15:49] <mdz> lool: I don't have access to that AA1 today, it's in the office.  I don't have a netbook at home yet unfortunately
[15:49] <ScottK> pitti: I think the testing was correct.  I just uploaded a fix for post-RC in Jaunty and once that's accepted I'll update the SRU.
[15:49] <lool> mdz: (Also the mobile QA folks are on in central and west coast, so they come up a bit later)
[15:49] <pitti> ScottK: so it makes it better, but not perfect yet?
[15:49] <mdz> lool: ok, just checking if you needed help
[15:49] <ScottK> pitti: Yes.  Definitely.
[15:49] <cjwatson> liw: /var/lib/locales/supported.d/
[15:49] <philwyett> pitti, You can close it if you wish as won't fix. Kind of sad and makes me wonder a little why I bother. Thanks for your time.
[15:50] <pitti> ScottK: so then we should perhaps move it to -updates, but keep the bug open for the remaining issue?
[15:50] <mdz> lool: I'll wait for the QA folks to come around first
[15:50] <ebroder> DktrKranz: I just found one that I hadn't seen before. Let me try to extract the relevant bits
[15:50] <ScottK> pitti: I'd say close that bug and I'll open a task in Bug #360689 for Intrepid.
[15:50] <pitti> ScottK: ah, WFM; thanks
[15:51] <liw> cjwatson, thanks; so my system seems to be supporting the locale, but gtk says it's not... I guess gtk is being silly
[15:51] <ScottK> pitti: Did you get to the fakeroot SRU yet?
[15:52] <cjwatson> liw: the actual generated locales are in /usr/lib/locale/
[15:53] <ogra> bah
[15:53] <ogra> my babbage install worked flawless this time
[15:53] <ogra> lool, ^^^
[15:54] <ogra> did it in english though
[15:54] <ogra> and to a new SD card i hadnt used yet
[15:54] <ogra> lool, i'll try another one in german to the same card now ...
[15:54] <pitti> ScottK: I will, I'll fully process all SRU bits today (just in the middle of catching up with teh SRU bug mail)
[15:54] <ScottK> pitti: OK.
[15:56] <ebroder> DktrKranz: Just posted the full list of CVS deltas to the bug
[15:56] <ogra> seb128, dont wait for the valgrind log ...
[15:57] <seb128> ogra: don't worry, I've enough bugs backlog to keep busy, I'm not waiting on your issue ;-)
[15:57] <ogra> heh
[15:57] <ogra> i did an english install to a new SD card ... works now
[15:57] <asac> awe: Meru VCell :) ... wonder how  a per-station setup is special? e.g. different BSSIDs for the same ESSID, sounds normal.
[15:57] <ogra> i'll try the same in german hoping its not caused by any langpacks
[16:13] <DktrKranz> ebroder: commented
[16:14] <ogra> slangasek, i dont see the babbage image on the isotracker
[16:14] <ebroder> DktrKranz: Ok. I'll rework the bug for just the security fixes, then. Thanks for the input
[16:18] <DktrKranz> ebroder: thanks you :)
[16:18] <DktrKranz> s/s//
[16:20] <lfaraone> If I were to incorperate some of Canonical's GPL code into my project where would the apropreate place to give attribution be?
[16:21] <cody-somerville> Was console-common in ubuntu-standard in dapper?
[16:23] <cjwatson> cody-somerville: it was in ubuntu-minimal
[16:23] <cjwatson> (transitively, anyway)
[16:23] <cody-somerville> cjwatson, What was the reason that changed?
[16:24] <cjwatson> cody-somerville: it was replaced by console-setup in edgy, which unified X and console keymap configuration
[16:24] <cjwatson> http://wiki.ubuntu.com/SaneInstallerKeyboard
[16:25] <cody-somerville> Awesome
[16:25] <cjwatson> cody-somerville: Debian will be doing the same; there are a few things to fix that were more critical to Debian than to us
[16:26] <cody-somerville> cjwatson, What is Debian doing now?
[16:26] <cjwatson> hopefully we'll get those resolved this year
[16:26] <cjwatson> Debian's still on the old system
[16:26] <cjwatson> console-setup was actually mostly written in Debian, although we contributed quite a lot to it
[16:26] <cjwatson> but it isn't the default there yet
[16:27] <cody-somerville> Okay.
[16:27] <cody-somerville> Thanks :)
[16:27] <cjwatson> why the question?
[16:27] <DnaX> ogra: now all work perfectly in irda-utils package, fill patches on bug report, in time for rc?
[16:28] <ogra> no, thats post RC stuff
[16:28] <ogra> images are already rolled and in testing
[16:30] <cody-somerville> cjwatson, I didn't know it changed and noticed the lack of console-common when looking at mobile-netbook-remix's manifest file for today's build
[16:31] <cjwatson> cody-somerville: ok; just to check, though, it does have console-setup?
[16:31] <cody-somerville> cjwatson, sure does
[16:32] <seb128> does the bbc plugin list only 1 item for other people too?
[16:35] <awe> asac: ping
[16:39] <asac> awe: yes. i am still here ;)
[16:40] <awe> asac: the per-station bssid.  yikes.  ;)
[16:40] <awe> asac: i think it's something to do with the key exchange
[16:40] <asac> awe: hehe. just curious how that is different to a "normal" shared essid setup
[16:41] <asac> wasnt obvious from what you pasted/wrote
[16:41] <mvo> seb128: bbc-plugin> I have a lot more, my totem is 2.26.1-0ubuntu2
[16:42] <awe> asac: whenever the mainframe ( or  whatever you want to call it ), sees a new station send a Probe, it responds with a new BSSID
[16:42] <mvo> seb128: let me upgrade
[16:42] <awe> so every station gets a unique BSSID for the same ESSID
[16:43] <awe> I don't understand how this messes up the key exchange, but this setup seems to work fine for Open and WEP configurations
[16:43] <asac> awe: are those BSSIDs kind of volatile? e.g. does the main frame hand out new ones regularly or something?
[16:43] <awe> I spent about 4 hours onsite to narrow it done to what I described.  I'll probably need to go back onsite again to get further details.
[16:44] <awe> asac: it hands out a new BSSID for each unique station
[16:44] <awe> I don't know whether they can be re-used or not
[16:45] <DnaX> ogra: all done (bug #340873)
[16:45] <awe> Anyways, smagoun asked me to file an upstream bug, but I realize you can't do much without more info
[16:46] <DnaX> ogra: what about this? https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/361431
[16:47] <awe> asac: I need to get back to another fire I'm fighting right now, and am also supposed to leave for a few days of vacation tonite.  Perhaps we can chat more about this next week, and maybe I'll go onsite again to get more details
[16:47] <asac> awe: yeah. i think that info isn't really enough. we need kind of output of wpasupplicant and maybe even driver and so on
[16:47] <directhex> hm. interesting.........
[16:47] <asac> awe: enjoy your holiday. i guess its not that urgent ;)
[16:48] <directhex> well i never!
[16:48] <awe> asac: thanks!
[16:49] <ogra> DnaX, thats nothing for jaunty anymore ... its not even triaged
[16:57] <liw> mvo, I have just prepared a new computer-janitor upload and requested a freeze exception; if it gets accepted, could I entice you to do the upload?
[16:57] <mvo> liw: sure
[16:58] <liw> mvo, excellent, thank you
[17:07] <ogra> slangasek, so since there are no babbage images on the isotracker i'll report directly to you :P i did two successful english and one gernam install of the imx51 image today (one broken one due to HW issues), its fine to go out as RC
[17:07] <ogra> *german
[17:09] <robbiew> Keybuk: two minutes for FC11?  wow
[17:10] <Keybuk> yeah, they're really laying down the gauntlet
[17:11] <ogra_babbage> wohoo
[17:11] <Keybuk> normally I'd be a lot nicer about my open source colleagues work, but I'm really enjoying the muppetfreude
[17:12]  * ogra googles muppetfreude
[17:12] <Keybuk> ogra: it's a word that elmo invented
[17:12] <ogra> hehe
[17:12] <Keybuk> you know how schadenfreude is delight in the suffering of others?
[17:12] <Keybuk> muppetfreude is delight at the incompetence of others
[17:12] <ogra> yeah
[17:12] <ogra> its an ingenious word
[17:12] <ogra> kudos elmo
[17:13] <kees> james_w: can you quickly patch bug 236305 to have s-t-b just block the creation of the "admin" user as a quick work-around?
[17:14] <james_w> kees: probably. It was jpds that was looking at that
[17:14] <kees> james_w: ah, okay.
[17:14] <kees> james_w: I wasn't sure if a fix was pending.
[17:15] <james_w> jpds: what do you think of that solution for Jaunty?
[17:16] <ebroder> kees: Got a second to look at bug 356861? We have a patch now for all 4 releases
[17:16] <jpds> kees, james_w: I _think_ that there's a patch available at: http://mail.gnome.org/archives/system-tools-list/2008-May/msg00006.html
[17:18] <kees> ebroder: later on today, most likely.  I have a bunch of publication work to do today.
[17:18] <ebroder> Ok, cool
[17:18] <james_w> jpds: I don't see that diff fixing the issue
[17:18]  * hyperair pokes dtchen
[17:20] <hyperair> dtchen: #202089 worth an upload? it seems that pitti would like it fixed for good
[17:21]  * pitti waves with the "Jaunty is in deep freeze" banner
[17:26] <calc> is it possible to get a copy of the LSB spec anymore?
[17:26] <calc> it seems to have vanished over the years
[17:26] <hyperair> use the source, calc.
[17:26] <Keybuk> calc: linuxbase.org?
[17:27] <calc> Keybuk: couldn't find it on there but found it on freestandards.org finally
[17:27] <jpds> james_w: I'll take another look at the source later.
[17:27] <james_w> jpds: cool, thanks
[17:33] <doctormo> Does anyone know much about python/gtk/glade and how to get them to use po translations? None of the tutorials I try seem to work for this project and I could do with some assistance.
[17:36] <jpds> doctormo: Standard gettext module doesn't work?
[17:36] <doctormo> jpds: not the way I'm using it
[17:48]  * calc is somewhat surprised bo is arguing that ia64 is supposed to be installed into /usr/lib64 also as LSB essentially contradicts that without actually coming out and saying it (afaict)
[18:03] <mdz> bryce: is bug 358574 a duplicate of bug 359392?
[18:14] <liw> I need to change a patch to the kernel; what's the best process to do that in Ubuntu? get the kernel source package, apply patch, dch -i, debuild?
[18:14] <directhex> hm. are there any new headline items that people want to include in karmic which are going to cause the usual crunch for CD space?
[18:16] <calc> directhex: java :)
[18:17] <directhex> blimey
[18:17] <directhex> openjdk?
[18:17] <calc> there has been some talk of getting openjdk and the java bits for OOo onto the cd, not sure if the OOo bits will make it though
[18:17] <superm1> liw, that would take a long time to build. i'd use the info from the wiki (https://help.ubuntu.com/community/Kernel/Compile) instead
[18:17] <superm1> liw, it's got advice on how to just build one of the x86 kernels rather than the 4 or so that it normally would
[18:18] <directhex> calc, i think magicking 100 meg for openjdk is already a major challenge
[18:18] <liw> superm1, thanks; I'd be happy to wait for it to compile, as long as the result is correct, though
[18:18] <directhex> calc, my current chain of thought is only offering to free up ~4 meg
[18:19] <superm1> liw, well you will have just as accurate a result, just far quicker if you follow the directions on that page
[18:19] <directhex> calc, this chain of thought may also result in lynchings
[18:24] <bryce> mdz, sounds like it
[18:25] <bryce> mdz, although I'd not seen that particular error message before..  But the timing and symptoms match up
[18:26] <calc> directhex: i think there are some plans to free up more space, but i don't know how
[18:26] <directhex> calc, i'm sure details will be forthcoming at UDS
[18:27] <directhex> calc, if it were to receive some fixing of slightly over-eager Recommends:, then replacing Rhythmbox with Banshee would save megs & add features
[18:28] <directhex> calc, this is not the case today, but certainly when using --without-recommends the numbers speak for themselves
[18:28] <bddebian> lamont: Hey, I almost forgot about you. :)  Do you have any plans for xdelta?
[18:30] <calc> directhex: ok
[18:30] <directhex> calc, however, i suspect some areas of the internest would start a riot if this were to take place
[18:34] <lamont> bddebian: meh
[18:35] <lamont> what does it want? besides firey death?
[18:35] <jdong> kees: what level of local access is necessary to compromise udev as per USN-758?
[18:35] <Mirv> directhex: has there been any talk lately about using lzma on squashfs?
[18:36] <directhex> Mirv, i don't know. would that be good?
[18:36] <bddebian> lamont: That's fine with me to, I just want libglib1.2 gone. :)
[18:37] <calc> Mirv: i believe cjwatson thinks that is a bad idea
[18:37] <bddebian> Of course debdelta and pristine-tar are still r(b)deps afaik
[18:37] <calc> Mirv: would both increase memory requirements and slow it down more afaik
[18:37] <Mirv> directhex: not as good as with packages, but sladen (or someone) estimated 15% gain could be done
[18:38] <Mirv> calc: I know
[18:38] <directhex> Mirv, 15% of 700 meg is almost java
[18:38] <kees> jdong: any local user.
[18:38] <maxb> ooi, has anyone looked into lzma-compressed .debs ?
[18:38] <Mirv> directhex: I know :) it could be something to play with, even if it would be too slow / memory-hog on low-end computers. it's soon time for play-time anyway.
[18:39] <jdong> kees: lovely :) whee
[18:39] <Mirv> maxb: they are in use already selectively, for example openoffice
[18:39] <calc> maxb: i implemented it back in 7.10
[18:39] <kees> jdong: i.e. the ability to run a C program
[18:39] <jdong> kees: is there a PoC anywhere?
[18:39] <calc> maxb: er 8.04 actually
[18:39] <jdong> kees: I presume most udev-using distros are vulnerable?
[18:39] <directhex> maxb, depends on whether you want debian compatibility
[18:39] <kees> jdong: I am unaware of a public exploit, but it probably won't take long to be developed
[18:39] <maxb> I mean, how much CD space would be saved by using them across the board.
[18:40] <calc> maxb: maybe 150MB more than current maybe, but it would increase unpack requirements by 30MB for all packages
[18:40] <kees> jdong: yes, any distro running udev is vulnerable.  I'm not aware of any work-arounds either.  it's a pretty serious issue.
[18:40] <calc> er 30MB memory
[18:40] <lamont> bddebian: ah, that.  yeah - let me get a debian upload to close the debian bug and then I'll request a sync,  because hey, why it's not like we're frozen or anything :-D
[18:40] <jdong> kees: yeah if that's understatement of the day. Ouch.
[18:40] <kees> jdong: note that it requires a reboot as well.
[18:40] <calc> maxb: see wiki.ubuntu.com/dpkg-lzma
[18:40] <jdong> kees: noted
[18:40] <ebroder> kees: Restarting udev isn't good enough?
[18:41] <ebroder> I missed that in the notice. Bleh
[18:41] <kees> ebroder: you can stop/start it, but you'll likely lose ptys, etc.  i.e. ssh broke for me when I tried a stop/start
[18:41] <jdong> ebroder: is it yet another fun day for linerva? :)
[18:41] <bddebian> lamont: Well I meant for Debian :)
[18:41] <ebroder> jdong: It very well might be
[18:41] <lamont> ah, ok
[18:42] <Mirv> maxb: on live CD the packages aren't available as such, since the whole CD is a squashhfs image. therefore for live-cd lzma usage squashfs-lzma should be used.
[18:42] <ebroder> jdong: And we were just finally starting to build up some uptime!
[18:42] <jdong> ebroder: haha, always something to ruin it :)
[18:42] <jdong> *attempts a udev stop-and-start on a test box*
[18:43] <Mirv> maxb: so on live cd it doesn't matter even if all packages used lzma
[18:43] <Mirv> and someone correct me if I'm wrong etc :)
[18:43] <Keybuk> jdong: don't do that
[18:43] <jdong> Keybuk: hehe alright then, jdong will reboot instead :)
[18:44] <maxb> I was going to say "there are some loose packages on the livecd", but only 32 and they come to <10MB
[18:44] <Keybuk> jdong: you can use /etc/init.d/udev restart
[18:44] <Keybuk> but then the upgrade should do that for you
[18:45] <jdong> Keybuk: so does applying the update without restarting effect the security update?
[18:45] <Keybuk> you must restart the running udevd
[18:45] <Keybuk> it us udevd that is exploitable
[18:46] <Keybuk> kees: interesting point, jaunty will restart the running udevd - but pre-jaunty won't
[18:46] <ebroder> kees: Are you in touch with the Debian security team yet? Do you know if we should expect an update today? This week?
[18:47] <kees> ebroder: they are aware of it; I'm not sure when it is planned for.  I know RH said they won't be publishing today.  I expect SUSE to publish shortly.  (1700 UTC was their idea)
[18:47] <Keybuk> jdong: it's pretty safe to just kill udevd and run udevd --daemon again
[18:48] <Keybuk> if you plug a USB device in at *that exact moment* it won't work, OBVIOUSLY :p
[18:48] <kees> Keybuk: I put notes in the USN to reboot.  That's not uncommon.
[18:49] <jdong> Keybuk: ah, thanks :)
[18:49] <geofft> hm. on a server where you don't expect new hardware after boot, can you just kill udevd?
[18:49] <Keybuk> geofft: probably not recommended
[18:49] <Keybuk> various things stop working
[18:49] <Keybuk> (if you don't restart it again)
[18:51] <Aleksey_S> hi all
[18:51] <Aleksey_S> guys, is here someone experienced in audio?
[18:53] <Aleksey_S> especeally, i am interested in bug 354522
[18:58] <ashmew2> hi
[18:58] <ashmew2> i need to ask something
[18:58] <ashmew2> where do i start as a ubuntu deve ?
[18:58] <ashmew2> developer*
[18:58] <ashmew2> i dont know where to begin , which language to learn.
[18:58] <ashmew2> What to do
[18:59] <liw> ashmew2, have you read https://wiki.ubuntu.com/UbuntuDevelopment ?
[19:00] <Aleksey_S> I am not member of ubuntu-devel team, just user of ubuntu. but as programmer i can say, that no mean what language do you know
[19:05] <ashmew2> liw: I tried that site
[19:05] <ashmew2> Aleksey_s: Which language is most suitable ?
[19:05] <ashmew2> C or python or C++
[19:06] <Aleksey_S> unfortunately, there isn't simple answer on this sort of questions
[19:06] <geofft> ashmew2, find things you're interested in making better for yourself personally
[19:06] <ashmew2> hmm..ok..so i start by learning one language from scratch , like hello world
[19:06] <geofft> and learn whatever language that code is in. That's the most effective way
[19:06] <liw> ashmew2, Ubuntu consists of tens of thousands of programs, written in hundreds of languages
[19:07] <Aleksey_S> yes.
[19:07] <ashmew2> If i am an absolute beginner at programming ,will C++ be a good start ?
[19:07] <liw> ashmew2, Python is probably the easiest to learn; C, C++ and perl are also very common
[19:07] <geofft> The best way to be a better coder is to read and understand and hack existing code.
[19:07] <Aleksey_S> if you want to be experienced programmer don't start with python etc
[19:07] <Aleksey_S> interpreted languages, i mean
[19:07] <ashmew2> Start with C++ then ?
[19:07] <ashmew2> yeah i get that
[19:07] <Aleksey_S> yes
[19:08] <Aleksey_S> then java python etc, will be very simple to learn for you
[19:08] <ashmew2> So..you learn gradually from tutorials on the internet how to develop applications ? I mean you start from Hello World..
[19:08] <liw> I think it's perfectly fine to start with Python or other interpreted languages even if you want to become an experienced programmer (he says, having been a programmer for 25 years now, and started with an interpreted language )
[19:08] <ashmew2> wow..
[19:08] <liw> ashmew2, if you don't know how to program, may I suggest: http://www.htdp.org/
[19:08] <dtchen> Aleksey_S: what are the audio codecs in use for the two computers?
[19:08] <ashmew2> 25 years is a LONG time
[19:09] <ashmew2> liw:Thanks for the link :D
[19:09] <Aleksey_S> dtchen: i don't follow
[19:10] <ashmew2> Thanks guys! Cya around (hopefully) :D
[19:10] <Aleksey_S> i think it is very hard to understand pointer arifmetics etc when you started with high level language
[19:10] <dtchen> Aleksey_S: for the bug report you quoted, what are the audio codecs in use?  see /proc/asound/card*/*codec*{,/*}
[19:10] <ashmew2> yeah
[19:10] <ashmew2> i tried doing pointers
[19:10] <ashmew2> and cant understand it in C++
[19:10] <ashmew2> arrays is ok
[19:10] <Aleksey_S> are this info missing in my reports attached?
[19:10] <ashmew2> simple programs is ok
[19:10] <ashmew2> well i g2g..Cya
[19:13] <Aleksey_S> dtchen: i thought i attached all required info. if it isn't so, i will reboot to ubuntu and gather that info. unfortunately, it will be not easy, because my espeak sounds terrible
[19:13] <Aleksey_S> and i am visually impaired, i can't work without speech support
[19:14] <dtchen> Aleksey_S: ah, yours is present. (too many people commenting in that bug report without attaching necessary info)
[19:14] <dtchen> Aleksey_S: one thing you could try is using a kernel with ALSA fixes
[19:15] <dtchen> Aleksey_S: i've posted a test at http://kernel.ubuntu.com/~dtchen
[19:16] <Aleksey_S> do you think it is alsa bug?
[19:16] <Aleksey_S> all apps, which aren't using portaudio work correctly
[19:17] <dtchen> Aleksey_S: it's not clear whether it's only portaudio or some other component in the stack
[19:18] <Aleksey_S> ok then
[19:18] <Aleksey_S> how i can test your kernel?
[19:19] <Aleksey_S> e.g. what i need to do to install it
[19:19] <dtchen> Aleksey_S: do you use proprietary drivers according to Hardware Drivers?
[19:20] <Aleksey_S> mmm
[19:20] <Aleksey_S> i have intel video
[19:21] <Aleksey_S> and atheros wifi card. but i think it uses freevare driver
[19:21] <Aleksey_S> i think no, i am not using proprietary drivers
[19:21] <Aleksey_S> can you gather that info from my attachments?
[19:22] <dtchen> well, apport reports that you aren't using any, but that's only at the time of post
[19:22] <Aleksey_S> sure then
[19:23] <dtchen> so, we'll assume you only need to install http://kernel.ubuntu.com/~dtchen/linux-image-2.6.28-12-generic_2.6.28-12.42~crimsun2lp345627_amd64.deb
[19:24] <Aleksey_S> how about headers etc?
[19:24] <dtchen> sha256sum == 5ab3db6eaf636a5aaa348eefa876bea7f4079da4e95db73b25d697aa8e8250ab
[19:24] <Aleksey_S> *what about
[19:24] <dtchen> Aleksey_S: let's migrate to #ubuntu+1 so we don't clutter this channel
[19:24] <Aleksey_S> that checksum doesn't mean anything to me. i don't know how to check it under linux
[19:25] <Aleksey_S> #ubuntu+1? is + sign allowed in channel names?
[19:25] <dtchen> yes
[19:29] <ubuntuman> hi
[19:29] <ubuntuman> !seen amitk
[19:30] <ubuntuman> anybody here involved in the arm port who can explain to me why the orion5x support has been dropped?
[19:31] <ubuntuman> i use a linkstation from buffalo and was going to install the beta right now in it, seeing the installer image and kernel have been removed :(
[19:52] <mdz> Keybuk: can you tell me how to extract the UUID from a swap device?
[19:53] <mdz> Keybuk: ah, never mind, vol_id does it
[20:13] <liw> pitti, slangasek: about #361792 (freeze exception for computer-janitor): I don't want to push the release managers, but I need to know whether I should stay up and wait for the verdict or whether I can go sleep
[20:15] <pitti> liw: if in doubt, just upload it, and be prepared for it to get rejected
[20:15] <pitti> liw: it won't go into RC anyway
[20:15] <pitti> so no need to stay up
[20:15] <liw> pitti, ah, that's what I needed to know, thank you
[20:33] <mdz> pitti: did you already upload apport -0ubuntu5?
[20:33] <pitti> mdz: yes, it's sitting in the unapproved queue
[20:33] <mdz> pitti: is it safe to commit a trivial change to the ubuntu branch?
[20:34] <pitti> mdz: you can always commit it, but I can't guarantee that it will land in jaunty proper
[20:34] <mdz> pitti: it's not urgent for jaunty, I just want to get it off of my HDD
[20:34] <mdz> pitti: it's a one-liner in a hook, if for some reason you did need to do another upload it would be safe
[20:35] <pitti> mdz: sure; and if not, it'll just land in karmic
[20:35] <jpds> kees: Patch added to bug #236305.
[20:35] <mdz> pitti: thanks, done
[20:35] <kees> jpds: cool, thanks.
[20:36] <mdz> ogasawara: the change I just committed in apport r1390 will attach the missing info from https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Hibernate specific information
[20:36] <ogasawara> mdz: awesome, thanks
[20:36] <mdz> ogasawara: if there are any other places where you're still asking for users to collect info manually, I am happy to help add those to the hook as well, just point me to them
[20:37] <ogasawara> mdz: will do
[20:37] <mdz> ogasawara: it's very easy, this one was a two-line change:
[20:37] <mdz> +	attach_file_if_exists(report, "/etc/initramfs-tools/conf.d/resume",
[20:37] <mdz> +                          key="HibernationDevice")
[20:39] <ogasawara> mdz: so it should be easy for us to whip up any future patches
[20:39] <mdz> ogasawara: yes, I've added a lot of convenience functions to make common things into one-liners
[20:39] <mdz> ogasawara: "attach the output of this command", "attach this file", and so on
[20:39] <mdz> ogasawara: "pydoc apport.hookutils" shows everything that is available
[20:48] <pitti> mdz: ah, I rejected the ubuntu5 upload from the queue, since I messed up (apport.default still in the orig.tar.gz)
[20:48] <pitti> mdz: oh, did you already upload 0ubuntu6? it says "jaunty", not "UNRELEASED"
[20:48] <mdz> pitti: that's my mistake, it should be UNRELEASED
[20:48] <mdz> you can merge it into ubuntu5 if you want
[20:49] <pitti> mdz: done, and pushed
[20:54] <mdz> pitti: apport-collect didn't do quite what I'd hoped on bug 361852 (no hook info).  is that a bug?
[20:57] <pitti> mdz: ah, it's the old source vs binary package confusion
[20:58] <pitti> there is no "linux" package (at least not the one you mean)
[20:58] <pitti> mdz: workaround: apport-collect -p linux-image-2.6.28-11-generic 12345
[20:58] <pitti> but it shoudl be clever enough to at least run the source package hooks
[20:58] <pitti> so that's also a bug
[21:01] <dtchen> mdz: is there a way to filter output from a command using apport.hookutils's command_output()?
[21:02] <dtchen> mdz: use case is: pactl stat|grep ^Default
[21:37] <YokoZar> Anyone know when mvo will be back?
[21:37] <YokoZar> he seems to have disappeared on vacation or something
[21:37] <ScottK> He was back today
[21:44] <kees> cjwatson: I want to answer the question "what source packages have binary packages in the seed supported-server?"  Due to moving of binaries "up" when germinate runs, is there no output that can answer that question short of walking the STRUCTURE file myself and expanding each seed?
[21:50] <ubuntuman> anybody here involved in the arm port who can explain to me why the orion5x support has been dropped?
[22:25] <kees> bryce, kirkland, soren: do any of you know what the magic is that causes my mouse to track in a guest X session in virt-viewer _without_ having had to click into the viewer?  This works for me on hardy, but not jaunty.
[22:26] <kirkland> kees: i'd guess that this is a vnc option
[22:26] <kees> kirkland: but it works in my hardy guests...
[22:27] <kirkland> kees: oh, hmmf
[22:37] <tjaalton> kees: hardy probably uses -input-vmware
[22:38] <kees> tjaalton: ah-ha.  is that still available in later releases?  (and if so, how do I enable it?)
[22:38] <tjaalton> sorry, -vmmouse
[22:38] <tjaalton> it is, but you'd need to disable evdev
[22:38] <tjaalton> on the guest
[22:39] <kees> cjwatson: nm, nijaba says you're busy.  :)
[22:40] <kees> tjaalton: isn't that a not-good thing to do?
[22:40] <tjaalton> copy the hardy xorg.conf and then add 'Option "AutoAddDevices" "false"' to ServerFlags
[22:41] <tjaalton> kees: probably isn't that worrying on a virtual guest
[22:41] <kees> okay
[22:42] <tjaalton> -vmmouse could ship an fdi file to override evdev
[22:42] <tjaalton> oh, it does
[22:43] <tjaalton> so check that it's used, 'lshal' and look for the mouse
[22:44] <tjaalton> and the value of input.x11_driver
[22:44]  * kees switches to #u-x
[23:02] <jdong> tjaalton: wow creepy I just posted about that on the forums.
[23:03] <jdong> http://ubuntuforums.org/showthread.php?p=7079221#post7079221
[23:03] <jdong> the vmware planets have aligned.
[23:06] <tjaalton> jdong: heh, ok then.. the fdi file should just be fixed
[23:07] <jdong>   input.x11_driver = 'evdev'  (string)
[23:07] <jdong> what info is helpful for fixing it?
[23:08] <tjaalton> so filing a bug against -vmmouse with ubuntu-bug from a VM should gather enough information to fix it
[23:09] <tjaalton> running ubuntu-bug should include everything
[23:09] <tjaalton> but at least the lshal output from the VM is needed
[23:10] <tjaalton> hal-probe-vmmouse doesn't seem to do it's business
[23:10] <jdong> yeah that seems to be the issue
[23:12] <jdong> haha ubuntu-bug OOM.
[23:12] <jdong> obviously I trimmed back this VM a bit too much.
[23:12] <jdong> do you feel the lshal alone is sufficient info?
[23:13] <tjaalton> should be enough
[23:13] <tjaalton> do you have mdetect installed?
[23:14] <jdong> no; should I?
[23:14] <tjaalton> because hal-probe-vmmouse uses vmmouse_detect from mdetect
[23:14] <tjaalton> no wonder it doesn't work
[23:14] <jdong> wow.
[23:14] <jdong> you're kidding :D
[23:14] <tjaalton> try installing it
[23:15] <tjaalton> the newer upstream version of -vmmouse includes it
[23:16] <tjaalton> ..which seems to be four months old, oops
[23:17] <jdong> tjaalton: works
[23:17] <jdong> do you think we can get this through freeze?
[23:17] <tjaalton> file a bug and we'll see :)
[23:18] <jdong> roger
[23:24] <slangasek> ogra: great, thanks for the update
[23:26] <slangasek> liw: as pitti says, when in doubt, upload to the frozen queue :)
[23:31] <kees> kirkland: okay, usplash inits the screen and then quits immediately (without drawing anything) on my jaunty VM...
[23:31] <kirkland> kees: what's your kvm command line?
[23:32] <kees> /usr/bin/kvm -S -M pc -m 512 -smp 1 -name 64bit-Ubuntu-9.04-desktop -uuid ea8cfb3a-cd8f-d588-14bd-a809b2ce6ac1 -monitor pty -pidfile /var/run/libvirt/qemu//64bit-Ubuntu-9.04-desktop.pid -boot c -drive file=/vmware/64bit-Ubuntu-9.04-desktop.qcow2,if=ide,index=0,boot=on -net nic,macaddr=00:0c:29:5f:50:a9,vlan=0,model=virtio -net tap,fd=21,script=,vlan=0,ifname=vnet2 -serial none -parallel none -usb -vnc 127.0.0.1:2
[23:32] <kirkland> kees: let me try with those options
[23:33] <kees> kirkland: actually, this might be simpler than that....
[23:33] <kees> kirkland: ran it on the cmd line, got "no usable theme found for 1024x768"
[23:33] <kirkland> kees: oh, hmm, yeah, that would do it
[23:33] <kirkland> kees: we should add higher res themes to usplash-themes
[23:34] <kees> kirkland: gimme a second to investigate... I think I hadn't been noticing it due to the X crasher.  I assumed it was all related
[23:34] <kees> hrm, no luck.
[23:37] <kees> kirkland: all my own fault.  I think i've got it sorted
[23:38] <kirkland> kees: yeah, i was able to launch my vm with your command (mostly)
[23:38] <kirkland> kees: what was your problem?
[23:39] <kees> kirkland: I'd written a custom usplash package and didn't correctly unregister its alternative when removed.
[23:39] <kirkland> kees: :-)
[23:40] <jdong> hahaha :)