[00:15] <ari-tczew> unimatrix: packages.ubuntu.com is orphaned
[00:18] <unimatrix> ari-tczew how so? is there a replacement?
[00:18] <ari-tczew> unimatrix: in http interface? no
[03:42] <jturek> hi guys, anybody running latest maverick, having their network wifi LED flashing on and off like mad?
[03:43] <jturek> i don't know how to explain this in a bug report lol
[03:43] <jturek> wifi is up and running, just the LED keeps flashing like its telling me morse code
[04:01] <ansgar> How often do the moderators for<EMAIL_ADDRESS>approve messages?
[06:28] <micahg> DktrKranz: are you familiar with yasm?  I see you touched the package about 2 yrs ago
[07:10] <pitti> Good mornin
[07:11] <pitti> (no 'g's just yet at this hour, sorry)
[07:24] <ttx> geser: yes
[07:25] <ttx> geser: sfcb depends on cim-schema, which still needs some work on licensing
[07:25] <ttx> geser: so at this point it needs to live in multiverse
[07:25] <ttx> and so do all the things that depend on it
[07:29] <pitti> hey ttx, feeling better?
[07:30] <ttx> pitti: slightly, meds starting to take effect. Thanks :)
[07:33] <DktrKranz> micahg: no
[07:49] <micahg> pitti: do you know about yasm?
[08:06] <dholbach> good morning!
[08:26] <pitti> micahg: I know it exists, not much else
[08:26] <micahg> pitti: k, I'm wondering if I can update the package in Ubuntu since Debian isn't being responsive and we're right before FF
[08:26] <pitti> sure
[08:26] <micahg> pitti: k, thanks
[08:28] <andersk> I think glib2.0 2.25.12-1ubuntu1 is badly broken (at least on i386): bug 614240.
[08:28] <andersk> If so, this is going to cause major headaches for maverick users tomorrow.  :-(
[08:29] <micahg> robert_ancell: ^^^
[08:32] <pitti> CDs failed to build the same way
[08:33] <robert_ancell> micahg, yes, :(
[08:34] <robert_ancell> occurs on i386, not amd64.  Anyone care to test a fix?
[08:37] <pitti> http://cdimage.ubuntu.com/daily-live/20100806/maverick-desktop-amd64.manifest
[08:38] <pitti> MUAHAH!
[08:38] <pitti> no hal any more!!
[08:38] <pitti> \o/
[08:38] <robert_ancell> pitti, your quest is complete!
[08:40] <Chipzz> pitti: gz :)
[08:42] <robert_ancell> pitti, do you have i386 hw?
[08:43] <pitti> robert_ancell: I have two amd64 installs
[08:43] <pitti> robert_ancell: but I can test something in a VM
[08:44] <pitti> i. e. boot the alpha-3 i386 VM and update or so
[08:45] <robert_ancell> pitti, actually, the ppa is fast today, it's building there now.  thanks
[08:48] <robert_ancell> pitti, build failed, it's pulling in glib to build glib...  can you try building lp:~robert-ancell/+junk/glib-i386-fix on i386 and see if there is the error reported in bug 61420 when it builds?
[08:48] <robert_ancell> bug 614240
[08:58] <robert_ancell> seb128, hey
[08:58] <seb128> hey robert_ancell
[08:58] <robert_ancell> seb128, been breaking stuff, sorry :(
[08:58] <seb128> robert_ancell, you did upload the new glib?
[08:59] <robert_ancell> seb128, yup, wasn't getting any problem here - do you have any i386 hw?
[08:59] <seb128> "i386" in sense of non i686?
[09:00] <robert_ancell> seb128, not sure, definitely broken on i386
[09:00] <seb128> but yes my box is not amd64
[09:00] <seb128> robert_ancell, I wrote you an email to tell you to not upload before having it tested by somebody who had the issue :-(
[09:01] <robert_ancell> seb128, sorry, I misread that
[09:03] <seb128> robert_ancell, we missed the :03 run now, I will do a testbuild with -O0 there
[09:03] <seb128> did anybody tried that?
[09:03] <robert_ancell> seb128, ok, thanks.  I can't reproduce the problem but I have a possible fix in  lp:~robert-ancell/+junk/glib-i386-fix
[09:04] <seb128> robert_ancell, want me to test that first?
[09:04] <robert_ancell> seb128, yes please.  Look for a warning after compiling gsignal.c
[09:04] <seb128> robert_ancell, did you try to upload to a ppa? ;-)
[09:04] <robert_ancell> seb128, yes, but it pulled in glib to build glib - how do we get around that?
[09:04] <seb128> did it?
[09:05] <robert_ancell> http://launchpadlibrarian.net/53153005/buildlog_ubuntu-maverick-i386.glib2.0_2.25.12-1ubuntu2_CHROOTWAIT.txt.gz
[09:05] <pitti> bonjour seb128
[09:05] <seb128> that's going to be fun
[09:05] <seb128> pitti, hey
[09:05] <seb128> pitti, help!
[09:07] <pitti> erm, why does glib b-dep on glib?
[09:07] <pitti> ah
[09:07] <pitti> libdconf2.0?
[09:07] <robert_ancell> pitti, it may be because of the dconf depends
[09:07] <seb128> let's change it back to a recommends
[09:07] <pitti> robert_ancell: so, try the following:
[09:08] <pitti> - upload a glib2.0 without dconf and the fix
[09:08] <pitti> - let it build and publish
[09:08] <pitti> - reupload glib2.0 with dconf
[09:08] <seb128> just change it back to a recommend
[09:08] <seb128> that's a circular depends anyway
[09:08] <seb128> I will add the recommends to gnome-session or something
[09:09] <pitti> recommends sounds good enough as well
[09:09] <robert_ancell> ok, uploading now
[09:09] <robert_ancell> (to ppa)
[09:11]  * seb128 builds locally
[09:11] <seb128> I hacked the rules to not run make check, that takes hours
[09:11] <seb128> robert_ancell, sorry for not being clear in my email :-(
[09:11] <robert_ancell> seb128, I should have checked the debian reports closer
[09:12] <seb128> did you find it now?
[09:12] <robert_ancell> seb128, yes, afterwards when I knew the compiler error to search for
[09:13] <seb128> robert_ancell, oh, did they reassign it away from glib?
[09:13] <seb128> in any case update building there
[09:13] <robert_ancell> seb128, no, but I didn't realise that bug was the problem we were facing.
[09:14] <seb128> I didn't realize it was not happening on amd64 ;-)
[09:14] <robert_ancell> seb128, the weird thing is the compiler says "this is going to fail for sure" and then lets you keep compiling!
[09:15] <seb128> I've noticed reading your email, I didn't notice the build warning yesterday
[09:16] <seb128> robert_ancell, seems the warning is fixed
[09:17] <seb128> it's building the udeb variant now but I've no "//usr/include/bits/string3.h:86: warning: call to __builtin___memset_chk will always overflow destination buffer" in the log after the shared build
[09:17] <robert_ancell> seb128, good sign...
[09:19] <seb128> oh come on
[09:20] <seb128> building rfgdbg now
[09:20] <seb128> why do need to build glib, gtk etc 3 times
[09:21] <seb128> robert_ancell, btw you should add the dh_installdirs call to the rules while you are at it
[09:21] <seb128>  	dh_install -i
[09:21] <seb128> +	dh_installdirs -i
[09:22] <seb128> and same for the -s
[09:22] <seb128> robert_ancell, and be ready to upload if that build works ;-)
[09:22] <robert_ancell> seb128, prepping now...
[09:24] <seb128> robert_ancell, ok, it's running the dh_
[09:25] <pitti> hm, what's all this complaining from uscan in maverick?
[09:25] <pitti> dpkg: version ''2.31.6'' has bad syntax: invalid character in version number
[09:25] <seb128> robert_ancell, works! go go go upload it ;-)
[09:25] <seb128> ups
[09:25] <seb128> robert_ancell, wait
[09:25] <pitti> this seems to break bzr bd etc.
[09:26] <seb128> robert_ancell, no, don't
[09:26] <seb128> robert_ancell, any gtk software segfault on g_bsearch_array_lookup_fuzzy()
[09:26] <robert_ancell> seb128, ?
[09:26] <seb128> the install worked
[09:26] <seb128> but gtk-demo or gedit or whatever still segfault
[09:27] <robert_ancell> damn, plan B, can you upload with -O0?
[09:27] <seb128> pitti, should we block the binaries? it makes any gtk software segfault on i386
[09:27] <seb128> robert_ancell, can try
[09:29] <pitti> seb128: ah, so the fix doesn't work?
[09:29] <pitti> or any workaround?
[09:29] <pitti> seb128: we could just upload the previous glib?
[09:29] <pitti> it'd be better than blocking binaries IMHO
[09:30] <seb128> ok
[09:35] <seb128> ok
[09:35] <seb128> pitti, robert_ancell: I've uploaded an untested version
[09:35] <seb128> building it locally now
[09:35] <pitti> a reversion to the previous glib?
[09:36] <seb128> pitti, no, a build with -O0 which the debian guys says workaround the compiler issue
[09:36] <seb128> pitti, I'm not sure the previous version wouldn't have the same issue
[09:36] <seb128> pitti, we are running into a gcc bug not a glib one
[09:36] <seb128> that code didn't change
[09:37] <pitti> eww
[09:42] <seb128> grrrr
[09:43] <seb128> #0  0x011eb53e in ?? () from /usr/lib/gio/modules/libgvfsdbus.so
[09:43] <seb128> #1  0x00761996 in _g_local_file_info_get
[09:43] <seb128> gtk-demo runs now but not gedit
[09:44] <robert_ancell> seb128, I have to go sorry, can you handle this?
[09:45] <seb128> robert_ancell, yes, enjoy your evening, don't worry we will sort it
[09:45] <seb128> pitti, should we block the binaries or not?
[09:45] <robert_ancell> seb128, thanks, I owe you a pile of beers
[09:45] <seb128> pitti, it makes all the gtk programs crash on i386
[09:45] <seb128> which basically means no session for anybody upgrading I guess
[09:46] <seb128> and we will not catch a fix in the next publisher run now
[09:47] <seb128> pitti, or wait
[09:48] <seb128> hum no
[09:56] <seb128> pitti, hello?
[09:58] <pitti> seb128: so, your workaround didn't work either? does it work with -O0?
[09:59] <seb128> pitti, my workaround was -O0, that fixes a crash but anything using gvfs crashes still
[09:59] <seb128> I'm trying to rebuild the previous version now
[10:04] <seb128> pitti, bah
[10:04] <seb128> pitti, does the buildds install recommends?
[10:04] <pitti> they don't, no
[10:04] <seb128> http://launchpadlibrarian.net/53155396/buildlog_ubuntu-maverick-i386.glib2.0_2.25.12-1ubuntu2_CHROOTWAIT.txt.gz
[10:05] <pitti> The following NEW packages will be installed:
[10:05] <pitti>   libdconf0 libmpfr4
[10:05] <seb128> right, I'm wondering what brings libdconf0 in
[10:05] <seb128> I changed it to a recommends
[10:06] <pitti> hm, is that even the build-depends install already?
[10:06] <pitti> it could just be the initial chroot upgrade
[10:06] <pitti> Updating debian chroot for build 7d742a5eeb0eac0743fc0c3c1f21ea01fa1a5850
[10:06] <pitti> glib is in the buildd chroot
[10:06] <seb128> :-(
[10:06] <pitti> darn
[10:08] <pitti> so, I'm afraid this needs lamont love
[10:08]  * pitti stops buildds
[10:08] <pitti> well, the i386 ones, anyway
[10:08] <pitti> other arches are not affected?
[10:09] <pitti> seb128, lamont: i386 buildds on manual, to avoid further FTBFSes until the chroot is sorted out
[10:09] <pitti> seb128, lamont, elmo: I think what needs to happen is a manual chroot upgrade with ignoring the segfault in libglib2.0-0's postinst
[10:10] <pitti> and then build/publish a glib without the libdconf dependency
[10:10] <pitti> then the chroot should at least be able to upgrade itself again
[10:10] <seb128> pitti, well, I'm not so concerned about the buildds that about the fact that every i386 downloading that upgrade will get a non starting system
[10:10] <seb128> or rather graphical system
[10:12] <sebner> seb128: good to know that I don't do a restart :D
[10:12] <seb128> sebner, well you shouldn't be able to start any gtk application either
[10:12] <pitti> seb128: so, you want the i386 .debs blocked? you need to ask #is about that, I'm afraid, I can't do that
[10:13] <seb128> pitti, well either we need to solve that quickly or we need to block the debs
[10:13] <seb128> pitti, what do you think?
[10:13] <sebner> seb128: uh great, good that I opened my browser and xchat already before the upgrade xD
[10:14] <pitti> seb128: blocking debs would probably be prudent, since we need to fix the chroots either way, and it's a couple of hours until lamont wakes up
[10:14] <seb128> ok
[10:15] <sebner> seb128: but I guess a simple glib downgrade fixes it?
[10:15]  * sebner waves at pitti btw :)
[10:15] <seb128> yes
[10:15] <pitti> hello seb128
[10:15] <pitti> sebner, even
[10:16] <debarshi> Where can I find some documentation on writing a Ubiquity plugin? I need to add some extra pages to Ubiquity for some Ubuntu-based boxes that we are making at the university.
[10:17] <debarshi> I am currently reading through the sources of the existing plugins ...
[10:18]  * Adri2000 needs a core-dev to approve lucid task in bug #569365, please
[10:27] <pitti> seb128: worth a try: does it work with gcc-4.5?
[10:28] <seb128> pitti, how do I try that easily?
[10:29] <pitti> configuring with CC=gcc-4.5 should do it
[10:29] <pitti> and b-dep'ing on gcc-4.5
[10:29] <pitti> it's in main
[10:29] <seb128> let me try
[10:29] <pitti> seb128: i. e. in configure-stamp rule, where CFLAGS= is set
[10:29] <pitti> (untested)
[10:30] <seb128> I'm finishing my 2.25.12.is.2.25.11 build and then test that
[10:39] <seb128> pitti, my 2.25.12.is.2.25.11 works
[10:39] <pitti> nice
[10:39] <seb128> pitti, so at least we have something we can upload one the buildds are sorted
[10:39] <seb128> trying gcc-4.5 now
[10:39] <pitti> seb128: so it's not quite clear then whether it's a glib or a gcc bug?
[10:41] <seb128> pitti, other distros don't have the issue with that glib and the debian guys who investigated says it's a compiler issue
[10:41] <seb128> pitti, I'm trying gcc-4.5 next
[11:39] <lamont> pitti: what's up?
[11:41] <seb128> lamont, hey! need help fixing the buildds
[11:41] <seb128> lamont, we got a libglib uploaded which segfaults on i386
[11:41] <lamont> oh joy
[11:41] <apw> seb128, lamont its also affecting the PPA builders
[11:41] <seb128> lamont, and we can't get a new version fixed because the buildds dist-upgrade pre-build fails on it
[11:43] <apw> pitti, should we disable the PPA i386 buildd's too as they are pinging jobs to CHROOTWAIT
[11:44] <lamont> apw: manualing them now, but I'm pretty sure that's not what pinging means
[11:44] <apw> lamping them to CHROOTWAIT perhaps :)
[11:44] <pitti> seb128: confirmed that armel and powerpc are affected too
[11:45] <pitti> seb128: given that sparc also succeeded, looks like a 32 bit only issue?
[11:45] <asac> all stop!
[11:45] <pitti> glib doing something nasty to pointers?
[11:45] <pitti> MANUALing powerpc and armel
[11:46] <seb128> pitti, should I upload my downgraded version for now?
[11:46] <pitti> seb128: if that works, please do
[11:46] <seb128> done
[11:46] <pitti> seb128: then it'll be ready to try when the builders are working again
[11:46] <seb128> I'm away for a quick bite, will be back in 10 minutes or so
[11:50] <lamont> pitti: so we need all 32-bit maverick architectures?
[11:50] <pitti> lamont: seems so; i386, armel, powerpc AFAICS?
[11:51] <lamont> joy
[11:51] <pitti> lamont: what would you recommend here? manually upgrading the chroot and || true'ing the postinst of libglib?
[11:51] <pitti> lamont: or temporarily disabling dist-upgrade?
[11:51] <pitti> it fails during dist-upgrade of the chroot, before starting the actual build, AFAICS
[11:51] <lamont> pitti: I just rolled a fresh i386 chroot, and helped libglib2.0-0 to land well
[11:52] <pitti> lamont: ok; disabling dist-upgrade is harder to do/not advisable?
[11:52] <lamont> produces a less reproducible result
[11:53] <pitti> lamont: just saying that with that hacked chroot this probably needs another update once glib is fixed?
[11:54] <lamont> once glib is newer, the dist-upgrade will take care of it each time
[11:55] <lamont> glib isn't a quick build.  do we need the old glib to build the new glib, or is the gio-modules segv isolated?
[11:56] <pitti> lamont: it's not quite clear yet whether it's a gcc bug or a bug in the newer glib, but so far we don't have any other solution than to downgrade glib
[11:56] <pitti> lamont: we don't need the old glib for build, it was a circular dependency (now fixed)
[11:57] <lamont> ah, ok.
[11:58] <lamont> so I'm hearing that we want to disable the upgrade on 32-bit, upload the old glib as a higher version, let it publish, and then re-enable the dist-upgrade, yes?
[11:59] <pitti> lamont: sounds good
[11:59] <pitti> lamont: well, I don't insist on disabling the upgrade; I was just asking whether it might be easier for you
[12:00] <pitti> it might be a central change, as opposed to having to fiddle with N chroots twice
[12:00] <lamont> given the borked nature of the new build, and your promise not to reenable everything until I turn it back on, I'm happy
[12:00] <lamont> it's not a central change
[12:00] <pitti> ok; so whatever is easiest and works :)
[12:00] <asac> i think if lamont wanted it to be simple we already would have a webUI to patch chroot etc. :-P
[12:00] <pitti> lamont: the new build is broken?
[12:01] <asac> j/k
[12:01] <pitti> lamont: (sorry, I didn't actually follow the changes in glib; this time I was by and large a bystander)
[12:01] <lamont> pitti: borked nature of a fresh chroot <-- forget what I said about "new build"
[12:01] <pitti> ah
[12:04] <lamont> pitti: use the following machines to build glib:  palmer, ross, artigas, hawthorn
[12:04] <pitti> lamont: understood; I'll bump its build score to make sure it goes first
[12:05] <seb128> lamont, pitti: thanks!
[12:05] <asac> thanks all for fixing this
[12:05] <lamont> once it's done and published, you can unmanual everything EXCEPT those 4.  poke me to go undo the hack, pls
[12:05] <pitti> lamont: ack
[12:05] <pitti> https://edge.launchpad.net/ubuntu/+source/glib2.0/2.25.12.is.2.25.11-0ubuntu1
[12:05] <pitti> hmm
[12:05] <pitti> lamont: just to make sure everythign is as expected, did we drop sparc and ia64 arches from maverick now?
[12:06] <lamont> final decision is slated for next week, iirc
[12:06] <pitti> because above build doesn't have build records for those
[12:06] <pitti> sorry, ia64 is there, but no sparc
[12:07] <Daviey> cjwatson: Ciemon has been testing Maverick, and he encountered a bug which i haven't been able to reproduce yet.  He's found that grub->recovery mode can give him a root console.  Is there something that has changed in the last  few days that could have caused that?
[12:07] <lamont> pitti: I wonder if it's still PaS on sparc
[12:07]  * lamont looks
[12:08] <pitti> glib? that'd ruin pretty much everything
[12:08] <pitti> given that upstart needs it
[12:08] <lamont> %glib2.0: !sparc                                                     # temporary workaround for buildd-killer
[12:08] <lamont> I win
[12:08] <lamont> pitti: sparc was dead in lucid
[12:09] <lamont> lack of a kernel and all that
[12:09]  * pitti sets artigas and sejong (sparcs) to manual
[12:09] <lamont> why?
[12:09] <pitti> ah, sorry, sparc is not affected
[12:09] <pitti> lamont: you said to use artigas for the glib build
[12:10] <pitti> no, sparc _is_ affectd
[12:10] <pitti> sorry, had a phone call in parallel (done now)
[12:10] <pitti> lamont: in general we still get sparc build records for maverick, so better to stop it
[12:10] <lamont> sparc has 2.24.0-0ubuntu4
[12:10] <pitti> ah, so it's not affected because the broken glib failed?
[12:11] <pitti> indeed, https://edge.launchpad.net/ubuntu/+source/gnome-session/2.31.6-0ubuntu1 succeeded on sparc
[12:11] <pitti> (from ~ 1.5 hours ago)
[12:11] <lamont> sparc doesn't believe in glib of the current era
[12:11] <pitti> ok, sparc back on auto
[12:11] <pitti> lamont: so should I just ignore your "plz use those" for artigas then?
[12:11] <pitti> and you can undo the hack there?
[12:11] <lamont> hack gone on artigas, ignore artigas
[12:12]  * pitti puts the other three back on auto, and puts a sweet cherry on top of the glib build to lure them into grabbing the builds faster
[12:13] <lamont> pitti: on that, do you need anything more from me until glib is building?  (I can actually remove the hack once the build is into installing build-deps)
[12:13] <pitti> there, they took the bait; I set them back to manual
[12:14] <pitti> lamont: assuming that these builds will actually succeed, should be enough
[12:14] <lamont> cool
[12:14] <pitti> lamont: would it be okay to revert the hack in an hour or so? just in case..
[12:14] <lamont> sure
[12:14] <pitti> we don't have a desperatingly long queue
[12:14] <pitti> so the outage of those three shoudln't hurt
[12:15] <pitti> seb128: ok, I'd like to grab some lunch, and those builds will take a bit anyway; do you need anything else right now?
[12:16] <seb128> pitti, no, thanks for helping there, I will email ubuntu-devel now
[12:20] <pitti> seb128: it's past the build-dep isntall stage on all three, anyway, so seems lamont's hack worked :)
[12:20]  * pitti &
[12:38] <seb128> pitti, lamont: new glib failed to upload
[12:38] <seb128> "2010-08-06 11:35:00 WARNING Upload was rejected:
[12:38] <seb128> 2010-08-06 11:35:00 WARNING     invalid literal for int() with base 10: '24\t.'"
[12:38] <seb128> wth?
[12:38] <seb128> http://launchpadlibrarian.net/53161958/upload_1907875_log.txt
[12:38] <seb128> "2010-08-06 11:34:50 ERROR   Exception while accepting:
[12:38] <seb128>  invalid literal for int() with base 10: '24\t.'
[12:38] <seb128>  -> http://launchpadlibrarian.net/53161956/hMxV26MZk2BTThKsEzJvkTYKbvL.txt (invalid literal for int() with base 10: '24\t.')
[12:38] <seb128> "
[12:45] <wgrant> seb128: That looks like the pkgstriptranslations issue from a few weeks ago.
[12:45] <wgrant> (yes, the error message sucks)
[12:46] <seb128> lamont, did your changes brought back pkgstriptranslations to an old version or something?
[12:46] <geser> seb128: pitti fixed that already in the past
[12:46] <lamont> seb128: that tarball was last upgraded some time ago
[12:46] <wgrant> I didn't know that any chroots existed with the bad version held, though...
[12:46] <lamont> so you're saying you want pkgstriptranslations?  any other packages vs weeks ago?
[12:46] <seb128> wgrant, lamont has been tweaking things to fix the glib screwup
[12:46] <lamont> wgrant: not held, we just completely skipped the dist-upgrade step
[12:47] <wgrant> Hmm. I wonder why the chroots would have that version, though.
[12:47] <wgrant> How odd.
[12:47] <seb128> what was the buggy version?
[12:48] <wgrant> I forget... the one where it was uploaded like 5 times in one day.
[12:48]  * wgrant checks.
[12:48] <wgrant> That bug was fixed in 73.
[12:48] <lamont> wgrant: they have the july 14 binaries
[12:48] <lamont> ish
[12:48] <lamont> (all of the tarballs)
[12:49] <wgrant> lamont: Hm, you recreated them during the brokenness? :/
[12:49] <seb128> lamont, can you check the version on the builders?
[12:49] <lamont> then the dist-upgrade step brings them current
[12:49] <lamont> wgrant: I just looked at the timestamp on the tarball
[12:49] <wgrant> Also, wouldn't this have been several hours easier if the old glib binaries were revived?
[12:51] <lamont> wgrant: yes and no
[12:52] <lamont> ii  pkgbinarymangler                70                        strips translations and alters maintainers d
[12:53] <seb128> lamont, can we update that and retry build?
[12:53] <wgrant> lamont: I mean, surely it'd be nice to fix archive breakage quickly without screwing with chroots....
[13:01] <pitti> argh
[13:01] <pitti> old ghosts come back then!?
[13:01] <lamont> seb128: and crunching along nicely now
[13:01] <lamont> pitti: you said no dist-upgrade... so you get july 14 bits
[13:01] <lamont> that was my point
[13:01] <seb128> lamont, thanks
[13:02] <lamont> seb128: it'd be nice if once we get this published, you did a fresh upload of the old bits one more time
[13:02] <seb128> lamont, you want another glib source upload?
[13:02] <pitti> lamont: right, but I didn't think of the possibility that of all possible times we'd catch the two hours with broken mangler :-( sorry about that
[13:03] <lamont> pitti: in other news, my plan (as of last night) was to build new chroots first thing this morning.
[13:03] <lamont> there's some irony or such in there somewhere
[13:03] <wgrant> So, seriously, wouldn't stuff like this be easier if you could remove the broken binaries and bring back the old ones into the archive? That's quite doable.
[13:03] <lamont> wgrant: with a higher than broken version number?
[13:03] <wgrant> lamont: Not critical if the chroots are old.
[13:03] <pitti> lamont: nice timing for the win!
[13:03] <lamont> except for the user
[13:04] <seb128> lamont, you need a source upload? when?
[13:04] <pitti> someone retried the glib i386 build then?
[13:04] <pitti> "started 5 mins ago"
[13:04] <wgrant> lamont: Well, the intention would be to get builds unbroken, then get a newer version out to users once the world is fixed.
[13:04] <lamont> seb128: once the current one is published - I'll let pitti decide if he wants that to build (using current build-deps) before autoing the world, or if he's ok with the july 14 build-deps and letting it happen when it does
[13:04] <lamont> pitti: I did
[13:04] <lamont> with current pkgbinarymangler
[13:05] <seb128> why do you need a new source upload?
[13:05] <seb128> if you retried the current one
[13:05] <lamont> seb128: totally separate issue
[13:05] <pitti> seb128: the current build is bad, since it builds with an old toolchain, etc.
[13:05] <lamont> seb128: I'd like glib to be built with current build-deps, instead of 3-week old build-deps
[13:05] <seb128> ok, fair enough
[13:05] <lamont> s/build-deps/maverick/
[13:05] <seb128> I'm still aiming at trying to fix 2.25.12 if I can
[13:06] <pitti> seb128: that'd be even better, of course :)
[13:06] <pitti> seb128: it's an exercise in git bisect, by and large?
[13:06] <lamont> if you give me a window where the world is happy, I'll freshen the chroots this morning
[13:06] <seb128> pitti, I'm not sure, 2.25.12 built from tarball doesn't crash
[13:07] <seb128> but I'm only LD_LIBRARY_PATH loading the libraries
[13:08] <pitti> seb128: do you get a crash if you have the working glib installed, and LD_LIB_PATH'ing the one from the known-broken glib .deb?
[13:08] <pitti> seb128: if that doesn't crash either, then apparently L_L_P doesn't work (enough); if it doesn't crash, then it might be a patch of our's?
[13:13] <seb128> pitti, yes
[13:13] <seb128> it crashes this way
[13:16] <pitti> seb128: ok, so LD_L_P is working to reproduce the crash, and it's something that we patched in our package?
[13:16] <pitti> seb128: i. e. I assume "build from tarball" means "from upstream"?
[13:17] <seb128> pitti, it means tar xzf orig.tar.gz; cd glib; ./configure --prefix=/usr && make
[13:17] <pitti> *nod*
[13:18] <seb128> pitti, I'm doing a deb build without distro changes now
[13:19] <pitti> seb128: my first suspect would be 71_gio_launch_handler.patch
[13:19] <seb128> it's not
[13:19] <seb128> debian doesn't have this change
[13:19] <pitti> ok; well, then good hunting!
[13:19] <seb128> I'm wondering if that could be due to the rules
[13:19] <seb128> LDFLAGS += -Wl,-O1
[13:20] <seb128> for example
[13:20] <seb128> pitti, thanks ;-)
[13:20] <seb128> pitti, thank you for trying to give me hints as well ;-)
[13:23] <pitti> i386 finished
[13:23] <pitti> seb128: would you mind testing the binaries from https://edge.launchpad.net/ubuntu/+source/glib2.0/2.25.12.is.2.25.11-0ubuntu1/+build/1907344 ?
[13:23] <pitti> seb128: they were built with an older toolchain, so we can't assume that they work now (i. e. as in your local build)
[13:25] <seb128> pitti, trying
[13:27] <seb128> pitti,
[13:27] <seb128> pitti, works
[13:28] <pitti> \o/
[13:28] <pitti> lamont: so, you can un-hack palmer/ross/hawthorn
[13:30] <lamont> pitti: all unhax0red.
[13:30] <lamont> pitti: ok if I leave the unmanual to you?  if it's published, I'll go do it now if you want
[13:30] <pitti> lamont: yes, that's fine
[13:31] <pitti> I'll reanimate them
[13:31] <pitti> lamont: and seems seb128 just found the root cause
[13:31] <pitti> so we now at least have a much better workaround
[13:32] <lamont> yay
[13:32] <didrocks> hum, I get some "Failed to upload", I think this is related to previous chroot/builder issue? (https://launchpad.net/ubuntu/+source/zeitgeist-extensions/0.0.3-0ubuntu1/)
[13:33] <pitti> didrocks: yes, you can just retry those
[13:33] <didrocks> pitti: ok, thanks :)
[13:46] <didrocks> pitti: still the same upload issue
[13:46] <pitti> didrocks: hang on, will look later
[13:46] <seb128> didrocks, what does the upload log say?
[13:46] <didrocks> sure, no hurry, good luck with you current debug stack :)
[13:47] <didrocks> http://paste.ubuntu.com/474019/
[13:47] <didrocks> 2010-08-06 12:36:42 WARNING Upload was rejected:
[13:47] <didrocks> 2010-08-06 12:36:42 WARNING     Duplicated ancestry
[13:47] <pitti> didrocks: ah, that's not mangler then
[13:47] <didrocks> I don't remember we uploaded it before…
[13:47] <pitti> didrocks: someone promoted a package to main or universe while it was built
[13:47] <pitti> you need to wait for a publisher
[13:48] <didrocks> pitti: "a package"? I don't really understand where the error is here TBH
[13:48] <pitti> didrocks: zeitgeist-extensions?
[13:49] <pitti> didrocks: look at https://edge.launchpad.net/ubuntu/+source/zeitgeist-extensions/+changelog
[13:49] <pitti> didrocks: it's published twice
[13:49] <pitti> apparently it was moved to main within this our
[13:49] <didrocks> oh ok, this is possible even if the first binary wasn't NEWed? ok, I understand now :)
[13:49] <didrocks> pitti: thanks, I'll wait for the publisher so
[13:57] <lamont> pitti: are we just waiting on a publisher run for the unmanual?  or are you waiting for another glib2.0?
[13:58] <pitti> lamont: publisher, and https://edge.launchpad.net/builders/hawthorn to finish
[13:58] <lamont> oh yeah.  hawthorn
[13:58] <lamont> that has the current pkgbinarymangler, fwiw
[13:58] <pitti> lamont: I'd like the packages to be published before I let any other package buildl
[13:58] <pitti> otherwise we have to retry even more
[13:59] <lamont> verily
[14:57] <jcastro> mpt: any clue as to where to report bugs on the apt.ubuntu.com redirector thing?
[14:57] <mpt> jcastro, no -- no-one is assigned to work on it
[14:58] <jcastro> is it going away eventually or will it be superceded by something or ... ?
[14:58] <jcastro> (trying to figure out if we should tell people to use it)
[15:06] <hyperair> Can't locate Dpkg.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/bin/dpkg-source line 22.
[15:06] <hyperair> BEGIN failed--compilation aborted at /usr/bin/dpkg-source line 22.
[15:06] <hyperair> what happened? O_o
[15:10] <mpt> jcastro, I nagged rickspencer3 about finding someone to develop it at Guadec. More nagging would help. :-)
[15:14] <jcastro> mpt: I am born to nag, I just need the name of the person who touched it last
[15:16] <mpt> jcastro, Andrew Glen-Young iirc
[15:18] <pitti> seb128: I think I can set the buildds back to auto now
[15:18] <pitti> libglib2.0-0 | 2.25.12.is.2.25.11-0ubuntu1 |      maverick | amd64, i386, ia64, powerpc
[15:19] <lamont> pitti: woot!
[15:19] <lamont> pitti: you say so, I'll do it
[15:19] <pitti> palmer and ross back on auto
[15:19] <pitti> lamont: not yet armel
[15:19] <pitti> that still needs 40 mins for publishing
[15:19] <pitti> lamont: but the rest looks okay
[15:20] <seb128> pitti, thanks
[15:20] <lamont> pitti: so... terranova samarium lansones lychee actinium lemon litembilla rothera papaya hassium seaborgium thorium iridium thallium vernadsky adare muntries sandpaperfig radium rosehip nannyberry doubah uranium einsteinium dubnium shipova, yes?
[15:21] <lamont> done
[15:21] <pitti> lamont: https://edge.launchpad.net/builders looks good now
[15:22] <pitti> lamont: oh, you have an en-masse way to enable/disable them? I usualy click through all of them on above page
[15:22] <lamont> pitti: btw, you forgot ivy and kaylaberry when you did the manual thing... though I think we're safe there
[15:22] <Lukian> testing an upgrade from lucid to maverick results in dpkg: parse error, in file '/var/lib/dpkg/status' near line 48098 package 'virtualbox-3.1': error in Version string `3.1.6-59338_Ubuntu_karmic': invalid character in revision number -- should I file this bug against virtualbox or dpkg?
[15:23] <pitti> lamont: oops, indeed; wasn't aware that we had armel PPA builders
[15:23] <lamont> pitti: nothing actually uses them quite yet that I've seen
[15:23] <seb128> Lukian, known dpkg bug
[15:23] <Lukian> known bug? cheets
[15:23] <lamont> though in theory, that's going to change
[15:23] <seb128> Lukian, it's filed in launchpad and debian already
[15:23] <Lukian> cheers*
[15:24] <seb128> Lukian, you can edit your available and status files to workaround the issue
[15:24] <seb128> it does't like the _U..._
[15:24] <Lukian> already done ;)
[15:24] <pitti> seb128: how is that a dpkg bug?
[15:24] <Lukian> pitti, because it's a semi-valid version number? :>
[15:25] <pitti> how is 3.1.6-59338_Ubuntu_karmic a valid version number?
[15:25] <pitti> it's clearly not
[15:25] <Lukian> haha indeed
[15:25] <Lukian> but yeah, it still needs to be filed and fixed
[15:25] <pitti> http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
[15:26] <Lukian> pitti, maybe one day Sun will even lowercase the executable from "VirtualBox" to "virtualbox"
[15:26] <Lukian> Oracle*
[15:27] <seb128> pitti, well dpkg allowed people to install it at some point so it should allow them to get out of it
[15:35] <jcastro> didrocks: feature requests for banshee-meego that are ubuntu-specific should go in launchpad?
[15:35] <didrocks> jcastro: if it's ubuntu specific, yeah it should
[15:36] <didrocks> jcastro: if we can have the udev branch merge next week, it will be awesome. I'll be then on holidays for two weeks…
[15:36] <jcastro> ok let me see
[15:37] <jcastro> didrocks: next wednesday fine?
[15:37] <jcastro> that's 1.7.4
[15:37] <didrocks> jcastro: yeah, it is :)
[15:38]  * Laney hopes we can get banshee back in sync
[15:58] <hrw> hi
[15:59] <ttx> pitti: got one for you. Due to bug 614393 I consider reverting a recent upload to antlr3-3.2 and go back to antlr3-3.0.1 we had in lucid
[15:59] <hrw> http://hrw.pastebin.com/PNhm3K5Y - can someone help me with debian/control file to make it pass lintian?
[16:00] <ttx> pitti: I don't think we raelly want 30+ MIRs over this one
[16:00] <ttx> pitti: I should do a 3.2-really3.0 upload ?
[16:02] <pitti> ttx: ooh, please do
[16:02] <ttx> pitti: I need some guidance on the process, I never did that.
[16:02] <geser> hrw: on which architectures should the package get build? i386, amd64, armel, etc or a subset or only one specific?
[16:03] <ttx> pitti: is it just about uploading a new "version" that is 3.0.1 but as 3.2-really3.0.1.orig.tar.gz ?
[16:03] <hrw> geser: any basically
[16:03] <pitti> ttx: right, rename hte old tarball accordingly, and bump debian/changelog
[16:04] <ttx> pitti: what should the version name look like ?
[16:04] <geser> hrw: then add "Architecture: any" to the source stance in debian/control to get rid of the error (E:)
[16:04] <ttx> lucid has  3.0.1+dfsg-4ubuntu2, maverick has FTBFS 3.2-4
[16:04] <hrw> ok
[16:04] <pitti> ttx: 3.2.is.3.0.1-0ubuntu1 perhaps?
[16:05] <ttx> pitti: that would force us to stick with it until debian goes to 3.3, right (not that I care, but...)
[16:07] <pitti> ttx: but if you reuse 3.2-*, then you can't upload a new orig.tar.gz
[16:07] <geser> hrw: and you can ignore the warning about "linux-source" as it's is a real-package, and the other warning looks like you missed the XSBC- before Original-Maintainer
[16:08] <pitti> ttx: so 3.2 can't be built without the new dependencies?
[16:09] <ttx> no, upstream migrated to maven build system and debian followed suit
[16:09] <ttx> that's something we'll have to do at one point
[16:09] <ttx> but I'm pretty sure this is not the right moment in cycle to do it
[16:10] <ttx> especially with the possible outcome of breaking eucalyptus by upgrading a few libs in the process
[16:10] <pitti>  ttx 3.2.is.3.0 it is, then?
[16:10] <geser> ttx: as your are currently talking about a MIR (and AFAIK take also care about java packages): could you comment on bug 614000 (as additional input for the MIR team)
[16:10] <ttx> yep, will do
[16:10] <ttx> geser: looking
[16:11] <ttx> sounds reasonable, at least for axis
[16:12] <ttx> libservlet2.4-java is getting deprecated, shouldn't have anything in main depending on it anymore
[16:13] <ttx> geser: commented
[16:13] <geser> thanks
[16:17] <ttx> pitti: thanks for your input !
[16:28] <pitti> seb128, lamont: FYI, I switched the armel buildds back to auto as well now
[16:28] <seb128> pitti, thanks
[16:29]  * pitti hugs seb128 "hero of maverick"
[16:29] <lamont> pitti: woot.
[16:29] <pitti> seb128: note that the previous upload somehow didn't create a sparc build, but I guess/hope the next one will again
[16:29]  * seb128 hugs pitti back
[16:29] <lamont> I'll cook a set of tarballs today, and get blessings on them before deploying them monday
[16:29] <pitti> but then again, let's just ditch it
[16:29] <seb128> thanks again for helping sorting that
[16:29] <pitti> lamont: we shold wait on the next upload from seb128 with the real fix, I think
[16:29] <pitti> (for "good" chroots)
[16:30] <pitti> have a nice weekend everyone!
[16:31] <lamont> pitti: true
[16:31] <lamont> seb128: poke me when it's uploaded, mk?
[16:31]  * lamont -> town, afk
[16:38] <sconklin> what's the right place for pure python app  modules to install? I'm working on packaging one and the original app installed to /usr/share/appname/, but the debian packaging tools want to put it in /usr/lib/pymodules/python2.6/appname/
[17:17] <mathiaz> kees: once you've gone through all your daily USN, would you mind poking at libdbi MIR (bug 608552)?
[17:18] <kees> mathiaz: yup, MIR is on the list for today. :)
[17:19] <mathiaz> kees: \o/ - think ya
[17:19] <kees> oar welcome
[17:27] <RoAkSoAx> can someone please take a look to the following MIRs: bug #515996 bug #527155 bug #527142 bug #527182
[17:29] <Daviey> jdstrand: Hey.. Are you thinking of doing a libvirt 0.8.3-1 merge?
[17:29] <jdstrand> Daviey: yes
[17:29] <jdstrand> Daviey: probably first thing next week
[17:31] <Daviey> jdstrand: Okay, that's great - could i ask that you keep me posted on it.. i'd like to test it as soon as.. thanks.
[17:31] <jdstrand> Daviey: sure
[17:32] <Daviey> thanks!
[17:32] <jdstrand> Daviey: I should qualify the 'first thing next week' -- that is when I will start it. it is a complicated merge and there is likely a migration script I need to finish writing
[17:33] <jdstrand> Daviey: I'm not sure when it'll be done, but libvirt is my priority next week
[17:33] <Daviey> jdstrand: yeah.. the delta looks kinda scary :(...   The migration script will be a debian/ maintainer script?
[17:34] <jdstrand> Daviey: initially, yes. depending on my findings I may push to Debian and upstream
[17:34] <Daviey> jdstrand: Well, if you want me to do some smoke testing with it against UEC before it hits the archive, i don't mind.. just point me to a branch :)
[17:34] <jdstrand> k
[17:34] <jdstrand> thanks
[17:34] <Daviey> np
[17:34]  * Daviey dashes.
[19:22] <tkamppeter> pitti, hi
[19:27] <geser> tkamppeter: he fled into weekend 3h ago
[19:39] <hakzsam_> hi all
[19:40] <hakzsam_> I try to install rhythmbox from the sources, I downloaded them with 'git clone git://git.gnome.org/rhythmbox'
[19:40] <hakzsam_> but I have a problem with the './configure' script
[19:40] <ion> topic
[19:41] <hakzsam_> the error message is here : http://pastebin.com/6tNs0dtr
[19:41] <Pici> hakzsam_: This isn't a support channel, please see the topic.
[19:41] <hakzsam_> Pici, okay, but where is the topic ?
[19:42] <Pici> hakzsam_: /topic should tell you
[19:42] <hakzsam_> Pici, thanks !
[19:53] <ebroder> Hmm...what happens if you build a live CD with a ureadahead pack? Are there too many differences across different hardware for it to help?
[19:54] <ebroder> Could I build a live CD, generate a pack, drop the pack in and then re-squash the fs? Or is that going to re-arrange everything to the point that it does more harm than good?
[19:56] <LucidFox> "Taking the time to fix all the reported bugs is likely to mean that the fully open beta will be somewhat delayed."  :-P
[19:57] <ScottK> ebroder: No, because I don't know how.  I suspect you'll only be satisfied by trying it, so you should just go do that.
[19:57] <ebroder> How can it be a bad idea, in theory at least? Let's see...I could drop the pack in the initramfs and copy it over to the aufs mount, so that would keep me from mucking with the squashfs...
[19:59] <ScottK> Which reinforces my point.
[19:59] <ebroder> Fair enough. I'm mostly curious if I can avoid duplicating someone else's work, but I'll probably just give it a go
[20:00] <ScottK> If you are duplicating someone's work, it's not mine.
[20:15] <hdon> hi all. i am debugging a program freeze in Pidgin on Lucid Lynx. (http://pastebin.mozilla.org/763072) i have installed libgtk2.0-0-dbg but gdb still doesn't know simple things like function prototypes to show me the arguments of functions on the stack automatically. please help :)
[20:49] <hdon> .....
[20:55] <LucidFox> Hmm
[20:55] <LucidFox> how can I get an @ubuntu/member IRC hostmask?
[20:56] <cody-somerville> LucidFox, If you're a Ubuntu member, you can ask the IRC Council.
[23:18] <RoAkSoAx> kees: I'm wondering why you changed MIR's bug #527155 bug #527182 bug #527142 to incomplete, when I intentionally changed them back to new (by first updating the necessary information) to be processed?
[23:19] <RoAkSoAx> without any further explanation
[23:22] <kees> RoAkSoAx: heartbeat was already approved (so it should stay in "In Progress" state)
[23:23] <kees> RoAkSoAx: cluster-glue is still missing manpages
[23:23] <kees> RoAkSoAx: cluster-agents depends on cluster-glue
[23:24] <kees> I didn't add any comments because the changes back to "new" looked accidental, and included no comments either. :P
[23:25] <verb3k> Previous releases of ubuntu used to list CD/DVD drive device names in fstab, but in Lucid this is no more, why?
[23:33] <RoAkSoAx> kees: oh ok, I thought it was because they were still unseeded... anyways, thank you :)
[23:36] <kees> RoAkSoAx: they should go from In Progress to Fix Released once they're seeded and an archive admin promotes them
[23:40] <RoAkSoAx> kees: ok. Thanks. I'll keep an eye on them till they get seeded. Thank you!
[23:43] <kees> RoAkSoAx: cool; thanks!


[00:23] <mikubuntu> guys, i'm at a friends trying to install 10.04, and it failed on the first partitioning step (says it failed to partition the ext4 file) what could be the problem, it will not go forward from here.  this is a usb stick i'm using, but i do have an alt install in the car.
[00:24] <cody-somerville> mikubuntu, Hey
[00:25] <cody-somerville> mikubuntu, Can you pastebin /var/log/partman ?
[00:26] <mikubuntu> hmmmm, i'm just running on the live disk right now
[00:27] <well_laid_lawn> it still should make the log afaik
[00:27] <mikubuntu> cody-somerville: i run xubuntu on a couple of my home machines, but this is ubuntu 10.04 i'm trying to install for him because he has the horsepower to run it, replacing xp
[00:30] <mikubuntu> i can't find a file manager on the livecd menu
[00:32] <De[V]oN> Hi, I have the last version of openoffice
[00:32] <De[V]oN> and I have this bug/issue<EMAIL_ADDRESS>[00:32] <De[V]oN> that is fixed / solved in a new version
[00:32] <De[V]oN> how can I upgrade to a new version if I already have the backports
[00:34] <well_laid_lawn> mikubuntu: alt+f2 thunar
[00:35] <mikubuntu> says :: The ext4 file system creation in partition #1 of Serial ATA RAID isw_bebjjhjaff_ARRAY (mirror) failed.
[00:35] <well_laid_lawn> !raid
[00:36] <De[V]oN> !openoffice :P
[00:37] <well_laid_lawn> !openoffice
[00:37] <De[V]oN> yes, I know...
[00:38] <De[V]oN> well_laid_lawn: I already have openoffice 3
[00:38] <well_laid_lawn> k :]
[00:38] <De[V]oN> but I have a ugly bug that I can't create new sheet
[00:39] <well_laid_lawn> a known bug?
[00:39] <De[V]oN> or even rename a sheet
[00:39] <De[V]oN> well_laid_lawn: yes, and it's fixed y the m82 version
 and I have this bug/issue<EMAIL_ADDRESS>[00:40] <mikubuntu> ok, i have thunar open what's the file?   /var/log/partman  for some reason i go thru thunar from var to log to partman and when i click partman the app crashes shut
[00:40] <De[V]oN> ii  openoffice.org                    1:3.2.0-7ubuntu4.1
[00:41] <well_laid_lawn> mikubuntu: the install partitioner still open?
[00:41] <well_laid_lawn> try the back button
[00:42] <mikubuntu> well_laid_lawn: i aborted the install process .. tried several times to use the back button but then it would not go forward
[00:43] <well_laid_lawn> De[V]oN: if you need the new version you'll have to get it yourself
[00:43] <De[V]oN> I try the PPA reposity and anyway  I have the it has the last version
[00:44] <mikubuntu> well_laid_lawn: i do have an alt install disk, but i wont be able to be online if i try that, and maybe it will have the same problem?
[00:44] <De[V]oN> well_laid_lawn: ok thanks that all I want to heard! and sorry for my bad english
[00:44] <well_laid_lawn> mikubuntu: sounds like you'll have to abort the install to get to the log - can you do that
[00:44] <well_laid_lawn> De[V]oN: you did fine with your english :]
[00:44] <mikubuntu> well_laid_lawn: can you tell me path to it?
[00:45] <well_laid_lawn> mikubuntu: not offhand
[00:45] <well_laid_lawn> ps aux | grep install    maybe
[00:45] <well_laid_lawn> ps aux | grep instal    maybe
[00:46] <De[V]oN> mikubuntu: why don't you try to open the log file whit another program?
[00:46] <mikubuntu> well_laid_lawn:  this is output i get: ubuntu   10817  0.0  0.0   3320   804 pts/0    S+   19:46   0:00 grep --color=auto install
[00:47] <mikubuntu> De[V]oN: ok, i just need to know how :(
[00:48] <well_laid_lawn> mikubuntu: thats the command you issued being found
[00:48] <De[V]oN> mikubuntu: I you just want to read that log file try with less /var/log/partman
[00:48] <De[V]oN> to quit use the q key
[00:48] <well_laid_lawn> nice
[00:48] <De[V]oN> sorry, if you want to...
[00:48] <well_laid_lawn> worth a shot :]
[00:49] <mikubuntu> well_laid_lawn: not sure i understand .. you mean command is ::    less /var/log/partman    ?
[00:49] <De[V]oN> mikubuntu: I don't know if you can read that file being a normal user, maybe you have to add sudo at the beginning
[00:50] <De[V]oN> mikubuntu: yes
[00:50] <De[V]oN> try first with  less /var/log/partman and if you can't read it try sudo  less /var/log/partman
[00:50] <De[V]oN> and you can move with the page down and page up keys
[00:50] <De[V]oN> mikubuntu: what are you looking for?
[00:53] <De[V]oN> and remember to quit use the q key ;)
[00:54] <mikubuntu> strange when i run that i get an endless output i think its just repeating over and over, should i just paste a section of it?
[00:55] <De[V]oN> mikubuntu: again, what are you looking for?
[00:55] <well_laid_lawn> the file is being written to so that's what you're seeing
[00:55] <well_laid_lawn> run   top   and see if the cpu is working hard
[00:55] <De[V]oN> mikubuntu: if you want to read the last part try with tail instead of less
[00:56] <mikubuntu> so should i paste just a section?
[00:56] <De[V]oN> mikubuntu: and if you want to read that file while if being writing use tail -f /var/.....
[00:56] <mikubuntu> oh, you're saying run with 'tail' it will go to the end?
[00:56] <well_laid_lawn> I would try and stop it being written to
[00:56] <well_laid_lawn> in top hit the k key to kill an app
[00:57] <mikubuntu> so kill the terminal and open another?
[00:57] <De[V]oN> mikubuntu: I don't know what are you looking for, I'm only helping to read that log file ;)
[00:57] <well_laid_lawn> just hit q
[00:57] <well_laid_lawn> the partitioner wouldn't make an ext4 filesystem
[00:58] <mikubuntu> De[V]oN: looking for the file that well_laid_lawn  wants to see
[00:58] <De[V]oN> mikubuntu: read what well_laid_lawn is saying to you, it seams that know what is your problem
[00:59] <mikubuntu> parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 149 parted_server: Opening infifo /bin/partman-commit: IN: QUIT parted_server: Read command: QUIT parted_server: Quitting ubiquity: IN: PARTITIONS =dev=mapper=isw_bebjjhjaff_ARRAY
[00:59] <De[V]oN> mikubuntu: ok so, use tail -f /var/log/partman and you are going to see only the last part (and while is be written)
[00:59] <De[V]oN> mikubuntu: to exit now you have to use the combination of CTRL+c keys
[00:59] <mikubuntu> well_laid_lawn: thats from the 'tail'
[01:00] <well_laid_lawn> er what is?
[01:00] <mikubuntu> parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 149 parted_server: Opening infifo /bin/partman-commit: IN: QUIT parted_server: Read command: QUIT parted_server: Quitting ubiquity: IN: PARTITIONS =dev=mapper=isw_bebjjhjaff_ARRAY
[01:00] <well_laid_lawn> k :] sorry
[01:01] <well_laid_lawn> mikubuntu: it is having an issue with the raid setup - did you know it was using a raid setup?
[01:01] <well_laid_lawn> !raid
[01:01] <De[V]oN> well here is 9pm so I'm going to cook and have dinner ;) see you in a while if I can help
[01:01] <mikubuntu> well_laid_lawn: nope
[01:02] <mikubuntu> De[V]oN: thx
[01:02] <well_laid_lawn> mikubuntu> says :: The ext4 file system creation in partition #1 of Serial ATA RAID isw_bebjjhjaff_ARRAY (mirror) failed.
[01:02] <mikubuntu> yup
[01:02] <well_laid_lawn> of Serial ATA RAID
[01:02] <well_laid_lawn> !raid
[01:02] <well_laid_lawn> !bot
[01:08] <mikubuntu> well_laid_lawn: i lookd at the raid page, but i don't understand why the installer is giving me this problem, i've never seen it before on lots of installs
[01:09] <well_laid_lawn> mikubuntu: could be anything from a less then ideal usb installer setup to ...
[01:10] <mikubuntu> and it looks like raid is something you 'install' or configure,
[01:10] <well_laid_lawn> I would try to kill the installer and read that log file - what does   sudo fdisk -l   return?
[01:11] <well_laid_lawn> I know nothing about raid sorry :]
[01:11] <well_laid_lawn> I don't even know if fdisk does raid...
[01:12] <mikubuntu> well_laid_lawn: http://pastebin.ubuntu.com/473324/
[01:12] <well_laid_lawn> k
[01:13] <mikubuntu> that is the first usb installer i have made, and it is untested
[01:14] <well_laid_lawn> looks like raid to me
[01:14] <well_laid_lawn> mikubuntu: time to get the alt cd then I think
[01:14] <mikubuntu> and like i said, i DO have an alternate installer on a cd that i could use, but i am worried to start an install and have to abort and leave him with NO SYSTEM
[01:15] <mikubuntu> the usb is running fine live, its what i'm on right now talking to you
[01:15] <well_laid_lawn> you could take out a disk... - like I said I know nothing about raid
[01:15] <mikubuntu> how did raid come into the picture i wonder, because i have never had this issue before
[01:16] <well_laid_lawn> maybe you never installed on a raid system before?
[01:17] <well_laid_lawn> !info mdadm | mikubuntu
[01:17] <mikubuntu> you mean the raid system is set up on the target microsoft machine?
[01:17] <well_laid_lawn> or is set in the bios
[01:19] <mikubuntu> is that something microsoft 'support' might have altered in his bios to thwart os installs?
[01:19] <mikubuntu> i'm a suspicious person ... they keep getting this guy for $100 and more a pop to 'fix' his machine
[01:19] <mikubuntu> he's 94 years old
[01:20] <mikubuntu> he has allowed them remote access many times
[01:21] <xman> hi! can someone help me get my sound working?
[01:21] <mikubuntu> i gotta go for now, thanks for all your help well_laid_lawn
[01:21] <well_laid_lawn> I don't know - I would think it would be a hardware setup choice
[01:21] <well_laid_lawn> mikubuntu: sorry we didn't get further for him
[01:21] <xman> I have no clue what to do?
[01:22] <well_laid_lawn> I feel that way too sometimes...
[01:22] <xman> just  upgraded from 9.10
[01:22] <well_laid_lawn> woot
[01:22] <mikubuntu> thx again
[01:23] <xman> with 9.10 it worked just fine, but not with 10.04?
[01:24] <xman> what can I do?
[01:28] <xman> ya all sleeping here?
[01:28] <well_laid_lawn> I was making coffee :]
[01:28] <xman> hehe:)
[01:28] <well_laid_lawn> what does   aplay -l   return in terminaql
[01:28] <xman> why did you say that, now I gotto make some to:)
[01:29] <well_laid_lawn> or in terminal even...
[01:29] <xman> you know Im a total noob with this thing
[01:29] <xman> I can install the restricted extras but thats about it
[01:29] <well_laid_lawn> everyone was a noob once
[01:30] <well_laid_lawn> it is a practise thing
[01:30] <xman> yeah I guess
[01:30] <well_laid_lawn> same as using windows is
[01:30] <xman> it say list of playback hardware
[01:31] <xman> card 0 ICH5 [intel ICH5]
[01:32] <xman> whatever that means? but it seems I got a soundcard, hehe:)
[01:32] <well_laid_lawn> does   aplay /usr/share/sounds/alsa/Font_Center.wav   do anything?
[01:33] <well_laid_lawn> !tab
[01:33] <xman> it say the dir or file not exist
[01:34] <xman> ok thanks ubotto
[01:34] <well_laid_lawn> use the tab key to autocomplete the filename - so type aplay /u   and hit the tab key
[01:35] <xman> same result
[01:36] <well_laid_lawn> you can't tab to a file that doesn't exist
[01:37] <xman> I see the file
[01:37] <well_laid_lawn> so you need to type the path in right
[01:37] <well_laid_lawn> capitals are important
[01:37] <xman> yes Im inteh alsa dif now
[01:37] <xman> dir
[01:37] <well_laid_lawn> hit tab button twice then
[01:38] <xman> but its called Front_Center.wav
[01:38] <xman> not Font:)
[01:38] <well_laid_lawn> oops my bad - I did mean to type Front
[01:39] <xman> I just did audacious Front_Center.wav
[01:39] <xman> the audacious pos up and play it but not sound comeing from my speaker?
[01:40] <xman> sorry, I mean it pops up
[01:40] <well_laid_lawn> audacious is very diff then aplay - aplay comes from alsa and it is alsa that sets the sound up
[01:41] <xman> ok, will try aplay then
[01:42] <well_laid_lawn> aplay /usr/share/sounds/alsa/Front_Center.wav   it should have been
[01:43] <xman> yes it say it playing it
[01:43] <xman> but I hear no sound
[01:43] <well_laid_lawn> k
[01:43] <xman> strange huh?
[01:44] <well_laid_lawn> try    cat /dev/urandom > /dev/dsp   - be careful it is loud - ctrl+c   to kill it
[01:45] <xman> ok wait
[01:46] <xman> no sound
[01:47] <well_laid_lawn> I've got an ich5 on the pvr - one sec
[01:48] <xman> ok:)
[01:49] <well_laid_lawn> can you paste the file /etc/asound.state ?
[01:49] <well_laid_lawn> !paste
[01:49] <xman> ok I try
[01:50] <well_laid_lawn> and if you run the sound through external speakers make sure they're on :]
[01:51] <xman> sure, Im not that dumb :)
[01:51] <well_laid_lawn> heh
[01:51] <xman> lol
[01:52] <xman> man, I dont have that file?
[01:52] <xman> Im in the etc dir now, don't see it
[01:53] <well_laid_lawn> is there an alsa folder?
[01:53] <xman> nope
[01:54] <xman> I know I should have that:O
[01:54] <well_laid_lawn> any other sound cards in the system?
[01:55] <xman> no I only have the one intergrated in my mobo
[01:55] <well_laid_lawn> no tv card or similar?
[01:55] <xman> no nothing
[01:55] <well_laid_lawn> k
[01:55] <xman> I have 2 controllercards?
[01:56] <well_laid_lawn> what does   sudo service alsa restart   return?
[01:56] <xman> alsa: unrecognized service
[01:58] <xman> maybe the driver for the ich5 is not installed?
[02:00] <well_laid_lawn> lsmod | grep snd   will tell
[02:00] <xman> ok
[02:01] <xman> I pasted it in that website
[02:01] <well_laid_lawn> it will have a diff url
[02:02] <xman> snd_intel8x0           25588  6
[02:02] <xman> snd_ac97_codec        100646  1 snd_intel8x0
[02:02] <xman> ac97_bus                1002  1 snd_ac97_codec
[02:02] <xman> snd_pcm_oss            35308  0
[02:02] <xman> snd_mixer_oss          13746  3 snd_pcm_oss
[02:02] <xman> snd_pcm                70662  3 snd_intel8x0,snd_ac97
[02:02] <well_laid_lawn> k
[02:02] <xman> snd_seq_dummy           1338  0
[02:02] <xman> snd_seq_oss            26726  0
[02:02] <xman> snd_seq_midi            4557  0
[02:02] <xman> snd_rawmidi            19056  1 snd_seq_midi
[02:02] <xman> snd_seq_midi_event      6003  2 snd_seq_oss,snd_seq_midi
[02:02] <xman> snd_seq                47263  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_m
[02:02] <well_laid_lawn> you'll get kicked
[02:02] <xman> idi_event
[02:02] <xman> snd_timer              19098  2 snd_pcm,snd_seq
[02:02] <xman> snd_seq_device          5700  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmi
[02:03] <xman> di,snd_seq
[02:03] <xman> snd                    54148  18 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mix
[02:03] <xman> er_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
[02:03] <xman> soundcore               6620  3 snd
[02:03] <xman> snd_page_alloc          7076  2 snd_intel8x0,snd_pcm
[02:03] <xman> thats all:)
[02:03] <xman> what is say?
[02:04] <well_laid_lawn> the first line was enough
[02:04] <well_laid_lawn> the modules are there
[02:04] <xman> ok, sorry
[02:04] <xman> this is so wierd :/
[02:04] <well_laid_lawn> !intelhda
[02:04] <well_laid_lawn> might have a clue
[02:05] <xman> ok I will have a look
[02:09] <xman> thanks anyway:)
[02:10] <well_laid_lawn> np :]
[02:17] <Guest11331> anybody have problems with webkit based browsers crashing?
[03:15] <eduardo> Good night, yesterday I received a lot of help to fix a problem with my screen, it's a notebook Toshiba Satellite M35X, when I start the laptop in normal mode, the screen goes black. I applied some of the instructions I received yesterday but the problem persists. I need to know how to configure the screen manually to fix this issue, the system only starts in recovery mode...
[03:42] <eduardo> sorry the light went off... I'm back to see if somebody can help me
[03:55] <eduardo> Good night, yesterday I received a lot of help to fix a problem with my screen, it's a notebook Toshiba Satellite M35X, when I start the laptop in normal mode, the screen goes black. I applied some of the instructions I received yesterday but the problem persists. I need to know how to configure the screen manually to fix this issue, the system only starts in recovery mode...
[04:58] <eduardo> I don't have audio either, it looks like a driver problem... ¿are there drivers in Linux?
[05:22] <eduardo> Please ¿is there in the chat room somebody who can help me??...
[05:23] <psycho_oreos> the drivers for sound card should generally be built into the kernel
[05:25] <eduardo> Thank you for answering, ¿how do I know if they are there?? ¿may I see if the drivers for the screen are there too?
[05:27] <psycho_oreos> `modprobe -l' would show all the available modules regardless if they are suitable with your machine's configuration or not.. then there's `lspci -k' which will show you what chipsets you have that's visible to linux kernel on pci level bus (i.e. non USB) followed by kernel modules in use and available modules (if any)
[05:29] <eduardo> Thank you I'll take a look... and tell you what I found... ¿Ok?
[05:30] <psycho_oreos> maybe, but if you're going to paste, use pastebin
[05:38] <eduardo> Ok... I will paste only the ones dealing with audio or vga   there are 999 lines of output for the first order I'll look for those lines only and ask about the ones I think that could be useful
[05:59] <eduardo> lspci -k output is 46 lines this one appears when I look for "audio" : 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03
[06:06] <eduardo> sorry I had to restart...
[06:09] <eduardo> can you read above?? or do I paste th result again??
[06:13] <psycho_oreos> that paste was missing kernel modules
[06:18] <eduardo> Ok I'll see again... be patient please I'm really new in this ... before I restarted I was trapped in a "man" page... wondering how to go back to the screen with a prompt... and looking the documentation ... there appear a lot of information about man pages but not on how to go back to the terminal screen :(
[06:22] <psycho_oreos> to get out of man pages you press q
[06:23] <well_laid_lawn> man man tells that :]
[06:29] <eduardo> 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)Kernel modules: snd-intel8x0
[06:31] <eduardo> thank u well_laid_lawn and psycho_oeros I'll surely remember that when I'm trapped again... hehe ... q for "quit" ¿isn't it?
[06:31] <well_laid_lawn> yep :]
[06:33] <psycho_oreos> so it seems like there is a driver available, it might be muted
[06:34] <eduardo> :-) it's easier for Spanish speakers like me when we know some English and we make the association with the English words composing the command :-)
[06:35] <eduardo> you mean muted in the volume control ??
[06:36] <well_laid_lawn> or in alsamixer in terminal
[06:37] <tehC0unt> sup playaz
[06:38] <psycho_oreos> there's #ubuntu-es channel
[06:38] <well_laid_lawn> !en | tehC0unt
[06:38] <eduardo> there's an icon like a speaker, it says "mixer" (mezclador in Spanish)
[06:38] <tehC0unt> haha are you guys kidding
[06:38] <tehC0unt> i was just messing around
[06:39] <psycho_oreos> eduardo, there's #ubuntu-es
[06:39] <tehC0unt> guess ill leave
[06:41] <eduardo> eduardo@NOTEBOOKEDUARDO:~$ alsamixer "no se puede abrir el mezclador: No existe el archivo o directorio" can't open the mixer: there is no directory
[06:42] <psycho_oreos> try sudo
[06:44] <eduardo> I'm a translator and interpreter English - Spanish and my Specialty is computing... I rather to deal with this things in English, many translations I have found look like being done by automatic translators... hehe
[06:45] <eduardo> same output, "no directory"
[06:45] <eduardo> apt-get alsamixer??
[06:46] <well_laid_lawn> try   which alsamixer
[06:50] <eduardo> /usr/bin/alsamixer
[06:51] <well_laid_lawn> so you have it already
[06:51] <well_laid_lawn> in terminal what does   aplay -l   return?
[06:52] <eduardo> seemingly... but  it answers "no file or directory"
[06:55] <well_laid_lawn> ok - in terminal   lsmod | grep snd   - there will be lots hopefully if the first says intel that's fine
[06:55] <eduardo> may be it was not installed completely... sometimes my connection fails in the middle of an "upgrade"
[06:57] <eduardo> snd_intel8x0 25588 0
[06:58] <eduardo> snd_ac97_codec        100646  1 snd_intel8x0
[07:01] <eduardo> http://paste.ubuntu.com/473399/
[07:03] <well_laid_lawn> the first line is all that is needed :]
[07:05] <well_laid_lawn> try in terminal   cat /dev/urandom > /dev/dsp   - watch out it is loud - ctrl+c to stop it
[07:05] <eduardo> ok
[07:09] <eduardo> permission denied even with sudo first
[07:09] <well_laid_lawn> in terminal do   groups   and see if audio is listed
[07:12] <eduardo> ok
[07:13] <eduardo> eduardo adm dialout cdrom plugdev lpadmin admin sambashare
[07:13] <well_laid_lawn> no video or audio in there
[07:14] <eduardo> so I should add that??
[07:15] <well_laid_lawn> yep
[07:15] <well_laid_lawn> I would do   user -G video,audio
[07:15] <well_laid_lawn> I would do   useradd -G video,audio
[07:15] <well_laid_lawn> eduardo: ^^
[07:16] <well_laid_lawn> with sudo of course since it is a system setting
[07:16] <eduardo> with sudo first I suppose?
[07:16] <eduardo> hehe I was writing...
[07:16] <well_laid_lawn> :]
[07:17] <well_laid_lawn> then run   groups again to check
[07:17] <well_laid_lawn>    *
[07:19] <well_laid_lawn> oops - you have to log out and back in for it to take effect
[07:19] <well_laid_lawn> eduardo: ^^
[07:21] <eduardo> it answered with a "man" about the use of useradd
[07:21] <well_laid_lawn> :] k - one min
[07:23] <eduardo> useradd [options] USER
[07:23] <well_laid_lawn> sudo useradd -G video,audio eduardo
[07:24] <eduardo> so it would be sudo useradd audio,video eduardo or sudo useradd [audio,video] eduardo
[07:25] <well_laid_lawn> sudo useradd -G video,audio eduardo
[07:25] <eduardo> ok
[07:25] <well_laid_lawn> there's a -G in there to say add to groups
[07:26] <eduardo> oops "the user eduardo already exists"
[07:29] <well_laid_lawn> k
[07:34] <well_laid_lawn> eduardo: try   sudo usermod -a -G video,audio eduardo
[07:35] <eduardo> ok
[07:36] <eduardo> done ... back to the prompt without comments... did it worked then??
[07:37] <eduardo> why your name appears in red sometimes??
[07:37] <well_laid_lawn> doesn't yours?
[07:38] <well_laid_lawn> it is 'cause I used your nick eduardo
[07:38] <well_laid_lawn> :]
[07:38] <well_laid_lawn> !nick
[07:41] <eduardo> uff there's so much to learn...
[07:43] <eduardo> well I'm using the name of the owner of the laptop, my name is Patricio hehe
[07:44] <well_laid_lawn> heh
[07:46] <eduardo> should I restart the laptop before I do "groups" again?? it still gives me the same output than before
[07:48] <well_laid_lawn> or just logout
[07:54] <eduardo> Ok thank you I hope now it will work, ¿how do I register my nick in Freenode? (This time my name Patricio, and I'm won't change it again)
[08:01] <TheSheep> eduardo: http://freenode.net/faq.shtml#contents-userregistration
[08:30] <eduardo_> I have a Launchpad account ¿is it valid as a registration?
[08:31] <well_laid_lawn> not for in here - you need freenode registration
[08:31] <well_laid_lawn> but you don't have to register
[08:31] <eduardo_> ¿why not?
[08:32] <well_laid_lawn> if you register someone else can't use your nick
[08:32] <well_laid_lawn> if you don't they can
[08:33] <eduardo> see :]
[08:37] <eduardo_> I see... I have Joined a group of xubuntu users... https://launchpad.net/~xubuntu-users
[08:39] <well_laid_lawn> great - how did the sound go?
[08:45] <eduardo_> I'm going to restart now but before I'm going to save the chat in a text file in order to post the "solution" if it works out... there ae many questions about this topic in the forums, but none of those answers worked... and I will translate it too to help Spanish speaking users...
[08:49] <eduardo_> Bye I'll be back to give you feedback about the results...
[08:49] <well_laid_lawn> luck
[08:49] <eduardo_> thanks a lot
[09:22] <randhol> Hi. I have setup to autoimport photos from camera, that works great. However, I get asked if I want to import from SD card every time I turn on the printer-scanner as it has a SD card inside. Is there a way to remove this question? I only want to import fram cameras automatically
[09:22] <eduardo> !nick well_laid_lawn Bad luck with the final result but one more step close to the solution, now I have the permissions at least hehe
[09:27] <eduardo> tomorrow I  will try again the other instructions you gave me... thanks to your help I'm every time closer to solve this issue... thank you very much... now I'm going to sleep here in Chile is very late... 4:26 a.m. ... bye
[13:40] <heoa> cat *billion_fs.JPG  > many_fs.JPGs <--- how do you sort them?
[13:40] <TheSheep> heoa: what?
[13:41] <heoa> TheSheep: concatenated file with JPG-files. How do you separate them back to JPG-files?
[13:46] <TheSheep> heoa: you can write a short program that will look for the jpeg headers and split on them...
[13:50] <heoa> TheSheep: or I will just us "$ tar -cvf *.JPG" and then "$tar -xvf *.JPG", sounds less reinventing the wheel
[13:50] <heoa> err -xvf *.tar
[13:56] <TheSheep> definitely
[13:56] <TheSheep> and you also save the names
[13:59] <nexus6__> morning
[14:00] <nexus6__> is there a way to set the panels to default?
[14:01] <TheSheep> nexus6__: what do you mean?
[14:59] <pteague_work> awesome, i have no xorg.conf to modify to turn off the bloody touchpad while i type
[15:00] <TheSheep> pteague_work: why do you need to modify the xoeg.conf for that?
[15:01] <TheSheep> pteague_work: and you can just create it
[15:01] <TheSheep> (just be careful not to make typos like me ;) )
[15:02] <pteague_work> from various articles i'm looking at for turning the touchpad off it says i need to edit the xorg.conf & find the section for synaptics touchpad & then add `Option "SHMConfig" "on"`
[15:03] <heoa> how can i alter the "ctime" with touch? "$ touch -d '2010-08-06'" but no apparent relation to "$ find . -ctime +/-$NUMBER"
[15:04] <pteague_work> touch -t yyyymmddhhii.ss  ?
[15:05] <pteague_work> it changes the last modified time, but i'm not sure if it updates the node information
[15:14] <heoa> pteague_work: easy to check "$ ls -lc", no change to ctime
[15:15] <pteague_work> ctime is the node modified time right?
[15:15] <pteague_work> or creation time?
[15:16] <pteague_work> aha, found something i could do without needing xorg.conf... https://help.ubuntu.com/community/SynapticsTouchpad
[15:16] <heoa> pteague_work: yes, cretion time that seems to depend on fs, so some hardlinks may need mods
[15:21] <pteague_work> touch i think only modifies the filestamp which does update the mtime to the time that you modified the file >.<  there may be some fs tool that let's you modified c/mtime, but i'm not sure what would work
[15:38] <mmoebius> pteague_work: read 'man touch' -> mtime, atiome are selectable by options
[15:52] <nexus6__> why is the xubuntu channel so empty?
[15:53] <nexus6__> ubuntu 1600, xubuntu 70
[15:53] <vinnl> That's about the same ratio as the user ratio I'd say
[15:53] <charlie-tca> Because Xubuntu has fewer users
[15:54] <charlie-tca> We could use help increasing the user number, though.
[15:54] <charlie-tca> Let people know this is a good alternative to use!
[15:54] <nexus6__> i am a ubuntu beginner... but does ubuntu and xubuntu really differs that much?
[15:54] <charlie-tca> um, "this" = "Xubuntu"
[15:55] <charlie-tca> Ubuntu uses Gnome, Xubuntu uses Xfce, so yes, as far as the actual "what you see", it does
[15:55] <nexus6__> for the newbie it looks like only the GUI system is a different
[15:56] <charlie-tca> Behind the scenes, we are much lighter, too. Xubuntu uses fewer resources than Ubuntu does.
[15:56] <nexus6__> i heared abount lubuntu
[15:56] <nexus6__> did you try that?
[15:56] <charlie-tca> We also use different applications than Ubuntu
[15:57] <nexus6__> you mean the standard apps right? because in the software center i can dowload the same apps like on ubuntu
[15:57] <pteague_work> mmoebius, really? i just scanned it & didn't see that, but kind of busy at work ;)
[15:57] <charlie-tca> Ubuntu has OpenOffice, Rythmbox. Xubuntu has Abiword, Gnumeric, Exaile
[15:58] <charlie-tca> Yes, you can add the same apps, but the default apps are not the same
[15:58] <charlie-tca> I have not tried Lubuntu
[15:58] <pteague_work> ah, --time=(access|atime|use)
[16:05] <nexus6__> i use xp most of the time
[16:05] <nexus6__> windows xp
[16:07] <nexus6__> and actual i try to figure out myself if xubuntu can beat windows xp on performance
[17:26] <nikolam> khm. how to prevent applications from stealing window focus while typing?
[17:29] <charlie-tca> change the settings in Applications -> Settings -> Xfce4 Settings Manager -> Window Manager, focus and in Window Manager Tweaks, focus
[20:37] <crom> hi all,,,,,i need DUND....anyone knows where to get it?
[20:42] <crom> hi all,,,,,i need DUND....anyone knows where to get it?
[20:58] <slow-motion> hi
[21:05] <crom> hi
[21:48] <nexus6__> is there a german xubuntu channel?
[21:49] <charlie-tca> I don't know if there is german for Xubuntu itself, but there is german Ubuntu channel you could ask in...
[21:49] <charlie-tca> !german
[22:15] <xubuntu624> quit
[22:30] <cees> any helper here?
[22:39] <charlie-tca> !help
[23:46] <slow-motion> n8