[00:00]  * LimCore facepalms @  
[00:00]  * LimCore facepalms @  "first reported on 2007-12"
[00:03] <LimCore> I written to upstream now
[01:32] <Awsoonn> what package contains the 'Add Printer wizard' in kubuntu?
[01:57] <bdmurray> Awsoonn: system-config-printer
[02:03] <Awsoonn> bdmurray: thank you~
[02:06] <LimCore> bdmurray: btw I consider that a bug
[02:07] <LimCore> it should be installed by default imho
[02:07] <LimCore> same as missing pages in kcontrol center
[02:07] <persia> LimCore: If you consider something a bug, best to reserve a bug number :)
[03:03] <CarlFK> play yellowaudio.wav  - play soxio: Failed reading `yellowaudio.wav': unknown file type `auto'
[03:03] <CarlFK> but aplay yellowaudio.wav  - Playing WAVE 'yellowaudio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono
[03:03] <CarlFK> play says SUPPORTED FILE FORMATS: m3u pls
[03:04] <CarlFK> seems kinda odd - am i missing something ?
[03:05] <CarlFK> https://bugs.launchpad.net/ubuntu/hardy/+source/sox no open bugs.
[03:05] <CarlFK> i can't belive this is a bug
[03:18] <CarlFK> "﻿libsox-fmt-all"
[04:47] <mrooney> can anyone verify if clicking the thumbnail at the top of http://tinyurl.com/6hhmdy causes firefox to ask if you want to open or save the image? and if so, if this is a bug?
[04:50] <persia> mrooney: Trying a parallel test in epiphany, it opens it in a helper application (as I've likely told it not to ask in the past).  I'd consider it not to be a bug: users can tell the application if they want to always choose one or the other, and it can otherwise be difficult to easily open objects in one's editor/viewer of choice.
[04:54] <mrooney> persia: well the bug is that it's an image, shouldn't it just display it like any other image?
[04:55] <persia> mrooney: No?  For me, it opens in my image processor.  That way I can blow it up, transform it, save it, etc.  I prefer that to viewing it in the browser.
[04:55] <mrooney> oh is that how yours is always configured?
[04:55] <persia> Perhaps there is a bug that it should offer to display, open, or save it.
[04:55] <mrooney> for me all images are opened in the browser
[04:55] <persia> mrooney: For some media types, but not all.
[04:55] <mrooney> except this case
[04:56] <persia> mrooney: Interesting.  Maybe the markup is different?
[04:57] <persia> Blah.  It's all Javascript, and I don't feel like opening a parser.
[04:58] <ruiboon> mrooney: the server header of that link states 'Content-Disposition: attachment'
[04:58] <ruiboon> so firefox is correct to offer to save it
[04:59] <mrooney> ruiboon: oh I see, I would have to yell at google then I guess
[06:50] <theJamAbides> Guys, just wanted to say that I'm excited to get started with helping out the community... but as I've just decided... it's also bedtime.  So see you all in the near future!
[08:36] <Balachmar> Hi, I have reported the following bug a while ago, and I want to see whether I can do anything to get it fixed. https://bugs.launchpad.net/ubuntu/+bug/231662
[08:38] <Balachmar> Since this is a regression, (because it worked fine in gutsy) I assume that a fix shouldn't be too hard. Although that is probably a wrong assumption :)
[12:55] <hggdh> seb128, ping and good morning (at least for me)
[13:31] <sectech> How hard would it be to make  a python script to get the stats of how many bugs you touched per day and set to different statuses? (just a question based off curiosity)
[14:00]  * heno does OOo SRU verifications today, even though it's not actually on the OOo bug day list
[14:50] <qense> hello
[14:52] <LimCore> hi gen
[14:52] <LimCore> hi qense
[14:57] <heno> pedro_: Did we consider adding an SRU verification section to the bug day pages?
[14:57] <heno> it's not applicable for all bug days of course
[14:58] <heno> but for OOo today there were 10 pending verifications
[14:58] <pedro_> heno: it would be indeed something nice to have there, yes
[14:59] <heno> well, we might of course do an SRU day soonish anyway :)
[14:59] <pedro_> hopefully next week ;-)
[15:00] <seb128> what do you call sru day?
[15:00] <heno> pedro_: rock! (got your email, thanks)
[15:01] <heno> seb128: each sru should have a bug, so it can still be a bug day
[15:01] <seb128> that seems to be a small bug day
[15:01] <seb128> there is not so many bugs to verify
[15:01] <heno> btw, it would be great if anyone could reproduce bug 224358 - few people seem able to
[15:02] <seb128> around 30 bugs seem a low number for a bug day
[15:02] <heno> but there is a screencast of it so it's clearly real
[15:02] <seb128> especially than some are crasher not easy to trigger
[15:02] <heno> seb128: I see a few more on this list http://people.ubuntu.com/~sbeattie/sru_todo.html
[15:02] <pedro_> seb128: there's also universe which have a few of them
[15:03] <heno> and we were talking about including universe srus too
[15:03] <seb128> alright, you are the guys running bug days
[15:04] <seb128> but I think it's not a lot for a day
[15:04] <seb128> I look regularly at the list to verify sru bugs and most of those not verified require a special setup or have no easy testcase to be triggered so are not easy to verify
[15:06] <heno> writing test cases would be one of the bug improvement tasks
[15:10] <seb128> heno: speaking for my bugs, those which have no testcase usually are because there is no testcase
[15:10] <seb128> heno: could be new stable upstream version where no specific bug is fixed, could be a crash which happens every months and that we have no idea how to trigger
[15:12] <heno> right
[15:12] <seb128> also not sure how likely contributors will set up an ltsp installation only to verify those
[15:12] <heno> stgraber would :)
[15:12] <seb128> ;-)
[15:12] <seb128> I think that bugs which are not verified are usually not easy to verify
[15:13] <seb128> otherwise somebody in the team give those a try quickly
[15:13] <seb128> ie, I know that pedro verify quickly things easy to try
[15:13] <seb128> and pitti does the same
[15:13] <heno> we'd like to get people into doing some verifications though, and their setups can become more advanced as they learn
[15:13] <seb128> so the things on the list would be mostly tricky things
[15:13] <seb128> which might not be ideal to bring contributors
[15:14] <heno> seb128: well desktop is a special case because you guys rock on bugs ;)
[15:14] <heno> but I'm working my way through OOo sru verifications now, and they're not that complex
[15:14] <heno> just take a bit of time
[15:14] <LimCore> hi heno
[15:15] <LimCore> heno: if you are interested in OOo bugs, I have mine own bug that I need confirmation from
[15:15] <heno> hey LimCore
[15:15] <LimCore> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/179230
[15:15] <heno> LimCore: I can try
[15:15] <bddebian> Boo
[15:15] <LimCore> would be nice if someone can confirm its 1 minute. But follow the steps exactly, including closing and re-opening the document
[15:15]  * LimCore bbl
[15:15] <LimCore> read the second description not the original one
[15:18] <seb128> heno: right, there is likely some bugs that could be verified by contributors there, I just wanted to point that there is likely not a lot of easy tasks for a bug day
[15:18] <seb128> enough comments from me on the topic ;-)
[15:27] <afflux> hi
[15:31] <heno> LimCore: confirmed
[15:31] <LimCore> heno: thanks.  Can you perhaps also confirm in upstream (link is there)?    They want to test on native version, Im downlading now;   bbl
[16:38] <heno> calc: https://bugs.launchpad.net/ubuntu/hardy/+source/openoffice.org/+bug/237371/comments/12
[16:42] <calc> heno: thanks :)
[16:42] <calc> hopefully it is promoted to updates soon :)
[16:43] <NickGarvey> if there is a problem in the way a package gets removed with apt-get, where do I go to fix that?  When the start-stop-daemon stops the program, it needs a -o, but I'm not sure where to add that -o in order to apply a fix in my bug report
[16:43] <heno> yep, it looks good
[16:43] <NickGarvey> (I hope this is the right place to ask this)
[16:44] <james_w> NickGarvey: that will be the prerm or the postrm
[16:44] <james_w> (if you don't know what I mean by that then I can take a few steps back)
[16:45] <NickGarvey> I believe I do, I have the source file and that is under the /debian directory
[17:00] <NickGarvey> james_w: worked, thanks a lot
[17:00] <james_w> NickGarvey: have you posted a patch to the bug report?
[17:00] <NickGarvey> not yet, but I'm about to
[17:00] <james_w> I'll do the necessary to get it uploaded if you provide the bug number.
[17:01] <james_w> great, thanks.
[17:05] <NickGarvey> #240720
[17:06] <james_w> bug 240720
[17:07] <james_w> I'm just looking to see if there are any ubuntu devs interested in the package
[17:08] <james_w> ah, the Debian maintainer is, great.
[17:10] <james_w> I can't find him on IRC at the moment, I think we should give him a couple of days to respond.
[17:10] <james_w> if he doesn't I'll forward to Debian as a prod, is that ok with you?
[17:11] <NickGarvey> absolutely, thanks a lot
[17:11] <james_w> no problem, thanks for writing the patch.
[17:57] <bdmurray> calc: is bug 239022 expected behavior?  dragging the image just seems to grab the image properties not the image itself
[17:59] <techno_freak> bddebian, it looks like it drags and drops the html for the image, rather than the image
[18:00] <bdmurray> right, I'm just not sure if that is expected behavior or not
[18:00] <bdmurray> You can get the image in by right clicking and choosing copy and then pasting
[18:00] <techno_freak> ya
[18:01] <techno_freak> bddebian, doing the same to desktop creates a link to the image, rather than copying the image there
[18:02] <techno_freak> so when you drag the image from FF, you are just copying the link to the image than the image itself
[18:02] <calc> bdmurray: not sure, it probably should be treated as a bug, a wishlist at worst
[18:02] <calc> dragging and dropping into gimp pastes the image
[18:03] <calc> dragging and dropping into gedit gives the url without the html bit
[18:03] <techno_freak> i remember it was working as expected in FF2, i have drag dropped images to the desktop
[18:03] <calc> it might be a bug in the way firefox DnD, not really sure which bit is at fault
[18:04] <calc> but after verifying if it happens on upstream OOo i can send it to them
[18:05] <techno_freak> gimp would have done 'open image from location' rather
[18:09] <calc> \
[18:10] <calc> sorry my 9mo old is attacking my keyboard
[18:36] <sectech> Can someone review bug #230850...   Let me know what your opinion is....
[18:38] <sectech> As far as I can tell this bug will stay at "confirmed" (the reporter set it to that) forever because it seems lmsensors changed there config file around a bit intentionally.
[18:40] <james_w> hi sectech
[18:40] <james_w> so libsensors3 no longer reads that line? (the one that was in the last comment)
[18:41] <thekorn> bdmurray, hi, i will have a look at the debian BTS soap-interface over the next weekend, and answer to your mail, then I should be able to say what'S possible and how
[18:43] <sectech> james_w,  It must read it differently according to Alex Murray....
[18:44] <sectech> Of course it's going to read differently when the reporter changes the calculations around on the line
[18:44] <sectech> sorry for the delays... building maintenance is here to fix our sink
[18:44] <sectech> lol
[18:44] <james_w> I'm not sure what to do with it really.
[18:45] <james_w> Alex seems to suggest that the sensor name they are using may be wrong,
[18:45] <james_w> I don't know anything about sensors though, so I'm stumped for what to ask.
[18:45] <james_w> I'm heading out now anyway, sorry to leave mid-conversation.
[18:45] <sectech> That's the thing though... Is it reading it _wrong_ of just differently...
[18:45] <sectech> It's okay
[18:54] <bdmurray> thekorn: okay, great.  I might have found one for fedora too - I'm still experimenting with that.
[19:22] <calc> why isn't apport enabled by default?
[19:22] <bdmurray> because Hardy is a stable release now
[19:22] <calc> oh ok, so its just enabled during dev stage?
[19:23] <bdmurray> calc: yes that is correct by default
[19:23] <calc> ok
[19:24] <bdmurray> blooddrunk: let's take bug 238822 as an example
[19:24] <blooddrunk> k
[19:25] <bdmurray> We know they are using Hardy and which version of openoffice.org they are using
[19:25] <bdmurray> It looks like there is enough information to test the bug too
[19:26] <LimCore> I see lots of effort to fix OOo bugs?
[19:26] <LimCore> that indeed would be nice
[19:26] <LimCore> while at it, can ubuntu finally unnoobify it's fonts?   Fonts seem to default ot bitstream vera, which is broken
[19:27] <LimCore> in desktop (i.e. KDE),  and also it seems to be the default in OOo etc.. can we fix this, bdmurray?
[19:27] <bdmurray> LimCore: that sounds like a really disruptive change which would require a fair bit of discussion
[19:28] <LimCore> bdmurray: why its disruptive?
[19:28] <bdmurray> because it would impact every user
[19:28] <LimCore> well, bitstream vera is broken
[19:29] <LimCore> common glyps like either polish ąćłż or  german o-umlaut dont exist there (WTF O_o)
[19:29]  * LimCore googles his bug report
[19:31] <LimCore> https://bugs.launchpad.net/ubuntu/+bug/179157
[19:31] <LimCore> bdmurray:  see:  https://bugs.launchpad.net/ubuntu/+source/ttf-bitstream-vera/+bug/11180   and  attached PDF:  http://launchpadlibrarian.net/11075847/linux_fonts_test_1.pdf
[19:32] <bdmurray> blooddrunk: have you had any luck experimenting with bug 238822?
[19:33] <LimCore> ok, this seems to be fixed now, bdmurray.
[19:35] <sbeattie> bdmurray: got a moment?
[19:36] <sbeattie> ... for a bug query qeustion
[19:36] <bdmurray> sbeattie: okay
[19:37] <sbeattie> Given this query https://bugs.launchpad.net/ubuntu/+bugs?orderby=-importance&search=Search&field.subscriber=sru-verification&field.component=1&field.omit_dupes=on
[19:37] <sbeattie> Any idea why https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221673 doesn't show up?
[19:37] <sbeattie> ... in that list?
[19:37] <bdmurray> sbeattie: it's fix released for ubuntu and fix committed for Hardy
[19:38] <bdmurray> so because it is fix released it won't show up
[19:40] <sbeattie> Hrm. So how do I get it to show up?
[19:41] <bdmurray> sbeattie: throw in the release in your url
[19:42] <bdmurray> like ubuntu/hardy/+bugs
[19:43] <sbeattie> Ah!
[19:43] <sbeattie> Weird, the list it generates appears to have every entry duplicated.
[19:44] <bdmurray> you can't win every time
[19:45] <sbeattie> I'm personally shooting for 10%.
[19:45] <sbeattie> Thanks for the help, I can strip out dupes.
[19:46] <bdmurray> is it really in there?
[19:47] <sbeattie> Is what really in there?
[19:47] <bdmurray> oh, the bug you were looking for
[19:47] <sbeattie> 221673 shows up on the second page.
[19:48] <bdmurray> cool
[19:48] <sbeattie> bdmurray: is there any interest in making the component available in the task class in python-launchpad-bugs?
[19:48]  * calc is around if anyone has OOo questions :)
[19:49] <bdmurray> calc: did you see my one about bug 239022 is that behavior expected?
[19:50] <calc> bdmurray: ah i'll follow up to it
[19:51] <calc> bdmurray: happens for me on firefox 2 also
[19:52] <bdmurray> it happened for me too with abiword so I'm not sure what should happen
[19:54] <calc> i'm adding firefox-3.0 to the bug to get input from alexander about it
[19:54] <calc> since it appears to affect more than just OOo
[19:55] <sbeattie> bdmurray: or would it just be smarter to use python-apt and query the archives directly for where the package is located?
[19:56] <bdmurray> sbeattie: I don't recall hearing what exactly you were trying to do.
[19:56] <sbeattie> Sorry, I'm trying to break down SRU bugs by component/repo.
[19:57] <bdmurray> I'd check with pitti to find out what he does, but I think using the package in -proposed makes the most sense because a bug report could have invalid tasks affecting a package.
[19:58] <bdmurray> calc: so are your running upstream OOo and our version concurrently?
[19:59] <sbeattie> The python-launchpad-bugs LPTask class could export the component as reported by launchpad (it currently doesn't), but I am unsure how much to trust LP in that regard.
[20:00] <sbeattie> pitti greps the -proposed changelogs directly for LP bugs and reports based off that; I want to do that as well, but I also want to catch bugs that might be missed by that.
[20:01] <greg-g> sbeattie: the list of bugs that ubuntu-motu is subscribed to?
[20:01] <greg-g> would that help?
[20:01] <greg-g> https://bugs.launchpad.net/~motu-sru
[20:01] <sbeattie> greg-g: for motu srus, that's what LaserJock is doing.
[20:01] <greg-g> erm, -sru, is what I mean
[20:01] <greg-g> that link is correct, my sentence is not
[20:02] <calc> bdmurray: i have two vmware images one with 2.4.0 (need to update to 2.4.1) and one with 3.0 beta
[20:02] <calc> plus the current 2.4.1-1ubuntu1 on my main system
[20:02] <calc> and 2.4.0-3ubuntu6 amd64 on my other system
[20:02] <bdmurray> calc: okay, is there a way to identify bugs that need forwarding?
[20:03] <sbeattie> greg-g: I'm basing off of sru-verification to try to capture SRUs for main.
[20:03] <calc> best way is to reproduce it on upstream version 2.4.1 or 3.0beta
[20:03] <calc> just noting how to reproduce the bug in the report is good enough though and then pointing me to it (or marking it triaged)
[20:04] <calc> since i already have everything setup i can verify it is a upstream issue or not
[20:04] <bdmurray> calc: okay bug 238822 is triaged now
[20:05] <calc> looking at it
[20:05] <calc> looks funny :)
[20:07] <bdmurray> that's what I thought. ;)
[20:08]  * calc looking at it under 3.0 now
[20:09] <calc> shows up the same under 3.0beta
[20:10] <calc> so its not ubuntu/ooo-build issue
[20:12] <calc> who is "Ubuntu Desktop Bugs"?
[20:15] <pedro_> calc: usually seb128
[20:16] <calc> pedro_: ah ok
[20:21]  * pochu hugs pedro_ :)
[20:21]  * pochu hugs bdmurray too
[20:21]  * pedro_ hugs pochu back
[20:22] <pochu> pedro_: how is everything going? I haven't been on IRC a lot for the last couple of weeks due to exams...
[20:25] <pedro_> pochu: everything is going pretty good, how about you?.  Right i recall you told me about it during UDS, did you managed to finish the program (it was a game right?)?
[20:26] <pochu> pedro_: yeah, I have to write a tetris in assembly, and I've just almost finished it! :)
[20:26] <pochu> but I still have two exams to do...
[20:26] <pochu> nice to know things are fine :)
[20:28] <calc> 49.69% triaged, yipee :)
[20:28] <calc> almost 50%
[20:37] <sectech> bdmurray,  Do you have a python script that gives a triagers stats? Like how many bugs he/she touched, triaged, rejected..etc?
[20:48] <bdmurray> sectech: yesh, I have one that can parse the mailing list for that
[20:54] <sectech> bdmurray, could I have it? :)
[20:55] <bdmurray> sectech: sure, you need to have the mbox archive for it to be useful though
[20:56] <sectech> ahh ok
[20:56] <sectech> regardless... brbr
[20:56] <sectech> brb
[21:09] <afflux> seb128: for bug 235698, I'm probably not able to provide any valgrind logs since the crash seems to occur very early around logging in. Any ideas?
[21:13] <seb128> afflux: rename the binary and use a small wrapper using the same name and calling valgrind on the real binary?
[21:13] <afflux> could work. will try that.
[21:13] <afflux> thanks
[21:13] <seb128> you are welcome
[21:15] <bdmurray> calc: the test document in bug 229809 crashes openoffice for me but that is not what the bug is about
[21:19] <calc> lookint
[21:19] <bdmurray> whoops, my bad.  openoffice was trying to recover a different document.
[21:20] <calc> bdmurray: opens fine for me
[21:20] <calc> i'll see what happens when i try print to pdf
[21:21] <calc> printed to pdf fine for me
[21:21] <bdmurray> I've an HP OfficeJet that prints it fine
[21:21] <calc> this is on 2.4.1-1ubuntu1 though
[21:21] <bdmurray> right, I've the same
[21:21] <calc> so it might have fixed the problem, i don't have a standard hardy install here
[21:22] <calc> do you want to follow up to the bug, or me?
[21:22] <bdmurray> saivann: that's your bug right?  could you try -proposed?
[21:22] <saivann> bdmurray : looking..
[21:24] <saivann> bdmurray : Oh thanks, I'll try it right now, I did not receive your comments
[21:24] <calc> for some reason some of the bug mails i thought i would be getting haven't shown up in my box either
[21:24] <calc> but i am getting at least some of them
[21:24] <calc> maybe lp is just a bit slow
[21:25] <calc> like i haven't seen the 229809 message bdmurray sent yet
[21:26] <calc> oh i see now
[21:26] <calc> i somehow had my folder mis-sorted
[21:26] <calc> lots of them popped up now
[21:27] <bdmurray> I don't understand what subtotal(9;a1:a5) should do in bug 239774
[21:28] <calc> bdmurray: for ones like that i ask for an example file and step by step instructions, heh
[21:28] <calc> there are lots of parts of OOo I don't know about being as it is so huge
[21:29] <bdmurray> right, well I gave it a go and will ask then
[21:30] <calc> i'm glad i got the launchpad-integration bits in though, it makes it a lot easier to see what is going on
[21:30] <bdmurray> yeah, absolutely
[21:31] <calc> apport-bug's are much better than what we had up to a few months ago :)
[21:32] <saivann> bdmurray : I was able to reproduce the bug until I updated to -proposed, so I did set it to fix released. Do you want to set a nomination for hardy?
[21:32] <bdmurray> saivann: No, that package should transition normally to -updates.
[21:32] <saivann> bdmurray : Thanks
[21:32] <bdmurray> Thank you!
[21:42] <bdmurray> sectech: I see you closed bug 239742, which seems fine, but you might also mention the url https://help.ubuntu.com/community/ReportingBugs
[21:43] <sectech> One sec I'll pull it up
[21:43] <sectech> Oh
[21:44] <sectech> Yeah I did that because I thought an apport report would save the reporter from manually getting a lot of information...
[21:45] <sectech> bdmurray,  What did you want me to say about that link?
[21:45] <bdmurray> Yes, I think that while it could be intrepreted as "hard-core" is fine.  Putting the link to that documentation might help the reporter follow the instructions more easily.
[21:45] <sectech> Ahh okay
[21:47] <sectech> bdmurray,  updated...
[21:49] <bdmurray> calc: what is an odf file?
[21:49] <afflux> bdmurray: a formula
[21:50] <calc> http://filext.com/file-extension/ODF
[21:50] <calc> that site is usually pretty good for any file type you find
[21:51] <afflux> (I just typed "odf" in the adress bar in firefox which took me directly to wikipedia :P)
[21:51] <bdmurray> brilliant
[21:53] <afflux> hehe
[21:54] <afflux> going to bed now, good night ;)
[22:04]  * calc hugs everyone for the help with OOo bugs :-)
[22:05]  * jpds hugs the rest of the room to make everyone feel loved.
[22:06] <calc> bdmurray: btw bug 238551 is the infamous fontconfig can't write to future dated dirs (or something like that) bug
[22:07] <bdmurray> calc: okay
[22:07] <calc> been getting bugs about that for years
[22:22] <bdmurray> calc: bug 238548 might be close able
[22:47] <heno> calc: one day he future will arrive and you wont get those dir bugs any more because it will magically just work :)
[22:49] <calc> grr lp going down in ~ 10m
[22:50] <heno> meh
[22:55] <calc> guess its a good excuse to stop working for the day :-\
[22:57] <calc> net 15 bugs down, not bad, 20 less new bugs as well :)
[23:04] <calc> lp dead now for 5 hours
[23:06] <bdmurray> it never takes that long...
[23:13] <calc> they had to cancel a conversion once because it took a lot longer, heh
[23:13] <calc> but probably not usual
[23:13] <calc> wow i can't do any bug work for the next three days after 5pm :-\
[23:31] <bdmurray> calc: that's not how I read the announcement - malone is only affected today
[23:35]  * greg-g nods
[23:38] <visik7> hi
[23:38] <visik7> I can reproduce a bug on epiphany but I dunno if it appears only on my machine or not
[23:38] <visik7> anyone could help me ?
[23:41] <bdmurray> visik7: which release of ubuntu and package version of epiphany do you have?
[23:41] <visik7> ubuntu 8.04
[23:42] <visik7> epiphany gecko 2.22.2-0ubuntu0.8.04.2
[23:42] <visik7> there are 2 bugs one that I was able to reproduce on another machine the other not
[23:42] <visik7> could you test it ?
[23:43] <bdmurray> visik7: sure
[23:43] <visik7> I've also try to downgrade epiphany and its dependancies excluding -proposed
[23:43] <visik7> and -updates
[23:43] <visik7> but the bug persist
[23:43] <visik7> so ok
[23:43] <visik7> go to
[23:43] <visik7> www.cerimages.com
[23:43] <visik7> and hit ctrl++
[23:43] <visik7> should segfault
[23:43] <visik7> I dunno why with that site
[23:43] <visik7> with other it doesn't
[23:44] <visik7> do you got the crash ?
[23:44] <bdmurray> yes, I did
[23:45] <visik7> good
[23:45] <visik7> at least it's not only mine
[23:45] <visik7> the other bug is this I got epiphany crash simply going on www.meebo.com
[23:45] <visik7> it exits with Gtk:ERROR:(/build/buildd/gtk+2.0-2.12.9/gtk/gtkplug.c:182):gtk_plug_set_is_child: assertion failed: (!GTK_WIDGET (plug)->parent)
[23:46] <visik7> also here I've tested with various verison of epiphany and its dependancies with and without extensions
[23:46] <visik7> and with more than one user
[23:46] <visik7> but I was unable to reproduce on another machine
[23:47] <bdmurray> just at the home page?
[23:47] <visik7> yes
[23:47] <visik7> just the homepage
[23:47] <bdmurray> that works for me
[23:47] <visik7> I really dunno what should be
[23:48] <visik7> moreover seems that the bug is inside the gtk
[23:48] <visik7> and not inside epiphany
[23:49] <visik7> I got the same crash with firefox3
[23:50] <visik7> do you got some crash with ff3 ?
[23:50] <bdmurray> I'm sorry which crash with ff3?
[23:51] <visik7> meebo
[23:51] <bdmurray> I didn't experience a meebo crash with epiphany
[23:51] <visik7> neither with ff3 ?
[23:52] <bdmurray> not with ff3 either
[23:53] <visik7> must be some of my libraries
[23:53] <visik7> the strange thing is that
[23:53] <visik7> if I run a firefox instance
[23:53] <visik7> or (epiphany)
[23:53] <visik7> and then run epiphany www.meebo.com
[23:53] <visik7> it doesn't crash
[23:54] <visik7> if I've no ff3 or epiphany session opened before it crash
[23:54] <visik7> are your epiphany/ff3 all closed ?
[23:58] <visik7> bdmurray: ?