[00:02] or on a current version, correct [00:14] hi... i tried to reproduce a bug i reported this last june... but i'm unsure about one thing [00:14] whoever is using a laptop: does you screen dims when inactive? (before going totally black/starting the screensaver i mean) [00:15] Tiibiidii: not mine (Lucid) [00:15] ok... [00:15] hggdh, do you remember if back in karmic it was still working? [00:16] Tiibiidii: I *think* it was [00:16] but not sure [00:16] Thanks hggdh. [00:16] due to an annoying bug i disabled the dimming... but to reproduce this very bug i need it enable... but it seems that now it isn't possibile at all [00:16] ok [00:17] Tiibiidii: I still see the option to dim on 10.4 [00:17] and by enabling it... does it work? (i know... it's rather boring to stand still waiting for the screen to dim) [00:17] (thank you however) [00:17] Tiibiidii: will try [00:18] I am working on cleaning up bug 525534. The reporter points to a blog post that states that someone is working on a issue with x.org upstream. Would that be considered already reported(even though I have not found a duplicate bug report yet) or should I clean up the bug. [00:18] thanks again... and don't bother to reply if you're trying right now :) [00:18] Launchpad bug 525534 in xorg (Ubuntu) "[karmic] gnome-power-manager warns about a bug in xserver (blanking problem) (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525534 [00:19] Tiibiidii yes, it dims [00:20] Thanks for your help on helping me get used to this. [00:20] ok... hggdh, so this is yet another bug with my system? should i report it? ...i fear it may be some sort of misconfiguration on my end (even though i don't really know how it could've went wrong) [00:21] Anzenketh: I think this has been reported already (but I do not remember the bug #) [00:21] Tiibiidii: what do you mean, another bug? [00:21] OK I will see if I can find it. [00:21] what is your Ubuntu version? [00:21] my laptop doesn't dim [00:21] karmic [00:22] i tried tweaking around inside gconf-settings to make it work... but afaik it could've made it worse [00:22] Tiibiidii: OK. Keep in mind I am running Lucid. [00:22] yes, you could ;-) [00:23] I am working on cleaning up bug 525534. The reporter points to a blog post that states that someone is working on a issue with x.org upstream. Would that be considered already reported(even though I have not found a duplicate bug report yet) or should I clean up the bug. <-- this bug has a shitload of duplicates... due to the fact it's very visible... i'm also affected by it... here's one of the num [00:23] erous duplicates: I am working on cleaning up bug 525534. The reporter points to a blog post that states that someone is working on a issue with x.org upstream. Would that be considered already reported(even though I have not found a duplicate bug report yet) or should I clean up the bug. [00:23] Launchpad bug 525534 in xorg (Ubuntu) "[karmic] gnome-power-manager warns about a bug in xserver (blanking problem) (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525534 [00:23] ops [00:24] one of the numerous duplicates: 423694 [00:24] #423694 [00:24] keep in mind hovewer that, from what i've read: [00:24] Thanks you found it faster then me [00:25] some patches have already been applied and shipped... but the blanking problem is still present [00:25] and so one old bug solved by those patches (and that prompt the same annoying notification) may be a different one to one still unsolved [00:26] and that the bug of the alarming notification itself could be considered a different bug from the one's that causing it [00:27] Thanks you found it faster then me <-- i actually had it in my browser's history from 2 hours ago :P [00:43] Still getting used to triage Bug 525545 and 449335 look like they are duplicates although they do not describe the exact same thing. I don't want to do something wrong I should mark as duplicate due to they are somewhat simular. [00:43] Launchpad bug 525545 in seahorse (Ubuntu) "Problem after changing session password (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525545 [00:43] Launchpad bug 449335 in seahorse (Ubuntu) "always ask password on startup (affects: 2)" [Low,Incomplete] https://launchpad.net/bugs/449335 [00:44] Just trying to get a idea of how close something has to be to mark as duplicate. [00:48] hi Anzenketh, usually we don't assign ourselves to bugs that we are triaging unless we're going to make a patch or actively work on a fix === kermiac_ is now known as kermiac [00:48] Ok [00:49] just letting you know :) [00:49] Thanks I am new just came in today. How close does something have to be to another bug to be a duplicate [00:50] np Anzenketh :) [00:50] it has to be pretty much identical. [00:51] if you look at bug 525545, you will notice the OP is using karmic & is asked for their password twice after changing their p/w [00:51] Launchpad bug 525545 in seahorse (Ubuntu) "Problem after changing session password (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525545 [00:52] whereas in bug 449335 the OP is using karmic & hasn't mentioned anything about changing their p/w or being asked for their p/w twice [00:52] Launchpad bug 449335 in seahorse (Ubuntu) "always ask password on startup (affects: 2)" [Low,Incomplete] https://launchpad.net/bugs/449335 [00:53] if you've got any other questions, feel free to ask as their are usually a few people around in here that will be more than willing to help :) [00:54] Ya I was thinking they are similar but not close enough to be the same. [00:55] it's ok, once you've done a few you'll get the hang of it - and there's usually ppl in here who will answer any questions you might have :) [00:56] anyway, I'm off to lunch BBL === kermiac is now known as kermiac_ [00:56] this clipboard fail bug seems to get lots of users really ANGRY recently. bug #11334 [00:56] Launchpad bug 11334 in ubuntu (and 2 other projects) "MASTER Copy-Paste doesn't work if the source is closed before the paste (affects: 74) (dups: 21)" [Wishlist,Confirmed] https://launchpad.net/bugs/11334 [00:57] again.. what should one do to just have this parcellite in main, auto-installed with desktop and auto run on gnome start?? [00:58] becasue, now other people /then me/ say its an epic fail [00:58] unless we are totally out of disc space (parcellite is tiny), I think we can just do it [00:59] It's such an old bug - I'm kinda attached to it [01:00] you should be attached to it [01:00] if you like when people say linux'es desktop is a joke and they are correct [01:00] my opinion has always been that if any project that tries to fix this problem have a screenshot section on their homepage than they are doing this wrong [01:01] we can hide the icon later (but why) lets fix it now first shall we? [01:02] it's one of ubuntus biggest fails imho, like the broken sound/pulse, and hanging GFX/nvidia - but this one is SO TRIVIAL to fix, compared with really problems with kernels/drivers, or the flash problems... its like x1000 times easier =) I think we are talking about it much more then it would take to just fix it [01:02] is it really so trivial? [01:04] just because there are quite a few implementation of clipboard doesn't mean that they do it the right way. I'm not saying that it shouldn't be fixed - just that from what I can recall the problem was much more complex [01:04] 1) install parcellite 2) add parcellite to auto-start for GNOME 3) BUG IF FIXED \o/ we are no longer 20 years behind other "real" OS ;) woooooooo 4) ???? 5) PROFIT [01:05] you are not a developer, aren't you? [01:05] I am [01:05] you? [01:06] if 10+ years C C++ php counts. Why do you ask [01:06] so am I - and I remember at least few discussions about it when developers were rising some problems that programs like parcellite may introduce - but the last time I've been interested in it was years ago [01:07] you probably mean that this solution is sort of work around and/or is "hackish" [01:07] no, not that [01:07] then what? [01:07] I tried, it works [01:08] in either way it works better then by default. So just install this untill there is time for "better" solution [01:08] I have no idea - it was years ago. something about that those daemons may use a lot of memory in some cases [01:08] They can use an arbitrary amount, depending on what is in the clipboard. [01:08] but anyway, this isn't the right channel or even a way of fixing this bug [01:08] in the bug report, there is a work around by some ubuntu devel or something. It constist of installing an tiny application + starting it at gnome startup. all I say is: JUST STOP OVER TALKING IT ALREADY =) and simply apply this work around by default! how hard is it [01:08] I don't remember the last mailing list discussion about it. [01:09] If the bug is exactly the same except for the version of ubuntu (9.10 vs 9.04) I can mark ad duplicate right? [01:09] But if parcellite is considered the best-of-breed solution, it may be worth filing an MIR and restarting the discussion. [01:09] Anzenketh: right [01:09] But that would be for lucid+1, as lucid is past FeatureFreeze. [01:09] jesus whats with you and the discussions [01:09] you know what, if I would be ubuntu developer, [01:09] this bugs would be fixed now. For months. Or years [01:10] LimCore: what are you waiting for? Becoming a developer isn't difficult. [01:10] it takes 15 minutes to fix it I bet. 30 if you need to print all the forms on paper, get them stamped and faxed forth and back [01:10] The discussion is essential to avoid upload wars. If there is not consensus, there's no assurance that another developer won't override one's changes. [01:10] ok then, my point is: FIX THE BUG [01:11] what are disadvantages? [01:11] I don't know. I'm just suggesting the way forward. [01:11] sigh, what the heck is it with broken sound/pulse being an Ubuntu-specific thing? [01:11] * persia doesn't have permission to make a change log that [01:11] I mean there's FUD, and then there's /FUD/ [01:12] I didnt seen anyone mention any real disadvantages. If someone would copy a huge load of images or 1000 page document, then yea we should expect some memory usage, thats normal (even if it would be 30 instead of 15 mb) [01:12] crimsun: If only one man climbs a mountain, and he slips, he must be wearing lousy shoes. [01:13] crimsun: I am not sure if this is ubuntu fault, but definatelly getting sound to work fully and realibly on ubuntus in a stable way, is often hard. Did not tried other linuxes too much there [01:13] of course it's non-trivial -- I know that quite well. [01:13] it should be trivial [01:13] I just don't see anyone who's complaining bitterly also /stepping forward to help fix it/ [01:14] again with other OSes, I would like Ubuntu sound to be at least as good as on windows in 1999 or so [01:14] but as I said, this bug (sound) probably is very hard to fix, weeks or months of work. Compared to half a day for clipboard things [01:14] anyhow, I don't have time to "discuss" whether sound sucks in Ubuntu. [01:15] crimsun: for people with new Ubuntus that I know (~7 new), for half of them the sound system is failing seriously - they can not play and/or record sound [01:15] tell them to use Lucid, then. [01:15] I do not know, is there a reason for such a broad bug reports? [01:16] because unless there would be some team dedicated to making Ubuntu sound /really/ working, its just waste of time with the reports if noone is acting on them [01:16] LimCore: there /is/ a team [01:16] is it as fast as with the clipboard problem? [01:16] I haven't read backscroll, so I don't know the comparison. [01:16] LimCore: I explained the clipboard problem before...no one wants to listen [01:17] micahg: I am listening. I tried (yours?) work around to install percellite, it works. Why we keep talking unproductivly instead just applying that work around to everyone on Lucid and SRU to Karmic [01:18] LimCore: because not everyone wants that installed, Ubuntu is not like Mac and Windows in that there is no core OS, it's a compilation of packages [01:18] LimCore: also, space on the CD is limited [01:18] then kick out some of artwork [01:19] users just get frustrated [01:19] micahg: that's not the reason - we have a set of packages that are installed as the default desktop and parcellite takes like 300kb installed [01:19] LimCore: Rather than complaining about this, why not work to implement it. Like I said, if parcellite is known to be the right solution, the first step would be to review the MIR process to make sure the code is clean. [01:19] we all know ubuntu is failing to provide functionallity known in other system for 10..20 years, the work around is trivial, and yet here we are still talking instead of doing [01:19] LimCore: Then start a discussion about having it installed by default. [01:20] I dont want to discuss, I want to get it fixed [01:20] A discussion is a necessary part of that. The discussion may be quick. [01:20] if I would like to discuss unprodictivly while people that need my help are left behind I would join UN [01:20] But complaining in this channel neither helps fix the bug nor helps triage other bugs. [01:20] then where exactly to have that discussion? [01:21] Well, first you need to get it into main (or at least have an approved MIR). [01:21] At that point, ubuntu-devel@lists.ubuntu.com is probably appropriate, but starting the discussion prematurely won't help fix the bug. [01:21] this seems to just slow down fixing of the bugs [01:22] Which part? [01:22] Reviewing the code to make sure it's supportable and maintainable? [01:22] the talking part, we already know the problem and the work around [01:22] Or making sure that other developers won't undo the changes after making them? [01:22] the code will be one-liner like + precellite to some auto-run in gnome skelleton [01:22] Many of this class of discussion are 3-4 mails over a week or so. It doesn't need a lot of discussion. [01:23] what about the first part, about MIR and main? [01:23] But *first* the package has to be gotten in good shape. [01:23] That's just a matter of making sure the package is mostly bug free, doesn't have secuirty holes, etc. [01:23] well, glipper is bs, it crashed/hangs. But percellite works [01:23] Make sure it already does the right autostart stuff, and so on. [01:23] Right, but while you know this, not everyone might. [01:23] So get parcellite into perfect shape, and file the MIR [01:23] !mir [01:24] mir is Main Inclusion Report - see https://wiki.ubuntu.com/MainInclusionProcess for more information. [01:24] Bugs are fixed because people capable of fixing the bugs fix them. [01:24] Bugs are not fixed by complaining that developers don't do anything: this just makes people less likely to volunteer to fix bugs. [01:25] Similarly, if you want to help make sound better, join the audio team, and again, it's by *doing* stuff that you get it solved, not by complaining about the issues in the bug forum. [01:26] btw how long it can take to become ubuntu developer [01:26] The first step is intent. WIth that step, one can br productive in days. [01:27] It usually takes a cycle or so of being a developer prior to being granted upload permission. Sometimes more. Depends on activity, skill, time, etc. [01:27] I thought being ubuntu developer is connected with somone approving rights to some ssh keys and stuff [01:27] (it took me about two years from when I first started being a developer until I was granted upload rights, but some people do it in 4-5 months). [01:27] there is a mode where one can upload changes to experimental or something, and then just /quickly/ ask for pushes of that into real repos? [01:27] No. Being an Ubuntu Developer is about deciding to be an Ubuntu Developer. [01:27] upload rights don't hinder controbutions [01:28] *contributions... [01:28] so where are such contributions pushed? [01:28] ppa? [01:28] Generally we attach debdiffs or diff.gz files (depending on the change) to bugs. [01:28] And we seek sponsorship [01:28] that should takes minutes not days imho [01:28] *take [01:28] http://wiki.ubuntu.com/MOTU/Contributing has a (somewhat outdated) description of how to start being a developer. [01:29] !sponsorship [01:29] Factoid 'sponsorship' not found [01:29] Bother. [01:29] !sponsor [01:29] Factoid 'sponsor' not found [01:29] https://wiki.ubuntu.com/SponsorshipProcess [01:29] Anyway, one basically subscribes a team to a bug. [01:29] Thanks micahg [01:29] !sponsorship is http://wiki.ubuntu.com/MOTU/Contributing [01:29] * micahg recalls someone calling me a bot :P [01:29] !dance [01:29] Factoid 'dance' not found [01:29] Getting sponsored takes between hours and weeks, depending on the bug, the availability of sponsors, etc. [01:30] A few days is usually about normal. [01:30] universe sponsors are more abundant than main sponsors ATM [01:30] you'd hope so [01:30] Well, more people can upload to those packages, so the pool of volunteers is bigger :) [01:31] with a 10:1 ratio of packages [01:31] so when I make patches that are accepted, I can be now some officiall debian developer? [01:31] Debian is different. [01:31] But yeah, spend a couple months working on patches with the development team, and the DMB will probably grant you official "Contributing Developer" status. [01:32] I ment to write Ubuntu [01:32] Beyond that it's just demonstrating involvement and capability to join a given development team, and that team might grant you upload rights to their packages. [01:32] (so you become a Kubuntu Developer or Mythbuntu Developer or Ubuntu Desktop Developer, or MOTU, etc.) [01:33] I think 4 weeks should be my goal [01:33] Like I said before, most of the developer teams like to see work though at least a full development cycle before granting someone upload permissions. [01:33] took 1 with FLTK to get rw access [01:34] (4 weeks should make sense to contributing devel stat; not to rw) [01:34] 4 weeks probably takes a lot of effort on your part, to make enough significant contributions that get support from other developers. [01:34] But I'll wish you good luck with it. It's not a bad goal, if aggressive. [01:35] fast progress is good [01:36] :) === Iyunkateus is now known as aihunkatihys [02:52] Bugs that have not been touched in a while do we close them or leave them open? [02:53] neither [02:53] if there is reason to think its fixed, as the user to confirm its still broken [02:53] time is not itself a reason [02:54] If there is not enough information do we set it to incomplete? Or just post comments. [03:00] More or less what is the incomplete status for? [03:03] incomplete means 'not enough data for a developer to work on' [03:05] Oh ok so if I run across a bug report that needs more information comment and set it to incomplete? [03:05] the process docs are all on the wiki [03:06] Oh there it is duh. I just read that too. [03:07] Sorry bit new still trying to get the hang of tings [03:07] no worries [03:07] questions are good [03:17] 18528 bugs ouch wonder how many of them are fixed in the most up to date version. === wgrant_ is now known as wgrant [03:47] crimsun: seb wanted to leave Bug #524304 as a separate one for now. [03:47] Launchpad bug 524304 in gtk+2.0 (Ubuntu) "High CPU usage with murrine progressbars (affects: 6)" [High,Confirmed] https://launchpad.net/bugs/524304 [03:50] vish: ok. OTOH, it affects _every_ GTK engine [03:51] On the triage documentation it state leave developer process bugs alone that means do not change anything on them right including the status? [03:51] vish: I iterated through every single one shipped in Ubuntu to verify it [03:51] crimsun: not here and for the few others who have that bug.. it happens only with murrine [03:51] s/engine/style/ [03:51] it definitely happens here, and I've verified across two daily-live images [03:51] Anzenketh: correct [03:52] Ok made a mistake on that so changed it back. [03:52] but whatever, I've a workaround [03:52] and it is? ;) [03:52] minimising to tray were applicable [03:52] where * [03:52] oh.. ;) that works too [03:53] crimsun: as i mentioned on the bug, as soon as i switch to any other theme which does not use murrine engine. the cpu drops instantly.. [03:53] crimsun: are you using nvidia? [03:54] someone else had another bug which was specific to nvidia [03:55] vish: on the current machine, no (GM45). [03:55] ah nvm then :) [03:56] crimsun: the best way to test that^ murrine bug is install the widget factory and notice the cpu is high with only murrine engines [03:57] themes that use clearlooks/industrial/ or the fallback raeleigh dont have this problem [03:59] If Developer process bugs are not to be touched how to we get them of the non treaged page? [03:59] Or do we just not worry about it? [04:01] Anzenketh, example? [04:02] bug 525075 [04:02] Launchpad bug 525075 in maximus (Ubuntu) "Please merge maximus (0.4.14-1) from Debian Testing (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525075 [04:02] I set to complete due to it had a patch in it but then i figured it was a developer bug due to it was requesting a merge [04:10] Anzenketh: How do you mean "set to complete"? [04:10] I mean like set to triaged or Confirmed [04:11] Oh, yeah, it's best to just ignore those bugs. [04:11] There are efforts working on better ways to deal with them, but it will take some time. [04:12] Setting to "confirmed" in this case wouldn't have mattered (and it would be the correct status, technically, according to the developer workflows), but we try to avoid doing anything that generates bugmail for that class of bug. [04:12] Ideally, we'd have some other way to track candidates. [04:13] The DistributedDevelopment team has done work to enable that for some workflows, but the tools are still maturing. [04:13] With luck, this class of bugs will go away in another year or two. [04:14] vish: it's reproducible here for all engines [04:14] vish: I did that precise test on two daily-live images [04:14] anyhoo, back to audio bugs [04:14] crimsun: weird.. :s for the ones who confirmed that bug it happens only with murrine [04:15] yay audio :D [04:15] Ya launchpad does not seam like the best tool for triage either. [04:15] Well, if we could get rid of all the special case bugs, it would be better for that :) [04:17] Ya it would also be nice to systematically go down the bugs to be treaged [04:19] Well, I think there's only three special cases left: stable updates, syncs, sponsoring. [04:19] Sponsoring is getting closer and closer to being ready. [04:20] All three of those are developer process type bugs right? [04:21] Yes. [04:21] Well, syncs and sponsoring are. [04:21] stable updates are a bit trickier, as they also involve users. [04:21] But stable updates can probably be handled with improved nomination/distribution tracking support. [04:23] hello [04:23] i see there is opening for Linux QA at montreal office of canonical [04:25] I am looking at bug 194101 that there is a post from launchpad Janitor It states that there was a fix released for the bug. Should I also set the bug to fix released? [04:25] Launchpad bug 194101 in kubuntu-default-settings (Ubuntu) (and 1 other project) "Ignore error of "update-alternatives --remove" in postrm" [Medium,Fix released] https://launchpad.net/bugs/194101 [04:34] high i need help debugging my wifi card driver? any help available? [04:36] tweiseman: Support is best found in #ubuntu [04:36] If you know it's a bug, we can help make sure it gets the right attention. [04:36] okay i just saw you guys under a debugging page. ill check there [04:37] * Anzenketh wish there was a way or a process to put waiting for bug reporter to respond back [04:40] that could be helpful. i was talking to a local luug program near me and they said my driver is working fine but i just need to debug it [04:55] Recommend Bug 194946 be set to wishlist [04:55] Launchpad bug 194946 in partman-crypto (Ubuntu) "installer clobbered encrypted part. poor warning." [Undecided,New] https://launchpad.net/bugs/194946 [04:56] Anzenketh: No, because of the potential for user data loss. [04:56] (try again :) ) [04:56] Interesting I am part of the triage group but do not have access to set to triage. [04:58] Anzenketh: There are various levels of access control. Once you get more experience, you'll want to apply for Bug Control. [04:58] Ahh it is the bug control group [04:58] That makes sence. [04:58] But this takes a while. A very motivated individual with lots of experience might do it in 2-3 weeks, but it's usually a month or more (depending on activity level, etc.) [04:59] persia, that's good to know...i might be closer than i thought then [05:00] I am ok with waiting. I am glad I finally found something I can help out with. [05:00] ddecator: Just check the requirements. If you're certain you can give good answers to the questionaire, and expect enough people to be familiar with your work to review your application, you're in good shape. If you're not there yet, at least you'll know how far you have. [05:07] persia, hmmm, i can give good answers to the questionnaire, but i'm not sure how many people have been following me closely... [05:08] ddecator: Well, let me ask that a different way. Do you feel like you're part of the team, and most of the others here are peers, or do you still feel like you're learning how to do it? [05:09] If the former, you've probably been watched enough, as we tend to watch new folk (especially as we respond to requests to adjust status and importance). [05:09] If the latter, keep at it, and ask for status/importance review more, and you'll get there. [05:10] persia, i feel like you are all peers. i don't feel like i can take just any random report and know exactly what to ask for, but i can work out most of them, and micahg is teaching me how to specialize in firefox reports [05:13] ddecator: That's usually a good indicator. Worst case is that if you apply and get deferred, you'll get feedback why, and know what to do in order to be approved [05:14] We never reject anyone, we only defer or deny requests for increased permissions, and hope anyone who doesn't get more permissions today will apply again soon. [05:14] persia, true...one thing i'm wondering, the wiki asks if the person provided the importance they would give a report...i never said it in the comments, but i worked out the importance on this channel...does it need to be documented that i worked out the importance? [05:17] ddecator: You can just say "The importances for these bugs were all set on request by folk on #ubuntu-bugs" or similar. [05:17] You need to pick bugs where you chose the importance. If some still aren't set, then you can note it. [05:18] If you got them all set already, that's good evidence of team integration :) [05:18] persia, fair enough...so if i can find 5 reports that i think are good examples of my work, do you think i should apply and worst-case-scenario get helpful feedback? [05:19] ddecator: I'm not going to tell you to apply : I believe it's something people should do when they think they are ready. [05:20] In part this is because I believe that deciding one is ready is an important step to being ready :) [05:23] persia, good point =). i feel confident so i'm going to look at my previous reports and see if i can find 5 goods examples. if i get it all setup, who do i send it to? i don't see the list on lists.ubuntu.com [05:23] The answers you seek are in the wiki :) [05:23] persia, that's what i'm looking at, but i wasn't reading "AT" as @, haha [05:24] persia, thank you for all the help =) [05:31] bdmurray, jcastro: can I please get my bugcontrol membership renewed? it's about to expire... [06:12] there we go =) [07:31] bugcontrol please: set bug 525620 importance to Wishlist (I am the reporter) [07:31] Launchpad bug 525620 in launchpad-gm-scripts "control switch just for team names expansion, not LP_Karma_Suffix (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525620 [07:32] kamalmostafa: the bug has been reported in the upstream task , so only the concerned devs can change it [07:33] bd_murray i guess.. [07:34] vish: okay, no worries -- they'll figure it out. thanks. [07:34] np.. [07:48] www.search2.net [09:56] bdmurray: Why add the "patch" tag to bug #511502? There aren't any patches there that haven't already been uploaded. [09:56] Launchpad bug 511502 in xdvik-ja (Ubuntu) (and 16 other projects) "TeXLive 2009 transition: libkpathsea5 (affects: 2) (dups: 1)" [Undecided,Fix released] https://launchpad.net/bugs/511502 [09:57] bdmurray: If this is a script, might it make sense to try to tune to only hit active bugs, to avoid sending email for old stuff? [10:28] two days for the anniversery of #ubuntu-bugs topic ;) [10:29] It's a topic that would be hard to improve. [10:30] We used to add bits to it for Bug Days, but that gets annoying, and led to arguments about whether it was or was not Thursday and similar. [10:32] LOLOL [10:32] TimEZones suck : [10:58] hi, is there a project to file bugs against ubuntu archive mirrors? bug #525608 [10:58] Launchpad bug 525608 in update-manager (Ubuntu) "Cyprus Ubuntu mirror does not have the correct directory structure (affects: 1)" [Undecided,New] https://launchpad.net/bugs/525608 [11:12] what is the rescue mode package? [11:20] Damascene: if you mean the menu that is being displayed it is from friendly-recovery package [11:21] some one in ubuntu+1 is saying the recovery mode isn't working [11:21] Can you replicate? [11:22] we are asking him [11:24] I asked "Can *you* replicate", not can the person experiencing the issue replicate :) [11:24] The point being that it's probably best to either guide them to file a bug, or for you to replicate and file the bug. [11:24] persia: as he didn't tell what the problem was it's hard to duplicate it :) [11:24] Just asking about it in the absence of someone who is prepared to be the bug reporter is harder. [11:25] kklimonda: Surely :) [11:26] I understand now, sorry :) [11:26] I'll try [11:30] I saw the menu of recovery mode and dropped to root shell and rebooted, no problem there [11:34] OK, then you want them to report the bug, if they can get the system back into the state that shows it. [11:35] ok === kermiac_ is now known as kermiac [11:55] persia, here it is PascalFR [11:55] hello toward what package can I report a bug for rescue mode beeing unusable ? [11:58] kklimonda: You said it was "friendly-recovery", right? [11:59] persia: yes he told me that [11:59] :) [11:59] Well then, that's probably it :) [12:00] * persia doesn't know about this package, but keeps getting highlighted === kermiac is now known as kermiac_ [12:10] well it is already reported as bug #489014 :) [12:10] Launchpad bug 489014 in friendly-recovery (Ubuntu) "Selecting "recovery" on reboot causes mixed console and menu activity (affects: 1)" [Undecided,New] https://launchpad.net/bugs/489014 [12:17] status now bug #489014 [12:17] Launchpad bug 489014 in friendly-recovery (Ubuntu) "Selecting "recovery" on reboot causes mixed console and menu activity (affects: 2)" [Undecided,Confirmed] https://launchpad.net/bugs/489014 [12:17] ok [12:18] thanks Damascene persia kklimonda [12:32] hello === om26er_ is now known as om26er [12:57] amjaduae, Hi [13:10] I'm having trouble with a certain bug (aside from the bug itself). Something makes 'finding the root device' impossible, but what package is responsible for that? I filed against lvm2, because root is on lvm, but I'm not sure about that and debugging is hard when one can't boot. (Most of the time booting does not work, but when it works, nothing can be seen in the logs off course) [13:10] Oh I forgot. It's bug 460914 [13:11] Launchpad bug 460914 in lvm2 (Ubuntu) "karmic rc: root device sometimes not found (affects: 1)" [Undecided,New] https://launchpad.net/bugs/460914 [13:11] hi Damaascence [13:13] The bug is extremely critical and severe. Don't pay attention to the 'affects 1'. I'm seeing this on 5 different servers. Probably my way of installing, but I don't know what I did wrong during install. [13:13] err Damascene [13:17] hggdh: hey :) [13:35] amjaduae, :) [13:35] whats up Damascene:) [13:36] may I private message you? amjaduae [13:36] sure , but what it is that you can not say here [13:36] a secret maybe :) [13:36] offtopic [13:37] k [13:57] hi nigel [13:57] hi nigelb [13:57] hggdh: any luck with the hook? [13:57] or rather the filtering.. [14:00] nigelb: I had missed a small detail... [14:00] http://etherpad.com/HocXEybBnk [14:01] nigelb: instead of str(1) I should have written str.group(1) [14:01] hggdh: that caused the entire issue? [14:02] yes [14:02] hggdh: what does the last part do? [14:02] the debugging [14:04] hggdh: lol, you forgot '\n' again [14:05] oops.1 debugging?? oops.2 \n? [14:06] lol "## DEBUGING ##" [14:06] why did you use '\\n' instead of '\n'? [14:06] oh, yestypo [14:06] typo [14:07] ah, I thought it was meant to be something and you forgot an option :p [14:07] the ## debugging ## piece I am still writing -- a way to call the hook without needed to run rhythmbox [14:08] um, we dont need to run rhythmbox anyway (unless using debug output) [14:08] but I need to go back into apport, and see what is in the 'ui' parameter to add_info() [14:08] yes. you could call 'python ./source_rhythmbox.py' instead [14:08] line 26 is also looking wrong ;) should be `response2 is None` [14:08] *this* one I am not guity of ;-) [14:09] nigelb: ^ [14:09] haha [14:09] ah, it should be response2 == None [14:09] I added the none from the c hangover [14:09]