=== bcurtiswx_ is now known as bcurtiswx [00:59] * BUGabundo $ do_funny_stuff(sleep) ; $ echoes REM === scream is now known as NonvocalScream === NonvocalScream is now known as scream [01:37] Bug 408095 should be tagged as wishlist, please [01:37] Launchpad bug 408095 in gnome-settings-daemon ""Disable touchpad while typing" should ignore modifier keys when monitoring keyboard activity" [Undecided,New] https://launchpad.net/bugs/408095 [01:40] Scienceman123, can you please explain why (I see no other comments in the bug)? [01:40] * hggdh is not against, just would like some reasoning [01:40] I'm very for [01:40] hggdh: 'ctrl-click' [01:41] or do mean, reason for wishlist? [01:41] lifeless, yes. I would rather not move to wish without a comment [01:41] every change in status should have a comment explaining why [01:42] It is not a regression [01:42] Scienceman123: you sure about that? [01:42] And it does not fail to do something it should [01:42] It's a "It would sure be nice if" kind of thing [01:43] it seems [01:43] its also got a solution in it. [01:43] I suggest turning it into a patch and moving on. [01:43] Ok then [01:43] Sorry, I'm new [01:43] Scienceman123, I am not arguing it. It is just that blind change in status should not happen. You have a good reason, so you should comment in explaining it. And I will be extremely happy to change it. [01:43] Scienceman123, no problems, and we are glad you are helping [01:44] indeed [01:44] lifeless, +1 [01:53] arghh. Hotel connections really suck :-( [01:56] ah well. Scienceman123 has left the building. I will add the patch === jdstrand is now known as jdstrand__ === jdstrand_ is now known as jdstrand [07:36] good morning! === andre___ is now known as andre__ [14:52] Boo === ryanakca_ is now known as ryanakca === micahg1 is now known as micahg [16:57] Can somebody please tag bug 253465 with verification-done? I cant figure it out [16:57] Launchpad bug 253465 in daemontools "[SRU] daemontools-run needs to work with upstart" [Medium,Confirmed] https://launchpad.net/bugs/253465 [17:00] You can click Update Description/Tags and add i, Lademord [17:14] hello all, well i am kinda new to this and would like to know a good starting point for a noobm and please don't refer me to the wiki [17:16] yvan300, heh. Allright, I will not refer you to the wiki. But I *do* ask: have you read it? [17:16] hggdh: more or less, but what i really want to know is what do you recommend that i start to do first [17:17] yvan300, OK. more or less sounds good ;-) [17:17] hggdh: so what should i do then? [17:17] yvan300, I understand you want to triage bugs, right? [17:18] (after all, this is what we do in this channel) [17:18] hggdh: that's the point , i don't know wht to do, i just want to help and thus i need guidance [17:18] yvan300, we will guide you, no problems [17:19] hggdh: ok so what to do first then? [17:19] yvan300, go to https://bugs.edge.launchpad.net/ubuntu/ , and select -- say -- "newest first", anc lcik on the search buttom [17:20] what now hggdh [17:21] then look at the bugs that will be shown. Select one you feel comfortable (or *less* uncomfortable), and try to see if it explains the issue, has the data needed, etc [17:21] You *may* not feel comfortable with any of them; in this case, just get the next page, and try again [17:22] when you find one you want to work on, start, and ask here in case of doubts [17:22] hggdh: do i need to know any programming to solve these, i am currently learning python [17:23] yvan300, no, not necessarily. But you really should look at some of the wiki pages (https://wiki.ubuntu.com/BugSquad/KnowledgeBase comes to mind) [17:23] you can, if you want, fix on the python packages. It is up to you, and we will still be glad you are helping [17:24] hggdh: ok thanks for your help :D [17:24] triage is the first step: we must understand what the issue is (if indeed is an issue), *then* we can try to solve it [17:24] yvan300, you are welcome. Again, please do not hesitate to ask for help [17:25] hggdh: i will keep that in mind [17:25] thank you. And thank you for helping [17:28] hggdh: can you run me through how you would tipically fix a bug [17:30] hggdh: sorry found a tut in the wiki [17:40] yvan300, we will be here, anyway ;-) [17:41] but, please keep in mind that *before* one can fix a problem, the problem must be understood... and this is where triaging pops up === ejat is now known as e-jat [17:55] someone feel like taking a look at this bug? I'm not sure if it's an issue with some post-removal scripts in tomboy/fspot, or if it's with dpkg, or both [17:55] https://bugs.launchpad.net/ubuntu/+bug/403726 [17:55] Launchpad bug 403726 in f-spot "package f-spot 0.5.0.3-1ubuntu6 failed to install/upgrade: subprocess post-removal script returned error exit status 139" [Undecided,New] [17:58] plars, difficult to say, all I can see is that something got a segfault === yofel_ is now known as yofel [20:21] hey