[00:49] If a user reports a bug and it is really just user error should it be given an importance rating? [01:00] RedSingularity, I would say no, but the error needs to be explained to the reporter [01:00] so that they understand what happened and why [01:00] sound reasonable? [01:05] JFo: sounds good to me [01:05] thanks [01:06] my pleasure RedSingularity === stlsaint is now known as STLSAINT === emma is now known as emmaldp === emmaldp is now known as emma [05:53] * RedSingularity is all alone?? [05:53] RedSingularity: what makes you think that with 112 people in the room [05:54] micahg.......the silence...... [05:55] I am off to bed anyway. Have a good one :) [06:23] RedSingularity: why are you telling people to destroy their Firefox profiles? [07:26] hi all..am a newbee to linux..suppose i find that there is some mistake in any of the gnome apps,can i get its source code,fix it and report to the community? [07:28] to get the source code in a terminal type apt-get source [07:29] galoisfield: Also, see https://help.ubuntu.com/community/ReportingBugs on how to report bugs [08:02] should this bug #96083 be closed? it is from 7.04 [08:02] Launchpad bug 96083 in migration-assistant (Ubuntu) "Installer hangs at "Migrate" on eMachines w3080 w/XP on 2nd HD (heat: 12)" [Undecided,Incomplete] https://launchpad.net/bugs/96083 [08:06] should this bug #96083 be closed? it is from 7.04 [08:06] Launchpad bug 96083 in migration-assistant (Ubuntu) "Installer hangs at "Migrate" on eMachines w3080 w/XP on 2nd HD (heat: 12)" [Undecided,Incomplete] https://launchpad.net/bugs/96083 [08:10] ssj6akshat: no, in some cases it might happen that the same bug affects current versions also [08:10] don't just close blindly [08:10] get the reportd to confirm on latest release (maverick) [08:10] *reporter [08:11] if you can't confirm yourself [08:11] and only if you have reason to think it has been fixed [08:12] it really annoys reporters to have requests to reconfirm when we've done nothing to actually help with the bug. [08:12] *really annoys* [08:12] okay [08:24] please set this bug's status to Won't Fix bug #161101 [08:24] Launchpad bug 161101 in neutrino (Ubuntu) "The "Close" button in "About" window is not working (heat: 3)" [Undecided,New] https://launchpad.net/bugs/161101 [08:24] since the project is dead and is no longer maintained [08:30] okie [08:30] ssj6akshat: Cannot [08:31] why? [08:31] ssj6akshat: The project's no longer maintained, but still the package is maintained by Debian QA [08:31] and I can fix it [08:31] Won't fix -> Cannot be fixed [08:31] Which translates to: [08:32] 1) The fix is impossible by design [08:32] 2) The fix goes against a design decision [08:32] None of these block this bug [08:32] Infact [08:32] it should be confirmed if it can be reproduced [08:32] then fix it, I can't see an old bug standing [08:34] bilalakhtar: umm, neutrino got pulled from the archive in intrepid's cycle: https://launchpad.net/ubuntu/+source/neutrino/+publishinghistory [08:36] really? [08:36] Then why didn't this bug get deleted? [08:37] okay, marking Won't fix [08:37] ssj6akshat: ^^ [08:37] yay victory [08:51] shouldn't bug #199716 be marked Fix Commited if a proposed branch is merged? [08:51] Launchpad bug 199716 in ubuntu-meta (Ubuntu) (and 1 other project) "Implement XDG Base Directory Specification for all *buntu specific software (affects: 1) (heat: 3)" [Undecided,New] https://launchpad.net/bugs/199716 [08:53] anyone? [08:53] shouldn't bug #199716 be marked Fix Commited if a proposed branch is merged? [08:53] Launchpad bug 199716 in ubuntu-meta (Ubuntu) (and 1 other project) "Implement XDG Base Directory Specification for all *buntu specific software (affects: 1) (heat: 3)" [Undecided,New] https://launchpad.net/bugs/199716 [08:55] anyone? [09:00] ssj6akshat, fix released for update-manager. Fixed in update-manager (1:0.131) [09:02] !patience | ssj6akshat helps too.. [09:02] ssj6akshat helps too..: Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/ [09:02] err.. we need a better factoid here ;p [09:22] jibel, should i set it to Fix Released? [09:22] !thank vish [09:22] Factoid 'thank vish' not found [09:24] :s [09:35] ssj6akshat ¦ yea, no one thanks me! ;p [09:43] ssj6akshat, yes, set it to fix released [09:44] jibel, done [09:44] ssj6akshat, thank you [10:27] hi all, i have confirmed 656035 could someone set this to triaged? it seems like an upstream bug, is this correct? [10:39] gotta go [12:04] got disconnected, so don't know whether someone replied previously to my question, so repeating it... [12:04] can bug 644223 be marked as triaged? It is already confirmed by more than two users, has quite some info on the report as well as in its duplicates (don't know whether its enough) [12:04] Launchpad bug 644223 in pm-utils (Ubuntu) "Suspend problem with Maverick on ThinkPad W500 (affects: 19) (dups: 3) (heat: 82)" [Undecided,Confirmed] https://launchpad.net/bugs/644223 [12:36] wow! channel silent for last 45 mins (except my babble). is there a football match being played somewhere? :) [12:39] geekosopher, I was studying for exams [12:39] ssj6akshat: sorry to disturb buddy [13:03] can bug #224283 be marked as Won't Fix since xulrunner 1.9 is now unsupported by mozilla and is unsupported in Hardy too https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-June/000719.html [13:03] Launchpad bug 224283 in xulrunner-1.9 (Ubuntu) "fonts are insanely huge after upgrading to Hardy (heat: 3)" [Undecided,New] https://launchpad.net/bugs/224283 [13:03] and all the desktop releases before hardy are eol [13:04] ssj6akshat: Except Jaunty. [13:07] jpds, jaunty is after hardy [13:11] also isn't jaunty EOL today? [13:12] ssj6akshat, jaunty eol is tomorrow [13:15] ssj6akshat, the fact that xulrunner-1.9 is not supported by mozilla doesn't make the bug a "won't fix". Hardy is supported until april 2013 and 2015 for server. [13:15] 23rd. [13:15] ssj6akshat, and if some good soul wants to investigate and fix it, he's welcomed. [13:17] ssj6akshat, hardy is supported until 2011 and 2013 for server. [13:17] More timing stuff here: https://wiki.ubuntu.com/Releases [13:22] jibel, but you can't upgrade to hardy since older desktop releases are EOL [13:22] ssj6akshat:why not? [13:22] ssj6akshat, why not ? [13:23] hggdh, stop reading my mind [13:23] :-) [13:25] aah, you can still upgrade https://help.ubuntu.com/community/EOLUpgrades [13:34] :-) [13:56] hggdh, oh I forgot xulrunner 1.9 is not even supported by canonical they pushed 1.9.2.4 a long time ago === tux_race1 is now known as tux_racer [14:12] pedro_: massive requests to joing bugsquad? [14:12] :-) [14:14] hggdh, just cleaning up the queue :-P [14:17] ? was there a queue? [14:17] of proposed members, yes [14:25] I thought we would get the request on email. Hum. Are they sent round-robin (or something) to each of the admins? [14:32] Hi [14:34] hello guys can make the progress of release by changing the name of the source distribution in the repo list? [14:35] someone knows this practice? [14:36] :-& === lmontrie_ is now known as lmontrie === lennix_ is now known as lennix [15:40] hggdh, pedro_, I think I've made my 5-a-day https://wiki.ubuntu.com/UbuntuBugDay/20101021 [15:40] :-) [15:41] jibel, wow you mean like 500 a day ? :-P [15:41] jibel: you made a bit more than 5-a-day :-) [15:41] I can't stand regressions anymore for today [15:41] LOL [15:43] * jibel -> coffee break [16:01] hi [16:01] is gnome do is in active development/ [16:01] ? [16:01] i have a bug for it [16:01] don't wait, just file it [16:04] * micahg thought we gave up on asking if things are still an issue [16:05] We basically did, but LP development tends to lag behind bugsquad practice :) [16:09] does bug control have the ability to add tasks now? [16:09] can anyone set this bug #624622 's status as Won't Fix since Dock is split from Do [16:09] Launchpad bug 624622 in do "Have a blank screen i have to press to get docky working (affects: 1) (heat: 158)" [Undecided,In progress] https://launchpad.net/bugs/624622 [16:12] micahg, I don't think so: I think you need to be an uploader for something to do more than nominate. [16:13] hmm, how was jibel able to add tasks then [16:13] oh, he's a member of -drivers [16:14] through the QA team, makes sense :) [16:21] micahg, if you're referring to the 'is it still an issue' I asked, that's because I was cleaning regression-* bugs and I can't test in every release to know in which release the regression still lies and there's not always the relevant bits in the changelog. [16:21] It's much faster to ask then. [16:22] jibel: yes, but I'm not on Lucid, so I can't test anymore [16:23] jibel: also, that's what VMs are for [16:26] micahg, you not, but if we're talking about 511250, another commenter confirmed and a dev will look at it. [16:26] jibel: I'm one of the devs in this case :P [16:27] micahg, I know that :-) but chrisccoulson just assigned the bug to himself [16:27] We'd do better to never consider any group (triagers, reporters, developers, etc.) external to ourselves. We might not be very good at some task, but as soon as we assume it is now someone else's problem, we run into issues. [16:27] was referring to bug 548567 though [16:27] Launchpad bug 548567 in update-notifier (Ubuntu) "update notifier not appearing after upgrade to Lucid (affects: 3) (heat: 18)" [Undecided,Incomplete] https://launchpad.net/bugs/548567 [16:28] hi! [16:29] chrisccoulson, hi [16:30] micahg, do you know who works on light-themes? [16:30] micahg, same thing, the bug was tagged regression-potential in lucid beta, but I needed to check if that's still a regression in lucid final and maverick because one of the commenter says he's experiencing it after you said it's fixed. [16:30] bbordwell: I think vish was working on it a little [16:31] jibel: hmm, ok [16:31] vish, are you around? [16:32] micahg, I'm sorry, but I really can't check myself in a VM all the reports we had to clean. [16:32] micahg, I'll do a second pass in 1 month if there's no reply. [16:32] jibel: hmmm..ok [16:34] re. all of that -- we need to revisit the whole concept of triaging -- including required changes in default LP behaviour [16:35] hggdh: +1 :) (also see discussion on this in -devel :)) [16:35] +1 [16:36] micahg: yes, I sent an internal email about that thread. I think *all* of them are correct [16:36] hggdh, are you going to register a blueprint to discuss it while at UDS? [16:37] pedro_: I was thinking about it. The more I think, the more important I see it [16:37] would be great to have one [16:37] * hggdh goes to enter the BP [16:43] hggdh, well vish does not seem to be around, do you know how I could get this bug some attention with a dev? It seems that no one is looking at it: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/640096 [16:43] Launchpad bug 640096 in light-themes (Ubuntu) (and 1 other project) "cpufreq using grey almost invisible font (affects: 57) (dups: 9) (heat: 212)" [Medium,Triaged] [16:43] bbordwell: looking [16:43] hggdh, Please subscribe me to that one (as essential). [16:43] persia: ack [16:45] bbordwell: I think the best option is to raise it on the #ubuntu-desktop channel [16:45] alright thanks [16:49] https://lists.ubuntu.com/archives/ubuntu-devel/2010-October/031866.html [16:49] https://lists.ubuntu.com/archives/ubuntu-devel/2010-October/031866.html [16:49] dammit [16:50] https://blueprints.edge.launchpad.net/ubuntu/+spec/ubuntutheproject-qa-n-triage-revisited [16:50] there it is. persia, I added you in already [16:51] * charlie-tca subscribing too [16:58] bbordwell ¦ hey [16:58] vish, hey I heard that you had done some work with light-themes and I was wondering if you could take an interest in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/640096 [16:59] Launchpad bug 640096 in light-themes (Ubuntu) (and 1 other project) "cpufreq using grey almost invisible font (affects: 57) (dups: 9) (heat: 212)" [Medium,Triaged] [16:59] bbordwell ¦ replied on -desktop :) [17:03] Is the following a bug: Update Manager shows up, and tells me there are 31 packages to install. I click "check", and it processes a bit, and there are zero packages to install. To be fair, I happened to be fiddling with a package management tool when it launched, but ought it automagically go away? [17:05] persia: you mean should update-manager disappear if there are 0 pacakges? [17:05] persia: if you were updating the system on another thread, then yes it can happen, the update-manager tries to keep up-to-date [17:06] Right. I know precisely why this happens: I'm wondering if after update-manager opens in the background, it ought check to see if the state changed every hour or so, and if there aren't pending updates, silently close itself. [17:06] It's one of those fiddly usability things: is it worse to close it later or to have your computer lose performance while it reindexes? [17:07] If others also think it's a bug, I'll file it. Otherwise, I'll forget all about it. [17:08] I find it bothersome when using Ubuntu that it can open and minimize itself, but never close itself [17:09] Then I'll call it a bug :) [17:09] * persia files [17:10] I will even triage it [17:10] heh [17:10] * charlie-tca thought he did that one before, to be honest [17:11] charlie-tca, Would you mind checking? If so, I'll not complete filing it. [17:12] If I did, it would be closed already [17:12] but I am looking [17:14] Lying around as expired is fine, or wontfix, or whatever :) I know it's not Fix Released. [17:14] nope, it was different [17:15] OK. New bug then :) [17:20] hmm, whatever I screwed up trying to upgrade to natty will require a new install of maverick to try it again. [17:27] charlie-tca, bug #665191 [17:27] Launchpad bug 665191 in update-manager (Ubuntu) "Update Manager stays open when it doesn't need to do so (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/665191 [17:31] Thanks [17:35] triaged [17:35] Thanks. [17:35] Guess I better go fix the sprinkler system before it freezes now [17:58] nepomuku! causes users to commit sepuku [17:58] half year ago I wasted days on getting damn nepomuku/akonadi working to be able to use kmail. Now after upgrade to 10.10, AGAIN Im unable to use my kmail. jesus [17:59] how about providing users with options like: [x] I dont care about no damn semantic search bs, just let me use my applications normally and programs like kmail will "just work" [17:59] xelister: ranting here will not help any... [18:00] yeap, that's why Im proposing an option to opt out of this bloat and "semantic search" - what ever this function is (sounds like bs to me, but just imho), some users will prefer to just have applications working. Essentiall apps like say, email client?! [18:01] xelister: have you opened a bug on your problem? Also, this is open source. Propose a fix. [18:01] well, why are we at all using this nepomuku, it seems to only annoy users. Perhpas the bug proposition should be to remove that alltogeather from default installation at least [18:02] *of kde / kmail [18:02] IDK, I do not use kmail. But, without a bug, nothing will be done [18:02] there's no kubuntu channel? [18:02] many developers there, pedro_? [18:02] xelister, i'm wondering if there's a kubuntu channel because you might get better feedback there [18:03] well last time after long hours across few channels including nepomuk/akonadi developers, we where able to make kmail work on report a bug or two in the process. WHY I ahve to do this now AGAIN. [18:03] and here we do not fix bugs. This channel is not about fixing bugs [18:03] then which? -motu ? [18:04] this is a KDE-specific issue, affecting core KDE applications. -motu is not the right place [18:05] https://wiki.kubuntu.org/Kubuntu/ContactUs <- xelister [18:06] hggdh: yeah why report a bug, it's the same thing as half year ago [18:07] xelister: OK. Then please do not rant here. [19:22] how do you open a report against a specific version of ubuntu, say it should be fix released in the package, but it is not fixed in lucid. (for example: https://bugs.launchpad.net/ubuntu/lucid/+source/poppler/+bug/547225) [19:22] Launchpad bug 547225 in poppler (Ubuntu Lucid) (and 2 other projects) "Evince fails to properly display this "type" of pdf (affects: 2) (heat: 16)" [Low,Triaged] [19:23] bbordwell, "Nominate for Release" (which has been done for that bug) [19:24] persia, ahh does the upstream patch need to be found first? [19:24] bbordwell, Are you asking how to achieve an effect like the one for that bug, or what to do for that specific bug? [19:25] like that bug [19:25] this is the bug I am looking at [19:25] https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/665226 [19:25] Launchpad bug 665226 in poppler (Ubuntu) "evince shows blank page where acroread does not (affects: 1) (heat: 6)" [Low,New] [19:25] fixed in upstream poppler and maverick [19:25] Use "Nominate for Release". This should only be done if you beleive the SRU criteria are met [19:25] !sru [19:25] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [19:27] ya that page says that the upstream patch needs to be found [19:27] so i will not nominate it [19:27] bbordwell, and i will reject it [19:27] Well, we need a fix. [19:27] bbordwell, please do not nominate every single bug [19:27] another way of Ubuntu blocking typical office use: opening PDFs in GIMP. https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/574342 ; Anything else to be done to have this fixed soon? [19:27] Launchpad bug 574342 in gimp (Ubuntu) "GIMP set as default pdf viewer (affects: 4) (heat: 22)" [Medium,Confirmed] [19:28] pedro_, you misread me I said I would not nominate it [19:28] bbordwell, oops i think i did [19:28] bbordwell, btw don't re open the bugs just because [19:28] please add a comment on it [19:28] xelister, What that seems to mostly need is someone determining *why* that happens, and fixing it. [19:29] persia: how to display/edit information about programs association with file types? [19:29] Heh. There's N ways. [19:29] pedro_, okay, but why the comment I did not reopen any bug [19:29] And all of them are broken in various ways. [19:29] persia: :/ [19:29] bbordwell, I've marked the bug as incomplete per my previous comment there, and you set it as new [19:30] I love it like KDE, since like 4 years, takes 10 seconds to simply save the changed file association [19:30] the big ones are probably xdg-mime, Debian's MIME system, and python's broken fake-MIME-by-guessing-at-extensions-whilst-ignoring-filetype [19:30] bbordwell, probably lp collision or something? === bilalakhtar_ is now known as bilalakhtar [19:30] pedro_, haha ya I wondered what was going on [19:30] bbordwell, let's blame lp ;-) [19:30] persia: one advantage of using extension only is performance of disc I/O [19:31] pedro_, btw I have confirmed that bug does work on maverick, and that it does not on lucid [19:31] bbordwell, awesome, thanks [19:31] xelister, Sure, but it's wrong. The magic number is much more likely to be accurate (and can distinguish all sorts of useful things, like the language of a text document, various markups, etc.) [19:33] pedro_, also I will just let you take over that bug so we do not have any more lp collisions haha [19:34] bbordwell, no worries, either of us can look, let's just make sure to reload the page ;-) [19:35] would be nice to have a collision warning on lp, just like bugzilla does [19:35] pedro_, Is there already an open bug about that? [19:37] mm i think there's one [19:37] * pedro_ search [19:38] persia, bbordwell bug 28459 [19:38] Launchpad bug 28459 in malone "Handle mid-air collisions in bug reports (affects: 2) (dups: 6) (heat: 37)" [Medium,Triaged] https://launchpad.net/bugs/28459 [19:38] must be hard to implement since it was filed on 2006 [19:39] I am a little hesitant about changing the importance set by someone else but would you guys agree that this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/654361 should be marked as much higher than low? [19:39] Launchpad bug 654361 in mesa (Ubuntu) "GLX 1.3 programs (like clutter) fail with software rasteriser (affects: 5) (dups: 1) (heat: 32)" [Low,Confirmed] [19:40] that causes quadrapassel, a game included by default, to fail to launch on any system without 3d accel (mostly nouveau) [19:45] pedro_, Or just not have convincing enough stories :) [19:46] bbordwell, It's still "low", because it's a fault that we presume a minority of people (including myself) experience. === lennix is now known as vlatom === yofel_ is now known as yofel === BUGabundo is now known as BUGabundo_dinner === BUGabundo_dinner is now known as BUGabundo [22:51] Hi for everyone [22:54] I am examining this report: # 665369 I think we can classify as incomplete what do you think? [22:58] bug #665369 [22:58] Launchpad bug 665369 in slime "#+nil ,@(foo) not fontified correctly (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/665369 [22:58] I don't think that's incomplete at all. [22:59] Plus, it's not an Ubuntu bug: it's a Slime bug, so it's best to talk to the Slime folk. [22:59] One key bit of information is that the bug reporter *is* a slime developer, so I presume it's a useful and accurate bug for the slime developers, even if it looks like nonsense to people unfamiliar with slime. [23:00] * persia puts it back to New, figuring the slime devs probably know which bugs they care about [23:06] persia: ok thanks! I think I could assign it to the team slime? [23:10] layn, We don't assign bugs to other folk. We only assign them to ourselves if we're going to work on them. [23:10] Bugs that aren't assigned are best left alone (unless you want to work on it), so that someone else has a chance. Maybe a long-time developer. Maybe someone new just getting interested. [23:10] oops ok [23:17] layn: we only deal with bugs in Ubuntu. Any other bug is out-of-bounds [23:18] could you unlink 665343 as duplicate of 664753 for me by chance? [23:19] sorry [23:21] bugs 665343 664753 [23:21] Launchpad bug 665343 in gnome-utils (Ubuntu) "dictionary default server does not give definitions/@ in english form. (dup-of: 664753)" [Undecided,Confirmed] https://launchpad.net/bugs/665343 [23:21] Launchpad bug 664753 in gnome-utils (Ubuntu) "can no longer lookup words via dictionary.org (affects: 4) (dups: 1) (heat: 20)" [Undecided,Incomplete] https://launchpad.net/bugs/664753 [23:23] thank you [23:23] hggdh: ok sorry [23:24] slink3r: done. Now how did you confirm 665343? [23:24] no, I was rushing [23:25] It's never worth rushing. [23:25] hggdh: I asked the team to deal with the slime bug [23:25] yeah, I won't again [23:25] There's simply no benefit? [23:25] layn, Which team? [23:27] persia: in fact, Tobias C. I checked Rittweiler intervened and belongs to the slime team and I asked him to take matters [23:27] layn, Better just to leave that kind of bug alone. [23:27] layn: again: we do *not* touch bugs that are not from Ubuntu. Not at all. NEVER. [23:27] (unless we happen to be part of the upstream team while wearing another hat) [23:28] * hggdh idly wonders if it is time to have a look at Opinion bugs... [23:29] hggdh: hey guys sorry but I reported the bug should I do now as I was trying to resolve [23:30] layn: which bug? [23:31] hggdh: Bug #665369 I can change the status? or you can do for me? [23:31] Launchpad bug 665369 in slime "#+nil ,@(foo) not fontified correctly (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/665369 [23:32] layn: the bug is already back in New, persia changed it. [23:32] layn: this bug is NOT Ubuntu, please do not work on it [23:34] hggdh: scuse me, In fact it was my mistake not to touch it raise my hands to say that absolutely put more attention [23:35] hggdh: I offer my apologies to slime team if necessary [23:36] layn: the only action you got was a request from the developer NOT to touch it anymore [23:37] hggdh: this slime? ok [23:38] yes [23:38] hggdh: do not touch [23:38] correct, thank you [23:38] hggdh: I pretend not to have all vito I would not make mistakes [23:39] hggdh: I pretend not to have seen all I would not make mistakes [23:45] hggdh: cosa ne pensi di questo? #665390 believe we can confirm or incomplete? [23:45] bug 665390 [23:45] hggdh: Bug 665390 on http://launchpad.net/bugs/665390 is private [23:46] Not all programs are guaranteed to use 24-hour time it says in help.ubuntu.com, so if someone reports a program which doesn't as a bug, should I just link that page? [23:47] or forward it upstream as a request? [23:47] bug 664965 [23:48] Launchpad bug 664965 in tomboy (Ubuntu) "Tomboy shows AM/PM instead of using the locales settings (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/664965 [23:48] For I do not think this is a bug [23:48] alright, I'll state that [23:48] thanks [23:49] layn: it might be a dup of bug 664014. BUT THEY ARE NOT UBUNTU! [23:49] Launchpad bug 664014 in indicator-applet "Clicking a dropdown menu when another window opens. Computer freezes. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/664014 [23:50] layn, How are you discovering bugs to triage? [23:51] hggdh: sorry but where can I get exclusive ubuntu bug can give me the link to alerts [23:51] slink3r: I would say it is a bug (not respecting locales, which means internationalisation is weak/missing/wrong) [23:52] slink3r: it will probably end as a wishlist, with an upstream bug linked in [23:52] persia: I'm looking at the new bugs reported [23:52] layn, Where? [23:53] persia:launchpad.net Bug tracking [23:53] URL? [23:53] layn: you can use this: http://tinyurl.com/37nuplc [23:53] layn: it will give you New/Incomplete bugs in Ubuntu [23:54] hggdh: friendly ok I'll go there then others will not touch them [23:56] layn: thank you [23:56] hggdh: I am that I have to thank you for being nice [23:57] layn: you are welcome [23:57] layn, If you run out, for any reason, feel free to ask here for guides. [23:57] There's lots of good ways to get lists of useful Ubuntu bugs, or fresh Ubuntu bugs, etc. [23:59] hggdh: thanks [23:59] persia: Thanks in fact I doubted that I now have been resolved