[00:11] Turl1 asked me a question: "can I start getting packages sponsored now? or should I wait more?" what do you guys have to say? [00:15] BUGabundo, I think it is OK no [00:15] w [00:17] its a dead upstream app, but with some recent new version (go figure) [00:17] but we have the same version since dapper [00:17] my advise is to update debian 1st [00:17] and then just sync [00:17] it would be better, yes [00:18] is it in universe? [00:18] and if it is dead upstream, who updated it? [00:19] universe, yes [00:20] hggdh: the user is not sure, thinks it was main devs, but not as active as before [00:20] hum. Better to ask at -motu, then [00:20] my advice too [00:20] eheh [00:21] :-) [00:40] hggdh: can I say something is officially supported if it's in a future release? [00:41] anyone else? [00:42] micahg: I would [00:42] depends on the case [00:42] something like this: The moonlight plugin is officially supported in Jaunty in version 1.0.1. [00:42] bug 374521 [00:42] Launchpad bug 374521 in firefox-3.0 "Moonlight crash" [Undecided,New] https://launchpad.net/bugs/374521 [00:43] user is running intrepid [00:44] BUGabundo: ?? [00:45] it wasn't supported on ii? [00:45] Nope [00:45] not as a plugin afaict [00:46] then we can't support it oficially [00:46] only by community, if any one backports it [00:47] ok [00:47] That's what I wrote then [00:47] I'll be back later [00:47] wanted to get in a quick bug [00:47] :) [00:48] eheh [00:58] bedtime [00:59] micahg, sorry. But yes, if the plugin was only added in in Jaunty, and the user has a crash in Intreprid, then there is no question it is unsupported (and, as such, closed invalid). [02:22] hi, same one speak spanish? [02:25] some one know how to connect a w380i sony ericsson cell phone to ubuntu (64b machine)? [02:33] !es [02:33] En la mayoría de canales Ubuntu se comunica en inglés. Para ayuda en Español, por favor entre en los canales #ubuntu-es o #kubuntu-es. [02:33] oops, guess he's gone ;) === stpere is now known as stpere|zzz [03:02] my Evo just decided it had worked hard for too long, and froze :-( [03:19] hello hggdh [03:20] just sitting down to look at LP bug # 301007 [03:20] hi pace_t_zulu [03:20] LP bug #301007 [03:20] Launchpad bug 301007 in matplotlib "python-matplotlib: missing package dependency (python-tk)" [Undecided,Confirmed] https://launchpad.net/bugs/301007 [03:20] that's better [03:20] hggdh: i was testing ubot4 [03:22] so it is still working ;-) [04:35] !arch [04:35] Factoid 'arch' not found [05:17] bug 374710 [05:17] Launchpad bug 374710 in ubuntu "Windows containing "tran" in the titlebar crash" [Undecided,New] https://launchpad.net/bugs/374710 [05:17] ?? [05:21] anyone can repeat this? [05:23] hggdh: Works for me (I have the current dir in the window title, so I did mkdir tran && cd tran and nothing bad happened). [05:24] Just rechecked with trans, still "works for me". [05:24] wfm also for me... [05:25] jmarsden, you have to try with 'trans', not 'tran' [05:25] tried both ways... both are OK. [05:25] yeah. This one takes the cake for a weird bug [05:26] well, I will update the bug, and ask for more data. Let's see what happens [05:27] Sounds like he may have a proxy or something running trying to do on the fly translation??? [05:31] hggdh: what do I answer the guy in bug 254139? [05:31] Launchpad bug 254139 in firefox-3.0 "huge text displayed on certain web pages" [Undecided,Incomplete] https://launchpad.net/bugs/254139 [05:33] micahg, looking at it now [05:36] micahg, I would say "fix released", unknown fix. You might look at the changelog for ffox 3.0.10, and see if any entry there would match, or approach, this issue [05:37] well, user started with 3.0.1 [05:37] so, that's a lot of changelogs [05:37] jmarsden, I thought of something like that, but the reporter also states being able to trigger with *any* other programme that sets the window title. I still think this is very weird... [05:38] I agree... I wonder if the thing looking for trans is in his closed source video driver or something??? [05:38] micahg, then I would say don't worry ;-) but the changelog is cummulative [05:39] micahg: Say you don't know, but you are glad the issue seems to have been resolved :) [05:40] jmarsden, the *only* way I can see this happening is via a common programme/library/whatever... I asked the reporter to reproduce with apport enabled. If we get the new apport-generated bug, then we can look at the backtrace (hopefully it will be complete) [05:42] Yep. Definitely a bug to remember, if this does end up being replicable :) [05:46] hum. the data for the X sounds strange... built with a 2.6.24 kernel, and Jaunty released with a 2.6.28 one... [05:48] ah well. Je me sens un peu faible... [05:48] hggdh: means user started with Hardy and upgraded [05:48] user is using a 2.6.28 kernelkl [05:48] Current Operating System: Linux cerberus 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 [05:49] yes, but I would have expected X to have been built with an equivalent kernel (since otherwise we might have dependencies issues on the builder) [05:50] current Jaunty is X 1.6 [05:51] look like user us running Jaunty [05:51] yes. Which, still, makes the reference to 2.6.24 unexplained. Unless this is the date for the nvidia driver, and the reporter downloaded it from nvidia [05:52] ah [05:52] I see what you're saying [05:52] sorry [05:52] I"ve never seen X output like that before [05:52] no prob, micahg [05:53] and I am not an X expert (always hated the thing, since the first time I saw it, a long time ago ;-) [05:54] * pace_t_zulu hggdh: the reporter says " [05:54] * pace_t_zulu Nvidia Quadro FX 540 PCI-E 16x [05:54] * pace_t_zulu I am using the nvidia proprietary 180 driver" [05:54] so it is proprietary [05:54] yes. Downloaded from us, or from nvidia? Both are proprietary... [05:55] hggdh: does it matter doesn't Ubuntu get the binaries from nvidia? [05:56] hggdh: it would really just matter for package management... right? [05:56] pace_t_zulu, I *think* so, but I do not have nvidia (I have ATI), and I use the radeon driver, which is free [05:56] hggdh: if he got the binary from nvidia than it would not be automatically updated by apt [05:57] i would think [05:57] pace_t_zulu, I think you are correct -- to a point: ATI and nvidia may release up-to-date drivers, that may (or may not) be incompatible with a specific ubuntu release [05:57] hggdh: if he got the binary from Ubuntu repos then it would be updated [05:57] yes [05:57] hggdh: i am all to familiar with this problem [05:57] back in the early days of compiz [05:58] please ignore this [05:58] please ignore this @bugtracker add malone malone https://launchpad.net/malone Malone [05:58] apt-cache policy nvidia-glx-180 is the easiest way to find out [05:58] yes, so was I -- I used fglrx at the time, eventually got fed up with having a tainted kernel, and went 2D-only with radeon [05:58] https://bugs.launchpad.net/ubuntu/+bug/373557 srry last time [05:58] Launchpad bug 373557 in ubuntu "Sync libwww-delicious-ruby 0.3.0-1 (universe) from Debian unstable (main)." [Undecided,New] [05:59] hggdh: i run ubuntu in vmware these days... so i am 2d only also [05:59] hey binarymutant [05:59] there is a nvidia-glx-180 in the repositories [05:59] guys, binarymutant is trying to setup ubotu in #ubuntu-us-tn [05:59] hey pace_t_zulu still trying ubotu [05:59] that's why he is testing it in here [06:00] binarymutant: keep up the good work [06:00] what is the issue with the bot? [06:00] ah [06:00] hggdh: if he is a Quadro user, he is probably quiet dependent on 3d (or likes burning money) [06:00] should have read the backlog [06:00] heh [06:01] hggdh: what backlog? [06:01] !backlog [06:01] Factoid 'backlog' not found [06:01] the channel log [06:01] hggdh: where do you find that? [06:01] I am lost. Find what? [06:02] hggdh: where can you get a backlog for any given #ubuntu channel on freenode? [06:02] ah [06:02] !logs [06:02] Official channel logs can be found at http://irclogs.ubuntu.com/ - For LoCo channels, http://logs.ubuntu-eu.org/freenode/ [06:03] it is saved at... (hold on) [06:03] darn! again! [06:04] hggdh: thank you [06:04] no, Flannel did it. [06:05] Flannel: thank you [06:06] this is it, folks. Good night. [06:06] night [06:18] night hggdh [06:21] night guys... [06:54] good morning [08:05] good morning === simono is now known as _simono_ [13:34] hi, i have had an issue with resuming after hibernate and i would like to search in launchpad if other people had this problem before [13:34] but neither the error message (an unknown error has occured, code 1) nor syslog is very helpfull [13:35] quite a few people have had problems with various things after hibernate, but if your more specific searches aren't throwing up matches I'd go ahead and raise a new bug, it can always be merged later if it is a duplicate [13:35] so, can you tell me where i can look up a more precise error log to post it to launchpad? [13:36] ah, ok [13:36] what sort of error does Xorg.log give you? [13:38] you could try installing the xorg-server dbg package and running it through gdb to get a full backtrace if it's an Xorg crash [13:38] what is the "issue" you're having with? [13:39] i have done a hibernate, tried to resume, but the notebook turn immediately of, back to suspend to ram [13:39] from there i could do the resume [13:39] but not directly from hibernation [13:40] and it seems as i can recreate this process, because i had this also before [13:42] d [13:44] i can't find any problems within Xorg.0.log [13:50] can i check any other log files? === asac_ is now known as asac === stpere|zzz is now known as stpere === seb128_ is now known as seb128 [15:11] Boo [16:08] hi everyone [16:09] hi hggdh [16:25] hi G__81 [16:32] i saw your mail and i have gone through the triaging process :) [16:32] the flowchart is wonderful [16:33] but in the incomplete flowchart flow some flows are marked in grey what does that indicate [16:35] g_81, can you give me the link? [16:36] https://wiki.ubuntu.com/Bugs/HowToTriage/Charts [16:38] G__81, the grey mark the status of a bug [16:38] no [16:39] my doubt is [16:39] in the From Incomplete flow chart when it transitions from Incomplete you see the next boxes are marked light [16:40] oh.............. got it [16:40] i didnt see it i got it cleared [16:40] :) sorry [16:40] G__81, although it is a bit of a stretch, if it is incomplete it is already considered a bug [16:40] yes [16:40] :) [16:41] so the "convert to answers" flow would not apply [16:41] yes [16:41] just installed 9.04 in VBox [16:41] good [16:41] now am gonna move that 9.10 [16:42] G__81, if you have enough disk, you might want to save this 9.04, and copy the VM image [16:42] not a problem i could install it again :) [16:43] :-) [16:43] thats the advantage of ubuntu when compared to fedora it gets installed fast :) [16:43] heh. There *had* to be something better somewhere ;-) [16:43] i ve been using Red hat right from 5.1 to Fedora 10 and i see the difference when i switched to Ubuntu [16:43] i respect Fedora but i feel this is one thing of the so many things i like about Ubuntu [16:44] hey hggdh can you give me the link for the list of bugs so that i could start my triaging process ? [16:44] it is all linux... a distribution is (or should be) mostly a personal decision. All of the major dists are good [16:45] yes [16:46] https://bugs.edge.launchpad.net/ubuntu [16:46] all the bugs at your disposal === ecanto is now known as edson [16:48] hggdh, i have a question [16:48] https://bugs.edge.launchpad.net/bugs/374733 [16:48] Launchpad bug 374733 in swami "Swami needs updating to latest SVN." [Critical,New] [16:49] how do you classify this bug. I dont see this as a bug [16:49] it is not... hold on [16:49] looks more or less like a wishlist or enhancement :) [16:50] see https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs [16:51] it is a workflow "bug". Note that the reporter is also the assignee. This is a bit of a excess, even for workflow, but I believe Luke wanted to have it recorded, and indeed LP is a very good place [16:52] workflow bugs are not to be touched on triage, so please do not worry about this one [16:52] yes [16:52] i saw that link thanks for the link [16:52] welcome [16:54] let me triage one and let me know your comments [16:57] hggdh, #163544 [16:58] bug 163544 [16:58] Launchpad bug 163544 in tracker "tracker search tool shows no results" [High,Confirmed] https://launchpad.net/bugs/163544 [16:59] thats what i ve triaged [17:00] G__81, hold on, this is an old (and long) bug [17:01] yes but it still exists in 9.04 [17:02] and thats why i triaged it [17:05] G__81, good. Some points: (1) if you look at https://wiki.ubuntu.com/Bugs/Description, you will see some guidelines. The ones I am thinking about, right now, is "Lastest Package Tested". and "Next Step". [17:05] :) so am i right ? [17:05] For Latest Package Tested"... it is the Jaunty version of tracker [17:05] G__81, yes, you are this *IS* a bug, no doubt [17:06] :) [17:06] just 3 more minutes for the 9.10 to get installed completely [17:06] for "Next Step"... a bit more complex. Ideally we would go upstream and either find an existing bug there, or open a new one. [17:07] So, right now, Next Step could say something like "needs upstream task" [17:08] The point is I had to read all the bug to find out it is still a bug, and still present in Jaunty... [17:08] so how do i rectify it [17:08] yes you are right you have to go through the entire stuff to find out its 9.04 bug [17:08] just edit the description, and add the fields [17:09] (click on the "Update description/tags") [17:09] ok then ? [17:09] and add what ? [17:10] well, you can go upstream on tracker, and look for a similar bug... [17:11] how do i ? go to gnome bugzilla ? [17:11] right now I tend to consider this bug a wishlist -- the code to do what should be done seems not to be there yet [17:12] yes, b.g.o [17:13] oops [17:13] not sure [17:13] ok currently let me leave it like this then :) [17:13] k [17:15] if the fix has been released then what do we do [17:16] if upstream has fixed it, but Ubuntu is still running an older version, then the Ubuntu task stands [17:16] if upstream has a bug opened (and closed fixed resolved), then we add an upstream task to the bug. LP will update the status to closed automatically [17:17] so what do i put there ? its in new state [17:17] (but the Ubuntu bug will still be confirmed) [17:17] the upstream bug? [17:17] #186713 [17:17] 186713 [17:18] G__81, prefix with "gnome bug " is in b.g.o, "bug " if in LP, etc, etc [17:18] gnome bug 186713 [17:18] eeeck [17:18] yeah the developer says he has fixed it but what would be the status in LP [17:19] bug 186713 [17:19] Launchpad bug 186713 in keytouch "[hardy] keytouch blocks logout" [Unknown,Fix released] https://launchpad.net/bugs/186713 [17:19] G__81, where is this bug [17:19] where ? i didnt get you sorry [17:19] ah, I see my mistake [17:20] G__81, note that the *upstream* bug has been fixed [17:20] yes [17:20] not the Ubuntu one [17:20] yes [17:20] so can i mark it confirmed [17:20] coz in ubuntu its still open [17:20] as ubuntu has not merged it [17:20] into its repo [17:21] hold on, reading through it ;-) [17:21] :) [17:25] it seems the last one to touch it incorrectly reopened it. It was already fix released [17:25] https://bugs.edge.launchpad.net/ubuntu/+source/keytouch/+bug/186713/+activity [17:25] Launchpad bug 186713 in keytouch "[hardy] keytouch blocks logout" [Unknown,Fix released] [17:26] so can i close it then ? [17:26] so you can just put it back as fix released, and add a comment stating you did it because there was no explanation given for reopening it [17:26] yes, you should [17:26] be back in a few === Igorot is now known as Knightlust [18:04] can someone confirm bug 374106? For example using bug 375000 [18:04] Launchpad bug 374106 in launchpad "ubuntu-universe-sponsors subscribed but don't show under Subscribers" [Undecided,New] https://launchpad.net/bugs/374106 [18:04] Launchpad bug 375000 in transmission "Please merge transmission 1.60-2 from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/375000 [18:07] kklimonda: I can see it [18:07] kklimonda: can you confirm that they are present in the source? [18:07] james_w: hmm? [18:08] kklimonda: check the HTML source of the page [18:08] oh [18:08] you should be able to see them there [18:08] if so, then working out what is hiding them would help [18:11] james_w: actually I get different html source for edge and for stable LP.. [18:11] sure [18:12] does it differ in the list of subscribers though? [18:13] james_w: nah - they are in both [18:13] ok [18:13] are you able to work out why they are hidden on edge? [18:15] nothing in source look suspicious.. i'll try disabling all extensions and see if it helps.. if not i'll use webdeveloper to check it.. [18:17] running firefox in -safe-mode helped so now I only have to check which extension is blocking it.. ;) [18:18] looks like adblock is blocking it o.O [18:19] easylist contains rule: ##*[id$="sponsors"] [18:20] I'm marking this as invalid.. [18:20] hmm.. or maybe i should leave it? "some" people use adblock and may encounter this problem [18:21] ok hggdh i got to go now thanks for your help and i ve triaged some today and will do more tomorrow and my aim is to get upto speed and start fixing bugs and hence have installed 9.10 too [18:24] G__81, thank you for your help [18:24] my pleasure and i hope you my application gets accepted some day ;-) [18:26] it will, G__81, it will. It was just that you had no experience to show with Ubuntu... [18:27] thanks 9.10 does not boot in VM [18:27] it just waits in Starting HALD [18:27] the app-armour did not start === micahg1 is now known as micahg [19:52] how to add link to debian bts in lp bug? [19:53] kklimonda: also affects distribution -> select debian from list [19:54] kklimonda: or find the URL to debain BTS and then click "also affects distro" and paste BTS URL there [19:54] thanks === simono is now known as _simono_ [20:05] hmm.. what to do with bug 375062 ? [20:05] Launchpad bug 375062 in transmission "Transmission downloads data multiple times" [Undecided,New] https://launchpad.net/bugs/375062 [20:05] reporter is saying that it was fixed in newer debian version [20:05] right now I'm mergin 1.60-2 from debian but this report is for 8.10 [20:06] should I mark it as fixed in package's changelog ? [20:06] (also we don't know when was it fixed but it's another issue) [20:08] there is also bug 359268 which doesn't sound like bug to me - pressing enter will select quit and shouldn't space work for selecting options? Maybe i should check it in gnome hig? [20:08] Launchpad bug 359268 in transmission "Focus should not be on "Don't ask me again" when I quit Transmission" [Undecided,New] https://launchpad.net/bugs/359268 [20:13] btw, what should I do about bugs that were fixed earlier like bug 191496 ? ;) [20:13] Launchpad bug 191496 in transmission "Finished torrent with not all files downloaded" [Undecided,New] https://launchpad.net/bugs/191496 [20:13] (damn, I'm spamming this channel..) [20:34] kklimonda, on the transmission bug -- can you check on Jaunty? [20:34] which one? [20:34] :) [20:35] (they are all transmission :) ) [20:35] heh. Sorry... 359268 [20:35] it you can confirm it, it is a wishlist, and will have to be upstreamed [20:36] i can confirm it in both 1.51 and 1.60 so it wasn't fixed [20:36] cool. So it is confirmed, and we need to look upstream (and open a bug if needed)... [20:36] so even if I'm not sure if it's a bug I should send it upstream? [20:37] it's a wish then? :) [20:37] well, it is -- at least -- a wish. It does sound plausible that the default action should be selected [20:38] well, you can select quit with enter key. [20:38] that's why I'm wondering if it isn't in some kind of HIG [20:38] it might well be. It does sound like one [20:40] for the second one, if 1.51 (or 1.52) are currently available on Jaunty, then it is fixed on the new release (so fix released) [20:45] kkilmonda - bug 375062 is a duplicate of an already fixed bug [20:45] Launchpad bug 375062 in transmission "Transmission downloads data multiple times" [Undecided,New] https://launchpad.net/bugs/375062 [20:45] **kkilmonda ^^ [20:46] kklimonda^^ [20:46] i'll spell your name right eventually;) [20:46] :} [20:46] chrisccoulson: i've found 5 or 6 bugs that are fixed in 1.60 [20:47] chrisccoulson: you can use to autocomplete nicks - it's way easier than spelling most of them ;) [20:47] kklimonda - bug 375062 was fixed in 1.51 in jaunty, and the bug on LP was closed. users of earlier versions will still exhibit the issue though [20:47] Launchpad bug 375062 in transmission "Transmission downloads data multiple times" [Undecided,New] https://launchpad.net/bugs/375062 [20:47] kneat [20:47] neat** [20:47] lol [20:49] chrisccoulson: bug 318186 was also fixed. Why aren't they closed for transmission (source)? [20:49] Launchpad bug 318186 in transmission "Transmission fails to start" [Unknown,Fix released] https://launchpad.net/bugs/318186 [20:49] kklimonda - bug 375062 is a duplicate of bug 295040 [20:49] Launchpad bug 375062 in transmission "Transmission downloads data multiple times" [Undecided,New] https://launchpad.net/bugs/375062 [20:49] Launchpad bug 295040 in transmission "multiple download works strangely" [High,Fix released] https://launchpad.net/bugs/295040 [20:49] feel free to mark it as such:) [20:51] kklimonda - bug 318186 was never closed because no reference was added to the changelog entry of the upload which fixed it [20:51] Launchpad bug 318186 in transmission "Transmission fails to start" [Unknown,Fix released] https://launchpad.net/bugs/318186 [20:51] the upstream ticket suggests it was fixed in 1.5x, so it should now be closed as fixed as jaunty has this version [20:52] no wonder you were asking for those LP bug numbers in changelog ;) [20:54] it makes life much easier. for gnome stuff it is common to change the ubuntu task to "fix committed" when a bug is fixed upstream, as gnome updates come quite frequently. the next person to update the package can then search for the bugs that are fix committed and add these to the changelog [20:54] although i don't think all teams agree with that [21:02] is it worth effort reporting bug 364644 (and similar) to upstream? [21:02] Launchpad bug 364644 in transmission "transmission crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()" [Medium,New] https://launchpad.net/bugs/364644 [21:03] there is a full traceback with symbols [21:05] if there is a good backtrace, then yes [21:06] i would probably ask the reporter to provide a valgrind log first though. [21:17] hello === erhesrhsrtb54vyh is now known as Elbrus [21:20] Hi, if one use a rule to move mails from a certain contact into a certain folder (under the inbox) you won't get notifications about new mail, anyone know if that is a known bug? [21:21] In what mail client? [21:21] Evolution [21:21] * Hellow does not use Evolution [21:23] But this would perhaps be a bug in evolution? [21:28] askand1, depends on what is it you use for email notifications from evolution [21:28] hggdh: I use whatever is on a default Jaunty installation, notify-OSD I guess [21:29] on notify-osd I am not sure. While I was using the evo plugin, I would receive a notification, though [21:29] and I have a LOT of rules on Evo [21:30] I usually have notification disabled nowadays, and keep myself pretty much on the Unread search folder [21:32] I wonder if this is some error with my account, there mails to a certain mailadress (that I move to a certain folder) that does not give notifications [21:34] chrisccoulson: thanks for help :) [21:34] you're welcome:) [21:35] guud evening [21:35] askand1, it might well be, a good test is to go back to the Evo standard plugin, and try there [21:35] hey BUGabundo :) [21:35] gold evening BUGabundo [21:36] hey kklimonda hggdh [21:36] hggdh: its more rainy then golden [21:36] so is it here, so is it here... [21:36] hggdh: how would I do that? [21:37] hggdh: lots of Sun last week, rain since yesterday :( [21:37] askand1, Edit/Plugin/Mail Notification, select the configuration tab [21:37] BUGabundo, it has been raining here (not continuously) since my wife went to Belgium [21:37] hggdh: so far so good, then? [21:38] AH [21:38] askand1, first one [21:38] stupid me [21:38] oh I notice you already found it ;-) [21:38] :) [21:38] good. Try it now, with no other changes [21:39] brb [21:39] hggdh: Yes, now I get a sound but no notification (so it's a notify-osf problem I guess) [21:40] askand1, not sure if notify-osd. Hold on [21:41] some one put me to speed... what the discussion about? [21:41] askand1, I would consider first evolution-indicator notify-osd is the framework [21:42] BUGabundo, askand1 had a problem where Evo email filtered to other mailboxes did not trigger notify-osd [21:42]