[00:19] <hggdh> vish: there?
[00:38] <dota> hggdh: thanks for the session today
[00:44] <hggdh> dota: welcome, I hope it helped
[00:45] <dota> hggdh: it will i plan to run a bug jam on saturday for the first time
[00:51] <hggdh> dota: perfect!
[00:52] <hggdh> and there will be people here, and at the community channels that will help you on any doubt (I will not be in, am busy elsewhere)
[02:42] <vish> hggdh: hi..
[03:05] <RedSingularity> Anyone available to stamp a "triaged" for me?  bug 742101
[03:05] <ubot4`> Launchpad bug 742101 in update-manager (Ubuntu) "update-manager can't handle sources.list containing deb [arch=$arch] style lines (affects: 1) (dups: 1) (heat: 18)" [Undecided,Confirmed] https://launchpad.net/bugs/742101
[03:06] <paultag> RedSingularity: marked triaged / medium
[03:07] <RedSingularity> paultag: thanks buddy :)
[03:07] <paultag> RedSingularity: sure thing champ :)
[03:07] <paultag> RedSingularity: good to see the bug work ;)
[03:30] <trinikrono> hey can someone look at bug 424021 i believe it can be set to triaged and priority low
[03:30] <ubot4`> Launchpad bug 424021 in checkgmail (Ubuntu) "Popup messages sometimes appears on the top when the applet is on the bottom. (affects: 3) (heat: 16)" [Undecided,Confirmed] https://launchpad.net/bugs/424021
[03:31] <trinikrono> i read also that the bug should be triaged before it is sent upstream can a mentor confirm this for me?
[03:32] <trinikrono> ddecator: ping :D
[03:47] <duanedesign> hello trinikrono
[03:48] <trinikrono> :D hi duanedesign
[03:48] <trinikrono> i am wondering if the bug has enough info to be considered triaged
[03:50] <duanedesign> trinikrono: i dont suppose you are running Lucid?
[03:50] <trinikrono> well i am
[03:51] <duanedesign> ahh
[03:51] <duanedesign> and are you affected by this?
[03:51] <trinikrono> not me personally it behaves quiet nicely
[03:51] <trinikrono> thats why i am wondering what to do with this bug
[03:52] <trinikrono> but another reporter confirmed it
[03:52] <trinikrono> i dont think a bug can be triaged if it is sometimes
[04:24] <rav-> Bug #744645  seems to be bug of moonlight and not firefox. so should i mark it invalid ?
[04:24] <ubot4`> Launchpad bug 744645 in firefox (Ubuntu) "firefox with Moonlight plugin hangs (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/744645
[04:28] <duanedesign> rav-: moonlight-plugin-mozilla
[04:28] <rav-> thnx
[04:28] <duanedesign> thank you
[05:01] <trinikrono> duanedesign: im here
[05:01] <trinikrono> went for a little nap
[05:09] <duanedesign> trinikrono: no worries
[05:10] <duanedesign> trinikrono: there was a bad netsplit, was not sure if you were still on :)
[05:10] <trinikrono> lol
[05:10] <trinikrono> they cant cut me
[05:11] <trinikrono> duanedesign: the question i have is
[05:11] <trinikrono> is this bug considered triaged?
[05:12] <duanedesign> if you want to forward it upsream http://sourceforge.net/tracker/?group_id=137480&atid=738663
[05:33] <trinikrono> duanedesign: i know its bug tracker
[05:33] <trinikrono> do you think the bug can be set to triaged
[05:37] <duanedesign> trinikrono: i do not know what else could be added to it
[05:37] <duanedesign> trinikrono: i think that is all that can be done to it here
[05:38] <duanedesign> trinikrono: so yes
[05:38] <trinikrono> duanedesign: one question, should the bug be triaged before it is reported upstream
[05:39] <trinikrono> i read that in a wiki page earlier
[05:39] <trinikrono> so thats why i wanted it to be triaged first
[05:40] <duanedesign> trinikrono: yes, they should be triaged before sent upstream
[05:40] <micahg> triaged, but not necessarily marked as such
[05:41] <trinikrono> hello micahg
[05:42] <nigelb> so  you're going to start a new distro?
[05:42] <trinikrono> so can some triage/low the report for me?
[05:42] <nigelb> ugh, sorry
[05:42] <trinikrono> :D
[05:42] <micahg> hi trinikrono
[05:54] <trinikrono> well can it be set to triaged for me pleased
[05:54] <trinikrono> please lol
[14:38] <charlie-tca> Thoughts on mentorship team a: if the mentees need to be given a package, can we give them nautilus or evolution to start with? Most should be using both of those. :-)
[14:56] <om26er_> if apport fails to retrace a bug we mark that bug as invalid, don't we?
[14:57] <pedro_> om26er_, nope, we ask to the reporter if they can get a backtrace manually
[14:57] <om26er_> hmm.. is there a stock reply for that pedro_ ?
[14:57] <pedro_> om26er_, only if it's firefox you can close it as invalid
[14:58] <pedro_> yes one sec
[14:58] <pedro_> https://wiki.ubuntu.com/Bugs/Responses#Missing%20a%20back%20trace <- om26er_
[14:58] <om26er_> aha, thanks pedro_ ;)
[14:58] <pedro_> om26er_, make sure to remove the Coredump.gz if its still in the bug report
[14:59] <pedro_> you're welcome
[14:59] <om26er_> yep just removed it
[16:00] <bdmurray> cyphermox: I saw you looking at bug 551809, or the upstream one at least, it seems to me that crash could occur in a lot of applications is that right?
[16:00] <ubot4`> Launchpad bug 551809 in gtk+2.0 (Ubuntu Maverick) (and 2 other projects) "gnome-settings-daemon crashed with SIGSEGV (affects: 478) (dups: 148) (heat: 2222)" [High,Triaged] https://launchpad.net/bugs/551809
[16:03] <cyphermox> bdmurray, could occur in any app that made use of libappindicator and updates icons regularly -- bug afaik this should be "fixed" in natty now, barring some issues with the ubuntu-mono icons now on the "Classic Gnome" session
[16:04] <bdmurray> cyphermox: that's could but I'd imagine there are still some duplicates hiding in Launchpad and a bug pattern could be written to stop further crash reports
[16:04] <bdmurray> cyphermox: er, that's good!
[16:13] <bdmurray> cyphermox: do you what would be good to look for in the stacktrace?
[19:57] <njin> hello, is Migration Assistant disabled ?
[20:18] <njin> chrisccoulson: hello, is migration assistant disabled?
[20:46] <psusi> hrm.. I can't seem to find documentation on the proper usage of the assigned to field
[20:48] <yofel> psusi: assigned to on what? launchpad? That would be the person working on a fix
[20:50] <psusi> yofel: that's what I thought... and the status should be in progress shouldn't it?
[20:50] <psusi> so a bug that has been incomplete and assigned to a team for 6 tears obviously has something wrong, right?
[20:50] <yofel> yes
[20:50] <psusi> years rather
[20:50] <yofel> well, if it's the ubuntu-desktop team, they used that to track their bugs ages ago
[20:50] <psusi> bug #30015
[20:50] <ubot4`> Launchpad bug 30015 in gnome-pilot (Ubuntu) "should automatically detect attached devices and use the apporpriate port (heat: 1)" [Wishlist,Incomplete] https://launchpad.net/bugs/30015
[20:52] <yofel> ask seb on why he reassigned that back then, but that's not correct by todays policy
[20:52] <psusi> so I thought that the policy was assigned and in progress should go hand in hand... but I can't find it written anywhere now... am I just not finding it or does this need documented?
[21:37] <palhmbs> that xulrunner --gre-version bug when installing with synaptic is causing me problems again.
[21:42] <palhmbs> ps afg -- http://pastebin.com/Ejy4nryr
[21:44]  * micahg hides
[21:45] <palhmbs> heh - I haven't bothered to report this, because I figure I prolly caused it somehow
[21:45] <micahg> chrisccoulson: any ideas ^^
[21:46] <palhmbs> I've killed synaptic and rm the lock file - then run dpkg --configure -a
[21:46] <hggdh> psusi: of old different teams had different policies on bugs
[21:46] <palhmbs> which seems to fix it
[21:46] <micahg> palhmbs: can you attach strace and see where it's stuck?
[21:46] <palhmbs> I got told to run gdb and do a traceback
[21:47] <palhmbs> last time
[21:47] <micahg> palhmbs: that works too
[21:47] <palhmbs> how would I roll back the changes I just made so that  I could give you that?
[21:47] <micahg> palhmbs: apt doesn't have a good way to roll back, is it still stuck?
[21:48] <palhmbs> nope
[21:48] <micahg> palhmbs: what arch/ubuntu version again?
[21:48] <palhmbs> maybe I'll wait till xulrunner upgrades again - it seems to happen *every* time
[21:48] <palhmbs> ubuntu 10.10
[21:48] <palhmbs> xubuntu flavor
[21:48] <micahg> palhmbs: you could just downgrade xulrunner to the release version and upgrade again
[21:48] <micahg> palhmbs: i386 or amd64?
[21:49] <palhmbs> yeah I think I remember how to downgrade - I'll try that - i386 (32-bits)
[21:53] <palhmbs> er - dpkg -r xulrunner-1.9.2
[21:53] <palhmbs> dpkg: dependency problems prevent removal of xulrunner-1.9.2
[21:53] <palhmbs> how then?
[21:53] <palhmbs> i've looked into dpkg --force-help and am left clueless
[21:54] <micahg> palhmbs: you can do something like sudo apt-get install xulrunner-1.9.2=1.9.2.10+build1+nobinonly-0ubuntu1
[21:55] <palhmbs> oh - well if that's the easiest way, I like it :D
[21:58] <palhmbs> ok if I run gdb with synaptic how do I make sure that I get enough scrollback in my terminal - shall I redirect output to a file, if so how
[21:59] <roadmr> palhmbs: try using the script command, it will log everything you see (and type) into a file
[22:02] <palhmbs> ok that looks helpful - script -c gdb synaptic -f /tmp/synaptic_trace.txt --- that about it?
[22:03] <roadmr> palhmbs: yep, looks right to me
[22:03] <roadmr> palhmbs: you can just run script /tmp/whatever.log, you get back a shell, and everything you do up until you type exit will be logged
[22:03] <roadmr> palhmbs: so you're not limited to a single command - an entire interactive session can be logged
[22:06] <trinikrono> has anyone ever seen this in a xsession log? (nautilus:1202): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
[22:06] <trinikrono> i am working on bug 698877
[22:06] <ubot4`> Launchpad bug 698877 in nautilus (Ubuntu) "Rubbish bin won't empty (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/698877
[22:06] <trinikrono> thanks!
[22:13] <palhmbs> nuts - it didn't fail to install whilst running gdb.
[22:13] <palhmbs> I'll defer this till I have to upgrade xulrunner again.