=== nixternal_ is now known as nixternal
=== asac_ is now known as asac
=== bluefrog is now known as blue-frog
=== null_vec1or is now known as null_vector
=== blue-frog_ is now known as blue-frog
=== doko__ is now known as doko
[13:51] <_myrtille_> Hi :)
[13:51] <_myrtille_> could someone help me with creating a bugreport?
[13:51] <james_w> sure, what is the problem you are having?
[13:51] <_myrtille_> i found an invalid bugreport concerning "my" bug:
[13:52] <_myrtille_> https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/190625
[13:52] <ubotu> Launchpad bug 190625 in gnome-games "robot crashes when I teleport" [Undecided,Invalid]
[13:52] <_myrtille_> in which is stated, that one should submit the crashreport in var/crash
[13:52] <_myrtille_> but i don't have a crashreport there, so i can't submit it
[13:52] <_myrtille_> how do i make one?
[13:52] <pedro_> _myrtille_: get a trace with gdb
[13:52] <_myrtille_> ok :)
[13:53] <pedro_> _myrtille_: https://wiki.ubuntu.com/DebuggingProgramCrash <- all the info is there
[13:53] <_myrtille_> yes, i read it, but i wasn't sure wether i should follow general instructions or the specific way, pointed out in that bugreport
[13:54] <_myrtille_> and the second thing is: I dried making a log with valgrind, but I only get:valgrind: /usr/games/gnobots2: Permission denied
[13:57] <james_w> _myrtille_: to use valgrind you will first have to run "sudo chmod g-s /usr/games/gnobots2"
[13:57] <_myrtille_> what does it do?
[13:57] <james_w> and then "sudo chmod g+s /usr/games/gnobots2" when you are finished.
[13:57] <james_w> it removes the setgid bit from the permissions of the executable.
[13:57] <_myrtille_> thx :)
[13:58] <james_w> setgid means that when you run the game you are able to write to the high score file, we have to temporarily remove that capability to please valgrind.
[13:58] <_myrtille_> ok :)
[14:19] <james_w> _myrtille_: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-games/+bug/213341, thanks.
[14:19] <ubotu> Launchpad bug 213341 in gnome-games "robots crashes when trying to teleport" [Undecided,New]
[14:20] <_myrtille_> :)
[14:20] <_myrtille_> no. thank you :)
[14:20] <james_w> _myrtille_: it would be great if you could install some dbgsym packages to make the backtrace better.
[14:20] <james_w> at the moment there's not a lot of information there.
[14:20] <_myrtille_> actually, i tried, i installed this yelp-dbgsym package mentionned in the wiki-article
[14:21] <_myrtille_> are there others, that would improve the result?
[14:21] <james_w> ah, that's just an example.
[14:21] <james_w> you want gnome-games-dbgsym
[14:21] <_myrtille_> ok :p... i didn't get that one :p
[14:21] <james_w> and probably some others would help, one moment
[14:22] <james_w> libgnome2-0-dbgsym and libgtk2.0-0-dbgsym please
[14:22] <james_w> also, it doesn't crash for me, and the differences are that I'm using gnome in English, so one of those could be the cause
[14:23] <james_w> can you try running it as "LANG=C gnobots2" please?
[14:23] <seb128> why not just using apport to send the crash?
[14:23] <james_w> there is no crash file apparently.
[14:24] <seb128> btw, bug #190625
[14:24] <ubotu> Launchpad bug 190625 in gnome-games "robot crashes when I teleport" [Undecided,Invalid] https://launchpad.net/bugs/190625
[14:24] <seb128> ah, it's noted in the new one
[14:26] <_myrtille_> i can't install the debugging symbols because they depend on gnome-games version 1:2.20..3-0ubuntu1, i have 1:2.20.1-0ubuntu1
[14:26] <_myrtille_> but i can't find the newer version with aptitude
[14:27] <james_w> have you done an aptitude update?
[14:27] <_myrtille_> @james_w  i'm still getting the crash when i use your command to change the language
[14:28] <_myrtille_> i did one 20 Minutes ago when integrating the sources for the debugging packages
[14:28] <james_w> maybe your mirror hasn't been updated yet
[14:29] <james_w> http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-games/gnome-games_2.20.3-0ubuntu1_i386.deb
[14:29] <james_w> oops, wrong one
[14:30] <james_w> _myrtille_: are you on gutsy?
[14:30] <_myrtille_> yes
[14:31] <james_w> ah, ok, the dbgsym debs only apply to hardy.
[14:32] <_myrtille_> i'm feeling stupider by the minute ;)
[14:34] <james_w> no need for that, I should have asked earlier
[14:35] <james_w> so, there's a possibility that this is fixed in Hardy already, would you be able to test?
[14:35] <_myrtille_> i would be willing to test, i don't know if i'm able... what do i need to do?
[14:36] <james_w> you could download the beta and try the live cd.
[14:36] <james_w> or you could upgrade to hardy.
[14:37] <_myrtille_> na... i don't think i'll be upgrading anytime soon. :p
[14:38] <_myrtille_> it's the only pc i have and i need it to be reliably working for another month
[14:38] <_myrtille_> but i'll try the live cd
=== jjesse is now known as jjesse_VACATION
=== jjesse_VACATION is now known as jjesse_vacation_
[15:17] <_myrtille_> james_w: re, sry for the wait... just managed to kill my lan connection, so it might take a while, until i can download hardy
[15:17] <james_w> _myrtille_: no problem.
[15:17] <_myrtille_> but i let you know (here and in the bugreport) of the results
[15:17] <james_w> great, thanks.
[16:02] <jcastro> seb128: do you remember that bug wrt. gnome-vfs/gvfs that was wrongly linked upstream?
[16:02] <jcastro> seb128: I found out how to delete watches
[16:02] <seb128> jcastro: how?
[16:02] <seb128> jcastro: well, deleting watches work
[16:02] <jcastro> on the left side there is an applet thing for bug watches
[16:02] <seb128> jcastro: closing upstream taks as invalid works
[16:02] <jcastro> ah
[16:02] <seb128> my issue is that you can't reassign the upstream task
[16:03] <seb128> or delete it
[16:03] <jcastro> ah ok
[16:03] <jcastro> I will bring that up today
[16:03] <seb128> so you have to keep an invalid task on the wrong product which is annoying
[16:03] <seb128> thanks ;-)
[16:03] <jcastro> do you remember the bug though? I need to screenshot the watch-deletion thing for the wiki. :D
=== qense is now known as qense|dinner
[16:51] <bicyclist> Are the hardy heron repos broken ?
[16:54] <seb128> bicyclist: no, why?
[16:54] <bicyclist> cause the update removes nautilus, and ubuntu-desktop !!!!
[16:54] <bicyclist> I am now on kde cause gnome does not work any more on my hardy install.
[16:54] <bicyclist> broken dependencies when i try to installl ubuntu-desktop
[16:58] <bicyclist> Now my whole gnome installation is broken and im a forced to use kde
[16:59] <prana> yeah, i decided against taking today's updates when i saw that it was going to remove ubuntu-desktop.
[16:59] <prana> :-/
[16:59] <bicyclist> should have done that too but hopefully it will be fixed soon.
[17:00] <seb128> that's not a bug
[17:00] <seb128> that's on purpose
[17:00] <seb128> that's supposed to make you stop updating while everything is not available
[17:00] <bicyclist> Grin.
[17:00] <seb128> now if users where reading before acknowledging the removals
[17:01] <bicyclist> well came home from work, brain on hold ;)
[17:06] <bicyclist> seb128 so we are in a transition ? What is being brought into the reps ?
[17:06] <seb128> bicyclist: libgnome-desktop-2 and gnome-control-center needs to be updated together
[17:06] <seb128> is that the issue you are having?
[17:06] <bicyclist> Yes i assume.
[17:09] <bicyclist> so we just have to wait i assume.
=== qense|dinner is now known as qense
[17:12] <bicyclist> Grin, just in the process of reinstalling ubuntu-desktop
[17:16] <qense> guys, any thoughts about bug 212271? Especially the last two comments
[17:17] <qense> https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271
[17:17] <ubotu> Launchpad bug 212271 in linux-ubuntu-modules-2.6.24 "2.6.24-15-generic: saa7134-alsa makes HAL to fail" [Medium,Confirmed]
[17:25] <prana> qense: not knowing too much about it, but hal breaking seems bad.
[17:26] <qense> yes, that is what I thought too
[17:26] <qense> but I'm not sure on what to do next
[17:26] <RainCT> ubotu, give me bug #212250 :P
[17:27] <qense> bug 212250
[17:27] <ubotu> Launchpad bug 212250 in boson "Merge boson 0.13-3 from Debian(Unstable)" [Undecided,Fix released] https://launchpad.net/bugs/212250
[17:27] <qense> that one?
[17:27] <RainCT> o_O
[17:27] <qense> you shouldn't use the # I suppose
[17:27] <RainCT> qense: thanks
[17:27] <qense> :)
[17:27] <RainCT> it used to work with #
[17:27] <RainCT> bug #212250
[17:27] <RainCT> bug 212250
[17:28] <andrea-bs> bug #212250
[17:28] <qense> bug 212250
[17:28] <ubotu> Launchpad bug 212250 in boson "Merge boson 0.13-3 from Debian(Unstable)" [Undecided,Fix released] https://launchpad.net/bugs/212250
[17:28] <qense> :P
[17:28] <RainCT> qense: seems like he likes you :P
[17:28] <qense> I seem the only one who can get it working
[17:28] <qense> maybe because I and ubotu live in the same country ;)
[17:28] <qense> bug 1
[17:29] <qense> aaargh! he stopped listening
[17:29] <ubotu> Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1
[17:29] <prana> qense: re 212271, do you know what the syslog messages about Tainted refer to?
[17:29] <RainCT> bug 2
[17:29] <RainCT> :'(     xD
[17:29] <prana> bug 212250
[17:29] <ubotu> Launchpad bug 212250 in boson "Merge boson 0.13-3 from Debian(Unstable)" [Undecided,Fix released] https://launchpad.net/bugs/212250
[17:29] <qense> ubotu doesn't work always
[17:30] <qense> prana: no I don't really
[17:30] <prana> qense: i don't know what the tainted stuff is but it looks suspiciously like a bug in the sound driver's /proc implementation caused hald to get beat up by the kernel.
[17:30] <qense> do you have a bug number?
[17:31] <prana> i'm looking at the messages.txt file from bug 212271. e.g., log lines from Apr  5 15:18:45
[17:31] <ubotu> Launchpad bug 212271 in linux-ubuntu-modules-2.6.24 "2.6.24-15-generic: saa7134-alsa makes HAL to fail" [Medium,Confirmed] https://launchpad.net/bugs/212271
[17:31] <bdmurray> prana: tainted means there is a proprietary driver loaded
[17:33] <prana> bdmurray: ah yes, the nvidia module in this case, perhaps.
[17:33] <qense> saa7134-alsa is loaded there
[17:34] <bdmurray> usually you see something like "nvidia: module license 'NVIDIA' taints kernel"
[17:34] <prana> bdmurray: exactly; so the taint state is probably not related to the actual bug.
[17:34] <qense> at the last line gnome-keyring has a segfault
[17:35] <qense> is gnome-keyring having a segfault everytime?
[17:35] <prana> qense: i'd imagine that's b/c it is trying to use hal?
[17:35] <qense> network-admin had one too(at least one)
[17:35] <qense> b/c?
[17:35] <prana> because
[17:35] <qense> ok
[17:36] <qense> is hal actually running at that time?
[17:36] <qense> the log starts with a segfault of gdm!
[17:38] <prana> i'd say that hal need not be an affected package for this particular bug; the kernel team should track down the problem from the kernel oops in the messages file and fix the driver bug.
[17:38] <qense> ok, so I should mark the bug for hal as won't fix and assign the other to the kernel oops team?
[17:39] <prana> (if I were in bugcontrol) i'd definitely do the assigning to the kernel oops... not sure if invalid or wontfix is better status for the hal bug.
[17:39] <bdmurray> The last comment regarding hal seems reasonable to me
[17:40] <qense> yeah, hal shouldn't stop working when a driver causes problems
[17:43] <qense> but is it really a kernel oops? It doesn't look like the stuff described at the KernelOops page at the wiki, which looks more like a kernel panic
[17:44] <bdmurray> this one has an oops in it
[17:44] <qense> ok
[17:44] <bdmurray> http://launchpadlibrarian.net/13157843/dmesg
[17:44] <qense> i'll tag it
[17:44] <qense> it is already
[17:45] <bdmurray> yeah, sorry about that.
[17:46] <qense> :)
[17:46] <qense> oh no! I missed a few karma points!
[17:46] <bdmurray> heh
[17:48] <qense> so what should be done more to the bug, especially concerning the hal part
[17:48] <qense> ?
[17:48] <prana> can karma points be redeemed for prizes? ;-)
[17:53] <RainCT> lol
[17:55] <Iulian> That's interesting indeed :)
[17:56] <qense> but you can just create your own project, create a lot of blueprints and you'll have 10000 karma
[17:56] <qense> that's very easy
[18:00] <Arby> could someone look at bug 213112. Sounds like a server problem to me
[18:00] <ubotu> Launchpad bug 213112 in update-manager "Power PC Security Repositories Bug" [Undecided,New] https://launchpad.net/bugs/213112
[18:01] <Arby> but just wondering if there is a known problem with these repos
[18:07] <pen> I got white screen after suspend, is there a way to solve this?
[18:07] <pen> I still can login by typing pass and press enter
[18:08] <pen> but it's disturbing to not have a login screen instead of a plain white screen
[18:22] <mvo> Arby: thanks for telling me about #213122
[18:23] <Arby> mvo:  no problem
[18:23] <Arby> I'm setting off on an evening of update-manager bug triage
[18:25] <james_w> go Arby :-)
[18:27] <Arby> mvo: 213112 looks to have been around for a week or so
[18:27] <Arby> bit odd for a repo problem
[18:28] <Arby> is there something unusual about those repos
[18:32] <james_w> Arby: it appears as if the ports haven't had the source setup for the hardy security yet, I'm not sure who to ask about that.
[18:42] <mvo> Arby: I'm checking this bug now, I think its something in update-manager (or the user setup that update-manager should correct)
[18:42] <mvo> Arby: please let me know about more interessting ones :-D I very much appreciate your help!
[19:06] <Arby> mvo: what's the best thing to do with bug 213040? do I mark it as patch included or something?
[19:06] <ubotu> Launchpad bug 213040 in update-manager "update-manager: spelling errors in hardy.tar.gz" [Undecided,New] https://launchpad.net/bugs/213040
[19:10] <mvo> Arby: yeah, thanks. bad timing unfortunately as we are deep in string freeze
[19:10] <mvo> Arby: and it would be nice if we could get a diff instead of a copy of the tarball with the fixes in :)
[19:11] <Arby> ok, I can ask for one. Is there a tag for patch included or how do I mark it?
[19:13] <james_w> Arby: if the user checks the "This is a patch" box when they add an attachment then the attachment is marked as a patch
[19:13] <james_w> you can also tag the bug report as "patch", I don't know how mvo likes to work though.
[19:14] <Arby> as in, edit tags -> patch you mean?
[19:14] <Arby> sorry I don't understand tagging yet
[19:15] <james_w> Arby: yes, "Edit description/tags" and then add "patch" to the tags text box.
[19:15] <Arby> ok thanks
=== thekorn_ is now known as thekorn
[19:19] <prana> i want to have the submitter forward bug 163341 upstream and mark it as wontfix; reasonable?
[19:19] <ubotu> Launchpad bug 163341 in git-core "git-svn gets wrong parent revision for tags" [Undecided,Incomplete] https://launchpad.net/bugs/163341
[19:23] <mvo> james_w: thanks, I don't have any preferences yet, a patch tag sounds good to me.
[19:24] <james_w> prana: why wontfix?
[19:33] <Arby> mvo any thoughts on importance for bug 186465
[19:34] <ubotu> Launchpad bug 186465 in update-manager ""distribution upgrade" hangs during update to hardy" [Undecided,Confirmed] https://launchpad.net/bugs/186465
[19:34] <Arby> there's a lot of noise in that thread
=== chuck_ is now known as zul
[19:34] <Arby> but there's also some potentially interesting stuff
[19:35] <Arby> see the comment by jan.tore.korneliussen
[19:36]  * mvo looks
[19:36] <mvo> it shouldn't hang anymore (I hope :)
[19:37] <Arby> so that should be marked fix released ?
[19:49] <Arby> in bug 212020 is update manager really the problem or is it just the messanger in this case?
[19:49] <ubotu> Launchpad bug 212020 in update-manager "update-manager crashed with SIGSEGV in PyThread_release_lock()" [Undecided,New] https://launchpad.net/bugs/212020
[19:50] <mvo> Arby: I need to look into #186465 again to be sure
[19:51] <mvo> Arby: for 212020 I suspect its just the messanger, a segfault here is either python or python-apt, it looks like a difficult one, I haven't seen any duplicates yet too
[19:51] <Arby> mvo: oh sorry. I may have marked 186465 wrongly then
[19:51] <mvo> Arby: no problem, I will check and update the status then
[19:53] <Arby> mvo: what do you want me to do with 212020, assign to python-apt or just leave it alone for now?
[19:54] <mvo> Arby: I would say leave for now, I will inspect the code to see if I can find obvious mistakes in my threading code
[19:55] <Arby> ok
[19:55] <prana> james_w: it seems like a bug that someone else should fix, not ubuntu
[19:57] <james_w> prana: that's not what wontfix would mean here I think.
[19:57] <james_w> we would normally leave it confirmed or triaged in Ubuntu and add an upstream watch.
[19:57] <james_w> asking for them to forward it is a good idea though.
[20:00] <Arby> mvo: next one is bug 211978.
[20:00] <ubotu> Launchpad bug 211978 in update-manager "do-release-upgrade -d doesn't work immediately after running do-release-upgrade" [Undecided,New] https://launchpad.net/bugs/211978
[20:01] <Arby> dapper -> hardy server upgrades should work yes?
[20:02] <Arby> ah nevermind
[20:02] <mvo> Arby: yeah, looks like a bug in update-manager-core, I milestoned it and prepare a fix
[20:02] <Arby> yeah I just saw the confirmed lavel
[20:02] <Arby> *label
[20:02] <Arby> my bad
[20:03] <prana> james_w: as far as I know, git does not have a bug tracker. so what should be done in that case?
[20:03] <prana> (i asked on #git and they said, e-mail the git dev list.)
=== jacobmp92 is now known as jacob
[20:08] <prana> james_w: also, i am not completely convinced its a bug versus some oddness in handling the particular svn configuration the user reported.  (git-svn, as far as I know, relies on certain conventions in svn usage, that this config might not match.)
[20:23] <crashsystems> has anyone taken a look at bug #204420?
[20:23] <ubotu> Launchpad bug 204420 in hwtest "hwtest-gtk "crashes" and consumes 100% cpu power" [Undecided,New] https://launchpad.net/bugs/204420
=== txwikinger is now known as txwikinger2
=== txwikinger2 is now known as txwikinger
[20:33] <james_w> prana: yeah, they use the list.
[20:34] <prana> james_w: so how would we add an upstream watch?
[20:34] <james_w> I don't know if you can do it with mailing lists, bdmurray do you know?
[20:36] <james_w> prana: I've just read it and I think they should definitely take it to the mailing list.
[20:36] <james_w> you can ask them to report back with any findings.
[20:36] <prana> james_w: and leave it as incomplete?
[20:38] <james_w> I don't know about that. I would go for confirmed so that it doesn't expire, but I'm not sure.
[20:38] <james_w> or just New perhaps.
[20:40] <bdmurray> james_w: I saw a box where you have an option of saying you "I have already emailed an upstream bug contact:"
[20:40] <james_w> ah, I think I've seen that too.
[20:40] <bdmurray> I'm not quite certain what that does exactly though
[20:41] <james_w> if you enter an empty upstream task and then click the arrow to edit it you are given several options.
[20:41] <bdmurray> Hmm, it is a odd placeholder
[20:42] <bdmurray> shows up like "'Bug tracker at mailto:bob@localhost.com'"
[20:43] <james_w> it would be useful to be able to have a url of the mailing list archives there as well, so that you can find any discussion if you are interested.
[20:43] <james_w> I don't know if that would work.
[20:44] <bdmurray> I believe launchpad does some sanity checking on urls
[20:45] <james_w> yeah, bug tracker watches are quite restrictive I understand, I think it would be useful to be less restrictive here.
[20:48] <Arby> a little help on bug 208112 please, does restricted-drivers-manager lock the dpkg database at all?
[20:48] <ubotu> Launchpad bug 208112 in update-manager "first update fails after fresh hardy install" [Undecided,Incomplete] https://launchpad.net/bugs/208112
[20:48] <prana> james_w: huh. i'll leave it as incomplete for now and ask him to follow up.
[20:50] <prana> Looking at bug 203594; should it be set to triaged/low?
[20:50] <ubotu> Launchpad bug 203594 in xmonad "xmonad does not have xinerama/twinview support - possibly a libgch6-x11 problem" [Undecided,Confirmed] https://launchpad.net/bugs/203594
[20:51] <james_w> Arby: it will do if it is updating it or installing something.
[20:52] <Arby> james_w: ok thanks
[20:55] <mvo> Arby: it might be a apt-get update in the background, its certainly not good usability that it gives this error
[20:56] <Arby> mvo:  I've asked the user if they asked r-d-m to do any installation
[20:56] <mvo> yeah, that sounds good
[20:56] <mvo> thanks
[20:57] <Arby> surely it shouldn't lock the database just to report that action might be necessary
[20:57] <Arby> at least in theory
[20:58]  * mvo nods
[20:58] <Arby> although I suppose it has to check the availability of packages
[20:59] <mvo> yeah, but it can do this without locking
[21:05] <prana> can someone set bug 208894 to wishlist?
[21:05] <ubotu> Launchpad bug 208894 in mercurial "mercurial-1.x upgrade" [Undecided,New] https://launchpad.net/bugs/208894
[21:09] <blueyed> prana: done, also added the upgrade tag. If you want to have it in Hardy, you need to get a FeatureFreezeExcpetion for it (see wiki.ubuntu.com)
[21:13] <prana> blueyed: so looks like i'd have to learn how to prepare/build the updated package?
[21:14] <blueyed> prana: it would be easier, if it was in Debian already.. but it's not (in unstable). They have 0.9.5-3 (packaging changes) and I'm looking into filing a sync request for it.
[21:15] <prana> blueyed: yeah, i would have linked to an upstream debian request but i didn't see one.  unless you count http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472583
[21:15] <ubotu> Debian bug 472583 in mercurial "mercurial: consider enabling inotify extension in 1.0" [Wishlist,Open]
[21:16] <prana> i think since hardy is an LTS, it'd definitely be worth having the 1.0 release of mercurial; oddly i only noticed that the new version had been released b/c of this bug. :-)
[21:16] <Arby> mvo: bug 206452 seems to be a dupe of 186465 so it looks like this problem still exists :(
[21:16] <ubotu> Launchpad bug 206452 in update-manager "Gutsy to Hardy upgrade freezes" [Undecided,Incomplete] https://launchpad.net/bugs/206452
[21:17] <blueyed> prana: well, not really. Anyway, you need a FFe and can look into the details afterwards. I've just tried "uscan" on the Debian source and it updated fine to 1.0. You would need to do this, too and then generate diffstat etc to get an ACK from motu-release.
[21:19] <blueyed> prana: I'm not using hg myself, so the bar is quite high for me to jump into this, but I'd be glad to help you out.
[21:21] <blueyed> prana: the best would be to ask the Debian maintainer(s) nicely.. when has it been released?
[21:21] <prana> blueyed: looks like the hg release was on mar24.
[21:22] <prana> blueyed: it would probably be worth me learning how to do this in general but it seems like the best approach would be to have the debian maintainer do this one.
[21:22] <blueyed> prana: so maybe file a "Please package new upstream version 1.0" bug report in debian's bts?
[21:23] <blueyed> prana: if you want to try it yourself: https://wiki.ubuntu.com/PackagingGuide/Howtos/DebianWatch
[21:24] <blueyed> prana: ..but a sync request from the maintainer itself gets an ACK more likely.. ;)
[21:25] <prana> blueyed: yeah, i'll see if i can get a debian bug submitted.
[21:28] <warren_> https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/153943
[21:28] <ubotu> Launchpad bug 153943 in gdebi "Gdebi-kde uses massive amounts of memory!" [High,Confirmed]
[21:39] <prana> blueyed: Looks like uscan now automatically calls uupdate; though i can't figure out where the new dsc file comes from.
[21:39] <Arby> can someone confirm if bug 206104 is a dupe of bug 107779?
[21:39] <ubotu> Launchpad bug 206104 in update-manager "crashed with 'ascii' codec can't encode characters in position 0-10" [Undecided,New] https://launchpad.net/bugs/206104
[21:39] <ubotu> Launchpad bug 107779 in adept "Upgrade Tool Crashed" [Undecided,Confirmed] https://launchpad.net/bugs/107779
[21:39] <Arby> they look pretty similar but the traces aren't quite identical
[21:39] <blueyed> prana: you need to create the new .dsc yourself, using e.g. "debuild -S"
[21:40] <blueyed> prana: maybe that's a better topic for #ubuntu-motu though.. ;)
[21:41] <prana> blueyed: ok, cool. i created the debian bug and linked it to the ubuntu one.
[21:41] <mvo> Arby: riddel should know, but this one *might* be fixed already we should probably ask if he can try it agian
[21:42] <prana> blueyed: or rather, linked the ubuntu one to it; is acquiring the FFe something done in parallel?
[21:42] <mvo> Arby: I don't think its a duplicate
[21:43] <Arby> mvo ok
[21:43] <blueyed> prana: yes, you need to create a bug to request FFe, but need to provide the info (e.g. Upstream changelog, diffstat etc). I'd wait a day or two, to see if the Debian maintainer reacts.
[21:44] <Arby> mvo: you mean the window freeze? ask if who can try it again, the user?
[21:44] <prana> blueyed: cool, thanks again.
[21:44] <Arby> (sorry too many bugs on the go :) )
[21:44] <mvo> Arby: yes please, ask the one with the qt decode ascii problem if he can try again
[21:45]  * Arby <-- drowning under the fire hose :)
[21:45] <Arby> ok will do
[21:45]  * mvo hugs Arby
[21:45] <mvo> you do great! release time is terrible for update-manager bugreports
[21:46]  * Arby dives back in
[21:46] <mvo> I need to go to sleep now, but I will be followup on it tomorrow, thanks again for your help :)
[21:46] <Arby> your welcome
[21:47] <Arby> if I can make a dent in the list it's time well spent
[21:48] <prana> alright, enough ubuntu bugs for today; maybe will play with learning about generating ffe requests later.
[22:02] <Arby> ok that's enough for me I'm off for the night
[22:03] <Arby> have fun folks
[22:44] <emgent> hello people
[22:45] <emgent> someone know well python-launchpad-bugs?
[22:45] <emgent> python-launchpad-bugs support in anteater have some problem, and i`d like a little help for fix it
[22:46] <emgent> https://code.edge.launchpad.net/~ubuntu-whitehat/ubuntu-whitehat-project/uwht.dev
[22:46] <emgent> bdmurray? :)
[22:47] <bdmurray> emgent: looking
[22:47] <emgent> thanks :)
[22:47] <bdmurray> what happens?
[22:47] <emgent> seems not send info
[22:52] <bdmurray> emgent: you might need a "bug.commit" in there
[22:52] <blueyed> emgent, bdmurray: yes.
[22:53] <emgent> oh shit
[22:53] <emgent> bdmurray: blueyed thanks :)
[22:53] <bdmurray> emgent: no problem