| Delemas | I submitted a bugfix package in a PPA as a fix for a bug 594827. How does it end up in Universe? Should I change status to Fix Committed? | 01:51 |
|---|---|---|
| ubot4 | Launchpad bug 594827 in freeipmi (Debian) (and 1 other project) "broken bmc-watchdog init script/logrotate config (affects: 2) (heat: 28)" [Undecided,New] https://launchpad.net/bugs/594827 | 01:51 |
| * Delemas finds the HowToFix wiki entry and gives it a whirl... | 01:59 | |
| yofel | Delemas: does this still happen with 0.7.17~beta2-1 in maverick and natty? if not the bug should be fix released - and your bugfix only applied to lucid as an SRU | 02:01 |
| Delemas | Yes the bugs still happen in all the recent builds right up and including 0.8.12 which is the latest Debian devel (or whatever it is called...) | 02:03 |
| yofel | then you should include a debdiff against the natty package, subscribe ubuntu-sponsors so it gets uploaded - once it's fixed you can prepare SRUs for maverick and lucid. Best ask for help in #ubuntu-motu | 02:04 |
| Delemas | The patches are quilted so they could be applied to 0.7.17~beta2-1 and it could use a similar upstart script... | 02:04 |
| === wagle_ is now known as wagle | ||
| RedSingularity | micahg: confirmed a bug in thunderbird. If you could take a look that would be great! I did search for dupes but you always seem to find the ones I miss. :) | 04:08 |
| RedSingularity | bug 699922 | 04:08 |
| ubot4 | Launchpad bug 699922 in thunderbird (Ubuntu) "Thunderbird displays notification on wrong monitor (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/699922 | 04:08 |
| micahg | RedSingularity: sounds like a dupe | 04:10 |
| RedSingularity | micahg: lol see what i mean? Have any idea of what bug? | 04:10 |
| micahg | RedSingularity: nope, taking a look, I just know it's an old issue | 04:10 |
| RedSingularity | micahg: i did see one about windows...it is a few years old though | 04:11 |
| ddecator | over 6 years old | 04:11 |
| micahg | RedSingularity: sorry, I don't have time to dig further, but the issue sounds familiar, feel free to upstream | 04:43 |
| RedSingularity | micahg: Alright. Thanks much for looking buddy :) | 04:44 |
| RedSingularity | jibel_: Why does the update-manager bring up the gnome-power-manager? | 05:45 |
| om26er | vish, are bugs in classic desktop session considered papercuts? | 09:12 |
| om26er | bug 506404 | 09:14 |
| ubot4 | Launchpad bug 506404 in gnome-panel (Ubuntu) (and 1 other project) "System menu in top panel also shows logout/shutdown when using indicator-applet-complete (affects: 10) (dups: 5) (heat: 66)" [Medium,Confirmed] https://launchpad.net/bugs/506404 | 09:14 |
| seb128 | om26er, hi | 09:14 |
| seb128 | om26er, that one will be fixed before release, no need to papercut it | 09:14 |
| om26er | seb128, totally awesome, have been waiting for this for a while ;) | 09:15 |
| * om26er just realized 60% of the comments are his own :p | 09:16 | |
| seb128 | om26er, btw do you triage telepathy-logger sometimes? there are 2 recent crashers that needs to be forwarded to the upstream tracker | 09:18 |
| om26er | seb128, have not seen them in email might be private? checking and will send upstream | 09:19 |
| seb128 | om26er, you are not suscribed to this source it seems | 09:21 |
| seb128 | https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/725015 | 09:21 |
| ubot4 | seb128: Error: Bug #725015 is private. | 09:21 |
| seb128 | https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/725512 | 09:21 |
| ubot4 | Launchpad bug 725512 in telepathy-logger (Ubuntu) "telepathy-logger crashed with SIGSEGV in free() (affects: 16) (dups: 11) (heat: 120)" [Medium,Confirmed] | 09:21 |
| om26er | telepathy team is not subscribed? | 09:21 |
| seb128 | seems now | 09:21 |
| seb128 | not | 09:21 |
| seb128 | oh it is, sorry | 09:22 |
| seb128 | well the second one is public and got duplicates | 09:22 |
| om26er | the latest version is 0.2.3 we have 0.2.1 btw | 09:22 |
| seb128 | om26er, weird | 09:24 |
| seb128 | om26er, http://git.collabora.co.uk/?p=telepathy-logger.git;a=summary has 0.2.1 | 09:24 |
| om26er | http://telepathy.freedesktop.org/releases/telepathy-logger/ | 09:24 |
| seb128 | do you know where they worked on 0.2.3? | 09:24 |
| om26er | they moved to freedesktop remember | 09:24 |
| seb128 | if I want to see the commits it that version? | 09:24 |
| om26er | oops | 09:24 |
| seb128 | oh right | 09:24 |
| seb128 | it's written at the top of the page | 09:25 |
| vish | om26er: hey.. | 09:25 |
| vish | om26er: which bug? | 09:25 |
| seb128 | om26er, ok, we should perhaps update, not sure if it's still worth upstreaming those 2 bugs | 09:26 |
| om26er | vish, Hi! bug 506404 which seb just said would be fixed before release | 09:26 |
| ubot4 | Launchpad bug 506404 in gnome-panel (Ubuntu) (and 1 other project) "System menu in top panel also shows logout/shutdown when using indicator-applet-complete (affects: 10) (dups: 5) (heat: 66)" [Medium,Confirmed] https://launchpad.net/bugs/506404 | 09:26 |
| vish | om26er: oh! cool :) | 09:27 |
| om26er | seb128, the first is upstreamed already, sending the second lets see what they say on this | 09:27 |
| seb128 | om26er, thanks | 09:28 |
| om26er_ | seb128, upstream says updating to tp-logger 0.2.3 should fix the issues | 12:59 |
| seb128 | om26er_, ok great, I uploaded that earlier | 13:13 |
| === shadeslayer_ is now known as shadeslayer | ||
| === meetingology` is now known as meetingology | ||
| === brendand_ is now known as brendand | ||
| dholbach | https://wiki.ubuntu.com/UbuntuDeveloperWeek day 2 starting in 25 minutes in #ubuntu-classroom | 15:36 |
| Jthorn | having a problem reinstalling from a live cd after formatting hard drive...the installation and demo won't load up just keep getting a failed: getpwuid(0 | 16:04 |
| Jthorn | user id not found | 16:04 |
| === zyga is now known as zyga-food | ||
| === berdario is now known as Tiibiidii | ||
| penalvch | Please mark Medium Importance for LibreOffice bug 626755 | 17:28 |
| ubot4 | Launchpad bug 626755 in openoffice.org (Ubuntu) (and 1 other project) "soffice.bin crashed with SIGSEGV in SwXTextRange::~SwXTextRange() (affects: 2) (dups: 1) (heat: 20)" [Undecided,New] https://launchpad.net/bugs/626755 | 17:28 |
| kamusin | penalvch, ;) | 17:34 |
| penalvch | kamusin: Thank you. | 17:35 |
| acarpine | I think the importance field of the bug 362875 should be set to Medium (the wireless card doesn't work) | 18:17 |
| ubot4 | Launchpad bug 362875 in linux (Ubuntu) "rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. (affects: 16) (heat: 86)" [Undecided,Confirmed] https://launchpad.net/bugs/362875 | 18:17 |
| acarpine | tks | 18:17 |
| === zyga is now known as zyga-afk | ||
| === erhesrhsrtb54vyh is now known as Elbrus | ||
| === zyga-afk is now known as zyga | ||
| psusi | bug #161126 appears to have been rejected by Debian. Shouldn't the status in Ubuntu also then be set to WontFix? | 19:26 |
| ubot4 | Launchpad bug 161126 in ddrescue (Debian) (and 2 other projects) "Package name misleading (affects: 5) (heat: 5)" [Unknown,New] https://launchpad.net/bugs/161126 | 19:26 |
| micahg | psusi: yes, especially with the restructuring of those packages happening in Debian | 19:28 |
| psusi | micahg: what restructuring? | 19:52 |
| psusi | it looks to me like they just decided to keep both... one just got updated to a new upstream the other day in unstable | 19:53 |
| micahg | psusi: http://lists.debian.org/debian-devel/2011/02/msg00594.html | 19:55 |
| psusi | pfft... why the heck did he close the bug report requesting that then? | 19:58 |
| psusi | seems like he rejected the suggestion to do that there, and now on the ml is saying he is going to do it | 19:58 |
| ddecator | micahg: do you still prefer to add lp bugs to bugzilla yourself, or do you prefer we use lp to link them? | 19:58 |
| micahg | ddecator: using LP is fine | 20:02 |
| ddecator | micahg: alright, just wanted to check. i'm helping RedSingularity file that thunderbird bug upstream | 20:03 |
| micahg | ddecator: you should be able to link when filing as well (See Also link) | 20:03 |
| ddecator | micahg: oh, didn't know that, thanks for pointing it out. RedSingularity ^ | 20:04 |
| RedSingularity | micahg: in the "URL" box when filing? | 20:05 |
| RedSingularity | micahg: "URL that demonstrates the problem you are seeing (optional)." | 20:06 |
| ddecator | i think that's for a website that causes the issue in question | 20:06 |
| RedSingularity | ah | 20:07 |
| RedSingularity | still looking.... | 20:07 |
| RedSingularity | ddecator: well it says under that "IMPORTANT: if the problem is with a broken web page, you need to report it a different way. " | 20:08 |
| ddecator | right, if the website is broken. the URL is for a website that should work but doesn't because of a bug in firefox | 20:08 |
| ddecator | micahg: is the link added after the report is filed? i know there is the "See Also" part on the completed report | 20:08 |
| micahg | ddecator: it should be on the advanced details for filing | 20:09 |
| ddecator | micahg: i don't see it anywhere on the page for filing a new bug | 20:12 |
| RedSingularity | ddecator: me neither...Additional info maybe?? | 20:13 |
| ddecator | RedSingularity: there is a separate field for "See Also" where the lp link should be on the completed report | 20:13 |
| RedSingularity | ddecator: just did a text string search for "see also" with no results. Does it come up after hitting "submit bug" at the bottom? | 20:15 |
| ddecator | RedSingularity: i'm not sure, that's why i asked micah. i know the field is on the completed report, but i thought you needed special privelages in order to add the link there, at least after the bug has been filed | 20:16 |
| RedSingularity | ah | 20:16 |
| micahg | ddecator: could need special privs, idk | 20:17 |
| ddecator | micahg: i think it is :) | 20:17 |
| RedSingularity | ddecator: just submit then? | 20:17 |
| ddecator | micahg: do you want to add it for us or should RedSingularity just put a link in the description? | 20:18 |
| RedSingularity | ddecator: i "could" put it in the additional information area as well | 20:19 |
| ddecator | RedSingularity: i'm just not sure if the mozilla devs have some sort of preference | 20:20 |
| RedSingularity | true | 20:21 |
| micahg | RedSingularity: it'll be added to see also when you link on LP | 20:23 |
| ddecator | ah, i didn't know linking it would add it automatically | 20:25 |
| RedSingularity | micahg: bug 699922 is ready for the stamp. I think "low" would be more than appropriate :) | 20:33 |
| ubot4 | Launchpad bug 699922 in thunderbird (Ubuntu) (and 1 other project) "Thunderbird displays notification on wrong monitor (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/699922 | 20:33 |
| hjd | Is it ok to add links to CVE reports on CVE-bugs where it's not present yet (like bug 714846), or are there certain requirements before it should be added? I've tried checking how to triage security bugs on the wiki, but I was unable to find anything. | 20:41 |
| ubot4 | Launchpad bug 714846 in linux (Ubuntu Karmic) (and 6 other projects) "CVE-2010-4242 (affects: 1) (heat: 396)" [Low,In progress] https://launchpad.net/bugs/714846 | 20:41 |
| micahg | hjd: if it's appropriate, it should be fine | 20:44 |
| micahg | hjd: https://wiki.ubuntu.com/SecurityTeam/BugTriage | 20:45 |
| hjd | micahg: ok. I read that page already, and the only thing I found was that confirmed bugs should usually be linked to a CVE-report. | 20:49 |
| micahg | hjd: so, to answer your question, you can add them if they actually apply to the bug reporrt | 20:49 |
| hjd | ok | 20:52 |
| psusi | bug #118467 has been marked as incomplete for nearly two years, but not expired due to it being filed upstream. comments in lp, and upstream, and redhat's bug tracker on the issue ( which has been closed ) indicate inability to reproduce, and the bug was originally reported in a release that has reached eol. Is there a way to manually change the status to expired? | 21:22 |
| ubot4 | Launchpad bug 118467 in gnome-applets (Fedora) (and 3 other projects) "Feisty Gnome Umount Utility displays empty Info Boxes on Failure (dups: 1) (heat: 5)" [Unknown,Won't fix] https://launchpad.net/bugs/118467 | 21:22 |
| yofel | psusi: by email interface and launchpad API - I have a script if you want it | 21:24 |
| yofel | psusi: http://bazaar.launchpad.net/~yofel/+junk/lp-scripts/view/head:/lp-set-expired.py | 21:27 |
| charlie-tca | why not set it invalid, if it can be reproduced in two years? | 21:28 |
| charlie-tca | Or since it is valid upstream, confirm it based on that | 21:29 |
| psusi | charlie-tca: because it has been set to expired, and so the next state is supposed to be expired? | 21:39 |
| charlie-tca | nope | 21:39 |
| charlie-tca | by that reasoning, almost every bug marked incomplete should then expire next, | 21:40 |
| psusi | yes, that is the rule | 21:40 |
| charlie-tca | Instead, they could be marked "confirmed", "triaged", "expired", or even back to "new" | 21:40 |
| psusi | well yea, but barring any other action, it goes to expired after a while | 21:41 |
| charlie-tca | They do not have to expire. It depends on the actual responses and further action taken | 21:41 |
| charlie-tca | If you expire every incomplete bug, why bother asking for anything else, just expire them instead | 21:41 |
| psusi | because you ask for something, AND mark it as incomplete, then give time to get a response and complete it | 21:41 |
| charlie-tca | There really is not a rule that says a bug went incomplete, it must then expire | 21:42 |
| psusi | normally lp automatically transitions it to expired after a while, but in this case, that was blocked by the upstream link | 21:42 |
| charlie-tca | and what happened upstream? is it dead? | 21:42 |
| charlie-tca | Did upstream declare the bug invalid? | 21:43 |
| psusi | no, it's just sat there for 2 years after someone said they could not reproduce it | 21:43 |
| charlie-tca | Um, please do not expire any bugs I triage. | 21:43 |
| psusi | if it's triaged, then it isn't incomplete | 21:44 |
| charlie-tca | If I worked the bugs, leave them alone. They are mine to triage properly | 21:44 |
| hggdh | psusi: no, there is no way to set a status of expired. The most you can do is set it as invalid (and add a blurb explaining why) | 22:11 |
| em | do any of you know why ubuntu would put untrusted packages in the Repo? | 22:19 |
| paultag | em: they won't -- which package is untrusted? | 22:20 |
| paultag | I'll be happy to check it out | 22:21 |
| * paultag pokes em | 22:24 | |
| micahg | I got that warning a couple days ago | 22:27 |
| ddecator | warning? | 22:28 |
| micahg | about untrusted packages | 22:30 |
| udienz | micahg, about gkamus, rpath has been fixed and re-uploaded again in revu | 23:30 |
| udienz | arrhh.. wrong place | 23:31 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!