[02:55] <stlsaint> vish: ping
[07:21] <vish> stlsaint: pong
[07:44] <stlsaint> vish: my membership on lp is about to expire
[07:45] <vish> stlsaint: hmm, who was your mentor?
[07:57] <vish> stlsaint: ?
[08:32] <stlsaint> vish: oh sorry, drew is
[16:40] <abudawud> can someone set https://bugs.launchpad.net/ubuntu/+source/openmovieeditor/+bug/682151 to triaged?
[16:40] <ubot2> Launchpad bug 682151 in openmovieeditor (Ubuntu) (and 1 other project) "typo in software center summary for open movie editor (affects: 1) (heat: 6)" [Undecided,Confirmed]
[16:42] <vish> abudawud: it needs to be sent to Debian, then we can set it to triaged
[16:45] <abudawud> vish, can you explain to me why a typo in 'Ubuntu Software Center' needs to go to Debian please? :)
[16:45] <devildante> abudawud: the descriptions and summaries come from Debian
[16:46] <vish> abudawud: that package is autosynced from debian right now, as well..
[16:46] <abudawud> devildante,  thanks I was unaware
[16:46] <devildante> abudawud: np ;)
[16:46] <yofel> and they're part of the package, and have nothing to do with software center, it just displays them
[16:46] <abudawud> yofel, I figured that part, but I figured we managed the descriptions
[16:46] <abudawud> guess thats what I get for figgerin
[16:47] <yofel> abudawud: no, you can see the descriptions too with 'apt-cache show <pkg>', they're in the packages control file
[16:47] <devildante> vish: so any papercut bug ready to be worked on needs to be assigned to papercuts-ninja?
[16:48] <vish> devildante: yea, we are assigning a few everyday.. just to not flood the list with too many bugs at one time. ;)
[16:48] <devildante> heh, thanks vish :)
[16:48] <vish> devildante: but you can pick anyone you want, assigned or not ;)
[16:49] <devildante> I know that ;)
[16:49] <vish> devildante: oh you wanted to assign bugs? sure.. feel free to :)
[16:49] <devildante> vish: no, I don't want to
[16:49] <devildante> vish: but all these assignements make me want to fix all these bugs :p
[16:50] <vish> devildante: FIX it!!!
[16:50] <vish> :D
[16:50] <abudawud> vish, what should that be assigned to? Just Debian as a whole or do they have a certain place for typos in the repo list?
[16:51] <devildante> vish: lol
[16:51] <vish> abudawud: nah, not assigned, we need to send them a mail.. its simple, have a look at : https://wiki.ubuntu.com/Debian/Bugs
[16:52] <devildante> abudawud: reportbug is your friend ;)
[16:52] <abudawud> vish, yea the 'assigned' was a misnomer from reading your conversation with devildante  oops :P
[16:52] <vish> :)
[16:52] <devildante> :)
[16:55] <vish> yofel: i wanted to ask about Bug #391626 , all it needs is forwarding?
[16:55] <ubot2> Launchpad bug 391626 in hundredpapercuts "Changing file associations in KDE is hard (affects: 2) (heat: 3)" [Undecided,Confirmed] https://launchpad.net/bugs/391626
[16:55] <abudawud> derp *** ERROR: "Ubuntu" BTS is currently unsupported.
[16:55] <abudawud> reportbug doesnt seem to work in 10.10
[16:56] <abudawud> nevermind
[16:56] <abudawud> I'm not reading as I go apparently
[16:59] <vish> devildante: regarding the help bug, just poke mpt on irc monday, if we are waiting for a reply on the bug, it might take longer for him to read mails ;)
[16:59] <devildante> vish: okay, thanks for the tip :)
[17:01] <yofel> vish: yes, forwarding should be enough
[17:02] <vish> yofel: could you? :)  i dont even have a kde bugzilla account or test machine :)
[17:03] <vish> yofel: seele seems interested, i wonder why she hadnt forwarded it still..
[17:04] <yofel> vish: bit busy currently, but I'll have time to do it later, completely forgot about that one...
[17:05] <vish> yofel: cool,thanks. later is fine..
[17:15] <abudawud> hey vish or devildante, once the debian bug is reported and linked should the ubuntu and papercut bugs be marked as invalid?
[17:15] <devildante> no
[17:16] <vish> abudawud: we can mark it triaged.
[17:16] <vish> abudawud: you have now done most of the major work for that bug, if can just submit a patch as well in debian, the bug is done ;)
[17:17] <abudawud> vish, want to push me in the right direction by telling me what package contains the information to patch :P
[17:19] <vish> abudawud: https://wiki.ubuntu.com/Bugs/HowToFix and the package is  openmovieeditor
[17:21] <vish> abudawud: see the Generating a patch section? its written with a typo example..
[17:21] <vish> abudawud: but remember to send it to debian..
[17:27] <abudawud> vish, can you set it to triaged for me? https://bugs.launchpad.net/debian/+bug/682151
[17:27] <ubot2> Launchpad bug 682151 in debian (and 2 other projects) "typo in software center summary for open movie editor (affects: 1) (heat: 6)" [Unknown,Unknown]
[17:27] <abudawud> and low priority ;)
[17:29] <vish> abudawud: when adding the debian task , we should use the "also affects distribution"
[17:29] <vish> ah you dint add the package!
[17:30] <vish> abudawud: i'm confused.. which option did you use?  the project or distro?
[17:31] <abudawud> vish, sorry what? for the debian bug?
[17:31] <vish> yea
[17:31] <abudawud> I don't remember it asking honestly
[17:31] <vish> np.. :) the distro task should have auto-completed the package hence was wondering..
[17:32] <vish> abudawud: you can add it now yourself, just click the down arrow, and you will find the package entry field
[17:32] <vish> next to "Debian"
[17:33] <abudawud> done
[17:35] <vish> abudawud: done.. ;)
[17:35] <vish> abudawud: you are also working on the patch, right?
[17:36] <abudawud> yea, and I just found out that it doesn't mention that typo anywhere in the source package
[17:36] <vish> abudawud: you can set the papercuts task as 'In progress' then
[17:36] <vish> abudawud: set the .desktop file
[17:36] <vish> see*
[17:36] <vish> the summary is often from there
[17:36] <abudawud> should have shown up with a find ./ | xargs grep "typo" though right?
[17:37] <vish> grep "typo"??
[17:37] <abudawud> with the typo there
[17:38] <abudawud> find ./  |  xargs grep "simple non-linear video edito"
[17:39] <vish> abudawud: not sure why it does not grep..  but try looking at the .desktop, it would be the Comment in the .desktop which has the typo..
[17:39] <devildante> abudawud: just search in the .desktop file and debian/control, the summary is retrieved from one of these files
[17:40] <abudawud> well thats ridiculous
[17:40] <abudawud> wonder why it didnt grep out
[17:40] <abudawud> ah nvm... the = is right on the first word
[17:58] <abudawud> can anyone inform me how to edit a bug in the debian tracking system to change the package name? :)
[18:01] <crimsun> abudawud: http://www.debian.org/Bugs/server-control#retitle
[18:01] <crimsun> argh, sorry
[18:01] <crimsun> http://www.debian.org/Bugs/server-control#affects   <---
[18:07] <abudawud> thanks crimsun
[18:08] <crimsun> np.
[18:58] <devildante> vish: here?
[19:01] <vish> devildante: yo!
[19:02] <devildante> vish: I just submitted a patch upstream for a papercut bug that is assigned to papercuts-ninja ; should I re-assign it to myself?
[19:02] <vish> devildante: yup.
[19:03] <vish> devildante: and set it as In progress too
[19:03] <devildante> yessir
[19:05] <devildante> vish: done, thanks for helping :)
[19:05] <vish> np..
[19:06] <devildante> what just happened here? a bunch of people got read, write, and ping timeout errors at the same time :p
[19:19] <abudawud> If I submitted a patch to the archaic bug tracker, should I submit the patch to launchpad as well or just let the debian bug run its course?
[19:20] <abudawud> archaic debian bug tracker**
[19:26] <abudawud> vish, the patch is committed in the debian bug, what should I do with the 100 papercuts bug?
[19:27] <devildante> abudawud: mark it as in progress and assign yourself
[19:28] <abudawud> devildante, and just sit on it? Don't upload the patch to lp?
[19:28] <devildante> abudawud: no, debian will handle it
[21:16] <tomkCZ> hi!
[21:16] <tomkCZ> I need a help with a bug ;)
[21:23] <penguin42> which bug?
[21:24] <tomkCZ> evolution+echange in maverick
[21:24] <tomkCZ> https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/631395?comments=all.
[21:24] <ubot2> Launchpad bug 631395 in evolution-exchange (Ubuntu Maverick) (and 2 other projects) "When upgrading from 10.04 to 10.10, exchange mail accounts no longer work in Evolution. When clicking the account, the folder structure won't expand and the account does not send or receive e-mail (although) it does appear in the send/receive dialog box. (affects: 75) (dups: 8) (heat: 467)" [High,Triaged]
[21:25] <tomkCZ> it's just not working on maverick
[21:25] <tomkCZ> need some backport of the newest version from natty
[21:25] <penguin42> Sorry, I don't know much about either exchange or evolution
[21:26] <tomkCZ> I see, just trying
[21:26] <tomkCZ> it cannot be fixed by some amateur workaround, people responsible should come with working version ;)
[21:27] <penguin42> tomkCZ: It looks like it was fixed a few days ago in Gnome upstream
[21:28] <tomkCZ> it was several times penguin42 and it still is crappy
[21:28] <tomkCZ> it needs newest version 2.32 which was supposed to come with gnome 2.32 ....
[21:29] <tomkCZ> evolution 2.30 is beyond saving, at least it seems ...
[21:29] <penguin42> tomkCZ: From the stuff on that bug it looks like the fix was newer than that
[21:31] <penguin42> tomkCZ: since it's only just got fixed upstream I guess it will take some time to trickle down; now I don't know what the Ubuntu policy on it is - the bug is marked as High so I guess there is a chance the maintainers might take the upstream fix
[21:31] <tomkCZ> a fix for this particular bug was released like twice really fixing the folders expanding, breaking stability, refreshing folder, closing folders .......crash, crash,crash
[21:31] <penguin42> tomkCZ: Hey some bugs are hard to fix!
[21:33] <tomkCZ> I understand that, on the other hand releasing major email client in major distro without possibility to fetch emails is also let's say hardcore !
[21:33] <penguin42> tomkCZ: Just because the bug affects a lot of people doesn't mean it's easier to fix
[21:35] <penguin42> tomkCZ: If I'm reading the upstream bug correctly it's saying there is something in the maverick-proposed repository - have you tried it?
[21:35] <tomkCZ> you probably right, the question is if it is a priority, more precisely if someone was working on that - which didn't seem from the bug log
[21:36] <tomkCZ> I tried two different updates of evolution files, not sure about this last one
[21:36] <penguin42> tomkCZ: Try enabling maverick-proposed and if it has an evolution update see if that fixes it; if it does then comment on the bug to say that it fixes it
[21:37] <tomkCZ> in proposed it is the same version it is going to be released for updates ?
[21:37] <penguin42> tomkCZ: That depends whether people find the versionin proposed helps or makes things worse
[21:38] <tomkCZ> I used proposed a while ago for some ssh stuff and it got inconsistent with standart updates then
[21:38] <tomkCZ> but I do have testing version of maverick so I'll try it
[21:38] <tomkCZ> you see,  still on lucid - cannot move there without emails working
[21:39] <penguin42> tomkCZ: They tend to be pretty careful about doing updates; even though it's broken for a major case a fix could make it break it for more people, so they'll want to test a lot
[21:41] <tomkCZ> ok, if you say so, I am little sceptic about regres testing if they let it released in the first place ;)
[21:42] <tomkCZ> I like ubuntu, but some recent events make it harder nad harder
[21:45] <penguin42> tomkCZ: I don't think that much testing of individual apps takes place
[21:46] <tomkCZ> but application like evolution is crucial, usual folks don't care about tuned kernel
[21:47] <penguin42> tomkCZ: I don't use evolution, but my guess is that it was tried on imap or pop but not on exchange perhaps
[21:47] <tomkCZ> and yet ubuntu wants to step further to commercial ;)
[21:47] <penguin42> tomkCZ: I don't know, but my guess is the LTS versions have more testing for that stuff
[21:48] <tomkCZ> unfortunately for me it has problems with X forwarding lol
[21:48] <penguin42> LTS or Maverick?
[21:48] <tomkCZ> lucid
[21:49] <tomkCZ> that's why I want to move to mm, otherwise I wouldn't care much
[21:49] <tomkCZ> I was happy on intrepid for two years
[21:50] <penguin42> tomkCZ: What's your X forwarding problem ?
[21:50] <tomkCZ> it's basically if you forward a window doesn't matter if throught ssh or telnet it freezes when clicking in it with the right mouse invoking menu
[21:51] <tomkCZ> wierd stuff
[21:51] <penguin42> oh that's an odd one
[21:51] <penguin42> on what program?
[21:51] <tomkCZ> something to do with lucid kernel, perfectly fixed on maverick
[21:51] <penguin42> doubt right click issues have anything to do with kernel
[21:52] <tomkCZ> it's more inputs from keyboard and mouse
[21:52] <tomkCZ> you  see desktop and the forwarded app are still alive but it blocks inputs somehow
[21:53] <tomkCZ> lucid is the only version it had problems with
[21:53] <tomkCZ> fine on intrepid, fine on maverick etc.
[21:54] <penguin42> tomkCZ: Do you know if there is a bug number for that?
[21:54] <tomkCZ> on a pc I need forwarded stuff for my work I have maverick and MS outlook in virtualbox ;)
[21:56] <tomkCZ> yup I found it - it's mine https://bugs.launchpad.net/ubuntu/+bug/624583
[21:56] <ubot2> Launchpad bug 624583 in xserver-xorg-input-evdev (Ubuntu) "X server inputs(keyboard and mouse) are blocked when X forwarding (affects: 1) (heat: 39)" [Undecided,New]
[21:56] <tomkCZ> as it is fixed on mm I thought piece of cake to move on
[21:57] <penguin42> tomkCZ: Can you clarify the Solaris thing - which end is the Solaris one; the one running the app or the one with teh X server?
[21:57] <tomkCZ> app
[21:57] <tomkCZ> I read somewhere the kernel on lucid has these inputs issues
[21:58] <penguin42> does it happen if it's not Solaris ?
[21:58] <tomkCZ> really dunno, I tested with solaris with several computers nad ubuntu versions
[21:58] <tomkCZ> because I needed solaris ........
[21:59] <penguin42> yeh; it would be interesting to track it down to an interaction with Solaris or something more general
[21:59] <tomkCZ> and for the subject do you remember that horrible problem on karmic koala with connecting external monitor killing X ..
[22:00] <tomkCZ> I would go more deeper but new version was scheduled soon and it's fixed there so I thought move and forget
[22:00] <tomkCZ> but evolution is crappy there ;)
[22:01] <tomkCZ> I seem to experience one critical bug per every release - not very happy with thar
[22:01] <penguin42> tomkCZ: If you can track it down to whether that bug only happens with Solaris guests or is more general I think it would be interesting
[22:01] <penguin42> tomkCZ: I understand that - I'd like less of them as well
[22:02] <tomkCZ> I could track it but I doubt anyone would care for that when it is ok on newer version
[22:02] <tomkCZ> that's hiw ubuntu fixes stuff lately - hey, wait for the new version
[22:03] <penguin42> tomkCZ: Well Lucid is LTS so they might - but I don't know
[22:03] <penguin42> tomkCZ: Still, it would be helpful I think to be able to track it down - if you make it really easy for a developer to test it by saying 'it breaks on exactly this combination' it might be easier
[22:03] <penguin42> tomkCZ: It'll also help anyone else who hits the same problem
[22:06] <tomkCZ> still if there is a new version without this problem and I suspect they are all working on natty already ;)
[22:07] <penguin42> yeh that's probably true
[22:08] <tomkCZ> I am still undecided if this is a good or bad thing, but it may make me to leave ubuntu to debian for an instance
[22:09] <tomkCZ> bugs are not fixed properly you know
[22:10] <tomkCZ> ok nice to chat, bbl