[00:21] <jdong> calc: yup firefox gets pissed when the theme changes
[00:46] <lamont>  /usr/lib/udev/migrate-fstab-to-uuid.sh: 141: uuidgen: not found
[00:46] <lamont> so which package gets the bug report that says uuidgen moved from e2fsprogs to uuid-runtime?
[00:48] <kirkland> kirkland@t61p:~/bin$ dpkg -S /usr/lib/udev/migrate-fstab-to-uuid.sh
[00:48] <kirkland> volumeid: /usr/lib/udev/migrate-fstab-to-uuid.sh
[00:48] <kirkland> lamont: ^ ?
[00:49] <slangasek> e2fsprogs, given that e2fsprogs is essential?
[00:49] <lamont> slangasek: as in uuid-runtime should be, too?
[00:49] <slangasek> not sure, hence the question mark
[00:56] <lamont> well, do-release-upgrade -d kinda breaks without it...
[00:57]  * lamont heads out to dinner with his daughter
[00:57] <Fujitsu> do-release-upgrade -d also breaks horridly if any one python-central-using package dies even slightly.
[02:19] <blueyed> Hobbsee: ca you please release virtualbox-ose-modules from NEW?
[02:19] <blueyed> s/ca/can/
[02:20] <Hobbsee> slangasek: might want to
[02:20]  * Hobbsee isn't here for overly long, and hasn't done the previous ones
[02:23] <slangasek> I can't do it just now, but will look later this evening
[02:36] <Fujitsu> Hmmm.
[02:36] <Fujitsu> Did somebody break libpri's shlibs?
[02:36] <Fujitsu> dpkg-gencontrol: warning: can't parse dependency libpri1.0 libpri1.2 (>= 1.4)
[02:42] <sistpoty> Fujitsu: hm... I really thought I've seen libpri in motu-release's bug mail, but it must have been somewhere else, since search didn't show anything
[02:43] <Fujitsu> mvo uploaded it two days ago.
[02:43] <Fujitsu> I presume he broke it, as asterisk built fine recently.
[02:46] <sistpoty> Fujitsu: ok, sent a mail to mvo
[02:47] <Fujitsu> sistpoty: You have? Thanks, it's blocking an asterisk security update.
[02:48] <sistpoty> Fujitsu: feel free to ping though, in case you see mvo around ;)
[02:54] <LaserJock> sistpoty: ummm, like shouldn't you be asleep or something?
[02:56] <sistpoty> LaserJock: yes, I should. and actually I'm on my wy to bed now ;)
[02:56] <sistpoty> so good night everyone
[02:57] <LaserJock> sistpoty: good night
[03:50] <keescook> hmpf, wireshark crashes almost instantly for me.  :(
[04:06] <blueyed> keescook: when starting capturing or on startup already? both works for me.
[04:35] <keescook> blueyed: a little after starting capturing -- seems to be a glib segv -- hmpf, I will dig deeper tomorrow
[04:38] <Fujitsu> I find it often hangs after starting a capture.
[04:39] <blueyed> fwiw, I'm currently using the -server kernel.
[04:45] <Fujitsu> Hmm, it still does its hanging thing.
[04:45] <Fujitsu> Only on this laptop.
[08:18] <Ape> I'd like to have a new feature in the gnome applet called system monitor
[08:18] <Ape> It would be nice, if I could import a value from a file or from a script
[08:19] <Ape> and then draw it like the other values(system load, ram, network usage)
[08:19] <Ape> Where can I get the codes and start to make that feature?
[08:19] <Ape> Or does somebody want help me with that?
[08:23] <Ape> I found the sources in launchpad
[08:23] <Ape> how can I add a new value input here?
[08:55] <genete> Hi. I'm Synfig contributor and Ubuntu user. We have released recently the new Synfig version 0.61.08 but it seems we have been late for next ubuntu vesion.
[08:56] <genete> I still having a 6.06 ubuntu vesion working and the last synfig release is fully compatible with it building from source.
[08:57] <genete> Is is possible that someone package a backport for synfig last version? Check out here: http://synfig.org/Main_Page
[08:59] <crevette> hello;  is universe freezed ? ie can we push new version of softawre ?
[09:17] <Adri2000> genete: a backport is possible only from the current developement version of ubuntu, ie. hardy right now. if the version you want backported is not in hardy, either try to get a freeze exception for it (which becomes harder and harder as we are approaching the final release), or wait for intrepid developement to start
[09:18] <Adri2000> crevette: there is Feature Freeze, so you can push bug fixes, but no new upstream release with new features (except if you get a freeze exception)
[09:21] <crevette> too bad nobody cared about nemiver :/
[09:24] <genete> Adri2000: ok, so take an eye on this project. I beliebe that it covers a big hole in the Open Source map and lately is being relaunched. Please drop by #synfig for synchoronization for next ubunutu release.
[09:25] <genete> Glad to meet you. Bye
[09:25]  * genete is away: Estoy ocupado
[09:28] <Mirv> bryce: hi, the new gnome-control-center doesn't have the i18n patch 104 fixed
[09:29] <Mirv> bryce: it still only patches the already-applied 101, and you mentioned you would fix it in a proper way despite the fact that 101 is coming from upstream so it cannot be changed or so...
[09:33] <Mirv> bryce: the point was that the patch I originally offerred was supposed to be a patch changing the current 101 patch, not to be put in debian/patches directory.. but since you didn't want to change the 101 patch itself, you included my patch as a file to debian/patches which doesn't work
[09:57] <Mirv> bryce: easiest would be mv 104_cc-randr12-enable-i18n.patch 100_cc-randr12-enable-i18n.patch <- no need to rework the patch for now. but a new upload should be done rather soon, since my patch was only reverting one string (as an example) to such that is already translated, so others have to be retranslated (soonish) by translators.
[09:58] <Mirv> bryce: and finally, there's now also a bug 212132 :)
[09:58] <ubotu> Launchpad bug 212132 in gnome-control-center "i18n patch 104 is not correctly applied" [Undecided,New] https://launchpad.net/bugs/212132
[09:59] <bryce> Mirv: sorry about that, let me take a look
[10:13] <bryce> Mirv, ok I've redone your patch to fix it, and uploaded.
[10:13] <bryce> night
[10:17] <kblin> hi
[10:26] <Mirv> bryce: thanks a lot, good night :)
[12:23] <afflux> I checked at https://launchpad.net/ubuntu/+source/bluez-pin/ but couldn't find any indication on where bluez-pin has gone after feisty. Any hints?
[12:25] <afflux> ah, it was removed from debian
[13:19] <qense> I've got a question about a bug I'm triaging: bug 186264
[13:19] <ubotu> Launchpad bug 186264 in hal "keyboard randomly goes dead; takes a logout to restore functionality." [Undecided,Incomplete] https://launchpad.net/bugs/186264
[13:19] <qense> I'm not sure if it's really in HAL and I was wondering if you know something more about it.
[13:19] <qense> And do you think it contains enough information?
[14:54] <Alan> I hope this is the right place for this, but...  Is there any particular reason why the update manager has to steal focus repeatedly during an update?
[14:54] <qense> not really in my eyes, it could be considered as a bug
[14:55] <Alan> But not one that anybody has ever bothered to report/fix?  I guess it isn't that important, but it's been around for a while...
[14:55] <Alan> It's frustrating that I can't actually do anything if i'm running a couple of updates because the focus is stolen every few seconds...
[14:56] <qense> you should report a bug at bugs.launchpad.net/ubuntu
[14:56] <qense> it's indeed anoying
[14:56] <Alan> At least it's not as bad as WinXP's "You still need to restart" popup every 5 mins :P
[14:57] <qense> yes
[14:57] <qense> in Linux you only need to restart when the kernel has been updated
[14:58] <Alan> Yeah, I like that
[14:59] <Alan> oooh, old bug...
[14:59] <Alan> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/35876
[14:59] <ubotu> Launchpad bug 35876 in metacity "'Downloading package information' and 'building dependency tree' progress dialogs steal focus" [Low,Confirmed]
[14:59] <ion_> And usually you can even delay that, unless there's a security fix of course.
[15:00] <Alan> ion_, i love the nice modular linux kernel - back when i ran gentoo, i got a 2-month uptime on my desktop even when i'd been adding in entire subsystems to the kernel :)
[18:03] <qense> Are there -server restricted modules for 7.10?
[18:06] <Nafallo> qense: not that I'm aware of no.
[18:06] <qense> ok
[18:06] <qense> hardy does
[18:06] <Nafallo> oh. didn't know that.
[18:06] <Nafallo> what's in there?
[18:06] <qense> someone I'm helping wants to install wireless drivers, but he's using the server kernel
[18:07] <qense> so that won't work unfortunately
[18:07] <Nafallo> wireless on a server?
[18:07] <Nafallo> that sounds... weird :-)
[18:07] <qense> yeah, I know :)
[18:56] <muhaha007>  hi
[18:56] <muhaha007>  does anybody know, where I can find the examples.pyw in pythoncard?
[18:56] <muhaha007>  normally it should be in /usr/lib/python2.5/site-packages/PythonCard, but there's no such directory
[18:56] <muhaha007>  installed it from apt
[18:57] <muhaha007> :)
[18:59] <mok0> muhaha007: dpkg -L pythoncard
[19:00] <muhaha007> mok0: well, just /usr/share/doc/pythoncard
[19:01] <muhaha007> but /usr/lib/python2.5/site-packages DOES exist :)
[19:02] <muhaha007> mok0: evrything seems to be installed, codeEditor is working, but the directory for the samples doesn't exist
[19:03] <muhaha007> mok0: so there's no /site-packages/PythonCard
[19:05] <mok0> muhaha007: perhaps it's in another package
[19:05] <mok0> pyhoncard-doc or pythoncard-tools
[19:05] <mok0> or python-pythoncard
[19:06] <mok0> muhaha007: pythoncard-doc: /usr/share/doc/pythoncard-doc/samples/webserver/webservices/examples.py
[19:09] <muhaha007> dok0: thx, I'll search there, looking for samples.pyw :)
[19:15] <syke_> hi
[19:16] <syke_> several people (including myself) are reporting an issue where xulrunner-1.9 forces the removal of firefox-3.0, and then it is impossible to get it reinstalled
[19:16] <syke_> this just started this morning, in case developers aren't aware of the issue
[19:16] <qense> wasn't the xulrunner and firefox hug day thursday :P this bug is just too late
[19:16] <qense> syke_: it's probably a dependency issue
[19:17] <qense> what's the bug report at LP?
[19:17] <syke_> I don't know that there is one -- this literally juts started happening to everyone sometime between last night and a few hours ago
[19:18] <qense> :(
[19:18] <jdong>  1.9~b5+nobinonly-0ubuntu1
[19:18] <syke_> it does appear to be a dependency issue
[19:18] <jdong> yeah brand new versions just uploaded it would seem
[19:18] <jdong> published 3hrs ago
[19:18] <jdong> could just be a transient archive issue?
[19:18] <syke_> I'm happy to try thing here locally and pass the info along to #ubuntu+1, if it works
[19:19] <qense> the bug isn't reported
[19:19] <qense> do you think it's useful to open a bug report or is it likely going to be fixed very soon when firefox-3.0 is updated>
[19:19] <jdong> syke_: can you file a bug report with the symptoms?
[19:19] <syke_> sure
[19:19] <jdong> thanks :) just so that the mozilla folk not active rigth now are aware of the issue :)
[19:20] <qense> syke_: are you a member of ubuntu-bugcontrol?
[19:20] <muhaha007> mok0: samples.pyw doesn't seem to exist
[19:20] <qense> otherwise I can set the importance to high
[19:20] <muhaha007> mok0: it's not in /usr/* or /lib/*
[19:21] <syke_> qense: nope, wasn't aware of such a thing
[19:21] <qense> ok
[19:21] <syke_> should I be?
[19:21] <qense> no :)
[19:21] <syke_> heh ok
[19:21]  * Gnine thanks all folks who make ubuntu possible
[19:21] <LaserJock> muhaha007: there's a samples.py in pythoncard-doc but that's it, as far as I could tell
[19:22] <muhaha007> mok0: on the project-page-documentation they say, that there should be a samples.pyw in /usr/lib/python2.5/...
[19:23] <muhaha007> mok0: I hope they didn't cut that out in ubuntu repo ;)
[19:23] <LaserJock> muhaha007: there isn't a samples.pyw in Ubuntu
[19:23] <LaserJock> muhaha007: but you should see if samples.py is equivalent
[19:24] <muhaha007> mok0: it's not :)
[19:24] <muhaha007> samples.pyw is a binary for showing all the examples with source code and stuff
[19:25] <muhaha007> mok0:http://pythoncard.sourceforge.net/walkthrough1.html
[19:26] <LaserJock> muhaha007: oh, that could be why it's not there
[19:27] <LaserJock> muhaha007: what if you ran samples.py?
[19:27] <muhaha007> mok0: cant, must change it to executable first :)
[19:27] <muhaha007> mok0:but that shouldn't be the problem
[19:28] <LaserJock> you can run it with python
[19:28] <LaserJock> python samples.py
[19:28] <muhaha007> mok0:whooops: gives me errors in source code
[19:29] <muhaha007> mok0:if I run it with python, nothing happens
[19:29] <muhaha007> doesnt seem to be the binary I am searching for
[19:30] <syke_> https://bugs.launchpad.net/ubuntu/+source/xulrunner-1.9/+bug/212416
[19:30] <ubotu> Launchpad bug 212416 in xulrunner-1.9 "latest xulrunner-1.9 update breaks firefox-3.0" [Undecided,New]
[19:30] <syke_> there's that bug
[19:30] <LaserJock> muhaha007: well, I don't know what to tell you. The samples are there so you can try them out and the html docs as well
[19:30] <muhaha007> mok0:I googled for it, found one entry in ubuntu-forum, but no solution, because there was a problem installing it from the source code
[19:31] <qense> syke_: have others confirmed it?
[19:31] <syke_> qense: yes
[19:32] <Gnine> #ubuntu-bugs is more suitable place for such announcements
[19:32] <syke_> as I said, there is now a steady stream of people coming into #ubuntu+1 and reporting the sympthoms
[19:32] <syke_> gnine: I will note for the future
[19:32] <qense> pl
[19:32] <qense> ok*
[19:33] <syke_> qense: is there anything else you'd like me to try, or add to the bug report?
[19:34] <qense> it's complete for now, but be prepared to ask questions from developers
[19:34]  * jdong updates his hardy chroot and takes al ook
[19:34] <syke_> answer questions, you mean? :)
[19:34] <syke_> certainly
[19:35] <syke_> another issue that comes up a few times a day for the last few months is this one: https://bugs.launchpad.net/ubuntu/+bug/197558
[19:35] <ubotu> Launchpad bug 197558 in linux "ssb module breaks BCM4328 with ndiswrapper (regression from 2.6.24-10)" [Medium,Triaged]
[19:35] <qense> syke_: lets move to #ubuntu-bugs
[19:35] <syke_> sure
[19:36] <jdong>      3.0~b4+nobinonly-0ubuntu1 0
[19:36] <jdong> syke_: it's because firefox 3.0b5 has not hit the archives yet
[19:36] <syke_> jdong: hopefully it's on its way, then?
[19:36] <syke_> and wasn't just a partial commit?
[19:37] <jdong> syke_: yeah, it should be on its way. this problem should resolve itself in a few hours
[19:37] <jdong> syke_: you can verify by typing "apt-cache policy firefox-3.0"
[19:37] <jdong> note that it reports 3.0~b4 is in the repos
[19:38] <jdong> and doing the same for xulrunner-1.9 reports 1.9~b5 is the current version
[19:39] <syke_> jdong: correct
[19:40] <syke_> I had another question -- can the gcc-snapshot of the gcc 4.3 branch be moved to a gcc-4.3 package, then gcc-snapshot pointed at the actual trunk (4.4)?
[19:47] <syke_> bueller?
[19:50] <LaserJock> syke: I doubt we'd do that kind of change for hardy
[19:50]  * jdong starts looking at a backport of xulrunner
[19:50] <jdong> go betas.
[19:51] <LaserJock> oh man
[19:51] <syke> ok. just seems weird to have a real gcc release still as a snapshot
[19:51] <jdong> syke: well at the time it's packaged it was a snapshot
[19:51] <syke> wasn't gcc-4.2 quickly shifted from snapshot to a discrete package?
[19:51] <jdong> and as LaserJock said it's likely too late in the release cycle to put in a new gcc
[19:51] <qense> I don't know what to do next with bug 186264 , it contains a lot of information already, but I couldn't find the actual cause. Are there any developers around here who know more about this piece of software and can help?
[19:51] <ubotu> Launchpad bug 186264 in hal "keyboard randomly goes dead; takes a logout to restore functionality." [Undecided,Incomplete] https://launchpad.net/bugs/186264
[19:51] <syke> well, not as the default, for sure ;)
[19:52] <LaserJock> syke: well, it actually is a svn snapshot
[19:53] <jdong> bzr version
[19:53] <jdong> grr
[19:53] <syke> laser: I get that, but gcc 4.3 was released almost a month ago now :) trunk is now 4.4
[19:53] <LaserJock> syke: sure, but it's not lying to call it a snapshot ;-)
[19:54] <syke> er, sure.. that's one way to look at it ;)
[19:54] <syke> I did notice that it is now a snapshot of the 4_3 branch, rather than trunk, at this point
[19:54] <LaserJock> yeah
[19:56] <syke> is it just a matter of the usptream debian providing a discrete 4.3 package?
[19:56] <syke> (or do they even do such a thing?0
[19:56] <syke> it wouldn't matter to me if I didn't have to futz with symlinks as much to use gcc 4.3 for my local development
[19:57] <LaserJock> I believe that's exactly it
[19:57] <syke> ok cool
[19:58] <LaserJock> 4.3 entered debian on the 2nd
[19:58] <LaserJock> which is a long time after our Feature Freeze
[19:59] <syke> 3/2 or 4/2?
[20:00] <LaserJock> 4/2
[20:00] <syke> ok
[20:00] <LaserJock> sorry, I was wrong
[20:00] <syke> hm?
[20:00] <LaserJock> 3/9 was the first 4.3 version in Debian
[20:00] <qense> Sorry for bumping but I've been trying to get an answer for the whole day: I don't know what to do next with bug 186264 , it contains a lot of information already, but I couldn't find the actual cause. Are there any developers around here who know more about this piece of software and can help?
[20:00] <ubotu> Launchpad bug 186264 in hal "keyboard randomly goes dead; takes a logout to restore functionality." [Undecided,Incomplete] https://launchpad.net/bugs/186264
[20:01] <poningru> any reason why firefox was uninstalled just now?
[20:01] <syke> btw, the firefox-3.0 update is now in my repo and things are happy again
[20:01] <syke> pon: do another update, then reinstall
[20:01] <qense> so the bug can be marked as invalid or fix released
[20:02] <syke> yup
[20:02] <syke> and the several duplicates that have popped up in the last hour
[20:02] <syke> laser: I'll try poking my canonical rep on that front, also
[20:03] <LaserJock> syke: which front?
[20:06] <syke> laser: both this ndiswrapper issue and gcc-4.3
[20:07] <syke> at my work we are switching to gcc-4.3 aggressively since it now has a built-in warning that find stack-based buffer overflows
[20:07] <syke> -Warray-bounds, which works by default with -O2 and -Wall
[20:08] <LaserJock> well, you can use gcc-snapshot
[20:08] <syke> we also got about a 5% increase in performance in one of our big C++ apps just by recompiling in GCC 4.3 thanks to the new constant folding
[20:08] <syke> yes, but as I say, it's a pain to use/deploy since the symlinks all have to be updated
[20:10] <LaserJock> well, I guess you could ask then, but I seriously doubt we'd make that change this late
[20:11] <syke> yup, never hurts to ask
[20:11] <syke> btw, I really appreciate you guys being so helpful/positive :)
[20:11] <LaserJock> better than your Canonical rep would be to ask doko
[20:11] <LaserJock> he's the toolchain guy and does much of the gcc maintaining in Debian and Ubuntu
[20:12] <syke> appears to be idle -- any idea when he is usually on?
[20:12] <LaserJock> European business hours
[20:12] <laga> syke: you can probably also rebuild the debian deb on your box isntead of building from source.. that might save you some symlinking hassle..
[20:12] <LaserJock> and probably not until the weekend is over
[20:12] <syke> laga: that's a good idea, actually -- thanks!
[20:12] <LaserJock> laga: yeah, that would probably be a good idea
[20:13] <syke> we try to not customize the ubuntu too much, but we already have to for eclipse-cdt and whatnot
[20:13] <laga> syke: pbuilder might be a good friend here
[20:13] <syke> pbuilder?
[20:13] <syke> I already have been building local KDE packages for optimization, testing, and bugfixes
[20:15] <LaserJock> syke: https://wiki.ubuntu.com/PbuilderHowto
[20:15] <LaserJock> allows you to build .debs in a clean chroot
[20:15] <LaserJock> and you can build .debs for multiple releases on a single machine
[20:16] <syke> oh cool, thanks! I was just using dpkg-buildpackage before
[20:16] <LaserJock> pbuilder is a lot cleaner
[20:17] <syke> it certainly reads that way ;)
[20:17] <syke> brb
[20:17] <LaserJock> if you have LVM free space around you could also try https://help.ubuntu.com/community/SbuildLVMHowto
[20:18] <LaserJock> that's pretty darn close to the environment that all the Ubuntu .debs are built on
[20:18] <poningru> :(
[20:18] <poningru> I had to install firefox manually
[20:18]  * poningru is wondering why updating removed firefox
[20:19] <LaserJock> poningru: there was a xulrunner/firefox mixmatch
[20:19] <LaserJock> temporary archive issue
[20:19] <poningru> ah 1.9
[20:19] <poningru> gotcha
[20:19] <poningru> wait I thought gecko 1.9 was gran paradisio
[20:21] <LaserJock> is there a problem with that?
[20:23] <poningru> I'm just confused... digging around to figure out what the problem is
[20:24] <LaserJock> what problem?
[20:24] <poningru> the mixmatch
[20:24] <poningru> the xulrunner/firefox version mismatch issue
[20:24] <poningru> ignore me I'm just confused
[20:28] <syke> poningru: it's been resolved -- people should be able to update and reinstall firefox3 now
[20:28] <syke> (and monodevelop_)
[20:31] <poningru> sweet danke
[22:28] <emgent> heya