[00:19] <DanaG> Ooh, finch uses the unicode ☎ for status.
[01:17] <calc> tytso is here at UDS telling us about ext4 :-)
[01:25] <calc> now talking about the bugs still in ext4
[01:29] <RAOF> calc: Oooh.  Any doosies?
[01:30] <calc> RAOF: some data corruption issues in some cases with sparse files like with bittorrent, bdb, etc
[01:30] <calc> but they are working on them
[01:31] <RAOF> Sounds fun!  Every one loves data corruption in their fs :)
[01:31] <calc> yea, heh
[01:33] <crimsun> RAOF: what?  no reiserfs on your woody box?
[01:34] <calc> he also does not recommend mounting ext3 with ext4 driver
[01:34] <calc> since its not tested well yet
[01:36]  * RAOF doesn't /have/ a woody box.
[01:37] <RAOF> Marvelous!
[01:38] <calc> but it appears that ubuntu will allow installing with ext4 in jaunty but not the default
[01:38] <calc> so anyone who wants to play with fire can get burned ;-)
[01:41] <RAOF> Nifty.  It's already possible to format and mount ext4, but a little installer love will let more people get burned!
[01:42] <calc> yea :)
[01:44] <calc> there is actually better support for SSD in ext4 also
[01:45] <calc> it tells the SSD that the block is no longer used so it can reuse it for wear leveling
[04:42] <karlp> wait not supported? as in i can't ask for help in this channel?
[04:42] <karlp> or as in not supported for #ubuntu ? (which is obvious)
[04:51] <karlp> when i start kdm, my usb {keyboard and mouse} are completely unusable
[04:52] <karlp> but on the console, it's perfectly fine
[04:52] <karlp> i'll updating+upgrading again
[04:55] <RAOF> karlp: Sounds like an X input-hotplug issue
[04:56] <karlp> RAOF: how would i fix it? it worked fine with intrepid and i, out of the blue, decided to update to jaunty, against better judgement
[04:57] <RAOF> It'd be useful to see your /var/log/Xorg.0.log
[04:57] <RAOF> And your xorg.conf while you're at it.
[04:58] <karlp> grep '(EE)' /var/log/Xorg.0.log outputs just: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[04:58] <karlp> ah, but the WW is where it's out
[04:58] <karlp> for some reason it disables it
[04:59] <karlp> AllowEmptyInput is on
[05:02] <karlp> serverflags section... going to change it to false
[05:02] <karlp> rather add it to say it's false
[05:02] <karlp> i didn't add that in but i suspect the update must have
[05:03] <RAOF> The actual files would be useful :)
[05:04] <RAOF> pastebinit can be your friend.
[05:05] <karlp> yeah, well i sort of half-asked the question. i'm going to try to figure it out first before i bother you further
[05:05] <karlp> i just expected it's a package problem and didn't even think it could be a configuration file issue
[05:05] <karlp> i guess technically the configuration file is part of the package....
[05:05] <RAOF> Ish.  It's a bit tricky.
[05:07] <karlp> man, you ubuntu devs are insane. working non-stop... i just updated less than 5 minutes ago and it's already got more than a few megabytes worth of updates grabbed
[05:09] <karlp> fixed it :D
[05:09] <karlp> later
[07:03] <histo> think flash 64bit will maek it in to juanty?
[07:04] <rww> histo: it's in jaunty. It's just broken right now due to a bug involving a missing copy of libuuid1
[07:04] <histo> ahh Haven't yet installed jaunty maybe on a virtual machine for testing .
[07:04] <andersk> No, that's 32-bit flash with nspluginwrapper that's broken by the libuuid1 bug.
[07:04] <andersk> Adobe released a native 64-bit plugin that hasn't made it into Jaunty yet.
[07:05] <rww> andersk: oh, really? huh, i need to keep up better with my non-free stuff
[07:06] <andersk> http://blogs.adobe.com/penguin.swf/2008/11/now_supporting_16_exabytes.html
[07:08] <rww> heh, interestinfg
[07:10] <stdin> it's pre-release, so it won't be in jaunty until it's officially released
[08:30] <BUGabundo_work> I know this is stupid to ask
[08:30] <BUGabundo_work> but did any one here installed todays KDEPIM updates?
[09:11] <BUGabundo_work> humm even with a Nvidia Compiz efects seem slow and dragging!
[09:16] <lemonade_> which effects?
[09:20] <BUGabundo_work> several... windows transition, cube, etc
[11:11] <BUGabundo_work> and you lemonade?
[16:06] <Le-Chuck_ITA1> Hi there. I am testing jaunty and I noticed that the upgraded xorg and kernel are much slower than the ones provided on the cds. Is this considered normal or is it a bug? Moreover, I can use the previous kernel but how can I revert to the xorg that is provided on the cds'
[16:06] <Le-Chuck_ITA1> ?
[16:13] <BUGabundo_work> hi Le-Chuck_ITA1
[16:13] <BUGabundo_work> I mention exactly that today here in the #
[16:13] <Le-Chuck_ITA1> very good so it's not only my problem
[16:13] <BUGabundo_work> my guess: it aint finned tuned yet
[16:13] <Le-Chuck_ITA1> is it fundamentally newer than the xorg on the cds?
[16:14] <Le-Chuck_ITA1> cd
[16:15] <Le-Chuck_ITA1> A question to everybody: is it actually feasible to install some snapshotting system (LVM snapshots???) and then just try to upgrade, and revert if something goes wrong? What are the practical problems?
[16:15] <BUGabundo_work> I don't understand your question
[16:15] <BUGabundo_work> Le-Chuck_ITA1: most of the people here are at UDS-Jaunty
[16:15] <Le-Chuck_ITA1> BUGabundo_work: it seems to me that the version of xorg on the jaunty alpha1 image is faster than the one
[16:16] <BUGabundo_work> so don't count on getting much atteion
[16:16] <Le-Chuck_ITA1> ok so the simplest question is: "is the version on the installation cd faster for you?"
[16:16] <BUGabundo_work> do know
[16:16] <BUGabundo_work> I've been using jaunty eversince the tool chains were open
[16:16] <Le-Chuck_ITA1> yes and was it faster then?
[16:17] <IdleOne> Le-Chuck_ITA1, best thing would be to run new "snapshots" in VM and see if it works for you but I am not sure that is what you want
[16:18] <Le-Chuck_ITA1> IdleOne: hmm I would not test hardware drivers then
[16:24] <Le-Chuck_ITA1> well, I will reinstall hardy for now :)
[16:27] <BUGabundo_work> why not ibex?
[16:28] <Le-Chuck_ITA1> BUGabundo_work: actually I wanted to say intrepid, I already have hardy which is the latest version that works well
[16:28] <Le-Chuck_ITA1> intrepid was my "beta testing"
[16:28] <BUGabundo_work> ibex is the latest stable version
[16:28] <BUGabundo_work> jaunty is development
[16:28] <Le-Chuck_ITA1> Yes I know, but it does not work so well for me in some respect :)
[16:28] <BUGabundo_work> file bugs for it!
[16:28] <BUGabundo_work> let the devs know about them
[16:29] <Le-Chuck_ITA1> BUGabundo_work: I have a hundred of open bugs :P
[16:29] <Le-Chuck_ITA1> but if they aren't closed I can't work well, you know. In any case I am using ibex on two other machines where it's just working fine
[16:30]  * Le-Chuck_ITA1 thinks usb-creator is a great tool
[16:33] <Le-Chuck_ITA1> BUGabundo_work: do you remember if the system was faster when you started using jaunty?
[16:33] <BUGabundo_work> humm
[16:33] <BUGabundo_work> back then the nvidia driver didn't work
[16:34] <BUGabundo_work> so I can compare my experince with Compiz
[16:34] <BUGabundo_work> which is the single thing that I find slower!
[16:40] <Le-Chuck_ITA1> BUGabundo_work: I thought so but also using metacity X is slo
[16:40] <Le-Chuck_ITA1> w
[16:40] <Le-Chuck_ITA1> the rest of the system is very fast especially if compared to hardy
[16:40] <Le-Chuck_ITA1> but it's time to reboot now :) I just upgraded some X libraries
[16:40] <Le-Chuck_ITA1> bye and see you
[17:02] <FFForever> how bad do things get broken =D
[17:12] <FFForever> any news on but 272247 and jaunty?
[17:26] <ikonia> FFForever check the bug report in stead of asking someone to check it for you
[17:26] <ikonia> FFForever: you know the bug report so look it up
[17:27] <FFForever> ikonia, i did look it up there is nothing that says it still affects jaunty or not =( ive been reading it over and over =(
[17:27] <ikonia> possibly because it doesn't or it would be logged, or maybe it's not been tested on jaunty yet as it's still in heavey flux
[17:28] <ikonia> FFForever: it's not going to say "doesn't effect jaunty" it will only say "does effect jaunty" if it does
[17:29] <FFForever> how stable is jaunty i know there are package problems but they normally get cleared up in a day or 2 right?
[17:29] <ikonia> no
[17:29] <ikonia> they don't get cleared up in a day or two
[17:29] <ikonia> it's in a state of flux
[17:29] <ikonia> could work today, break tommorow, broke for a week, fixed for 2 days, broke for a day etc - it's unknown
[17:30] <FFForever> how long normally till ubuntu+1 reaches some sort of beta/stableness?
[17:30] <BUGabundo_work> eheh FFForever only one week past release!
[17:30] <BUGabundo_work> LOL
[17:30] <ikonia> when the "beta" or Release candidate are out
[17:31] <FFForever> BUGabundo_work, lol....
[17:39] <genii> I wonder why people run pre-releases of intermediate versions anyhow
[17:40] <genii> (as main OS, not on seaparete partition or sandboxed somehow)
[17:40] <BUGabundo_work> genii: Full Time testing??
[17:42] <ikonia> genii: because they are foolish
[17:43] <BUGabundo_work> oh come on ikonia... didn't expect that from you!
[17:44] <ikonia> what ?
[17:44] <ikonia> BUGabundo_work: people running development releases and expecting it to work or not break as their main OS are being foolish
[17:44] <ikonia> more so when the releases are not even at a beta stage
[17:44] <BUGabundo_work> hey...
[17:45] <BUGabundo_work> that's another thing!
[17:45] <BUGabundo_work> I know that running alpha it can and WILL break...
[17:45] <ikonia> that's what I said, it's a foolish thing to do
[17:45] <BUGabundo_work> no
[17:45] <ikonia> BUGabundo_work: I didn't say you, I said people who run it as a main release
[17:45] <BUGabundo_work> what you said is that running it is foolish
[17:45] <ikonia> you've been quite open that you'll happy trash and burn your builds
[17:45] <BUGabundo_work> eheh
[17:45] <ikonia> BUGabundo_work: in response to genii's comment
[17:46] <ikonia> which I have just clarified
[17:46] <BUGabundo_work> I run it, I know they break
[17:46] <BUGabundo_work> I help fixing
[17:46] <ikonia> I didn't say you -
[17:46] <ikonia> I've just clarified
[17:46] <BUGabundo_work> and make every release a little bit better for those using a stable!
[17:46] <genii> I did qualify "as their main OS"  etc
[17:47] <BUGabundo_work> I know from experience that any MAJOR changes/fix must be done before beta
[17:47] <genii> I like to have a separate partition for dev releases, myself
[17:47] <BUGabundo_work> complaining that "oh my Ubuntu has this bug" two weeks after Release will do no good
[17:47] <BUGabundo_work> genii: it is MY MAIN and ONLY OS on my laptop!
[17:47] <genii> BUGabundo_work: You live dangerously :)
[17:47] <BUGabundo_work> if it breaks, I just boot via network to a daily or stable release!
[17:48] <BUGabundo_work> or if without network, liveUSB
[17:48] <BUGabundo_work> been doing so ever since I started using ubuntu full time
[17:48] <BUGabundo_work> with 6.10 alpha6 or something
[17:48] <BUGabundo_work> tried 6.06 and it missed something so I just dist upgraded!
[17:49] <BUGabundo_work> won't stay on stable more then a few weeks
[17:49] <BUGabundo_work> usually by alpha 1 or 2, I'm using the devel version
[17:49] <BUGabundo_work> it feels strange not having HUGE amounts of updates!
[17:49] <BUGabundo_work> lol
[17:50] <genii> BUGabundo_work: Your average user has no clue of network booting or so on (or even "backups", depressingly), and so it always amazes me when someone is using it as their main desktop and then so surprised when suddenly something makes it inoperable
[17:53] <BUGabundo_work> lol
[17:53] <BUGabundo_work> I know
[17:53] <BUGabundo_work> I guess I been doing this for so long that I don't even bother
[17:53] <BUGabundo_work> and I know my ways around
[17:54]  * BUGabundo_work reminds ikonia that some day we will have to try that kdepim compile
[17:57] <ikonia> BUGabundo_work: happy to do so
[17:57] <ikonia> BUGabundo_work: the cmake method is new to me so I'm interested
[18:04] <BUGabundo_work> but not today
[18:04] <BUGabundo_work> I'm super huber late for group work!
[18:04] <BUGabundo_work> maybe tomorrow
[18:04] <BUGabundo_work> if I have some free time here at work
[18:04] <BUGabundo_work> and you are available
[18:04] <BUGabundo_work> I'll ping you
[18:43] <raymears> hi everyone. here's a kubuntu related question, if i may: is there any possibility of using the plasmoids from jaunty (beta) - which i've installed alongside intrepid -  in intrepid?
[19:04] <ikonia> raymears: nope
[19:04] <ikonia> raymears: don't swap distro packages
[19:43] <raymears> ikonia: damn and blast. ok. 'keep it clean' seems to be the motto here. another question: where can i find the source code of the plasmoids included in jaunty beta? i tried kde-look, websvn.kde.org and google... and found nothing.
[19:43] <ikonia> raymears: pull it out otf the jaunty repo
[19:44] <raymears> ikonia: you mean download the deb and extract things out of it?
[19:44] <ikonia> raymearchange your repo to the jaunty one, do apt-get source $package
[19:44] <ikonia> change the repo back
[19:44] <ikonia> diry but gives you the exact jaunty source package
[19:46] <raymears> heh. didn't think of that. any chance of breaking plasma?
[19:46] <raymears> now that i think of it.. no
[19:47] <raymears> stupid question. thanks
[22:09] <DanaG> grargh, Catalyst 8.12 doesn't work with Jaunty, either.
[23:26] <naught1017> anyone know what version of kdebase the jaunty alpha 1 ISO has on it?
[23:30] <naught1017> and there are no kubuntu dailies now? none since 3 weeks ago?
[23:33] <naught1017> maybe alternate will have to do :)
[23:34] <naught1017> http://cdimage.ubuntu.com/kubuntu/ports/ < what does "ports" mean?
[23:38] <naught1017> nm
[23:48] <DanaG> !find gnomeapplet.so
[23:48] <DanaG> "A required python module is missing! No module named gnomeapplet"
[23:49] <DanaG> yeah... file is missing.
[23:50] <DanaG> Time for me to file a bug, I guess.
[23:50] <DanaG>  dpkg -S gnomeapplet.so           --           dpkg: *gnomeapplet.so* not found.
[23:52] <DanaG> In fact.. a LOT of files are missing.