[00:20] <ebroder> Anybody want to sponsor my fix for bug #435505?
[00:45] <slacker_nl> why do some packages have their version number in the package name, an upgrade of the package will actually remove/install package, if only the version number would change I would only see a normal upgrade, eg, libuniconf4.4 to libuniconf4.6
[00:47] <sistpoty> slacker_nl: (binary) library packages have the soname denoted in the package name
[00:47] <sistpoty> slacker_nl: the reason is to have these coinstallable (e.g. if another package still needs the old and incompatible library)
[00:47] <slacker_nl> sistpoty: ahh, isee
[03:05] <ebroder> Can someone from ubuntu-release look at bug #429445?
[03:06] <ebroder> I really don't believe that this needs an FFe, but it seems like it might be easier to just get one than to argue the point
[04:12] <geofft> has there already been some discussion and/or flamage about Launchpad redirecting +filebug to the wiki page?
[04:15] <geofft> I want this not to happen (at least for my account) but I'd rather not file a new bug if there's some existing forum
[05:00] <dtchen> libuniconf4.6 is failing to upgrade due to debian 540320, which is resolved in wvstreams 4.6-2
[05:01] <dtchen> (i.e., Karmic needs a sync of 4.6-2)
[05:01] <ScottK> Does wvstreams build?
[05:12] <dtchen> ScottK: yes, on both i386 and amd64
[05:12] <dtchen> i ran piuparts on a locally pbuilt sync of 4.6-2
[05:14] <ScottK> dtchen: If you file a sync request, I'll ack it.
[05:18] <jdong> hmm is asac on leave recently?
[05:22] <dtchen> ScottK: bug 441936
[05:24] <ScottK> dtchen: Ack'ed.  Thanks.
[05:25] <dtchen> ScottK: thanks
[05:27] <ScottK> You're welcome.  Thanks for looking into it.
[05:30] <foxbuntu> evening everyone, I am just doing a little research trying to understand where the jobs are for upstart to start xsplash, cant seem to find the information i am looking for, anyone able to point me to it?
[08:03] <hyperair> does anyone notice bash completion being a little broken in karmic?
[08:03] <hyperair> for example, when using mv, completing a filename multiple times doesn't appear to work.
[08:05] <hyperair> hmm specifically when there are spaces in the filename.
[08:05] <hyperair> it completes until "stuff_before_first_space\ " and then it stops
[08:09] <fabrice_sp_> hyperair, that's strange, because it's working here, even with spaces
[08:09] <hyperair> is it?
[08:09] <hyperair> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543982
[08:09] <hyperair> this is the bug i'm seeing
[08:10] <fabrice_sp_> it has just completed "test fabrice/prueba" without pb
[08:10] <hyperair> could you grep your .bashrc for /etc/bash_completion?
[08:10] <hyperair> the bug says that removing /etc/bash_completion from bashrc fixes the problem
[08:10] <fabrice_sp_> sure
[08:11] <fabrice_sp_> I don't have a /etc/bash_completion file on karmic :-)
[08:12] <fabrice_sp_> that would explain why it's working in my case
[08:12] <hyperair> ah
[08:12] <hyperair> i see
[08:12] <hyperair> also, only some commands seem to fail
[08:13] <hyperair> i think it's those that are overridden in /etc/bash_completion
[08:13] <cody-somerville> It works for me and I do have /etc/bash_completion
[08:14] <hyperair> in karmic?
[08:14] <cody-somerville> yup
[08:14] <hyperair> which command did you use?
[08:14] <hyperair> mv seems to fail
[08:14] <cody-somerville> cd
[08:15] <cody-somerville> mv works for me as well
[08:15] <hyperair> is it sourced in your bashrc?
[08:15] <hyperair> cd fails for me
[08:15] <cody-somerville> yes
[08:15] <hyperair> hmm how strange.
[08:16] <hyperair> did you type until the \ before pressing tab?
[08:16] <hyperair> or did you press tab before that?
[08:17] <cody-somerville> not sure I understand your question
[08:17] <hyperair> sorry.
[08:17] <hyperair> basically filenames with spaces are generally tab completed to: bla\ bla
[08:17] <hyperair> the completion fails if you type until "bla\ "
[08:17] <hyperair> and then press tab
[08:17] <hyperair> for me, that is
[08:17] <hyperair> and as mentioned in the bug report
[08:19] <cody-somerville> are you saying that if you type "mv blah\" and then hit tab that its not completing for you?
[08:20] <hyperair> note the trailing space.
[08:20] <hyperair> "mv blah\ "
[08:21] <cody-somerville> yea, that doesn't work for me either
[08:21] <hyperair> and that's what i meant.
[08:21] <hyperair> it worked previously
[08:21] <cody-somerville> try not typing the \ and just a space
[08:22] <hyperair> heh?
[08:22] <hyperair> then it'll be interpreted as the next argument already
[08:22] <hyperair> and also, i didn't type the \. bash did.
[08:22] <hyperair> if i've got files "blah blah" and "blah asdf" then typing "b" and pressing tab will bring you to "blah\ "
[08:22] <cody-somerville> hyperair, type also one letter of the next word and it will complete it
[08:22] <hyperair> after which completion afils.
[08:22] <hyperair> fails*
[08:22] <cody-somerville> and if bash does the \ for me, then it does work
[08:23] <hyperair> doesn't work for me =(
[08:24] <hyperair> http://pastebin.com/f1281dbd2
[08:24] <hyperair> and completion fails
[08:25] <cody-somerville> yea, that does appear to be broken
[08:26] <hyperair> i suspect the _filedir function in /etc/bash_completion broke somewhere between jaunty and karmic
[08:27] <hyperair> or _filedir_xspec?
[09:02] <hyperair> hmm looks like it's not bash-completion that broke, but bash changed
[09:59] <gp_will_be_back> hi
[09:59] <gp_will_be_back> is net conections manger fixed in karmic koala
[09:59] <gp_will_be_back> ?
[10:00] <gp_will_be_back> https://bugs.launchpad.net/network-manager/+bug/279384
[10:01] <gp_will_be_back> as per gnome bug page it works on gnome but due some custom patch by ununtu not working in ubuntu
[10:16] <hyperair> gp_will_be_back: it will be fixed. (asac said so) for now you can use the network-manager trunk ppa.
[10:16] <hyperair> it works there.
[10:17] <hyperair> oh wait, that, i'm not sure
[10:17] <hyperair> i was thinking about the wrong bug
[10:17] <hyperair> i don't think so, but the other way is possible
[10:24] <gp_will_be_back> what is that way ?
[10:25] <gp_will_be_back> manually edit /etc/network/interfaces ?
[10:25] <gp_will_be_back> ;-)
[10:26] <gp_will_be_back> also that ubuntu one thing NEVER works
[10:28] <gp_will_be_back> but ubunto one stuff  not crtical .....networking connections applet stuff is
[10:30] <gp_will_be_back> feature is there never works .....unbutu....going M$ way hehe ....i remember have same exp in kubuntu 9.04 .....network manager didnt work ..............i asked kde team they said custom ubuntu patch was to be blammed
[10:32] <gp_will_be_back> does it works in karmic koala kubutu now ?
[10:35] <gp_will_be_back> why doesnt ubuntu use stuff that works like wicd rather half boiled patches
[11:09] <disown> Any channels where you can ask questions related to app development on ubuntu?
[11:11] <ion> The channel for the library/editor/build system/whatever you’re interested of.
[11:13] <disown> ion: I would like to find some info on how to integrate packaging, installation and testing in a dev cycle. I'll try the apt channel then?
[11:13] <ion> #ubuntu-motu should help with packaging.
[11:14] <disown> thanks
[11:59] <Chipzz> 11:35 < gp_will_be_back> why doesnt ubuntu use stuff that works like wicd rather half boiled patches
[12:00] <Chipzz> how about you read the actual gnome bug report and stop twisting the facts?
[12:00] <Chipzz> the actual quote from the gnome bug report:
[12:00] <Chipzz> > Dec  2 20:26:47 xendor NetworkManager: <debug> [1228229807.892297]
[12:00] <Chipzz> > probe_modem(): Couldn't get caps
[12:00] <Chipzz> Modem probing in NM is a custom Ubuntu patch and not in NetworkManager itself.
[12:00] <Chipzz> Please file a bug in launchpad for your problem.
[12:01] <Chipzz> that comment refers to modem probing, and has NOTHING to do with assigning a static IP address
[12:04] <gp_will_be_back> it works in vanilla Gnome doesnt it ?
[12:05] <gp_will_be_back> there is already bug filled regarding static ip and still unassigned
[12:06] <gp_will_be_back> https://bugs.launchpad.net/network-manager/+bug/279384
[12:07] <gp_will_be_back> oh wait its assigned to gnome bug --->> https://bugzilla.gnome.org/show_bug.cgi?id=555626
[12:08] <gp_will_be_back> mean while i have un -installed  it and using wicd
[12:20] <directhex> dtchen, what would happen if an app disables pulse on startup, and tries to use alsa's "default" plug?
[12:22] <Chipzz> gp_will_be_back: no it doesn't
[12:23] <Chipzz> gp_will_be_back: state the comment in either the launchpad or gnome bug report which says it works in vanilla gnome
[12:24] <Vittor> juego de boxeo online http://www.kobox.org/kobox-fande-Nourine.html
[16:06] <Rocket2DMn> hey guys, bug 421221 affects the listing for Text Editor in ubuntu-docs, however there still seems to be some upstream discussion about it
[16:07] <Rocket2DMn> Is the plan to release with "gedit Text Editor" in Applications->Accessories, or is it going to be adjusted again before final Karmic release?
[16:07] <Rocket2DMn> Is there another bug open for the issue that I'm just not seeing?
[16:39] <freeflying> tested today's daily build, still found some acpi warning message when bootup
[17:38] <SystemR32> Hello
[17:38] <SystemR32> Please I need help
[17:39] <SystemR32> anyone here?
[18:02] <Aji-Dahaka> there is a fix on network-manager that has been committed via launchpad.  Are there any docs on how to build the stuff from launchpad?  I downloaded the patches via bzr and ran the rules file to get the source from git, but I'm kinda lost at that point
[18:02] <Aji-Dahaka> it looks like something will have to apply the patch files and then the build process is probably about the same as "usual"
[18:45] <Turl> hello, can anyone on a laptop confirm this? https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/442378
[20:43] <lucas> could someone "give-back" ruby1.9.1 on i386? it built everywhere else, so I'm pretty surprised it failed to build on i386.
[20:53] <siretart> lucas: the package seems to have been built fine: https://edge.launchpad.net/ubuntu/+source/ruby1.9.1/1.9.1.243-2/+build/1275487
[20:54] <siretart> lucas: btw, you should be able to retry builds by yourself (if you have upload priviledges for the package, that is)
[20:59] <cjwatson> foxbuntu: upstart doesn't start xsplash, which might explain why you're having trouble finding where it does. :-) I think it's started by the GNOME session
[21:56] <foxbuntu> cjwatson, thanks, I learned that last night :)
[22:19] <lamont`>  /usr/sbin/invoke-rc.d: 274: /sbin/runlevel: not found <-- is maybe sysv-rc missing a Depends: upstart-compat-sysv ?
[22:41] <cjwatson> lamont: upstart rather than upstart-compat-sysv. I'm going to upload a fix to a PPA first since I'm slightly wary of pre-depends cycles here
[22:41] <lamont> ok
[22:48] <lamont> cjwatson: fwiw, the new chroots differ from the old chroots in that rather than /etc/hostname having some random buildd host (wherever it was built), they now say 'INVALID' - there's a part of me that wants to add that host to /etc/hosts. :-(
[22:53] <cjwatson> lamont: they also differ in that apparently the debconf frontend is borked ...
[22:53] <cjwatson> (you have a bug about that)
[22:57] <lamont> ah, thanks
[22:57] <lamont> got a handy bug number?  if not, I'll go find it
[22:59] <cjwatson> lamont: bug 442480
[23:43] <james_w> what makes two people seemingly independently file bugs about being unable to eject CDs against D-Bus in two days?