[00:07] <asac> ok i think i got it sdkpath was a complete mess
[00:07] <asac> uploaded asac2
[00:07] <asac> 4 more minutes to know ;)
[00:13] <asac> hmm seems will take a bit longer :/
[00:13] <asac> someone pushed a batch to builders
[00:13] <micahg> ok, I have to reboot in a minute
[00:14] <micahg> brb
[00:20] <asac> https://edge.launchpad.net/~asac/+archive/ppa/+build/1310215
[00:21]  * asac waits
[00:21] <micahg> asac: I just got clobbered by overeager xid caching
[00:21] <asac> yeah
[00:21] <asac> its going ahead
[00:21] <asac> now compiling
[00:21] <asac> ;)
[00:21] <asac> lets hope it doesn fail late
[00:24] <asac> http://pastebin.com/f398c7202
[00:24] <asac> thats the full debdiff
[00:24] <asac> the SetSDKPath part is probably not needed after i set the env in debian/rules
[00:24] <asac> but SetSDKPath was used in a lots of more patches ... which means that whoever did that, did clearly not understand what to do
[00:25] <asac> micahg: you got the XiD warnings?
[00:25] <asac> any bad consequence ;)
[00:25] <asac> ?
[00:25] <micahg> ate up > 3GB on home
[00:27] <asac> .xsession-errors?
[00:27] <asac> ouch
[00:27] <asac> thats really bad
[00:27] <asac> ok
[00:27]  * asac takes a big note to remove that warning asap
[00:27] <asac> helix still building
[00:27] <asac> good sign i guess
[00:28] <asac> unfortauntely i cant remember if lpia failed
[00:28] <micahg> I thought it was cause by something besides ff
[00:28] <asac> have to check that before being too happy ;)
[00:28] <asac> micahg: its just a warning that was added to latest gtk versions
[00:28] <asac> the same code path probably existed before
[00:28] <asac> but cluttering .xsession-errors by this amount is insane
[00:28] <asac> and we couldnt identify any correlation of this to crashes
[00:31] <asac> Successfully built  on meitnerium (virtual)
[00:31] <asac> https://edge.launchpad.net/~asac/+archive/ppa/+build/1310215
[00:31] <asac>  \o/
[00:31] <asac> what a hackfest ;)
[00:31] <asac> now ... does it work at all ;)?
[00:32] <micahg> ggod q
[00:32] <asac> good amd64 and i386 is bulding too now
[00:32] <asac> so we can test
[00:32]  * asac crosses fingers
[00:32] <asac> any idea how to test that ;)?
[00:33] <micahg> try helix content ?
[00:33] <asac> dunno where to find ;)
[00:34] <asac> hmm. maybe the wiki has that
[00:34] <asac> https://wiki.ubuntu.com/MozillaTeam/QA
[00:34] <asac> no example site :(
[00:34] <asac> great
[00:36] <asac> http://service.real.com/realplayer/test/
[00:36] <asac> that ?
[00:37] <micahg> sure
[00:37] <micahg> well, old version was broke
[00:38] <micahg> let's hope the new version works
[00:48] <asac> ok installing ;)
[00:49] <asac> audio/x-pn-realaudio-plugin
[00:49] <asac> so thats in about:plugins
[00:49] <asac> now checking tes
[00:50]  * BUGabundo /usr/local/bin/xfcre76 BUGabundo | tee /dev/sleep
[00:50] <asac> mm only rpm suffix
[00:50] <asac> BUGabundo: swq
[00:50] <asac> sw
[00:50] <BUGabundo> :S
[00:50] <BUGabundo> guud night
[00:54] <asac> micahg: uploaded
[00:55] <micahg> asac: it's  broke
[00:55] <micahg> core dump
[00:55] <asac> not for me ;)
[00:55] <asac> what did you try?
[00:55] <micahg> weird
[00:55] <micahg> http://service.real.com/learnnav/testrams/realvideo10_LAN.ram
[00:56] <asac> i have no idea what to test besides checking about:config
[00:56] <micahg> actually just launching the player fails
[00:56] <asac> .ram ... we need rpm files
[00:56] <asac> yes
[00:56] <asac> that plugin only deals with rpm
[00:56] <asac> i think thats a wrapper plugin
[00:56] <asac> which also requires a realplayer install in the back
[00:56] <asac> which i then raps if someone specifies the real player plugin mimetype
[00:56] <asac> seems to be something on top of normal realaudio streams
[00:57] <asac> but thats just what i got from a quick look ;)
[00:58] <asac> yeah so you need the realplayer package too
[00:58] <micahg> it works
[00:58] <micahg> http://guide.real.com/bestwebvideo
[00:59] <micahg> realplayer is the proprietary version
[00:59] <asac> indeed
[00:59] <asac> that thing is really real?
[00:59] <micahg> It has the real log
[00:59] <micahg> logo
[00:59] <asac> no that is flash
[00:59] <asac> no that is flash
[01:03] <micahg> it seems like it's all fglash
[01:03] <asac> how unfortunate that rpm is a confliciting suffix with redhat packages ;)
[01:05] <micahg> all I see are ram files
[01:05] <asac> yes
[01:05] <asac> me too
[01:06] <asac> asked in identi.ca twitter
[01:06] <asac> lets check
[01:07] <asac> no answer yet
[01:07] <asac> not good
[01:09] <asac> well... assume tahts the best we could still do for karmic ;)
[01:09] <asac> i wouldnt think it should be more broken than it was when it worked with ffox 3.0
[04:44] <dtchen> asac: WRT the sqlite3 staging for karmic-security in the PPA, is there a test case (or set of) that I should run? Should I be using the one mentioned in the bugzilla report?
[09:36] <asac> dtchen: oh coool. you found it? ... so yeah. i think for firefox the best you can get is "normal" use
[09:36] <asac> and "test in bugzilla"
[09:36] <asac> i am not so sure about what else to test to be sure that it doesnt introduce regressions in other apps
[09:39] <micahg> asac: I found another FTBFS if you want to fix it before release
[09:39] <asac> micahg: ?
[09:39] <micahg> on the test archive rebuild
[09:39] <micahg> https://launchpad.net/ubuntu/+archive/test-rebuild-20090909/+build/1225493
[09:40] <micahg> mozilla-bonobo
[09:40] <micahg> otherwise, I'll try to fix it after release
[09:41] <asac> hmm
[09:41] <asac> i thought i fixed that earlier this cycle
[09:41] <micahg> it's just a rebuild, hasn't been touched since intrepid
[09:42] <asac> http://news.bbc.co.uk/1/hi/technology/8326264.stm
[09:42] <micahg> wow
[09:42] <micahg> didn't even build in intrepid
[09:42] <asac> it has build deps on iceape
[09:43] <asac> that says all i guess
[09:43] <micahg> we have iceape
[09:43] <asac> we have?
[09:43] <micahg> yep
[09:43] <micahg> http://pastebin.com/f2a55774a
[09:43] <asac> https://edge.launchpad.net/ubuntu/+source/iceape/+changelog
[09:43] <asac> no sign of it since guty
[09:43] <asac> gutsy
[09:44] <micahg> well, we have a dev package for it
[09:44] <asac> ah you probably have seamonkey-dev
[09:44] <asac> then
[09:44] <micahg> yes
[09:44] <micahg> ah
[09:44] <micahg> that must be it
[09:44] <micahg> it's a stub package
[09:45] <asac> hmm
[09:45] <micahg> ok, I have to go to sleep
[09:45] <micahg> just figure I'd mention it in case you want to do it in the next 2 hours
[09:46] <micahg> otherwise, I'll do it for the next release
[10:46] <asac> xul 1.9 might still get out ;)
[10:46]  * asac hopes
[11:27] <asac_empathy> empathy for the world ;)
[11:53] <asac> back to irssi ;)
[12:59] <Cobalt> Hello. I'm using Firefox 3.5.x from the Ubuntu daily build PPA. However, it defaults to using Qt rather than GTK. I've seen no options to choose one over the other, there are no real indications on the web either. Also, there does not appear to be any different packages for one or the other. I have installed the gnome-support .debs, to no avail. Any pointers please?
[12:59] <Cobalt> Sorry, if I appear to be cross-posting, I was just informed of the existence of this channel.
[13:08] <av`> Cobalt, how do you know it's using Qt?
[13:09] <Cobalt> av`: My Qt apps look the same as Firefox. My GTK apps render their widgets differently. Also, different font rendering.
[13:11] <av`> I never had this problem and I use firefox since ages
[13:11] <av`> Cobalt, asac should be able to help you
[13:11] <av`> I'm leaving
[13:11] <Cobalt> Okay. I'll hang around in the channel, and ask again later.
[13:11] <av`> great :)
[13:20] <asac> Cobalt: not sure what you mean with Qt
[13:20] <asac> ffox uses gtk
[13:20] <Cobalt> asac: I'm looking for a screenshot I made when I first used Shiretoko. Gimme a minute.
[13:21] <eagles0513875> hey asac
[13:21] <asac> hi eagles0513875
[13:22] <eagles0513875> how goes things
[13:22] <eagles0513875> im sure your swamped finishing up stuff for release
[13:22] <asac> i stopped working directly
[13:22] <asac> do planning for lucis and ISO testing
[13:25] <Cobalt> asac: http://www.pastehere.com/PasteImages/mqednt.jpg
[13:26] <asac> whats the problem with that?
[13:26] <asac> looks normal to me
[13:26] <Cobalt> asac: Look at the menu bar. The rendering on the Firefox (maximised) window is different from Shiretoko and VLC. VLC definitely uses Qt, and Shiretoko looks pretty much the same.
[13:27] <eagles0513875> asac: let me know when i can begin helping you guys wiht lucid work :)
[13:27] <eagles0513875> will work on stuff for lucid happen after uds
[13:27] <asac> Cobalt: maybe you are using the gtk-qt widget engine
[13:28] <asac> but from the looks of it i cant tell
[13:28] <asac> that screen does not ahve any real widget
[13:28] <asac> that would allow to cmprae
[13:28] <Cobalt> asac: No, the opposite. I'm using the patch they made for Qt to use GTK settings. I'm on Hardy, by the way.
[13:28] <Cobalt> asac: And I made sure that gtk-qt engine is not installed, because they said the two weren't compatible.
[13:28] <asac> so yeah
[13:28] <asac> so qt looks like gtk then
[13:29] <asac> imo all is fine there
[13:29] <asac> would need real side-by-side comparison of buttons etc. also you could change qt theme
[13:29] <asac> and see if vlc changes while ffox stays
[13:29] <Cobalt> Well, there is no big difference, but it does look different. It's just that Qt's font rendering is somewhat slightly less pretty than GTK at this point, and I was just wondering what was going on. It's nothing major. But I still want to know kinda thing.
[13:30] <Cobalt> asac: Let me change the Qt themes.
[13:32] <asac> yeah. but for me it looks ok. good to know that qt apps now adapt so nicely to gtk desktops
[13:32] <asac> in the past it usually was only the other way around
[13:36] <Cobalt> asac: It's a bit of a mix and match. Font rendering is still aberrant. Widgets look like GTK's. Would there be any reason why the menu bar and other dialog fonts would not follow GTK's settings?
[13:37] <Cobalt> asac: http://pastehere.com/PasteImages/ypmslu.jpg
[13:37] <asac> font problems exist
[13:37] <asac> but is unrelatred to qt
[13:37] <asac> its a bug in fffox/cairo interaction
[13:37] <asac> bug 379761
[13:38] <asac> Cobalt: ^^
[13:38] <asac> that one
[13:38] <Cobalt> Fair enough. They just looked the same, that why I jumped to that particular conclusion. Thanks, I'll look that up.
[13:38] <asac> no problem
[13:38] <asac> better ask too much than not asking
[13:39] <asac> and me not noticing at all
[13:39] <asac> (we had that in the past too)
[13:40] <Cobalt> Some devs get bugged. :D I tried looking for it on Google, and launchpad, but the search terms I was using weren't giving me anything relevant, and it was difficult narrowing things down.
[13:40] <Cobalt> Thanks again. :)
[13:43] <asac> nß
[14:22] <Cobalt> asac: Thanks again, I applied both workarounds, messing with /etc/fonts had some minimal changes, changing the hinting style in .fonts.conf did the trick. :)
[14:24] <Cobalt> z
[14:24] <Cobalt> Sorry. Thanks, and bye for now. :)
[16:09] <jcastro> hey asac, on amd64 why do we use nspluggin wrapper?
[16:11] <asac> because thats the only viable solution available
[16:12] <asac> 64-bit is not final and as such we have no way to keep up any kind of security support
[16:12] <asac> also we have not stable URL for that because we must not put that in the partner repo
[16:13] <asac> if you read all the bugs you will notice that 64-bit isnt really the cure for everything
[16:13] <asac> most folks think it is, but there are loads of users in the bug that say its crashing more often and then go back to our -installer
[16:13] <asac> in the bugs
[16:14] <asac> but even if 64-bit would be same quality as 32-bit i wouldnt go for it until we can provide proper support
[16:23] <dtchen> the 64-bit bear is...a bear.
[16:23] <dtchen> it requires at least twice the maintenance, but it's the only kludge possible currently ;(
[16:24] <asac> well
[16:24] <asac> for me nspluginwrapper works well
[16:24] <asac> sometimes with compiz you get mouse clicks getting dropped
[16:24] <asac> and maybe it sometimes crashes the wrapper
[16:25] <asac> but usually i can use all sites ;)
[16:46] <jcastro> asac: ok I was just wondering, thanks
[16:46] <asac> welcome
[16:47] <asac> jcastro: so the empathy crash is compoletely gone for you?
[16:47] <jcastro> yeah
[16:48] <jcastro> I can actually use it now
[16:48] <asac> hehe
[16:50] <dtchen> nspluginwrapper is another good stress test
[16:50] <dtchen> it reliably exposes bugs in video and audio stacks
[16:57] <asac> dtchen: because of the many crashes while pushing streams to audio stack?
[17:01] <dtchen> asac: well, it requires tight alignment between the host's stack and ia32-libs
[17:01] <dtchen> but yes, conceivably if that alignment is perfect, it's a good measure of the host's latency processing
[17:02] <dtchen> and that's all sorts of pain -- hardware, linux, alsa-lib, pulse, alsa-plugins, ..,.
[17:25] <micahg>  asac, flash on hardy seems broken
[17:28] <asac> micahg: in what way?
[17:28] <micahg> well, for sure the d/l link for the backports is broke
[17:29] <micahg> I need to check -updates
[17:31] <micahg> no, -updates is still working
[17:32] <micahg> I guess backports isn't officially supported, right?
[17:32] <asac> ok
[17:32] <asac> not sure what is in -backports
[17:32] <asac> i definitly didnt put anything there
[17:33] <micahg> 10.0.1.218+10.0.0.525ubuntu1~hardy1+really9.0.124.0ubuntu2
[17:33] <asac> ah yeah
[17:33] <asac> folks eagerly moved to amd64
[17:33] <asac> to 64-bit
[17:33] <asac> and then we backed that out
[17:33] <asac> or something
[17:34] <asac> i think someone let something in, which shouldnt have been in
[17:34] <micahg> yeah
[17:34] <asac> could be it was not 64-bit ...
[17:34] <micahg> bug 235135
[17:34] <asac> but we did something similar for a 64-bit upload at some point
[17:34] <asac> dont we have flash 10 now?
[17:34] <micahg> yes
[17:34] <asac> ok so its void ;)
[17:35] <asac> i just cant remember the full story ;)
[17:35] <asac> maybe a bit later today now that this bucket was reopened in my brain
[17:35] <micahg> but I guess because of SRU, it can't be released to Hardy which had 9?
[17:35] <asac> hmm
[17:35] <asac> i think there are other issues
[17:36] <asac> maybe it was konqueror exploding or something
[17:36] <micahg> well, it was a beta back then
[17:38] <micahg> well, here's the current problem, the URL in the old backports package is broke, so do I just tell the user to install the version from -updates which is a later version anyways, or open a hardy backports task to fix the link to point to the latest flash 9 or both?
[17:38] <asac> micahg: isnt the -backports version lower than what is in -updates?
[17:38] <asac> why would useres still bump into that package?
[17:39] <micahg> yes and no, the ubuntu version is higher, but it serves a lower flash version
[17:39] <asac> oh shit
[17:39] <asac> what a mess
[17:39]  * asac is slow today
[17:39] <micahg> yep :)
[17:39] <micahg> apparently no one caught it when the security update was done last year
[17:39] <asac> ok so we need to update flash with the same version approach as the backport package
[17:39] <asac> but still with 9
[17:40] <asac>  9.0.246.0ubuntu1    updates, security (multiverse)   12 weeks ago
[17:40] <asac> thats 12 weeks
[17:40] <asac> not a year
[17:40] <micahg> ok, should I prepare something tonight?
[17:40] <micahg> oh really
[17:40] <micahg> I thought adobe dropped flash9
[17:40] <asac> no
[17:40] <asac> they still support it
[17:40] <asac> security wise
[17:40] <asac> afaik
[17:40] <asac> otherwise we wouldnt hav gotten that update i guess ;)
[17:40] <micahg> wow, yeah, so 3 months ago
[17:41] <asac> together with the flash 10 updates
[17:42] <asac> so yes. target the bug that complains about that brokenness to hardy and mark it as hardy-updates
[17:42] <asac> its high
[17:42] <micahg> should hardy-updates or backports?
[17:42] <asac> and then preparte the debdiffs and let me know
[17:42] <asac> micahg: no. hardy-updates ... and -security
[17:42] <asac> otherwise we will have to update -backports forever
[17:42] <micahg> so we're going to bump the -updates version in the same manner as the backports so 10...really9
[17:42] <asac> yes
[17:42] <micahg> got it
[17:43] <asac> that should be higher and then we can just keep it
[17:43] <asac> and make a FAT note in the changelog why thats needed etc.
[17:43] <asac> micahg: target it for hardy-security (not hardy-updates)
[17:43] <micahg> :( no hardy-updates milestone
[17:43] <asac> we will push it through -proposed to -updates and -security
[17:43] <asac> micahg: there probably is a 8.04.2
[17:43] <asac> or something
[17:43] <micahg> .3
[17:44] <asac> yeah ... that then
[17:44] <micahg> ok
[17:45] <asac> thx for spotting this ;)
[17:46] <asac> that was clearly a heroic act ;)
[17:46] <micahg> np, the user had a 404 :)
[17:46] <micahg> ugh, now I have to go to work
[17:46] <asac> take care
[17:46] <asac> i will be out too
[17:46] <asac> try to come back later
[17:46] <asac> like 5 hours
[17:46] <micahg> we don't have a branch for flash do we?
[17:46] <asac> but maybe i crash ;)
[17:46] <asac> no
[17:46] <asac> just debdiff
[17:47] <micahg> ok, got it, you should have it in the morning
[17:47] <asac> micahg: thx
[19:14] <yoasif> hey guys
[19:15] <yoasif> i am using karmic and my firefox consistently segfaults -- the statically built one from mozilla works fine as does swiftfox... any ideas?
[19:33] <micahg> yoasif: what video card?
[19:35] <yoasif> nvidia geforce 9000
[19:36] <micahg> ah, are you using the nvidia drivers?
[19:41] <yoasif> micahg, yes
[19:42] <av`> asac, around?
[19:43] <micahg> yoasif: can you try the nv or noveau drivers?
[19:43] <yoasif> micahg, probably, but they don't work that well for my hardware
[19:44] <micahg> I've seen quite a few reports lately about crashes with the nvidia drivers and firefox
[19:44] <yoasif> micahg, it's kind of a major problem heh
[19:44] <micahg> yes
[19:44] <yoasif> surprised that it's not getting any attention
[19:44] <yoasif> or is it?
[19:44] <micahg> well, it will now
[19:44] <av`> micahg, and what about #455852
[19:44] <micahg> bug 455852
[19:44] <yoasif> micahg, what can i do to help?
[19:45] <av`> micahg, that is a big website for canadian users (like youtube)
[19:45] <av`> and flash doesnt work
[19:45] <av`> since jaunty
[19:45] <micahg> av`: the site worked for me
[19:45] <av`> try playing a video
[19:45] <micahg> av`: I did
[19:45] <micahg> and flash works for me
[19:46] <micahg> av`: which video card?
[19:46] <micahg> or rather driver
[19:46] <av`> micahg, http://www.cbc.ca/video/#/Shows/ID=1309967601
[19:46] <av`> this works for you?
[19:47] <micahg> it's loading
[19:47] <micahg> hold on
[19:47] <yoasif> micahg, what bug number is the one with nvidia + firefox
[19:48] <yoasif> so i can subscribe to it
[19:48] <micahg> no
[19:48] <micahg> it's not working
[19:48] <micahg> but other sites are
[19:48] <av`> yeah
[19:48] <av`> but some canadian users complained badly about this
[19:48] <micahg> youtube and hulu work
[19:48] <av`> and said this could be a stopper for karic
[19:48] <av`> * karmic
[19:48] <av`> don't know why it doesnt work
[19:49] <micahg> av`: I took the ca video bug
[19:49] <micahg> I'll look into it this week
[19:50] <av`> great, let me or asac know the progress on it
[19:50] <av`> so we can ask an SRU for both jaunty and karmic
[19:50] <micahg> yoasif: I don't have one yet
[19:51] <micahg> av`: well, it'll probably be an upstream fix in any case, so SRUs should happen automatically assuming we can land on 1.9.1 branch for FF
[19:51] <av`> yeah, it should be fixed somewhen
[19:52] <av`> in the near future
[19:52] <av`> :)
[19:52] <yoasif> i was wondering if i should do a reinstall, but i guess it won't even help
[19:52] <yoasif> i guess ill start tracking the LL repos when they open up
[19:52] <micahg> yoasif: are you on IRC usually?
[19:52] <yoasif> micahg, yes
[19:52] <micahg> ok, if I remember, I'll ping you when I have a master bug for it
[19:52] <yoasif> ill set this chan as autojoin
[19:53] <micahg> or else, come back in 2 days and ping me :)
[19:53] <yoasif> haha sounds good
[19:53] <micahg> worst case, I'll get to it sat night
[19:53] <yoasif> SRU for karmic though?
[19:53] <yoasif> probably?
[19:53] <yoasif> i think it deserves it
[19:53] <yoasif> major app
[19:53] <micahg> well, probably upstream ff again
[19:53] <yoasif> weird, the statically built one works fine
[19:53] <yoasif> for me
[19:53] <micahg> so, if the patch is clean and/or we can land on 1.9.1 branch, it'll go into karmic
[19:53] <yoasif> from mozilla.org
[19:54] <micahg> well then, maybe it's one of the other libraries
[19:54] <micahg> can't say SRU before I know what the issue is :)
[19:58] <yoasif> heh
[20:05] <micahg> asac: are you ready for 3.0.15 and 3.5.4?
[20:05] <micahg> asac: shipping wed oct 28
[21:25] <fta> micahg, was my pbuilder script useful for you?
[21:28] <micahg> fta: I haven't had time to try it yet
[21:28] <fta> ok
[21:28] <micahg> just had a hard deadline thrown at me
[21:28] <micahg> so I won't be able to do too much before the weekend
[21:29] <fta> work? school?
[21:29] <micahg> work
[21:29] <micahg> project is taking too long
[21:35] <fta> dtchen, any progress with sdl?
[21:36] <dtchen> fta: no, sorry. Work has higher priority.
[21:37] <fta> u too :) ok
[21:53] <BUGabundo> howdy
[21:59] <fta> hey
[21:59] <fta> BUGabundo, do you know if it's possible to commit/collapse/merge vbox snapshots?
[21:59] <fta> it's getting too big too fast
[22:00] <BUGabundo> humm compress the disk virtual images?
[22:00] <BUGabundo> or really the snapshots?
[22:00] <BUGabundo> never tried with snapshots
[22:00] <BUGabundo> but you can delete unused ones
[22:03] <BUGabundo> Untrusted packages could compromise your system's security.
[22:03] <BUGabundo> You should only proceed with the installation if you are certain that
[22:03] <BUGabundo> this is what you want to do.
[22:03] <BUGabundo>   gwibber
[22:03] <BUGabundo> any one knows what's this is ??
[22:04] <BUGabundo> MItM attack while LP is down or something ?
[22:15] <fta> BUGabundo, i started with a 30GB VM, made a snapshot after the initial install, it quickly grew to 10GB, then i made another snapshot once everything was installed and configured. so i now have 30+10+7=47GB, but inside the guest, my 30G are not even half full
[22:17] <BUGabundo> not my domain
[22:17] <BUGabundo> I could ask around
[22:17] <BUGabundo> but then again so can you
[22:17] <BUGabundo> :)
[22:33] <fta> BUGabundo, http://forums.virtualbox.org/viewtopic.php?t=229  it's confusing not only for me apparently
[22:34] <BUGabundo> ehe
[22:34] <BUGabundo> I bet
[22:47] <fta> tried "discard a snapshot"
[22:47] <BUGabundo> and ?
[22:47] <fta> it says "Discarding a hard drive 'foo.vdi' ...(2/2)"
[22:48] <fta> scarry
[22:48] <BUGabundo> ahah
[22:48] <BUGabundo> make a snapshot of the all thing before doing it
[22:48] <BUGabundo> LOLOLOLOL
[22:48] <fta> Time remaining is increasing, 1 sec per sec :P
[22:48] <fta> looks more like a clock to me
[22:49] <BUGabundo> hahahahahah
[22:50] <fta>  23:50:32 up 3 days, 22:42,  5 users,  load average: 5.98, 3.91, 1.95
[22:52] <BUGabundo> hey
[22:52] <BUGabundo> hope that's a quad core :)
[22:52] <fta> nope, dual
[22:52] <BUGabundo> ai ai
[22:52] <fta> ok, done
[22:52] <fta> looks ok, booting now to confirm
[22:54] <fta> good, it worked