[02:22] <strycore> Hi
[02:23] <strycore> maybe I haven't searched enough but I'm having trouble finding the procedure to get proper crash logs for nautilus
[02:24] <charlie-tca> if you can reproduce the crash and the logs are not /var/crash, use https://wiki.ubuntu.com/DebuggingProgramCrash to get a gdb backtrace
[02:30] <strycore> hmm ok, I think I've done this before, but nautilus is special, it restarts itself when it crashes
[02:30] <charlie-tca> do a "while application is running " retrace, maybe?
[02:31] <charlie-tca> I have run some apps for a few days, to get a valid backtrace
[02:31] <strycore> if I run killall nautilus && debug nautilus i get Program exited normally. (where debug is https://github.com/strycore/scripts/blob/master/debug )
[02:32] <charlie-tca> You can also install debugging symbols, and enable apport, so that when it crashes, you get an automatic crash file in /var/crash
[02:32] <strycore> ok, i've just installed the -dgb package, making it crash is the easy part :)
[02:41] <strycore> hmm reading the crash log, i can't seem to see any useful information, I'm sending it to Launchpad anyway
[02:45] <strycore> wait ... what ? "Report a bug about “ubuntuone-client”" ??
[02:50] <charlie-tca> did ubuntuone-client crash?
[02:50] <charlie-tca> Is that apport generated?
[02:51] <strycore> nope, it's only nautilus, it's bug #680968
[02:51] <ubot4> Launchpad bug 680968 in ubuntuone-client (Ubuntu) "nautilus crashed with SIGSEGV in g_str_hash() [ubuntuone_nautilus_observed_file_unref] (affects: 13) (dups: 13) (heat: 126)" [Medium,Triaged] https://launchpad.net/bugs/680968
[02:52] <charlie-tca> Nautilus crashed, but the cause of the crash was not anything broken in nautilus, but something in Ubuntuone-client instead
[02:54] <strycore> yes it's ubuntuone that made nautilus crash
[02:55] <strycore> i'm installing ubuntuone-client-dbg but i'm not sure I'll get more information about the crash
[02:57] <charlie-tca> Try installing debug symbols for libgobject, too
[02:57] <charlie-tca> if it has any
[02:58] <strycore> oh another crash and now "This is not a genuine Ubuntu package", I bet this is because I have nautilus-elementary installed ...
[03:01] <strycore> oh well, I'll ppa-purge it
[07:09] <bullgard> I get a kernel error message similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495674&trim=no . What package should I associate my error report to Launchpad to?
[07:09] <ubot4> Debian bug 495674 in alsa-utils "[udev] Driver 'pcspkr' is already registered, aborting..." [Minor,Open]
[08:07] <nobuto> I reported Bug #719170 and attached valgrind.log. But it doesn't seem to contain gconf part. Is there any additional thing I can do?
[08:07] <ubot4> Launchpad bug 719170 in gconf (Ubuntu) "Segmentation fault during processing triggers for gconf2 when installing some packages on LiveCD (affects: 1) (dups: 1) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/719170
[08:23] <trinikrono> any bug control ninjas online i would like a opinion about bug 355856
[08:24] <ubot4> Launchpad bug 355856 in firefox (Ubuntu) "follow system's toolbar preferences (heat: 4)" [Wishlist,Confirmed] https://launchpad.net/bugs/355856
[08:28] <vish> trinikrono: it needs to be sent upstream.. or linked to an existing upstream bug
[08:29] <trinikrono> upstream as in debian ,gnome or firefox vish?
[08:29] <vish> trinikrono: so you'd have to first search mozilla's bugzilla
[08:30] <vish> trinikrono: also..  firefox packaging is done by the Ubuntu mozilla team themselves, so debian does not apply to firefox
[08:32] <trinikrono> vish: well i am wondering about how it would interact with the system to get the preferences is that a gnome thing?
[08:33] <vish> trinikrono: well, the gnome prefs are saved in ~/.config folder, and firefox would just have to read it..
[08:34] <vish> trinikrono: this is quite an old known issue, so i would probably expect an existing bug in mozilla's tracker
[08:34] <vish> or it might be closed as a WONTFIX
[08:34] <trinikrono> vish: i will go looking for it
[08:45] <trinikrono> vish: i found one but its unconfirmed
[08:57] <trinikrono> i believe that it can be set to triaged and importance low, if you are still around vish
[09:16] <vish> trinikrono: done..
[09:16] <trinikrono> thanks
[09:16] <trinikrono> can you look at one more bug for me before i go to work ?
[09:18] <trinikrono> its bug 601986 i am not sure where too start
[09:18] <ubot4> Launchpad bug 601986 in linux (Ubuntu) "Disk driver problems on Toshiba NB305Netbook (affects: 5) (heat: 39)" [Undecided,Confirmed] https://launchpad.net/bugs/601986
[09:20] <vish> trinikrono: i'v got no idea either..
[09:20] <trinikrono> i still havent picked a package to stick on so my bugs are pretty random
[09:42] <seb128> jibel, hey
[09:42] <seb128> jibel, do you get that nautilus crash every time?
[09:48] <jibel> seb128, yes I do. It looks like the nautilus window needs to be maximized to crash.
[09:49] <seb128> jibel, I don't get the issue there, can you get me a stacktrace?
[09:49] <seb128> the bug one is useless
[09:50] <seb128> jibel, I just tried like 15 times it doesn't crash here
[09:50] <jibel> seb128, okay. I'll change the testcase it's not related to the way nautilus is launched. If I launch it from the command line it crashes too.
[09:51] <seb128> jibel, rather get me a stacktrace ;-)
[09:51] <jibel> seb128, indeed, it crashes on a netbook but not on a laptop, both running on i386.
[09:52] <seb128> weird
[09:52] <seb128> jibel, can you scp the .crash file somewhere when I can download it?
[09:52] <seb128> the retracers clean the bugs as duplicate and whipe the infos
[09:53] <seb128> it's a bit annoying when the master lacks details
[09:53] <seb128> it means we don't get those details from the new bugs
[10:03] <bullgard> I get a kernel error message similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495674&trim=no . What package should I associate my error report in Launchpad to?
[10:03] <ubot4> Debian bug 495674 in alsa-utils "[udev] Driver 'pcspkr' is already registered, aborting..." [Minor,Open]
[14:08] <jibel> charlie-tca, Hi, I don't understand your comment in bug 659577, you say it is fixed in bug 681518. My understanding is that it is fixed in Natty and may need a SRU in Lucid.
[14:08] <ubot4> Launchpad bug 659577 in xfce4-panel (Ubuntu) "xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself() this happens when i log out of xubuntu 10.10 (affects: 6) (dups: 6) (heat: 58)" [Medium,Incomplete] https://launchpad.net/bugs/659577
[14:08] <ubot4> Launchpad bug 681518 in xfce4-panel (Ubuntu) "xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself(). (affects: 1) (heat: 48)" [Medium,Fix released] https://launchpad.net/bugs/681518
[14:10] <kklimonda> which was the first ubuntu with grub2 installed by default?
[14:15] <charlie-tca> jibel: I never got a reponse on it being fixed in natty
[14:16] <charlie-tca> It was reproduced in both 10.10 and 10.04, but I don't know if actually got fixed in natty
[14:16] <jibel> charlie-tca, so 681518 shouldn't have been set to fix released ?
[14:20] <charlie-tca> Maybe I screwed the things up? The stacktraces did not match, so I could not dup #681518 to #659577.
[14:21] <charlie-tca> I will put the thing back to hoping for a sru if you think they should be the same thing.
[14:22] <jibel> charlie-tca, okay. I referred 659518 in the iso-tracker, that's the one the retracer think it is a duplicate of. Lets trust it this time.
[14:23] <charlie-tca> okay, and I should put it triaged, right?
[14:24] <charlie-tca> Hm, no, that should be fix-released with awaiting a sru, if it is fixed in natty
[14:24] <bcurtiswx> bdmurray, you there?
[14:24] <jibel> charlie-tca, correct.
[14:25] <charlie-tca> jibel: thanks for keeping me straight
[14:25] <jibel> charlie-tca, :-)
[14:37] <mr_pouit> charlie-tca: jibel: it's fixed in natty, because xfce4-panel has been rewritten and doesn't use libxfcegui4 anymore (and this is also why it can't be backported/sru'ed)
[14:40] <jibel> mr_pouit, thanks for confirming, I've added it to the isotracker as a failure in 10.04.2, now it's up to you if you want/can fix it there or not.
[15:07] <kklimonda> any idea how to check which one of two - grub or grub2 is installed in the mbr?
[15:10] <penguin42> yeuch
[15:10] <penguin42> probably not trivial
[15:15] <arand> kklimonda: well, you can read it with dd -> xxd, I reckon you'd ned documentation to tell which code comes from which though...
[15:16] <kklimonda> arand: right, I was hoping for a higher-level solution :)
[15:17] <arand> I'm not sure if bootinfo script does that, or if it just says "GRUB"
[15:18] <kklimonda> hmm, I'll have to check
[15:19] <arand> Looking at an example RESULTS.txt it doesn't seem so.
[15:21] <kklimonda> oh well, I've just asked a guy to reboot ;)
[15:22] <kklimonda> I'll if he shows up again
[15:22] <kklimonda> I'll have to wait and see*
[16:56] <njin> hello, can someone change status to medium instead low to bug 717690 thanks
[16:56] <ubot4> Launchpad bug 717690 in qemu-kvm (Ubuntu) "package qemu-kvm 0.13.0+noroms-0ubuntu12 [modified: usr/share/man/man1/qemu-user.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/qemu-ppc64', which is also in package qemu-user 0.13.50-2011.02-0-0ubuntu1 (affects: 2) (dups: 1) (heat: 18)" [Low,Confirmed] https://launchpad.net/bugs/717690
[17:02] <bdmurray> Hello, it is the 15th and 1700UTC right?
[17:03] <micahg> yep
[17:04] <bdmurray> Anybody here for a meeting?
[17:07] <yofel> o/
[17:09] <bdmurray> so the agenda is at https://wiki.ubuntu.com/BugSquad/Meeting
[17:09] <bdmurray> We have some action items from the last meeting
[17:10] <bdmurray> hggdh: Is preparing a regression-potential bug day something you still have time for?
[17:11] <bdmurray> Actually lookin in Launchpad there are only 11 of these that aren't kernel bugs.
[17:12] <bdmurray> So I'll review those and we can drop the r-p bug day idea
[17:13] <hggdh> OK
[17:14] <bdmurray> hggdh: there is also "clean up the Regression wiki pages" assigned to you
[17:14] <bdmurray> we double-checked this last week and it looked done right?
[17:14] <hggdh> bdmurray: yes indeed
[17:14] <hggdh> jibel and I did it
[17:14] <bdmurray> cool!
[17:15] <bdmurray> nigelb: there is an item assigned to you - "edit bugsquad headers to be similar or link to each other appropriately".  Does that sound familiar?
[17:17]  * charlie-tca made it
[17:17] <bdmurray> okay I'll follow up with nigelb after the meeting
[17:18] <bdmurray> Has anybody seen devildante around?
[17:18] <charlie-tca> not for a long time, now that you mention it
[17:19] <bdmurray> Hmm, I hope everything is alright.
[17:20] <bdmurray> I'll follow up on the list regarding HowToTriage simplification.
[17:20] <bdmurray> It seems to me a lot of people are curious about where to start or what is first ....
[17:22] <bdmurray> vish: Do you have any updates regarding the mentorship program?
[17:22] <vish> oh! meeting..
[17:22] <vish> bdmurray: nope.. :)
[17:22] <vish> just that not much of activity going on there ;p
[17:23] <vish> and both me and bdmurray have tried poking the team, but we have had little response
[17:24] <vish> any ideas for encouraging the mentees would be good.. :)
[17:24] <vish> …
[17:26] <bdmurray> Some questions that come to my mind are "how did people end up becoming mentees?" and "what are they looking for in a mentor?"
[17:27] <hggdh> I am also wondering about it, and about commitment from the mentees
[17:28] <vish> well, some "mentees" might just be curious lp usrs joining teams
[17:30] <vish> IMO, one way to ensure that a mentee is active is getting them to send reports
[17:31] <vish> on that, i would also like to mention that we seem to have had very few gain in BC members over the past few months
[17:33] <micahg> if you feel the need for mentees to send reports, I think you've already lost
[17:33] <bdmurray> Does anybody recall how the mentorship team / program was advertised?
[17:33] <vish> micahg: we are already at 0, it cant get worse ;)
[17:34] <vish> 0 activity*
[17:35] <bdmurray> I think micahg's point is if we are asking people to report as a way to motivate them we are doing it wrong
[17:35] <micahg> +1
[17:35] <bdmurray> The mentorship program should make it fun somehow
[17:36] <vish> why i _thought_ a report(any activity or no activity) might work is, alteast it makes the mentee commit to a schedule.. right now we have no schedule and no target
[17:36] <micahg> when I was being mentored, *I* was asking questions because *I* wanted to be involved and learn how things work
[17:37] <vish> micahg: yes, very true
[17:37] <vish> but how to motivate the less motivated?
[17:37] <micahg> vish: I think it might be better to try to attract the more motivated
[17:38] <bdmurray> micahg: +1
[17:38] <njin> +1
[17:38] <vish> how do we weed them out?
[17:38] <micahg> i.e. more publicity about what bug squad does
[17:38] <vish> right now how the mentoring team works is.. anyone can join the team,
[17:38] <bdmurray> look at who is already active in Launchpad
[17:38] <vish> and the memberships are approved by the date
[17:39] <vish> and we wait for the mentee to start work
[17:39] <bdmurray> Its an open team really?
[17:39] <vish> no, but we approve anyone
[17:39]  * micahg thought the mentoring teams were going to be moderated or restricted
[17:40] <vish> anyone in the sense, we approve motivated <----> less motivated individuals.
[17:40] <vish> we dont have a system to sort them
[17:40] <micahg> vish: 90 day trial
[17:40] <bdmurray> So I think an effort should be made to "clean up" the team.  I noticed at least one person in the team that might be a mistake
[17:41] <micahg> or 30 day even
[17:41] <vish> NOTE: I'm not focussed on the report is a must thing.. i'm open to any ideas  :)
[17:41] <charlie-tca> no work in 30 days should be plenty to say "try again when you have time"
[17:41] <charlie-tca> but if they are active, we see them before they even get a mentor assigned
[17:41] <micahg> yep
[17:42] <vish> yet, thats a schedule :)
[17:42] <charlie-tca> So, we wait a year, two years, more? that is still a schedule
[17:42] <vish> so thats was the kinda thing i was thinking ; only making them report about it would have been the wrong part :)
[17:42] <bdmurray> I think a schedule of doing 1 thing in 30 days isn't unreasonable
[17:43] <vish> err.. s/yet/yep
[17:43] <bdmurray> That one thing can be editing a bug title or adding a tag
[17:43] <charlie-tca> I would expect anyone who wants to learn would be doing at least one bug a week.
[17:44] <bdmurray> How about one thing a fortnight? ;-)
[17:44] <njin> i think that if someone would learn frequent assidually bugsquad
[17:44] <njin> would/want to
[17:44] <vish> sounds good to me..
[17:44] <charlie-tca> If they are doing a single bug a month, how will they remember what to do?
[17:45] <hggdh> indeed
[17:45] <bdmurray> In terms of actions wrt to the mentorship program I see the following:
[17:45] <hggdh> one a week is already too few
[17:45] <bdmurray> 1) "Clean up" existing team
[17:45] <vish> so who checks?
[17:45] <bdmurray> 2) Advertise the team and purpose again
[17:52] <hggdh> and keep on checking
[17:55] <njin> I think that is also a good idea to have more visibility
[17:56] <njin> and explain to people that is easy to start to work in bugs triaging
[17:57] <charlie-tca> now it feels right... ;-)
[17:57] <yofel> ^^
[18:00] <charlie-tca> oops, looks the whole meeting went too, huh?
[18:02] <njin> what's *net*split
[18:02] <micahg> !netsplit | njin
[18:02] <ubot4> njin: netsplit is when two IRC servers of the same network (like freenode) disconnect from each other, so users on one server stop seeing users on the other. If this is happening now, just relax and enjoy the show. See http://en.wikipedia.org/wiki/Netsplit
[18:03] <njin> micahg, thanks
[18:28] <micahg> bdmurray: did our meeting fizzle?
[18:30] <bdmurray> micahg: that's one word for it. ;-)
[18:32] <bdmurray> I think we covered everything though
[18:33] <bcurtiswx> bdmurray, hey i wanted to add something but couldn't catch you before I had to head out for another meeting
[18:33] <bdmurray> bcurtiswx: oh, sorry about that!
[18:34] <bcurtiswx> bdmurray, i was going to suggest for people who have adopted packages to talk to their upstreams more frequently about how they can improve bug report/bug flow.  I did with mine (empathy) and i think it was a great thing to do..
[18:34] <bdmurray> bcurtiswx: could you tell us about that on your blog or on the bug squad mailing list?
[18:35] <bcurtiswx> sure
[18:36] <bdmurray> bcurtiswx: here is what I did and how it has helped?
[18:36] <bcurtiswx> bdmurray, OK
[18:36] <bdmurray> bcurtiswx: cool, I'm excited to hear about it!
[19:12] <AbhijiT> hi guys
[19:12] <AbhijiT> would love if someone set this bug for wish list
[19:12] <AbhijiT> https://bugs.launchpad.net/ubuntu/+source/dia/+bug/719529
[19:12] <ubot4> Launchpad bug 719529 in dia (Ubuntu) "Dia UML object selection (affects: 1) (heat: 6)" [Undecided,New]
[19:14] <AbhijiT> !ping
[19:15] <ubot4> ping-pong, a fun game for all the family
[19:16] <bdmurray> AbhijiT: done
[19:16] <AbhijiT> :o
[19:16] <AbhijiT> bdmurray, :D thanks!!! :D
[19:16] <AbhijiT> my net problem here!
[20:07] <nigelb> bdmurray: Hey.  Its on my list.  I'll get to it soon.
[20:08] <bdmurray> nigelb: cool, thanks for letting me know!
[20:09] <nigelb> bdmurray: sorry, I was away from IRC for a while working :)
[21:17] <kees> hggdh: sbeattie pointed bug 718839 out to me
[21:17] <ubot4> Launchpad bug 718839 in linux (Ubuntu) "QA Regression test kernel-security reports two failures on 2.6.24-28.84 Xen (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/718839
[21:18] <kees> hggdh: I'm not sure I'd ever run qrt on the Xen host before, so I don't think either of those issues are regressions.
[21:18] <hggdh> kees: I was not sure (hell, this is a nice way of saying I had no idea) either; I tried to raise you folks yesterday about it
[21:19] <hggdh> kees: I do no think this is an issue, but it might be interesting to follow later on
[21:19] <kees> hggdh: yeah, I'm adding some notes to the bug report.
[21:20] <kees> hggdh: do you have that system still running? I'm curious what /proc/version_signature shows
[21:20] <hggdh> kees: I *think* it is still surviving, let me look
[21:21] <hggdh> kees: yup, still alive
[21:22] <hggdh> kees: Ubuntu 2.6.24-4.6-generic
[21:22] <hggdh> uname -a reports it as a -xen kernel
[21:23] <kees> hggdh: /proc/version_signature doesn't mention -xen ?
[21:23] <hggdh> kees: nope. uname reports 2.6.24-28-xen
[21:24] <hggdh> notice the versions are different
[21:24] <hggdh> kees: if you want to play with it, it is accessible from citron
[21:27] <kees> hggdh: sorry, I'm a bit confused. this is for the -xen _host_ kernel yes?
[21:43] <hggdh> kees: yes, indeed, Xen host
[21:44] <kees> hggdh: why does uname -a and /proc/version_signature differ?
[21:44] <kees> I probably don't want to know. regardless, -xen in uname -r is sufficient for me to skip those tests in the future.
[21:45] <hggdh> kees: heh. It *might* be because I installed the kernel on a -generic?
[21:45] <kees> maybe I just don't understand Xen. you're running this on the dom0 not the domU right?
[21:46] <hggdh> kees: yes, this would be a Dom0 -- the actual hipervisor
[21:47] <kees> strange! but, I don't mind. :) I've update q-r-t now.
[21:59] <penguin42> kees: In Xen there are two layers, Dom0 and DomU; DomU is a guest, Dom0 is the host, they both need special code (in the paravirtualised setup); I think you can build the code so that the same kernel can be used for both and it'll detect if its on real hardware
[22:00] <kees> penguin42: right, but you can still log into the host as a real machine, right?
[22:00] <penguin42> kees: Yeh
[22:01]  * kees nods
[22:04] <hggdh> Dom0 is still functional
[22:05]  * penguin42 hasn't used xen for years ago
[22:23] <njin> hello, can someone triage this and set to low for me bug 719654 (screencast attached), thanks fabio
[22:23] <ubot4> Launchpad bug 719654 in usb-creator (Ubuntu) "0.2.28 - boucing bar or progress bar ? (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/719654
[22:30] <bdmurray> njin: done
[22:33] <bdmurray> njin: oh, by the way is there a reason for moving bug 718187 from linux to xorg?
[22:33] <ubot4> Launchpad bug 718187 in xorg (Ubuntu) "Acer T230H Multi-touch Monitor (Quanta Optical Touch) (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/718187
[22:33] <njin> looking
[22:39] <njin> bdmurray: yes, it is detected and working, but sometimes don't respond and the touch is delayed
[22:39] <penguin42> I'd say it's 50/50 if it's the kernel or X
[22:39] <njin> but i'm waiting reply for the reporter
[22:39] <njin> for/from
[22:40] <penguin42> I suppose having flipped it to xorg, getting him to do an apport-collect will get the info on X as well as the kernel stuff already collected
[22:42] <bdmurray> njin: ah I see it bootdmesg.txt now
[22:42] <bdmurray> thanks!
[22:44] <bdmurray> I think, or like to think, copying relevant log file bits into a comment saves other people time later on
[22:44] <penguin42> bdmurray: Yeh, I wish the bots would do some of that
[22:44] <penguin42> especially for some of the boring package installation failures
[22:45] <bdmurray> penguin42: Do you have an idea of what could be done?
[22:45] <penguin42> bdmurray: Only some of one at this point; the package installation ones tend to have vast apt logs and an error at the end - but the trick seems to be finding the first real error in the log, and that's boring with a long file and difficult if it's not in your native language; that sounds automatable at least partially
[22:46] <njin> bdmurray, thanks for triaging usb-creator bug