[00:00] <yotux> I am using rsync to download now,  will it speed up the process next time I need to update the ISO?
[00:01] <fader_> yotux: Absolutely.  The first time you have to download the whole thing, but in the future rsync will only download the changes
[02:34] <fader_> marjo: you know if you don't test things you can keep the bug numbers low :)
[02:34] <marjo> fader_: yes, classic QA problem
[02:35] <fader_> marjo: We can have the Boston vs. New York thing here... see who can file the best bug :)
[02:35] <marjo> fader_: i'm on it!
[02:36] <fader_> marjo: Any bugs yotux files count toward my total.
[02:36] <fader_> (C'mon, yotux! :D )
[02:37] <fader_> It's quiet tonight... usually ISO testing is more raucous.  Maybe for beta. :/
[02:37] <marjo> fader_: just finding dup bugs from alpha2
[02:38] <fader_> marjo: See, like I said, there's your mistake... of course if you *look* for bugs you're going to find them!
[02:38] <marjo> fader_: ack
[02:38] <fader_> marjo: Every time you say that I think of this: http://isitluck.files.wordpress.com/2009/07/bill-the-cat-ack.jpg
[02:39] <marjo> fader: +1
[02:40] <marjo> fader: boot speed is pretty fast even on my acer aspire one
[02:40] <fader_> \o/
[02:40] <marjo> how's it booting for you?
[02:41] <fader_> I got an SSD in the mail yesterday; I can't wait to hook that up and see how my boot looks
[02:41] <marjo> oh nice!
[02:41] <fader_> Meh, pretty fast, but I haven't been clocking it
[02:41] <fader_> I'm also doing this in VirtualBox
[02:41] <fader_> So it's not a great test
[02:41] <fader_> *test of boot speed :P
[02:45] <marjo> fader_ shouldn't davmor2 be up in the middle of the night testing wubi or something?
[02:45] <fader_> marjo: +1
[02:45] <fader_> I miss when he tested all the ISOs and the rest of us just hung out and kibbitzed
[02:45] <marjo> fader_ yeah, i feel like he's slacking off these days
[02:46] <marjo> maybe hggdh, bladernr & ameetp will pick up the slack
[02:46] <marjo> in US time zones
[02:46] <fader_> We should find out where he lives, go to his house in the middle of the night, and make puppydog eyes at him until he feels bad and starts testing
[02:47] <fader_> hggdh, bladernr-away, ameetp: marjo's volunteering you for things again
[02:47] <marjo> fader_ I can just see his face!
[02:47] <fader_> Yeah, it'd probably be making a gigantic "NO"
[02:47] <fader_> :)
[02:47] <marjo> AFAIK, it's past dinner time in the US
[02:48] <marjo> fader: anybody using testdrive?
[02:48] <marjo> i don't have the hardware for it
[02:48] <fader_> marjo: I think hggdh was using it earlier but he was running into problems booting afterward
[02:48] <marjo> but it's supposed to also work under virtualbox
[02:48] <marjo> ah ok
[02:49] <fader_> Hmm
[02:49] <fader_> He was using it under kvm, but that's all I know
[02:50] <hggdh> I was using testdrive, but something is not going kosher here
[02:50] <marjo> hggdh: you might want to report your non-kosher issues to dustin
[02:50] <hggdh> bllody virtualbox states I do not have an AMD64, and testdrive/kvm is not quite working out either
[02:51] <marjo> dustin aka kirkland
[02:51] <hggdh> I will. One of the issues I already traced to an open bug (-vga std fails)
[02:52] <fader_> hggdh: What processor do you have?  That's the first I've heard of virtualbox hating on an amd64
[02:52] <marjo> hggdh: well, do YOU have AMD64, gotta have that VT technology or the equivalent in AMD chips
[02:52] <hggdh> :-) I have a AMD64 Turion x2
[02:52] <hggdh> trueAMD, and all that
[02:52] <fader_> Virtualbox will let you run VMs without virtualization support in the processor, so I'm extra confused
[02:53] <hggdh> vBox is refusing to run stating I have a i686
[02:53] <fader_> hggdh: Did you install from a 32-bit disc?
[02:53] <fader_> What does uname -a say?
[02:54] <hggdh> Linux xango 2.6.32-14-generic #20-Ubuntu SMP Sat Feb 20 05:18:19 UTC 2010 x86_64 GNU/Linux
[02:54] <fader_> Weird.
[02:55] <hggdh> tell me :-(
[02:55] <marjo> fader_: vBox even runs on my acer w/ little ole atom chip
[02:55] <hggdh> I have gone back 4 kernel versions (it *was* working, some time ago) to -10, and nothing (except I got my vterms back)
[02:56] <fader_> I blame davmor2
[02:56] <hggdh> I have tried vbox-ose and vbox proprietary, same thing
[02:56] <fader_> (mostly because he's not here to defend himself)
[02:56] <hggdh> :-)
[02:57] <hggdh> so far, this week I have booted & installed the bloody server CD some 30 times.
[02:58] <fader_> If it makes you feel any better, the MythTV theme I've been waiting for looks like it's in SVN for the same version of Myth that's going to be on the next Mythbuntu: http://www.fecitfacta.com/Arclight/Welcome.html
[02:58] <fader_> (It probably doesn't, but it makes *me* feel better)
[02:58] <hggdh> LOL
[02:58] <fader_> hggdh: Welcome to my world :)
[02:58] <fader_> I close my eyes and see the CD language selection screen :)
[02:59] <hggdh> I was ogling a 12-gauge nearby, and wondering on a radical redesign/reengineering of my laptop
[02:59] <fader_> It would be better ventilated after that, for sure
[03:00] <hggdh> guess so. I would also have no more issues with the video card
[03:00] <fader_> Hehe
[03:05] <hggdh> But I swear, next laptop will (1) have a smaller screen (17'' is good, but BIG); use Intel for video, wireless, etc)
[03:06] <fader_> hggdh: That's why you need a huge laptop for daily use and a netbook for travel :)
[03:07] <fader_> Any excuse to buy new toys.
[03:07] <hggdh> well, there's that, yes. Hum.
[03:07]  * hggdh starts thinking on how to explain to wife a new toy
[03:08] <charlie-tca> heh, it gets a little better with time. I do at least 4 installs every day
[03:08] <fader_> "It is easier to get forgiveness than permission."
[03:08] <hggdh> nice one!
[03:11] <fader_> Yeesh, I don't know what KDE is doing but it's thrashing like crazy on first boot
[03:12] <fader_> Ah, file indexing.  That explains it.
[03:21] <fader_> Okay, Real Life is calling me... I'm being required to go be social briefly before bedtime.  G'night all!
[03:21] <marjo> fader_: be social! g'night!
[03:21] <fader_> marjo: Don't test too much.  You'll find more bugs!
[03:22] <marjo> fader_: go New York!
[03:22] <fader_> Bah, you're just jealous about not being the Hub of the Universe :)
[03:22] <fader_> *bamf*
[07:03] <ara> good morning all!
[07:14] <persia> ara: Good morning.  I sent the following whilst you were away:
[07:14] <persia> ara: Sorry for the delay: I don't know much about the mirrors,; but usually ask in #ubuntu-mirrors: it may be that one of them is having an issue that needs that sysadmin to help.
[07:14] <ara> persia, thanks, I'll ask there
[07:51] <sbeattie> Riddell: are kubuntu 8.04 -> 10.04 upgrades expected to be supported?
[08:03] <mvo> sbeattie: hello! I have a test profile for them, not sure how official they are
[08:12] <sbeattie> mvo: okay, I just tried it, and it failed, see bug 527605
[08:12] <ubot4> Launchpad bug 527605 in update-manager (Ubuntu) "kubuntu 8.04 -> 10.04 upgrade fails, due to likely dependency cycle (affects: 1)" [Undecided,New] https://launchpad.net/bugs/527605
[08:13]  * mvo looks
[08:13] <mvo> uhhh
[08:13] <mvo> nasty
[08:22] <yotux> I did a test install and it failed
[08:22] <yotux> how can I document this or get more details to help the dev team?
[08:28] <sbeattie> yotux: file a bug in launchpad and mark the test install case as failed in http://iso.qa.ubuntu.com/
[08:31] <yotux> thank you sorry my first test case
[08:31] <yotux> I am not sure what to file the bug as though?
[08:32] <yotux> Not sure what is causing the system to hang any idea how to investigate this?
[09:27] <ara> launchpad timing out... great
[09:48] <davmor2> ara sorry no means of testing today :(
[09:49] <ara> davmor2, yes, in millbank, isn't it?
[09:49] <davmor2> Yeap
[09:49] <ara> davmor2, ok, no problem. enjoy the view! ;-)
[09:49] <davmor2> :)
[09:50] <davmor2> ara, maybe when the fog clears
[09:50] <ara> davmor2, :D
[10:02] <ara> mvo, if you want me to file a bug regarding the crash in the software-center, let me know
[10:09] <Riddell> sbeattie: no 8.04 to 10.04 isn't supported for kubuntu, although it should work anyway
[10:12] <mvo> ara: thats fine, I have a look now
[10:12] <ara> mvo, meaning, do I file the bug or not? :D
[10:13] <mvo> ara: sorry, no need for a report
[10:13] <ara> mvo, OK :)
[11:39] <slangasek> hum, has there only been one install test of UNE?  Is anyone else seeing bug #527528?
[11:39] <ubot4> Launchpad bug 527528 in netbook-meta (Ubuntu) "[Alpha 3 Testing] After first boot default GNOME desktop is installed (affects: 1)" [Undecided,New] https://launchpad.net/bugs/527528
[11:39] <slangasek> plars, GrueMaster: ^^ I guess that's not affecting arm netbook images, or you would've shouted? :)
[11:40] <persia> I've been playing with current UNE (x86) with a hacked ubiquity and didn't see that,but it might be the hacked ubiquity.
[11:40] <slangasek> hmm
[12:14] <plars> slangasek: are we sure that bug submitter is using the current alpha?
[12:14] <plars> InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100107)
[12:14] <plars> slangasek: ^^
[12:15] <slangasek> plars: that likely just indicates he filed the report from his normal lucid install rather than from his test install
[12:16] <slangasek> plars: since the bug was correctly linked from an ISO test report :)
[12:17] <persia> There was a case reported today in #ubuntu-bugs of a user who was confused that someone linked to their (previously filed) bug from the ISO test report.
[12:18] <persia> (not the same bug, but probably not an uncommon phenomenon)
[12:18] <plars> slangasek: it was just a red flag for me, especially combined with the bug only affecting 1 person, and the comment that it was a bug that they saw in alpha2 that they are now seeing again in alpha3
[12:19] <slangasek> plars: OTOH, he's the *only* person who's reported doing a test install of UNE so far :/
[12:19] <plars> right
[12:19] <plars> slangasek: if I weren't *just* waking up and having to head out to an early dr. appointment, I'd pull the image and try to reproduce now myself, unfortunately I'm not in a position to do so at the moment
[12:20] <slangasek> 'sok, let's make Europe do it
[12:21] <czajkowski> heh
[12:27] <persia> czajkowski: You're in a good timezone :)  Mind doing a test install of UNE?
[12:27] <czajkowski> I'm at work :(
[12:28] <czajkowski> I'm on windows machines..
[12:28] <slangasek> the best machines to test on
[12:28] <slangasek> >:)
[12:28] <czajkowski> persia: if you've any tips on upgradding my hardy machine mini 9 bought from dell to lucid do let me know
[12:29] <czajkowski> slangasek: tell me about it!
[12:30] <persia> czajkowski: Grab usb-creator from hardy-backports, use it on a lucid iso to create a boot stick.  Boot off that to make sure that the kernel has the support you need.  Either reinstall or do-release-upgrade as you like.
[12:31] <czajkowski> that solves my lunchtime plans, shall upgrade the mini then
[12:33] <persia> czajkowski: Do test though: it may be that something doesn't work (because those didn't precisely ship with Ubuntu)
[12:33] <czajkowski> yes I suspect it won't be just straight forward
[12:34] <persia> It may be though.
[13:32] <czajkowski> persia: doing do-release-upgrade shows no new release found
[13:33] <persia> czajkowski: I suspect someone hacked that then.  Hrm.
[13:34] <persia> czajkowski: Try manually installing update-manager 1:0.87.31 from hardy-updates and trying again, with `do-release-upgrade -d`
[13:35] <czajkowski> update-manger was installed
[13:35] <czajkowski> added -d still same message
[13:35] <czajkowski> no new release found
[13:35] <persia> *which* update-manager?
[13:36] <persia> And did you report on the ISO tracker about your experience with the Alpha 3 ISO with usb-creator?
[13:36] <czajkowski> didnt have a usb on me said I;d just jump in and update
[13:37] <ara> czajkowski, what about "update-manager -d"
[13:38] <persia> czajkowski: WHat'S the output of `apt-cache show update-manager | grep ^Version`?
[13:38] <czajkowski> that worked
[13:38] <czajkowski> ara: ^^
[13:38] <ara> \o/
[13:39] <persia> bug in hardy do-release-upgrade?
[13:39] <czajkowski> ara: well it launched update manger, it still didn't offer lucid :(
[13:39] <czajkowski> now for persia instructions
[13:39] <persia> Or something special-patched in the Dell Mini 9 preload?
[13:39] <ara> czajkowski, :(
[13:40] <ara> mvo_, ^
[13:40] <ara> mvo_, any suggestions?
[13:40] <ara> morning cr3
[13:40] <cr3> ara: hi there
[13:41] <mvo_> czajkowski: do you run as sudo? or normal user? are you behind a proxy?
[13:42] <czajkowski> mvo_: run as sudo, am behind a firewall...
[13:42]  * persia really thinks it's a hacked update-manager to not support dist-upgrades.
[13:42] <mvo_> czajkowski: what does "DEBUG_UPDATE_MANAGER=1 update-manager -d" print? please try running as normal user
[13:42] <czajkowski> mvo_: will do
[13:42] <mvo_> thanks
[13:43]  * ara steps out for lunch
[13:44] <czajkowski> mvo_: thats funky, it launched update manager and in the terminal  it outputs  Metarelease._init_() useDevel=True useProposed=Fakse
[13:44] <czajkowski> MetaRelease.download()
[13:44] <czajkowski> no self.metarelease_information
[13:45] <persia> czajkowski: Which version of update-manager do you have, please?
[13:45] <czajkowski> persia: I tried your command and nothing happend
[13:45] <mvo_> ok, so it appears that it can not connect to changelogs.ubuntu.com/meta-release, if you do a wget on that, does that work?
[13:45] <mvo_> i.e.  wget http://changelogs.ubuntu.com/meta-release
[13:46] <czajkowski> mvo_: much more helpful
[13:46] <czajkowski> let me switch machines so I can get you the output
[13:46] <czajkowski> DEBUG output created by Wget 1.10.2 on linux-gnu.
[13:46] <czajkowski> --13:46:12--  http://debug_update_manager=1/ => `index.html'
[13:46] <czajkowski> Resolving debug_update_manager=1... failed: Name or service not known.
[13:46] <czajkowski> --13:46:12--  http://update-manager/ => `index.html'
[13:46] <czajkowski> Resolving update-manager... failed: Name or service not known.
[13:46] <czajkowski> FINISHED --13:46:12--
[13:47] <czajkowski> Downloaded: 0 bytes in 0 files
[13:47] <persia> czajkowski: can you tell the version from /usr/share/doc/update-manager/changelog.gz ?
[13:47]  * persia suspects there is a changelog entry like "debian/rules - removed creation of dist-upgrade.tar.gz"
[13:47] <mvo_> czajkowski: what persia said, the exact version would be good too
[13:48] <czajkowski> ok
[13:48] <czajkowski> bear with me a tic, still at work
[13:48] <mvo_> sure
[13:49] <czajkowski> Version: 1:0.87.30netbook0belmont6
[13:49] <czajkowski> Version: 1:0.87.30netbook0belmont3
[13:49] <czajkowski> Version: 1:0.87.30netbook0belmont2
[13:49] <czajkowski> Version: 1:0.87.30netbook0belmont1
[13:49] <czajkowski> Version: 1:0.87.30
[13:49] <czajkowski> Version: 1:0.87.24
[13:51] <mvo_> ohhh, that smeels strongly like it does not support upgrades
[13:51] <czajkowski> well that would mean me and a lotta other mini 9 flks will be rather peeved :(
[13:51] <persia> mvo http://netbook-remix.archive.canonical.com/updates/pool/public/u/update-manager/update-manager_0.87.30netbook0belmont6.dsc
[13:52] <persia> czajkowski: The Mini 9 ships with an Ubuntu derivative that has a bunch of stuff different and definitely doesn't intentionally support upgrades.
[13:53] <czajkowski> hmm i thought it was explained it could only support LTS so I've been waiting since i got it to upgrade to next LTS
[13:54] <persia> czajkowski: Anyway, force-install http://ie.archive.ubuntu.com/ubuntu/pool/main/u/update-manager/update-manager_0.87.31_all.deb and then it should work properly.
[13:55] <czajkowski> persia: add it to the software sources?
[13:56] <persia> czajkowski: If you activate that link it ought pull a package you want installed.  Running update-manager after that ought do the right thing (that's the Ubuntu hardy update-manager)
[13:56] <persia> When you run it in dist-upgrade mode, it should handle dealing with the software sources (I think).
[13:57] <persia> mvo may know better.
[13:57] <czajkowski> ok
[13:58] <persia> Oh, that devices claims to be "lpia" doesn't it?
[13:58] <czajkowski> yes
[13:58] <persia> If it's "lpia" then you need to reinstall.
[13:59] <czajkowski> balls
[14:01] <slangasek> well
[14:01] <slangasek> you could lie and tell it that it's i386
[14:01] <slangasek> --force-architecture or something
[14:01] <slangasek> downloading the hardy dpkg and apt debs for i386 and dpkg -i --force-architecture should be enough to trick it, I think?
[14:01] <persia> slangasek: For a dist-upgrade from hardy on a derivative to lucid?  That sounds likely to break in odd an unexpected ways.
[14:02] <slangasek> :)
[14:02] <czajkowski> so much for simple upgrade at lunch time
[14:03] <fader_> Morning all
[14:04] <fader_> I'll kick off a UNE install for slangasek if that's still desirous
[14:05] <slangasek> fader_: still is, yes
[14:05] <czajkowski> Thanks for the help though.
[14:10] <fader_> slangasek: Does it matter if it's in a VM?
[14:10] <slangasek> fader_: not that I'm aware of
[14:10] <fader_> Cool; I'll let you know what happens :)
[14:19] <thekorn> I just did a UNE entire disk install
[14:20] <fader_> thekorn: Did you see bug 527528 when you did?
[14:20] <ubot4> Launchpad bug 527528 in netbook-meta (Ubuntu) "[Alpha 3 Testing] After first boot default GNOME desktop is installed (affects: 1)" [Undecided,Incomplete] https://launchpad.net/bugs/527528
[14:21] <fader_> I'm 93% through an install as well so I'll also try to reproduce, but I'm interested if you saw it too
[14:21] <thekorn> fader_, no, not when installing on an empty disk
[14:22] <thekorn> didrocks mentioned sth. about an existing HOME partition
[14:22] <fader_> thekorn: Was this the most recent build?  The one that we're testing for Alpha 3?
[14:22]  * fader_ assumes so but wants to cover all the bases. :)
[14:23] <thekorn> fader_, yes, I used *24.3
[14:23] <fader_> That's even weirder, as the test case that has that bug reported against it was an 'entire disk' install
[14:23] <fader_> thekorn: Are you going to / will you report that result to the ISO tracker?
[14:24] <thekorn> fader_, already reported the result
[14:24] <fader_> thekorn: Thanks!
[14:25] <davmor2> canon fader_  oh that should be foder right
[14:26] <fader_> o_O
[14:27] <fader_> davmor2: Can you repeat that in American for me?  ;)
[14:31] <fader_> Wow, update-grub is slow :(
[14:35] <fader_> slangasek: thekorn and I have both now performed a UNE install and are unable to reproduce bug 527528
[14:36] <ubot4> Launchpad bug 527528 in netbook-meta (Ubuntu) "[Alpha 3 Testing] After first boot default GNOME desktop is installed (affects: 1)" [Undecided,Incomplete] https://launchpad.net/bugs/527528
[14:37] <slangasek> fader_: ok, cool - perhaps you could follow up to the bug with a note on this?
[14:37] <fader_> slangasek: Already got it open in my browser :)\
[15:02] <slangasek> kubuntu desktop, netbook respins posted
[15:11] <hggdh> I found my issue with vBox... forgot only *one* of kvm or vBox can be running
[15:11] <hggdh> so rmmod kvm_amd does the trick
[15:11] <marjo> hggdh: aha!
[15:11] <hggdh> darn!
[15:11] <marjo> that makes more sense than last night
[15:11] <hggdh> it did not make sense, and kvm just is not working here (another issue)
[15:12] <hggdh> so I am back to vBox, and kicking :-)
[15:12] <charlie-tca> I just filed bug 527832 against desktop images.
[15:12] <ubot4> Launchpad bug 527832 in ubiquity (Ubuntu) "[Lucid] Ubiquity shuts off my monitor during the startup to live environment (affects: 1)" [Undecided,New] https://launchpad.net/bugs/527832
[15:12] <charlie-tca> It is very consistent blanking my monitor every time; both ubuntu and xubuntu do it
[15:12] <hggdh> does it recover?
[15:12] <charlie-tca> probably won't get fixed for alpha3, but should be in the notes
[15:13] <charlie-tca> It takes 7-8 minutes to get to the desktop
[15:13] <hggdh> bad
[15:13] <charlie-tca> oops; 7-8 minutes to the gdm screen; 13-18 minutes to the desktop
[15:16] <fader_> charlie-tca: I think davmor2 was seeing something similar
[15:16] <charlie-tca> I think it is a conflict with plymouth and nvidia
[15:17] <charlie-tca> Just seems like users are not going to wait to see anything when it takes so long
[15:18] <fader_> It's not a bug, it's a feature to enforce a stretching break!
[15:18] <fader_> Speaking of which...
[15:18]  * fader_ installs updates and reboots.
[15:18] <charlie-tca> OH! :-)
[19:33] <fader_> Hmm, I can't seem to manage to boot lucid at all after installing it to real hardware :(
[19:35] <sbeattie> fader_: how is it failing? I've had it succeed here...
[19:35] <fader_> sbeattie: It hangs on boot, whether or not I let plymouth run
[19:35] <sbeattie> fader_: what flavor?
[19:35] <fader_> If I do the default boot it hangs on the ubuntu splash screen and ignores ctrl+alt_Fx
[19:35] <fader_> If I do nosplash I see boot messages and then it hangs anyway
[19:36] <fader_> amd64 desktop
[19:36] <fader_> I wonder if it's possibly nvidia related
[19:36] <sbeattie> quite likely; my nvidia system turns off it's display during the plymouth portion of boot.
[19:37] <sbeattie> (but it's also old and a 32 bit machine)
[19:37] <fader_> Yeah, I heard about that, but I haven't seen it.  I'm letting this system sit where it seems to be hung for a while and see what happens
[19:38]  * sbeattie is currently trying to do an ubuntustudio install, but that's on a machine with ati graphics.
[19:40] <fader_> As much as I hated trying to play Civilization IV under Wine on it, my old Intel graphics system always worked.
[19:40]  * fader_ sighs wistfully.
[19:42] <sbeattie> indeed, I've rarely needed 3D support, so I've had several intel based machines because they tended to just work (and not break things like suspend)
[19:43] <fader_> Is there a way to disable plymouth from grub?  I expected nosplash to do it, but adding --verbose it looks like it's still getting run
[19:45] <sbeattie> I'm not sure.
[19:48] <fader_> Ah, hmm
[19:48] <fader_> Seems that alt+sysrq+k kills it
[19:48] <fader_> And all I had to do was fsck /dev/sda1
[19:48] <fader_> That seems... bad.
[19:49] <fader_> Let's see if I can reproduce that
[19:49] <fader_> Nope
[21:20] <yotux> I installed a test case and it failed how do I figure out which bug it would be
[21:20] <yotux> get a black screen
[22:04] <yotux> is anyone else here have a problem with the nouveau drivers
[22:06] <fader_> yotux: Are you talking about the screen being black at boot?
[22:08] <yotux> yes sorry
[22:08] <yotux> was interested to see if it was an isolated indecent
[22:09] <yotux> fader_ besides that issue everything else appears to be going smooth
[22:09] <fader_> yotux: I haven't seen that myself, but I know several other people have and I believe there's a bug about it
[22:10] <yotux> If there was I am sorry I filed bug 528056
[22:10] <ubot4> Launchpad bug 528056 in linux-meta (Ubuntu) "nouveau driver not configured correctly (affects: 1)" [Undecided,New] https://launchpad.net/bugs/528056
[22:11] <charlie-tca> bug 527832 for the desktop cd?
[22:11] <ubot4> Launchpad bug 527832 in ubiquity (Ubuntu) "[Lucid] Ubiquity shuts off my monitor during the startup to live environment (affects: 1)" [Undecided,New] https://launchpad.net/bugs/527832
[22:11] <fader_> yotux: There's also bug 523788 which may be related
[22:11] <ubot4> Launchpad bug 523788 in plymouth (Ubuntu Lucid) (and 1 other project) "Only see X mouse cursor on VT during boot (affects: 4) (dups: 1)" [High,Confirmed] https://launchpad.net/bugs/523788
[22:11] <fader_> Heh, or that one charlie-tca just mentioned :D
[22:11] <charlie-tca> heh, I guess it is not isolated, huh?
[22:12] <yotux> lol guess not,  I used alt cd
[22:13] <yotux> I was going to try the LTSP install test case can I use a laptop booting over the network for a thin client?
[22:14] <fader_> yotux: I believe you should be able to use anything that supports PXE
[22:14] <fader_> So if the laptop does, you're all set
[22:15] <yotux> Thankz
[22:15] <yotux> have fun guys time to install bye