[00:22] <mbrigdan> Anybody?
[02:22] <charlie-tca> !away | otubo[AFK]
[02:22] <ubot4> otubo[AFK]: Please do not use noisy away messages and nicks in Ubuntu channels. It is annoying and unnecessary. Use the command "/away <reason>" to set your client away silently. See also «/msg ubottu Guidelines»
[11:26] <decoder> there's still a memory leak in nm-applet :( just killed it again with 140 MB of memory used
[11:26] <decoder> takes very long though to accumulate
[11:36] <AlanBell> bug 739812 is listed as affecting unity (ubuntu natty) how do I add oneiric to it?
[11:36] <ubot4> Launchpad bug 739812 in unity (Ubuntu Natty) (and 2 other projects) "Must use hardware keyboard to perform search for applications in Unity (affects: 8) (heat: 56)" [Medium,Confirmed] https://launchpad.net/bugs/739812
[11:48] <penguin42> don't know - it's not obvious is it
[11:53] <AlanBell> yeah, not sure if it is because I lack rights to target a release or if I just don't know what I am doing
[12:04] <jibel> AlanBell, this action requires specific rights. I nominated it for O.
[12:05] <jibel> AlanBell, importance is medium but I think it should be High
[12:06] <jibel> AlanBell, what's you take on that ?
[12:07] <AlanBell> I think it should be high
[12:10] <AlanBell> it is "A bug which impacts accessibility of a core application" and probably meets some of the other criteria for high https://wiki.ubuntu.com/Bugs/Importance
[12:11] <AlanBell> it is a bit of a blocker for a good touchscreen tablet experience with 3d unity
[14:32] <ashams> Hello Guys, I need your opinion here: https://answers.launchpad.net/launchpad/+question/169157
[15:02] <hggdh> ashams: can you please expand on what it is intended to? I am not sure, reading the question
[15:03] <ashams> hggdh: Hi, thanks for reading :)
[15:03] <ashams> hggdh: the story that I've noticed that we're not doing enough work on forwarding bugs upstream
[15:04] <ashams> hggdh: so I decided to research on how to enhance our procedures to do so.
[15:05] <ashams> hggdh: one of these problems was, that upstream related tags are quite a lot.
[15:05] <ashams> hggdh: and it can't be easily used to find this type of bugs
[15:06] <ashams> hggdh: so I was thinking of creating one *generic* tag that can be easily searched for, and then a bug triager can forward, or do whatever to a bug.
[15:07] <ashams> hggdh: of course beside other tags, to describe special cases.
[15:07] <ashams> hggdh: So?
[15:14] <hggdh> I do understand you. But there are other rules for the game that also imply upstreaming
[15:15] <hggdh> I am not saying your idea is good, or bad, or whatever. I am just being the usual devil's advocate
[15:15] <hggdh> the point is not all bugs are upstreamble. Some are related to UBuntu packaging, or to a local patch (that upstream refuses)
[15:17] <hggdh> so no matter what, you need to work on a specific bug and determine if it is a local issue (i.e., Ubuntu-related) or not; then if it is a real issue, or -- say -- lack of reading the manual (or even lack of _a_ manual)
[15:18] <hggdh> _if_ you decide it is upstreamable, you can either upstream it yourself immediately or, for example, open a placeholder upstream task (and mark the bug comfirmed, _not_ triaged)
[15:19] <hggdh> so, what does a tag bring that would make it more efficient?
[15:19] <hggdh> ashams: ^
[15:22] <ashams> hggdh: it can be efficient if someone decided to work on this criteria(Forwarding Bugs) just to speed up development of many packages...
[15:24] <hggdh> ashams: one usually selects a specific source package to work on; then all bugs that are not triaged are fair game (since all are potential real bugs, and potentially in need of upstreaming)
[15:28] <hggdh> ashams: the point is, for one to add such a tag to a bug, one first of all needs to *know* it has to be upstreamed. So, adding a placeholder upstream task (or actually upstreaming it then) is more effective than adding a new tag
[15:33] <ashams> hggdh: I was thinking of that process as not all bug triagers have time(or like) to forward bugs, so it was just to give someone else a way to focus on this.
[15:33] <ashams> I was thinking of splitting the long process into pieces, triagging, forwarding, instead of leaving it as a big one, thus it may look like a big task to bug triagers.
[15:34] <bdmurray> pedro_: as you write these patterns are you unsubb'ing ubuntu-bug-control from the bugs?
[15:34] <ashams> hggdh: no matter if I'm currently adopted some pkg
[15:36] <pedro_> bdmurray, oh no, i was just removing the tag, will unsubscribe the bugcontrol team as well
[15:36] <bdmurray> pedro_: great, I'll look and see if there is a tool for that
[15:36] <pedro_> bdmurray, thanks for the heads up
[15:46] <charlie-tca> Looking for someone that will confirm bug 833862
[15:46] <ubot4> Launchpad bug 833862 in onboard (Ubuntu) "Onboard Keyboard should have a menu entry for Xubuntu/Xfce (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/833862
[15:46] <hggdh> pedro_: shouldn't bug 832533 be milestoned?
[15:46] <ubot4> Launchpad bug 832533 in gvfs (Ubuntu Oneiric) (and 2 other projects) "gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance() (affects: 151) (dups: 29) (heat: 490)" [High,Triaged] https://launchpad.net/bugs/832533
[15:47] <hggdh> and my compiz died a horrible death. Again.
[15:47] <charlie-tca> looks to me like it should be milestoned, yes.
[15:59] <hggdh> ashams: sorry, my system barfed... so reboot, submit a new bug, etc, etc
[16:00] <ashams> hggdh: np, hope it works fine now :)
[16:02] <hggdh> no, not yet...
[16:03] <pedro_> agg this alt+tab of unity is driving me crazy :-/
[16:03] <pedro_> hggdh, i've milestoned it , thanks ;-)
[16:15] <ashams> hggdh: reported it, if so would you give a link to that bug, I'm curious :)
[16:16] <hggdh> ashams: bug 833879, but we have to wait for the backtracer to work
[16:16] <ubot4> hggdh: Bug 833879 on http://launchpad.net/bugs/833879 is private
[18:40] <mbrigdan> Hey! I'm going to report a bug about ubuntu ignoring module blacklists, but I'm not sure which package to file it against. update-initramfs ignores the blacklist, so I could file it against that, but other blacklisted modules that update-initramfs isn't adding are also getting loaded, implying that the problem is elsewhere. Any advice?
[18:57] <hggdh> mbrigdan: probably against module-init-tools
[18:58] <mbrigdan> hggdh, Its not just in the initramfs though. Modules that aren't loaded into it are still somehow being loaded, even though they're blacklisted.
[19:02] <hggdh> mbrigdan: I am not sure I follow you. I suggested module-init-tools because this is the package that deals with blacklisting
[19:03] <hggdh> I did not say anything about initramfs...
[19:03] <mbrigdan> Oh, it does all the blacklisting, not just for update-initramfs?
[19:03] <mbrigdan> The init part just confused me
[19:04] <mbrigdan> I'll go with that then
[19:04] <hggdh> this is the owner of the directories and the modules maintenance
[19:04] <mbrigdan> alright, thanks
[19:04] <hggdh> you are welcome
[22:27] <penguin42> yofel: Can you have a look at bug 833737 - I think you said that you had problems with nautilus starting in KDE
[22:27] <ubot4> Launchpad bug 833737 in kde-workspace (Ubuntu) "No way to remove entries from ksmserverrc (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/833737
[22:28] <yofel> k, busy filing a FFe for digikam, I'll have a look later
[22:29] <penguin42> yofel: Ok, out of interest what's the digikam issue
[22:30] <yofel> well, trying to get digikam 2.0.0 into the archive which would make the geolocation support work again, which needs a FeatureFreezeException
[22:31] <penguin42> but we would be going from a beta/pre-release to the final thing which sounds like a good idea anyway
[22:32] <bdmurray> I'll plus one that FFE ;-)
[22:32] <yofel> ^^
[22:33]  * penguin42 gently wonders if that would also cure the black on dark grey text....
[22:35] <penguin42> for some reason this 1.9.x doesn't feel intuitive for me - I can't quite pin it down though