[00:01] <maxb> The dist-packages thing is all about separating the install directories for site-installed modules being installed for the *system* python, vs. the modules of a completely site-installed python
[00:10] <JanC> maxb: right, so that if you install the new google-developed cpython-fork from source, things don't break between both of those
[06:26] <dholbach> good morning
[06:37] <YoBoY> hi dholbach
[06:37] <YoBoY> good morning
[06:43] <dholbach> hi YoBoY
[07:54] <thekorn> good morning
[08:15] <Ryan52> is there some easy way I can subscribe to bugs for packages? where easy means from a script or from a non interactive command line program. ;-)
[08:18] <thekorn> Ryan52, goto launchpad.net/ubuntu/+source/PACKAGE and click on "subscribe to bugmail"
[08:19] <Ryan52> I want to do this from a script..
[08:19] <Ryan52> your method doesn't scale well.
[08:20] <thekorn> ah, ok, got it now ;)
[08:21] <Ryan52> basically I'm lazy, I already have a list of "my" (or partially mine, or soon to be mine) packages (there's 104 of them), and I want to get ubuntu bug mail for them. I think I'm subscibed to maybe 10 of them... :P
[08:23] <thekorn> Ryan52, there are two python libraries to access launchpad, python-launchpad-bugs and launchpadlib, but both cannot do this for you
[08:23] <thekorn> oh, 104, that's a big number
[08:27] <thekorn> but I think scripting this should be easy, it looks like you have to POST something like {"field.subscribe_me.used": 1, "field.subscribe_me":1} to https://edge.launchpad.net/ubuntu/+source/PACKAGE/+subscribe
[08:28] <Ryan52> how do I handle logging in from a script, tho?
[08:31] <thekorn> Ryan52, you can use your mozilla cookie or a base64 encoded Authorization header
[08:35] <Ryan52> thekorn: ok, thanks!
[08:35] <thekorn> no problem
[12:29] <BUGabundo> calc: https://bugs.launchpad.net/bugs/346943
[12:29] <BUGabundo> that bug is becoming a nuisance
[12:31] <james_w> BUGabundo: rgrep -i office ~/.compiz/session
[12:32] <BUGabundo> james_w: empty
[12:33] <james_w> BUGabundo: what about calc?
[12:33] <BUGabundo> sorry?
[12:34] <james_w> rgrep -i calc ~/.compiz/session
[12:34] <BUGabundo> james_w: empty too
[15:12] <bddebian> Boo
[15:15] <BUGabundo> foo
[15:15] <bddebian> :)
[15:35] <BUGabundo> calc: ping
[15:35] <BUGabundo> just .openoffice or openoffice3 too?
[15:39] <calc> BUGabundo: any .openoffice*
[15:39] <BUGabundo> did both
[15:39] <calc> BUGabundo: perhaps .openoffice.org2 and .openoffice.org
[15:39] <BUGabundo> updated the bug
[15:39] <BUGabundo> it *worksP
[15:40] <calc> ah so it is some sort of werid configuration issue on your system
[15:40] <BUGabundo> I only have .org and .org3
[15:40] <BUGabundo> where would OOo conf set the Workspace?
[15:41] <calc> i have no idea at all
[15:41] <calc> i have a small idea
[15:41] <calc> let me see if i can find the file name
[15:42] <calc> i don't know if it is the same file as was causing problem for other users or not, let me see
[15:42] <BUGabundo> want me to pack and upload those conf dirs?
[15:42] <calc> maybe 3/user/registry/data/org/openoffice/Setup.xcu
[15:42] <calc> not really needed, unless you can make it reproduce again with a clean config dir i can't do anything with the bug
[15:43] <calc> as upstream won't take the issue unless I can prove it happens on their version
[15:43] <BUGabundo> ok
[15:43] <calc> they outright close their own bugs by the mere mention of Ubuntu in the same bug report, regardless of if the user even uses ubuntu
[15:43] <calc> eg a Windows XP OOo user mentioned that Ubuntu seemed to have the same problem so they closed the bug
[15:43] <calc> *@#! developers ;-)
[15:44] <charlie-tca> \o/
[15:44] <calc> that file above i noted may be all that is needed to be deleted to make it work for you
[15:44] <calc> but i am not certain, that file causes problems for users with forced maximized mode (aiui)
[15:44] <calc> charlie-tca: :)
[15:45] <BUGabundo> calc: http://pastebin.com/m68630c59
[15:47] <calc> BUGabundo: does just removing that file fix the problem also?
[15:47] <calc> i don't see anything in that file that seems to note virtual desktop it should run on
[15:48] <calc> but i am not 100% certain i am reading the file correctly
[15:48] <BUGabundo> let me try
[16:00] <BUGabundo> calc: just removing that file, seems to fix the prob
[16:00] <calc> BUGabundo: ok
[16:01] <calc> BUGabundo: if you can determine how to properly reproduce the bug then please reopen bug report with the information, then i can send the bug report to OOo developers
[16:01] <calc> otherwise they either close the bug immediately or never look at it at all
[16:02] <calc> we have a bug where OOo can get stuck in a permanent fullscreen mode which I was never able to reproduce until someone gave exact instructions (had to do with compositing being disabled, etc) then it was easy and now upstream is looking into it :)
[16:05] <BUGabundo> ok
[16:05] <BUGabundo> but since most of that info on the file doesn't seem to affect me options
[16:05] <BUGabundo> I have no idea how to reproduce
[16:05] <BUGabundo> maybe a PPA vs Archive thing
[16:07] <calc> ppa is the same as the archive (essentially)
[16:07] <calc> i only modified options that had to be to make it compile on older releases
[16:07] <calc> its probably just something very hard to trigger
[16:08] <calc> the fact the file is corrupt is a symptom not the issue itself, so without knowing what the issue is we can't really fix it
[16:10] <BUGabundo> ahh
[16:10] <BUGabundo> like XFS fail to dump to disj
[16:10] <BUGabundo> *disk
[16:10] <calc> sorta
[16:10] <BUGabundo> like many now like to call Ext4 bug
[16:10] <BUGabundo> that could be it
[16:11] <BUGabundo> very hard to trigger
[16:11] <calc> something in OOo is getting confused and writing out bad data about window states, which causes it to open on a different window than it should
[18:35] <thekorn> bdmurray, hi, I think it's time to purge lp_activity_comments.user.js from launchpad-gm-scripts
[18:35] <thekorn> it does not work correctly and launchpad does the job now
[18:37] <bdmurray> thekorn: sounds good to me, its exciting to see it deprecated ;-)
[18:38] <thekorn> yes, this new way of presenting activitylogs is the best UI improvement in the last couple of month ;)
[18:40] <thekorn> bdmurray, what do you think is the best way to proceed, should I create a bug for this, change it in an attached branch and request a merge?
[18:47] <bdmurray> thekorn: I hate to "lose" the script totally as it might contain something somebody can learn from.  Perhaps renaming it is the best idea?
[18:49] <thekorn> bdmurray, well the good thing about VCS is that it is still in the history, but renaming it is also fine, what about creating a "deprecated" directory and putting it there
[18:50] <bdmurray> thekorn: deprecated sounds fine and a merge proposal would be great
[18:50] <thekorn> ok, I'm going to create one now
[18:50] <thekorn> thanks
[18:50] <bdmurray> Thank you!
[19:09] <thekorn> bdmurray, I've created https://code.edge.launchpad.net/~thekorn/launchpad-gm-scripts/purge-activity-comments/+merge/5077
[20:25] <pitwalker> Anyone can start xfmedia without compositing?
[20:25] <pitwalker> https://bugs.launchpad.net/ubuntu/+source/xfmedia/+bug/333384
[21:39] <torkiano> hello, I reported bug #348275 but now all work ok
[21:40] <torkiano> I see here: https://wiki.ubuntu.com/Bugs/Responses#Bugs resolved after update or config change that I should mark it as invalid
[21:41] <torkiano> What should I do?
[21:44] <bdmurray> torkiano: What is different that may have fixed it?
[21:46] <torkiano> maybe the latest network-manager upgrade, but I am not sure, sorry
[21:47] <bdmurray> since other people are experiencing it and it is being tracked in Jaunty I'd leave it be
[21:47] <bdmurray> However, generally setting a bug to Invalid in this case would be fine
[21:48] <torkiano> bdmurray, ok, thank you
[21:48] <bdmurray> Thank you for asking!
[21:49] <torkiano> bdmurray, I close the upstream kernel bug because I don't upgrade any kernel package
[22:17] <hggdh> greg-g, ping
[22:20] <greg-g> hggdh: hello
[22:23] <hggdh> hi greg-g -- re. bug 351211 -- I am considering reassigning all such bugs elsewhere, perhaps libc
[22:23] <hggdh> this really does not look like a coreutils issue. In fact, we have many such bugs in other packages
[22:24] <greg-g> hggdh: sure, I actually didn't take a close look at those as I was just marking a lot of private bugs public (especially ones that were "master" bugs for other duplicates)
[22:25] <greg-g> this was after bdmurray blogged about the list of bugs opened during Jaunty's development, I sorted by Gravity and there were a bunch of private near the top
[22:26] <hggdh> heh
[22:26] <hggdh> OK, I will start the reassignment
[22:28] <hggdh> oooooh this goes a loong way back... oldest open bug on SEGV at __libc_start_main is bug 90660!
[22:32] <greg-g> wow, yeah, something to look into then
[23:24] <ghindo> Hi, if I know of a bug which has already been reported upstream, should I still report it through Launchpad?
[23:24] <bdmurray> ghindo: It depends on its importance / severity
[23:24] <bdmurray> Is it something that needs to be fixed in Jaunty?
[23:25] <ghindo> bdmurray: I'm not sure
[23:25] <ghindo> bdmurray: I'm mostly asking on behalf of this thread:  http://ubuntuforums.org/showthread.php?t=1112258
[23:27] <bdmurray> ghindo: Yes, that would be good to open in Launchpad since its a crash and something we'd like to fix in Jaunty
[23:29] <ghindo> bdmurray: Cool, thank you.
[23:30] <bdmurray> Some low priority ones it might make more sense just to open upstream, and the fixes will be pulled in during development of the next release.