[01:12] <kakemann> should bug 377201 be set as a duplicate of bug 383271?
[01:12] <ubot4> Launchpad bug 377201 in audacious "update audacious && audacious-plugins to 2.0.1" [Undecided,New] https://launchpad.net/bugs/377201
[01:12] <ubot4> Launchpad bug 383271 in audacious "Please merge audacious 2.0.1-1 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/383271
[01:14] <BUGabundo> kakemann: I guess so
[01:14] <BUGabundo> hey ogasawara
[01:14] <bcurtiswx> kakemann: is 2.0.2 and 2.0.1-1 different?
[01:14] <bcurtiswx> sorry 2.0.1 and 2.0.1-1
[01:15] <kakemann> hmm, I have to look into that
[01:15] <kklimonda> kakemann: yes - you can set it as a duplicate
[01:15] <bcurtiswx> ah, because debain marks first build as -1 right?
[01:15] <kklimonda> yeah
[01:15] <kakemann> ok, will do
[01:16] <kakemann> thanks
[01:16] <bcurtiswx> thanks kklimonda
[04:15] <madmax_X> hello all
[06:15] <dholbach> good morning
[06:27] <e-jat> morning dholbach
[06:28] <dholbach> hiya e-jat
[06:28] <e-jat> :)
[06:40] <dholbach> hola ara
[06:40] <ara> good morning dholbach
[07:36] <thekorn_> good morning bugsquad
[08:31] <xteejx> bug 383768 is this a good idea to force the update?
[08:31] <ubot4> Launchpad bug 383768 in mktemp "[karmic] The essential package 'mktemp' is marked for removal." [Undecided,Confirmed] https://launchpad.net/bugs/383768
[08:38] <Hobbsee> no
[08:39] <xteejx> Hobbsee, thanks :) Was kinda thinking it was a stupid idea, I assume they'll resolve it?
[08:39] <Hobbsee> yes.
[08:39] <Hobbsee> and that bug has to be a dupe
[08:39] <Hobbsee> the master is pro bably under coreutils
[08:39] <xteejx> cool, ps good morning everyone :)
[08:40] <xteejx> I tagged it as metabug
[08:43] <savvas> hm..
[08:44] <savvas> I think it is update-manager that must learn to ignore that one
[08:44] <xteejx> I did look for dupes but couldnt find any
[08:46] <savvas> great job! :)
[08:46] <xteejx> thanks :D
[08:46] <randomaction> this seems to cause build failures for newly uploaded packages
[08:47] <savvas> randomaction: the chroot problem?
[08:47] <randomaction> yes
[08:47] <savvas> I've noticed it, but geser at #ubuntu-motu recommended to wait for a while and retry the build
[08:48] <savvas> +Conflicts: mktemp
[08:49] <savvas> +Replaces: mktemp
[08:49] <savvas> I wonder if it should have "Provides: mktemp" ?
[08:51] <geser> savvas: I haven't looked at the specific one chroot problem but most such problems are transient unless they appear in bulk
[08:51] <savvas> ok :)
[08:57] <xteejx> guys, does that mean that the problem will just float past and be fixed one day when people update?
[08:59] <savvas> xteejx: it should :)
[08:59] <xteejx> savvas, Ok cool :)
[09:00] <savvas> It's either coreutils fault or update-manager.. or they should remove mktemp's "Essential"
[09:00] <xteejx> I didn't expect a stable system hehe, but I hear quite a lot of UI improvements are going into karmic
[09:00] <savvas> hm.. that last one seems great :P
[09:01] <xteejx> no point asking me - I haven't a clue about MOTU lol
[09:03] <mvo> savvas: I check it out, I can make u-m ignore mktemps essential
[09:04] <seb128> mvo: the issue should be fixed in debian now, I will do an autosync run
[09:04] <savvas> mvo: no no, it's fixed in coreutils - dholbach replied :)
[09:05] <dholbach> seb128: I think it's synced already, it needs to be built manually though because the chroots are busted
[09:05] <savvas> dholbach: wouldn't it be better if mktemp was demoted from "Essential" ? Or that wouldn't make a difference?
[09:05] <seb128> dholbach: everything has been synced or just coreutils, ie should I still do a normal daily autosync?
[09:06] <dholbach> seb128: I don't know
[09:06] <dholbach> savvas: <wgrant> coreutils contains and now Conflicts with mktemp.
[09:06] <dholbach>  apt doesn't like removing Essential packages, which mktemp is.
[09:06] <dholbach>  A fixed coreutils has been uploaded (producing a transitional non-Essential mktemp binary), but it needs to be built manually.
[09:06] <seb128> alright
[09:07] <savvas> ah I get it, mktemp is orphaned
[09:07] <wgrant> Right.
[09:08] <wgrant> Presumably in a release or two coreutils will drop the mktemp binary, and all will be good.
[09:08] <savvas> well the coreutils workaround ought to work :)
[09:09] <wgrant> But for now we just have to wait. Is anybody but infinity sufficiently empowered to fix this?
[09:11] <xteejx> how soon is "soon to be processed"?
[09:12] <xteejx> and how is it going to work the fix, will it just "work" or is there anything extra thats needed to be done?
[09:12] <wgrant> The coreutils/mktemp issue will vanish. Nothing special will need to be done.
[09:13] <xteejx> wgrant, just upgrade as normal then? :)
[09:13] <wgrant> Yes.
[09:13] <xteejx> cool
[09:28] <Ekushey> i filed a new bug, can someone take a look at it? it's # 383444
[09:28] <xteejx> bug 383444
[09:28] <ubot4> Launchpad bug 383444 in tzdata "Timezone change for Bangladesh" [Undecided,New] https://launchpad.net/bugs/383444
[09:34] <wgrant> I'm impressed.
[09:34] <wgrant> They introduce it without a definite date of termination?
[09:35] <Ekushey> wgrant, it's still undecided
[09:35] <Ekushey> btw it's my first bug report, i hope it looks OK?
[09:36] <wgrant> That's OK.
[09:36] <Ekushey> ok, that's a relief then
[09:36] <wgrant> In future I wouldn't use tinyurl-like services, though.
[09:36] <Ekushey> will remember that :)
[09:37] <wgrant> Hmm. 2009h is still the latest.
[10:04] <askand1> kklimonda: hi, I can not upgrade to 1.7 from your ppa, only partial upgrade
[10:04] <askand1> any idea on why?
[10:11] <askand1> kklimonda: ah nevermind, solved it, what did you say was the name of the new debugpackage? :)
[11:32] <siretart> hey folks
[11:32] <siretart> I'm currently preparing a new upload of vlc and wanted to go through the list of vlc bugs
[11:33] <siretart> unfortunately, the bug list is filled up with 'triaged' crasher bugs, which I'd like to exclude somehow
[11:33] <siretart> is that possible?
[11:33] <siretart> I don't have the time and energy to process all those crasher bugs, but I want to see what 'other' 'regular' bugs have been filed
[11:34] <seb128> siretart: not really, you can filter out the triaged bugs
[11:35] <siretart> that list is rather short
[11:35] <siretart> I do remember that there are some bugs in 'triaged' status which are fixed in this new version
[11:35] <siretart> but I cannot locate them
[11:37] <seb128> no easy way to do what you want no
[11:37] <siretart> this means the buglisting of vlc is useless to me as I cannot handle it
[11:38]  * Hobbsee wonders if bughelper will help with that
[11:38] <seb128> siretart: the issue is just the number of bugs?
[11:39] <siretart> more my inability to sort, filter and handle the large amount of bugs
[11:39] <seb128> you are not really trying apparently
[11:39] <seb128> you just focus on one thing you can't do
[11:39] <siretart> hm. probably
[11:39] <seb128> all the crash bug are importance medium
[11:40] <siretart> I'm currently checking the bugs wich are 'fix committed'
[11:40] <seb128> so you can review everything which is not medium for example
[11:40] <siretart> there are 4 bugs
[11:40] <siretart> okay, I'll try that next
[11:41] <seb128> "show bugs that are resolved upstream" lists 17 bugs
[11:41] <seb128> you might want to review that list too
[11:42] <siretart> three triaged bugs with importance not medium.. :/
[11:42] <seb128> nobody is looking at vlc bugs
[11:42] <siretart> :/, because the bug I expected is not there. but still a few more bugs
[11:42] <siretart> yes, thats unfortunate
[11:43] <seb128> if you do a new version upload you can probably close quite some of those bugs which have an upstream task closed
[11:44] <siretart> okay, will check them
[11:51] <siretart> okay, so the idea is to filter for bugs that need upstreaming, then upstream them in batch, and on new upstream version check what bugs can be closed, right?
[11:58] <seb128> siretart: yes
[12:12] <siretart> okay, I've now done so
[12:12] <siretart> unfortunately, the buildds are broken ATM, so I cannot testbuild
[13:04] <askand1> kklimonda_: transmissions keeps crashing : /
[13:10] <askand1> How do I tell gdb to ignore "Program received signal SIGPIPE, Broken pipe."?
[13:14] <dholbach> try          (gdb) help handle
[13:19] <askand1> dholbach: thanks handle SIGPIPE nostop noprint nopass seems to work
[13:19] <dholbach> rock on
[13:45] <kklimonda_> askand1: the same backtrace? or similar?
[13:46] <kklimonda_> askand1: and have you tried 1.70?
[13:51] <askand1> kklimonda_: I am trying now with 1.70, got a sigpipestop but added "handle SIGPIPE nostop noprint nopass" and trying again now
[15:09] <savvas> mvo: could you take a look at an older merge request for software-properties (KDE)? It fixes some unicode text strings: https://code.edge.launchpad.net/~medigeek/software-properties/kde_deb_and_deb-src_unicode_fix/+merge/4956 diff: http://tinyurl.com/m26xuw
[15:10] <savvas> " some unicode text strings" = a unicode bug
[15:10] <savvas> I can't seem to find the bug number right now though.. hm..
[15:12] <savvas> mvo: found it, bug #102773 - the last comments, the software sources list appears "gibberish": http://launchpadlibrarian.net/24255059/adept1.png
[15:12] <ubot4> Launchpad bug 102773 in software-properties "l10n broken in software-properties" [Medium,Fix released] https://launchpad.net/bugs/102773
[15:14] <mvo> savvas: sure, I do this now
[15:14] <savvas> thanks :)
[15:16] <stpere>  /win 21
[15:16] <stpere> oops, sorry :)
[15:16] <savvas>  you lose!
[15:16] <savvas>  :p
[16:27] <jdstrand> dholbach: hi! looking at bug #383696 I see you unsubscribed the sponsors team. looking at the bug, it seems it needs a sponsor. am I missing something?
[16:27] <ubot4> Launchpad bug 383696 in kio-gopher "Sync kio-gopher 0.1.3-1 (universe) from Debian unstable (main)." [Undecided,Confirmed] https://launchpad.net/bugs/383696
[16:28] <dholbach> jdstrand: "this sync is perfect"
[16:28] <dholbach> I took this as an ACKed sync request
[16:28] <dholbach> ubuntu-archive is subscribedx
[16:28] <jdstrand> dholbach: yes, but I didn't see that he was a sponsor perse
[16:28] <dholbach> so all's good, no?
[16:28] <dholbach> ah
[16:28] <dholbach> right
[16:28] <dholbach> he dropped out of ~motu
[16:28] <dholbach> nevermind
[16:28] <dholbach> I'll ACK it
[16:29] <dholbach> I reviewed it myself
[16:29] <jdstrand> dholbach: excellent, thanks
[16:29] <dholbach> done
[16:29] <bcurtiswx> ACK?
[16:29] <dholbach> acknowledged, approved, OK :)
[16:29] <bcurtiswx> ahh, :-) ok thx
[16:30] <dholbach> :-)
[16:32] <bcurtiswx> so does an ACK mean its triged, or fix released or..?
[16:32] <dholbach> bcurtiswx: this isn't a real bug, but more a "workflow bug"
[16:32] <dholbach> basically it's there to organise work between groups of developers
[16:32] <dholbach> it's safe to ignore it
[16:33] <dholbach> if you want to know more about it, check out https://wiki.ubuntu.com/SyncRequestProcess
[16:33] <bcurtiswx> dholbach: ok j/w here.  i know to stay away from syncs as a triager.  Im always interested in learning more.. thx
[16:33] <dholbach> cool :)
[16:39] <xteejx> Who do I get in contact for pushing a bug through with the accessibility team, its a feature that has been broken for quite some time....bug 377060
[16:39] <ubot4> Launchpad bug 377060 in espeak "[jaunty karmic] espeak missing words and phonemes from sentences" [Low,Confirmed] https://launchpad.net/bugs/377060
[16:40] <dholbach> themuso probably, but he's in Australia so hopefully sleeping
[16:47] <xteejx> dholback, oh ok daniel, it should be ok to leave it on LP shouldn't it? I mean it will get seen to, right?
[16:47] <xteejx> actually forget that, stupid question
[16:48] <xteejx> !julius
[16:48] <ubot4> Factoid 'julius' not found
[16:48] <dholbach> xteejx: I guess so, yes - but you can make sure and talk to him on Monday about it
[16:48] <xteejx> dholbach, Will do, thanks :)
[18:49] <bcurtiswx> I <3 showing up at work when nobody else does... it means i can leave early!!!!  bbl
[19:46] <hggdh> who takes care of devicekit?
[19:50] <bdmurray> hggdh: I believe pitti is familiar with it
[19:52] <hggdh> bdmurray, thanks
[19:52] <hggdh> now I have to find the bloody bug... lost it :-(
[20:13] <xteejx> bdmurray, Sorry about that bug report earlier
[20:15] <bcurtiswx> is there an IRC page for the community council?
[20:15] <kklimonda> irc page?
[20:22] <bcurtiswx> IRC channel
[20:22] <bcurtiswx> i've got web pages on the brain.. sorry
[20:22] <bcurtiswx> lol
[20:25] <andersk> Can someone set the importance of bug 382608 to Low?
[20:25] <ubot4> Launchpad bug 382608 in openafs "Sync openafs 1.4.10+dfsg1-2 (universe) from Debian unstable (main)." [Undecided,New] https://launchpad.net/bugs/382608
[20:26] <askand> Hi, I have a way to get a segfault in GDB 100% on my computer, can someone please try if it's just me? Move .mozilla to .mozillabackup or something, run: 'firefox -g 2>&1 | tee firefoxfresh.txt'  and then 'run'
[20:28] <dtchen> andersk: why low?
[20:36] <kklimonda> askand: indeed, it crashes
[20:37] <askand> kklimonda: ok would you mind sending the bugreport due to bug 314212 :)
[20:37] <ubot4> Launchpad bug 314212 in python-apt "Apport unable to report crash -  urlopen error timed out" [Medium,Confirmed] https://launchpad.net/bugs/314212
[20:37] <kklimonda> askand: btw, how is transmission 1.70? has it crashed yet? :)
[20:38] <askand> no, one of the few apps on my system that are rocksolid atm :)
[20:39] <kklimonda> send report for gdb? what does it have in common with this error?
[20:39] <kklimonda> damn, it's getting cold again o.O
[20:39] <kklimonda> askand: let's hope it doesn't crash then.. ;)
[20:40] <askand> kklimonda: I can't send it with report because of the timeout error :)
[20:40] <askand> apport*
[20:40] <kklimonda> oh, i see
[20:45] <kklimonda> askand: looks like it's already reported: bug 258578
[20:45] <ubot4> Launchpad bug 258578 in gdb "gdb crashed with SIGSEGV in iterate_over_threads()" [Medium,New] https://launchpad.net/bugs/258578
[20:46] <askand> indeed :)
[20:51] <BUGabundo> guud evening
[20:51] <kklimonda> hey
[20:52] <BUGabundo> hey kklimonda
[20:55] <andersk> dtchen: it fixes an OpenAFS kernel crash with kernel >= 2.6.27, (Debian bug #528785), so it is certainly important to OpenAFS users, but I won't continue to nitpick.
[20:55] <ubot4> Debian bug 528785 in openafs-modules-source "openafs-modules-source: Random kernel crashes when accessing AFS" [Important,Fixed] http://bugs.debian.org/528785
[20:58] <dtchen> andersk: right, that much is understood, but sync requests generally are wishlist
[20:58] <dtchen> andersk: effectively, however, importance is largely ignored when overriding deltas
[21:00] <andersk> Okay.  I didn't see that documented anywhere (e.g. <https://wiki.ubuntu.com/SyncRequestProcess> doesn't mention it; maybe it should).
[22:07] <bcurtiswx> ok, so since i am still not used to the apport-collect, it just collects the basic info from the persons computer for the bug right. bug #384060 im working with, and i can not reproduce the issue
[22:07] <ubot4> Launchpad bug 384060 in ubuntu "gnome-ppp needs sudo" [Undecided,New] https://launchpad.net/bugs/384060
[22:08] <bcurtiswx> does BUGNUMBER need a # ?
[22:08] <BUGabundo> nopwe
[22:08] <BUGabundo> $ apport-collect BUGID
[22:09] <BUGabundo> IF the bug has a package assign
[22:09] <bcurtiswx> that it does
[22:09] <BUGabundo> and you can also add data from another package to a bug that doesn't mention it
[22:09] <BUGabundo> $ apport-collect BUGID -p OTHERPACKAGE
[22:09] <BUGabundo> oh and user must be running a recent ubuntu version and have -updates enabled
[22:10] <BUGabundo> since -collect hooks came too late
[22:10] <bcurtiswx> its karmic
[22:10] <bcurtiswx> gnome-ppp
[22:12] <BUGabundo> ok
[22:12] <BUGabundo> let me try it
[22:12] <BUGabundo> don't even have it
[22:13] <bcurtiswx> lol
[22:14] <bcurtiswx> bdmurray: in the greasemonkey script for user responses.. with the "vague" response, i find myself having to ask for package and ubuntu versions an awful lot.  do you think you could add those to the responses in a future release?
[22:17] <bdmurray> bcurtiswx: They way I see it vague should only be used for the lowest quality bugs.  I'd generally try to use "Collect It" as much as possible.
[22:17] <bcurtiswx> bdmurray: ok, thx
[22:17] <bdmurray> Does that make sense?
[22:18] <bcurtiswx> yeah, does collect work with hardy/intrepid/jaunty/karmic?
[22:18] <bdmurray> No, no, yes, yes! ;-)
[22:19] <bcurtiswx> so, for the no,no vague a better response?
[22:22] <bdmurray> Well you said you have to ask for the ubuntu version a lot so I'm not sure how'd you know if it was Hardy or Intrepid, but I could do that.
[22:23] <BUGabundo> bcurtiswx: to answer you Q: gnome-ppp is not asking me to be root
[22:24] <bcurtiswx> BUGabundo: thats what i had happen too, is it supposed to ask for root permissions?
[22:25] <bcurtiswx> bdmurray: yeah, good point.. wtg brain <facepalm>
[22:28] <BUGabundo> bcurtiswx: maybe. if it is going to change your connection... but I don't think it needs too
[22:28] <BUGabundo> I can operate *over* to original Link, so it can run on userland
[22:28] <BUGabundo> bcurtiswx: ask asac
[22:29] <bcurtiswx> asac: so you don't have to scroll up, should gnome-ppp ask for a sudo password when called from a user level by default ?
[22:31] <bcurtiswx> BUGabundo: so the user is experiencing a bug, as we have verified that it works ....AFAIK as designed
[22:31] <BUGabundo> bcurtiswx: better ping asac on #ubuntu-mozillateam. he is not so much active here
[22:31] <BUGabundo> bcurtiswx: well karmic is unstable
[22:32] <BUGabundo> he better be running uptodate before filling bugs
[22:32] <bcurtiswx> BUGabundo: i tested on karmic... works "fine"
[22:33] <BUGabundo> me too
[22:33] <bcurtiswx> i did forget to ask if hes fully updated.. but the apport collect will tell us right away if anythings not updated
[22:33] <BUGabundo> but you never know what the user actually did on the other side
[22:33] <BUGabundo> or even if he can reproduce it for sure
[22:33] <BUGabundo> or its just ear say
[22:33] <BUGabundo> bcurtiswx: ask him if it is reproduclbe
[22:34] <bcurtiswx> BUGabundo: k
[22:34] <plars> Would steps to reproduce + a legible photo of the panic and most of the stacktrace generally be considered sufficient for confirmed on a kernel bug? I know that text output of the full stacktrace would be preferable but I don't think he's been able to get that from his netbook
[22:35] <BUGabundo> plars: on shutdown? yes a pic is nice
[22:35] <plars> BUGabundo: it's not on shutdown, no
[22:35] <BUGabundo> plars: kernel devs tend to accept that
[22:35] <plars> ok
[22:59] <bcurtiswx> any here running kubuntu karmic ?
[23:00]  * BUGabundo hands "one" to bcurtiswx
[23:01] <bcurtiswx> can you test bug #384098
[23:01] <ubot4> Launchpad bug 384098 in openoffice.org "Some tables will not display" [Undecided,New] https://launchpad.net/bugs/384098
[23:01] <BUGabundo> no time sorry
[23:01] <BUGabundo> trying to fix U1
[23:01] <bcurtiswx> ok
[23:02] <bcurtiswx> i guess its time to break down and VM kubuntu
[23:03] <BUGabundo> eheh