[07:08] <pitti> Good morning
[07:10] <proppy> oy
[09:55] <seb128> hey mvo
[09:58] <mvo> hey seb128
[09:58] <seb128> mvo: so you broke the bling on my laptop between rc and jaunty ;-)
[09:59] <seb128> mvo: I will find you at uds!
[09:59] <seb128> or before ;-)
[09:59] <mvo> seb128: *cough*
[09:59] <mvo> seb128: I did
[10:00] <seb128> not nice
[10:00] <mvo> but ... but ... they forced me to
[10:00] <seb128> I don't have a box where jaunty does bling now
[10:00] <mvo> bling for everyone!
[10:00] <mvo> seb128: didn't you say you get freezes when you remove the virtual desktop size? or was that just slowdown?
[10:00] <seb128> yet, not for me apparently, my desktop has too new ati and my laptop has been broken for now good reason ;-)
[10:00] <seb128> slowness
[10:01] <seb128> I didn't get any freeze yet on this box (and I'm using it full time to work)
[10:02] <seb128> nobody seems to be interested to try if the virtual thing fix their hang apparently though
[11:18] <pitti> rickspencer3: I don't think we need https://blueprints.edge.launchpad.net/ubuntu/+spec/gdm2
[11:19] <pitti> rickspencer3: I thought we already decided that we'll move when we have the facebrowser?
[11:19] <pitti> seb128: ^ ?
[11:25] <seb128> pitti: agreed
[12:02] <mvo> seb128: re-freeze> supsend-resume does not make a difference for you?
[12:03] <asac> gtk seems to use host=i686-pc-linux-gnu now ... but it was i486-pc-linux-gnu in beta ... what happened?
[12:03] <asac> seb128: ? any idea
[12:04] <seb128> mvo: I did suspend resume at least 15 times this week for sure
[12:04] <seb128> mvo: never got any freeze or hang
[12:04] <mvo> seb128: really strange, no idea then
[12:04] <seb128> asac: lool reworked the rules to specify armel flags could be it
[12:05] <seb128> asac: does that create any issue?
[12:05] <asac> hmm. that broke 32bit loading on 64 now
[12:05] <asac> e.g. we have a missing link
[12:05] <asac>  ls -l /usr/lib/gtk-2.0/2.10.0/i486-pc-linux-gnu
[12:05] <asac> lrwxrwxrwx 1 root root 29 2007-10-11 17:43 /usr/lib/gtk-2.0/2.10.0/i486-pc-linux-gnu -> ../../../lib32/gtk-2.0/2.10.0
[12:05] <seb128> that would be a ia32libs issue rather no?
[12:05] <asac> but no i686
[12:05] <asac> is that link shipped by ia32libs?
[12:05] <asac> if so, yeah
[12:06] <asac> seb128: great. ok
[12:06] <seb128> gtk doesn't ship any lib32 directory I think
[12:06] <asac> i already feared that the link was shipped by gtk ;)
[12:06] <asac> ia32 can still be updated
[12:06] <asac> thanks
[12:07] <asac> lool: do you have any bug i can refer to for this "host" change?
[12:07] <asac> lool: please confirm that we explicitly switched to i686
[12:07] <asac> (not that we can still change it ;))
[12:07] <lool> Uh
[12:08] <asac> strings /usr/lib32/libgtk-x11-2.0.so  | grep linux
[12:08] <asac> i686-pc-linux-gnu
[12:09] <lool> asac: I'm trying to understand
[12:10] <asac> lool: in gtk/Makefile.am there is -DGTK_HOST=\"$(host)\"
[12:10] <asac> or something
[12:11] <lool> asac: I'm trying to understand which change broke that
[12:11] <asac> lool: that was i486-pc-linux-gnu in beta
[12:11] <asac> ah ok
[12:11] <lool> asac: http://paste.ubuntu.com/154623/ is the closest
[12:12] <asac> lool: so maybe it changed in the toolchain?
[12:13] <lool> The --build flag is missing entirely in ubuntu8
[12:13] <asac> this paste looks weird ;)
[12:13] <lool> asac: Crap, it's a fix I made to SVN and which didn't make it to the Ubuntu pacjages
[12:13] <lool> Missing backspace after --enable-test-print-backend
[12:14] <lool> seb128: ^
[12:17] <lool> asac, seb128 moved to -release
[14:09] <asac> mvo: pmsg
[14:11] <mvo> asac: looking
[14:19] <asac> hmmm ... how does gtk select icons from theme. does it always select scalable if that exist? even for really tiny icons?
[14:36] <lool> seb128: Hey, I'm running Ubuntu under qemu from a fresh jaunty install and IndicatorApplet is encountering a problem on startup; how can I tell what happened on the bonobo / orbit2 server side?
[14:37] <lool> "Child process did not give an error message, unknown failure occurred"
[14:37] <lool> That's all I see in the .xsession-errors log
[14:38] <seb128> no idea out of the .xsession-errors log
[14:38] <seb128> does it work if you click on "reload" for the applet?
[14:38] <seb128> do you get any error if you run /usr/lib/indicator-applet/indicator-applet on a command line and add it to the panel then?
[14:40] <lool> seb128: I don't get reload, only don't delete versus delete
[14:40] <lool> (I think that's it's because it's on startpu)
[14:40] <lool> seb128: Running /usr/lib/indicator-applet/indicator-applet outputs nothing but exits with return code 1
[14:41] <seb128> tedg: ^
[14:41] <seb128> lool: is there an instance already running?
[14:41] <lool> seb128: oh yes
[14:42]  * lool starts a guest session
[14:47] <lool> seb128: I think it's an orbit2 tmieout
[14:47] <lool> It's very slow in qemu
[14:47] <lool> So I get popups about notification area, indicator applet and another one when starting the guest session
[14:47] <lool> seb128: I don't think we care much then => /me goes doing something useful :)
[14:47] <seb128> right
[15:14]  * Ng facepalms. If gnome-panel is told by gconf to start on a monitor that doesn't exist, it seems to go into a loop and never starts
[15:14]  * Ng fires up the bug filing cannons
[15:28] <seb128> Ng: you are firing the upstream canons right? ;-)
[15:28] <Ng> seb128: I did both and linked them :)
[15:28] <seb128> good
[15:42] <Ampelbein> pitti: have you had a look at bug 359963?
[15:54] <pitti> Ampelbein: not yet, it's not a major issue, but it's on my near-term TODO list
[15:54] <pitti> rickspencer3: FYI, new ubuntu desktop/alternates (20090420.1) available
[15:56] <rickspencer3> pitti: sweet
[16:02] <seb128> Ampelbein: that's not really an issue the retracing doesn't work on those bugs anyway that's just the error not being clear
[16:02] <seb128> Ampelbein: that's not really an issue the retracing doesn't work on those bugs anyway that's just the error not being clear
[16:02] <Ampelbein> seb128: well, if the retrace failed and apport-retrace finds outdated packages it closes the report right-away.
[16:02] <seb128> Ampelbein: which seems correct
[16:03] <Ampelbein> seb128: but not in cases where it falsely identifies packages as being outdated.
[16:03] <seb128> well if the retracing doesn't work the reason doesn't really matter
[16:04] <Ampelbein> it's still a legitimate crash and should be treated as such. for example the triager could try a manual retrace or ask the reporter to reproduce. if the report is closed, the reporter will feel like being ignored.
[16:05] <seb128> we should change the default message but still close those imho
[16:05] <Ampelbein> i think the issue happens when a recommended package is uninstalled. Then the dependencies.txt give NONE as installed version and the retracer treats it as being outdated
[16:05] <seb128> we have thousand of those useless bug around, they add noise and are never worked anyway, if the submitter update the bug he can as well reopen it
[16:06] <seb128> I'm in favor of autoclosing all bugs which have a non-useful stacktrace and ask the submitter to reopen if you can provide one
[16:06] <seb128> that's just the message to be closed
[16:06] <seb128> closed -> updated
[16:07] <Ampelbein> hmm. on second thought this sounds ok, because that's what the triager would do anyway. (ask for backtrace)
[16:07] <seb128> apport could be smarter about detecting packages to install too
[16:08] <seb128> ie look at the procmaps and installed what is there
[16:08] <seb128> it would fix lot of compiz retracing being broken for example because the crashes are in plugins which are not depends
[16:11] <Ampelbein> that would be really awesome.
[16:14] <pitti> seb128: apport has looked into ProcMaps and installing extra packages from there for ages
[16:14] <seb128> pitti: ah, ok so maybe there is an another reason why some retracing don't work correctly then, I just assumed that was due to that
[18:22] <mpt> rickspencer3, just came across https://blueprints.launchpad.net/ubuntu/+spec/ubuntu-software-development-kit
[18:24] <mpt> and https://blueprints.launchpad.net/ubuntu/+spec/widgetry
[18:35] <pitti> good night everyone!
[18:51] <asac> pitti: good night
[19:31] <calc> heh OOo 3.1.0rc2 won't even be out until after Ubuntu 9.04
[19:31]  * calc is glad he didn't try to cram OOo 3.1 into jaunty :)
[19:32] <calc> they are consistently behind schedule
[21:14] <chrisccoulson> hi seb128
[21:14] <seb128> hello chrisccoulson
[21:14] <chrisccoulson> have you noticed any freezing issues with evolution-data-server?
[21:15] <james_w> chrisccoulson: I get one on "Formatting message" quite frequently
[21:15] <seb128> bugs on launchpad or local bug?
[21:15] <seb128> how "with evolution-data-server"?
[21:15] <chrisccoulson> i haven't reported it yet. i was going to report it on bugzilla, but wasn't sure if it was just my setup
[21:15] <seb128> you don't notice from an user perspective what e-d-s is doing
[21:15] <seb128> but evo can be hanging due to e-d-s crashing
[21:16] <seb128> we have some known calendar bugs
[21:16] <seb128> can you give details on your issue?
[21:16] <chrisccoulson> for me, evolution stops working. it appears to be functioning but when you try and send an e-mail or fetch from my POP server, it just does nothing
[21:16] <chrisccoulson> then i got a backtrace of e-d-s
[21:16] <seb128> james_w: you should open a bug for that, on bugzilla if you can is better ;-)
[21:17] <james_w> seb128: there's a really old one on bugzilla I'm subscribed to
[21:17] <chrisccoulson> seb128 - this is the backtrace i get, and it is the same everytime e-d-s freezes: http://pastebin.ubuntu.com/154929/
[21:17] <seb128> james_w: oh ok, I though the old issue has been fixed, I've not seen a such bug in the whole jaunty cycle I think
[21:18] <james_w> it's not happened to me for a couple of weeks, but was happening a couple of times a day before that
[21:18] <seb128> chrisccoulson: no, I've not seen bugs similar to this one
[21:18] <chrisccoulson> hmmmm
[21:18] <james_w> the chatter on that bug suggest it might be a new problem though
[21:18] <dobey> hey packager types
[21:20] <seb128> hello dobey
[21:24] <seb128> chrisccoulson: how busy are you this week?
[21:24] <chrisccoulson> relatively busy until the second half of the week
[21:24] <chrisccoulson> how come?
[21:24] <seb128> chrisccoulson: or asked differently, do you want to do the nautilus sru update for this zooming issue?
[21:24] <seb128> or should I do it
[21:25] <chrisccoulson> yeah, i can do that
[21:25] <seb128> there is no hurry srus will not be accepted until after jaunty anyway
[21:25] <seb128> ok, thanks
[21:25] <chrisccoulson> that won't take too long to do. i could probably do it later this evening
[21:25] <seb128> as said no hurry we will not have those accepted before jaunty
[21:33] <seb128> chrisccoulson: base the update on the bzr version mvo already commited a fix there which can go in the same sru upload
[22:51] <Ampelbein> hi all. bug 270976 : I succeeded in creating a package of gst-plugins-bad with the mplex plugin enabled, installed it and all other libav*unstripped* packages and brasero does not complain anymore about a missing plugin. yet it fails burning with "Illegal operation". see bug 364324 for reference. am i right that the crash happens in libmjpegtools?
[23:10]  * dobey wonders what broke his keyboard layout