[01:11] <yofel> shadeslayer: we already had a buildlog fetching script for neon, but there I only downloaded the files without parsing them
[01:11] <yofel> I'll look at yours tomorrow
[01:12]  * yofel is off to bed
[01:46] <littlegirl> Hey there, does anybody know whether LibreOffice Base will come already installed in a default Kubuntu 12.04 installation? It isn't in the beta and I'm trying to decide whether to remove references to it from the Kubuntu documentation.
[01:53] <tbruff13> can anyone in this channel help me
[09:19] <Riddell> apachelogger: your boot splash looks good, when are you going to upload those changes?
[11:25] <yofel> shadeslayer: for the parsing you want something like this: http://paste.kde.org/442166
[11:26] <Mamarok> Riddell: still have plasma-desktop not working on KDE start: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/955826
[11:27] <Mamarok> and how would libexiv2-11 cause plasma-desktop to crash? Doesn't seem related to me, and I never was asked to upgrade that
[11:28] <yofel> Mamarok: it's apport failing to retrace the crash because you have a ppa version of libexiv2-11 installed
[11:28]  * yofel wonders why that is even handled by apport and not drkonqi
[11:29] <Mamarok> yofel: because it is not a KDE problem but a Kubuntu one
[11:29] <Mamarok> and if a never version of libevix si required why isn't it suggested in the updates to start with?
[11:30] <yofel> Mamarok: it's not required, you have a newer version installed - which breaks the retracer
[11:30] <Mamarok> and why is libexiv causing a plasma problem? That is an image library for digikam and Gwenview
[11:30] <yofel> wait
[11:30] <yofel> libexiv2 has nothing to do with the crash probably
[11:30] <yofel> it's just that the retracer can't install the debugging symbols and fails
[11:31] <Mamarok> oh well...
[11:31] <yofel> still, without at least some backtrace this is impossible to debug - my desktop PC works fine with 4.8.1
[11:32] <yofel> does ~/.xsession-errors have anything related to the crash?
[11:32] <Mamarok> let me check
[11:33] <Mamarok> ouch, what should I grep for?
[11:33] <yofel> plasma? I'm not sure if it even would put anything in there
[11:34] <Mamarok> no, nothing
[11:35] <Mamarok> maybe I can get a new one that is not as huge, let me try
[11:35] <yofel> do you still have the .crash file from apport? maybe you could manually retrace that with apport-retrace on your system
[11:35] <yofel> I would need to look up how that works again though
[11:36] <Mamarok> where would that be?
[11:36] <yofel> /var/crash
[11:38] <Mamarok> yes, still there, and since it still crashes... except that I don't get a crash message for it, it is as if it wouldn't even start
[11:38] <Mamarok> ls -la
[11:38] <Mamarok> oops, wrong focus
[11:38] <yofel> ^^
[11:39] <Mamarok> yofel: what are you refering to?
[11:39] <Mamarok> oh, sorry, moment
[11:42] <Mamarok> gosh, too big for a paste apparently, should I upload it to the bug report?
[11:42] <yofel> Mamarok: yes please
[11:44] <Mamarok> yofel: uploaded
[11:44] <yofel> thanks
[13:55] <BluesKaj> Hi all
[14:59] <aman-dev_> hi all
[15:00] <aman-dev_> can anyone help me out in analyzing the code for kdevelop ide  ?
[15:11] <shadeslayer> uh
[15:11] <shadeslayer> aman-dev_: #kdevelop
[15:13] <shadeslayer> yofel_: Hmm, will test, though I don't quite understand that code
[15:13] <shadeslayer> I know only basic regex
[15:14] <DoctorPepper> shadeslayer: did you  take a look  to the virtuoso patch ? 
[15:15] <shadeslayer> DoctorPepper: I did, but was *very* tired which is why I didn't upload the fix fearing I might foobar something
[15:15] <shadeslayer> I'll upload it tonight after dinner
[15:24] <shadeslayer> yofel_: https://gist.github.com/2065358
[15:52] <shadeslayer> yofel_: there seems to be a problem with your indexes
[16:24] <shadeslayer> ugh, virtuoso has too many changs for a SRU
[16:25] <shadeslayer> and kubuntu backports is already full
[16:40] <yofel_> shadeslayer: oops, I didn't take non-cmake packages into account
[16:41] <shadeslayer> :)
[16:41] <shadeslayer> I could add blacklists to not check those packages
[16:42] <shadeslayer> or just check if the retval was empty
[16:42] <shadeslayer> Riddell: poke
[16:42] <yofel> shadeslayer: check for empty
[16:44] <shadeslayer> :O
[16:45] <shadeslayer> yofel: yay
[16:45] <shadeslayer> oh my
[16:45] <yofel> hm, first pattern doesn't work right
[16:45] <shadeslayer> yeah
[16:45] <shadeslayer> prints out alot more than required
[16:45] <shadeslayer> infact
[16:45] <yofel> I only tested this on 2 logs
[16:45] <shadeslayer> prints out the entire log till 'Configuring Done'
[16:46] <yofel> yeah, which isn't what I wanted
[16:46] <shadeslayer> *nod*
[16:46] <shadeslayer> I was actually thinking of running grep with the context option
[16:46] <shadeslayer> which would give you some info, but not all of it
[16:53] <yofel> ok, works now after I threw out the on-disk caching
[16:53] <yofel> but fails on attica o.O
[16:55] <yofel> ah, and I also didn't handle cmake packages that don't print a summary.... -.-
[17:02] <yofel> shadeslayer: patch: http://paste.kde.org/442334
[17:03] <yofel> that works better, if you think it prints too much modify the patterns
[17:04]  * shadeslayer looks
[17:05] <shadeslayer> yofel: it's *perfect*
[17:05]  * shadeslayer adds to tools
[17:06] <yofel> lol, don't say that until you're run it over all packages we have :D
[17:06] <yofel> *you've
[17:06] <shadeslayer> yep, it's running
[17:09] <yofel> I'm not sure if the case without a summary will find everything as I think cmake and pkgconfig have different patterns IIRC, not sure
[17:10] <shadeslayer> can't be helped :(
[17:10]  * shadeslayer notices that alot of packages are missing optional deps
[17:10] <yofel> some aren't in the archive, but most should be, I haven't checked in a while
[17:11] <shadeslayer> Now  you have a script to do it, I'll email the full log the ML
[17:12] <shadeslayer> Quintasan_ gave me the idea for this a couple of days ago
[17:13] <shadeslayer> yofel: what can we drop from kubuntu-backports? Need to backport virtuoso 6.1.4
[17:13] <yofel> I don't know either, build it somewhere else and copy it over
[17:14] <shadeslayer> and that'll work?
[17:14] <yofel> yes
[17:14] <shadeslayer> *giggle*
[17:16] <shadeslayer> trolololol
[17:17] <shadeslayer> yofel: Now inspecting project-neon-qca2-plugin-ossl
[17:17] <shadeslayer> Traceback (most recent call last):
[17:17] <shadeslayer>   File "kparselog.py", line 31, in <module>
[17:17] <shadeslayer>     build = lp_PPA.getBuildRecords(build_state='Successfully built', source_name=source.source_package_name)[0]
[17:17] <shadeslayer>   File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/resource.py", line 804, in __getitem__
[17:17] <shadeslayer>     raise IndexError("list index out of range")
[17:17] <shadeslayer> IndexError: list index out of range
[17:17] <shadeslayer> aaaarghh
[17:17] <shadeslayer> yofel: http://paste.kde.org/442358/
[17:18]  * yofel wonders why a source package would be 0 successfull build records
[17:18] <yofel> actually, why are you looking for successfull builds?
[17:19] <shadeslayer> I shouldn't?
[17:19] <shadeslayer> https://launchpad.net/~yofel/+archive/neon/+build/2882335 < Built just fine I think
[17:20] <shadeslayer> yofel: I should check for published builds?
[17:20] <yofel> yeah, I don't get that error either
[17:20] <yofel> you already do that
[17:21] <shadeslayer> yeah
[17:21] <shadeslayer> well
[17:21] <yofel> but then you check the whole ppa again for builds for a specific package
[17:21] <yofel> in my script I simply got all builds for the source with: source.getBuilds()
[17:22] <yofel> which should give you 1 or 2 depending on arch all/any
[17:24] <shadeslayer> oh
[17:25] <shadeslayer> yofel: getBuilds just returns a list of successfully built build objects?
[17:25] <yofel> getBuilds returns a list of ALL builds for the published source
[17:26] <yofel> including the failed ones
[17:26] <shadeslayer> hm
[17:26] <yofel> why don't you want those?
[17:26] <yofel> failed to configure is a valid case here
[17:26] <shadeslayer> yeah, I'll fix that .. didn't consider all cases last night
[17:39] <shadeslayer> yofel: does your knotify4 go bonkers when you login into neon
[17:39] <shadeslayer> hogs up all memory driving everything into swap
[17:40] <yofel> I haven't used neon in a while
[17:43] <Riddell> shadeslayer: you poked?
[17:44] <shadeslayer> yus
[17:44] <shadeslayer> Riddell: can you approve bug 958683 for precise and oneiric?
[17:44] <shadeslayer> I'm just about done, will attach a patch and build log
[17:44] <Riddell> yofel: why make bug 955826 private?
[17:45] <yofel> Riddell: I wasn't sure what the coredump would contain, probably doesn't need to be
[17:47] <Riddell> if it crashes on login I wouldn't think Mamarok would have time to start browsing porn or anything she doesn't want made public
[17:48] <yofel> lol, yeah ^^
[17:48] <Riddell> hmm apport made it invalid
[17:48] <yofel> shadeslayer: for an SRU that's the wrong version, please use -1ubuntu1.1 for oneiric
[17:49] <shadeslayer> uh, ok, I've used 1ubuntu2~oneiric1 earlier ..
[17:49] <yofel> ~oneiric1 is something you use for backports
[17:49] <Mamarok> and I usually don't surf pron, and markey has no access to my laptop :)
[17:50] <yofel> Mamarok: did you have a chance to install updates? (from  tty)
[17:50] <yofel> nvm the tty
[17:50] <Mamarok> yofel: I have updated several times already, still the same bahavior
[17:51] <yofel> which version of libexiv2-11 is installed right now?
[17:54] <shadeslayer> yofel: http://paste.kde.org/442364
[17:54] <shadeslayer> already fixed the error at the end
[17:55] <yofel> Now inspecting project-neon-calligra: Not a cmake package - lol, too messy I guess
[17:55] <shadeslayer> :P
[17:56] <shadeslayer> likewise for gwenview
[17:56] <Mamarok> yofel: for some strange reason still the oneiric one, let me check my package sources
[17:57] <Mamarok> but I only have precise sources
[17:59] <Mamarok> and no never package suggested for libexiv2-11 than 0.22
[18:00] <Mamarok> debug files though is 0.22-2
[18:00] <Mamarok> no idea why there is such a mess
[18:01] <yofel> I think "0.22-oneiric" is higher than "0.22-2" 
[18:01] <Mamarok> oh, that doesn't make much sense
[18:01] <Riddell> it is dpkg --compare-versions 0.22-oneiric gt 0.22-2 && echo $?
[18:03] <Mamarok> no output besides $
[18:04] <Mamarok> and if I try to install the -dbg file it wants to downgrade libexiv2....
[18:04] <shadeslayer> hmm .. SRU docs say I can just upload my fix
[18:04] <yofel> shadeslayer: if you have upload rights yes, otherwise find a sponsor
[18:05] <shadeslayer> yofel: cool, but I'd rather wait for some feedback first
[18:06] <yofel> Mamarok: can you downgrade it, move the .crash file out of /var/crash, crash it again and then file a new bug?
[18:06] <yofel> maybe then the retracer won't fail on us
[18:06] <Mamarok> ok
[18:07] <Riddell> download the precise package and dpkg --install it
[18:07] <Mamarok> but why is the oneiric package higher than the precise one?
[18:08] <yofel> because whoever made the oneiric package used the wrong version
[18:08] <Mamarok> Riddell: easier: install the libexic2-dev, that downgrade it as well
[18:09] <Mamarok> OK, brb
[18:09] <Riddell> https://launchpad.net/ubuntu/+source/libkexiv2 -> Other versions of 'libkexiv2' in untrusted archives. -> kubuntu-updates owned by Philip Johnsson
[18:09] <Riddell> has the troublesome package
[18:09] <Riddell> anyone know this guy? https://launchpad.net/~philip5/+archive/kubuntu-updates
[18:11] <yofel> I've seen him online a few times in various places, I'll talk to him when I see him
[18:11] <Mamarok> he provides the digikam packages
[18:11] <yofel> as a matter of fact, he's in #kubuntu
[18:11] <shadeslayer> oh my oh my
[18:12] <Mamarok> hm, how do I get a crash report now? plasma-desktop didn't start
[18:12] <yofel> apport *should* have made a new crash file in /var/crash/
[18:13] <Mamarok> nope
[18:13] <yofel> -.-
[18:14] <yofel> take the old crash file and file the bug again with that maybe
[18:14] <yofel> apport is weird -.-
[18:14] <shadeslayer> heh
[18:14] <shadeslayer> its python ... what else did you expect
[18:15] <yofel> oh, you *can* make perfectly sane python applications - in theory
[18:15] <shadeslayer> unfourtunately real life is quite different :(
[18:16] <Mamarok> so basically I should file the same crash again? can't we just reopen it and let it do the same stuff again?
[18:17] <Mamarok> or maybe I should change some settings in apport so it actually does retrace it?
[18:17] <yofel> apport deleted the core dump, so no
[18:17] <yofel> well
[18:17] <Mamarok> it didn't delete anything it just dind't update it
[18:17] <yofel> you *can* do the retracing yourself using apport-retrace
[18:17] <Mamarok> didn't
[18:17] <yofel> you didn't but the retracer did
[18:18] <Mamarok> which I should do before restarting plasma-desktop actually I guess?
[18:18] <yofel> that shouldn't matter
[18:19] <yofel> the .crash file has to core dump, so you can retrace it with plasma running
[18:19] <Mamarok> apport-retrace isn't even installed
[18:19] <shadeslayer> Mamarok: you'll need to install it :)
[18:19] <yofel> right, you normally should never have a use for it
[18:19] <shadeslayer> it doesn't come on standard installs
[18:22] <Mamarok> so now I just tell him the report number?
[18:22] <yofel> wait
[18:25] <Mamarok> yofel: just tell me here, I have supper ready, will do when I am back :)
[18:25] <yofel> Mamarok: do something like: sudo apport-retrace -o new.crash <crashfile>
[18:25] <yofel> k
[18:26]  * yofel does another sandboxed attempt in the meanwhile
[19:05] <shadeslayer> KDevelop as well
[19:10] <Riddell> these upstrams keep us busy
[19:10] <Mamarok> rekonq
[19:10] <Riddell> shadeslayer: didn't you say you were going to automate kdevelop packaging?
[19:10] <Mamarok> gah, wrong focus, sorry
[19:10] <Riddell> Mamarok: has a new version?
[19:10] <debfx> & akonadi & soprano
[19:10] <Riddell> ah :)
[19:11] <shadeslayer> Riddell: nope ... 
[19:11] <shadeslayer> I could do it though ...
[19:13] <shadeslayer> would be a basic shell script
[19:13] <Riddell> shadeslayer: nah, one day I'll get round to making generic scripts in python
[19:13] <Riddell> no point doing it hacky and project specific
[19:14] <shadeslayer> Hmmm
[19:14] <shadeslayer> We were supposed to have a automation meeting
[19:14] <shadeslayer> but no one set that up
[19:14] <yofel> I know
[19:15] <yofel> because I wanted to do that and a) didn't have time b) waited for shadeslayer's dev meeting
[19:16] <Mamarok> yofel: I get that error: ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath
[19:17] <yofel> O.O
[19:17] <yofel> someone else? ^ I'm out of ideas
[19:20] <yofel> shadeslayer: how about doing it a day or 2 after beta freeze? Otherwise I would schedule that sometime in april
[19:21] <yofel> need to write a mail about packaging tracking anyway
[19:21] <Mamarok> yofel: no problem, I will see if apport will eventually redetect the crash one day and report it again
[19:22] <yofel> thanks
[19:48] <Philip5> Riddell: you asked for me :)
[19:48] <Riddell> oh hi Philip5 
[19:48] <Philip5> hi there
[19:48] <Philip5> heard that my ppa got some attention
[19:48] <Riddell> you broke Mamarok's computer and now she's going to come after you with her Swiss yodelling
[19:48] <Philip5> lol
[19:48] <Riddell> it's the version numbers that are wrong
[19:49] <Philip5> yes i know that are not in the debian standard
[19:49] <Mamarok> Philip5: you are quite lucky: I can't yodel :)
[19:49] <Riddell>  0.22-oneiric is newer than 0.22-2
[19:49] <Philip5> but what happened that broke something?
[19:49] <Philip5> yes
[19:50] <Philip5> is it exiv2 that is the problem?
[19:50] <Riddell> if you have 0.22-oneiric installed and upgrade to precise that doesn't work
[19:50] <Riddell> yes
[19:50] <Philip5> aha
[19:50] <Riddell> the right way to do it is the magic ~ operator
[19:50] <Riddell> 0.22-2~oneiric1
[19:51] <Riddell> that ~ makes it "less than" 0.22-2
[19:51] <Philip5> i know but i'm just lazy and want my own packages to override official ones
[19:51] <Philip5> not the best solution though
[19:52] <Philip5> but in my world exiv2 from my ppa or the official in pricise shouldn't break anything
[19:52] <Philip5> even though it's not neat
[19:52] <Mamarok> Riddell: I don't think it breaks plasma, I think it prevents apport retracing the plasma crash
[19:53] <shadeslayer> yofel: Can we do it in April, I'm planning to finish off my internship by then
[19:54] <Philip5> Mamarok: that's true. if you have my package installed but not libkexiv2-dbg and have upgraded to precise then my package of libkexiv2-dbg isn't avalible and you have a package installation problem
[19:55] <Philip5> Riddell: i think i heard requests on help with maintaining digkam for kubuntu too?
[19:55] <yofel> shadeslayer: ack
[19:56] <Mamarok> Philip5: it would be nice if we had that in the kubuntu-backports, yes
[19:56] <Philip5> Riddell: it's just that digikam is a pain in the butt to maintain in an official debian policy way. digikam is un-orthodox in how it release and distribute its software
[19:56] <yofel> which one? 2.6 would be something for beta
[19:56] <littlegirl> Hey there, do any of you know how to link to an element by id in the current xml document?
[19:56] <yofel> ah, 2.5 wasn't backported
[19:57] <Mamarok> littlegirl: which document?
[19:57] <Philip5> it's a mess trying to maintain digikam when it come bundled with other libs that are conflicting with upstream kde grapgic libs
[19:57] <Riddell> Philip5: yeah digikam is not always packager-friendly
[19:57] <Riddell> Philip5: but we'd love the help :)
[19:57] <GirlyGirl> littlegirl: see my pm
[19:57] <littlegirl> Mamarok: It's the video.xml document in the kubuntu-docs branch.
[19:58] <Philip5> Riddell: i know it would be nice. i'm just a bit lazy when it comes to document changelogs and such
[19:58] <yofel> Philip5: we could help with that ;)
[19:58] <Philip5> yofel: hehe, true
[19:59] <Philip5> with digkam 2.6 it will be a bit easier in a way as they have bumped the graphic libs so they will not conflict with upstream kde grapgic libs... as far as kde in it self doesn't get an update again
[20:00] <yofel> Philip5: well, we use what can be used from kde and only the libs from digikam that kde itself doesn't ship
[20:00] <yofel> works so far
[20:01] <Philip5> yofel: do you guys port source code from digikam into kde graphic libs or use official releases of kde graphic libs?
[20:01] <yofel> Philip5: official releases, that's why we use some things from digikam as libkface and others never got a release by themselves
[20:02] <Philip5> ok, that's understandable
[20:03] <Philip5> yofel: with digkam 2.6 we get libkexiv2-11 and other never versions of libs that are not in kde yet. how do you handle that? introduce libkexiv2-11 with digikam or keep digikam using libkexiv2-10 from official kde?
[20:04] <yofel> dunno, that's something for Q as Precise will ship with 2.5
[20:04] <Philip5> not a problem yet then
[20:05] <Philip5> Mamarok: just curious, what have you used from my ppa? digikam or some other stuff?
[20:06] <Mamarok> digikam, I wanted 2.5 for Oneiric
[20:06] <Philip5> ok, you and 2000 other users then :)
[20:07] <yofel> yeah, digikam from your ppa is rather popular
[20:08] <Philip5> i have noticed
[20:08] <Philip5> but never asked for it but it just happened
[20:08] <swecarp> Philip5,  is a good suport fore the swedish ppl i have used him alott 
[20:09] <Philip5> swecarp: you make it sound so dirty... used me a lot... ;)
[20:09] <swecarp> sorry not dirty talk Philip5  u knowe me 
[20:09] <Philip5> i know
[20:09] <yofel> lol
[20:10] <Riddell> it would be good to have digikam amongst the regulars in the ~kubuntu-ppa/backports PPA but that needs someone to maintain it :)
[20:10] <yofel> Riddell: I'm looking at it
[20:11] <Philip5> Riddell: i was asked to help doing digikam maintainace dor debian too so maybe i should do both if i go for it... all in so to speak
[20:11] <Philip5> dor=for
[20:13] <yofel> Philip5: that would make things easier as you would know what needs to be done when merging
[20:14] <Philip5> yes, but more responsability and work for me :)
[20:16] <yofel> true
[20:19] <swecarp> i have a question here will the final be att 700 mb iso ore will it be smaller
[20:19] <ScottK> IIRC we're aiming for ~706mb or less (which will fit on a CD).
[20:20] <yofel> swecarp: CD for precise will be 700 
[20:20] <ScottK> No guarantees we make it.
[20:20] <yofel> hey, be optimistic!
[20:20]  * yofel fails at it himself though
[20:20] <swecarp> ty im hoping it will fit a cd 
[20:28] <shadeslayer> oh god, don't remind me of digkam
[20:28] <shadeslayer> I spent a entire week fixing the ARM build
[20:29] <shadeslayer> yofel: I thought we were increasing the CD Image size?
[20:29] <shadeslayer> to fit more stuff onto it
[20:29] <yofel> shadeslayer: not for precise
[20:29] <shadeslayer> 0.o
[20:29] <shadeslayer> Wasn't the decision made at UDS?
[20:29] <shadeslayer> that's what I remember, CD sizes will be increased
[20:30]  * yofel remembers a discussion about it, but nothing more
[20:31] <shadeslayer> hm, I thought they reached a consensus
[20:32] <shadeslayer> a reason why the images were over the older limit of 700 MB's
[20:32] <yofel> well, we will increase it for Q
[20:32] <shadeslayer> and why I haven't been able to test them -.-
[20:32] <yofel> you have no dvd's o.O?
[20:33] <shadeslayer> none that are rewritable I should really get one
[20:33] <shadeslayer> I have a rewritable CD though
[20:43] <shadeslayer> Nighters everyone :)
[20:55] <Riddell> kubuntu has same DVDs as always
[20:55] <Riddell> ubuntu desktop has slimmed down DVDs without alternate on them
[20:55] <Riddell> next cycle I expect ubuntu to move to a 1GB limit or so and make USB or DVD the requirement
[21:00] <swecarp> Riddell,  that will make me that run a old computer neading to burn a dvd everytime i nead to do some thing
[21:02] <yofel> hm, digikam 2.5 seems to require new opencv
[21:03]  * yofel will look again tomorrow
[21:21] <Riddell> swecarp: so your new computer has CD only?  you can use a USB key
[21:23] <swecarp> my puter has onley cd and cant bbot from usb its an old p4
[21:24] <Riddell> but you have an old computer that does have a dvd burner?
[21:24] <swecarp> no dvd burner thats why i ask
[21:25] <Riddell> swecarp: and how well does current Kubuntu run on such an old computer?
[21:26] <swecarp> the curent 11,10 runs gr8 the best i ever had  u have done a good job with it
[21:27] <swecarp> i have upp graded it to 1gb ram 
[21:29] <swecarp> Riddell,  kubuntu did make this old mashine a new life after manny years with windowes and running slowe
[21:32] <Riddell> mm
[21:33] <Riddell> I wonder if we have a wya to 
[21:33] <Riddell> I wonder if we have a way to tell how many people are in that position
[21:33] <Riddell> swecarp: would "use the netboot CD image" be a suitable solution?
[21:34] <swecarp> Riddell,  i havent tryed that but instaling direkt from the net is a great thing if thats possibel
[21:36] <swecarp> i think moste ppl have Dvd burners today  so my problem isent so big 
[21:36] <sreich> yeah, computers these days come with combos. i don't even think you can buy *just* a cd reader
[21:37] <swecarp> sreich,  my trubbel is that im running an old p4
[21:49] <ybit> fun fact: muon crashes when apt-get update is running in the background
[21:49]  * ybit might need to report a bug
[21:53] <ybit> oh
[21:53] <ybit> nope
[21:53] <ybit> it just crashes everytime it's launched
[23:57] <littlegirl> Hey there, Darkwing, sorry I'm so slow, but I'm verifying the accuracy of the content. (:
[23:59]  * jalcine_ is away: Gone away for now