[01:26] <hggdh> chrisccoulson, ping
[01:31] <chrisccoulson> Hi hggdh!
[01:41] <hggdh> sorry for the delay, just got home from a business trip
[01:42] <hggdh> chrisccoulson, I am looking at bug 244631
[01:42] <chrisccoulson> ah yes! we discussed this one brifly earlier
[01:43] <chrisccoulson> i think the 2 people in that report have 2 differetn bugs
[01:43] <hggdh> sound like it
[01:43] <hggdh> sounds
[01:43] <chrisccoulson> i'm not really sure what else to ask from the original reporter
[01:46] <hggdh> for the gnome-keyring hang... I have opened a bug upstream (http://bugzilla.gnome.org/show_bug.cgi?id=544998) this happens with Evo, and causes Evo to stop responding
[01:46] <hggdh> we need a gnome-keyring-daemon backtrace on this, together with a Evo backtrace
[01:51] <chrisccoulson> Thanks! i'll ask the reporter to try and obtain the backtraces.
[01:51] <chrisccoulson> i see all of the error messages related to gnome-keyring on my current install, but I don't notice any hanging
[01:54] <hggdh_> chrisccoulson, I am having issues with my X server (looping)
[04:37] <anakron> Hi
[04:37] <anakron> https://bugs.launchpad.net/ubuntu/+bug/253177
[04:38] <anakron> This bug must be wishlist
[04:38] <anakron> XD
[04:39] <anakron> https://bugs.launchpad.net/ubuntu/+bug/253211     This must be in Wishlist
[04:40] <persia> anakron: Agreed in both cases.
[04:45] <anakron> thx
[04:49] <anakron> Thanks persia for 253177
[06:43] <anakron> Hi
[06:43] <anakron> https://bugs.launchpad.net/ubuntu/+bug/241574   This could be sent to wishlist?
[06:44] <anakron> ¬¬
[06:45] <anakron> :O
[07:25] <Hew> anakron: Shouldn't that bug be marked as new/confirmed rather than In Progress?
[07:25] <Hew> bah, they've gone
[10:30] <qense> hello
[10:35] <Hobbsee> heya!
[10:40] <qense> Did I miss anything during my two weeks of holiday? :)
[10:42] <Hobbsee> the sky fell in
[10:43] <Hobbsee> otherwise, no, not really
[10:43] <qense> ok, great
[12:52] <mcas> hi
[12:55] <james_w> hi mcas
[12:55] <mcas> hi james_w
[14:44] <bddebian> Boo
[16:06] <Hew> Can someone be a third party to agree/disagree with bug #106373?
[16:22] <chrisccoulson> Hew: I just had a look at that bug report. I agree with your comment that people running the development version are already well aware that breakage may occur
[16:23] <chrisccoulson> i wouldn't agree with modifying update-manager in the development version to warn a user that upgrades might break their system. the whole point of testing the development version is to find and fix things that break anyway
[16:25] <Hew> chrisccoulson: yea, my thoughts exactly
[16:25] <Hew> I'll mark it invalid then
[16:26] <chrisccoulson> i think thats the correct thing to do
[16:29] <Hew> chrisccoulson: did you have a chance to test the gnome vs kde weirdness in the VM?
[16:52] <chrisccoulson> Hew: I tried it briefly last night. i couldn't get it to run kwin when i logged in to GNOME though
[16:52] <chrisccoulson> but i did see some other wierdness
[16:53] <chrisccoulson> each time i changed between KDE and GNOME sessions, the resolution was all messed up.
[16:53] <chrisccoulson> i eneded up re-installing the Intrepid install late last night though because of some other problems, so I'll try again in a bit
[16:55] <Hew> chrisccoulson: yea, I was running KDE again earlier today and it's getting pretty unwieldy. I noticed some qt packages got bumped up to 4.1 though so I'll try again tomorrow after a restart
[16:58] <chrisccoulson> the problem with my VMWare setup, is that it tells X that the optimum resolution is 800x600. When I log in for the first time, I can set the resolution to 1600x1200, and then it remembers this between sessions. What I was seeing last night though is that if I log in to KDE and then back in GNOME again, the resolution had defaulted back to 800x600 again (and this happened both ways). I could change the resolution back again, but this
[16:58] <chrisccoulson> very odd
[17:03] <Hew> I should see if I can reproduce the problem in virtualbox-ose, but the vbox modules seem to be out of sync again..
[21:33] <hggdh> chrisccoulson, ping & hello
[21:48] <chrisccoulson> hi there hggdh!
[21:49] <chrisccoulson> thanks for responding to that bug report we spoke about yesterday. i haven't had a chance to do it yet today