[00:00] <dlentz> I unmarked it as a duplicate
[00:22] <hggdh> dlentz: did you find the apport hooks?
[00:23] <hggdh> dlentz: if not, you can search for all packages that provide one via apt-file
[00:24] <hggdh> apt-file search usr/share/apport/package-hooks
=== s9iper1 is now known as bil21al
=== bil21al is now known as s9iper1
[00:54] <hggdh> lifeless: I am setting bug 931167 as a dup of bug 931207 -- I added a valgrind to mine
[00:54] <ubot4`> Launchpad bug 931167 in network-manager-applet (Ubuntu) "NM-applet using crazy memory (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/931167
[00:54] <ubot4`> Launchpad bug 931207 in network-manager-applet (Ubuntu) "nm-applet memory usage continuously increasing (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/931207
[00:56] <hggdh> hum, there is also bug 930491
[00:56] <ubot4`> Launchpad bug 930491 in network-manager-applet (Ubuntu) "Large memory leak in nm-applet (affects: 12) (dups: 1) (heat: 54)" [Undecided,Confirmed] https://launchpad.net/bugs/930491
[02:10] <em> Im going to report a bug. The bug is that something is packaged wrong. What do you assign the bug too?
[02:11] <micahg> em: the package in question
[02:11] <em> Okay.
[02:11] <em> python-pyopencl
[02:12] <micahg> what about it?
[02:14] <em> well i just found that someone already reported this bug
[02:14] <em> https://bugs.launchpad.net/ubuntu/+source/pyopencl/+bug/763457
[02:14] <ubot4`> Launchpad bug 763457 in pyopencl (Ubuntu) "pyopencl falsely depends on nvidia-current (affects: 18) (heat: 82)" [High,Confirmed]
[02:14] <em> so now what do I do?
[02:14] <em> It's been reported just no one cares maybe.
[02:16] <micahg> well, is there another implementation of opencl in the archive that it can depend on, it seems like the only one is provided by the nvidia binary drivers
[02:18] <em> I dont really understand what that means. But I don't have an nvidia card but I want to install python-pyopencl
[02:18] <micahg> I can take a look in a bit, but I think someone else offered to fix this sometime soon
[02:23] <em> if a bug like that gets fixed does it show up in updates of 11.04 also?
[02:23] <micahg> no, not unless someone does the work
[02:23] <em> or would the package in 11.04 just be left buggy?
[02:23] <em> I think I don't understand the meaning of updates then
[02:24] <em> when the update manager says there are updates, what's going on there?
[02:24] <kklimonda> someone did the work :)
[02:24] <em> if someone will do the work i will send them a bitcoin
[02:24] <kklimonda> first the bug should be fixed in the current development release (that's what micahg is thinking about doing himself right now)
[02:25] <kklimonda> after that it can be considered if the fix is a good candidate for stable releases
[02:25] <em> I see.
[02:26] <em> 11.04 is a stable release?
[02:26] <kklimonda> if so someone (maybe the same person who did the initial fix, but not necessarily ) has to prepare a fix for every affected release
[02:26] <micahg> umm, this needs someone that deals with graphics to fix since our binaries don't provide those opencl packages
[02:27] <kklimonda> I'd try asking RAOF if he's still working on that - he's the last person to comment on it
[02:27] <kklimonda> (or rather planning on working)
[02:29] <em> I'll see if I can find him.
[03:31] <hggdh> now THIS is a record (at least for me): Thunderbird is using 1.5G of resident memory!
[03:38] <micahg> hggdh: I've hit that before when I moved large amounts of main between accounts
[03:40] <hggdh> micahg: it was idling...
[03:41] <hggdh> *IS* idling
[03:42] <micahg> wow, I have 14 accounts and mine is only using 735Mb, but it's only been running for about 9 hours
[03:43] <hggdh> micahg: is it worth the time to valgrind the beast?
[03:43] <hggdh> or is it just the old problem with memory management?
[03:44] <micahg> well, memory management should be improving, but if you've found a leak, it might be worth valgrinding (but IIRC, there's some trick to doing that with Mozilla stuff)
[03:45] <hggdh> yeah. Will look at moz to find the details. I am already on a valgrind streak, given that nm-applet is also memory hungry now
[03:46] <hggdh> and compiz. And indicator-application-service
[03:46] <micahg> yeah, found that out earlier today
[03:46]  * micahg wonders if it's the new libc
[03:46] <hggdh> I was wondering about a common source as well
=== yofel_ is now known as yofel
[09:18] <mainerror> dlentz: Thank you! I've added more information and steps to reproduce. :)
[11:35] <Kurdistan> hi I have bug in latest kubuntu 11.10. when I connect my usb bluetooth and try to send files between laptop-phone my laptop freezes.
[11:35] <Kurdistan> can this be a kernel bug?
[11:36] <Kurdistan> uname -r
[11:36] <Kurdistan> 3.0.0-16-generic
[11:36] <Kurdistan> have tested different 3.0.0* kernel with same result
[11:40] <Kurdistan> it have worked with previews (k)ubuntu releases
=== greyback is now known as greyback|lunch
=== greyback|lunch is now known as greyback
=== bladernr_afk is now known as bladernr_
=== bregma_ is now known as bregma
=== charles_ is now known as charles
=== tobin is now known as joshuaBRB
=== joshuaBRB is now known as tobin
[21:05] <veger> I think bug #788768 can be solved with updating the package to the newer debian package. I have gained some experience with modifying packages and providing fixes, but I never updated a package to a higher version. Could anyone guide me a bit, or tell me how to apply for a mentor/sponsor?
[21:05] <ubot4`> Launchpad bug 788768 in pbuilder (Debian) (and 1 other project) "Missing depends on dpkg-dev for dpkg-architecture (affects: 1) (heat: 6)" [Unknown,Fix released] https://launchpad.net/bugs/788768
[21:06] <dlentz> vegter, unless it's Precise, i don't think you can do it without an SRU
[21:07] <dlentz> do you need a newer version, or just adding dpkg-dev in the control file?
[21:07] <veger> newer version
[21:07] <veger> doing a precise update (first) is fine by me
[21:08] <veger> I'd like to update pbuidler to version 0.206 (currently it is 0.204)
[21:08] <veger> just to lern about updating (and fixing the mentioned bug)
[21:12] <veger> Oh... I see that pbuilder is on https://merges.ubuntu.com/p/pbuilder/ so it is a waste to update manually?
[21:13] <dlentz> that version is for precise, no?
[21:14] <yofel> precise has 0.204ubuntu2, fix is in 205
[21:14] <yofel> so this needs a merge
[21:15] <veger> it is not done automatically?
[21:16] <yofel> veger: nope
[21:16] <veger> found https://wiki.ubuntu.com/UbuntuDevelopment/Merging I'll try to use that guide to perform the merge to 0.206
[21:16] <yofel> auto-syncs are done automatically until DebianImportFreeze. But this is a merge, which always need to be done by someone
[21:16] <yofel> veger: what importance do you want on that bug?
[21:17] <veger> low I suppose, as it is easily circumvented by installing the package
[21:17] <yofel> agreed
[21:19] <veger> yofel: So I set the status to 'In Progress' and start following the merge guide I mentioned and report back here when I am done (or stuck)?
[21:20] <yofel> not here, if you need help with merging ask in #ubuntu-packaging or #ubuntu-motu
[21:21] <veger> yofel: dlentz: ok, thanks for helping
[21:22] <dlentz> i don't think i helped :P
[21:22] <veger> hm... you might be right... ;)
[21:24] <dlentz> i'm used to using my ppa's for packaging updates, never bother to merge them back
[21:25] <veger> I do the same for some packages, but I'd like to help out a bit so decided to see whether I could officially merge pbuilder
[21:52] <dlentz> &**$!)@ launchpad timeouts