[00:00] <Hopsa> ion: The application itself is nicely written and will be the control panel for all the gadmintools apps.
[00:00] <Hopsa> ion: http://mange.dynalias.org/linux/gadmin-control-panel/gadmin-control-panel-0.0.4.tar.gz
[00:01] <Hopsa> Nice to not have to write a password to open up the server control panels plus it saves space on the desktop etc
[00:02] <Hopsa> Some people like to know what it does and what its good for etc so i wrote that down: http://mange.dynalias.org/linux/gadmin-control-panel/screenshots/gadmin-control-panel-features.txt
[00:03] <Hopsa> ion: Checked the code ? / Made that partly in 2004 somewhere and finished it in 3 days now.
[00:04] <Hopsa> The hard part was sizing all images to fit and scale properly with eachother on the horizontal and vertical planes.
[00:10] <Hopsa> I have noticed that the gadmin-dhcpd icon looks like crap. Its a very early icon i made in gimp (With arrows as cables pointing downwards) and the computer icon is yellow and the screen is black. I have told upstream or downstream Debian in my case to let the original .png files be .png and not convert them to .xpm and loose resolution or just use the real .png files.
[00:11] <Hopsa> Well, i hope some of you enjoy the applications i made so far. Have a great time!
[00:13] <Hopsa> Dont hesitate to ask for help regarding any of the applications.
[03:24] <JontheEchidna> Could an archive admin please push muon 1.0.1-0ubuntu2 through approval queue please? It's in universe, and 0ubuntu2 fixes a missing dependency for the postinst script.
[03:57] <Hopsa> JontheEchidna: Ask them to update dhcpd3 to something remotely new as well.
[04:01] <pranay_09> hi, i have build an application , in java and i want to make a .deb package of it,where can i find instructions on how to do it?
[04:04] <persia> http://wiki.debian.org/Java/Packaging has some pointers that may be useful.
[04:05] <persia> If you're using ant, it's easiest.
[04:06] <pranay_09> persia, thanks
[04:36] <pranay_09> how do i know the JAVA_HOME and CLASSPATH?
[04:37] <pranay_09> i did gedit /etc/environment but didn't find them there
[04:40] <persia> You set the CLASSPATH you need to build.  You'll probably end up needing to list a few jars from your build-dependencies.
[04:40] <pranay_09> ok
[04:41] <persia> JAVA_HOME is tricky.  I've never had a good handle on it.  Try asking in #debian-java on OFTC (irc.oftc.org)
[04:54] <pranay_09> persia, i checked the link /usr/bin/java which pointed to some other link, and ultimately it's /usr/lib/jvm/java-6-openjdk/jre/bin/java  . I think this is correct?
[04:55] <persia> That works as long as you're using openJDK.
[04:56] <pranay_09> ya i have been using that only
[04:57] <pranay_09> any problem in it?
[04:57] <persia> Well, there's bugs :)  Also, some folks like gcj.
[04:57] <persia> Also it doesn't handle some architectures.
[05:04] <pranay_09> persia, ok, so what's the alternative?
[05:05]  * persia thought there was some smart JAVA_HOME path that did the right thing.
[05:06] <persia> Indeed: JAVA_HOME=/usr/lib/jvm/default-java
[05:06] <persia> http://pkg-java.alioth.debian.org/docs/tutorial.html has lots of useful bits.
[05:08] <pranay_09> so should i include this path in my /etc/environment file for JAVA_HOME?
[05:09] <persia> No.  You don't want JAVA_HOME set in /etc/environment
[05:09]  * persia doesn't remember why, precisely
[05:11] <pranay_09> ok, then that should be in the debina/rules file as shown in http://pkg-java.alioth.debian.org/examples/library-nodeps/ ?
[05:11] <pranay_09> *debian/rules
[05:11] <persia> Yep.
[05:12] <pranay_09> ok, thanks :)
[05:17] <JontheEchidna> (thanks to whomever pushed muon through)
[05:24] <pranay_09> persia, i have basically two java programmes, one is the gui and other has some code, and this requires a package called "spd-say" (no library) so which option should i go for in this page http://pkg-java.alioth.debian.org/examples/   it's not clear to me
[05:25] <persia> I'd probably use "Simple program using ant" for the gui, and "simple library using ant" for the code on which the GUI depends.
[05:26] <pranay_09> ok
[05:38] <pranay_09> persia, i have made both the programmes in netbeans 6.8 and under the netbeans folder i have the programme folder ,"Application" (which itself has sub-folders of build, src,nbproject,test,and files build.xml,and manifest.mf). Now in the given example of Simple programme using ant what should be the foo.jar file? and what's the usr/share/foo?
[05:47] <pranay_09> persia, ping
[06:11] <persia> pranay_09, Hrm.  I haven't worked with new code in netbeans for too long to be sure.  Sorry.  The folks in #debian-java can probably give better advice, but it will be quiet there for a couple more hours.
[06:12] <pranay_09> ok, :)
[06:30] <graphitemaster> this endless parade of joining channels is like a quest for the holey grail.
[06:31] <persia> What do you seek?
[06:32] <ebroder> No, no, no - the first question is "WHAT....IS YOUR NAME?"
[06:32] <graphitemaster> a developer of ubuntu :P
[06:32] <graphitemaster> oh right, Dale
[06:32] <KE1HA> graphitemaster:  when you joined the channel, looks the links it listed, there's allot of info there about the teams.
[06:32] <persia> IRC handles that question :)
[06:32] <persia> So, why do you seek a developer of Ubuntu (there are many here)?
[06:38] <pitti> Good morning
[06:38] <pitti> cnd: mtdev> argh, why is this so resilient? I promoted it twice now
[06:40] <pitti> cnd: ah, it's probably because the binaries are out of date; promoting again
[06:40] <graphitemaster> I want to join the dev
[06:43] <KE1HA> Just FYI, that fella graphitmaster wanting to join, just got banned from ubuntu channel.
[06:43] <graphitemaster> yeah after I was about to explain what the bash does.
[06:43] <graphitemaster> never give me time to explain, and not run it, just make me look like some bad person :/
[06:44] <KE1HA> Dude, it's a fork bomb, they know it, you know it, get over it.
[06:44] <graphitemaster> the ban was kinda dumb
[06:45] <graphitemaster> it's not like I told them to run dd if=/dev/sda of=/dev/zero
[06:45] <graphitemaster> or rm -rf /dev/sda
[06:45] <graphitemaster> it's a forkbomb, the worst it does is crash the pc
[06:45] <graphitemaster> and a properly configured linux should not crash from a fork bomb
[06:45] <KE1HA> There's allot of new users in that channel, they dont need that kind of help, they have enough troubles as it is. That's all I have to say.
[06:46] <ebroder> Guys, this is off-topic for this channel
[06:57] <pitti> you know, rm -rf /dev/sda causes no noticeable damage :)
[06:58] <pitti> and cat'ing /dev/sda to /dev/zero even less so
[06:58] <graphitemaster> ptti dd if=/dev/sda of=/dev/zero causes a lot of damage
[06:58] <persia> Just makes the machine sit on IO for a bit.
[06:58] <pitti> graphitemaster: like, eating some I/O resources?
[06:58] <RAOF> graphitemaster: You've got if and of around the wrong way.
[06:58] <graphitemaster> oopsy :P
[06:58] <pitti> or are you afraid of filling up your zero device?
[06:59] <persia> No.  That's definitely the right way.  the other would be unfortunate.
[06:59] <pitti> you can buy a new one for $10 or so
[06:59] <pitti> (and get a bigger one while you are at it)
[06:59] <RAOF> persia: Well, if he wants to cause a lot of damage he's got them around the wrong way ;)
[06:59] <ebroder> Depends on whether you're testing read or write performance!
[06:59] <RAOF> pitti: Do you have a lucrative sideline selling /dev/zero devices? :)
[06:59] <persia> pitti, A bigger zero device?
[06:59] <graphitemaster> /dev/urandom is better
[07:00] <pitti> RAOF: get a 2 TB SSD one, it rocks! but *shhhh*
[07:00] <pitti> persia: yeah, got fed up of -ENOSPC on dd'ing to /dev/zero :)
[07:00] <RAOF> pitti: Can I get a desktop-team discount from you? :)
[07:00] <pitti> RAOF: they come in pairs with null devices, too
[07:00] <persia> Wow.  I always used a grounding wire.  hadn't thought about buffering.  Way to reduce entropic decay!
[07:03] <graphitemaster> so the LTS releases means more time for parties for you guys or what?
[07:41] <ttx> Hopsa: dhcp 4.x was in debian experimental until July 2010 (package is called isc-dhcp). The dhcp3 package tracks the 3.x series. We mostly follow Debian there. We'll get isc-dhcp in universe for Natty Narwhal
[07:42] <ttx> Not exactly sure what the plans for transition would be. That's part of the minimal seed, so it's mostly a question for the Foundations team.
[08:04] <persia> Could someone give-back nautilus on amd64?  I get no "implicitly converted" messages in a local build on amd64. : https://launchpad.net/ubuntu/+source/nautilus/1:2.31.90-0ubuntu2/+build/1935864
[08:05] <dholbach> persia, retried it
[08:05] <persia> dholbach, Thanks.
[08:21] <pitti> persia: converted pointers? that's an additional check that the buildd does
[08:21] <pitti> persia: it only manifests as warnings usually
[08:21] <pitti> but try to build with -Werror, then you should get the same
[08:22] <persia> Ah, ugh.  Oh well.  nautilus needs help then.
[08:22] <persia> I did some greps on my build-log, hoping to catch them, but didn't see any.
[08:25] <geser> could someone please give-back php5 on amd64? libsnmp-dev is installable again. thanks
[08:26] <persia> You beat my test build :p
[08:26] <persia> https://launchpad.net/ubuntu/+source/php5/5.3.3-1ubuntu6/+build/1934201
[08:34] <pitti> geser: kicked
[08:55] <pitti> cnd: doing some binNEWing for the utouch stuff, should help more
[10:03] <G> whats the policy for creating an SRU candidate if the package has no patch system, should I add the patch system used in newer releases or use someother patch method?
[10:04] <G> I'm assuming just implement the patch system used in maverick but I just want to be sure
[10:04] <persia> Generally one tries to use the patch system preferred by the maintainer.  that one was added in maverick makes that a good choice.
[10:05] <G> persia: cool, was just checking :)
[10:05] <G> thanks
[10:05] <persia> If there's no obvious choice, the patch is typically carried directly in diff.gz or debian.tar.gz
[10:05] <G> persia: okay then, thanks
[10:28] <mvo> Riddell: I fixed bug #624599 in u-m, testing now, a rather silly bug on my part :/
[10:50] <DktrKranz> mvo: gdebi upload in Debian would require a python-apt one too, do you know if it's planned?
[10:50] <DktrKranz> (and if it can migrate into Squeeze?)
[10:52] <mvo> DktrKranz: the new version is in debian already, no? the new python-apt I mean, got uploaded yesterday iirc
[10:53] <mvo> DktrKranz: and it should be fine for squeeze
[10:54] <DktrKranz> mvo: oh, I probably missed that
[10:54] <mvo> DktrKranz: np, might not have hit all mirrors yet or something like this
[10:55] <DktrKranz> I'll see whether both can migrate
[10:55] <DktrKranz> I owe some favours from some RT guys ;)
[10:56] <mvo> heh, cool :)
[10:56]  * mvo hugs DktrKranz
[10:56] <persia> Could someone please give back gnome-games/powerpc?  It builds now : https://launchpad.net/ubuntu/+source/gnome-games/1:2.31.90-0ubuntu1/+build/1921729
[10:58] <pitti> persia: kicked (not that you couldn't do that yourself, but always happy to do a favor)
[10:59] <persia> pitti, I don't believe I can.  Mustn't one be core-dev?
[10:59] <persia> And thanks :)
[10:59] <pitti> oh, you aren't?
[10:59] <persia> No.
[10:59] <pitti> then that is the bug :)
[10:59] <pitti> so, sorry for the false statement
[10:59] <persia> heh.  I'm currently working on main stuff to meet my own criteria, and will try to change that.
[11:00] <cjwatson> anyone who can upload a package can retry builds for it
[11:00] <cjwatson> AFAIK
[11:00] <persia> That matches my understanding
[11:00] <cjwatson> oh yes, and gnome-games is in main
[11:04] <pitti> cjwatson: right, I just falsely assumed that persia had been a core dev for ages
[11:08] <tjaalton> pitti: hey, are you still tending cups? I filed bug 612578 couple of weeks ago, and would like to know what to do next
[11:09] <pitti> tjaalton: I'm not usually reading bugs, tkamppeter does a fine job of it
[11:10] <tjaalton> pitti: ok. tkamppeter ^^
[11:10] <pitti> tkamppeter: "cached IPPs"? you mean auto-discovered printers?
[11:10] <tjaalton> pitti: no, they are all in the printers.conf
[11:11] <tjaalton> but the ipp's get recreated after a purge & restart
[11:11] <tjaalton> and they work fine for a while
[11:21] <G> kirkland: if/when you are around in the next few hours, could you ping me about testing https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/589063 and getting it ready for a potential SRU
[11:54] <G> is it me or does the owner for qemu-kvm look wrong?
[11:54] <persia> owner?
[11:54] <G> https://launchpad.net/ubuntu/+source/qemu-kvm
[11:57]  * persia doesn't see "owner" on that page
[11:58] <G> errr sorry, meant Maintainer
[11:58] <persia> no, that's correct.
[11:59] <persia> There are no individual maintainers in Ubuntu.  Collaboration is a key component of our philosophy.
[12:02] <G> so there is a difference between "Ubuntu Developer Team" and "Ubuntu Developers"?
[12:02] <persia> Could someone please give-back libgweather/powerpc and libunique/powerpc?  https://launchpad.net/ubuntu/+source/libgweather/2.30.2-1ubuntu1/+build/1915522 https://launchpad.net/ubuntu/+source/libunique/1.1.6-1ubuntu3/+build/1914222
[12:03] <G> (i.e. the 'Maintainer' for qemu-kvm & packagekit)
[12:03] <persia> Probably just someone typing something slightly different for Maintainer.  We probably ought clean it up, but it's never been a priority.
[12:04] <G> ahhh okay, yeah, was just curious
[12:07] <sistpoty|work> persia: given back (I still love that button *g*)
[12:07] <persia> sistpoty|work, Thanks !
[12:09] <ogra> can someone let u-boot-linaro out of NEW please
[12:09] <ogra> we need the omap4 binary for omap4 images
[12:12] <tkamppeter> pitti, tjaalton, this seems to be a completely new problem. It seems that a new feature (not known which one) in CUPS has torn down other parts of CUPS, as usual.
[12:13] <G> btw, I take it as we are in FeatureFreeze there is no real use of doing Merge requests, or does that not apply to Universe?
[12:14] <tjaalton> tkamppeter: "as usual"? :)
[12:15] <persia> G, Depends on the merge.  http://qa.ubuntuwire.com/bugs/rcbugs/maverick/ has a rich set of potentially useful merges in need of review.
[12:16] <cjwatson> G: it shouldn't be a priority simply because it's a merge; if it's a priority, it should be because it fixes a bug
[12:17] <tjaalton> tkamppeter: I could try backporting the maverick version (1.4.4) and see what it feels like
[12:17] <G> persia: so the ones on that list are the ones that are most important to do
[12:17] <tkamppeter> tjaalton, pitti, CUPS has a cache in /var/cache/cups/. Here it caches things like list of available PPDs and also the remote printers discovered automatically via IPP. Looks like a bug in the writing of the info into the cache or the readback out of the cache, so that wrong info gets supplied if CUPS relies on the cache, but CUPS has correct info if it obtains it directly.
[12:18] <tkamppeter> tjaalton, good idea, perhaps it got fixed.
[12:18] <persia> G, No.  The ones on that list are packages where Debian fixed a bug that Debian declared Release Critical.  In many cases, Ubuntu needs to fix the same bug, and can use the solution from Debian.
[12:18] <persia> The nice thing about that list is it includes bugs *AND* potential solutions, as opposed to many other sources of important bugs, that may not come with solutions.
[12:19] <tkamppeter> tjaalton, with the "as usual" I mean that it often happens that if a new feature gets added in a new version, regression bugs occur.
[12:19] <tjaalton> tkamppeter: ah, ok
[12:57] <cnd> pitti, thanks, I'm starting to see some packages now :)
[12:59] <cnd> pitti, can you restart xserver-xorg-input-evdev now that utouch-grail is built?
[13:40] <pitti> cnd: retried
[13:50] <tjaalton> tkamppeter: bah, build failed: http://pastebin.com/YzBRjWtv
[13:50] <tjaalton> tkamppeter: i'll try to work around it on monday
[13:56] <cnd> pitti, looks like evdev failed becausee it couldn't find libutouch-grail-dev
[13:56] <cnd> does that need to be newed as well?
[13:57] <pitti> cnd: nothing utouchy in https://edge.launchpad.net/ubuntu/maverick/+queue?queue_state=0
[13:58] <cnd> pitti, http://launchpadlibrarian.net/54494596/buildlog_ubuntu-maverick-amd64.xserver-xorg-input-evdev_1:2.3.2-6ubuntu1_FAILEDTOBUILD.txt.gz
[13:58] <cnd> maybe it just needs more time?
[13:58] <pitti> libutouch-grail-dev | 1.0.11-0ubuntu1 |      maverick | armel, i386, powerpc
[13:58] <pitti> libutouch-grail-dev | 1.0.11-0ubuntu1 | maverick/universe | amd64
[13:58] <pitti> cnd: right, seems the amd64 one came too late and was mis-NEWed
[13:58]  * pitti promotes
[13:59] <cnd> ok
[13:59] <cnd> thanks for looking into it
[13:59] <pitti> cnd: nice timing, 4 mins before publisher
[13:59] <pitti> so, we can retry that one in an ohur
[13:59] <cnd> heh
[13:59] <cnd> k
[14:19] <amikrop> Hi, is there an available update for fixing this https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139 ?
[14:19] <amikrop> Or will you wait for 10.10?
[14:22] <cjwatson> amikrop: nothing yet, it's in my queue.
[14:23] <cjwatson> (asking here won't make it happen faster)
[14:24] <amikrop> cjwatson: OK. (That was not my purpose, anyway, in the first place). Thank you.
[14:28] <ogra> cjwatson, remind me (i always forget since i do it so rarely) changing platform.maverick/supported-hardware-common will be automatically picked up with the next publisher run, right ?
[14:30] <cjwatson> immediately - it's not in a task
[14:31] <ogra> k
[14:31] <ogra> so i just have to wait for jdstrand to get up and let the package out of new :)
[14:40] <hallyn> Daviey: around?
[14:40] <Daviey> hallyn: sadly :)
[14:41] <hallyn> Daviey: i added a quilt patch to xlc which wasn't using quilt before
[14:41] <hallyn> Daviey: should i only have to add 'include /usr/share/quilt/quilt.make
[14:41] <hallyn> to debian/rules?
[14:42] <hallyn> and then the patch should get applied during build?
[14:42] <hallyn> or is there more todo?
[14:42] <Daviey> hallyn: hmm.. what package is this?
[14:42] <hallyn> (like call dh_patch)
[14:42] <hallyn> Daviey: https://launchpad.net/~serge-hallyn/+archive/lxc-lucid-lazyumount
[14:46] <hallyn> Daviey: there is no 'build:' rule in debian/rules...
[14:46] <hallyn> does there have to be?
[14:46] <Daviey> hallyn: just looking at your PPA package source
[14:46] <Daviey> hallyn: There is a commented out dpatch include, right?  That is from upstream Debian?
[14:47] <hallyn> yes it is
[14:47] <cjwatson> lxc uses cdbs, so you need to use cdbs-appropriate patch handling
[14:47] <cjwatson> (not disagreeing with Daviey - just to explain why /usr/share/quilt/quilt.make won't cut it)
[14:47] <cjwatson> cdbs supplies the build: rule
[14:48] <hallyn> cjwatson: ok, that was the first q:  *does* quilt.make cut it :)
[14:48] <Daviey> hallyn: I might suggest using dpatch (although i prefer quilt, and it's a defacto standard) submitting it to debian would be easier if you follow upstreams preference
[14:48] <jdstrand> ogra: hey. I haven't looked at it yet, but how will this kernel impact beta?
[14:48] <hallyn> so dpatch will apply the quilt patches though?
[14:48] <ogra> jdstrand, kernel ?
[14:48] <ogra> jdstrand, i only need u-boot-linaro :)
[14:48] <Daviey> hallyn: dpatch is an equivilant patch system
[14:48] <hallyn> ok, thanks cjwatson and Daviey
[14:48] <ogra> jdstrand, especially the omap4-panda binary
[14:48] <hallyn> that explains why mypatch didn't fix it :)
[14:48] <Daviey> hallyn: hope that helps :)
[14:48] <jdstrand> ogra: oh, heh. I just assumed it was a kernel since it seems I always have an arm kernel on fridays :)
[14:49] <ogra> heh
[14:49] <cjwatson> if you wanted to use quilt, you would need to include /usr/share/cdbs/1/rules/patchsys-quilt.mk instead, but I agree it's better to go with what's already in debian/rules - use dpatch-edit-patch to create the patch file
[14:50] <hallyn> cjwatson: well i don't care what it uses to stack the patches, so long as it is using quilt format
[14:50] <cjwatson> why does it need to use quilt format?  as Daviey points out, submitting it to Debian will be easier if you use the patch system that the Debian maintainer seems to prefer
[14:51] <cjwatson> dpatch has its own format - it's still basically a patch, just different wrapping
[14:51] <Daviey> +1
[14:52] <cjwatson> everyone has their own preferences, but when working on existing packages it's best to fit in
[14:52] <hallyn> trying...
[14:52] <hallyn> Daviey: heh, I'd reserve my +1 for cdbs using git, but...
[14:55] <Daviey> hallyn: Opening a whole can of religious worms there :)
[14:55] <hallyn> Daviey: so, apart from opening the resulting binary in a dissassembler,
[14:55] <hallyn> is there any way for me to tell if i now have it right???
[14:55] <Daviey> hallyn: he build log, should show the patch being applied
[14:55] <hallyn> the build log for the binary build, but not for the source build?
[14:56] <Daviey> If you really want to see if the patch is applied, i guess you could experiement with adding a string change that is viable.. then remove it before upload? :)
[14:56]  * hallyn figures he'll brush up on his assembly reading skills, it's been af ew months by now
[14:57] <Daviey> hallyn: The source package should normally not have the patch applied for debian/patches/ packages.
[14:58]  * Daviey has been spoilt, mainly working with debian source package 3 packages this cycle.
[14:58] <hallyn> Daviey: oh well, it appears to *not* be being applied during binary build :(  back to the cdbs docs.  thanks.
[14:58] <Daviey> hallyn: edit-patch is a pretty nifty tool, i don't know if you've tried that yet?
[15:04] <diwic> hmm, any ideas why I can't find the correct Lucid version (1.0.22-0ubuntu5) of alsa-utils-dbgsym on ddebs.ubuntu.com?
[15:10] <tkamppeter> tjaalton, please contact pitti about your build problem. He did the symbol table stuff.
[15:26] <hallyn> Daviey: yeah, edit-patch was kinda fun to use  :)  (the end-result isn't the prettiest patch, but the build environment was cool)
[15:32] <Daviey> hallyn: yeah.. i think there is an open bug about using it with a VCS, it doesn't give you a chance to edit the patch boilerplat headers before promting you to commit
[15:33] <Daviey> but just hacking on the code, typing exit.. and getting a patch is really awesome.
[15:37] <hallyn> ttx: mathiaz: I can't remember, did either of you say you'd tried out rememberthemilk.com?
[15:37] <ttx> hallyn: I'm using it
[15:37] <mathiaz> hallyn: ttx is
[15:37] <ttx> hallyn: mathiaz used to use it.
[15:38] <mathiaz> hallyn: I tried it a couple of years ago as well
[15:38] <hallyn> (the mapping feature is making me think it's worth a try :)
[15:38] <mathiaz> hallyn: SpamapS is also using it IIRC
[15:38] <hallyn> ttx: and you still like it?
[15:38] <hallyn> mathiaz: why did you stop?
[15:38] <mathiaz> hallyn: required to be online
[15:38] <hallyn> (I'm using ubuntu one mainly, but i guess i feel like "mixing it up" a bit :)
[15:38] <ttx> hallyn: yes, I had to trick it though :) but its flexibility allows for it
[15:39] <ttx> hallyn: http://fnords.wordpress.com/2010/01/25/gtd-with-rtm/
[15:39] <hallyn> oh, right, so i tried to login last night for the first time an di t wanted javascript :)
[15:39] <hallyn> ttx: will read that, thx
[15:40] <ttx> hallyn: also allows nice tricks like http://bazaar.launchpad.net/~ttx/%2Bjunk/scripts/annotate/head%3A/gtd
[15:40] <ttx> hallyn: I slightly evolved my setup since that article
[15:41] <ttx> hallyn: let me know if you want to go further in that direction
[15:41] <ttx> mathiaz: I use my iPod touch RTM app for offline work :)
[15:42] <hallyn> i'll have to see if there's an n900 app
[15:42] <bigon> slomo: hi, any reason you removed gir on libgee in debian? http://packages.qa.debian.org/libg/libgee.html
[15:43] <slomo> bigon: yes, to do it properly there has to be a package for the typelib too and i don't want to add new GI packages to anything until their ABI is stable
[15:43] <bigon> mmm could you add it in experimental? I really need it
[15:44] <slomo> no, it doesn't make sense to go through NEW only to go through NEW again in 2-3 weeks
[15:44] <bigon> again?
[15:45] <bigon> empathy need folks that need libgee and I really want to upload it in experimental
[15:45] <slomo> bigon: yes, GI ABI changes... i won't touch any GI packaging stuff until it's really declared as stable and they use correct versioning (i.e. change the version in the paths and stuff when changing the ABI)
[15:46] <bigon> mmm ok
[15:46] <bigon> let's see if I can build folks without introspection
[15:46] <slomo> the situation is simply unacceptable as it is now *shrug* also, which version of GI do you need to folks?
[15:48] <bigon> 0.6.7 I think
[15:56] <cjwatson> doko: I can't seem to reproduce the configure test failure in bug 601030
[15:57] <cjwatson> doko: can you check whether it's still failing in the current test rebuild (I don't have the necessary URLs to hand) and post a build log URL?
[15:59] <doko> cjwatson: ok, will do. is there a test rebuild running?
[16:00] <cjwatson> doko: AFAIK you're the only one who's been doing test rebuilds of late
[16:07] <smoser> cjwatson, ping. re bug 623609. I think that if I could seed: 'grub-pc grub-pc/install_devices multiselect NONE' or something like that to indicate "dont bother installing bootloader", I would be good.
[16:09] <smoser> that would fix all the uec situations. but for ec2 i still need to work around grub-probe not functioning.
[16:38] <G> kirkland: unping, I'm just going to update the bug if you could take a look at it when you've got a chance (589063)
[16:39] <superm1> pitti, cjwatson; sigh, still hitting the hash sum mismatch on today's (http://people.canonical.com/~ubuntu-archive/cd-build-logs/mythbuntu/maverick/daily-live-20100827.log). can one of you manually rerun so that we could produce an image to regress the new ubiquity from yesterday?
[16:39] <pitti> I'll trigger a new build
[16:40] <pitti> running
[16:43] <superm1> thanks
[17:21] <ogra> jdstrand, anything holding up u-boot-linaro ? anything i can do ?
[17:22] <jdstrand> ogra: no, just got tied up. I'll do it now
[17:23] <pranay_09> hi, is the language option in spd-say package not active?
[17:23] <ogra> jdstrand, thanks a lot
[17:24] <pitti> superm1: http://cdimage.ubuntu.com/mythbuntu/daily-live/20100827.1/
[17:25] <pranay_09> i mean i tried to change the language as spd-say -s -l it "Hello" but i hear it in english only
[17:25] <superm1> pitti, great thanks! and finally these images aren't oversized too :)
[17:26] <pitti> superm1: I guess it also picked up the OO.o fix now?
[17:26] <pitti> ah, no OO.o on there
[17:26] <superm1> pitti, well i committed a  bunch of fixes like 4 days ago, but haven't been able to see if they fixed it
[17:26] <superm1> mostly pool/ stuff
[17:26] <pitti> ah
[17:30] <pitti> lifeless, james_w: wow, vcs imports in LP are really awesome these days! Just tried th "import now" button, and I can watch it getting updated
[17:30] <pitti> kudos!
[17:30] <pranay_09> well it's working for some language codes
[17:31] <ogra> pitti, could you promote u-boot-linaro now that the binaries are out of NEW ? MIR is at bug 613230
[17:32] <pitti> ogra: oh, it's literally called "u-boot"? I thought its name was "uboot"
[17:33] <pitti> ogra: source promoted
[17:33] <ogra> pitti, upstream calls it "das u-boot" :)
[17:33] <ogra> no idea how they got to that :)
[17:35]  * pitti promotes binaries to main in the  accepted queue
[17:35] <pitti> u-boot-linaro-ca9x4-ct-vxp_2010.06-695-gbd23130-linaro-0ubuntu1
[17:35] <pitti> what a package name!
[17:35] <ogra> hehe
[17:35] <ogra> blame slangasek
[17:36] <ogra> i think he made that up
[17:36] <pitti> "I need a package name". "Lets put my cat on the keyboard and see what she comes up with"
[17:36] <slangasek> hey now
[17:37] <ogra> lol
[17:37] <slangasek> I didn't name it, I would've left the 'linaro' out of the package name ;)
[17:38] <pitti> ogra: is the u-boot-omap4 task relevant? the package already produces a u-boot-linaro-omap4-panda binary, after all?
[17:38] <pitti> the maverick task is "wontfix", but I'm not clear whether we need a separate source at all now
[17:38] <ogra> pitti, i want to recycle the bug for u-boot-omap4 rempoval request later
[17:39] <ogra> we wont need it anymore if the linaro one works
[17:40] <ogra> that bug evolved quite a lot ... its started with a breakage of u-boot-omap4 the research showed that the old source we have from TI is unfixable and the the linaro one has no such issues which produced the other task
[17:40] <ogra> then we turned it into a MIR :)
[17:40] <ogra> and if the build sctipts are changed i'll turn it into a removal
[17:44] <pitti> ogra: so, want me to remove u-boot-omap4?
[17:46] <ogra> pitti, only after i changed the build scripts ... and i need a break first
[17:47] <pitti> ogra: ok; don't worry, just asked if I should clean that up, but it's not that urgent
[17:47] <ogra> ok
[17:58] <cnd> pitti, I just did a apt-get update, but libutouch-grail1 amd64 still seems to be in universe
[17:59] <cnd> should it be in main by now?
[18:14] <james_w> pitti: nothing to do with me :-) jelmer and the launchpad-code and bzr teams did that
[19:23] <SpamapS> anybody know a simple way to tell that a conffile has been changed or not?
[19:26] <soren> SpamapS: Well, it's neither simple or elegant, but grepping for the conffile's name in /var/lib/dpkg/status gives you the md5sum of it at install time. You can use that for comparison.
[19:26] <SpamapS> soren: I want something I can ask a user to do (so I can see if they've editted it...)
[19:27] <soren> SpamapS: Ah.
[19:42] <lanoxx> is a lock-file considered a cache-file? xdg_spec wise
[20:32] <ScottK> doko: Is there an approved FFe somewhere for dehydra?  There isn't one referenced in debian/changelog.
[20:34] <doko> ScottK: yeah, I know, one day late. I assume I have to write one
[20:34] <ScottK> doko: Feature freeze was last week, so a week and a day.
[20:34] <doko> ok, ok
[20:59] <glickster> i dont get it mod-wsgi 2.8 has major bugs in it, why wont ubuntu upgrade it to 3.2 in lucid?
[21:00] <ScottK> glickster: We virtually never do major version upgrades post release.  It might be suitable for backports though.
[21:00] <ScottK> !backports | glickster
[21:33] <doko> ScottK: https://bugs.edge.launchpad.net/ubuntu/+bug/625532
[22:11] <steve|m> hmm, gcalctool crashes with a Segmentation Fault when entering 26^160
[22:15] <Neo--> hey guys, anyone knows when do we get to know whether or not our UDS sponsorship request had been approved or denied?
[23:05] <chrisccoulson> hi, is someone able to approve firefox-3.6.9 for me please?
[23:10] <sistpoty> chrisccoulson: the release-team tried to hide so far from reviewing (me included :P)
[23:10] <chrisccoulson> heh ;)
[23:11] <ScottK> able != willing
[23:25] <cjwatson> I realise it's a bit late, but merges.ubuntu.com should be working again now (thanks to some advice from Keybuk on safe ways to free disk space)
[23:26] <Hopsa> cjwatson: Are there any bugs filed againt dhcpd3 ? Its giving me a segfault on Lucid. "Invalid read of size 4"
[23:29] <Hopsa> cjwatson: Whatever i do to the configuration it segfaults and it doesnt do that on any other of the dists i use.
[23:29] <ScottK> cjwatson: That's good news.  There's one bugfix merge I've been procrastinating because manual merge would be painful.
[23:29] <Hopsa> Its a whole mayor version behind schedule
[23:30] <Hopsa> Remove patches and release a newer binary.
[23:32] <Hopsa> Also: I noticed that Firefox stopped working on Ubuntu 8.04. -safe-mode would only show a the clear cookies etc things and then it would leave a zombie Firefox.
[23:33] <Hopsa> Its got something to do with ns_loginit()
[23:34] <Hopsa> Switching xulrunners made no difference and reinstalling firefox did likewise
[23:37] <cjwatson> Hopsa: it's not usually a good plan to grab the last person who happened to talk in the channel in the assumption they'll know ;-)
[23:38] <cjwatson> "Remove patches and release a newer binary" <- no, patches would have been there for a reason, it requires slightly more checking than that particularly in a stable release
[23:38] <cjwatson> but I know very little about that package in particular
[23:39] <Hopsa> I know that dhcpd should never need to be segfaulting. Please check this.
[23:40] <Hopsa> It does this on startup for me on Lucid with all current updates
[23:40] <cjwatson> I'm afraid I have too much else to do right now
[23:40] <cjwatson> please simply file a bug
[23:40] <Hopsa> So servers are not a priority. hmm..
[23:41] <cjwatson> huh?
[23:41] <cjwatson> not my priority != not Ubuntu's priority
[23:42] <cjwatson> I personally do not do much server work
[23:42] <cjwatson> this is why you generally shouldn't try to grab people personally on IRC until you're quite familiar with the project, but instead go through the bug tracking system
[23:42] <Hopsa> So ubuntu will only care about desktop things like openoffice and stuff ?
[23:42] <cjwatson> non sequitur
[23:42] <cjwatson> you asked me personally
[23:43] <cjwatson> I do installer and bootloader stuff
[23:43] <penguin42> Hopsa: People care about servers, there is a #ubuntu-server I think
[23:43] <Hopsa> Felix sit annus noctus
[23:43] <Hopsa> Oh, thanks penguin42 !
[23:43] <penguin42> Hopsa: It's just some people deal with different bits of stuff and the people who know about your problem might not be around
[23:43] <penguin42> Hopsa: File a bug against the package and they'll get told
[23:48] <Hopsa> penguin42: Thank you for your help. Ill keep an eye out for people in the know.
[23:50] <chrisccoulson> Hopsa, rather than "keeping an eye out", you should just file a bug on launchpad
[23:51] <Hopsa> chrisccoulson: No, id rather get a hold of persons in the know. But thank you.
[23:51] <chrisccoulson> hmmm, that's not the way to do it. imagine if every user did that? it would be chaos. the bug tracker exists for a reason
[23:52] <penguin42> Hopsa: File the bug anyway, it'll collect a load of stuff and backtrace and stuff which if you are lucky to find someone (which may be rare) it'll help them
[23:54] <Hopsa> penguin42: I need the unstripped libs for dhcpd to do so. How can i install those ?
[23:55] <penguin42> Hopsa: You can file the bug anyway - just run  ubuntu-bug dhcpd (or whatever the package is called)
[23:55] <chrisccoulson> well, you don't need them if you use apport. however, you can find the information you need here: https://wiki.ubuntu.com/DebuggingProgramCrash
[23:55] <chrisccoulson> (which you would have been told by someone else if you reported a bug)
[23:56] <Hopsa> Nope, i need to get the debug info or i cant pinpoint the error. Im developing stuff etc on Ubuntu and most other dists.
[23:58] <chrisccoulson> ok, so you sound like you don't really need any help then


[10:00] <chrisccoulson> hi, any chance of someone taking a quick look at https://answers.launchpad.net/launchpad/+question/653688 ? Sorry, I don't want to seem like a pain, but I'm kind of blocked
[10:01] <wgrant> chrisccoulson: Done
[10:01] <chrisccoulson> wgrant, awesome, thanks!
[19:24] <muktupavels> https://code.launchpad.net/~ubuntu-gnome-flashback/+archive/ubuntu/daily-builds/+recipebuild/1421174
[19:24] <muktupavels> why it fails on artful?
[19:29] <tsimonq2> dpkg: error processing package tex-common (--configure):
[19:29] <tsimonq2>  subprocess installed post-installation script returned error exit status 1
[19:29] <tsimonq2> Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-3) ...
[19:29] <tsimonq2> Errors were encountered while processing:
[19:29] <tsimonq2>  tex-common
[19:29] <tsimonq2> muktupavels: That's why.
[19:29] <muktupavels> is that problem with package?
[19:29] <muktupavels> It builds on zesty
[19:29] <tsimonq2> Yes.
[19:30] <muktupavels> Do you know how to fix that? So I can forward that info..
[19:30] <tsimonq2> muktupavels: I don't know, I was simply telling you what the problem was. :P
[19:43] <muktupavels> same recipe works locally on artful


[07:27] <smartboyhw> Good afternoon Noskcaj
[07:28] <Noskcaj> hey smartboyhw
[07:28]  * Noskcaj was busy making rockets
[07:28] <smartboyhw> Noskcaj, LOL
[07:28] <Noskcaj> it fell over and made lot's of smoke
[07:28]  * smartboyhw has just finished a new package's packaging
[07:28] <smartboyhw> Noskcaj, BOO
[07:28] <Noskcaj> lol
[07:28] <smartboyhw> Noskcaj, give me the chemical equation of the rocket plz:P
[07:29] <Noskcaj> KNO3 + sugar = rocket
[07:29] <Noskcaj> google "R-candy"
[07:29]  * Noskcaj can
[07:30] <Noskcaj> 't think of anything to package
[07:30] <Noskcaj> stupid enter key
[07:30] <Noskcaj> lol
[07:30] <smartboyhw> KNO3 (Potassium nitrate) + Sugar (C6H12O6) = Rocket fuel
[07:30] <smartboyhw> Nice
[07:30] <smartboyhw> Noskcaj, LOL
[07:32] <smartboyhw> Noskcaj, my bug is 1208021
[07:32] <smartboyhw> I broke it down into multiple binaries
[07:32] <smartboyhw> https://bugs.launchpad.net/ubuntu/+bug/1208021
[07:32] <smartboyhw> And now I got only 1 lintian warning \o/
[07:33] <Noskcaj> I saw that thismorning. (Noskcaj's one debian packge only has 1 warning)
[07:34] <smartboyhw> Noskcaj, good
[07:34] <smartboyhw> Normally, it's a manpage warning LOL
[07:35] <Noskcaj> no, mine is completely lintian clean
[07:35] <Noskcaj> https://mentors.debian.net/package/python-meld3
[07:35] <smartboyhw> Noskcaj, oh good
[07:35] <smartboyhw> I can't write manpages myself, so:P
[07:35] <Noskcaj> neither, i really need to learn how
[07:40] <Noskcaj> smartboyhw, for update software version bugs, are they "fix released" when the current dev release contains the new version? if so, i have a lot of triage to do
[07:44] <smartboyhw> Noskcaj, yes
[08:01] <smartboyhw> Noskcaj, how's your "bug triaging"?:P
[08:01] <Noskcaj> nothing, did you reply? my internet crashed
[08:03] <smartboyhw> Noskcaj, I did reply yes
[08:04]  * Noskcaj looks at logs
[08:04] <Noskcaj> I've got an MIA to file, then i'll do that.
[08:06] <smartboyhw> Hey elfy any testcase you want to mess with today?:P
[08:07] <elfy> nope
[08:09] <smartboyhw> elfy, oh:(
[08:11] <elfy> testcases are more or less cracked as far as I am concerned
[08:12] <elfy> only 2 not being worked on
[08:13] <smartboyhw> elfy, good:) Which two?
[08:14] <elfy> can't remember now :)
[08:14] <smartboyhw> Meh:P
[08:16] <elfy> onboard is one I think
[10:31] <phillw> balloons: next time you're about, I cannot find the test case for lxterminal. I know it was of the ones I converted over and we then re-loaded last time the applications database was flushed...... Any ideas?
[10:36] <smartboyhw> phillw, I thought somebody submited another testcase of LXTerminal
[10:36] <smartboyhw> Just now
[10:39] <phillw> smartboyhw: indeed, and I have just gone through my archived stuff and found the one for lxterminal and lxtask, along with all the sub tests for pcmanfm..... I'll strangle Nicholas if he's managed to loose them all AGAIN!
[10:40] <phillw> smartboyhw: you have mail :)
[10:45] <phillw> smartboyhw: I'm still going to strangle balloons as he seems to have lost the lxterminal and lxtask ones :P
[10:48] <elfy> lxtask is there
[10:48] <elfy> test number 1510
[10:50] <phillw> elfy: so, where did lxterminal vanish to? :)
[10:53] <phillw> he he, It was a while ago, still using <dl>, <dt>, <dd> etc back then :D
[11:44] <elfy> phillw: we still do use <dl>, <dt>, <dd>
[11:47] <phillw> elfy: ooh, I was told the CSS had changed.... just goes to show how quickly you can out of touch with things.... balloons had a script to convert them to the 'new' CSS system. I have enough 'fun' keeping to the wiki rules :D
[11:50] <elfy> just look at a reccent one - we use those tags - but we don't do all the seperate test names within a testcase
[11:53] <phillw> back then, for pcmanfm it was going to be too long a series of sub tests. I've seen this raised about how many steps can we reasonably expect a tester to do and a 'fail' of 4 -5 pages of a test case is why I split them and something that is still being actively discussed :)
[12:31] <smartboyhw> phillw, OK
[13:15] <phillw> elfy: as the test case for lxtask relies on lxterminal, it is rather redundant as of now :(
[13:18] <elfy> just needs to be fiddled with Iexpect
[13:21] <phillw> elfy: if the old or new version of lxterminal can be added, I will ask the person from lubuntu who is keen on test cases to follow on.... I am borg, his resistance to being assimilated into the 'writing test cases' is futile :D
[13:22] <elfy> :)
[13:23] <elfy> I have to be honest - I've aas much interest in other flavour testcase as others appeared to have in xubuntu ones :)
[13:23] <elfy> our team did a wonderful job and we'll now have other xubuntu jobs for them to do :p
[13:24] <phillw> elfy: I have to be also honesty... I have as much interest in cadence testing as that. For testers, I have already mentioned this to balloons but I do think it should be put on a more formal setting.
[13:32] <elfy> phillw: don't mistake my lack of interest in *buntu for one of not being willing to help people :)
[13:33] <elfy> s/help people out
[13:33] <phillw> elfy: I've known you far too long to make that mistake :)
[13:33] <elfy> good :)
[13:38] <phillw> elfy: BTW, my semi-feral editor of grammar and explaining stuff that is n00b friendly is awaiting a new task... I was thinking about you posting up a page about using the testing repos :D
[13:38] <smartboyhw> phillw, tracker you mean? What repos?
[13:39] <smartboyhw> I thought you are talking about Debian testing:O
[13:39] <elfy> phillw: packages.qa do you mean?
[13:41] <phillw> smartboyhw: it is a new section to be added to https://wiki.ubuntu.com/Testing/Activities the PPA area was recently added, need a section for enabling the dev area of the repos, why it is asked to be done, what the dangers are and how to revert back if it borks.
[13:41] <smartboyhw> phillw, what PPA area?
[13:41] <phillw> elfy: ^^
[13:41]  * smartboyhw still can't understand:
[13:41] <smartboyhw> :P
[13:42] <smartboyhw> I'm a little bit troubled with Multi-Arch packaging here
[13:42] <smartboyhw> So I'm sorry for not understanding
[13:42] <phillw> smartboyhw: then can I suggest you read the page :P https://wiki.ubuntu.com/QATeam/PPA_Testing
[13:42]  * elfy is bereft of time unfortunately - still dealing with sso logins
[13:43] <smartboyhw> phillw, well that page seems good
[13:43] <phillw> elfy: yeah, I did seem to get a lot of traffic on my personal area about that. I'll go and find another "volunteer" :P
[13:48] <smartboyhw> phillw, since you are the Lubuntu QA Lead please review the remaining two merge proposals into lp:ubuntu-manual-tests
[13:49] <elfy> phillw: don't you just love someone telling you what to do ... :p
[13:49] <smartboyhw> elfy, well that two testcases clearly are based on Lubuntu and I don't have Lubuntu:P
[13:49] <smartboyhw> I've already reviewed two...
[13:50] <elfy> I understand that - you just need to think about what your 'pronouncements' look and read like :)
[13:51] <smartboyhw> elfy, 'pronouncements' yeah:)
[13:51] <smartboyhw> Maybe I should write one, I haven't written a manual testcase for a LONG LONG time.
[13:51] <phillw> smartboyhw: and I know little of the new test case system. If the code will not crash something, then get it merged. The testers will pick it apart for any errors. Trust the testers.
[13:51] <smartboyhw> phillw, OK fine.
[13:51]  * smartboyhw goes reviewing
[13:52] <smartboyhw> When I review things, I tend to run through them actually though
[13:52] <elfy> so would I
[13:55] <phillw> smartboyhw: my current 13.10 has good days, I can run through the test case once it is no longer a diff report :)
[13:56] <smartboyhw> phillw, so you hate diffs?
[13:56]  * smartboyhw is used to diffs
[13:56] <smartboyhw> phillw, I'm downloading the Lubuntu alternate to test the image + run through the testcase;P
[13:56] <smartboyhw> I mean, run through the image testcase + the reviewing testcases:P
[13:57] <phillw> smartboyhw: with a passion.. http://pastebin.com/D7jShWjM
[13:57] <smartboyhw> phillw, ?
[13:57] <phillw> I have that gunk thrown at me on wiki pages I am subscribed to.
[13:57] <smartboyhw> I've merged it in and pushed already
[13:58] <phillw> smartboyhw: that was my email announcement. I'm not qualified to accept such a thing.
[13:58] <smartboyhw> phillw, email announcement!?!?!?
[13:59]  * smartboyhw can't understand what phillw is talking at all......
[13:59] <phillw> smartboyhw: yup, I get emails for each merge proposal :)
[13:59] <smartboyhw> phillw, yeah sure, so? :P
[14:00] <elfy> wanders off ...
[14:04] <phillw> I have a quick look to see if there is something crazy, but then leave them to others.... smartboyhw https://wiki.ubuntu.com/UbuntuGNOME/Header?action=info is on version 158....
[14:04] <smartboyhw> phillw, \o/
[14:04] <phillw> Amd I DO read each notification.
[14:05] <smartboyhw> phillw, oh no, I will hate these:P
[14:05] <smartboyhw> bzr diff is my favorite LOL
[14:06] <phillw> smartboyhw: when you grow up, you will learn about wiki editing. Makes test cases look a walk in the park :P
[14:07] <smartboyhw> phillw, LOL
[14:09] <phillw> go look at the code at https://wiki.ubuntu.com/https:/wiki.ubuntu.com/phillw/temp and work out why it does not work :)
[14:09] <smartboyhw> phillw, thanks but I don't want wiki challenges
[14:11] <phillw> smartboyhw: wiki is NOT that scary... I fail to understand how any tester would no be able to learn how to be an editor, especially those who run class room sessions :'(
[14:12] <smartboyhw> phillw, I'm sorry, I would rather want to go and work on code challenges or something......
[14:15] <phillw> smartboyhw: and yet the wiki area is the 1st point of contact for many new commers. Too many kids want the 'exciting stuff' yet they forget that without the wiki area and the manual area, being an advocate for *buntu is to no avail.
[14:16] <phillw> </end rant>
[14:57] <smartboyhw> Hello SergioMeneses
[14:58] <SergioMeneses> hi smartboyhw ...morning here! how are you?
[14:58] <smartboyhw> SergioMeneses, great:)
[14:58] <SergioMeneses> good to know
[15:16] <smartboyhw> phillw, no need for you to approve the 2 Lubuntu testcases I mentioned, I merged and tested them already:)
[15:18] <phillw> smartboyhw: thanks, can you send an email to the L-QA thread about the subject?
[15:18] <smartboyhw> phillw, OK
[15:20] <smartboyhw> phillw, done
[15:20] <smartboyhw> I'm thinking of telling balloons to add him as a testcase admin
[15:21] <smartboyhw> He's really talented:P
[15:22] <phillw> smartboyhw: thanks, as the 'general' qa / wiki person there is a limit to what I can do without burn out :)
[15:23] <phillw> If he is a good test case writer. get him on board!
[15:23] <smartboyhw> phillw, there's also a limit too when I am packaging for Kubuntu:P And phillw I will surely recommend him to balloons


[11:49] <melodie_> hi
[11:51] <melodie_> I have something to say about the quality in Ubuntu, which would not be even distro specific, but I don't know where to port that : the Category line in desktop files through the different Desktop Managers and through the applicaitons is a HUGE MESS !
[11:52] <melodie_> I have fired Xubuntu in Virtualbox to see something, and seeking for the language-selector to put it into my language, I realized that the menu entry is not there though the program is installed
[11:53] <melodie_> what the heck? I have looked into the destop file and of course a long list of categories, but nothing that allows it to display in the Xfce or Whiskermenus! and what about Synaptic? I installed it, but I can try to launch it, it won't start! something wrong with pkexec not started in Xubuntu
[11:53] <melodie_> this is Trusty, and LTS it is supposed to be working out of the box.
[11:53] <melodie_> and the desktop files through all the distros I know of are a mess
[11:54] <melodie_> this is something which should be done straight, in order to provide a good user experience, not a mess looking into /usr/share/applications each time a program is not found in the menus
[11:54] <melodie_> thanks for reading and passing the message.
[22:13] <average_guy> when I am testing an iso and the installer crashes, how can I go in and retrieve the log file?  I just filed https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1349007  and I am wondeing how I could possibly attach more useful information to my reports.