[00:03] <silver-->  my ftp client . had a problem to connection on SSL explicit..     i tried with several servers..and  always the same problem.. i  can connect without any problem.. but  the folders listing not working
[02:41]  * kenvandine hugs chrisccoulson for the awesome dbusmenu fix!
[02:42] <kenvandine> 3 line patch fixed at least 3 bugs!
[02:42] <kenvandine> chrisccoulson == hero!
[03:23] <kenvandine> chrisccoulson, lets make that 4 bugs fixed in that 3 line patch!
[05:04] <robert_ancell> RAOF, does this look familiar? http://imgur.com/QkB1j
[05:04] <RAOF> Mmmm, static.
[05:04] <RAOF> What did you do to get this?
[05:05] <RAOF> It looks basically like your card is trying to scan out from totally uninitialised memory, such as you might find after a sufficiently cold reboot.
[05:07] <robert_ancell> it happens after a while of usage, possibly related to interacting with the unity dock
[05:08] <robert_ancell> it used to happen within a minute of running in Unity, I thought it was fixed, but I just triggered it then
[05:08] <robert_ancell> always the same pattern, and it flickers like white noise
[05:08] <robert_ancell> it also flashes to black every minute or so like it's trying to change mode
[05:09] <RAOF> It flickers?  Hm.
[05:09] <RAOF> Gah.  I thought those flashes were fixed!  (It's a kernel bug)
[05:09] <robert_ancell> I don't get the problem if I run metacity
[05:09] <RAOF> The flashing-to-black, or the crazy static?
[05:09] <robert_ancell> either
[05:10] <robert_ancell> once it displays like this I have to do a hard reboot
[05:10] <RAOF> Ok.  Then the flash to back is not what I was thinking of.
[05:10] <RAOF> Does dmesg or Xorg.0.log have anything interesting?
[05:11] <RAOF> (This is radeon, right?)
[05:12] <robert_ancell> radeon, yes
[05:13] <robert_ancell> nothing in dmesg (but this is after a reboot, so shouldn't be right?)
[05:14] <RAOF> Right.  You'd need to ssh in to grab dmesg.
[05:14] <RAOF> Of course, just to make this easier, dmesg is more likely to contain interesting stuff :)
[05:14] <robert_ancell> Xorg.*.log doesn't contain anything interesting
[05:14] <RAOF> It'd be .log.old if you've restarted.\
[05:15] <RAOF> But if there's something there it's likely to be less interesting than what's in dmesg.
[05:17] <robert_ancell> http://paste.ubuntu.com/577689/
[05:18] <RAOF> Yeah, nothing particularly smoking-gun.
[05:19] <RAOF> Interesting that Synaptics seems to be complaining at the end; possibly this is the kernel going totally mental and confusing multiple things?
[05:21] <robert_ancell> yeah, that looked odd to me too
[05:22] <robert_ancell> also, why the RADEON entry so late after the first ones?
[05:22] <RAOF> That'll be something probing RandR
[05:23] <RAOF> Causing radeon to probe the EDID of the lvds display.  Which, unsurprisingly, won't have changed.
[05:29]  * RAOF goes out to collect his car from the servicəååšlccc555
[07:24] <didrocks> good morning
[07:25] <kenvandine> good morning didrocks
[07:25] <didrocks> hey kenvandine :)
[07:29] <RAOF> Heydi ho, didrocks
[07:34] <pitti> Good morning
[07:34] <pitti> hey didrocks
[07:34] <pitti> hello RAOF
[07:35] <RAOF> Hey there pitti!
[07:40] <didrocks> hey RAOF, pitti!
[07:41] <pitti> didrocks: I think I can work on bug 723782 next week; is that early enough?
[07:41] <ubot2> Launchpad bug 723782 in gnome-session "Finalize gnome-session fallback detection" [Medium,New] https://launchpad.net/bugs/723782
[07:41] <didrocks> actually, having the notifications on the second monitor is quite nice, I can work on emails without being distraction as I miss them all :)
[07:42] <didrocks> pitti: oh really? That would be awesome. I planned to tackle that next week if nobody jumped on it
[07:42] <didrocks> pitti: next week is good enough, the remaining pieces from unity for that will land not this week but next week :)
[07:43] <didrocks> pitti: if you are trading that for other tasks, I still an try working on that "off IRC" time
[07:43]  * didrocks has done 80% of the alt-F2 work yesterday, now time to tackle the remaining and harder 20% :)
[07:54] <didrocks> re, sorry have an hardware issue I guess…
[07:54] <didrocks> so, didn't receive anything after my last words
[07:54] <didrocks> seems my nvidia card is in a bad shape
[07:55] <didrocks> artefacts everyone (even in bios boot)
[07:55] <didrocks> no way to start 3D anymore, I'm in failsafe mode…
[07:55]  * RAOF screams hardware problem! At didrocks' crazy magnetic flicker problem :)
[07:55] <RAOF> However, that sucks.
[07:55] <didrocks> RAOF: the magnetic issue is not hardware, it has been confirmed by loicm
[07:57] <RAOF> Oh.  So your failing card doesn't have *any* upside :(
[07:57] <didrocks> RAOF: http://people.canonical.com/~didrocks/Capture-10.png
[07:58] <didrocks> see the small "aubergine" repeated motif?
[07:58] <didrocks> the weird thing is that it's only on the background
[07:58] <didrocks> not in the panel
[07:58] <didrocks> or in the apps
[07:58] <didrocks> RAOF: and when I try to start with the nvidia driver, it stalls in the nvidia logo
[07:59] <didrocks> no way to switch to a tty or whatever…
[07:59] <RAOF> Um, that looks right to me?
[07:59] <didrocks> RAOF: hum… can you try to zoom in?
[07:59] <didrocks> as it zoomed here, I assumed it was visible
[07:59] <didrocks> hum, maybe not
[08:00] <didrocks> no, it doesn't zoom, so yeah, I'm the only one to see it
[08:00] <RAOF> I see some of the icons being smeared, but that may well just be the crappy VGA output.
[08:00] <didrocks> yeah
[08:00] <RAOF> Hurray for problems on scanout!
[08:00] <didrocks> ok, so not that…
[08:00] <didrocks> no idea at all to see what happens?
[08:01] <RAOF> Sometimes you need to take an actual picture of the screen because the problem isn't caught on the download-from-vram path.
[08:02] <didrocks> yeah
[08:02] <didrocks> ok, let's try to cool it a little bit, waiting for 15 minutes
[08:02] <RAOF> When's your laptop refresh?
[08:03] <didrocks> 2 years?
[08:04] <didrocks> ok, overheating apparently…
[08:04] <RAOF> :(
[08:05] <RAOF> Actually, that's not bad.  Maybe you can fix it with some judiciously applied thermal paste and compressed air.
[08:08] <didrocks> so, from a french forum, with 30 people posting…
[08:08] <didrocks> overheating and they put it in the hoven
[08:09] <didrocks> 180°C, 6 minutes
[08:09] <RAOF> That was a different problem, wasn't it?
[08:09] <didrocks> to redo the join…
[08:09] <RAOF> That was when the solder would degrade causing craziness.
[08:10] <RAOF> But just plain overheating sounds like a job for Dust Removal Man!
[08:10] <didrocks> yeah, seems to fix people's issue for some weeks…
[08:10] <didrocks> hum
[08:11] <didrocks> let's cool it down for now, switching to my netbook :/
[08:26] <ara> morning all!
[08:27]  * bryceh_ waves to ara
[08:29] <ara> quick question: is there any gconf key(s) to set up switching to classic-desktop on next boot?
[08:30] <ara> (or any other way to set it up trough the command line)
[08:30] <pitti> ara: not very user-friendly, but you can set Session=gnome-2d in ~/.dmrc
[08:30] <ara> pitti, awesome, thanks!
[08:31]  * ara hugs pitti
[08:31] <pitti> ara: I take it that's for automatic testing?
[08:31] <pitti> ara: that's actually the canonical way to select it (it's what gdm writes when you change the session there)
[08:31]  * pitti hugs back ara
[08:32] <ara> pitti, yes, we need to switch back to classic-desktop to take bootchart metrics with the 2d desktop to compare
[08:32] <pitti> ara: actually we do have an user-friendly way as well, in gdmsetup :)
[08:32] <ara> and we can only access trough ssh
[08:47] <didrocks> RAOF: FYI, what I'm seeing is this: http://www.youtube.com/watch?v=5wINkdSpU2o
[09:29] <chrisccoulson> good morning everyone
[09:29] <pitti> hey chrisccoulson
[09:30] <chrisccoulson> kenvandine, which other bugs did it fix? :)
[09:30] <chrisccoulson> hi pitti, how are you?
[09:30] <pitti> chrisccoulson: I'm great, thanks! new natty langpacks with 4.0 XPIs uploaded
[09:30] <chrisccoulson> excellent, thanks!
[09:31] <pitti> chrisccoulson: did upstream respond already wrt. maxVersion?
[09:31] <chrisccoulson> pitti - yeah, i think they plan to fix it, but the rc1 builds have already been spun
[09:32] <chrisccoulson> and the branch is closed right now anyway
[09:33] <seb128> hey pitti chrisccoulson
[09:33] <chrisccoulson> hi seb128, how are you?
[09:34] <seb128> chrisccoulson, I'm fine thanks, how are you?
[09:34] <seb128> had fun on libdbusmenu it seems
[09:34] <chrisccoulson> yeah, apparently i fixed a few bugs ;)
[09:35] <seb128> great
[09:37] <chrisccoulson> seb128 - oh, i think i fixed your pidgin bug too1
[09:37] <seb128> which one?
[09:37] <seb128> the one after activating an account which asks for a pwd?
[09:39] <chrisccoulson> seb128 - yeah, i don't get that now
[09:39] <seb128> chrisccoulson, btw is the fix ken uploaded yours?
[09:40] <chrisccoulson> seb128 - yeah, that's the one
[09:40] <seb128> ok great
[09:40] <chrisccoulson> i didn't realise he uploaded it already
[09:40] <seb128> I will get that installed and do another round of testing
[09:40] <chrisccoulson> thanks
[09:40] <seb128> do you have issues remaining or did that just fix the set?
[09:40] <chrisccoulson> i fixed the unity-panel-service crash too
[09:41] <seb128> nice
[09:41] <chrisccoulson> that was easily reproducible once i fixed the dbusmenu bug :)
[09:41] <chrisccoulson> i just ran an application that added and removed menus every 50ms, whilst i scrubbed the menubar ;)
[09:41] <chrisccoulson> it crashed repeatedly every few seconds
[09:45] <seb128> ;-)
[09:45] <seb128> chrisccoulson, thanks a lot for working on those issues, nice to get that sorted
[09:46] <seb128> there is still the indicator-datetime crasher ;-)
[09:47] <didrocks> kenvandine: did you merge the commit you proposed in the packaging branch? seems to be only one commit looking at bzr history. This breaks daily builds, next time, can you do it in two commits please?
[09:48] <seb128> didrocks, what do you mean by 2 commits?
[09:48]  * pitti is out for ~ 45 mins
[09:49] <didrocks> seb128: I mean, bzr merge ../upstream-change
[09:49] <didrocks> bzr commit
[09:49] <didrocks> then packaging change
[09:49] <didrocks> bzr commit
[09:49] <didrocks> (and eventuall dch -r "" && debcommit -r for a big bonus :))
[09:50] <seb128> k
[09:50] <seb128> I tend to do one commit as well
[09:50] <seb128> like bzr merge, dch -i, commit
[09:50] <didrocks> this confuses bzr when you merge back
[09:51] <didrocks> (so, merging the packaging branch in upstream trunk)
[09:51] <didrocks> which is what daily builds do
[09:51] <didrocks> it tells "ohhh, changes in both side (conflicting most of the time because of version bump), what to do"
[09:52] <seb128> ok, makes sense
[09:52] <seb128> thanks for the explanation
[09:52] <didrocks> yw :)
[09:54] <didrocks> kenvandine: also, you didn't propose the libunity change
[09:54] <didrocks> (or I miss something, maybe)
[10:16] <Ampelbein> hi! with unity and thunderbird-globalmenu I have the problem that some menu items are not selectable, for example the 'Message filters'. If I remove the package 'thunderbird-globalmenu', I can access those items again. Is this a known issue or should I file a new bug against 'thunderbird'?
[10:20] <chrisccoulson> Ampelbein, are you sure you're not fully updated? I'm sure I fixed that one already
[10:20] <Ampelbein> chrisccoulson: updated this morning, 2 hours ago. I'll check again, just to be sure.
[10:21] <Ampelbein> chrisccoulson: thunderbird is 3.1.9+nobinonly-0ubuntu1
[10:22] <chrisccoulson> so, if you select a message in your inbox and go to tools, "Message filters" is not active? it should activate as you open the menu
[10:23] <Ampelbein> chrisccoulson: yes, that's my problem. it doesn't activate, let me make a screenshot
[10:24] <chrisccoulson> hmmm, it works here. do you have any other extensions installed?
[10:25] <Ampelbein> chrisccoulson: I have enigmail installed, too. http://tinypic.com/r/33ff1mx/7
[10:25] <Ampelbein> chrisccoulson: it works if I remove the -globalmenu package
[10:28] <chrisccoulson> Ampelbein, hmmm, i can't reproduce that :/
[10:28] <chrisccoulson> do bookmarks work in firefox?
[10:28] <Ampelbein> chrisccoulson: I use chromium, but let me try
[10:28] <chrisccoulson> (with firefox-globalmenu)
[10:29] <Ampelbein> chrisccoulson: yes, in firefox the bookmarks menu works
[10:29] <chrisccoulson> ok, that's good then
[10:31] <Ampelbein> chrisccoulson: any commandline switch I can activate to get some info?
[10:32] <chrisccoulson> unfortunately not
[10:32] <chrisccoulson> you can set GLOBALMENU_DEBUG=1 in your environment though, and that will show both menubars
[10:33] <chrisccoulson> could you please do that, then try opening the tools menu inside thunderbird, and then try the tools menu from the panel?
[10:33] <Ampelbein> ok
[10:35] <Ampelbein> chrisccoulson: hmm 'andreas@anubis:~$ GLOBALMENU_DEBUG=1 thunderbird' but no menubar in thunderbird
[10:36] <chrisccoulson> Ampelbein, oops - http://bazaar.launchpad.net/~extension-hackers/globalmenu-extension/trunk/view/head:/extensions/globalmenu/components/src/uGlobalMenuService.cpp#L200
[10:37] <chrisccoulson> GLOBAL_MENU_DEBUG ;)
[10:37] <Ampelbein> chrisccoulson: ah ;-)
[10:38] <Ampelbein> chrisccoulson: inside thunderbird works, global does not
[10:38] <chrisccoulson> ok, that rules out 1 issue then
[10:38] <Ampelbein> chrisccoulson: I'm on amd64 if that's any help
[10:45] <chrisccoulson> Ampelbein, have you ever used chromebug before?
[10:46] <Ampelbein> chrisccoulson: no
[10:47] <chrisccoulson> actually, first it might be a good idea to check there are no errors thrown in the error console when you open the tools menu
[10:47] <Ampelbein> chrisccoulson: I looked already, error console is empty
[10:56] <seb128> pitti, pygobject 2.28 is out btw
[10:57] <pitti> yeah, saw yesterday on #python
[10:57] <seb128> ok, I was pointing it because I don't know if you notice GNOME tarballs updates or not
[10:58] <pitti> seb128: it's on my list after I'm done beating up langpacks
[10:59] <seb128> pitti, ok
[11:02] <chrisccoulson> Ampelbein, i might need to get you to use chromebug in a bit. in the meantime, i've got some other things to work on
[11:03] <chrisccoulson> brb, need to start classic session :/
[11:03] <geser> seb128: re bug #731832: as you set the bug to "Fix Committed" any sponsoring isn't needed anymore, right? the bug sumitter askes in #ubuntu-motu how to move on with it
[11:03] <ubot2> Launchpad bug 731832 in dee "Comma at end of enumerator list" [Low,Fix committed] https://launchpad.net/bugs/731832
[11:04] <seb128> geser, no, it will part of the weekly dx updates tomorrow
[11:04] <seb128> geser, it seems fixing -pedentic builds in an unstable distro can wait a day
[11:04] <seb128> geser, wouldn't bother doing sponsoring today
[11:05] <geser> ok, will forward this information to him
[11:05] <seb128> thanks
[11:20] <chrisccoulson> hmmm, i'm struggling to recreate this indicator-applet-appmenu crash :(
[11:45] <seb128> chrisccoulson, don't bother much, seems it doesn't happen often and the unity case is fixed
[11:56] <Sweetshark> pitti: I am still a bit confused by the |-Depends. In openoffice.org-dictionaries we add "| language-support-writing-*" at the end, so that we do not pull in openoffice.org-core. But should it not be the first alternative then?
[11:56] <vish> seb128: wrt Bug 721121, and mark's comment about the folder+pointer icon. i've removed that icon now. the upload is ready in ~ubuntu-art-pkg/humanity/release/ fixes that bug and a few other bugs, no other major changes, i had asked kenvandine to upload it when he is free, either you or kenvandine can upload when free ;)
[11:56] <ubot2> Launchpad bug 721121 in unity "Icon in Launcher should be home folder icon" [Medium,Fix released] https://launchpad.net/bugs/721121
[11:57] <pitti> Sweetshark: the order only really matters if you have neither LibO nor the l-support package installed; in a default install you'd have both
[11:57] <seb128> vish, what do you use instead of this one?
[11:57] <pitti> Sweetshark: so the main point of that thing is that you are able to uninstall LibO without having to remove the entire language-support for your language
[11:57] <vish> seb128: the gnome icon will be used, the one with the file cabinet
[11:58] <seb128> they don't have the same style though?
[11:58] <pitti> Sweetshark: the only point where the order matters is if you have a very stripped down system where you have neitehr LibO nor lang support, and you do e. g. apt-get install libreoffice-hyphenation-de
[11:58] <seb128> but it's orthogonal to the fix there?
[11:58] <vish> seb128: yea, orthogonal, but style is not a major issue.. neither me or Danrabbit had any better ideas :p
[11:58] <pitti> Sweetshark: right now this will pull in LibO instead of language-support, which I think is slightly "more" expected and correct
[11:58] <vish> seb128: style is nearly similar
[11:58] <seb128> ok
[12:02] <Sweetshark> pitti: understood
[12:51] <pitti> chrisccoulson: hm, the current langpacks for lucid/maverick ship stuff in usr/lib/firefox-addons/extensions/langpack-de@firefox-3.6.ubuntu.com/, but the XPIs have langpack-de@firefox.mozilla.org
[12:52] <pitti> chrisccoulson: I assume this is because we mangled them through xpi2xpi
[12:52] <pitti> chrisccoulson: but I suppose we can/should just use langpack-de@firefox.mozilla.org now/
[12:52] <pitti> ?
[12:53] <chrisccoulson> pitti - hmmm, i'm not sure how that works :/
[12:53] <pitti> chrisccoulson: I think my actual question is: does lucid's/maverick's firefox have a special patch to look for different langpack IDs?
[12:53] <seb128> pitti, bug #731007 btw
[12:53] <chrisccoulson> pitti - don't we swap out the install.rdf with po2xpi (or whatever it is that gets run)
[12:53] <ubot2> Launchpad bug 731007 in shotwell "Update to 0.9" [Wishlist,New] https://launchpad.net/bugs/731007
[12:53] <seb128> pitti, not sure who can ack it
[12:54] <chrisccoulson> pitti - the firefox source package generates a template install.rdf, which gets exported from launchpad i think (with the en-US.xpi)
[12:54] <pitti> chrisccoulson: yes, I suppose it does that; but we don't use po2xpi (which would take the LP translations into account), just xpi2xpi (which is a horribly complicated way of repacking)
[12:54] <pitti> seb128: queued
[12:54] <chrisccoulson> pitti - 1 second, i'll just have a look on my lucid machine behind me
[12:54] <pitti> chrisccoulson: for natty using the upstream ID works fine; did that change in natty?
[12:55] <pitti> chrisccoulson: right, I guess I'll build some local ones and try them in my chroot
[12:57] <chrisccouls0n> wow, i don't think jo has applied any updates on this machine in weeks
[12:57] <seb128> chrisccoulson, the pidgin issue is not fixed it seems there btw
[12:57] <chrisccouls0n> i log in, and update-manager provides me with a whole bunch of security updates
[12:57] <chrisccouls0n> seb128 - oh, that's not good :(
[12:57] <mvo> set her to auto-updates
[12:58] <chrisccouls0n> gaaaaah, syncdaemon
[12:58] <chrisccouls0n> i clicked to open gedit over 1 minute ago, it shouldn't take this long
[12:58] <seb128> chrisccoulson, will restart in a bit to verify but now the items are listed but the accounts one don't have their submenu
[12:59] <chrisccouls0n> pitti - ok, the lucid langpacks actually have em:id="langpack-de@firefox-3.6.ubuntu.com" in their install.rdf
[12:59] <seb128> session restart brb
[12:59] <pitti> chrisccouls0n: yes, I know; but not the ones I'm building with the fixed langpack-o-matic
[13:00] <pitti> chrisccouls0n: unfortunately the langpacks in the current PPA (with the old method) are now completely hosed, so I thought I'd move them all to the new (and much much simpler) way of doing things
[13:00] <chrisccouls0n> pitti - yeah, that makes sense. the same constraints will apply (install folder == em:id)
[13:01] <pitti> chrisccouls0n: so ffox doesn't have a builtin schema for the langpacks, the only condition is that id == folder?
[13:01] <chrisccouls0n> pitti - yeah,  ffox will only load extensions when the folder name is the same as the id
[13:02] <pitti> chrisccouls0n: ok, thanks; I'll double-check in my lucid chroot
[13:02] <chrisccouls0n> thanks
[13:02] <chrisccouls0n> i might update this machine to maverick
[13:02] <chrisccouls0n> lucid feels so old ;)
[13:03] <pitti> I now have test cases for both lucid and natty builds \o/
[13:03] <lag> It's broke! It's all broke!!
[13:04] <ogra_> stop whining, fix it :P
[13:04] <lag>  bug 731810
[13:04] <ubot2> Launchpad bug 731810 in nvidia-graphics-drivers ""conflicting memory types" -> "Failed to allocate primary buffer: out of memory"" [Undecided,New] https://launchpad.net/bugs/731810
[13:04] <lag> ogra_: :D
[13:04] <ogra_> get more memory :P
[13:07] <lag> With no nVidia driver it works okay
[13:08] <lag> I get a desktop, but no Compiz and everything looks just a little bit rubbish
[13:08] <mterry> chrisccoulson, so I remember seb128 saying that you were working on some libdbusmenu stuff that may fix some of the issues I have assigned.  I saw a new libdbusmenu go through, was that it?
[13:08] <lag> With nVidia I get the first application start to start then nothing
[13:08] <chrisccoulson> mterry, yeah, i found a bug last night that was causing some weirdness and ken uploaded it after i went to bed
[13:09] <mterry> chrisccoulson, nice.  UBUNTU_MENUPROXY is now undefined for me when I logged in, is that a separate issue?
[13:10] <chrisccoulson> mterry, possibly. i'm not sure where that gets set
[13:11] <seb128> mterry, weird, it's a /etc/Xsession.d wrapper which sets it
[13:15] <seb128> so
[13:15] <seb128> mterry, the new libdbusmenu with the fixes landed in natty, that fixed some of the issues with gnome-bt and empathy
[13:16] <seb128> mterry, the shotwell issue is still there though so you can work on that
[13:16] <mterry> guh, shotwell.  the funny thing is I remember having this exact problem when I first enabled shotwell and fixing it.  but i can't remember what the problem wass
[13:17] <seb128> mterry, https://code.launchpad.net/~mterry/indicator-appmenu/less-racy-window-closing
[13:17] <pitti> chrisccoulson: confirmed, works fine here with the upstream ID
[13:17] <seb128> mterry, https://code.launchpad.net/~mterry/indicator-appmenu/less-racy-window-closing/+merge/48381
[13:17] <seb128> mterry, it seems
[13:18] <chrisccoulson> pitti - cool, thanks
[13:18] <pitti> chrisccoulson: this is soooo much easier now
[13:18] <chrisccoulson> pitti - doing the thunderbird translations is even easier too :-)
[13:18] <chrisccoulson> (we just have a tb-locales package with the upstream xpi's in) ;)
[13:19] <seb128> mterry, out of this indicator-datetime needs some bug fixing, karl is out until the end of the week and seems to make slow progress, so if you feel like tackling some bugs there as well feel free
[13:19] <pitti> chrisccoulson: of course it's a step backwards from using our own LP-translated XPIs, but since we didn't have them anyway..
[13:19] <Sweetshark> didrocks: "Conflict/Replaces: openoffice.org-thesaurus << 0.6 in -fr for BE" <- What does tha mean? (from the openoffice.org-dictionaries changelog)
[13:19] <mterry> seb128, yeah, I have unfinished business in datetime from my preference FF run
[13:19] <chrisccoulson> yeah, it doesn't make sense to go through all that effort when we aren't using them anyway
[13:19] <pitti> chrisccoulson: ah, we do? that requires some extra language-selector magic, though
[13:19] <seb128> mterry, I can give you issues from it if you want, there is some translation issues, the events time not respecting the format and some crashers
[13:19] <pitti> chrisccoulson: actually it's quite easy now -- if you add the tbird XPIs to po2xpi/data, it'll Just Work (tm) now
[13:19] <didrocks> Sweetshark: it means that we probably move some files between packages
[13:19] <mterry> seb128, that merge sounds familiar, but is about multiple runss of shotwell, which this new issue isn't...  hmm, will dig
[13:20] <seb128> mterry, ok, so from my side please investigate on the shotwell issue and then feel free to go back to indicator-datetime
[13:20] <chrisccoulson> pitti - yeah, language-selector has some magic to pull in the the thunderbird-locales-* packages
[13:20] <didrocks> Sweetshark: and on upgrade, you don't know in which order the packages will be installed
[13:20] <seb128> mterry, right, seems that's what you proposed to fix the shotwell issues last time so I was just pointing it
[13:20] <chrisccoulson> pitti - perhaps we should ship the tb xpi's in the language packs too ;)
[13:20] <didrocks> Sweetshark: the conflicts/replaces is there to ensure that you get both new packages and that dpkg won't yell at you because you are trying to overwrite a file from another package
[13:20] <chrisccoulson> (and remove the evo ones) ;)
[13:21] <chrisccoulson> j/k
[13:21] <chrisccoulson> :-)
[13:21] <pitti> chrisccoulson: yeah, as I was saying it'd be trivial now to ship tbird XPIs right in the langpacks
[13:21] <seb128> trying to sneak another email client?!
[13:21] <dpm> chrisccoulson, pitti please let's not write off FF LP translations yet, I understand this is just some temporary measure to get the langpacks working, but it'd be good to be able to use LP in the future again. We did use devmode during the development cycle in the past, and this helped some teams, such as the Asturian guys, to have their translations shipped in Ubuntu easily and eventually they submitted them upstream
[13:21] <seb128> ;-)
[13:22] <pitti> dpm: right, it is
[13:22] <Sweetshark> didrocks: it is just that I dont see such Conflict in the control file
[13:22] <pitti> dpm: I'm just permanently writing off xpi2xpi
[13:22] <dpm> pitti, :)
[13:22] <didrocks> Sweetshark: well, it can has been removed in a further update
[13:22] <pitti> dpm: as I now have that in langpack-o-matic itself, with about 1/20th of the code, and with automatic test cases
[13:22] <dpm> excellent
[13:23] <Sweetshark> didrocks: ok, I will remove it then from the comment in the changelog for the next release
[13:23] <pitti> dpm: there's now just one rather short central function to install all XPIs for a given release into a langpack, so we can hook in po2xpi there in the future (without all the extra buggy scriptery around it)
[13:23] <didrocks> Sweetshark: you mean, you want to remove it in a past changelog?
[13:23] <didrocks> Sweetshark: or is in the the tip of it?
[13:24] <pitti> dpm: I also have test LP XPI export tarballs in the tests/ directory now (but not used yet)
[13:25] <dpm> pitti, ok, cool
[13:25] <Sweetshark> didrocks: I leave it in the old changelog entries, I will just not keep it as a "remaining difference to debian" in the new release
[13:26] <didrocks> Sweetshark: right
[13:26] <didrocks> if it's not there anymore, you can remove it :)
[13:26] <didrocks> hope that the remove was done with in mind that people will still have to upgrade between LTS though
[13:31] <seb128> mterry, btw ted approved your appmenu-gtk fix so don't forget to merge it
[13:31] <seb128> so it's in tomorrow's tarball
[13:32] <mterry> I can do that?  I don't think I'm part of DX
[13:32] <seb128> or is someone from dx supposed to do that? it's always confusing why they approve things without merge them directly
[13:32] <seb128> ok, will ping ted about that when he's there
[13:33] <seb128> mterry, btw https://code.edge.launchpad.net/~mterry/indicator-me/gsettings/+merge/38005 is set as "on hold", do you know why?
[13:33] <mterry> seb128, oh I don't have a pending appmenu-gtk fix.  But also, apparently I am in the DX LP team through Unity
[13:34] <seb128> mterry, https://code.edge.launchpad.net/~mterry/appmenu-gtk/cancellable-register-window/+merge/52248
[13:34] <seb128> mterry, that one is not merged it seems?
[13:34] <mterry> that got merged
[13:35] <mterry> seb128, if you look at trunk.  the merge proposal didn't notice thoughj
[13:35] <seb128> mterry, seems ted recommited it rather than merging your vcs
[13:35] <mterry> seb128, the gsettings branch isn't merged because I never went back and changed the gsettings paths
[13:35] <seb128> ok, setting it as merged then
[13:36] <mterry> seb128, arguably a FF breakage though to do it now
[13:36] <seb128> mterry, small one though
[13:36] <mterry> seb128, yeah, but do we care this cycle whether it's gconf or gsettings?
[13:36] <seb128> not really right
[13:37] <seb128> I was just cleaning a bug the list of assigned bugs for desktopers
[13:37] <seb128> bug -> bit
[13:37] <seb128> mterry, it's also that less gconf = faster login, but that's not like the 1 key from the indicator was going to make a difference
[13:37] <seb128> let's wait next cycle for it now
[13:38] <mterry> :)
[13:38] <seb128> mterry, you still have some oem bugs on https://bugs.edge.launchpad.net/~mterry/+assignedbugs
[13:38] <seb128> mterry, do you plan to still work on those? if not maybe you should unassign those?
[13:41] <mterry> seb128, heh, that page is pretty useless, isn't it, with all that cruft  :)
[13:41] <mterry> I'm supposed to be doing 56 things
[13:42] <seb128> slacker! ;-)
[13:43] <seb128> kenvandine, hey
[13:45] <Sweetshark> pitti: I merged the current debian unstable into openoffice.org-dictionaries-1:3.3.0~rc10-2ubuntu1. Should I push the bzr branch somewhere now?
[13:45] <pitti> seb128: just acked shotwell, FYI
[13:46] <pitti> Sweetshark: is it still called that way? Rene didn't rename it to libo-dicts?
[13:46] <pitti> Sweetshark: where did you merge it to? lp:ubuntu/openoffice.org-dictionaries ?
[13:47] <Sweetshark> pitti: still called openoffice.org dicts at debian as it will provide dicts for LO and OOo, I guess.
[13:47] <pitti> Sweetshark: if so, please push it to LP as lp:~bjoern/ubuntu/natty/openoffice.org-dictionaries/libo-update (or invent another name), and set up a merge proplsal
[13:47] <pitti> Sweetshark: does it build libo binaries now? or will the oo.o work for both?
[13:48] <seb128> pitti, thanks
[13:50] <Sweetshark> pitti: the dicts will work for both and the binary packages have neutral names now. there are transitionals in the openoffice.org source package for those, but _rene_ hasnt released that yet.
[13:50] <pitti> Sweetshark: ah, nice
[13:53] <Sweetshark> pitti: Ok, I dputted the source package to my personal testing ppa for now. I will push the branch when I return from lunch.
[13:53] <pitti> Sweetshark: late luch.. enjoy!
[13:53] <pitti> Sweetshark: I'll process the MP once you're done
[14:07] <chrisccoulson> tedg, when i run unity-panel-service in valgrind, i'm seeing this: http://paste.ubuntu.com/577851/
[14:08] <chrisccoulson> have you seen that before? it doesn't look like our bug does it?
[14:09] <tedg> chrisccoulson, No, I haven't seen that one before.  First blush I'd say it's not, but it could be us holding onto a variant reference too long.
[14:09] <tedg> chrisccoulson, There's definitely a memory leak in something unity-panel-service is doing though.  It's getting too big.
[14:09] <chrisccoulson> yeah, this one is a fairly sizeable leak
[14:09] <chrisccoulson> there's a few others, but none of them on this scale
[14:09] <tedg> chrisccoulson, That's where the memory is allocated, it would seem that we might not be unref'ing a variant that gets created there.
[14:10] <tedg> chrisccoulson, So, it could be our fault :)
[14:10] <chrisccoulson> tedg, yeah, that's the bit i'm trying to figure out :(
[14:11] <tedg> chrisccoulson, Try downgrading glib and see if it goes away.  That'd be a quick check to see if it's in GDBus or something else.
[14:22] <kenvandine> hey seb128
[14:22] <didrocks> hey kenvandine
[14:23] <didrocks> kenvandine: did you read my comments about dee and libunity? :)
[14:23] <kenvandine> not yet
[14:23] <kenvandine> didrocks, did i break something?
[14:23] <seb128> hey kenvandine
[14:23] <seb128> kenvandine, how are you?
[14:23] <kenvandine> :)
[14:23] <kenvandine> tired
[14:23] <kenvandine> and you?
[14:23] <didrocks> kenvandine: daily-build, but otherwise fine, I'll let your scrollback :)
[14:23]  * kenvandine needs more coffee
[14:23] <SpamapS> 14413 clint     20   0 2722m 2.2g 5648 R   93 56.6  72:47.79 /usr/lib/unity/unity-panel-service
[14:23] <SpamapS> run roh
[14:24] <kenvandine> ok
[14:24] <didrocks> SpamapS: restart it, should be fine :)
[14:24] <SpamapS> restart as in, kill and let it be restarted?
[14:24] <kenvandine> didrocks, ack on the 2 commits, sorry
[14:24] <didrocks> SpamapS: right
[14:24] <didrocks> kenvandine: no worry, just keep in mind for next time
[14:25] <kenvandine> didrocks, i didn't propose the libunity change because i think that file is getting generated in the dist isn't it?
[14:25] <didrocks> kenvandine: and on libunity? I saw no merge proposal
[14:25]  * kenvandine would rather it build with the package
[14:25] <didrocks> kenvandine: I think the gir is static there
[14:25] <didrocks> kenvandine: anyway, we can't keep that change :)
[14:25] <kenvandine> ugh
[14:25] <kenvandine> ok... why?
[14:25] <seb128> kenvandine, I'm fine thanks
[14:25] <kenvandine> if i delete the gir and run make
[14:26] <kenvandine> it generates that gir
[14:26] <seb128> kenvandine, seems you have stack of fix commited gwibber bugs on your assigned bugs list, should those be closed?
[14:26] <kenvandine> if the fixed libdee is installed
[14:26] <seb128> kenvandine, some got commited for weeks I guess they are in natty by now?
[14:26] <didrocks> kenvandine: but you fixed a generated file?
[14:26] <kenvandine> seb128, i'll look over them, i think i need to do a release
[14:26] <didrocks> kenvandine: so next file the file will be generated, it will be wrong
[14:26] <didrocks> time*
[14:26] <kenvandine> didrocks, sort of... the file is included in the dist
[14:26] <kenvandine> didrocks, no... it won't
[14:26] <didrocks> hum?
[14:27] <kenvandine> didrocks, the change i made wasn't static
[14:27] <kenvandine> i fixed libdee
[14:27] <kenvandine> and ran make :)
[14:27] <kenvandine> it generated that
[14:27] <didrocks> kenvandine: oh ok :)
[14:27] <didrocks> kenvandine: fine then!
[14:27] <kenvandine> libdee was broken
[14:27] <didrocks> sorry for the noise, thanks ;)
[14:27] <kenvandine> :)
[14:27] <kenvandine> no worries
[14:27] <didrocks> just think about the "2 commits" for daily build
[14:27] <kenvandine> seb128, a gwibber bug fix release is on my todo list for this week
[14:28] <kenvandine> didrocks, noted, i hadn't thought about what that would mean for daily builds
[14:28] <kenvandine> i always do it in one commit :)
[14:28] <didrocks> no worry, thanks for the fix :)
[14:28]  * kenvandine will adapt
[14:29] <kenvandine> vish, i promise i'll get to that upload early today (my time)
[14:29] <kenvandine> :)
[14:29] <seb128> kenvandine, but I don't get it, see for example https://bugs.launchpad.net/gwibber/+bug/522991
[14:29] <ubot2> Launchpad bug 522991 in gwibber "Gwibber does not display recipient of "wall to wall" posts [Facebook]" [Wishlist,Fix committed]
[14:29] <seb128> kenvandine, it was fix commited in octobre, shouldn't it be in the current natty version which is 2 weeks old?
[14:29] <seb128> kenvandine, you are several bugs in similar cases
[14:29] <seb128> kenvandine, https://bugs.launchpad.net/gwibber/+bug/519395
[14:29] <ubot2> Launchpad bug 519395 in gwibber "Flickr doesn't work for some usernames" [Wishlist,Fix committed]
[14:30] <seb128> etc
[14:30] <kenvandine> oh... i'll look over those
[14:30] <seb128> kenvandine, thanks
[14:31] <seb128> trying to bring to sanity to assignedbugs list for desktopers
[14:31] <seb128> kenvandine, i.e https://launchpad.net/~ken-vandine/+assignedbugs
[14:56] <vish> kenvandine: no worries, no hurry for me ;) … seb-128 had commented on that bug so was just letting him know "its ready" :)
[14:59] <Sweetshark> pitti: pushed as lp:~bjoern-michaelsen/ubuntu/natty/openoffice.org-dictionaries/libo-update
[15:11] <Sweetshark> Yay! Blizzard!
[15:15] <chrisccoulson> tedg - so, after looking through the code and at exactly what appears to be leaked, it's almost certainly a signal handler ref'ing a GVariant
[15:15] <chrisccoulson> the words needle and haystack spring to mind here ;)
[15:16] <tedg> chrisccoulson, Did you see my patch for glib regarding those?  They shouldn't cause a leak, but it might be confusing valgrind.
[15:17] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=643624
[15:17] <ubot2> Gnome bug 643624 in gdbus "Can g_variant_unref() on an already free'd variant" [Normal,New]
[15:17] <seb128> tedg, ^
[15:18] <chrisccoulson> oh, i hadn't seen thatr
[15:19] <tedg> seb128, chrisccoulson, Yeah, it looks like it's going to be fixed a different way long term.
[15:19] <tedg> But short term my patch fixes things.
[15:19] <tedg> (in that limited case)
[15:20] <seb128> tedg, well current comment on bz suggest they will backport their fix to the stable serie
[15:20] <seb128> tedg, so we should rather wait on that and backport that commit
[15:21] <tedg> seb128, Yes, but chrisccoulson could use my patch for now to make sure that isn't going to effect what he's debugging.
[15:21] <kenvandine> vish, wow, building humanity takes a while :)
[15:21] <seb128> tedg, right
[15:21] <tedg> seb128, And, also, noting they haven't yet *done* that ;)
[15:21] <seb128> tedg, they have a patch they seem to agree on so it will likely be fixed before natty
[15:21] <seb128> but yeah let's see
[15:28] <chrisccoulson> tedg - hmmm, your patch looks like it fixes a different issue. in the signal emission i'm looking at, the caller of g_signal_emit already calls ref_sink on the variant and then unrefs it afterwards
[15:29] <chrisccoulson> so, this might be a genuine leak ;)
[15:30] <tedg> chrisccoulson, Ah, okay.  Thanks for checking that, wanted to be sure.
[15:36] <seb128> kenvandine, should the ubuntuone-client conflicts on the unity gir be dropped?
[15:37] <kenvandine> yes
[15:37] <kenvandine> dobey said he would do that
[15:37] <kenvandine> dobey, ^^
[15:37] <seb128> that was a stupid thing to do to start with
[15:37] <seb128> the code obviously has fallbacking for when the import is not working, would have been easier to force that test rather than conflict on something other might use
[15:38] <kenvandine> yeah, instead of breaking updates
[15:43] <dobey> yeah i will do that
[15:43] <jibel> mvo, is bug 731724 on your radar. We received a bunch of those today. It looks like an issue with xapian.
[15:43] <ubot2> Launchpad bug 731724 in update-manager-core "software-center crashed with SIGSEGV in __cxa_allocate_exception()" [Undecided,New] https://launchpad.net/bugs/731724
[15:46] <kenvandine> dobey, thx
[15:57] <seb128> kenvandine, btw if you need to update telepathy-glib debian got the upload in their incoming
[15:57] <seb128> kenvandine, just mentioning it so you don't work for nothing
[15:59] <kenvandine> seb128, yup... was planning to sync that
[15:59] <kenvandine> thx
[16:03] <mvo> thanks jibel! I saw it already, but I was not able yet to reproduce
[16:03] <mvo> jibel: I have some rought idea
[16:03] <bcurtiswx> seb128, im getting 2.33.3 ready
[16:03] <seb128> bcurtiswx, you will need the new telepathy-glib then
[16:03] <seb128> it nees .6 and we have .5
[16:04] <bcurtiswx> seb128, yup, someone going to sync it ?
[16:04] <seb128> bcurtiswx, did you read the few lines just before what you said?
[16:04] <bcurtiswx> no, reading now
[16:05] <bcurtiswx> ah, kenvandine thx. could you let me know when that's all set?
[16:05] <zyga> mvo, hi, running software-center --debug segvfaults python on natty i386, right after refresh with days_delta: 0
[16:05] <kenvandine> bcurtiswx, yeah...
[16:06] <seb128> bcurtiswx, kenvandine: build it locally if you need it, we can do a sync when it hits the debian mirror
[16:06] <seb128> kenvandine, i.e I will sync-source it later if you wait
[16:06] <dbarth_> pitti: ping? quick check: are you also effectively working on patching the session menu for https://bugs.launchpad.net/ayatana-design/+bug/727823 or should that be tedg?
[16:06] <kenvandine> seb128, that would be cool
[16:06] <ubot2> Launchpad bug 727823 in indicator-session "Enable Gnome-Control-Center in Unity, and add "System Settings" link to the session indicator menu" [Wishlist,In progress]
[16:06] <kenvandine> i didn't want to start it just yet, need to run an errand at lunch in about 20m :)
[16:07] <pitti> dbarth_: hey
[16:07] <seb128> kenvandine, well just saying don't bother with it, I will direct sync later on
[16:07] <pitti> dbarth_: I'm going to, yes; just didn't start yet
[16:07] <jibel> mvo, That's easy here, let me know if you need more details like better trace.
[16:07] <kenvandine> cool
[16:07] <pitti> dbarth_: that's easy enough for me to handle, let tedg do the guru stuff :)
[16:07] <dbarth_> pitti: thanks for your help, much appreciated
[16:07] <bcurtiswx> well, will I need a bug report for 2.33.3 i can get one set now?
[16:08] <mvo> jibel, zyga: so for your guys just starting it is enough to crash it?
[16:08] <zyga> mvo, the crash is in Xapian:Database::Database(...) ctor
[16:08] <zyga> mvo, yes, the crash is in __cxa_allocate_exception
[16:08] <zyga> mvo, any chance you try to allocate -1 ?
[16:08] <tedg> dbarth_, BTW, I still don't consider the design task done until the spec gets updated.
[16:08] <kenvandine> bcurtiswx, yes please
[16:09] <bcurtiswx> kenvandine, OK i'll get that done now
[16:09] <tedg> dbarth_, We need a way to reject those.  Ridiculous.
[16:09] <kenvandine> bcurtiswx, when you prepare it, ping me and i'll review and sponsor
[16:09] <mvo> zyga: not me personally, the bindings probably. I will look into it after the meeting
[16:09] <bcurtiswx> it'll just need to depwait for tp-glib
[16:09] <mvo> jibel: is it i386 for you as ell?
[16:09] <bcurtiswx> so it shouldn't be hard at all
[16:10] <jibel> mvo, yes
[16:10] <tedg> dbarth_, For instance, pitti has no idea where in the menu it should go :)
[16:10] <pitti> tedg: they said "at the very end"
[16:10] <jibel> mvo, but the master report on amd64
[16:10] <mvo> ok
[16:11] <pitti> tedg: but that's why I'm waiting a bit, to have the design part settled
[16:11] <mvo> thanks!
[16:11] <tedg> pitti, Ah, I see that now.
[16:11] <tedg> The spec should be updated though :)
[16:18] <pitti> Sweetshark: hm, you didn't use bzr merge-upstream, so the bzr doesn't have the orig.tar.gz
[16:18] <pitti> Sweetshark: no need to re-do it now, but I won't actually push it to lp:ubuntu/, but let the package importer sort it out
[16:19] <bcurtiswx> kenvandine, https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/732077 all set
[16:19] <ubot2> Launchpad bug 732077 in empathy "Please update empathy natty to 2.33.3" [Wishlist,In progress]
[16:19] <kenvandine> thx
[16:19] <bcurtiswx> well actually i need to add that bug # into the changelog :X
[16:19] <bcurtiswx> i'll push that in a sec
[16:22] <Sweetshark> pitti: I dont know if there was any upstream branch at all. Given that, how can I use merge-upstream?
[16:23] <pitti> Sweetshark: it just takes a tarball (Debian's orig.tar.gz) and a version number; you can optionally specify an upstream bzr branch, but that's not the common case for our packages
[16:24] <Sweetshark> pitti: is theis stuff documented somewhere?
[16:24] <pitti> Sweetshark: yes, on https://wiki.ubuntu.com/DistributedDevelopment/
[16:25] <pitti> Sweetshark: in particular, https://wiki.ubuntu.com/DistributedDevelopment/Documentation/NewUpstreamVersion
[16:26] <Sweetshark> bookmarked. I had only "TrackingUpstream" on the bzr wiki
[16:26] <mvo> jibel: if you can reproduce it, could you please try http://paste.ubuntu.com/577903/ ?
[16:28] <mvo> or zyga: http://paste.ubuntu.com/577903/ <- does that help with the crash?
[16:29] <zyga> mvo, checking
[16:29] <seb128> tedg, mterry, do you have any clue if bug #727892 is appmenu-gtk or libdbusmenu?
[16:29] <ubot2> Launchpad bug 727892 in appmenu-gtk "totem's sound>languages is empty" [Undecided,New] https://launchpad.net/bugs/727892
[16:29] <jibel> mvo, sure, as soon as my gvim window stops being invisible :/
[16:30] <mterry> seb128, that's likely libdbusmenu
[16:30] <seb128> mterry, ok thanks, reassigned there
[16:32] <jibel> mvo, which version of software-center should I apply this patch to ? There's no such code in my version of s-c
[16:33] <zyga> mvo, same here,
[16:33] <zyga> mvo, I have 3.1.23.1
[16:33] <jibel> mvo, same version here
[16:33] <mvo> oh
[16:34]  * mvo scratches head
[16:34] <mvo> then I'm on the wrong track, sorry for the noise
[16:34] <mvo> I thought it was a locking issue with code that got added recently, but apparently I have not uploaded that yet
[16:34] <mvo> maybe that is the fix ;)
[16:44] <mvo> jibel: could you please do a "bzr get lp:software-center ; cd softare-cener ; ./software-center" and see if that crashes too?
[16:44] <jibel> mvo, sure
[16:46] <mvo> mpt: did you had a chance to read about the "display commandline executables for technical items" mail from yesterday (from nzmm)
[16:46] <mvo> ?
[16:47] <mpt> mvo, not yet
[16:47] <mvo> ok, thanks
[16:48] <jibel> mvo, yes it crashes, segfault (core dumped). I guess that it is not the expected result.
[16:48] <mvo> pitti: do you have a idea why there is no retrace output for #731724 ?
[16:48] <mvo> jibel: well, at leeast its consitent with the rest
[16:49] <mvo> jibel: what kind of machine is that, limited RAM or anything special like that?
[16:52] <seb128> mvo, because the submitter didn't send a .crash with the crashdump it seems
[16:52] <jibel> mvo, this one is a i386 testing vm with 1GB of memory allocated, but I can reproduce on the host which is an amd64 with 12GB of RAM.
[16:53] <mvo> thanks seb128
[16:53]  * mvo scratches head
[16:54]  * jibel is installing symbols to get a better trace.
[17:04] <seb128> mterry, you won bug #621301 as well
[17:04] <ubot2> Launchpad bug 621301 in libdbusmenu "Underscores missing in menu item text" [Undecided,New] https://launchpad.net/bugs/621301
[17:05] <seb128> mterry, it's low priority but I think it's around some code you hacked on recently and you might have a clue about it
[17:06] <mterry> seb128, yar
[17:06] <tkamppeter> jasoncwarner, hi
[17:12] <bentech4you> my wifi is not working..how to fix that.?
[17:12] <mvo> jibel: sorry, still no luck, tried it in a VM now. I have dinner and check it out again
[17:13] <bentech4you> i tried to install the firmware..that also failed
[17:14] <jibel> mvo, bug 732128 includes a better trace
[17:14] <ubot2> jibel: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/732128)
[17:17] <bcurtiswx> bentech4you, ask that in #ubuntu thats the support channel :)
[17:21] <tremolux> jibel: which is the bug that includes a better trace?
[17:22] <jibel> tremolux, bug 732128
[17:22] <ubot2> jibel: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/732128)
[17:22] <jibel> tremolux, which is now public
[17:23] <tremolux> jibel: ah, thanks!
[17:24] <jibel> tremolux, http://launchpadlibrarian.net/66003285/ThreadStacktrace.txt
[17:24] <jibel> tremolux, the coredump is attached if you want to play with gdb
[17:24] <tremolux> jibel: thanks!
[17:29] <pitti> mvo: could have been sent as reduced report perhaps (without coredump)?
[17:29] <bentech4you> please check this http://pastebin.com/1nbTnrp6..please help me to solve my wifi issue
[17:29] <pitti> mvo: bug 731681 has a good one
[17:29] <ubot2> pitti: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/731681)
[17:30] <cyphermox> bentech4you, please ask in #ubuntu , but essentially, what this means is your chipset isn't supported by that driver
[17:31] <bentech4you> i asked..but i didn't get any help from there
[17:31] <bentech4you> no this the same driver i installed on my other linux
[17:32] <bentech4you> i got this command from that driver's readme.txt file
[17:33] <bentech4you> also in my additional drivers ,t  it shows that driver is active but not currently in use"
[17:33] <cyphermox> bentech4you, it's most likely outdated. what you should do would be to make sure you're connected to wired, then use the Restricted drivers tool under System -> Administration to install the Broadcom STA driver properly. but like I said, you really should be asking in #ubuntu, not here. This channel is for development
[17:34] <cyphermox> that would be because you need to reboot after installing the driver --- or that the driver doesn't support your wifi card
[18:42] <pitti> good night everyone!
[18:42] <bcurtiswx> nite pitti
[18:43] <tremolux> 'night pitti
[18:47] <bcurtiswx> kenvandine, when u get a minute, run pithos listen to a song and while listening load banshee.  my volume gets set to 0 upon banshee  loading
[18:56] <kenvandine> bcurtiswx, ok
[19:04] <mvo> jibel: if you are still here, is there anything printed on the terminal before it crashes? anything odd in:
[19:05] <mvo> ls -ld ~/.cache/software-center/software-center-agent.db /var/cache/apt-xapian-index/index.* /var/lib/apt-xapian-index/index
[19:05] <mvo> jibel: I looked at the source and it seems it raises this when it can't stat the database path
[20:13] <mterry> do we have any xulrunner or eclipse experts hanging out?  https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/728825 is really chafing my caboose
[20:13] <ubot2> Launchpad bug 728825 in eclipse "Eclipse cannot start: "java.lang.UnsatisfiedLinkError: no swt-gtk-3557 or swt-gtk"" [Critical,Confirmed]
[20:42] <seb128> mterry, you want to talk to chrisccoulson
[20:42] <seb128> well at least for xulrunner
[20:42] <seb128> dunno about eclipse, maybe doko has a clue about it but out of that...
[20:44] <chrisccoulson> it's a linker problem
[20:44] <chrisccoulson> i bet if you rebuild swt-gtk now without --as-needed, it works again ;)
[20:44] <chrisccoulson> i tried it a few weeks ago, and that seemed to fix it
[20:54] <jibel> mvo, here is what is printed on the screen when I launch the bzr version http://pastebin.ubuntu.com/578011/ , the version from the repo doesn't output anything.
[20:54] <jibel> mvo, downgrading libgl1-mesa-glx fixes the problem on i386.
[20:55] <mterry> chrisccoulson, ooh, awesome, will try
[20:55] <mvo> thanks jibel
[20:56] <mvo> jibel: its seems the -glx change is really the trigger, its consistent on my machine and in a vm
[20:56] <tremolux> jibel: it fixes it for me too (I commented the bug)
[20:59] <jibel> mvo, I found at least one other app affected: bug 731820
[20:59] <ubot2> Launchpad bug 731820 in deluge "deluge-gtk crashed with SIGSEGV in __cxa_allocate_exception()" [Undecided,New] https://launchpad.net/bugs/731820
[21:00] <tremolux> jibel: and after upgrading libgl1-mesa-glx agan, the crash returns (if the condition of an empty ./data/xapian directory, that is the condition for the error, is recreated)
[21:00] <mvo> I wonder what is special about s-c to trigger it
[22:14] <bigon> could someone merge gnome-pkg-tools ?
[22:44] <ari-tczew> bigon: I could do it tomorrow, but I need sponsorship :P
[22:45] <bigon> well same here actually :p