[00:12] stpere, probably, yes. I do not consider 2.24.3 stable enough, so it will probably be a SRU [00:12] SRU? [00:13] Stable Release Update [00:13] oh ok [00:13] thanks [00:13] because I'm having a very bad bug here === ubott2 is now known as ubottu [00:13] https://wiki.ubuntu.com/StableReleaseUpdates [00:13] a sent email that get sent over and over again [00:13] everyday [00:13] it doesn't get out of outbox [00:14] it's marked as deleted in the outbox, so it's hidden [00:14] but is sent again anyway [00:14] very embarrassing [00:31] indeed, and I have not heard of such before [00:36] the pythonistas bugs really need a check for incomplete/invalid/outdated bug reports: https://bugs.launchpad.net/~pythonistas/+packagebugs [00:40] can somebody who knows something about backtraces have a look at bug 325903 and tell me if they think the root of the problem is in lib4vl [00:40] Launchpad bug 325903 in telepathy-stream-engine "telepathy-stream-engine crashed with signal 5 in g_object_ref()" [Medium,New] https://launchpad.net/bugs/325903 [00:40] im terrible at reading down traces [00:41] why does it have a "Medium" and a "new" status? [00:41] bug 322368 actually crashes at the same line in telepathy's nain [00:41] Bug 322368 on http://launchpad.net/bugs/322368 is private [00:41] main* [00:42] sectech, i think apport does that when it gets a complete backtrace [00:42] Ahh ok... [00:42] explains a few that I have seen previously then [00:42] yaeh its actually getting fairly common [00:42] I actually had a person report a bug against a "known problem" which he even quoted was in the release notes. [00:43] I guess he didn't read to NOT report bugs related to those. [00:43] lol [00:44] I didn't want to spend too much time for that one so I kindly explained that it was a known issue, hence his quote of the release notes and set it to "Won't fix" so he couldn't fiddle with the status [00:44] I could have dup'd it by searching for the original issue, but the point would seem kind of moot [00:44] heh, well, any ideas about those traces? [00:45] Hmm let me pull up the bug [00:45] im thinking actually since there are 2 bugs crashing initially at the same line in the program, it is a program problem [00:45] not a lib4vl issue [00:46] First I would look through the traces for sensitive information, and if there is none mark it public [00:46] I'm not the best at traces but I'll see if anything pops out at me [00:46] Rocket2DMn, this seems to be an abort signal from glib [00:47] good to know hggdh , how can you tell that glib is the source of the problem? [00:47] i mean, glib is in practically every gnome crash report [00:48] oh, I cannot. signal 5 is sigabrt, a request to abort the programme [00:48] glib generated it [00:48] probably as a result of the processing in first entry in the BT [00:49] hggdh, where did you see the sig 5? [00:49] in the title and the description of the bug [00:49] heh, helps if I scrolled up [00:49] I was looking though the traces [00:50] this is more probably an issue in the package itself (telepathy) [00:51] ok hggdh , but the big question is: how do i know the true source of the problem [00:51] heh [00:51] I think I found a bug in the livecd boot process. I need to talk to some before I submit a bug report. [00:52] hggdh, both bugs i listed crashed at the same line in the program's main.c, a lot of the traces are similar, but they end differently at 0 [00:52] Rocket2DMn, you would have to go to the source, and look it up in the glib docs on why it would generate an abort [00:52] huh -- I had not noticed the second bug [00:53] /headdesks [00:53] any one working on the livecd [00:54] Rocket2DMn, yes, both of them ended in sigabrt. Also both BTs show that glib is processing an assertion, and that this assertion failed [00:54] perhaps the users were running with --g-fatal-warnings ? [00:55] i have no idea what that option is [00:55] any failed assertion will cause the programme to terminate [00:55] so you think the bug needs to be filed against glib? [00:56] glib2.0 to be specific [00:56] Rocket2DMn, I do not think so, not so far [00:57] I do not know telepathy, so this can still be a telepathy issue [00:57] although glib bugs do happen, they are quite rare [00:57] that's what i would hav einitially thought [00:57] look at the bottom of both stacktraces, they crash at the samea line in main [00:58] stream-engine-main.c:335 [01:00] yes -- this is probably where it is registering itself with glib [01:01] so i guess i should file this against telepathy on freedesktop [01:02] yes, sounds so [01:03] man there are a fair number of bugs reported, how the heck am i supposed to find dups [01:03] wish they had a dup-finder like gnome [01:05] hmm none jump out at me [01:07] yes, this would help -- the dup finder rocks === Flare183_ is now known as Flare186 === Flare186 is now known as Flare18 === Flare18 is now known as FlareFlare [01:24] ok, i have question about defining an upstream link on LP [01:25] telepathy-stream-engine package has no upstream links defined, and i think "stream-engine" is what is needed [01:25] I was going to add that as an upstream series, but i'm not 100% sure === asac_ is now known as asac [02:39] Rocket2DMn, sorry for the delay, in a work technical discussion [02:39] Rocket2DMn, you copy copy & paste the link to the bug upstream [02:39] s/copy copy/just copy/ [02:48] hggdh, say again? [02:48] i asked in #launchpad and they said to go ahead and make the connection [02:49] hggdh, bug 322368 - i connected that ubuntu package with stream-engine (which is part of Telepathy) [02:49] Launchpad bug 322368 in telepathy-stream-engine "telepathy-stream-engine crashed with signal 5 in g_return_if_fail_warning()" [Medium,Triaged] https://launchpad.net/bugs/322368 [02:50] that package didnt have an upstream project associated with it yet [02:52] anyway, thanks for the help, im signing off now. peace [05:39] bdmurray : In case you're here, my membership in the bugcontrol team is about to expire and I would like to ask you to renew my membership if possible. I've not been as active with bugs in 2008 compared to 2007 but I'm still contributing when I have time and I expect to continue in that way in the next years. [05:41] bdmurray : I'm going outside now but if you want, you can email me at anytime or ping me on IRC === lacqui_ is now known as lacqui === Afwas_ is now known as Afwas [10:30] was navigating through LP to prepare for the Global Bug Jam I ran into this : https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/294991 the page says that its confirmed then triaged and I think its an upstream bug(right?) is there any more information I can get about this bug? [10:30] Ubuntu bug 294991 in telepathy-sofiasip "SIP/Ekiga accounts don't store contacts" [Unknown,Confirmed] [10:33] anybody there? [10:38] shankhs: what do you want to know exactly? [10:38] it's an upstream bug, yes [10:38] one part of it seems to be fixed upstream already [10:39] just click on the links in the "assigned to" column [10:50] dholbach: there are 2 links. both of them are trying to fix the bugs? Or is it that the bug affects both of them? [10:50] that's what I think [10:50] but I did not investigate it muchly and am no expert [10:52] dholbach: it also says that the bug is triaged and is confirmed that its an upstream bug then why ubuntu bothers to keep it in LP why not let gnome tackles it ? [10:52] shankhs: we still track it in LP, it's not resolved yet [10:53] In case there is a fix upstream that we want to add as a patch to the ubuntu package. [11:03] shankhs: btw empathy bug is already fixed on jaunty, but a task in Ubuntu for telepathy-sofiasip needs to be open to keep tracking of the upstream one [13:23] a couple bugs that i noticed that make triaging a bit harder are bug 291968 and bug 291980 [13:23] Launchpad bug 291968 in malone "status_upstream=hide_upstream seems to hide bugs with 'invalid' upstream status" [Undecided,New] https://launchpad.net/bugs/291968 [13:23] Launchpad bug 291980 in malone "bug incorrectly listed as pending_bugwatch" [Undecided,Confirmed] https://launchpad.net/bugs/291980 [13:26] bdmurray: do you know how to escalate issues like the above to the launchpad team? [13:26] bdmurray: i didn't know if this meeting was the appropriate place to raise the above issues [14:45] Hi [14:46] where should I report bug for the gnome login sound (glitches)... pulseaudio ? [14:46] in 9.04 [14:53] mvo bug 274737 [14:53] Launchpad bug 274737 in update-manager "Changelog url bug" [Low,Triaged] https://launchpad.net/bugs/274737 [14:59] kagou: I think that the best place for that kind of bugs is gnome-control-center , although I'm not an expert so... let's wait for some more suggestions! [15:01] may be seb128 have a better idea ? [15:02] no clue, open a pulseaudio bug on launchpad [15:03] thanx [15:03] cya [15:03] kagou: :) [15:04] kagou: I told you that it was better to wait for some more suggestions! [15:39] With the new updates, Kubuntu networkmanager works in Jaunty again :) [16:16] mangilimic, at leat my bug report is confirmed by someone else :) [16:36] MrKanister, I updated the hugday-tools package in my PPA this morning, I should work now without pulling py2.4 [16:37] this sqlite thing should also be fixed [16:40] thekorn: Thank you very much. The "hugday init" now works with "--cookie" (the ppa version), I will try the "--moinmoin-id" way later [16:41] super, thanks fr testing [16:42] thekorn: Great. "--wiki-id" is working like a charm :) [16:49] cool, if you have any ideas how this tool can be improved, I'm happy to hear about them [16:50] thekorn: I've added an agenda item to the QATeam for next week asking for testing on the hugday-tools [16:51] btw folks if you have something to discuss https://wiki.ubuntu.com/QATeam/Meetings [16:51] something new and cool you want to talk about just add it [16:51] gotta run now, see you later guys === Brownout_ is now known as Brownout [17:41] hey all [17:46] on Ubuntu's website, under the BugSquad section, under Getting Involved, I think there is a bug in the link to bugs without a package. [17:46] the entire top part of the list are bugs that need packaging, and i believe this is a different problem [17:47] or, it might be a bug in the search for bugs without a package, as requests for packages inherently have no package [18:02] mbwjr12, I think the problem here is that an important part is missing in the descriptive text of this section on the wiki page [18:02] something like "there are also some workflow related bugreports, like needs packaging bugs" [18:05] I'm bad in phrasing such texts [18:10] thekorn: using the advanced search function to find bugs without packages also returns bugs with [needs-packaging] in them [18:13] mbwjr12, right, because all this needs packaging bugs are not targeted to any package/project yet [18:15] and this is what should be explained on this wiki page, that there are alot of easy to triage bugs where the reporter was unable name a package, [18:15] thekorn: right, the search function is correct, they don't have a package. however, i think it would makes more sense not to list them because they will never have a package, they will be closed whenever they do get a package [18:17] can i just assign them a package with the name of whatever they want packaged? [18:17] but there are also this "needs packaging" workflow bugreports [18:18] no, because this package does not exist in ubuntu, and so it does not exist in launchpad [18:18] unfortunatly it is impossible to exclude this kind of bugs in the searchresults in launchpad [18:20] because there is no "exclude" tags (or similar) option in the search (yet) [18:21] ok [18:22] rule of thumb is: don't touch such workflow bugs unless you know what you are doing [18:23] and this has to be added to this "getting involved" page [18:25] using the same page to show bugs, and according to https://wiki.ubuntu.com/Bugs/HowToTriage/ under the section "Needs Packaging Bugs", there are number of bugs which need to have the wishlist status assigned to them if they aren't already in ubuntu or debian [18:26] for instance, this bug https://bugs.launchpad.net/ubuntu/+bug/263554 needs to be confirmed and set to wishlist importance. [18:26] Ubuntu bug 263554 in ubuntu "[needs-packaging] Kaltura - video editor server for online collaborative editing" [Undecided,New] [18:27] i see that i have permissions to confirm it, so should i confirm it and then let someone else come along and decide the importance? what is the proper course of action to take? [18:28] Normally, you mark it confirmed and then request here it be marked wishlist [18:28] ok [18:29] i have another question, brb [18:30] I marked that bug as wishlist [18:30] * thekorn is wondering if the reporter of this bug is a (spam) bot or something [18:31] Although the license part needs to be corrected. "open source" is a little vague [18:31] thekorn: lol, this is what my next question was going to be [18:31] he filed about 600 bugs, almost all of them seem to be autogenerated needs packaging bugs [18:31] why do people think that will somehow make ubuntu more likely to include the package? [18:32] maybe this is the reason why is account has already been deaktivatid [18:33] That would seem logical [18:34] so what would be the thing to do with this bug? [18:34] Which bug? [18:34] https://bugs.launchpad.net/ubuntu/+bug/263554 [18:34] Ubuntu bug 263554 in ubuntu "[needs-packaging] Kaltura - video editor server for online collaborative editing" [Wishlist,Confirmed] [18:34] As in here and bug-control will mark it as wishlist [18:35] If it looks complete, which it wasn't. It had the license as being "open source". I found the package source and verified it as GPL [18:35] and corrected it [18:35] I think we should talk to the motu guys how they would like to handle this 600 bugs, maybe close them all as invalid by a script [18:36] and ask to reopen it if somebody really wants to have this package in ubuntu [18:37] i also just found the source and it looks to affero gpl v3 === Rafik_ is now known as Rafik === k4v is now known as Guest44667 === Guest44667 is now known as k4v === k4v is now known as m4v_ === m4v_ is now known as m4v === Brownout_ is now known as Brownout [22:26] There isn't any way to get apport to attach its stuff to an existing bug report is there? [22:26] none that I know. Usually just have to use duplicate