/srv/irclogs.ubuntu.com/2009/01/26/#ubuntu-bugs.txt

emmaBug 321287] [NEW] Seahorse will not generate a key00:15
ubottuLaunchpad bug 321287 in seahorse "Seahorse will not generate a key" [Undecided,New] https://launchpad.net/bugs/32128700:15
sectechWe still have restricted drivers for Nvidia in Jaunty right?00:31
sectechJust got an answer about the nvidia question....  Kinda curious on what guidelines we are following for triaging the new drivers.00:40
hggdhemma, it works on Jaunty05:07
hggdhat least under my own userId05:07
=== |Ryan52 is now known as Ryan52
dholbachgood morning06:30
hggdhgood evening dholbach06:43
dholbachhiya hggdh06:44
cmkAusHI everyone07:53
cmkAusHI08:17
cmkAusIs anyone here?08:17
cmkAusCan someone help me08:18
jpdshi cmkAus, what's up?08:19
cmkAusHi 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:20
jpdscmkAus: 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:22
cmkAusI must sound like a noob I dont even know what KDE or GNOME is ?08:23
cmkAusand what does package really mean Is it a name of a particular programs?08:24
jpdscmkAus: They're the desktop envirnoments used by Kubuntu and Ubuntu.08:24
jpdscmkAus: It's the softare bundle that programs come in.08:24
jpdscmkAus: I suggest you read: https://wiki.ubuntu.com/Bugs08:25
cmkAusHow can I find out what a package does like for example package ubiquity or xorg. Is there a list of packages and descriptions somewhere08:28
jpdscmkAus: You can see the package descriptions doing: 'apt-cache show xserver-xorg' in the terminal.08:30
=== BugMaN1 is now known as BugMaN
jpdscmkAus: Or if you want an index, you could do a search at packages.ubuntu.com08:32
cmkAusCheers Thansk for your help I found something That I was interest MYSQL I will try to help out there08:33
HewIs it appropriate for me to triage my own bug 321359?09:35
ubottuLaunchpad bug 321359 in nautilus "nautilus crashed with SIGSEGV in IA__g_closure_invoke()" [Medium,New] https://launchpad.net/bugs/32135909:35
seb128Hew: sure, you can also directly send your bugs upstream if you want09:36
seb128Hew: you might want to specific the exact version you are using in bugzilla too09:37
Hewseb128: Yes, I was lazy and let the apport retracer do the trace (and dupe check) :P. Thanks, triaging.09:38
seb128Hew: and if you use lists or icon view, etc09:38
Hewseb128: Ok, will do.09:38
=== asac_ is now known as asac
=== LucidFox_ is now known as LucidFox
=== a|wen- is now known as a|wen
bddebianBoo15:19
=== dholbach_ is now known as dholbach
luckydeveloperhi all17:48
luckydeveloperi am new to bugsquad.. and i am excited to join the team..17:48
luckydeveloper:-D anybody there17:50
hggdhwelcome luckydeveloper17:53
=== Jazzva_ is now known as Jazzva
luckydeveloperi hope  i will make some good contribution to ubuntu :-[ ...... its late night here.. going to sleep.. bye.. ;-)17:59
hggdhgnome bug 56768718:01
ubottuGnome bug 567687 in Miscellaneous "Prefer plain-text plugin disables meeting invite acceptance (outlook/exchange)" [Normal,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=56768718:01
seb128hggdh: that was fixed, is that still an issue?18:05
hggdhseb128, no, just checking. Was it in 2.24.3?18:07
hggdh(chat in #evolution brought it up)18:08
seb128it was supposed to be fixed before that I think18:08
seb128read the upstream bug18:08
hggdhI am. It was committed to stable & trunk on Jan 1418:08
hggdhgnome bug 56769718:09
ubottuGnome bug 567697 in Mailer "Plain text emails render links with ampersand characters stripped out" [Major,Reopened] http://bugzilla.gnome.org/show_bug.cgi?id=56769718:09
seb128ok, maybe I'm thinking about a different issue18:12
seb128there was a similar one fixed some months ago I think18:12
seb128have to go now bbl18:12
bdmurrayhggdh: question for you in bug 31596618:18
ubottuLaunchpad bug 315966 in apport "Apport opens crash files as "file:///" urls" [High,Confirmed] https://launchpad.net/bugs/31596618:18
maxbintrepid->jaunty seems to have left "linux-doc" kept back..... file bug on update-manager?19:06
luckydeveloperjust 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:21
calcluckydeveloper: i think open week happened last week19:23
calcluckydeveloper: well Ubuntu Developer Week was last week19:24
calcluckydeveloper: not sure when the next Ubuntu Open Week will happen (or if it is the same thing)19:24
calchttps://wiki.ubuntu.com/UbuntuDeveloperWeek19:25
calcluckydeveloper: i think open week happens the week after the release19:25
calcluckydeveloper: so open week will probably happen at the end of april19:26
luckydevelopercalc: oh .. then i missed it :'( ..... oh  k.. then open week happens after every release? ..  then is DeveloperWeek for developers ???19:27
calcit seems developer week happens halfway through the release cycle and open week at the beginning19:28
luckydevelopercalc: are there any other similar "weeks" where i can participate ?19:31
calcnot sure19:31
* calc in meeting, bbl19:31
hggdhbdmurray, I am going to test it now19:31
chrisccoulsonhey, anybody seen anything like this before:19:41
chrisccoulsonbug 32122419:41
ubottuLaunchpad bug 321224 in compiz "Screen shifted to the right with nvidia drivers and compiz" [Undecided,Incomplete] https://launchpad.net/bugs/32122419:41
chrisccoulsondon't know if it's a compiz or video driver issue19:42
calcback19:46
ch05enHi, I've got a repeatable bug in the UDF filesystem that enables me to crash my box at will19:46
calcch05en: sounds bad, you probably should file a bug and perhaps mention it in #ubuntu-kernel19:47
ch05enIf you create a file with illegal utf-8 filename and copy it over to a writeable udf filesystem you panic the box19:47
ch05enok tnx19:47
hggdhbdmurray, indeed seems to be related to running apport-gtk as root19:48
EagleScreench05en UDF is failing for me since.. years?19:56
ch05enIt fails for you by panic? Then it has no place in a stable kernel.20:26
bdmurrayhggdh: great, thanks for testing20:27
hggdhwelcome20:27
benste1hello,20:30
benste1I'm new someone here who can help me with a bug?20:30
hggdhbenste1, just go ahead and ask your question. Someone here should be able to help you.20:31
benste1I 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 now20:32
ubottuLaunchpad bug 321548 in pidgin "pidgin can't send files" [Undecided,Confirmed]20:32
hggdhbenste1, it would be good to state what version of pidgin you tested with20:33
benste12.5..520:34
benste1and the jaunty one20:34
benste1(1:2.5.3-0ubuntu220:35
benste1why is the jaunty version older than the 8.10 one20:35
benste1?20:35
mangilimicbenste1, pidgin for 8.10 is  2.5.2-0ubuntu120:36
mangilimic:)20:36
benste1ups sorry20:37
mangilimicnope!20:37
benste1and now?20:37
hggdhnow, you can improve the bug description (as shown in https://wiki.ubuntu.com/Bugs/Description) with this data20:39
benste1I'll try to do so20:39
hggdhand then you wait for someone with more knowledge of pidgin to look at it20:41
benste1;-(20:41
hggdhheh20:41
benste1noprob20:42
benste1it's just the case20:42
benste1that we're having this issue since 200620:42
hggdhyou can also try the #pidgin channel -- they know more about it than most of us20:42
benste1thanks20:43
hggdhbenste1, you have this issue for 2 years, and only now you opened a bug report?20:43
benste1ej I'm a 17 year old pupil and I'm not familiar with those things20:44
benste1I just started last week with UDW20:44
hggdhno prob. We depend heavily on voluntary help... if you are willing to pursue this, we would really appreciate20:44
benste1:-)20:45
calcbdmurray: ping22:25
bdmurraycalc: oh right, you said something about no - numbers eh?22:28
calcbdmurray: oh yea i think that got fixed, i was going to ask how i go about updating the bug reporting info for OOo22:29
calci saw something about committing to a bzr repo?22:29
bdmurraycalc: yeah, in ubuntu-qa-tools there is a package-bug-guidelines directory with information22:30
calcoh ok22:30
bdmurrayit should be straightforward ;-)22:31
bdmurraybut let me know if you have any questions22:31
calcok22:31
calcthe Packages section is source packages right?22:33
bdmurraycalc: correct22:33
calcok22:33
calcbdmurray: ok i got it committed :)22:38
Rocket2DMnhey seb128 , can i ask you a few questions regarding desktop bug triage22:39
seb128Rocket2DMn: hi, sure22:39
Rocket2DMnbug 32097222:39
ubottuLaunchpad bug 320972 in ffmpeg-debian "totem-gstreamer-video-thumbnailer crashed with SIGSEGV" [Medium,Incomplete] https://launchpad.net/bugs/32097222:39
Rocket2DMnyou said "don't change desktop bugs which are not sent upstream to triager though"22:40
Rocket2DMndid you mean set to Triaged status?22:40
Rocket2DMnwould you rather have us just confirm bugs that have complete stacktraces?22:40
bdmurraycalc: what about asking for a test document?22:40
calcbdmurray: oh yea i should do that22:41
calcbdmurray: ok i'll update it22:41
calcbdmurray: also does this only show up on the advanced screen?22:41
bdmurrayNo, I just used it as an example22:41
seb128Rocket2DMn: 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 issue22:41
bdmurrayrather than having to click submit and for the title and then see it22:41
seb128Rocket2DMn:  you set some bugs as triaged without checking they were on the right component for example22:42
calcbdmurray: ok22:42
Rocket2DMnseb128, 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
seb128Rocket2DMn: for crashers a good stacktrace is enough22:42
Rocket2DMnok 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:43
seb128Rocket2DMn: yes, the stacktrace describes the codepath where it crashes, the first function listed is the one which crashed, the next ones are the callers22:44
seb128Rocket2DMn: that example is clearly a crash is the ffmpeg library22:44
Rocket2DMnseb128, ok, at what point do you pass the bugs upstream?  I'm registered on a bunch of upstream bugzillas but dont use them much22:45
calcbdmurray: done22:48
Rocket2DMnseb128, so for example, bug 320269 should be filed under poppler ?22:50
ubottuLaunchpad bug 320269 in okular "okular crashed with SIGSEGV in Poppler::convertAnnotColor()" [Medium,Triaged] https://launchpad.net/bugs/32026922:50
seb128Rocket2DMn: 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 easily22:51
seb128Rocket2DMn: that one can be opened on bugzilla.freedesktop.org, having a pdf example would be useful though22:52
seb128Rocket2DMn: in fact that's https://bugs.freedesktop.org/show_bug.cgi?id=1966922:52
ubottuFreedesktop bug 19669 in qt4 frontend "okular/poppler crash in Poppler::convertAnnotColor when opening large PDF (Qt book)" [Major,New]22:52
Rocket2DMncool, so just attach that to the LP report then?22:53
Rocket2DMnshould i make a note on the upstream report and link to the LP bug?22:53
seb128Rocket2DMn: right, click on the link bellow the bugs table to add a bug watch22:54
seb128Rocket2DMn: that's usually a good idea22:54
Rocket2DMnand file it under poppler too22:54
seb128reassign it to poppler rather22:54
Rocket2DMnyeah, thats wha ti meant22:54
seb128change okular to poppler22:54
seb128sometimes people invalid the task and add a new one22:54
seb128which is not a good idea because the subscriber to the wrong component are still mailed when you do that22:55
seb128so I prefer to make clear than you should better change the component22:55
Rocket2DMnyeah ive experienced that before, it is a bit of a pain22:55
bdmurraycalc: https://edge.launchpad.net/ubuntu/+source/openoffice.org/+filebug-advanced22:55
Rocket2DMnso does that bug look ok on LP now?22:55
Rocket2DMnand is there a way to attach ubuntu bug reports to the upstream, or should i just leave a simple comment?22:56
seb128bugzilla has no specific way to do that just add a comment22:57
calcbdmurray: thanks :)22:57
bdmurraycalc: thank you!22:58
Rocket2DMnthanks for the help seb12823:01
seb128Rocket2DMn: you're welcome, thank you for the bug triage!23:01
Rocket2DMnseb128, bug 321300 is a little different23:01
ubottuLaunchpad bug 321300 in kwlan "kwlan crash now impacting software updates" [Undecided,New] https://launchpad.net/bugs/32130023:01
Rocket2DMni dont immediately see a package popping out at me, does that get filed under gtk+2.0 ?23:02
seb128Rocket2DMn: seems you are working on kubuntu ;-)23:02
Rocket2DMnlol, not specifically23:02
Rocket2DMnim trying to get into some more advanced bug triaging23:03
Rocket2DMnive had a fair number of run ins with kernel bugs and X bugs23:03
seb128Rocket2DMn: not sure what the issue is there but the command which fails is a gtk one indeed so you can reassing it there23:03
seb128ok23:03
Rocket2DMnso seb128 what search string do you typically use in your upstream search to get the best results23:05
seb128Rocket2DMn: depends of the bug, for the poppler crash I search for bugs which have the first function of the crash in their description23:06
seb128searched23:06
seb128I usually try queries on the title or the comments depending on how easy the bug is to describe and of the keywords23:07
Rocket2DMnso for that other bug, i searched for "IA__gtk_icon_theme_lookup_by_gicon" but couldnt find anything23:07
seb128the installation one?23:07
seb128where did you search?23:07
Rocket2DMnfor the xchat-gnome bug, searching on freekdesktop23:07
seb128xchat-gnome uses bugzilla.gnome.org as a bugtracker23:07
Rocket2DMnguess i should check gnomes bugzilla23:07
Rocket2DMnhehe beat me to it23:08
seb128if you search for GNOME crashes, http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi23:08
seb128just copy the stacktrace there23:08
seb128and it'll list duplicates23:08
Rocket2DMnhmm it said it found a match but didnt list the bug number23:09
Rocket2DMnseb128, 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
seb128Rocket2DMn: what bug are you speaking about?23:11
Rocket2DMnbug 32030023:11
ubottuLaunchpad bug 320300 in xchat-gnome "xchat-gnome crashed with SIGSEGV in gtk_icon_theme_lookup_by_gicon()" [Medium,Triaged] https://launchpad.net/bugs/32030023:11
Rocket2DMnill reassign that in a minute like we talked about23:12
hggdhRocket2DMn, when simple-dup-finder shows no output, there is no match23:13
seb128reassign to what?23:13
Rocket2DMngtk+2.023:13
seb128not sure if that's an xchat or a gtk bug23:13
Rocket2DMnthe only mention of xchat in the trace is the very last line, #3123:14
seb128open a bug upstream either on xchat-gnome or gtk23:14
seb128right, which doesn't mean there is not a corruption somewhere or the software is not misusing gtk23:14
seb128this stacktrace is a weird one23:14
Rocket2DMnhehe, would you leave it filed under xchat-gnome, or would you re-assign it to gtk+2.0?23:15
seb128I'm not enough of a GTK hacker to have a clue about it easily23:15
seb128I would open an upstream bug on xchat-gnome and let them reassign if required, which doesn't mean I'm right ;-)23:15
Rocket2DMnhehe, well you wouldnt be the first23:15
* Rocket2DMn hangs head23:15
seb128the 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-gnome23:15
seb128and they will reassign if required23:16
seb128that's just a bet on the component ;-)23:16
seb128you don't do really wrong either way23:16
seb128do you get the issue?23:16
Rocket2DMnalright, 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
seb128looking at the strace it's weird it's crashing in private icon functions, having a valgrind log would maybe be useful there23:16
seb128right23:17
Rocket2DMnah yes valgrind, what is so special about that?23:17
seb128I usually just write a short sentence saying that the bug has been opened on URL23:17
Rocket2DMnshould i file upstream, request the valgrind on LP and mark as incomplete then?23:17
seb128and then copy the description and stracktrace23:17
seb128open upstream, set as triaged since it's set upstream and request a valgrind anyway in case23:18
seb128valgrind is not special but that's an useful tool23:18
seb128it gives clues about corruption23:18
Rocket2DMnalright, ill get to it23:18
Rocket2DMnthanks man23:18
seb128ie, sometimes you get a crash when accessing a variable and don't understand why23:18
Rocket2DMnyeah, im used to debugging my own code though23:18
seb128could be that it has been freed somewhere else before already, valgrind will tell you that and where23:19
Rocket2DMnnifty23:19
seb128ok, enough work for me for today23:21
seb128bye there, see you tomorrow23:21
Rocket2DMnthanks again seb128 , peace23:21

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!