[00:01] 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] 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] good morning [06:37] hi dholbach [06:37] good morning [06:43] hi YoBoY [07:54] good morning [08:15] 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] Ryan52, goto launchpad.net/ubuntu/+source/PACKAGE and click on "subscribe to bugmail" [08:19] I want to do this from a script.. [08:19] your method doesn't scale well. [08:20] ah, ok, got it now ;) [08:21] 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] Ryan52, there are two python libraries to access launchpad, python-launchpad-bugs and launchpadlib, but both cannot do this for you [08:23] oh, 104, that's a big number [08:27] 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] how do I handle logging in from a script, tho? [08:31] Ryan52, you can use your mozilla cookie or a base64 encoded Authorization header [08:35] thekorn: ok, thanks! [08:35] no problem === thekorn_ is now known as thekorn === thekorn_ is now known as thekorn === asac_ is now known as asac === draitz is now known as draitz- === draitz- is now known as draitz [12:29] calc: https://bugs.launchpad.net/bugs/346943 [12:29] Ubuntu bug 346943 in openoffice.org "opening an OOo existing file (with Compiz ON) OOo with appear on another Desktop window" [Undecided,Incomplete] [12:29] that bug is becoming a nuisance [12:31] BUGabundo: rgrep -i office ~/.compiz/session [12:32] james_w: empty [12:33] BUGabundo: what about calc? [12:33] sorry? [12:34] rgrep -i calc ~/.compiz/session [12:34] james_w: empty too === thekorn_ is now known as thekorn === thekorn_ is now known as thekorn === seb128_ is now known as seb128 [15:12] Boo [15:15] foo [15:15] :) [15:35] calc: ping [15:35] just .openoffice or openoffice3 too? [15:39] BUGabundo: any .openoffice* [15:39] did both [15:39] BUGabundo: perhaps .openoffice.org2 and .openoffice.org [15:39] updated the bug [15:39] it *worksP [15:40] ah so it is some sort of werid configuration issue on your system [15:40] I only have .org and .org3 [15:40] where would OOo conf set the Workspace? [15:41] i have no idea at all [15:41] i have a small idea [15:41] let me see if i can find the file name [15:42] i don't know if it is the same file as was causing problem for other users or not, let me see [15:42] want me to pack and upload those conf dirs? [15:42] maybe 3/user/registry/data/org/openoffice/Setup.xcu [15:42] 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] as upstream won't take the issue unless I can prove it happens on their version [15:43] ok [15:43] 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] eg a Windows XP OOo user mentioned that Ubuntu seemed to have the same problem so they closed the bug [15:43] *@#! developers ;-) [15:44] \o/ [15:44] that file above i noted may be all that is needed to be deleted to make it work for you [15:44] but i am not certain, that file causes problems for users with forced maximized mode (aiui) [15:44] charlie-tca: :) [15:45] calc: http://pastebin.com/m68630c59 [15:47] BUGabundo: does just removing that file fix the problem also? [15:47] i don't see anything in that file that seems to note virtual desktop it should run on [15:48] but i am not 100% certain i am reading the file correctly [15:48] let me try [16:00] calc: just removing that file, seems to fix the prob [16:00] BUGabundo: ok [16:01] 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] otherwise they either close the bug immediately or never look at it at all [16:02] 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] ok [16:05] but since most of that info on the file doesn't seem to affect me options [16:05] I have no idea how to reproduce [16:05] maybe a PPA vs Archive thing [16:07] ppa is the same as the archive (essentially) [16:07] i only modified options that had to be to make it compile on older releases [16:07] its probably just something very hard to trigger [16:08] 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] ahh [16:10] like XFS fail to dump to disj [16:10] *disk [16:10] sorta [16:10] like many now like to call Ext4 bug [16:10] that could be it [16:11] very hard to trigger [16:11] 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 === fader_ is now known as fader|lunch === fader|lunch is now known as fader_ [18:35] bdmurray, hi, I think it's time to purge lp_activity_comments.user.js from launchpad-gm-scripts [18:35] it does not work correctly and launchpad does the job now [18:37] thekorn: sounds good to me, its exciting to see it deprecated ;-) [18:38] yes, this new way of presenting activitylogs is the best UI improvement in the last couple of month ;) [18:40] 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? === Igorot is now known as Knightlust [18:47] 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] 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] thekorn: deprecated sounds fine and a merge proposal would be great [18:50] ok, I'm going to create one now [18:50] thanks [18:50] Thank you! [19:09] bdmurray, I've created https://code.edge.launchpad.net/~thekorn/launchpad-gm-scripts/purge-activity-comments/+merge/5077 === jtholmes is now known as jth === jth is now known as jtholmes === paul__ is now known as Elbrus === pedro__ is now known as pedro_ [20:25] Anyone can start xfmedia without compositing? [20:25] https://bugs.launchpad.net/ubuntu/+source/xfmedia/+bug/333384 [20:25] Ubuntu bug 333384 in xfmedia "xfmedia crashed with SIGSEGV in pthread_mutex_lock()" [Undecided,New] === hubuntu is now known as huayra === jjesse_ is now known as jjesse === yofel_ is now known as yofel [21:39] hello, I reported bug #348275 but now all work ok [21:39] Launchpad bug 348275 in linux "[iwlagn] networkmanager applet cannot connect to WPA2 home network" [Unknown,Confirmed] https://launchpad.net/bugs/348275 [21:40] 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] What should I do? [21:44] torkiano: What is different that may have fixed it? [21:46] maybe the latest network-manager upgrade, but I am not sure, sorry [21:47] since other people are experiencing it and it is being tracked in Jaunty I'd leave it be [21:47] However, generally setting a bug to Invalid in this case would be fine [21:48] bdmurray, ok, thank you [21:48] Thank you for asking! [21:49] bdmurray, I close the upstream kernel bug because I don't upgrade any kernel package === Igorot is now known as Knightlust [22:17] greg-g, ping [22:20] hggdh: hello [22:23] hi greg-g -- re. bug 351211 -- I am considering reassigning all such bugs elsewhere, perhaps libc [22:23] Launchpad bug 351211 in coreutils "mv crashed with SIGSEGV in __libc_start_main()" [Undecided,New] https://launchpad.net/bugs/351211 [22:23] this really does not look like a coreutils issue. In fact, we have many such bugs in other packages [22:24] 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] 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] heh [22:26] OK, I will start the reassignment [22:28] oooooh this goes a loong way back... oldest open bug on SEGV at __libc_start_main is bug 90660! [22:28] Launchpad bug 90660 in qemu "[apport] qemu-i386 crashed with SIGSEGV in __libc_start_main()" [Medium,Confirmed] https://launchpad.net/bugs/90660 [22:32] wow, yeah, something to look into then [23:24] Hi, if I know of a bug which has already been reported upstream, should I still report it through Launchpad? [23:24] ghindo: It depends on its importance / severity [23:24] Is it something that needs to be fixed in Jaunty? [23:25] bdmurray: I'm not sure [23:25] bdmurray: I'm mostly asking on behalf of this thread: http://ubuntuforums.org/showthread.php?t=1112258 [23:27] 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] bdmurray: Cool, thank you. [23:30] 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.