DelemasI 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
ubot4Launchpad 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/59482701:51
* Delemas finds the HowToFix wiki entry and gives it a whirl...01:59
yofelDelemas: 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 SRU02:01
DelemasYes 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
yofelthen 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-motu02:04
DelemasThe 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
RedSingularitymicahg: 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
RedSingularitybug 69992204:08
ubot4Launchpad bug 699922 in thunderbird (Ubuntu) "Thunderbird displays notification on wrong monitor (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/69992204:08
micahgRedSingularity: sounds like a dupe04:10
RedSingularitymicahg: lol see what i mean?  Have any idea of what bug?04:10
micahgRedSingularity: nope, taking a look, I just know it's an old issue04:10
RedSingularitymicahg: i did see one about windows...it is a few years old though04:11
ddecatorover 6 years old04:11
micahgRedSingularity: sorry, I don't have time to dig further, but the issue sounds familiar, feel free to upstream04:43
RedSingularitymicahg: Alright.  Thanks much for looking buddy :)04:44
RedSingularityjibel_: Why does the update-manager bring up the gnome-power-manager?05:45
om26ervish, are bugs in classic desktop session considered papercuts?09:12
om26erbug 50640409:14
ubot4Launchpad 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/50640409:14
seb128om26er, hi09:14
seb128om26er, that one will be fixed before release, no need to papercut it09:14
om26erseb128, totally awesome, have been waiting for this for a while ;)09:15
* om26er just realized 60% of the comments are his own :p09:16
seb128om26er, btw do you triage telepathy-logger sometimes? there are 2 recent crashers that needs to be forwarded to the upstream tracker09:18
om26erseb128, have not seen them in email might be private? checking and will send upstream09:19
seb128om26er, you are not suscribed to this source it seems09:21
ubot4seb128: Error: Bug #725015 is private.09:21
ubot4Launchpad bug 725512 in telepathy-logger (Ubuntu) "telepathy-logger crashed with SIGSEGV in free() (affects: 16) (dups: 11) (heat: 120)" [Medium,Confirmed]09:21
om26ertelepathy team is not subscribed?09:21
seb128seems now09:21
seb128oh it is, sorry09:22
seb128well the second one is public and got duplicates09:22
om26erthe latest version is 0.2.3 we have 0.2.1 btw09:22
seb128om26er, weird09:24
seb128om26er, http://git.collabora.co.uk/?p=telepathy-logger.git;a=summary has 0.2.109:24
seb128do you know where they worked on 0.2.3?09:24
om26erthey moved to freedesktop remember09:24
seb128if I want to see the commits it that version?09:24
seb128oh right09:24
seb128it's written at the top of the page09:25
vishom26er: hey..09:25
vishom26er: which bug?09:25
seb128om26er, ok, we should perhaps update, not sure if it's still worth upstreaming those 2 bugs09:26
om26ervish,  Hi! bug 506404 which seb just said would be fixed before release09:26
ubot4Launchpad 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/50640409:26
vishom26er: oh! cool :)09:27
om26erseb128, the first is upstreamed already, sending the second lets see what they say on this09:27
seb128om26er, thanks09:28
om26er_seb128, upstream says updating  to tp-logger 0.2.3  should fix the issues12:59
seb128om26er_, ok great, I uploaded that earlier13:13
=== shadeslayer_ is now known as shadeslayer
=== meetingology` is now known as meetingology
=== brendand_ is now known as brendand
dholbachhttps://wiki.ubuntu.com/UbuntuDeveloperWeek day 2 starting in 25 minutes in #ubuntu-classroom15:36
Jthornhaving 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(016:04
Jthornuser id not found16:04
=== zyga is now known as zyga-food
=== berdario is now known as Tiibiidii
penalvchPlease mark Medium Importance for LibreOffice bug 62675517:28
ubot4Launchpad 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/62675517:28
kamusinpenalvch, ;)17:34
penalvchkamusin: Thank you.17:35
acarpineI think the importance field of the bug 362875 should be set to Medium (the wireless card doesn't work)18:17
ubot4Launchpad 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/36287518:17
=== zyga is now known as zyga-afk
=== erhesrhsrtb54vyh is now known as Elbrus
=== zyga-afk is now known as zyga
psusibug #161126 appears to have been rejected by Debian.  Shouldn't the status in Ubuntu also then be set to WontFix?19:26
ubot4Launchpad bug 161126 in ddrescue (Debian) (and 2 other projects) "Package name misleading (affects: 5) (heat: 5)" [Unknown,New] https://launchpad.net/bugs/16112619:26
micahgpsusi: yes, especially with the restructuring of those packages happening in Debian19:28
psusimicahg: what restructuring?19:52
psusiit looks to me like they just decided to keep both... one just got updated to a new upstream the other day in unstable19:53
micahgpsusi: http://lists.debian.org/debian-devel/2011/02/msg00594.html19:55
psusipfft... why the heck did he close the bug report requesting that then?19:58
psusiseems like he rejected the suggestion to do that there, and now on the ml is saying he is going to do it19:58
ddecatormicahg: do you still prefer to add lp bugs to bugzilla yourself, or do you prefer we use lp to link them?19:58
micahgddecator: using LP is fine20:02
ddecatormicahg: alright, just wanted to check. i'm helping RedSingularity file that thunderbird bug upstream20:03
micahgddecator: you should be able to link when filing as well (See Also link)20:03
ddecatormicahg: oh, didn't know that, thanks for pointing it out. RedSingularity ^20:04
RedSingularitymicahg: in the "URL" box when filing?20:05
RedSingularitymicahg: "URL that demonstrates the problem you are seeing (optional)."20:06
ddecatori think that's for a website that causes the issue in question20:06
RedSingularitystill looking....20:07
RedSingularityddecator: 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
ddecatorright, if the website is broken. the URL is for a website that should work but doesn't because of a bug in firefox20:08
ddecatormicahg: is the link added after the report is filed? i know there is the "See Also" part on the completed report20:08
micahgddecator: it should be on the advanced details for filing20:09
ddecatormicahg: i don't see it anywhere on the page for filing a new bug20:12
RedSingularityddecator: me neither...Additional info maybe??20:13
ddecatorRedSingularity: there is a separate field for "See Also" where the lp link should be on the completed report20:13
RedSingularityddecator: 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
ddecatorRedSingularity: 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 filed20:16
micahgddecator: could need special privs, idk20:17
ddecatormicahg: i think it is :)20:17
RedSingularityddecator: just submit then?20:17
ddecatormicahg: do you want to add it for us or should RedSingularity just put a link in the description?20:18
RedSingularityddecator: i "could" put it in the additional information area as well20:19
ddecatorRedSingularity: i'm just not sure if the mozilla devs have some sort of preference20:20
micahgRedSingularity: it'll be added to see also when you link on LP20:23
ddecatorah, i didn't know linking it would add it automatically20:25
RedSingularitymicahg: bug 699922 is ready for the stamp.  I think "low" would be more than appropriate :)20:33
ubot4Launchpad 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/69992220:33
hjdIs 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
ubot4Launchpad bug 714846 in linux (Ubuntu Karmic) (and 6 other projects) "CVE-2010-4242 (affects: 1) (heat: 396)" [Low,In progress] https://launchpad.net/bugs/71484620:41
micahghjd: if it's appropriate, it should be fine20:44
micahghjd: https://wiki.ubuntu.com/SecurityTeam/BugTriage20:45
hjdmicahg: 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
micahghjd: so, to answer your question, you can add them if they actually apply to the bug reporrt20:49
psusibug #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
ubot4Launchpad 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/11846721:22
yofelpsusi: by email interface and launchpad API - I have a script if you want it21:24
yofelpsusi: http://bazaar.launchpad.net/~yofel/+junk/lp-scripts/view/head:/lp-set-expired.py21:27
charlie-tcawhy not set it invalid, if it can be reproduced in two years?21:28
charlie-tcaOr since it is valid upstream, confirm it based on that21:29
psusicharlie-tca: because it has been set to expired, and so the next state is supposed to be expired?21:39
charlie-tcaby that reasoning, almost every bug marked incomplete should then expire next,21:40
psusiyes, that is the rule21:40
charlie-tcaInstead, they could be marked "confirmed", "triaged", "expired", or even back to "new"21:40
psusiwell yea, but barring any other action, it goes to expired after a while21:41
charlie-tcaThey do not have to expire. It depends on the actual responses and further action taken21:41
charlie-tcaIf you expire every incomplete bug, why bother asking for anything else, just expire them instead21:41
psusibecause you ask for something, AND mark it as incomplete, then give time to get a response and complete it21:41
charlie-tcaThere really is not a rule that says a bug went incomplete, it must then expire21:42
psusinormally lp automatically transitions it to expired after a while, but in this case, that was blocked by the upstream link21:42
charlie-tcaand what happened upstream? is it dead?21:42
charlie-tcaDid upstream declare the bug invalid?21:43
psusino, it's just sat there for 2 years after someone said they could not reproduce it21:43
charlie-tcaUm, please do not expire any bugs I triage.21:43
psusiif it's triaged, then it isn't incomplete21:44
charlie-tcaIf I worked the bugs, leave them alone. They are mine to triage properly21:44
hggdhpsusi: 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
emdo any of you know why ubuntu would put untrusted packages in the Repo?22:19
paultagem: they won't -- which package is untrusted?22:20
paultagI'll be happy to check it out22:21
* paultag pokes em 22:24
micahgI got that warning a couple days ago22:27
micahgabout untrusted packages22:30
udienzmicahg, about gkamus, rpath has been fixed and re-uploaded again in revu23:30
udienzarrhh.. wrong place23:31

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