kalstabakken | when you're triaging an older bug, what should you do if the bug is not reproducible in the current version of the package? | 04:43 |
---|---|---|
kalstabakken | as a specific example, bugs reported for firefox 3.6 a few months ago that don't reproduce in 6.0 | 04:44 |
=== Hellow is now known as collinp | ||
=== abhinav_ is now known as abhinav- | ||
htorque_ | hello everyone! what in the user home dir could prevent apport from popping up upon crashes? i got this on two different oneiric systems but in both cases apport works fine with newly created users. | 10:55 |
=== JanC_ is now known as JanC | ||
bil21al | how to report the destop bugs,,i mean what command should use to report a main dextop bugs??? can any body tell me | 14:29 |
charlie-tca | ubuntu-bug unity | 14:31 |
charlie-tca | I think | 14:31 |
ashams | bil21al: you can report it anywhere, if you don't really know, like linux 'ubuntu-bug linux' ;) | 14:36 |
bil21al | ok tku | 14:36 |
jtaylor | isn't linux the kernel? thats not where desktop bugs should land | 14:38 |
charlie-tca | no, please do not report a desktop bug against linux! | 14:41 |
charlie-tca | That is not correct by any means, ashams | 14:41 |
charlie-tca | bil21al: Please use ubuntu-bug unity, or report it against ubuntu. | 14:41 |
charlie-tca | Reporting bugs against any package just to report it does not help at all. It creates more work for triagers and developers when you do that. | 14:42 |
abhinav- | I don't know if it would work in this case or not, but `ubuntu-bug -w` might be useful when you don't know the exact package name. never tried agains unity | 14:43 |
charlie-tca | If you don't know, please read https://help.ubuntu.com/community/ReportingBugs | 14:43 |
charlie-tca | It pretty much does tell how to report any bug | 14:43 |
ashams | charlie-tca: I meant that if a bug reporter can't identify which pkg to file against, he would simply report it against linux. Bug triager will handle it from there and will ask him to apport-collect <bug#>, to me it's a fair solution, what you think? | 14:45 |
charlie-tca | That is not correct, no | 14:45 |
charlie-tca | That attaches a lot of useless logs to the bug, which both a triager and developer must go through to find the actual problem. It could even mean the bug will not get touched | 14:46 |
ashams | abhinav-: ubuntu-bug -w is great :) | 14:46 |
charlie-tca | The correct procedure is to read the "How to report a bug" document and do what it tells you when you can not find the package | 14:46 |
charlie-tca | Linux bugs often do not get looked at for a long time, because they are very difficult to triage. Reporting stray bugs against linux can mean your bug gets closed as invalid. | 14:47 |
abhinav- | ashams: yeah. Its very handy, no need to fuss around about the correct package name | 14:47 |
charlie-tca | ashams: do you look at every bug reported against linux? | 14:48 |
ashams | charlie-tca: kernel team do? | 14:49 |
charlie-tca | Kernel team already has more bugs than they have time for. Why do you think it is okay to add to their workload? | 14:49 |
ashams | charlie-tca: what if we create some to collect bugs into one place, then we move it from there? | 14:50 |
ashams | charlie-tca: meant some where | 14:50 |
charlie-tca | It is not needed and adds more work for all of us. | 14:51 |
ashams | but will help newbie bug reporters to report their bugs ;) | 14:51 |
charlie-tca | We have excellent documentation about how to file any bug, why can't we use it? | 14:51 |
charlie-tca | https://help.ubuntu.com/community/ReportingBugs#Filing%20a%20general%20bug%20against%20no%20particular%20package | 14:51 |
charlie-tca | Can't they follow a simple direction to file that bug? | 14:52 |
charlie-tca | It seems you believe they aren't smart enough to read the wiki? | 14:52 |
ashams | charlie-tca: not at all, but how many lines in there? | 14:53 |
ashams | may be 500 | 14:53 |
charlie-tca | Please try to give advice that follows the guidelines we have worked hard to establish. | 14:53 |
charlie-tca | Looking in the Table of Contents on the page, it took me reading about 5 lines to find the right answer. | 14:54 |
ashams | lovely, but I think that we're already used to deal with bugs, while ~90% of *Computer users* in general have never heared of bugs! | 14:57 |
charlie-tca | Again, you assume they can not read? | 14:57 |
charlie-tca | Any user can read that table of contents and come to the exact line, called filing against no particular package. | 14:58 |
charlie-tca | It really is not as hard as you want it to be. | 14:58 |
charlie-tca | and it does make a lot less work for the kernel team, at the same time. | 14:58 |
ashams | charlie-tca: I think we imagine two different of users, mine would be a Business woman ;) | 15:02 |
ashams | oh no, meant different kind of users | 15:03 |
charlie-tca | Business woman is not stupid either. They can read, or they wouldn't be working | 15:03 |
charlie-tca | There is a valid reason for that wiki page. It really does mean those of us who triage bugs can do more in the limited time we have. | 15:04 |
ashams | charlie-tca: yeah, but her mind would be already filled with business, no room for bugs :) | 15:04 |
charlie-tca | !coc | 15:05 |
ubot4 | The Ubuntu Code of Conduct is a community etiquette document to which we ask all Ubuntu users to adhere, and can be found at http://www.ubuntu.com/community/conduct/ | For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct | 15:05 |
ashams | charlie-tca: you are a real good listener | 15:05 |
charlie-tca | Please do not degrade others for your own shortcomings | 15:05 |
ashams | charlie-tca: I don't, I just want to check if there would be better ways to get things done! | 15:06 |
paultag | ashams: stop; you're just making snide turdish comments to try to incite a response from charlie-tca | 15:06 |
paultag | ashams: kindly bug another channel. I hear ##windows gets upset easy. | 15:06 |
ashams | ashams: haha, ok, sorry guys.... | 15:06 |
paultag | cheers, have fun | 15:07 |
ashams | charlie-tca: whenever I find a better you'll be the first one to know, bye ;) | 15:08 |
bil21al | how can we apply for ubuntu membership??? | 15:55 |
yofel_ | bil21al: https://wiki.ubuntu.com/Membership | 16:04 |
=== yofel_ is now known as yofel | ||
=== abhinav_ is now known as abhinav- | ||
ali1234 | has the ability to "nominate for release" been restricted? | 18:23 |
=== abhinav_ is now known as abhinav- | ||
ali1234 | also why did launchpad janitor confirm my bug? | 18:34 |
jtaylor | duplicates and affected now confirm bugs | 18:36 |
ali1234 | ah, it's from affects | 18:36 |
ali1234 | that makes sense and is a good idea :) | 18:38 |
htorque_ | jtaylor: what does it do if there is more than one task? | 18:38 |
jtaylor | no idea | 18:41 |
ali1234 | so there is a nasty bug in unity which is trivially reproduced and forces the user to reboot or restart X, potentially losing unsaved work | 18:53 |
ali1234 | the bug is fixed in oneiric, but i don't know which patch fixed it. it just went away one day | 18:54 |
ali1234 | i don't seem to have the ability to nominate the bug for natty, and i don't have a patch that fixes only that bug anyway | 18:55 |
ali1234 | so what can be done about this? | 18:55 |
charlie-tca | ali1234: put a comment in the bug report that it still affects natty, and tell how to reproduce it. | 19:05 |
ali1234 | i've done that already | 19:05 |
ali1234 | the bug was originally opened against natty | 19:05 |
charlie-tca | What's the bug number? | 19:05 |
ali1234 | bug 826059 | 19:06 |
ubot4 | Launchpad bug 826059 in unity (Ubuntu) "unity gets stuck in 'expose' mode when you drag an icon over a launcher icon and hold it there (affects: 3) (dups: 1) (heat: 22)" [Low,Fix released] https://launchpad.net/bugs/826059 | 19:06 |
charlie-tca | looking | 19:06 |
charlie-tca | Okay, let me add a comment and try to nominate it for natty | 19:08 |
ali1234 | thanks. i'm looking in the unity source to try to find what fixed it | 19:08 |
charlie-tca | Okay, nominated | 19:09 |
* penguin42 is confused about bug 832949 - it shows a FTBFS yet https://launchpad.net/ubuntu/+builds?build_text=monkey-bubble&build_state=all doesn't show any recent build failures | 20:00 | |
ubot4 | Launchpad bug 832949 in monkey-bubble (Ubuntu Oneiric) (and 1 other project) "monkey-bubble version 0.4.0-0ubuntu8 failed to build in oneiric (affects: 1) (heat: 8)" [High,Confirmed] https://launchpad.net/bugs/832949 | 20:00 |
jtaylor | its from a test rebuild | 20:01 |
penguin42 | why don't they show up in the lp buold logs? | 20:02 |
penguin42 | build | 20:02 |
penguin42 | (I do wish there was an easy link to the build logs from the packages. page) | 20:03 |
jtaylor | there are links here: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html | 20:04 |
ali1234 | penguin42: there are packages out there which will build from source *once* but if you try to build it again it won't | 20:04 |
ali1234 | you have to delete the whole source dir and unarchive it again | 20:04 |
ali1234 | that wouldn't show up on the build service | 20:04 |
ali1234 | i don't know if this package is one of them, but just saying | 20:05 |
penguin42 | that would be very very nasty of them | 20:05 |
ali1234 | Qt used to have this problem, but i think it was fixed | 20:05 |
ali1234 | that was annoying since building Qt from scratch takes a looong time | 20:06 |
penguin42 | ok, well I've attached a fix to that bug report, I guess I could get up the energy to create a bzr branch with the fix and try and remember how to do it | 20:06 |
jtaylor | hm | 20:07 |
jtaylor | is that patch safe? | 20:07 |
jtaylor | are you upstream? | 20:08 |
penguin42 | jtaylor: It works (tm) - I've run a two player game against myself and multiple levels on the one player | 20:08 |
* penguin42 isn't the upstream | 20:08 | |
jtaylor | its just always risky when you remove assignments from function calls | 20:09 |
jtaylor | who knows if the function ahs side effects | 20:09 |
penguin42 | jtaylor: Yeh see my comments in the bug report | 20:09 |
jtaylor | especially the one in the critical section | 20:09 |
penguin42 | which one? | 20:09 |
jtaylor | handler = network_client_get_handler(client); | 20:10 |
penguin42 | oh, the handler= network_client_get_handler? | 20:10 |
jtaylor | 188 game.-manager.c | 20:10 |
penguin42 | yeh, if you look at the code it actually then calls network_client_get_handler later - note that isn't a lock/read/unlock - that's two separate locks | 20:10 |
jtaylor | might be safer to just disable werror for unused-but-not-set | 20:10 |
penguin42 | yeh - I also say that in one of the comments :-) | 20:10 |
jtaylor | and submit the issue upstream | 20:11 |
penguin42 | except I'm not sure upstream is alive | 20:11 |
penguin42 | jtaylor: which makes me wonder if the right solution is just to nuke the package | 20:12 |
jtaylor | if it still works one can keep it | 20:14 |
jtaylor | doesn't have any usability bugs | 20:14 |
penguin42 | well with that test build it doesn't currently build | 20:14 |
penguin42 | but yes I think the current build works still | 20:15 |
jtaylor | as there is no upstream and no real gain by fixing these warnings I'd disable the warning | 20:17 |
jtaylor | not worth risking adding a bug no one really cares about fixing | 20:17 |
penguin42 | jtaylor: The log snippet extractor for builds could do with spotting those errors | 20:18 |
* penguin42 suspects that warning breaks zillions of packages | 20:21 | |
jtaylor | quite a few | 20:22 |
jtaylor | but not all use -werror | 20:22 |
jtaylor | so build only fails for a very small fraction | 20:22 |
penguin42 | it's not a bad discipline to get into, it does help spot a lot of DOH type of bugs - but some times the compiler can be a little over zealos | 20:22 |
htorque | hi, how would i add a distro task ("<project> (ubuntu)") to a bug? | 20:23 |
yofel | htorque: which bug? In general, click on "Also affects distribution" | 20:23 |
* penguin42 always seems to fight with lp when I want to do that | 20:24 | |
htorque | yofel: gna, i must be blind, thanks! | 20:24 |
htorque | bug 835646 | 20:24 |
ubot4 | Launchpad bug 835646 in unity (Ubuntu) (and 1 other project) "unity-panel-service memory leak with Kile (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/835646 | 20:24 |
yofel | hm, and what do you want to add? | 20:25 |
htorque | i already did | 20:25 |
yofel | k | 20:26 |
htorque | i opened it against unity and added unity (ubuntu) as it's also happening there | 20:26 |
penguin42 | anyone any good with python/gtk issues - I've got virt-manager not opening a window, but I can't quite see why | 20:27 |
yofel | python yes, gtk no | 20:30 |
penguin42 | it's bug 551432 - but I'm fairly sure it's on the GTK side of things, or maybe the glade description of the window | 20:31 |
ubot4 | Launchpad bug 551432 in virt-manager (Ubuntu) "virt-manager create disk image with LVM hangs for ever (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/551432 | 20:31 |
penguin42 | it's also possible something is screwey with the lvm code but I don't quite see how that would stop the window appearing given where I've already got debug showing it got to | 20:32 |
=== abhinav_ is now known as abhinav- | ||
clemenstimpler | hi everyone - how do i file a bug against a translation? :) | 22:55 |
hggdh | ah well. Late, but... translation bugs... look at https://wiki.ubuntu.com/Bugs/HowToTriage, search for translation | 23:05 |
=== yofel_ is now known as yofel |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!