[01:45] hi there [01:46] I just red in the fridge, you're looking for people who can help you with translations [01:46] Am I right? [01:48] I want to help [01:50] moiso, I'd suggest asking in #ubuntu-translators as a more well-targeted channel. [01:51] Be aware that it's Friday night or Saturday morning most places, so lots of folks are out, sleeping, or praying about now. [01:52] haha you're right! thanks persia [01:52] Sorry i'm kind of a noob [01:52] No worries. Thanks for offering to help. [02:05] people are out, except people like persia and myself :P [02:05] its called devotion ;) [02:22] submitted some bugs to debian before going to sleep last night, 'submittodebian' reported the bug submitted and stated I'd receive an email as per usual but there's no reports lodged and no email conformation in my inbox.. has anyone experienced this before? [03:29] what do we do with comments that are spam, is there a way to remove them? see bug 600022 [03:29] Launchpad bug 600022 in firefox-3.0 (Ubuntu Hardy) (and 3 other projects) "package firefox 3.0.19 nobinonly-0ubuntu0.8.04.1 failed to install/upgrade: trying to overwrite `/usr/share/bug/firefox/presubj', which is also in package firefox-2 (affects: 6) (dups: 3) (heat: 93)" [High,Fix released] https://launchpad.net/bugs/600022 [03:32] drew2121: you file an 'answer' on LP against 'The Launchpad Registry' See https://answers.edge.launchpad.net/launchpad-registry/+question/108960 as an example [03:33] you mean make a new question? [03:35] drew2121: heh.. yeah, I do [03:36] drew2121: sorry mate, my brain is not completely into gear yet [03:36] its fine =) [03:40] also, can someone verify this should be wishlisted so i can mark it as triaged: bug 625474 [03:40] Launchpad bug 625474 in firefox (Ubuntu) (and 1 other project) "Firefox: Downloading a file: Open with: "Other..." should display the "Open With Other Application"dialog (affects: 2) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/625474 [03:42] nigelb: did you call me a 'minion'? http://irclogs.ubuntu.com/2010/08/27/%23ubuntu-bugs.html#t19:26 haha [04:17] kermiac: hahaha, kidding ;) [04:18] kermiac: having a jam today? [04:18] nigelb: haha, it's ok mate.... I had a good laugh [04:19] nigelb: nope, noone really showed any interest. The loco in Australia isn't really very local [04:20] i was also too busy & didn't send anything to the loco mailing list, so it's partially my fault too [04:20] kermiac: I'm *trying* to have one today [04:21] dunno how its going to end up [04:21] Not much of participation promised [04:21] If nothing works, I'll just take a session on how to tirage bugs :) [04:23] nigelb: well, good luck mate.... tedg would be the one to ask about an app-indicator hook, right? [04:23] not sure mate, ask vish, he'd know whom to poke [04:24] ok, thanks nigelb :) [04:24] * kermiac pokes vish! === rackIT_AFK is now known as rackIT [08:05] kermiac: yeah, either tedg or kenvandine.. [08:30] vish; I tried to send the fixes for the papercuts I patched to debian last night. 'submittodebian' said it was all submited but the tickets aren't on the bugtracker and I've not received any emails. Super weird. [08:30] somethinginteres: yeah , i dont understand why it dint work for you either [08:31] somethinginteres: have you tried sending the patch the old fashioned way? email? ;) [08:32] vish: ah, no I actually just read that was possible would it be fine to just send it via email and attach the debdiff? [08:32] somethinginteres: yup , should work [08:33] vish: no probs. So yeah if you're wondering 'why has the guy not sent it upstream for them to patch it first?' that's why. :D [08:33] somethinginteres: nah.. i dint wonder that.. :) [08:34] somethinginteres: but try to make sure to send patches for sync packages to debian, if we make changes in Ubuntu it increases the workload for a lot of people === standa is now known as stbulicek [08:37] vish: yeah for sure.. normally I've been sending the patches to debian as well as adding the debdiff on LP - not sure if that's what should be done [08:38] vish: I assume anything that tracks bugs on the debian bug tracker is considered a sync package, is that correct? === stbulicek is now known as stbulicek_ [08:39] somethinginteres, Best practice to send bugs both places. Extra points for sending them to ultimate upstream as well. [08:39] somethinginteres: any package that does not have an Ubuntu change , it is usually mentioned in the version# like 2.28~ubutnu0 === stbulicek_ is now known as stbulicek [08:41] persia, vish: alrighty. Well I'll get the bugs submitted on debian asap [08:46] hi [08:52] Hi, I need to get information for a bugs (623 450). It's in a state of "Fix Released". What does it mean? [08:53] bug 623450 [08:53] Launchpad bug 623450 in zenity (Ubuntu) "file selection on /dev returns wrong filename (affects: 3) (heat: 18)" [Low,Fix released] https://launchpad.net/bugs/623450 [08:53] It means it's fixed. [08:53] Seems to be only an issue with older versions of the software. [08:54] !sru [08:54] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [08:54] I think it's unlikely that it qualifies for a stable release update, but you could review the criteria, and if you think it does, start that process. [08:57] hi persia. How to fix in Lucid? [08:59] If you think it meets the criteria for a stable release update (lucid is a stable release), then you can start the process, as described on that wiki page. [08:59] If the stable release update coordinators happen to agree with you, and there's a working patch that causes no regressions, it can be fixed. [09:00] umh... [09:00] :) [09:06] It 's my first bug that I follow. I do not understand English well ... I read the steps I have suggested. The terminology is new to me and then almost incomprehensible. [09:09] OK. Let's look at the criteria in detail. Let me know when we use a term you don't understand, and we'll make sure you do. [09:09] Stable release updates will, in general, only be issued in order to fix high-impact bugs. [09:09] Examples: [09:10] Bugs which may, under realistic circumstances, directly cause a security vulnerability [09:10] This bug isn't a security issue, so this one doesn't apply. [09:10] Bugs which represent severe regressions from the previous release of Ubuntu. This includes packages which are totally unusable, like being uninstallable or crashing on startup. [09:10] So, if the bug exists in lucid, but didn't exist in karmic, we can use this example reason. [09:10] because it makes it impossible to track stuff in /dev. [09:11] Bugs which may, under realistic circumstances, directly cause a loss of user data [09:11] This is unlikely: folks get sent to the wrong place, but nothing is being deleted. [09:11] Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). [09:11] zenity isn't critical infrastructure, so this doesn't apply. [09:11] For Long Term Support releases we regularly want to enable new hardware. [09:12] lucid is LTS, but fixing this won't enable new hardware, so this doesn't apply. [09:12] FTBFS(Fails To Build From Source) can also be considered. [09:12] The package builds, so this doesn't apply. [09:12] In summary, based on the examples there, you'd have to demonstrate that this was a regression from previous releases of Ubuntu to qualify. [09:13] You'd also have to demonstrate that this was a high-impact bug. [09:13] Does that all make sense? [09:13] persia: you read something wrong [09:14] Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). [09:14] zenity isn't critical infrastructure, so this doesn't apply. [09:14] its saying "meep! dont touch critical infrastructure!" not "only critical infrastructure can be changed if its outside of those categories" [09:14] Oh. [09:14] so, leaf node packages is how id read that [09:15] In that case, the requirement is only that the bug be shown to be high-impact, and that an obviously safe patch be available. [09:15] It doesn't need to be a regression (but extra points if it is a regression: that helps the discussion with the SRU folk) [09:16] that also bumps it to "high impact" quicker [09:17] I disagree. [09:18] There were several regressions I identified in lucid that were low impact (minor visual issues that only affect people with certain combinations of vision impairment) [09:18] Annoying to me, but not important enough to fix. [09:18] (and easy to work around) [09:19] Being a regression only helps the justification if it *is* high-impact in some other way. Alternately, some high-impact bugs that are not regressions (it's better than it was, but still bad) won't be considered for SRU because it's too messy. [09:20] (and packages in that state are easy to get mistakenly worse when fixing one bit in the whack-a-mole game) [09:28] Thanks, I generally only use LST because the constant updates are not easily feasible (backup procedures too complex and not always working, updates very dangerous without full backups). Like me, many other people use the LTS versions. I'm developing software for the community 'to recover accidentally deleted files in Bash and the only way to interface to graphics and' zenity (I know). This bug stops me. I must find a way [09:29] Just blacklist /dev [09:29] It ought be tmpfs anyway [09:29] And deleted files ought reappear on reboot or reattach [09:30] (and next time get your software working in Ubuntu before the LTS releases :) ) [09:34] Ho letto, ma non so comunque come risolvere la questione. Cosa dovrei fare? [09:35] !it :) [09:35] Factoid 'it :)' not found [09:35] !it [09:35] Vai su #ubuntu-it se vuoi parlare in italiano, in questo canale usiamo solo l'inglese. Grazie! (per entrare, scrivi « /join #ubuntu-it » senza virgolette) [09:35] I have read, but still do not know how to resolve the issue. What should I do? [09:35] sorry :) [09:35] So, make your program ignore /dev [09:36] (or did I read the bug wrong: it looked like it only affected /dev) [09:36] umh [09:38] ok [09:38] thanks === yofel_ is now known as yofel === bilalakhtar_ is now known as bilalakhtar [15:13] I'm looking for an easy bug to fix [15:17] Sofox, choose the one you like https://bugs.launchpad.net/hundredpapercuts/+bugs?field.status:list=TRIAGED [15:18] Thanks [15:32] om26er, Nice list to choose from :) [15:33] * MichealH bookmarks === erhesrhsrtb54vyh is now known as Elbrus [16:34] MichealH: that bug's patch needs to be forwarded to debian, and bonus if you can write a nice description ;) [16:43] In bug 435990 a user is saying that firefox is slowing down his computer, i asked him to get a backtrace/strace and he said that wouldn't help, was i wrong in asking for an strace/backtrace? [16:43] Launchpad bug 435990 in firefox-3.5 (Ubuntu) "fox fatigue: getting progessively slower until unusable (affects: 2) (heat: 15)" [Undecided,Incomplete] https://launchpad.net/bugs/435990 [16:45] vish, Okay [16:46] How would I get sponsorship [16:46] MichealH: hmm , the patch sponsored? [16:46] vish, huh? [16:46] The .deb [16:46] How would I get sponsorship [16:46] ^ ? [16:47] How can Iget the .deb patch sponsored? [16:47] When does the debian freeze start [16:47] MichealH: .deb dont get sponsored [16:47] How do I upload them [16:47] MichealH: you write a debdiff [16:48] What is a debdiff? [16:48] MichealH: as i mentioned , that patch needs to be forwarded to debian. then we need not worry about debdiff [16:48] So how would I go about that? [16:49] I have a DEB in /var/cache/pbuilder/output [16:49] Or wherever it goes [16:50] MichealH: first try to read : https://wiki.ubuntu.com/Bugs/HowToFix [16:50] vish, Okay [16:56] vish, So I file a bug in Debians bug system with the package? [16:57] MichealH: yup, file a bug when you have a patch ready .. any doubts about making patches, ask in #ubuntu-motu .. [17:16] I would be interested to know if this bug https://bugs.launchpad.net/telepathy-butterfly/+bug/519551 will get fixed in 10.10 now that a fix has been released upstream [17:16] Launchpad bug 519551 in telepathy-butterfly (Ubuntu) (and 2 other projects) "Video call to/from MS Messenger contact does not work (affects: 4) (dups: 1) (heat: 43)" [Medium,Triaged] [17:22] TonyP: om26er might know^ , if he is around.. [17:34] hello, is there a list of interesting bugs that could be worked at bug jam? [17:35] gilbert_: well, you could use the latest bugs reported with maverick tag, would be nice if we triage many of those before final freeze [17:36] Thanks vish, I will send Omer an email [17:44] how's the global jam going? [18:28] drew2121: no, you were not wrong. There is the impression that they can only obtain a backtrace if it crashes. By following the wiki page, they can obtain the backtrace even if it does not crash. [18:29] they should follow the instructions, and when it slows, they can end the trace as it says. [20:16] devildante: hey , looks like the Software sources menu entry is not really hidden! :s [20:19] vish: why would it be hidden o.O? [20:20] yofel: because we fixed it to be hidden! but apparently the fix was not right :D [20:30] vish: hmm... [20:31] should please Scott Ritchie :p [20:32] vish: but more seriously, I don't know why it's not hidden :( [20:33] devildante: is there a .desktop also ? looks like you changed it only in the .desktop.in or I'm not sure.. [20:34] vish: the .in in .desktop.in means it will be translated before being renamed to .desktop [20:35] devildante: well , you submitted the merge, right? or did you make a debdiff? [20:35] vish: I submitted a merge and mvo merged it [20:36] note that /usr/share/applications/software-properties-gtk.desktop contains the change (at least for me) [20:36] devildante: check the diff for the upload , looks like the .in thing works when we debduild [20:36] oh! [20:36] devildante: but is it there in the menu? [20:36] vish: yes :( [20:36] bah! [20:38] devildante: i dont know , maybe someone in -motu might know [20:38] !weekend | vish [20:38] vish: It's a weekend. Often on weekends the paid developers and a lot of the community may not be around to answer your question. Please be patient, wait longer than you normally would or try again during the working week. [20:38] hrm! [20:38] ubot2 saves me from writing a lot :p [20:38] devildante: Error: I am only a bot, please don't think I'm intelligent :) [20:38] devildante: the two of us are here right? [20:38] yeah! [20:39] devildante: well, all i knew about the .desktop was there is a flag to hide it.. but not sure why it is not working.. so motu is your best bet, weekend or not! ;p [20:40] wow, 194 users in -motu! [20:40] vish: but how could they help us? [20:41] (as far as I know, MOTU is about packaging) [20:42] devildante: yeah , they might know, during packaging they make sure a file is displayed or not, and often .desktops are in the debian dir too [20:42] devildante: bah , anyway.. *I* dont know! ;p [20:43] devildante: all, i know is bug not fixed, yet ;p [20:43] meh, I'll ask them [20:44] devildante: see, two can play this game ;p [20:44] meh :p [21:41] is there a good guide on how I can run a git repository of a program without affecting my current stable installation? [21:42] bcurtiswx: would PPA purge do it? [21:42] if something gets borked? [21:43] i don't know what PPA purge is.. i guess i can assume what it does [21:43] i was told i could install something from get 'non system wide' [21:43] i didnt really get around to trying it though [21:44] that, in theory, would be easily undo-able [21:44] but if your adding a PPA [21:44] you can use PPA purge [21:44] OK, thx.. not exactly what I'm looking for tho [21:44] yeah :/ [21:48] bcurtiswx: It depends, if the git repo is being built from source and is a stand alone app then you can just tell it to build it into somewhere else - e.g. /more/disc/testing and run it from there, if it's a library you can point stuff to it like that using LD_LIBRARY_PATH , stuff gets more tricky if it's some integral part of gnome for example [21:50] penguin42, empathy [21:50] bcurtiswx: You probably stand a fairly good chance of building that in a separate dir; although if it depends on a lot of newer libraries for example things get messy [21:51] penguin42, OK, thx [22:08] any C Gtk+ experts here? I'm stuck :p [22:09] devildante: Only a tinkerer I'm afraid [22:10] penguin42: when invoking g_timeout_add with arguments to pass to the callback, in which format must they be? And what should be the callback prototype? [22:12] devildante: I don't know, but looking at code.google.com it looks like it's g_timeout_add(time, (GSourceFunc)function, anypointer); [22:13] and any pointer is passed as the one and only parameter to your function - whatever it happens to be [22:13] devildante: e.g. http://code.google.com/p/yplayer/source/browse/trunk/player.c?r=6 [22:14] penguin42, thanks :) [22:26] laugh at me then tell me what I did wrong here: sprintf(label_string, "%d:%d", minutes, seconds); [22:27] what are the types of all those [22:42] hmm [23:21] (whoops, sorry for late reply) [23:21] penguin42: these are int [23:21] devildante: OK so the two last ones were date and time, how was the string it's going into declared? [23:22] penguin42: gchar *label_string; [23:22] devildante: And did you allocate space for the string? [23:22] whoops [23:22] :-) [23:22] penguin42: I didn't :p [23:22] penguin42: thanks :) [23:23] no problem [23:23] * devildante doesn't like C [23:25] devildante: If you're doing something strictly linux only you can use asprintf that will allocate the string (passing &ptr as the first argument [23:25] penguin42: oh, didn't know that, thanks :)