[00:11] anyone here? [00:11] hggdh: ? [00:12] hi [00:13] hey [00:15] hey guys [00:15] i have an old bug that appears to be fixed to me [00:15] yay [00:16] i filed it nearly 3 years ago [00:16] lol [00:16] bug id ? [00:16] and we need to mark it as fixed upstream also [00:16] 73650 [00:16] launchpad bug # 73650 [00:16] launchpad bug #73650 [00:16] Launchpad bug 73650 in evolution-data-server "Subscribed Calendars do not adjust events to local time" [Low,Fix released] https://launchpad.net/bugs/73650 [00:16] that's better [00:18] you guys looking at it? [00:18] it *had* to be an e-d-s bug... [00:18] looking [00:18] haha [00:18] sorry [00:19] ehehh [00:19] that's hggdh field of work [00:20] i know [00:20] but he'll be happy to close one... [00:20] hum. I *do* remember a change to the timezones, sometime ago... [00:20] i check it because there was a libical update for jaunty today... [00:20] that's where the problem was... so i revisited the bug [00:20] pace_t_zulu, what version of Evo are you running now? [00:21] it could have been fixed 2 years ago for all i know [00:21] jaunty [00:21] hold on... i will be more specific [00:21] 2.26.1 [00:22] OK. Since then, libical went from being an internal source (a fork of the libical project) to standard libical. It may have been corrected under libical itself. [00:22] I will update upstream, and close it [00:22] hggdh: thanks [00:23] hggdh: how do i get privileges to modify the importance of a bug? [00:24] pace_t_zulu, you have to be experienced on Gnome bugzilla; you are then given some more access, and monitored (yes indeed) for a while [00:24] pace_t_zulu: you became a an ubuntu-bugcontrol member [00:24] oh, darn it, he was talking about LP :-( [00:25] it's ok [00:25] * hggdh was fully into bugzilla [00:25] I though he was... he may not have been [00:25] i know y'all don't give out those kinds of privileges like candy [00:25] i am modifying launchpad bug #371302 [00:25] Launchpad bug 371302 in ubuntu "When I play AVI file, the system crashes immediately " [Undecided,New] https://launchpad.net/bugs/371302 [00:26] marking it incomplete [00:28] hggdh: is that resonable? marking #371302 as incomplete? [00:28] pace_t_zulu, I closed upstream fixed obsolete (the ICS issue) [00:28] looking [00:29] hggdh: thank you for your help [00:30] pace_t_zulu, other questions that come to my demented mind: (1) "system crashes" -- the whole system, or just MoviePlayer? [00:30] (2) can the reporter provide us with the AVI (if it is not copyrighted/restricted access)? [00:30] hggdh: i didn't file it... just trying to help with triage... [00:31] pace_t_zulu, yes, I understand. Just giving you some other things to look for [00:32] hggdh: i added a comment with the questions you raised [00:34] adios Sebastien [00:36] hggdh: thanks for your help [00:38] hggdh: i'd like to resolve all the bugs i've been involved in... (launchpad bug #36189 might be wishful though) [00:38] Launchpad bug 36189 in gnome-panel "Applets do not scale well with changing resolution" [Unknown,Confirmed] https://launchpad.net/bugs/36189 [00:39] pace_t_zulu: that would mean I had to kill 400 bugs! [00:39] * BUGabundo brings out the big squatter [00:40] BUGabundo: my list is considerably shorter... but i guess that is indicative of my limited contribution so far... i want to step it up [00:42] hello all - is Brad Figg in the room? [00:43] Any one else want to advise on this bug -- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/365733 [00:43] Launchpad bug 365733 in linux "Jaunty - Wireless issue causes laptop shutdown to hang indefinitely" [High,Incomplete] [00:44] Brad asked for information that was already provided so I am not sure how to proceed [00:45] pace_t_zulu, with all due respect, the discussion should be carried upstream on 36189 [00:45] hggdh: i have carried it upstream... [00:45] hggdh: they're mum on the issue [00:46] :-) [00:48] that happens. Getting hold of some developers to think on it is not easy sometimes. They may also be busy elsewhere... [00:48] we might as well bump the gnome version, if this still happens on 2.26 [00:48] (it is right now set to 2.7/2.8) [00:49] one thing, though: the bug is in a NEW status, meaning it has been acknowledged as being real in b.g.o [00:53] night [01:08] hggdh: thank you for bumping the gnome version on the "right stick" bug [01:21] welcome, pace_t_zulu [17:47] showard: i saw the link you shared. thanks a lot :) [17:53] hey, is there a desktop application for launchpad which acts as the alternate to the functionality of the browser??? [17:53] did i just ask the question in the wrong channel??? [17:54] i dont know sorry [17:54] but you might want to ask in #launchpad [17:54] bencrisford: thanks... doing just that :) [17:56] ok :) [18:07] cruisemaniac: not really [18:11] bdmurray: thanks [18:11] what happens to that project, umm, I forget the name, which was going to do just that? [18:11] s/happens/happened/ [18:11] leonov [18:11] thats it [18:12] dead? [18:12] maybe comatose? [18:12] probably. [18:12] :) [18:18] \sh said, sometime ago, that he was trying to get back to it [18:34] hi there [18:35] hi [18:35] hi [18:36] what's up with the hug day ? [18:37] i forgot about that! when is it again? [18:38] i think it's today ^^ [18:38] https://wiki.ubuntu.com/UbuntuBugDay/20090514 [18:39] lol! :P i completely forgot [18:49] on the wiki there's hugday init --user LAUNCHPAD_ID --cookie PATH/TO/MOZILLA/COOKIE [18:49] what's the PATH/TO/MOZILLA/COOKIE ? [18:49] something in ~/.mozilla ? [18:52] o0 [19:04] here, at the bottom of the page : https://wiki.ubuntu.com/UbuntuBugDay/Tools [19:10] Strider^: yeah, the cookies.sqlite file inside that directory [19:11] ok thanks [19:11] Strider^: the documentation says that btw :" COOKIE is the cookie.sql or cookie.txt of your mozilla browser profile" [19:11] no problem [19:16] if there are any bug control members around it would be great if you could review my application. im just a bit worried about it being forgotten. Thanks :) [19:16] and another reply should reveal whether I am allowed in or not [19:17] so im a little anxious to know :) [19:18] bencrisford: Don't you worry, it me took a couple of weeks before I got my positive response. People simply have a lot of other things to do as well. [19:19] yeah i guess :) [19:21] soz just changed client [20:13] Anyone knows about bug 349992 ? Will it not be fixed in Jaunty? >:o [20:13] Launchpad bug 349992 in xserver-xorg-video-intel "[i945 tiling] (Needs kernel 2.6.30-rc3) Low performance due to no A17 workaround" [High,Fix released] https://launchpad.net/bugs/349992 [20:16] if it requires the .30 kernel, chances are good it won't make jaunty [20:21] can bug 371720 be set to Medium? It breaks scripts previously working in 8.10 [20:21] Launchpad bug 371720 in tix "_tkinter.TclError: unknown color name "{#c3c3c3}"" [Undecided,Confirmed] https://launchpad.net/bugs/371720 [20:22] (Unfortunately the only fix I know is upgrading tix to 8.4.3 and it won't make it as an SRU probably) [20:22] askand, the linux jaunty task is still open. It is the xorg intel driver that will not be touched, so far [20:23] kklimonda, is there a workaround for this? [20:23] thanks [20:24] hggdh: If there is I don't know it.. simple testcase http://bugs.python.org/file11493/test_combotix.py doesn't even use "#c3c3c3" string so it's something deeper.. [20:25] also no workaround was mentioned in a bug report I've linked to. [20:26] hggdh: also nothing on fedora forum - The solution is to upgrade tix to 8.4.3 [20:27] thanks [20:29] welcome [20:31] hggdh: the fact that bug 367214 is New on package and Fix commited for release means that it isn't fixed on KK yet, right? [20:31] Launchpad bug 367214 in python-django-tagging "utils.calculate_cloud() can leave font_size unset for most frequent tag" [Undecided,Fix committed] https://launchpad.net/bugs/367214 [20:33] can i set it as "in progress" if I've requested package sync? sync will fix it on KK [21:30] hi everyone [21:34] hey bugabundu [21:34] hey bugabundo* [21:34] eheeh [21:34] bencrisford_: don't you know how to use autocomplete on irc? [21:34] just push TAB key [21:35] BUGabundo: Wow! ice :D lol cheers [21:36] kklimonda, looking at it now. Sorry for the delay [21:36] sure [21:36] hggdh: kklimonda: [[]] [21:36] hey [21:36] BUGabundo, [] [] [] [21:36] how are you enjoing your U1 kklimonda? [21:37] kklimonda, the fix has been put available for jaunty-proposed -- this is one of the meanings form 'fix committed' on Ubuntu tasks [21:37] hggdh: yes - i know [21:38] oh [21:38] hggdh: so there is no reason to mark package as "In progress"? [21:38] yes, there is no reason. If the package will be sync-ed for kk, no. [21:38] I thought that two statues mean that the first one, package's is about fix for current development release [21:39] and the second one is about fix for nominated release. [21:39] k, thanks [21:39] yes [21:39] "in progress" is best used when one is actually working on a patch. [21:39] note the *actually* part, please [21:40] persia: I'm working on getting sync done.. poking MOTUs ;) [21:40] kklimonda, Right. THat's a sync, not a patch. [21:41] You might leave a note like "Will be fixed by a sync from Debian (see bug #747737) in a comment, but at that point, you can relax. [21:43] BTW, there should be a workflow request opened for it, kklimonda [21:44] hggdh: can you say something more or point me in the right direction? [21:45] I thought I've followed SRU closely.. [21:46] kklimonda, a sync request should have a description starting with "please sync blahblah from blehbleh", and it is opened as a bug on LP -- but it is *NOT* a bug, it is a workflow request. (there's more) [21:46] hggdh: I'm using requestsync tool [21:47] hggdh: I actually started using it after MOTU advised it instead of doing it by hand.. [21:48] oh, OK. Then all you need is to refer to the sync request on this bug, pretty much as persia said [21:49] and unassign yourself from this one (and we mark it as triaged [21:49] ) [21:50] hggdh: also mark it as Low if you are there already :) [21:50] heh. Will do it now :-) [21:51] And it's generally not best practice to sync for SRU. [21:51] Better to extract the patch, and prepare a special SRU candidate. [21:51] persia: sync is for KK [21:52] Oh, OK. That's fine then. [21:53] kklimonda, now the only thing that we need is a reference to the sync request, so that we can find this, and close it, when the sync is accepted & done [21:54] (or make sure that the changelog for kk will have the (LP #xxxxx) entry) [21:54] hggdh: it will need both? [21:54] i.e. one for sync request and second for this bug? [21:55] hggdh: as it's a sync we don't modify it in any way - I'll mark this bug as fix released (?) when sync is complete. [21:56] Sometimes the Debian uploads have the (LP: #nnn) magic, and it just works, but this isn't so often. [21:56] kklimonda, no, the sync reference is enough === yofel_ is now known as yofel [23:55] ogasawara: can this be a kernel bug you think? --> https://bugs.launchpad.net/ubuntu/+source/xfree86-driver-synaptics/+bug/374459 [23:55] Launchpad bug 374459 in xfree86-driver-synaptics "touchpad can be switched off, but not on again" [Undecided,Confirmed] [23:55] ogasawara: the reason why i'm suspect this is because "modprobe -r psmouse; modprobe psmouse" makes the touchpad work again [23:57] mnemo: I'd seen a similar kernel bug that the touchpad was disabled after suspend/resume and you'd have to reload the psmouse module to restore it [23:58] actually this is the opposite [23:58] taking it to S3 and back makes the touchpad work again [23:58] and it breaks just by itself after its been used a while [23:58] interesting [23:58] so I think the S3 wakeup triggers some kernel code that sort of "re initializes" it [23:59] thats why I asked if that modprobe command fixes it as well