[05:01] hi === BUGabundo is now known as BUGa_away === yofel_ is now known as yofel [15:21] hey AbhiJit [15:21] hello Gigacore [15:21] after so many days? [15:21] Dr_Who: great name [15:22] yea quite busy with studies [15:22] thanks ... a nick I've had for quite a long time [15:22] nice... love the series. [15:22] though I have to wait for the DVD now [15:23] guys can't I set importance to a bug? [15:23] Gigacore: only bug control members can set importance. [15:24] charlie-tca: ok [15:24] If you are not bug-control, you can ask here giving "bug # " and importance wanted [15:24] charlie-tca: thank you, will do [15:25] charlie-tca: I still have not gotten the icon done -- I am very sorry [15:25] no problem [15:25] anyway bug #461096 needs a fix [15:25] Launchpad bug 461096 in modemmanager (Ubuntu) (and 1 other project) "ZTE AC8700 modem doesn't work (affects: 8) (heat: 23)" [Undecided,Confirmed] https://launchpad.net/bugs/461096 [15:25] cprofitt: I just keep going anywayu [15:25] even am facing the same issue from ubuntu 9.10 [15:25] Gigacore: fix? [15:25] all the bugs need a fix [15:25] lol yes [15:59] Just looked at bug 461096 it digressed across multiple devices (potential developer nightmare). May want to refocus the upstream bug, asked and yet to be created, to focus on only ZTE AC8700 as well as ask other contributors to bug their EQ as new bug?! [15:59] Launchpad bug 461096 in modemmanager (Ubuntu) (and 1 other project) "ZTE AC8700 modem doesn't work (affects: 8) (heat: 23)" [Undecided,Confirmed] https://launchpad.net/bugs/461096 === jdstrand_ is now known as jdstrand [16:10] rusivi: if others are adding different equipment than the ZTE AC8700, they should be asked to file a new bug with logs [16:17] charlie-tca: Agreed. === AbhiJit_ is now known as AbhiJit === deryck is now known as deryck[lunch] === deryck[lunch] is now known as deryck [18:00] Hello to all fellows, there's a polish for this bug 672487 [18:00] Launchpad bug 672487 in ubuntu (and 1 other project) "Błędy pakietu kde-I 10n-pl przy próbie instalacji. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/672487 [18:10] njin: thanks, I'll take care of it [18:11] kklimonda_: :-) === zyga is now known as zyga-afk [19:09] pedro_: I've requested an apport-collect bugnumber, but nothing appear in the report bug 671548 [19:09] Launchpad bug 671548 in ubuntu (and 1 other project) "Touchpad not working Ubuntu 10.10 (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/671548 [19:10] njin: because it does not have a package assigned [19:11] njin: apport-collect can't operate without a package [19:11] charlie-tca, yofel: Thanks [19:12] either A) assign the bug to a package or B) use -p/--package with apport collect [19:12] ok === lifeless_ is now known as lifeless === kklimonda_ is now known as kklimonda [19:48] Bug #571707 has a fair bit of new comments, I'm not seeing the same bug pop up again on my machine which was at the time of reporting, so I'm guessing it _may_ be unrelated issues which should be directed to new bug reports, I'm not at all sure though... [19:48] Launchpad bug 571707 in plymouth (Ubuntu Lucid) (and 4 other projects) "fsck progress stalls at boot, plymouthd/mountall eats CPU (affects: 143) (dups: 16) (heat: 718)" [Undecided,Triaged] https://launchpad.net/bugs/571707 [19:52] arand: if your issue is different then the part under "Original Report", it would be best to file a new bug and let it be marked a duplicate. [19:55] charlie-tca: Well, I was talking about the new commenters' issues seeming different from that of the original (which I also saw, back then), and whether or not one should put a nicely put "shoo, file new bugs" comment there... [19:59] one can add a comment "Please file a new bug for your issue, using "ubuntu-bug plymouth" in a terminal." [19:59] and appropriate thanks [19:59] I usually just put in that their issue appears different, and would be best as a new bug [20:00] Yea, ok, I was thinking that might be the correct procedure, just wanted a second voice on it. [20:12] hi, I'm interested in helping with triage, and looking for a mentor if I'd be useful for the team. [20:15] hello, the layout has yo be showed? bug 671812 [20:15] Launchpad bug 671812 in ubuntu "Keyboard layout indicator doesn't show layout (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/671812 [20:16] *to [20:16] should probably tell the different layouts installed if there are more than one to use [20:17] If I add korean keyboard layout, I should be able to pick either english or korean from the indicator [20:18] charlie: ok, is a bug then ? === zyga-afk is now known as khr [20:19] yes, if it doesn't show any choices and more than one is installed [20:19] charlie: sorry, but i never changed my layout [20:20] erm, isn't the reporter saying that the indicator doesn't *indicate* anything? meaning, the icon doesn't show what layout is currently used [20:20] I don't use gnome so I'm not sure what it looks like actually === khr is now known as zyga [20:20] Could be you are right. I thought they want it to give the choices [20:21] (Xubuntu gives those keyboards in the indicator, and you can change keyboards by clicking on one.) [20:21] I think it did show the layout in the past with the notification area, can't remember how that looked like though (kde 4.5 shows the laguage code us/de/...) [20:23] hm, looks like they want it to do more than just show a keyboard in the indicator. [20:23] they gave us a screenshot. Seems like a keyboard with nothing is simply saying "yes, you installed a keyboard" [20:23] I cannot remember from feisty notification of layout in gnome, i've ever installed english and italian [20:24] right, and if you have more than one layout configured you usually want to know which one is currently enabled.. [20:24] but yes, in kde is showed [20:27] in gnome [20:27] stop, it is showed [20:28] I've just try to add another layout and now in notify appear a keyboard icon with ITA [20:31] in 10.10? [20:32] It might be a unity bug. Need more information from the reporter [20:37] charlie-tca: thanks i ask to th reporter more infos [21:11] Can someone take a lok bug 672749 thanks [21:11] Launchpad bug 672749 in ubuntu "Root file descriptor limits being applied to non-root processes with higher limits (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/672749 [21:14] njin, sounds valid to me at first pass. Let me dig in a bit and see if there's anything there [21:14] ok [21:15] Holy jesus -- they're setting it to 10240 fds [21:16] njin, I think this is related to something that was on Ubuntu devel about a month or two back [21:16] paultag: can you triage this bug, i canot understand [21:16] persia, ping -- do you recall anything about the state of the max fds on Ubuntu that was on -devel? njin's got a bug report about a program hitting it's cap [21:17] njin, Yes, let me first understand whats going on before bdmurra[y] kills me, I'm just off the phone and not thinking things over :) [21:17] :) [21:17] njin, :) thanks, rock on! [21:24] Buggers, I have to run -- can someone else take over sorting Bug #672749 ?, I don't think Zimbra is in the repos, and I'm not sure if they're also trying to file a bug against the ulimits stuff [21:24] Launchpad bug 672749 in ubuntu "Root file descriptor limits being applied to non-root processes with higher limits (affects: 1) (heat: 6)" [Medium,Triaged] https://launchpad.net/bugs/672749 [21:24] Much love === zyga is now known as zyga-afk [22:57] Hi! I'm looking at a bug report (http://bit.ly/bgt3e2) that i can't reproduce, should I ask the reporter to say if the bug is still happening on his system or what should I ask him? [22:58] bug number? [23:00] bug 670237 [23:00] Launchpad bug 670237 in gedit (Ubuntu) "gedit does not stay on top (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/670237 [23:00] not a gedit issue at least but whatever handles the windows [23:01] * micahg shudders WRT nvidia in anything after Karmic [23:01] micahg: what happended o.O? [23:01] yofel: no KMS [23:01] * charlie-tca will have to purchase an ATI card [23:01] aah heh [23:02] well, I always set the framebuffer res by hand so nothing's changed from my point... [23:02] and nouveau *is* getting better, slowly... [23:03] * micahg just saw a note that it's 3 yrs off [23:04] CaioAlonso: I would leave it alone. You can not ask the reporter if he still has it, since the bug was just filed 5 days ago. [23:05] As an alternative, you could ask them to try and reproduce it with a new user [23:05] yes, thats what I thought, its not a gedit bug, I can't reproduce it and its too recent to have been fixed in some other package [23:05] I could not reproduce here in natty, it may be something in the user directory causing the issue [23:06] I'll ask him to reproduce with a new user, thanks! [23:07] Thank you for helping [23:44] paultag, Not specifically, Based on the thread (last active 3 days ago), I suspect it to still be an active conversation. [23:45] Reviewing the thread in question, I have the impression that the simple fix is considered dangerous. === CaioAlonso_ is now known as CaioAlonso [23:52] persia, I'd agree [23:52] persia, just wanted to make sure I had the whole picture. We don't even package that software in Ubuntu IIRC ( have not had a chance to look it up ) [23:53] BBL, work [23:53] thanks persia