[00:15] <emma> Bug 321287] [NEW] Seahorse will not generate a key
[00:31] <sectech> We still have restricted drivers for Nvidia in Jaunty right?
[00:40] <sectech> Just got an answer about the nvidia question....  Kinda curious on what guidelines we are following for triaging the new drivers.
[05:07] <hggdh> emma, it works on Jaunty
[05:07] <hggdh> at least under my own userId
[06:30] <dholbach> good morning
[06:43] <hggdh> good evening dholbach
[06:44] <dholbach> hiya hggdh
[07:53] <cmkAus> HI everyone
[08:17] <cmkAus> HI
[08:17] <cmkAus> Is anyone here?
[08:18] <cmkAus> Can someone help me
[08:19] <jpds> hi cmkAus, what's up?
[08:20] <cmkAus> Hi I am trying to do my first bug thing whats a good package to work with and should i just stay with that package ?
[08:22] <jpds> cmkAus: I mostly look after bugs for packages I'm interested in. Do you have any particular type of packages you're interested in (KDE, GNOME, etc)?
[08:23] <cmkAus> I must sound like a noob I dont even know what KDE or GNOME is ?
[08:24] <cmkAus> and what does package really mean Is it a name of a particular programs?
[08:24] <jpds> cmkAus: They're the desktop envirnoments used by Kubuntu and Ubuntu.
[08:24] <jpds> cmkAus: It's the softare bundle that programs come in.
[08:25] <jpds> cmkAus: I suggest you read: https://wiki.ubuntu.com/Bugs
[08:28] <cmkAus> How can I find out what a package does like for example package ubiquity or xorg. Is there a list of packages and descriptions somewhere
[08:30] <jpds> cmkAus: You can see the package descriptions doing: 'apt-cache show xserver-xorg' in the terminal.
[08:32] <jpds> cmkAus: Or if you want an index, you could do a search at packages.ubuntu.com
[08:33] <cmkAus> Cheers Thansk for your help I found something That I was interest MYSQL I will try to help out there
[09:35] <Hew> Is it appropriate for me to triage my own bug 321359?
[09:36] <seb128> Hew: sure, you can also directly send your bugs upstream if you want
[09:37] <seb128> Hew: you might want to specific the exact version you are using in bugzilla too
[09:38] <Hew> seb128: Yes, I was lazy and let the apport retracer do the trace (and dupe check) :P. Thanks, triaging.
[09:38] <seb128> Hew: and if you use lists or icon view, etc
[09:38] <Hew> seb128: Ok, will do.
[15:19] <bddebian> Boo
[17:48] <luckydeveloper> hi all
[17:48] <luckydeveloper> i am new to bugsquad.. and i am excited to join the team..
[17:50] <luckydeveloper> :-D anybody there
[17:53] <hggdh> welcome luckydeveloper
[17:59] <luckydeveloper> i hope  i will make some good contribution to ubuntu :-[ ...... its late night here.. going to sleep.. bye.. ;-)
[18:01] <hggdh> gnome bug 567687
[18:05] <seb128> hggdh: that was fixed, is that still an issue?
[18:07] <hggdh> seb128, no, just checking. Was it in 2.24.3?
[18:08] <hggdh> (chat in #evolution brought it up)
[18:08] <seb128> it was supposed to be fixed before that I think
[18:08] <seb128> read the upstream bug
[18:08] <hggdh> I am. It was committed to stable & trunk on Jan 14
[18:09] <hggdh> gnome bug 567697
[18:12] <seb128> ok, maybe I'm thinking about a different issue
[18:12] <seb128> there was a similar one fixed some months ago I think
[18:12] <seb128> have to go now bbl
[18:18] <bdmurray> hggdh: question for you in bug 315966
[19:06] <maxb> intrepid->jaunty seems to have left "linux-doc" kept back..... file bug on update-manager?
[19:21] <luckydeveloper> just a minute ago, i read a "class" log(in knowledge base section of BugSquad Wiki page) which was taken by brian murray on an Ubuntu open week about reporting a bug.. and it was very useful. Where do those open week sessions / classes happen. . how can i attend them......:)
[19:23] <calc> luckydeveloper: i think open week happened last week
[19:24] <calc> luckydeveloper: well Ubuntu Developer Week was last week
[19:24] <calc> luckydeveloper: not sure when the next Ubuntu Open Week will happen (or if it is the same thing)
[19:25] <calc> https://wiki.ubuntu.com/UbuntuDeveloperWeek
[19:25] <calc> luckydeveloper: i think open week happens the week after the release
[19:26] <calc> luckydeveloper: so open week will probably happen at the end of april
[19:27] <luckydeveloper> calc: oh .. then i missed it :'( ..... oh  k.. then open week happens after every release? ..  then is DeveloperWeek for developers ???
[19:28] <calc> it seems developer week happens halfway through the release cycle and open week at the beginning
[19:31] <luckydeveloper> calc: are there any other similar "weeks" where i can participate ?
[19:31] <calc> not sure
[19:31]  * calc in meeting, bbl
[19:31] <hggdh> bdmurray, I am going to test it now
[19:41] <chrisccoulson> hey, anybody seen anything like this before:
[19:41] <chrisccoulson> bug 321224
[19:42] <chrisccoulson> don't know if it's a compiz or video driver issue
[19:46] <calc> back
[19:46] <ch05en> Hi, I've got a repeatable bug in the UDF filesystem that enables me to crash my box at will
[19:47] <calc> ch05en: sounds bad, you probably should file a bug and perhaps mention it in #ubuntu-kernel
[19:47] <ch05en> If you create a file with illegal utf-8 filename and copy it over to a writeable udf filesystem you panic the box
[19:47] <ch05en> ok tnx
[19:48] <hggdh> bdmurray, indeed seems to be related to running apport-gtk as root
[19:56] <EagleScreen> ch05en UDF is failing for me since.. years?
[20:26] <ch05en> It fails for you by panic? Then it has no place in a stable kernel.
[20:27] <bdmurray> hggdh: great, thanks for testing
[20:27] <hggdh> welcome
[20:30] <benste1> hello,
[20:30] <benste1> I'm new someone here who can help me with a bug?
[20:31] <hggdh> benste1, just go ahead and ask your question. Someone here should be able to help you.
[20:32] <benste1> I can't send files with pidgin, posted a bug https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/321548 and don't know what to do now
[20:33] <hggdh> benste1, it would be good to state what version of pidgin you tested with
[20:34] <benste1> 2.5..5
[20:34] <benste1> and the jaunty one
[20:35] <benste1> (1:2.5.3-0ubuntu2
[20:35] <benste1> why is the jaunty version older than the 8.10 one
[20:35] <benste1> ?
[20:36] <mangilimic> benste1, pidgin for 8.10 is  2.5.2-0ubuntu1
[20:36] <mangilimic> :)
[20:37] <benste1> ups sorry
[20:37] <mangilimic> nope!
[20:37] <benste1> and now?
[20:39] <hggdh> now, you can improve the bug description (as shown in https://wiki.ubuntu.com/Bugs/Description) with this data
[20:39] <benste1> I'll try to do so
[20:41] <hggdh> and then you wait for someone with more knowledge of pidgin to look at it
[20:41] <benste1> ;-(
[20:41] <hggdh> heh
[20:42] <benste1> noprob
[20:42] <benste1> it's just the case
[20:42] <benste1> that we're having this issue since 2006
[20:42] <hggdh> you can also try the #pidgin channel -- they know more about it than most of us
[20:43] <benste1> thanks
[20:43] <hggdh> benste1, you have this issue for 2 years, and only now you opened a bug report?
[20:44] <benste1> ej I'm a 17 year old pupil and I'm not familiar with those things
[20:44] <benste1> I just started last week with UDW
[20:44] <hggdh> no prob. We depend heavily on voluntary help... if you are willing to pursue this, we would really appreciate
[20:45] <benste1> :-)
[22:25] <calc> bdmurray: ping
[22:28] <bdmurray> calc: oh right, you said something about no - numbers eh?
[22:29] <calc> bdmurray: oh yea i think that got fixed, i was going to ask how i go about updating the bug reporting info for OOo
[22:29] <calc> i saw something about committing to a bzr repo?
[22:30] <bdmurray> calc: yeah, in ubuntu-qa-tools there is a package-bug-guidelines directory with information
[22:30] <calc> oh ok
[22:31] <bdmurray> it should be straightforward ;-)
[22:31] <bdmurray> but let me know if you have any questions
[22:31] <calc> ok
[22:33] <calc> the Packages section is source packages right?
[22:33] <bdmurray> calc: correct
[22:33] <calc> ok
[22:38] <calc> bdmurray: ok i got it committed :)
[22:39] <Rocket2DMn> hey seb128 , can i ask you a few questions regarding desktop bug triage
[22:39] <seb128> Rocket2DMn: hi, sure
[22:39] <Rocket2DMn> bug 320972
[22:40] <Rocket2DMn> you said "don't change desktop bugs which are not sent upstream to triager though"
[22:40] <Rocket2DMn> did you mean set to Triaged status?
[22:40] <Rocket2DMn> would you rather have us just confirm bugs that have complete stacktraces?
[22:40] <bdmurray> calc: what about asking for a test document?
[22:41] <calc> bdmurray: oh yea i should do that
[22:41] <calc> bdmurray: ok i'll update it
[22:41] <calc> bdmurray: also does this only show up on the advanced screen?
[22:41] <bdmurray> No, I just used it as an example
[22:41] <seb128> Rocket2DMn: for desktop bugs we use triager when the bug is an ubuntu bug or an upstream bug which has been sent upstream, just set it confirmed if you confirm the issue
[22:41] <bdmurray> rather than having to click submit and for the title and then see it
[22:42] <seb128> Rocket2DMn:  you set some bugs as triaged without checking they were on the right component for example
[22:42] <calc> bdmurray: ok
[22:42] <Rocket2DMn> seb128, by saying we can "confirm" the issue, did you want us to actually be able to reproduce it, or is seeing a complete trace good enough?
[22:42] <seb128> Rocket2DMn: for crashers a good stacktrace is enough
[22:43] <Rocket2DMn> ok thanks for clarifying, seb128 .  I don't have much experience reading traces but being a coder I can get a decent idea of what is going on - do you typically just looking ath #0 or #1 to determine the package?
[22:44] <seb128> Rocket2DMn: yes, the stacktrace describes the codepath where it crashes, the first function listed is the one which crashed, the next ones are the callers
[22:44] <seb128> Rocket2DMn: that example is clearly a crash is the ffmpeg library
[22:45] <Rocket2DMn> seb128, ok, at what point do you pass the bugs upstream?  I'm registered on a bunch of upstream bugzillas but dont use them much
[22:48] <calc> bdmurray: done
[22:50] <Rocket2DMn> seb128, so for example, bug 320269 should be filed under poppler ?
[22:51] <seb128> Rocket2DMn: when the bug has enough informations and is not due to a distribution change we open it upstream, most of desktop packages have not a lot of changes so usually bugs can be sent easily
[22:52] <seb128> Rocket2DMn: that one can be opened on bugzilla.freedesktop.org, having a pdf example would be useful though
[22:52] <seb128> Rocket2DMn: in fact that's https://bugs.freedesktop.org/show_bug.cgi?id=19669
[22:53] <Rocket2DMn> cool, so just attach that to the LP report then?
[22:53] <Rocket2DMn> should i make a note on the upstream report and link to the LP bug?
[22:54] <seb128> Rocket2DMn: right, click on the link bellow the bugs table to add a bug watch
[22:54] <seb128> Rocket2DMn: that's usually a good idea
[22:54] <Rocket2DMn> and file it under poppler too
[22:54] <seb128> reassign it to poppler rather
[22:54] <Rocket2DMn> yeah, thats wha ti meant
[22:54] <seb128> change okular to poppler
[22:54] <seb128> sometimes people invalid the task and add a new one
[22:55] <seb128> which is not a good idea because the subscriber to the wrong component are still mailed when you do that
[22:55] <seb128> so I prefer to make clear than you should better change the component
[22:55] <Rocket2DMn> yeah ive experienced that before, it is a bit of a pain
[22:55] <bdmurray> calc: https://edge.launchpad.net/ubuntu/+source/openoffice.org/+filebug-advanced
[22:55] <Rocket2DMn> so does that bug look ok on LP now?
[22:56] <Rocket2DMn> and is there a way to attach ubuntu bug reports to the upstream, or should i just leave a simple comment?
[22:57] <seb128> bugzilla has no specific way to do that just add a comment
[22:57] <calc> bdmurray: thanks :)
[22:58] <bdmurray> calc: thank you!
[23:01] <Rocket2DMn> thanks for the help seb128
[23:01] <seb128> Rocket2DMn: you're welcome, thank you for the bug triage!
[23:01] <Rocket2DMn> seb128, bug 321300 is a little different
[23:02] <Rocket2DMn> i dont immediately see a package popping out at me, does that get filed under gtk+2.0 ?
[23:02] <seb128> Rocket2DMn: seems you are working on kubuntu ;-)
[23:02] <Rocket2DMn> lol, not specifically
[23:03] <Rocket2DMn> im trying to get into some more advanced bug triaging
[23:03] <Rocket2DMn> ive had a fair number of run ins with kernel bugs and X bugs
[23:03] <seb128> Rocket2DMn: not sure what the issue is there but the command which fails is a gtk one indeed so you can reassing it there
[23:03] <seb128> ok
[23:05] <Rocket2DMn> so seb128 what search string do you typically use in your upstream search to get the best results
[23:06] <seb128> Rocket2DMn: depends of the bug, for the poppler crash I search for bugs which have the first function of the crash in their description
[23:06] <seb128> searched
[23:07] <seb128> I usually try queries on the title or the comments depending on how easy the bug is to describe and of the keywords
[23:07] <Rocket2DMn> so for that other bug, i searched for "IA__gtk_icon_theme_lookup_by_gicon" but couldnt find anything
[23:07] <seb128> the installation one?
[23:07] <seb128> where did you search?
[23:07] <Rocket2DMn> for the xchat-gnome bug, searching on freekdesktop
[23:07] <seb128> xchat-gnome uses bugzilla.gnome.org as a bugtracker
[23:07] <Rocket2DMn> guess i should check gnomes bugzilla
[23:08] <Rocket2DMn> hehe beat me to it
[23:08] <seb128> if you search for GNOME crashes, http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi
[23:08] <seb128> just copy the stacktrace there
[23:08] <seb128> and it'll list duplicates
[23:09] <Rocket2DMn> hmm it said it found a match but didnt list the bug number
[23:11] <Rocket2DMn> seb128, do you think i should file a new report then?  Would you happen to have a template you use to pass traces upstream?
[23:11] <seb128> Rocket2DMn: what bug are you speaking about?
[23:11] <Rocket2DMn> bug 320300
[23:12] <Rocket2DMn> ill reassign that in a minute like we talked about
[23:13] <hggdh> Rocket2DMn, when simple-dup-finder shows no output, there is no match
[23:13] <seb128> reassign to what?
[23:13] <Rocket2DMn> gtk+2.0
[23:13] <seb128> not sure if that's an xchat or a gtk bug
[23:14] <Rocket2DMn> the only mention of xchat in the trace is the very last line, #31
[23:14] <seb128> open a bug upstream either on xchat-gnome or gtk
[23:14] <seb128> right, which doesn't mean there is not a corruption somewhere or the software is not misusing gtk
[23:14] <seb128> this stacktrace is a weird one
[23:15] <Rocket2DMn> hehe, would you leave it filed under xchat-gnome, or would you re-assign it to gtk+2.0?
[23:15] <seb128> I'm not enough of a GTK hacker to have a clue about it easily
[23:15] <seb128> I would open an upstream bug on xchat-gnome and let them reassign if required, which doesn't mean I'm right ;-)
[23:15] <Rocket2DMn> hehe, well you wouldnt be the first
[23:15]  * Rocket2DMn hangs head
[23:15] <seb128> the gtk upstream guys tend to get too many bugs and not look to everything, you probably have a better chance to get a reply on xchat-gnome
[23:16] <seb128> and they will reassign if required
[23:16] <seb128> that's just a bet on the component ;-)
[23:16] <seb128> you don't do really wrong either way
[23:16] <seb128> do you get the issue?
[23:16] <Rocket2DMn> alright, sounds good.  when you open the bug upstream, what do you usually say?  Just say it was filed <here> on LP and give them the trace?
[23:16] <seb128> looking at the strace it's weird it's crashing in private icon functions, having a valgrind log would maybe be useful there
[23:17] <seb128> right
[23:17] <Rocket2DMn> ah yes valgrind, what is so special about that?
[23:17] <seb128> I usually just write a short sentence saying that the bug has been opened on URL
[23:17] <Rocket2DMn> should i file upstream, request the valgrind on LP and mark as incomplete then?
[23:17] <seb128> and then copy the description and stracktrace
[23:18] <seb128> open upstream, set as triaged since it's set upstream and request a valgrind anyway in case
[23:18] <seb128> valgrind is not special but that's an useful tool
[23:18] <seb128> it gives clues about corruption
[23:18] <Rocket2DMn> alright, ill get to it
[23:18] <Rocket2DMn> thanks man
[23:18] <seb128> ie, sometimes you get a crash when accessing a variable and don't understand why
[23:18] <Rocket2DMn> yeah, im used to debugging my own code though
[23:19] <seb128> could be that it has been freed somewhere else before already, valgrind will tell you that and where
[23:19] <Rocket2DMn> nifty
[23:21] <seb128> ok, enough work for me for today
[23:21] <seb128> bye there, see you tomorrow
[23:21] <Rocket2DMn> thanks again seb128 , peace