[00:00] ddecator: and you just got to know out bot too ;) [00:00] bug 511632 [00:00] yah, i just noticed that... [00:00] Launchpad bug 511632 in software-center "cannot download gstreamer0.10plugins bad" [Undecided,New] https://launchpad.net/bugs/511632 [00:00] that's the one =) [00:00] i couldn't tell if it might be a software problem or a network problem, so i asked for clarification... [00:01] ddecator: yes, 'Incomplete' when you ask the reporter for more info [00:01] (very helpful bot btw, kudos to whoever designed it) [00:01] yofel: thanks [00:01] !me | ddecator [00:01] ddecator: Hi! I'm #ubuntu-bugs's favorite infobot, you can search my brain yourself at http://ubottu.com/factoids.cgi - Usage info: http://wiki.ubuntu.com/IRC/Bots [00:02] haha, that's sweet [00:02] :P [00:02] any weechat user here? [00:04] can i ask for your opinion on another one yofel? [00:04] ddecator: sure, in general: just ask the question together with the bug number. If anyone can help s/he will answer you [00:05] perfect. bug 511604 which i'm thinking of asking him to clarify that everything else works with firefox and mark as incomplete, but maybe mark as invalid and ask him to post the bug on moonlight's bugtracker? [00:05] Launchpad bug 511604 in firefox-3.5 "Firefox with Moonlight 2.0 closes immediately " [Undecided,New] https://launchpad.net/bugs/511604 [00:07] hm... [00:08] maybe incomplete for now, invalid if he says everything else works? [00:09] I don't know much about triaging firefox bugs to be honest. Any firefox triagers here right now? (I would mark it Incomplete until he confirms that the page works fine with Moonlight disabled) [00:10] micahg should be back in a few [00:11] well the hard part is, firefox has bugzilla for their bugs, and i think the moonlight team has their own tracker for their bugs (i could check) but i figured i could mark it incomplete, then after he responds let him know where to turn? [00:11] ddecator: most probably they use something else. Upstreams differ on what they use to log bugs, and *how* they do it [00:13] hggdh: both firefox and moonlight have their own bug filling systems, so do you think i should tell the person to file it on moonlights if it's a silverlight problem or on mozillas if it's a firefox problem and then mark it invalid? [00:13] we first need to know more. Then we can go either way [00:14] know more from micahg or more from the submitter? [00:14] and, most of the times, if it is a problem with an Ubuntu package, we end up logging it upstream (but nothing prohibits the OP from doing it) [00:15] from both ;-) I do not deal with ffox, but micahg is very good there [00:15] alright, i'll keep the bug open for now until micahg gets here, thanks hggdh and yofel =) [00:15] welcome [00:15] you're welcome [00:16] micahg: perfect timing :D [00:16] hi yofel [00:17] ddecator: ping [00:17] hi micahg, nice to meet you [00:18] mind helping me with a ff-3.5 bug report micahg? [00:18] ddecator: what can I do for you [00:18] ddecator: bug #? [00:19] micahg: i'm looking at bug 511604 and don't know whether to mark it incomplete and ask for more information (to determine if it's a firefox or a moonlight problem) or to mark it invalid and ask them to report it either on mozilla's or moonlight's bug trackers [00:19] Launchpad bug 511604 in firefox-3.5 "Firefox with Moonlight 2.0 closes immediately " [Undecided,New] https://launchpad.net/bugs/511604 [00:19] ddecator: 1. we track upstream bugs in LP as well [00:20] ddecator: 2. is it your bug or are you triaging? [00:20] micagh: well, i'm triaging...kind of, i'm waiting to be assigned a mentor so i'm just trying to find easy bugs to get started on so i can get a feel for things [00:20] ooohhh 12 hours for my build to start... [00:21] ddecator: k, I would suggest requesting an apport crash report [00:21] ddecator: look at this: https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport [00:24] micahg: ok, so i should ask the person to enable apport and submit the crash information that it collects? [00:26] ddecator: yes, here's the text I use, http://pastebin.ubuntu.com/361634/ [00:28] micahg: perfect, thanks, i really appreciate the help [00:28] ddecator: have you seen the canned responses page yet? [00:29] micahg: i saw a link to it somewhere, but i haven't looked through it yet...do you have a link? [00:29] https://wiki.ubuntu.com/Bugs/Responses [00:31] bookmarked it. thanks =) [00:34] ddecator: don't forget to check out the 'Knowledge Base' linked on top of the page. Most of the Busquad documetation is linked there. [00:35] yofel: thanks for reminding me. i've gone through a lot of it, but now that i've gotten my feet wet i'll go through everything again [01:18] hggdh, hows the feeling? ;) [01:19] nigel_nb: heh. It is always a bit stressful, but fun. Nice work there [01:20] hggdh, after a month of planning and hardwork, worth it ;) [01:21] certainly. It was *very* good. Worthy of sequels [01:22] i'm thinking of something immediately after lucid launch [01:22] there would be a lot of new users and some good attention about it to [01:22] yes indeed [01:22] you would have momentum [03:21] can someone pls mark bug #511743 triaged [03:22] Launchpad bug 511743 in ntp "typo in ntpdate manpage (patch included)" [Undecided,Confirmed] https://launchpad.net/bugs/511743 [03:31] kermiac: any suggested Importance? [03:41] hggdh: probably low - doesn't seem to be that much of an issue [03:41] hggdh: only replaces a "." with a "," [03:41] kermiac: done [03:41] yep [03:41] ty hggdh :) [03:42] might be interesting to send it over to Debian also [03:42] kermiac: yw [03:43] hggdh: I'm not to sure on the exact process on how to do that, I'm still reading through the wiki stuff regarding upstreams [03:43] in this case it is opening a bug on Debian (after checking none exists about that), and linking it on this bug [03:44] ok, ty. I'll check [03:44] to open a bug on Debian you have to use email (or use 'reportbug') [03:46] ty for the info hggdh [03:46] ym, kermiac [03:46] yw [04:44] bug #511787 was i right to mark this rant as invalid & mention the Code of Conduct? [04:44] Launchpad bug 511787 in ubuntu "where is the ubuntu laptop?" [Undecided,Invalid] https://launchpad.net/bugs/511787 [04:46] kermiac: correctly done so, in my view. Rants should be placed elsewhere. [04:46] ty hggdh. That's exactly what i thought too, I just wanted a second opinion [04:47] * micahg has a lot of bugmail backlog... [04:47] moi aussi [04:47] er. So do I [04:50] I've been going though bugmail most of today & still sot over 50 to check... oh well, it's good fun mostly hehe [04:50] s/sot/got [04:52] bug #511436 should this be file against plymouth? [04:52] Launchpad bug 511436 in ubuntu "Computer doesn't shut down" [Undecided,New] https://launchpad.net/bugs/511436 [04:52] i got confirmation from the OP that it's on an installed system, not a live cd [05:21] please mark this triaged https://bugs.launchpad.net/empathy/+bug/442023 [05:21] Launchpad bug 442023 in empathy "Error dialog too wide" [Low,Confirmed] [05:23] done. [05:25] hey guys, i wanted to use the stock replies userscript, but it appears to not work entirely perfect in chrome. - particularly it's not saving any replies I'm trying to have as options, and not offering any from the wiki internets (like it's supposed to)...any suggestions? [05:25] or is this a known issue? [05:28] there's a few branches listed on https://code.edge.launchpad.net/launchpad-gm-scripts that talk about chrome support, but it's not clear what to use then [05:29] * om26er thinks it also has the status 'experimental' [05:32] well sure, i'd rather something experimental but more functional [05:32] and would at least know what to start with if i'm gonna try to help patch it at all :) [05:44] superm1: om26er: https://launchpad.net/~gm-dev-launchpad/+archive/ppa [05:44] micahg, so that's built from trunk? [05:45] superm1: every so often [05:45] okay well i grabbed the same thing (from https://code.edge.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master) [05:45] is there a bug tracker for the scripts then so i can at least file a bug on how they're working in chrome? [05:47] micahg, well that's for firefox? [05:47] superm1: https://bugs.edge.launchpad.net/launchpad-gm-scripts [05:47] *only [05:47] * micahg thought greasemonkey was FF only [05:48] micahg, chrome can run greasemonkey scripts [05:48] i loaded LP Karma and it's working correctly [05:48] thanks for the tracker micahg [05:48] and i'd hate to have to use FF just for triaging bugs if i'm already using chrome for everything else :) [05:51] superm1: 3.7 should come close to matching chrome in speed [05:52] micahg, well we're not there today ;) [05:53] micahg, it's close, but chrome is still a little faster [05:53] ddecator: it's still alpha ;) [05:53] or rather, not even alpha [05:54] micahg, right, but surprisingly stable...except for the feature to run plugins in a separate process...that doesn't work yet [05:54] ddecator: well, they have regression tests constantly running [06:17] could someone please set bug 511603 as low importance? (or otherwise, if you think it is different) [06:17] Launchpad bug 511603 in gnome-panel "launchers in panel overlap main menu making it inaccessible" [Undecided,Confirmed] https://launchpad.net/bugs/511603 [06:19] isn't it upstream? [06:20] ddecator: have you seen the importance wiki page? [06:21] micahg, yes, but the issue has an easy work-around so i thought it would be considered low. [06:21] ah, ok [06:22] ddecator: what's the easy workaround? [06:22] micahg, if you remove icons from the panel, the the icons "blocking" the menus move back to the right of the menus. i left a note in the comments. not the ideal solution, but an easy fix in the meantime [06:23] ddecator: I don't think that's an easy workaround [06:23] i could be wronfg [06:23] ddecator: have you checked for duplicates? [06:23] I don't think the presence or absence of a workaround affects importance. [06:23] sounds common [06:23] persia: according to the wiki if there's an easy workaround, it's low [06:24] persia: https://wiki.ubuntu.com/Bugs/Importance [06:24] Right. So I change the kernel to not boot unless you put reallyboot=yes on the kernel command line, and tell people to change that? [06:24] micahg, it's a tough call...it's launchers that cause the problem, so it's the user that puts them there, and it's easy to just reduce the number of launchers on the panel. guess it depends on your definition of "easy" [06:24] But sarcasm aside, my point is more that there should be some judgement employed beyond just having a workaround. [06:24] persia: agreed [06:25] micahg, let me double check for duplicates... [06:25] In the case of this bug, the issue to me is more that there's a mismatch between visual representation and behaviour, more than that some stuff is temporarily hidden. [06:27] micahg, i didn't find any duplicates, assuming this isn't an upstream bug [06:28] persia, so you're thinking medium? [06:31] ddecator: I'd call it low because it's a cosmetic/usability issue that does not limit the functionality of an application [06:31] I just don't think it should be low because it can be easily worked around [06:32] persia, ok, that's what i was thinking, but i just wanted to clarify. and i wasn't thinking it was low just because it was easy to workaround, but it was the deciding factor for me...if it hadn't been easy to work around (the icons get stuck behind the menus for example) then i would have leaned towards medium because of functionality issues [06:33] ddecator: Under which medium guideline? [06:35] persia, well that depends. is gnome-panel considered a core application? (this might be a really stupid question, but i'm just starting out with all of this) [06:39] gnome-panel is defined as a core component of a GNOME session, so is a core application for Ubuntu Desktop users. [06:41] persia, then one of the medium guidelines is that it has a moderate impact on a core application. however, since the bug can be worked-around so there is no impact on gnome-panel, since there is no loss in usability, and since it does not seem to be a large group effected, then i'm thinking low [06:41] well, slight loss in usability in-that you have a limit to launchers on the panel... [06:41] OK. That's an argument I can accept. Thanks for going through it. [06:42] I usually just phrase that as "If the issue is PEBCAK, but valid, it's low" [06:42] persia, no problem, i just wanted to clarify myself. and thanks for making me walk through it more so i can learn these things faster [06:43] thanks for changed the importance persia [06:44] Now see if you can get that bug from "Confirmed" to "Triaged" :) [06:46] Oooooh, a challenge [06:48] well, i confirmed the bug on my machine, as well as found the temporary work around, i commented on the work around so the submitter would be informed, the description is detailed and easily understood (in my opinion), and it should be enough to be worked on...just two possibilities [06:49] A) the bug must be filed upstream to the GNOME team so they can work on it (not sure if this is something handled by their team or the Ubuntu team), and/or B) i could reproduce the event again on my machine, take screenshots, and add to the report so it will be more thorough [06:50] am i on the right track persia ? [06:50] what can be done of the bugs with last comments 1+ year ago although they are triaged and upstream don't seem to have an response on them [06:50] A) is key. Another thing you might do is investigate whether it is the panel or the menu applet, perhaps by trying to replicate with other applets. [06:51] om26er: If a bug is valid and well-triaged, and the software hasn't changed lots (or if it has changed, not in a way to affect that bug), leave it alone unless you are working to fix it. [06:51] That applies regardless of the age of the bug. [06:52] alright, let me try to replicate it with other applets... [06:52] * vish wouldnt expect any fixes for gnome-panel [06:52] from upstream [06:53] vish: Why not? [06:54] persia: the devs arent really working on it anymore[apart from crashers] , with gnome3 and the gnome-shell approaching [06:55] I'm not sure I agree with that entirely, but my opinion is largely from http://shanefagan.com/2010/01/15/debunking-the-gnome-3-myths/ [06:56] persia: yes , but my opinion was from the vibe i got from vuntz [06:56] they feel that the panel is basically broken [06:56] vish: I certainly don't expect any fixes for gnome-panel from vuntz :) [06:57] ;) [06:57] But I'm not convinced everyone has that opinion, and beleive there's a place for both. [06:57] persia, i replicated the behavior...the icons never go behind any other applets, including another instance of the Menu Bar, only the default Menu Bar to the far left [06:58] i'm going to add a screenshot... [06:58] Not even another applet on the far left, or another instance of the menu bar on the far left? [06:58] screenshot doesn't help much. [06:59] well then let me upload it to imgur a sec so you can see... [07:00] persia, no, it is only the default menu bar...i had other applets on there (trash, drawer, etc) and it didn't affect any of them: http://imgur.com/GTZ7A.png [07:01] Does it affect the leftmost applet (if you remove the default menu), or only that applet? [07:02] If really only that applet, and only in the default instance (removing it and adding a new menu applet on the far left doesn't have the issue), then it's likely not an upstream problem, but only an issue with how Ubuntu sets up the default menu applet. [07:02] But I suspect it's more general. [07:03] interesting...ok persia i added the trash applet, moved it to the far left, and the trash applet sits on top of the "System" menu [07:04] heh. See, it can affect other stuff. Now you have a deeper understanding of the bug, and may want to adjust the description :) [07:04] Keep going in circles until you're sure you understand the bug perfectly, and then, if it looks to be an issue with the software, rather than configuration, report it upstream. [07:05] At that point, I'd call triage done, although others may have other suggestions. [07:05] alright, let me do some toying with removing the default menu bar... [07:07] ah, alright, it effects whichever applet is furthest left...i put multiple drawers up and they are now stacking as i add more items [07:09] i'll update the description in more detail. i'm assuming this makes it a software issue, which means it needs to be filed upstream, but i haven't done that before so let me first add the description... [07:17] persia, alright, i added my description so i'm going to look at GNOME's bugzilla for any duplicates [07:20] persia, i found a duplicate on their bugzilla, but it is unconfirmed. should i still link the two? [07:23] or does anyone else have advice? [07:25] ddecator: "duplicate in bugzilla" ? you mean , you found the bug reported in bugzilla too? [07:25] vish, in GNOME's bugzilla, yes [07:26] ah , we usually say i found the bug reported upstream as well :) [07:26] ddecator: you can link the two bugs , select the "also affects project" [07:27] haha, gotcha, still figuring it all out =p. alright, thanks vish, i'll get to it then [07:39] ok, i linked upstream. could someone take a look at bug 511603 for me and see if there is anything i missed? [07:39] Launchpad bug 511603 in gnome-panel "launchers in panel overlap main menu making it inaccessible" [Low,Confirmed] https://launchpad.net/bugs/511603 [07:43] ddecator: Try to confirm in a newer release (description states 9.04) to make sure it's still present. Checking with lucid would be best. [07:44] Also, the description doesn't seem to indicate that it only happens to the leftmost applet (either upstream or in LP) [07:44] (unless you discovered some other behaviour) [07:45] persia, the description i put in my last comment states that. should i put it somewhere else as well? and if need be, i can boot into lucid in a minute, but i put in the comments that i reproduced the behavior on 9.10 [07:45] ddecator: You can edit the main bug description directly. [07:45] (and should do, if you can improve it) [07:46] ah, didn't realize i could/should do that. should i also put a short description into the upstream? [07:48] I'm not familiar with GNOME bugzilla triage guidelines, but I bet there's a link somewhere from www.gnome.org [07:53] alright, i updated the launchpad description. i'll try to hunt down the upstream guidelines [07:58] persia, the upstream doesn't seem to have guidelines for if you are adding to an already filed bug. however, having an account doesn't allow me to change the description or anything, just add a comment. i left the one saying that it filed on launchpad and effects ubuntu, then left a link saying that there were more descriptions there. do you think that's good enough? [07:59] ddecator: add the upstream link in LP [07:59] Probably. Developers like to get fewer bugmails if possible (but good ones). [07:59] micahg, i added the "Also affects project" link like the wiki said. is there something else i'm supposed to do as well? [08:00] ddecator: sorry, forgot to refresh [08:01] ddecator: you should have also mentioned the version affected upstream [08:01] otherwise, looks good [08:02] ah, didn't think about it...i can't edit it, and i don't want to spam them with bug mail, so should i leave it as is and just remember next time? [08:02] ddecator: maybe come back in the morning and ask someone with gnome superpowers to add the version affected [08:02] in the mean time, I'm moving the bug to triaged [08:02] in LP [08:04] thanks micahg , i'll remember to do that tomorrow [08:05] thanks for all of your help as well persia [08:06] ddecator: Thanks for chasing the bug. Now for the next one :) [09:29] could someone set Bug #511767 and Bug #511670 , to triaged/low , they have been sent upstream [09:29] Launchpad bug 511767 in f-spot ""Hash for Duplicates" is non-intuitive" [Undecided,New] https://launchpad.net/bugs/511767 [09:29] Launchpad bug 511670 in gedit "Gedit displays shadow on top of edit window in fullscreen mode" [Undecided,Confirmed] https://launchpad.net/bugs/511670 [11:00] please mark this triaged/low https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/422525 [11:00] Launchpad bug 422525 in gwibber "Does not remember window position or selected view" [Undecided,Confirmed] [11:10] Hi, I am working on bug #476817 however we seem to got stuck, maybe there is someone here that might have some idea on how to proceed? [11:10] Launchpad bug 476817 in xserver-xorg-video-intel "[i855] [karmic] X freezes with intel 855GM videocard" [Undecided,Confirmed] https://launchpad.net/bugs/476817 [11:12] vish: I disagree with your triage of 511670. Note that the bug #91876 was fixed in compiz, not in eog. 511670 seems to me to be a regression of 91876, rather than a upstream gedit bug. [11:12] Launchpad bug 91876 in ubuntu "cdrom device does not exist" [Undecided,Invalid] https://launchpad.net/bugs/91876 [11:12] Err, bug 91786 [11:12] Launchpad bug 91786 in compiz "Compiz's Panel shadows show on top of other windows" [Low,Fix released] https://launchpad.net/bugs/91786 [11:13] vish: Of course, if you can defnend it, I may change my mind :) [11:13] persia: panel shadows are different from this... this is the shadow from the gtk toolbar falling on the page [11:14] persia: the compiz panel shadow was falling on the window [11:14] vish: OK. How was it fixed in eog? [11:14] persia: in EOG , the gtk toolbar shadow is not shown when the toolbar is hidden [11:18] om26er: I think 422525 needs further investigation, as it appears upstream believes it to have been fixed, especially because it's a bug against a PPA. If the issue is now only a distro issue, the description needs adjustment, at a minimum [11:18] vish: OK, and you've checked the relevant issues to verify that this is an eog-specific change, and not a compiz change? [11:19] persia: the gedit bug has nothing to do with compiz. I get this shadow too in KDE with kwin [11:20] Hrm. I don't get it with metacity, which is part of why I'm arguing :) [11:20] persia, i have edited the description [11:21] mark this triaged as it has been upstreamed [11:21] https://bugs.launchpad.net/gwibber/+bug/503247 [11:21] Launchpad bug 503247 in gwibber "Send Reply has no effect" [Undecided,Confirmed] [11:22] om26er: Again. The bug appears to reference a PPA version,:1) that doesn't deserve an Ubuntu task, and 2) upstream reports it to be fixed. [11:22] persia: the shadows are drawn by compiz but , the panel shadow had to be hacked by Amaranth , and the shadow had to be drawn twice apart from the windows [11:22] once for the windows and then again from the panel , that was why the panel shadow was a bug in compiz [11:22] persia, should i change everything in description and add mine? [11:22] s/from/for [11:23] vish: Hrm. OK, if you're sure. I'm just bothered because I can't reproduce it. [11:23] om26er: You should try to make the description as accurate as possible, using whatever means that takes. [11:23] persia, sure thanx. [11:23] om26er: Further, the description should ideally present enough information that a developer doesn't need to hunt through the bug comments to understand the issue. [11:24] persia: fwiw , i get the shadow on the page with metacity too [11:24] gedit fullscreen shadow* [11:24] Hrm. Very odd indeed. Oh well. [11:26] persia, see now. is it ok to be triaged? [11:27] om26er: No, because that's a different bug. [11:28] Especially as the bug has tracked the change being applied to fix it in bzr from upstream through to Ubuntu. [11:29] I tried it if I resize gwibber and place it at a certain place of screen and quit and start it again it opens at the same location [11:29] So, to triage this, you need to check if the patch was unapplied for some reason, and if so, clearly indicate that it's a reopening, or close it as Fix Released, and go report a new bug. [11:30] ok [11:32] Hrm. I can't figure out where to go with 476817 either. [11:37] om26er: I'm also not going to mark 503247 as triaged, because I still don't understand the bug after reading the description and looking at the screenshots. It looks like maybe some new feature is being requested to auto-activate a window under certain conditions, or maybe prevent the user from completely hiding the entry box, but it's just not clear what, and in either case, I'm curious why this wouldn't be wishlist. [11:37] Sending upstream is just one part of triage, and usually the last step. [11:51] persia, now can you please look at it again https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/422525 [11:51] Launchpad bug 422525 in gwibber "Does not remember window position or selected view" [Undecided,Confirmed] [11:52] om26er: This also looks like a completely different bug. [11:52] this is what the user wanted to explain [11:53] om26er: On what basis do you believe the original bug to be 1) even valid in Ubuntu, and 2) if valid, not closed? [11:54] persia, this bug was a mixture of two bugs one was reported else where and is fixed now and the other part is still the problem so I have change it to the other part [12:01] om26er: Could you explain in more detail? I've read the original description and the comment stream, and it seems to me that things have been fixed. [12:02] I just reproduced [12:04] persia, click on facebook account and then close(not quit) it will minimize to indicator applet then again click on indicator applet and gwibber will popup but now facebook won't be selected rather messages pane will open [12:04] om26er: You've apparently produced two behaviours, based on the bug changes: 1) when maximised and closed, the window isn't maximised on restart, and 2) when running in a facebook pane, and closed, and reopened, it doesn't restart in a facebook pane. I fail to see how either of these are "When gwibber starts, it does not remember the previous window position or the last selected view". [12:05] OK, so this is gwibber not remembering prior state. How was this the original bug? [12:05] persia, here 'selected view' means not remembering facebook pane [12:06] OK, and you've set the description to be against lucid. [12:06] Setting low/triaged [12:07] persia, thank you for your time [12:07] I still think it would be better to junk this bug as a bad try and create a new bug, because of the bzr branch references. [12:08] By making this bug more specific, you'll need to clean up the branch references, and someone looking through the bzr history later may be confused. [12:08] But, you have triaged the bug, so I've marked it as such (regardless of whether I think it ought be triaged). [12:09] should I open a clean bug report and mark this duplicate or invalid? [12:09] om26er: Thanks for your effort with bugs. I may believe you're overeager in calling things triaged in most cases I happen to respond to your status change requests, but I really do appreciate the work you're doing to try to improve the state of the bugs. [12:10] Were I handling this bug, I'd have changed the description to be just about position, and then marked it Fix Released, and opened a new bug about the views. [12:10] If there were no bzr links and references in patches in other bugs, I'd do precisely what you've just done. [12:11] But that's because I tend to find it easier to file new bugs than clean up references in old ones. On the other hand, I believe this to be my personal preference, rather than part of how people should be triaging bugs. [12:11] So I have no argument with what you've done, except that the branch references need cleanup. [12:12] ok [14:04] Whishlist bug 511912 [14:04] Launchpad bug 511912 in irssi "Make a menu item for Irssi" [Undecided,New] https://launchpad.net/bugs/511912 [14:09] yofel: Done. Please also update the description to point out that it should open in a terminal, etc. and push to Debian. The Debian irssi maintainer tends to be fairly responsive (and has an interest in Ubuntu) [14:09] will do [14:11] yofel: By the way, can't you set wishlist yet? [14:11] persia: bdmurray seems to be on a trip [14:11] so not yet [14:13] well then, it's been a while since I've used reportbug... [14:14] bug 1 [14:14] Launchpad bug 1 in tilix "Microsoft has a majority market share" [High,New] https://launchpad.net/bugs/1 [14:14] Yay, LP API. [14:25] persia: done [14:26] jpds: No more screen scraping? [14:28] persia: https://code.edge.launchpad.net/~jpds/ubuntu-bots/bugs-via-launchpad-api/+merge/17957 ← no more /+text reading. [14:29] Lovely! [14:35] It's only on ubot4 for now (needs Lucid packages). [14:36] ubot4 is in some of my favorite channels though :) [14:36] persia: Error: I am only a bot, please don't think I'm intelligent :) [14:38] \o/ [15:27] Hi [15:28] Hey strycore [15:29] There's a dead link here : https://wiki.ubuntu.com/BugSquad/KnowledgeBase/Classes/Triaging in the Bug Triage paragraph ( https://wiki.ubuntu.com/ReportBugs2 ) , does this page exist somewhere else ? [15:30] I'm trying to gather all the information about bug reporting to make a PDF document, it's the only way I will understand the whole thing ^^ [15:31] Hrm. I don't see where that goes with a quick look. [15:32] You'd have to track down the rest of the classes (and I don't see them at all: probably moved in some wiki reorg), and then change the link. [15:34] ok I'll try to do that [15:37] Good luck. === Saby is now known as Saby_ === Saby_ is now known as Saby [15:50] bug 352228 [15:50] Launchpad bug 352228 in linux (Ubuntu Karmic) (and 1 other project) [affects 28] "Intel Wireless 5300 AGN: iwlagn: No space for Tx" [Medium,Confirmed] https://launchpad.net/bugs/352228 [15:50] Not too shabby. [15:55] jpds: bot updated? nice :D [15:55] yofel: Still improving the code a bit. [15:56] would it make sense to add a duplicates indication? [dup 19] maybe? or would that be an overload of information [15:57] bug 41231 [15:57] Launchpad bug 41231 in nautilus (Ubuntu) "Nautillus freezes after opening a large sized sub-folder in a folder in the home directory (dup-of: 26198)" [Low,Invalid] https://launchpad.net/bugs/41231 [15:57] Launchpad bug 26198 in nautilus (Ubuntu) (and 1 other project) "Nautilus Thumbnail creation freeze system" [Low,Fix released] https://launchpad.net/bugs/26198 === yofel_ is now known as yofel [16:04] yofel: There doesn't seem to be anything about number of duplicates in the api docs. [16:04] nvm then [16:04] yofel: Maybe worth filing a bug against LP asking for it? [16:06] persia: could be, but someone that knows the LP API should do that, I've never even looked at it until now [16:07] Let me investigate something. [16:09] Oh hi, bugs does have a "duplicates" method. [16:10] bug 352225 [16:10] Launchpad bug 352225 in notify-osd (Ubuntu) "notify-osd crashed with SIGSEGV in _XReply() (dup-of: 351593)" [Medium,Invalid] https://launchpad.net/bugs/352225 [16:10] Launchpad bug 351593 in notify-osd (Ubuntu) "notify-osd crashed with SIGSEGV in _XReply() (affects 4) (dups: 9)" [High,Fix released] https://launchpad.net/bugs/351593 [16:10] yofel: ^--. [16:11] cool :D [16:44] hey, is it me or bug #423694 && #421347 are dups? [16:44] Launchpad bug 423694 in gnome-power-manager (Ubuntu) "session active, not inhibited, screen idle message (affects 19) (dups: 1)" [High,Confirmed] https://launchpad.net/bugs/423694 [16:44] ubot4, #421347 [16:44] Factoid '421347' not found [16:45] bug 421347 [16:45] Launchpad bug 421347 in xserver-xorg-video-intel (Ubuntu) "[i945gm] gnome-power-manager and blanking (removal of bodges) (affects 28) (dups: 1)" [Undecided,Confirmed] https://launchpad.net/bugs/421347 [16:46] Tallken: ubot4 doesn't understand #XXX references, use bug XXX instead [16:46] yofel, thanks :) [16:48] yofel, can you give a quick look and tell me if they aren't dups? just if I'm missing some tag which would indicate they're being treated as belonging to something different [16:48] since the first uses [i945gm] [16:48] Tallken: a moment, have to finish something else first [16:48] ok, thanks in advance :) [16:49] when you want my input, use the nickname, will continue some work here but using my nickname pops up stuff :p [16:49] I know :P [17:00] I could've disabled it :p [17:00] heh [17:13] bug 397839 [17:13] Launchpad bug 397839 in gnome-power-manager (Fedora) (and 5 other projects) "Screen randomly goes off in karmic (affects 27) (dups: 6)" [Unknown,Fix released] https://launchpad.net/bugs/397839 [17:13] this is one confusing issue... [17:15] yofel: the bug is highly hardware specific , it is most probably in xorg... [17:21] Tallken: well, as vish this seems to be quite specific. As I use KDE and never had an issue like this with my i945GME I can't really comment on this [17:21] *as vish said [17:22] but vish commented on a *third* bug related? [17:24] Tallken: the 423694 is a dup of the other bugs , since its just an alert in gpm to say ... check your xorg , its not working properly [17:24] ah ok [17:25] so the three bugs pop out the same warning [17:25] but the causing issues are different [17:25] so, not dups [17:25] Tallken: but , some see the message even when they dont have blanking... ;) [17:26] ok, thanks for the explanation :) [17:26] np.. [17:26] I'd say my problem was the 397839 but will wait to see if it happens again before I mark the "this bug affects me too" [17:27] Tallken: it would be better if you opened a new bug... since the bug has been marked as fixed.. [17:28] LOL hadn't noticed [17:28] thanks for the warning [17:28] will wait for it happen again to do it though [21:00] anyone available to give me there opinion on a bug? [21:00] their* [21:01] err... [21:01] !ask [21:01] Please don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [21:01] ;) [21:01] :p [21:03] hm, there was another one... [21:03] !anyone [21:03] A large amount of the first questions asked in this channel start with "Does anyone/anybody..." Why not ask your next question (the real one) and find out? [21:03] there ^^ [21:03] ddecator: in short: yes [21:03] we're waiting for your question/bug number :) [21:04] we are waiters [21:04] * BUGabundo goes get food [21:04] haha, fair enough...it's actually a bug you subscribed to yofel , bug 511632, i don't think it can be confirmed, and i think it's a problem with gst-plugins-bad-multiverse0.10 instead of software-center (i changed it), and i'm going to give the guy a link to the package, but i'm not sure how to file the bug [21:04] Launchpad bug 511632 in gst-plugins-bad-multiverse0.10 (Ubuntu) "Cannot download gstreamer0.10-plugins-bad (affects 1)" [Undecided,Incomplete] https://launchpad.net/bugs/511632 [21:05] oh that one... [21:06] i updated the description and everything, but i can't find any bugs upstream...but it doesn't seems to be that specific package, and he's tried several servers, so i'm at a loss [21:06] it seems to be that specific package, it doesn't seem to be the software center* [21:12] ddecator: every time you changed servers, did u try another package to see if it works? [21:13] nigel_nb, i didn't change servers. i'm running 64-bit and the submitter is running 32-bit so i didn't know if that would make a difference. and i didn't as him to try other packages after switching servers, i just asked him to run 'sudo apt-get upate' after each change. i've had no trouble getting the package which is why i haven't confirmed the bug [21:14] ddecator: is multiverse enabled? [21:15] micahg: would the package appear at all if it was disabled? [21:15] yofel: idk [21:15] yofel: possibly if something suggests it [21:15]