=== _thumper_ is now known as thumper
[02:26] <duflu> jamesh, pulseaudio 1:11.1-1ubuntu7.5 is still in proposed. Did you get an update on that?
[02:26] <jamesh> duflu: not yet.  I'll ping jdstrand about it.
[02:27] <jamesh> duflu: yesterday I noticed some problems with the mouse pointer on my desktop.  It looked a lot like https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371
[02:27] <ubot5> Ubuntu bug 1865371 in gnome-shell (Ubuntu) "Mouse Cursor or Touchpad indicator/pointer not working" [Undecided,Incomplete]
[02:27] <duflu> jamesh, sounds like progress: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196
[02:27] <ubot5> Ubuntu bug 1856196 in snapd-glib (Ubuntu Focal) "Lower the snapd recommends to a suggests" [High,Fix released]
[02:27] <jamesh> might be tied to the Radeon driver?
[02:28] <duflu> jamesh, yeah too many possible causes so please open a new bug from yours: ubuntu-bug gnome-shell
[02:36] <thumper> does anyone know who runs the matrix bridge?
[02:38] <sarnold> I've heard they actually have a person now
[02:48] <jamesh> duflu: here's a new bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080
[02:48] <ubot5> Ubuntu bug 1867080 in gnome-shell (Ubuntu) "No mouse cursor drawn in Wayland session" [Undecided,New]
[02:52] <duflu> Ta, jamesh
[02:53] <duflu> jamesh, can you please add output from 'lspci -k' ?
[02:55] <jamesh> duflu: done
[02:58] <duflu> jamesh, fixed in mutter 3.36.0
[03:01] <jamesh> duflu: I guess this is the same as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371 then
[03:01] <ubot5> Ubuntu bug 1866371 in wayland (Ubuntu) "Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update" [Undecided,Confirmed]
[03:02] <duflu> yep
[03:03] <duflu> That was in the list of 90 bugs I am in the process of catching up on
=== pieq_ is now known as pieq
[06:26] <jibel> hi all
[06:36] <duflu> Hi jibel
[06:45] <oSoMoN> good morning desktoppers
[06:54] <duflu> Hi oSoMoN
[06:59] <duflu> Good trip home?
[07:00] <oSoMoN> hey duflu. My trip was short an uneventful, how was yours?
[07:01] <duflu> oSoMoN, amazingly I have so far got away without a cold or flu, which is unusually good. The main flight was very full but I took a pill and slept most of it
[07:02] <oSoMoN> good! I haven't had any ubuflu symptom either, but then again my travel was negligible compared to yours
[07:09] <didrocks> good morning
[07:11] <duflu> Hi didrocks
[07:11] <oSoMoN> salut didrocks
[07:17] <didrocks> hey duflu, salut oSoMoN
[07:35] <duflu> Weird. Why has my focal desktop kept the login screen theming bugs that were fixed for my laptop last week?
[07:35] <duflu> Fully updated
[07:52] <jibel> same here
[07:52] <jibel> the login screen is fine but the shield is not
[08:07] <duflu> jibel, oh that's different again
[08:08] <duflu> Surely this is related to how old my install is. Probably doesn't happen in new installs
[08:08]  * duflu makes another USB stick
[08:08] <jibel> i'll try on today's build
[08:35] <duflu> jibel, adding a user account photo fixes one of the issues
[08:40] <seb128> goood morning desktopers!
[08:41] <duflu> Morning seb128
[08:41] <duflu> jibel, I forgot the centring bug is not yet fix-released (bug 1865563)
[08:41] <ubot5> bug 1865563 in yaru-theme (Ubuntu) "password box not centered" [Undecided,Fix committed] https://launchpad.net/bugs/1865563
[08:42] <didrocks> salut seb128
[08:43] <seb128> hey duflu, didrocks, how are you?
[08:43] <duflu> seb128, travelled well and no longer jet lagged, I think. You?
[08:44] <seb128> duflu, ah, good to read! and no cold/flu/... on the way back this time?
[08:44] <seb128> I'm good, return trip was easy train for me :)
[08:44] <seb128> and week has been busy with GNOME 3.36 updates
[08:44] <didrocks> seb128: I’m good, thanks! You?
[08:44] <seb128> didrocks, I'm good thanks! played some tennis yesterday evening :)
[08:45] <duflu> seb128, yeah some element of luck there and also better practices
[08:45] <seb128> wasn't great because of the wind but still nice to be outside/moving
[08:47] <didrocks> nice
[09:02] <Wimpress> Hello desktopers
[09:03] <Laney> hey
[09:03] <seb128> hey Wimpress, how are you? had a good day off? got internet fixed?
[09:03] <seb128> hey Laney
[09:03] <duflu> Hi Wimpress and Laney
[09:03] <Wimpress> Yep. Good day off. Fixed network/internet in the afternoon.
[09:04] <Wimpress> Looks like it went wonky again in the early hours.
[09:04] <Wimpress> So....
[09:04] <Wimpress> duflu: o/
[09:04] <Wimpress> Did some live streams last night, basic debian/ubuntu package updates, testing, etc.
[09:05] <Wimpress> So internet did hold up for that, but died at the very end :(
[09:13] <jibel> can someone try today's iso on a real machine and tell me if it boots?
[09:13] <didrocks> hey Wimpress, Laney
[09:15] <jibel> uh, looks like image checksum is broken
[09:16] <jibel> this is bug 1867065
[09:16] <ubot5> bug 1867065 in casper (Ubuntu) "Installer hangs at boot on machine with LVM" [Critical,Confirmed] https://launchpad.net/bugs/1867065
[09:18] <jibel> xnox, ^ I think it's for you
[09:18] <jibel> it's related to the checksum of the image
[09:56] <Wimpress> tseliot: Morning.
[09:57] <Wimpress> Have you seen any reports of the updated nvidia driver hard locking systems while updating initramfs?
[09:57] <Wimpress> My desktop hard locked while installing updates.
[09:59] <Wimpress> Got the system to boot, but trying to update/remove nvidia drivers hard locks the system everytime initramfs attempts to rebuild.
[09:59] <Wimpress> I'm on the 440 series driver.
[10:05] <Wimpress> OK. Kernel panics.
[10:06] <duflu> Wimpress, default kernel?
[10:06] <duflu> I noticed some complaints about 5.6
[10:06] <duflu> with nvidia-440
[10:07] <Wimpress> Yes, 5.4 kernel.
[10:07] <duflu> Different bug then
[10:08] <Wimpress> core dumps each time DKMS is updated when recovering via single user.
[10:08] <duflu> Wimpress, seb128, also I would have thought we should display the Ubuntu logo before then?...
[10:08] <seb128> before what?
[10:09] <duflu> before the kernel boots and potentially hangs
[10:09] <seb128> can we do that?
[10:09] <duflu> grub can surely?
[10:09] <Wimpress> That is working duflu.
[10:09] <seb128> I guess, unsure how much would that would be, feels late to start on that for this cycle
[10:09] <Wimpress> I see the Ubuntu logo.
[10:10] <duflu> Ah OK.
[10:10] <duflu> I don't on some machines
[10:10] <Wimpress> Also, I have recovered the system.
[10:10] <Wimpress> But this is non-recoverable with any graphics driver loaded.
[10:12] <seb128> Laney, mozjs68 has a test failure on i386, I retried once but same error :-/
[10:13] <Laney> I know, it was unlikely to be fixed with a retry
[10:13] <Laney> have been looking at it already
[10:13] <seb128> k, good :)
[10:13] <Laney> https://bugzilla.mozilla.org/show_bug.cgi?id=1621900
[10:13] <ubot5> Mozilla bug 1621900 in Untriaged "bug653153.js test fails on 32-bit x86; problems with exponential handling" [Normal,Unconfirmed]
[10:13] <Wimpress> seb128: There are three merge proposal for Ubiquity Slideshow.
[10:13] <Wimpress> Will it help if I pull those into one MR?
[10:13] <seb128> Wimpress, no
[10:14] <Wimpress> OK
[10:15] <seb128> Wimpress, if you want to help you can review/accept the Mps
[10:15] <seb128> Wimpress, I can do the merge/upload but I'm not going to test flavor/have a call if they look right
[10:16] <seb128> Wimpress, the other option is to just merge without testing and trusting them to not screw their own slides
[10:16] <Wimpress> I can do the review.
[10:16] <seb128> thx
[10:16] <seb128> I will do the merge/upload if you ack the mps
[10:16] <Wimpress> I did a live stream about updating/testing Ubiquity slideshow last night.
[10:17] <seb128> you should get real days off sometime :)
[10:17] <Wimpress> Can I review my own MR? ;-)
[10:17] <Wimpress> I trust me.
[10:18] <Laney> Ah, that should be the person you trust *least*!
[10:18] <Laney> who wrote this and what was I thinking?
[10:19] <seb128> Wimpress, I'm fine review yours if you review the other ones
[10:21] <seb128> Laney, I retried libproxy/i386 autopkgtest with the right trigger, should be candidate now
[10:22] <Laney> cool
[10:22] <Laney> poor focal :(
[10:26] <Wimpress> seb128: OK, I'll review them this evening.
[10:27] <seb128> Wimpress, thanks
[10:28] <seb128> Laney, do you know if there is a way to ask for a debian autopkgtest retry?
[10:31] <Laney> seb128: excuses and/or ci.debian.net have retry links
[10:32] <seb128> Laney, sorry, it's not a failure, I just want to ask for a new try with what is current in unstable
[10:32] <seb128> https://ci.debian.net/packages/r/ruby-gnome/unstable/amd64/ didn't get tried yet with the new webkit2gtk
[10:34] <seb128> in fact there might be one in the queue if I read pending/ correctly
[10:34] <seb128> I guess I just need to wait then :)
[10:34] <Laney> ok
[10:34] <seb128> thx for the reply though!
[10:34] <Laney> but no I don't know how to schedule arbitrary jobs there
[10:35] <Laney> would be a question for #debci if you need it in future
[10:35] <seb128> ah, I didn't know they had a channel, thx
[10:41] <seb128> Laney, is that you that sponsored adwaita to Debian for Marco? if so could you gbp push the update?
[10:42] <Laney> ok
[10:42] <Laney> ping-fest
[10:42] <seb128> sorry :(
[10:42] <seb128> I will stop there :p
[10:43] <Laney> it's ok, means work is happening
[10:43] <seb128> thanks!
[10:43] <Laney> I needed to ask for him to push the upstream/foo tag on that one and then I guess didn't get notified or forgot to go back to it
[10:48] <seb128> Trevinho, hey, how are you? how is the dock fixing going?
[10:51] <xnox> jibel:  hey, the disk check goes, prints results, pauses a little or longer, continues to boot.
[10:51] <xnox> jibel:  currently pass & fail code paths are the same.
[10:52] <xnox> jibel:  the "lvm" fail message is a bit of a red herring, i should fix that to not confuse people.
[10:57] <jibel> xnox, yeah, I think the problem is that there is no feedback while the checksum is occuring, it takes time so people swtich to another console and see this message.
[10:57] <xnox> jibel:  but on the desktop it should be pretty
[10:57] <jibel> it is not
[10:57] <xnox> jibel:  the text messages are not pretty
[10:57] <xnox> jibel:  on the desktop plymouth should be painting pretty %
[10:58] <xnox> jibel:  something has regressed, if it's not pretty, let me download new image.
[10:58] <jibel> there is no feedback at all, no message or anything
[10:58] <jibel> just a black screen with the dell logo, the ubuntu logo and a spinning loading icon
[10:59] <xnox> jibel:  did somebody break plymouth theme?
[10:59] <seb128> xnox, the spînner logo maybe doesn't output thing like the ubuntu one was?
[10:59] <xnox> seb128:  so you switched the theme, without testing installer?
[10:59] <xnox> seb128:  great, spinner logo doesn't support any custom messages that we use in systemd-fsckd & casper. Installer image should use the ubuntu-logo splash theme
[11:00] <seb128> I guess yes
[11:00] <xnox> seb128:  and spinner theme is not suitable for us, as is, unless we ensure fsck:* messages are supported.
[11:00] <seb128> it also means we are regressing in installed system where fsck is happening?
[11:00] <xnox> seb128:  yes
[11:00] <seb128> Wimpress, ^
[11:00] <xnox> seb128:  because systemd-fsckd & plymouth integration is ubuntu-only.
[11:01] <xnox> seb128:  my system still uses ubuntu-logo => i guess my system is customized and I'm not getting stock focal experience then?
[11:01] <seb128> what does upstream do during fsck checks?
[11:01] <xnox> seb128:  nothing
[11:01] <seb128> do they display busyness in some other way?
[11:01] <xnox> they don't use filesystems that need fsck
[11:01] <seb128> xnox, either that or upgrade didn't pull the new recommends
[11:03] <xnox> seb128:  so my personal plan was to tweak ubuntu-logo theme to be "more like spinner", i.e. keep the vendor logo on screen, move the ubuntu logo down (to where gdm ubuntu logo is) and fade-in black to purple
[11:04] <seb128> xnox, wfm, the only reason I've been dealing with plymouth is that no one in foundation is actively taking care of it, but I would be happy to leave to people wanting to invest some work on getting us on a more modern look for boot splash
[11:04] <didrocks> xnox: systemd-fsckd isn’t ubuntu only, but having a plymouth theme support it is
[11:04] <xnox> seb128:  Wimpress: what's the driver for spinner theme? cause to fix things i could port fsck messages to the spinner theme; or do something inverse, make ubuntu-logo theme behave "more like spinner"
[11:05] <seb128> xnox, nicer user experience
[11:05] <xnox> seb128:  ack, let me play with spinner theme, to get a better feel for it.
[11:05] <seb128> especially for oem where like xps preinstalled where you have no grub menu
[11:05] <seb128> xnox, thanks!
[11:06] <xnox> seb128:  i guess it goes from dell logo, dell logo + spinner (a little bit), gdm?
[11:06] <seb128> xnox, yes
[11:06] <seb128> dell logo + spinner + ubuntu logo at the bottom of the screen
[11:06] <seb128> to be exact
[11:07] <xnox> seb128:  ooooh, and it's monochrome ubuntu logo
[11:07] <xnox> how black tie
[11:07] <seb128> yes, we got an updated logo in Frankfurt
[11:08] <seb128> xnox, also I'm about to update the spinner assets to be the yaru spinner
[11:08] <xnox> yeah, none of casper messages got printed with fsck progress
[11:08] <seb128> frederik provided me new assets
[11:08] <xnox> seb128:  do you have links as to how yaru spinner looks?
[11:09]  * xnox reboots
[11:09] <seb128> xnox, https://gitlab.freedesktop.org/Feichtmeier/plymouth/-/tree/master/themes/spinner the throbber-nnn files there
[11:14] <xnox> seb128:  it's a bit ugly with disk unlocking.
[11:15] <seb128> xnox, why? because the entry is placed to high on the screen?
[11:15] <xnox> seb128:  in ubuntu-logo, we poppped up the type password field below the centre logo, and hid it after typing password. In spinner, it removes dell logo, pushes the entry field for password, then hides it, jumps the unlock message possition, repaints the vendor logo.
[11:16] <xnox> seb128:  because it flickers the oem logo, instead of keeping it painted, and using the like spinner location for the entry field.
[11:16] <seb128> xnox, those are problem worth reporting upstream
[11:16] <seb128> but yeah, it could be better/get some extra polish
[11:16] <xnox> seb128:  as per Windows guidelines the area of the oem logo is not to be used for any messages or input.
[11:17] <xnox> seb128:  also there is flicker of the ubuntu logo. It seems like gdm "fades in" ubuntu logo on the bottom, although it is pixel perfect, it flickers a fade in of it.
[11:18] <xnox> cause it goes from white, instant to purple, fade in purple to white ubuntu logo.
[11:19] <xnox> seb128:  i wonder how quick it would be to make ubuntu-logo be spinner compatible. I.e. drop background painting, pop up oem logo, change ubuntu graphic, push it down => jobs done, in a non-regressive way
[11:19] <seb128> right, valid point/things we could improve if we have time/resources to look at those
[11:20] <xnox> seb128:  it might look slightly better, if at "spinner stop" one fades out ubuntu logo in plymouth
[11:20] <xnox> seb128:  fsckd messages support regression, imho is bad.
[11:20] <seb128> it's annoying indeed
[11:21] <seb128> could you open a bug about it?
[11:21] <seb128> we need to discuss what are our option/what we want to do
[11:21] <xnox> seb128:  what term do you use for new & old themes? spinner & ubuntu-logo? or bgrt & ubuntu-logo?
[11:22] <xnox> i see both in bugs =)
[11:22] <seb128> spinenr is the name of the theme
[11:22] <seb128> spinner
[11:22] <xnox> ack
[11:24] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867130
[11:24] <ubot5> Ubuntu bug 1867130 in plymouth (Ubuntu) "spinner theme doesn't support fckd progress messages" [Undecided,New]
[11:29] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867131
[11:29] <ubot5> Ubuntu bug 1867131 in plymouth (Ubuntu) "spinner theme flickers OEM logo on password entry" [Undecided,New]
[11:34] <seb128> xnox, thanks
[11:35] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867133
[11:35] <ubot5> Ubuntu bug 1867133 in plymouth (Ubuntu) "spinner theme flickers Ubuntu logo on gdm transition" [Undecided,New]
[11:44] <seb128> thx for the report, need to drop offline for a bit while relocating
[11:44] <Saviq> didrocks: I ran out of space on my zpool… can I just destroy the zsys snapshots? is there a database I'll need to clean somewhere?
[11:49] <didrocks> Saviq: waow, already? Your snapshots were taking so much space?
[11:49] <didrocks> yeah, remove them directly for now with zfs
[11:50] <didrocks> zfs destroy -r rpool@snapshot_name bpool@snapshot_name
[11:50] <didrocks> note that snapshots take no space if you don’t have any change
[11:50] <Saviq> didrocks: the problem is that you just never regain space…
[11:50] <didrocks> as it's a COW system
[11:51] <Saviq> (and I only have 128G atm)
[11:51] <didrocks> ah, that makes sense. You can adjust the gc if your need is a small machine
[11:52] <didrocks> dropping the conf file to the right place
[11:52] <didrocks> (and yeah, we only rely on zfs state, we don’t have a separate database on purpose to avoid async issues)
[11:53] <didrocks> zfs list -o space should be of help if you can print it out for our info with jibel
[11:53] <Saviq> Gah… recovery is busted…
[11:53] <didrocks> zfs list -o space -t snapshot
[11:53] <didrocks> also
[11:54] <didrocks> I thought that we kept in ubuntu as root an X% space for booting
[11:55] <Saviq> Need to boot from an external drive… we seem to lack the 5% root space… or well, it got filled with LXD
[11:58] <Saviq> Ok recovered enough to boot
[11:59] <didrocks> phew, if you can paste the space commands so that we see how much is taken by snapshots, that would be helpful
[12:07] <Saviq> didrocks: https://paste.ubuntu.com/p/RWbNT6p2j3/ https://paste.ubuntu.com/p/gPnqD3Qcbj/
[12:07] <Saviq> I don't think it gives it justice… I recovered almost 50G by dropping them
[12:10] <didrocks> hum. Indeed, the userdata ones are weird to not be the sum of them
[12:10] <didrocks> we’ll give it some tests
[12:16] <Saviq> I'll file a proper bug soon
[12:17] <Saviq> but I think that we've "lost" the 5% root buffer is something quite bad
[13:32] <jibel> xnox, seb128 the shutdown to reboot message also regressed cf bug 1865161
[13:32] <ubot5> bug 1865161 in casper (Ubuntu) "Written "press return to shutdown the computer" does not appear." [Critical,Confirmed] https://launchpad.net/bugs/1865161
[13:33] <xnox> jibel:  i somehow feel like spinner theme is not showing any messages, yet to test this with plymouth-x11 to confirm
[13:33] <xnox> jibel:  wasn't spinner theme meant to be "non-interactive"
[13:36] <xnox> jibel:  maybe we need like layers on the desktop iso to have "installer" layer with ubuntu-logo theme instead of the spinner one
[13:55] <ogra> kenvandine, i think we can skip today, unless yuo have anything pressing (i was busy with customer stuff all week so nothing to talk about from my side)
[13:55] <kenvandine> ogra: sounds good
[13:56] <popey> is it known that today's daily takes an age to boot?
[13:56] <popey> sits at the spinner for quite a bit longer than usual
[13:57] <jibel> yes, it's the fsck without feedback
[13:57] <popey> oh, i am not seeing the checker
[13:57] <jibel> there is bug 1867065 and the 2 others xnox filed
[13:57] <ubot5> bug 1867065 in casper (Ubuntu) "Installer hangs at boot on machine" [Critical,Confirmed] https://launchpad.net/bugs/1867065
[13:58] <popey> ta
[13:58] <jibel> bug 1867131
[13:58] <ubot5> bug 1867131 in plymouth (Ubuntu) "spinner theme flickers OEM logo on password entry" [Undecided,New] https://launchpad.net/bugs/1867131
[13:59] <jibel> bug 1867130
[13:59] <ubot5> bug 1867130 in plymouth (Ubuntu) "spinner theme doesn't support fckd progress messages" [High,Confirmed] https://launchpad.net/bugs/1867130
[14:02] <jibel> is it known that snap cannot be installed on a fresh installation of focal?
[14:02] <jibel> I get "too early for opetaion, device not yet seeded, ...."
[14:03] <popey> we have seen that before a number of times
[14:03] <popey> happens in lxc containers for example if you create one, shell in, then immediately snap install something
[14:03] <jibel> the machine has been up for more than 1 hour now
[14:03] <jibel> it's a real machine
[14:03] <popey> oh
[14:03] <popey> a bug then
[14:03] <jibel> installed from today's build
[14:03] <popey> -> snap
[14:04] <jibel> livecd-rootfs bug. I thought it was fixed
[14:08] <seb128> jibel, did we just get the plymouth theme changing on the iso for some reason or has it been that way for weeks but nobody tested the iso during that timeframe?
[14:12] <jibel> week
[14:12] <jibel> singular
[14:13] <jibel> I just did a more intensive review this morning
[14:13] <jibel> otherwise it's automated and unnoticed
[14:15] <seb128> jibel, the seed change was done in january, that's week*s* :-) https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=f7e2db8231
[14:17] <jibel> seb128, maybe but it's been broken after the change to enable md5check in casper which was end of february
[14:17] <jibel> until then it was the aubergine boot screen without a spinner
[14:18] <seb128> jibel, well, we saw that working
[14:18] <seb128> I was mostly curious to know when it stopped working
[14:19] <seb128> but I guess we don't have enough data to say/didn't do enough regular testing
[14:19] <seb128> oh well
[14:19] <seb128> we should probably find a way to force the ubuntu-logo theme on the iso
[14:20] <seb128> it's a special case with the checksum, reboot, etc
[14:20] <seb128> unless fixing the fsck case/displaying of message for spinner fixes those cases...
[14:24] <jibel> seb128, I'd say it broke within the last 2 weeks. According to https://discourse.ubuntu.com/t/defaulting-to-verify-the-image-integrity-before-installing-on-desktop/13472/6 it was still the aubergine background and the checksum message was displayed
[14:24] <popey> I tested last week and it worked
[14:24] <jibel> yeah
[14:24] <popey> something changed between last week and this
[14:25] <seb128> oh well
[14:25] <seb128> software
[14:25] <jibel> popey, snap bug is https://bugs.launchpad.net/bugs/1864252
[14:25] <ubot5> Ubuntu bug 1864252 in livecd-rootfs (Ubuntu Focal) "preseeded snap installs fail in images" [High,Fix released]
[14:25] <jibel> same symptoms as least
[14:25] <seb128> jibel, if we only we had worked on that trello card about storing images history, we could tell what changed and when :)
[14:26] <popey> https://youtu.be/YOUwdhNbHtk?t=519 - video proof of what it looked like on 1st march
[14:30] <hellsworth> good morning desktopers
[14:31] <seb128> hey Heather, how are you today?
[14:32] <hellsworth> feeling better. yesterday i felt a bit sick but seems it was nothing
[14:33] <seb128> oh, great that it was nothing!
[14:34] <hellsworth> yeah i was probably just being extra sensitive due to the world situation
[14:34] <Wimpress> hellsworth: Hello. How are you?
[14:35] <hellsworth> hi Wimpress !
[14:35] <hellsworth> i'm tickety boo :)
[14:36] <Wimpress> You've been spending to much time with popey  ;-)
[14:36] <hellsworth> lol
[14:41] <didrocks> hey hellsworth
[14:41] <hellsworth> hi didrocks !
[16:47]  * Laney eyes gjs/i386
[16:48] <seb128> :-(
[16:51] <Laney> didn't we kill this arch :p