[02:04] <bluesabre> That's fair, I'd say
[04:44] <Unit193> Presumably nobody has been testing sessions with GDK_CORE_DEVICE_EVENTS=1?
[07:19] <flocculant> knome: but Super+S is synaptic and repo reload
[07:40]  * flocculant is used to Xubuntu being listed last - thought we weren't on the 16.04.2 release announcement 
[08:31] <flocculant> bluesabre Unit193 - now we've got thunar 1.6.11 how do we go about getting it to 16.04 ? and will it happen before April? 
[08:32] <Unit193> !sru
[08:32]  * Unit193 shrugs.
[09:33] <knome> flocculant, noo ;)
[15:55] <pleia2> btw http://ubucon.org/en/events/ubucon-summit-us/schedule/
[15:55] <pleia2> "10 Years of Xubuntu"
[15:55] <pleia2> I guess I have a talk to write
[17:56] <flocculant> knome: so run how to start Xubuntu 17.04 on w.x.o ? 
[17:57] <flocculant> s/run how/run how to by me again ...
[18:01] <SwissBot> feed xfce4-announce had 5 updates, showing the latest 3
[18:01] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunar 1.6.11 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunar-1-6-11-released-tp48891.html (by Simon Steinbeiss)
[18:01] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-notifyd 0.3.5 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-notifyd-0-3-5-released-tp48893.html (by Simon Steinbeiss)
[18:01] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-weather-plugin 0.8.9 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-weather-plugin-0-8-9-released-tp48895.html (by Harald Judt)
[18:47] <knome> pleia2, congrats ;)
[19:27] <flocculant> Unit193 ochosi - now getting thunar crash when properties on a file - both with master from git or 1.6.11 from repos
[19:33] <ali1234> xfce4-display-settings is consistently segfaulting again
[19:33] <flocculant> bug 1665750
[19:34] <flocculant> did upstream at 13361
[19:34] <ali1234> backtrace has no debug symbols :(
[19:35] <flocculant> ali1234: well thunar-dbg is installed - perhaps I just do it wrong
[19:35] <flocculant> easy enough to redo - unfortunately ...
[19:35] <ali1234> how do i get 1.6.11?
[19:35] <ali1234> on 17.04
[19:35] <flocculant> https://wiki.ubuntu.com/Backtrace
[19:36] <ali1234> you can try "apport-retrace -s -S system /var/crash/..."
[19:36] <ali1234> but for me even that is not currently working
[19:36] <flocculant> ali1234: update for 1.6.11 - version in repo now
[19:37] <ali1234> i just did "apt upgrade" and i still have 1.6.10
[19:37] <flocculant> mmm
[19:37] <ali1234> maybe the mirrors are not synced yet
[19:37] <flocculant> ali1234: assuming you are uk ?
[19:37] <ali1234> yes
[19:37] <flocculant> I tend to use main server here
[19:38] <flocculant> assuming still uk that is :p
[19:38] <flocculant> pretty sure it's not coming from a ppa
[19:38] <flocculant> (uk too)
[19:38] <ali1234> i'll switch to the main archive
[19:39] <ali1234> in the mean time
[19:39] <flocculant> so *how* do I get debug symbols in a backtrace?
[19:39] <ali1234> have debug symbols installed for all libraries
[19:39] <ali1234> or use apport to do a retrace
[19:40] <ali1234> "apt upgrade" still says nothing to update
[19:40] <flocculant> except /var/crash is empty
[19:40] <ali1234> do you have access to errors.ubuntu.com?
[19:40] <acheronuk> no crash here. though I am running KDE on this machine
[19:40] <flocculant> ali1234: yea
[19:40] <ali1234> sometimes yoou can get backtraces from there, although it's hard to find the one you want
[19:41] <flocculant> ali1234: I might purge the gtk3 ppa's first and retry 
[19:41] <flocculant> and seems it only crashes out Properties on a file - not a folder
[19:42] <ali1234> did you do "ubuntu-bug thunar" to report that bug?
[19:42] <ali1234> that normally doesn't work if there's any ppa stuff involved
[19:44] <flocculant> ali1234: so - errors.u.c for 17.04 for thunar for the past day "No data to display"
[19:44] <flocculant> ali1234: and yea ack on if ppa involved
[19:44] <ali1234> hmm
[19:44] <ali1234> can you see private bugs?
[19:45] <flocculant> nope
[19:45] <ali1234> me neither :(
[19:45] <ali1234> 17.04 being unreleased sends bugs to launchpad, where they get marked private
[19:45] <ali1234> instead of e.u.c
[19:45] <flocculant> seems the only thunar-debug package is thunar-dbg 
[19:45] <ali1234> yeah but you need debug symbols for eg libgio
[19:45] <ali1234> libgtk
[19:45] <ali1234> etc ...
[19:46] <flocculant> mmm
[19:47] <flocculant> wouldn't it be nice if thunar-dbg included things it *might possibly* need :p
[19:47] <ali1234> -dbg packages have never really worked properly
[19:48] <flocculant> or if even there was a 'xubuntu-debug-symbols' or the like
[19:48] <ali1234> they're usually several days behind the repos
[19:48] <flocculant> ;)
[19:48] <ali1234> and they only exist for use by apport
[19:48] <flocculant> right
[19:49] <ali1234> which currently is broken for some reason
[19:49] <flocculant> :D
[19:49] <ali1234> your best bet is probably to get apport to send a backtrace to launchpad
[19:49] <ali1234> then wait for it to retrace
[19:49] <ali1234> but if anyone already did that your bug gets marked as private
[19:49] <flocculant> I managed to ubuntu-bug just before I posted the link
[19:49] <ali1234> then you have to go and ask it to be made public
[19:50] <flocculant> yea - been there more than once
[19:50] <ali1234> yeah but you have no crash report for apport to attach for some reason
[19:50] <flocculant> nope 
[19:50] <ali1234> i don't know why. maybe because it crashed too many times before
[19:50] <flocculant> pretty sure I didn't do the 'oh ffs just ignore this please' 
[19:51] <ali1234> i think it does that automatically after three or four crashes
[19:51] <ali1234> i cant get it to touch my crash because i reported it on launchpad
[19:53] <ali1234> (xfce4-display-settings:8733): xfce4-display-settings-CRITICAL **: xfce_randr_mode_width: assertion 'mode != NULL' failed
[19:54] <flocculant> I don't appear to be able to get that to fall over
[19:54] <ali1234> only happens in virtualbox
[19:54] <ali1234> https://www.bountysource.com/issues/34695319-display-settings-pops-up-and-then-disappearers
[19:55] <ali1234> apparently it doesn't only happen in virtualbox
[19:55] <ali1234> https://bugzilla.xfce.org/show_bug.cgi?id=12607 is true bug link
[19:59] <flocculant> ali1234: \o/ 
[19:59] <flocculant> ok so default/apport was set to 
[19:59] <flocculant> 0
[20:00] <flocculant> reset it to 1 - restarted - now have a crash report
[20:00] <ali1234> okay, now try "apport-retrace -s -S system /var/crash/..."
[20:02] <flocculant> seems to be trying - I assume it's going to fall down like you've been seeing
[20:02] <ali1234> no if it takes a long time it will probably work
[20:02] <ali1234> when it fails for me it fails instantly - because i already reported the bug
[20:03] <ali1234> i just unlinked the duplicate bug report on launchpad and now apport wants to report it again
[20:04] <flocculant> ali1234: well - ubuntu-bug reported it too with a 'some' stacktraces - I assume that's what we needed? 
[20:04] <ali1234> did it?
[20:04] <ali1234> i dont see any
[20:05] <flocculant> ali1234: the apport retrace is still going - I'd already re-reported it 
[20:05] <flocculant> currently private - going to un-private it - dupe my original to the new one
[20:08] <flocculant> bug 1665761
[20:09] <flocculant> hopefully then - that new one has debuig symbols - no idea, don't knwo what they look like
[20:11] <ali1234> sorry i lost internet there
[20:12] <ali1234> flocculant: i dont see any backtrace on your lp bug
[20:12] <ali1234> oh right duplicate
[20:14] <flocculant> hope that's got what's needed
[20:15] <flocculant> biab
[20:15] <ali1234> it doesn't really tell anything useful
[20:15] <ali1234> it crashed inside gio
[20:17] <flocculant> ftr - when we were testing thunar master+ patches last couple of weeks - Unit193 saw this in the ppa one atm, I couldn't replicate it with master and patches
[20:17] <ali1234> its probably random corruption (agan)
[20:17] <ali1234> it certainly looks like that, from the stack trace
[20:19] <ali1234> based on the stacktrace it looks like what happened is thunar tried to call a method on a gobject
[20:19] <ali1234> gio tried to look up the object in the giant hash table of objects it keeps
[20:19] <ali1234> but the hash table is completely corrupted, so the whole thing crashed
[20:20] <ali1234> so basically the usual random memory corruption caused by use-after-free somewhere completely different
[20:30] <knome> slickymaster, let's continue here...
[20:30] <slickymaster> sure
[20:30] <slickymaster> merge it knome 
[20:30] <knome> another thing too
[20:30] <slickymaster> I just got home from Lisbon and I still want to eat something before the meeting
[20:31] <knome> oh, ok
[20:31] <knome> then go have dinner
[20:31] <knome> i can catch up with that other thing later
[20:31] <slickymaster> I just have to warm the plate so we can do it now
[20:31] <knome> ok, so regarding documentation teams
[20:31] <knome> mostly non-xubuntu
[20:31] <slickymaster> yes
[20:32] <knome> since we now have our branch under ~xubuntu-doc, there's no real reason for us to keep certain team memberships
[20:32] <slickymaster> makes sense
[20:32] <knome> like ubuntu documentation committers - i will not be pushing anything to any other docs branch really
[20:33] <knome> and same for contributors - i don't think there is any synergy or technical reason why we should be members there
[20:33] <slickymaster> right, but will that tahes completely off the ubuntu documentation umbrella?
[20:33] <knome> the only direct implication of this is that unless you are a member of ubuntu bug control via other teams (or directly), you'll lose that
[20:34] <knome> slickymaster, in the social sense - we've already been separated technically for a long time (even more during the zesty cycle)
[20:35] <slickymaster> yeah, but we won't be a member of Ubuntu Documentation Project Team anymore, right?
[20:35] <knome> and there is https://launchpad.net/~ubuntu-doc
[20:35] <knome> xubuntu documentation is
[20:35] <knome> but tbh, i'm not sure if we need to be
[20:35] <knome> i only see mainbuntu, edubuntu and us there
[20:36] <knome> anything in the team description actually even applies to us
[20:36] <slickymaster> no objections from me reagrding tis
[20:36] <slickymaster> +h
[20:36] <knome> but this is why i wanted to talk with you about this
[20:36] <knome> to see if you think there is any (social) reason to belong to something like that
[20:37] <slickymaster> since we'll be managing our own branch we really don't need to be under their umbrella just for social sake
[20:37] <flocculant> ali1234: that all sounds like it makes sense to me from just words - but that's it :)
[20:37] <flocculant> evening knome slickymaster 
[20:37] <slickymaster> evening flocculant 
[20:37] <knome> slickymaster, yes, and there hasn't really been any benefits or any cooperation between different doc teams
[20:38] <knome> so i don't feel like there is any obligation to stay with the rest
[20:38] <slickymaster> that's true, an absolut sero
[20:38] <slickymaster> will that have to be submit to s vote, knome 
[20:38] <slickymaster> ?
[20:38] <knome> i'll take this to the meeting as well (mostly informational) and then do the changes
[20:38] <knome> meh, i don't think so
[20:38] <slickymaster> ok
[20:39] <knome> i'll ask if people think it should be voted on
[20:39] <slickymaster> even better
[20:39] <knome> but personally i don't think there's much to vote
[20:39] <slickymaster> anyone I'm officially +1 it
[20:39] <knome> heh :)
[21:21] <flocculant> ali1234: so on a xubuntu updated - but just vanilla, thunar works as expected
[21:24] <ali1234> if it's random memory corruption that doesn't mean much unfortunately
[21:24] <ali1234> can you make it crash again?
[21:25] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [zesty] r628 Merge flocculant's improvements for the contributor document... (by Pasi Lallinaho)
[21:35] <Unit193> Debian #855398
[21:50] <Unit193> flocculant: Do you have thunar-gtkhash installed?
[21:54] <Unit193> #6  0x00007f995c550ea6 in ?? () from /usr/lib/x86_64-linux-gnu/thunarx-2/libgtkhash-properties-thunar.so   so yes.
[21:55] <flocculant> Unit193: oh yea ...
[21:55] <Unit193> Try removing that plugin first.
[21:56] <flocculant> Unit193: yup
[21:57] <flocculant> I totally forgot about that bit - blaming irssi cos it's easy to look back in hexchat 
[21:58] <flocculant> Unit193: thanks for reminding me - I was completely lost on why it was failing now
[21:58] <Unit193> Sure thing.
[21:58] <flocculant> I guess the bug should be for thunar-gtkhash :)
[21:59] <Unit193> Trying something real quick.
[21:59] <Unit193> Or not, meeting time.
[22:00] <Unit193> #startmeeting Xubuntu community meeting
[22:00] <Unit193> Howdy and welcome to the Xubuntu community meeting.  Agenda: https://wiki.ubuntu.com/Xubuntu/Meetings
[22:00] <meetingology> Meeting started Fri Feb 17 22:00:00 2017 UTC.  The chair is Unit193. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[22:00] <meetingology> Available commands: action commands idea info link nick
[22:00] <knome> o/
[22:00] <krytarik> \o
[22:00] <Unit193> Well I'm here of course.
[22:00] <knome> krytarik, you missed the high-five. you're one row too low.
[22:01] <slickymaster> o/
[22:01] <Unit193> #topic Open action items
[22:01] <Unit193> I don't see any.
[22:02] <Unit193> #topic Updates and Announcements
[22:02] <flocculant> that's good for 3 months then :)
[22:02] <Unit193> We've already hit feature freeze.
[22:03] <flocculant> #info - Beta 1 due next week
[22:04] <Unit193> Any more, slickymaster, knome?
[22:04] <knome> nope
[22:04] <Unit193> #topic Discussion items
[22:04] <Unit193> #subtopic Thunar - 16.04/16.10 (flocculant)
[22:05] <slickymaster> nothing here
[22:06] <Unit193> flocculant: You have the floor.
[22:06] <flocculant> simply put- what are we going to do about thunar? 14.04 is EOL soon and we'll be expecting people to be upgraded to 16.04 or 16.10
[22:07] <Unit193> We have a fixed thunar now in the repos, so likely going to do an SRU.
[22:07] <flocculant> right
[22:07] <flocculant> the question is will that be done before EOL of 14.04 
[22:07] <flocculant> because if it's not
[22:08] <knome> as i mentioned before, since the 14.04 core is supported for 5 years, we can extend our promised 3 years to make sure it does
[22:08] <flocculant> then can we really expect people to care about EOL? 
[22:08] <flocculant> knome: yes - but do we just say 'foo' on our media?
[22:09] <knome> i don't think there is much more to be done
[22:09] <knome> anyway, we should totally be able to land the SRU before - we still have time
[22:09] <flocculant> so then we need to action that
[22:09] <knome> yes
[22:10] <knome> Unit193, want to help with the SRU?
[22:10] <flocculant> I know this all sounds obvious - just wanted it minuted :p
[22:10] <Unit193> knome: I'd hope bluesabre would.
[22:10] <knome> that works
[22:10] <knome> #action knome to work with bluesabre in order to get thunar SRU out ASAP
[22:10] <meetingology> ACTION: knome to work with bluesabre in order to get thunar SRU out ASAP
[22:10] <Unit193> flocculant: I believe it'll land close enough to the EOL, but we still have to get it in there either way.
[22:10] <knome> #nick bluesabre 
[22:11] <flocculant> Unit193: yup
[22:12] <Unit193> flocculant: So good?
[22:12] <flocculant> yea for sure
[22:12] <Unit193> #subtopic Documentation team reorganization (knome)
[22:12] <Unit193> knome: You have the floor.
[22:12] <knome> so as you might know, the xubuntu docs branch now live under ~xubuntu-doc
[22:13] <flocculant> sort of
[22:13] <knome> so in the same direction of progress, we were thinking that since there is no specific reason to belong to any of those ubuntu documentation LP teams, we might just as well do that
[22:14] <knome> obviously individuals are free to stay on any general documentation teams they want to 
[22:15] <knome> the biggest "change" (technically, this is purely social) is that the xubuntu documentation team would not be a member of https://launchpad.net/~ubuntu-doc any more
[22:15] <slickymaster> knome is right, since we now manage our own branch we really don't need to be under the ubuntu documentation umbrella just for social sake
[22:15] <Unit193> Thus wouldn't get loads of bugreports for other packages, that's why I let myself expire.
[22:15] <knome> but even that is justified; none of the text in the description applies to us, since this is not the way to get contributions to the xubuntu documentation even now
[22:16] <knome> and yes, there is this thought of not having the doc people get that load of mail
[22:16] <slickymaster> :)
[22:16] <knome> does anybody think we should have a vote on this, or should we simply proceed with the actions?
[22:17] <slickymaster> IMO we should just proceed with it
[22:17] <krytarik> +1
[22:17] <knome> (again, anything isn't affected, except getting unrelated mail will stop :))
[22:18] <flocculant> I'm +1 to us doing whatever suits us
[22:18] <knome> oki, then i guess we're fine
[22:18] <slickymaster> Unit193?
[22:18] <knome> #action knome and slickymaster to proceed with leaving some general ubuntu documentation teams
[22:18] <meetingology> ACTION: knome and slickymaster to proceed with leaving some general ubuntu documentation teams
[22:18] <Unit193> There seems to be no opposition or questions, so yeah.
[22:19] <knome> Unit193, sorry for not waiting for the reply, but i was pretty sure you'd be for it :P
[22:19] <slickymaster> lol
[22:19] <Unit193> Yep, fine.
[22:19] <knome> and i'm good with this, we can continue with the meeting
[22:19] <Unit193> #topic Announcements
[22:19]  * Unit193 scratches head.
[22:19] <Unit193> OK.
[22:19] <flocculant> thought we did that
[22:19] <knome> yes!
[22:20] <Unit193> For some reason, it's on the agenda.
[22:20] <knome> #info ~xubuntu-doc left ~ubuntu-doc
[22:20] <Unit193> slickymaster to schedule next meeting
[22:20] <flocculant> you can have some updates if you want :p
[22:20] <flocculant> #info - QA testing of 16.04.2 done and dusted, mostly internally to qa
[22:20] <flocculant> #info - testing of xfce components for ochosi:xfce4-notifyd and taskmanager
[22:20] <flocculant> #info - testing Setting Manager gtk3 for regressions - 3 bugs reported to bugzilla> xfce 13316, xfce 13317, xfce 13318
[22:20] <flocculant> #info - testing of thunar master plus 2 sets of patches (interminably it seemed ...) - response from 1 person via m/l (thanks Pjotr)
[22:20] <flocculant> #info - review Contributor Docs - removed mention of Trello
[22:20] <flocculant> oh - meant to lose the xfce from those :p
[22:21] <knome> lol :)
[22:22] <Unit193> Anything else for this meeting?
[22:22] <knome> hmm, well
[22:22] <knome> let's do this
[22:22] <flocculant> you might want to action slickymaster or he'll leave it for months :p
[22:23] <slickymaster> bah
[22:23] <Unit193> #action slickymaster to schedule next meeting.
[22:23] <meetingology> ACTION: slickymaster to schedule next meeting.
[22:23] <knome> #info The Xubuntu council is hanging in #xubuntu-council if anbyody has any issues they want to take up for the council. Please note that the channel has a no-idling policy, so please do not populate the channel without anything to say - or you will be booted
[22:23] <knome> there we go
[22:24] <Unit193> Thanks.
[22:24] <Unit193> #endmeeting
[22:24] <meetingology> Meeting ended Fri Feb 17 22:24:17 2017 UTC.  
[22:24] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2017/xubuntu-devel.2017-02-17-22.00.moin.txt
[22:24] <slickymaster> thanks Unit193 
[22:24] <flocculant> Unit193: thanks :)
[22:25] <Unit193> Thanks all for being here.
[22:25] <knome> thanks Unit193 
[22:25] <Unit193> And the song just ended.
[22:25] <flocculant> The Song Remains The Same too
[22:26] <knome> huh
[22:26] <knome> i just noticed ~xubuntu-council is a member of ~xubuntu-bugs
[22:26] <knome> there's no specific reason that is so, it's the owner of that team too
[22:26]  * knome silently presses a few buttons
[22:27] <pleia2> now no one sees bugs \o/
[22:27] <knome> (for fairness' sake, this has been done with other subteams a long time ago)
[22:27] <knome> pleia2, at least not the council members ;)
[22:27] <flocculant> pleia2: \o/
[22:27] <knome> pleia2, unless they are members of that team directly, like sean
[22:27] <slickymaster> hi pleia2 
[22:27] <flocculant> knome: you hope
[22:28] <knome> i don't - he is :)
[22:28] <knome> besides i could add him if i wanted... O:)
[22:28] <knome> https://launchpad.net/~xubuntu-bugs/+members
[22:28] <flocculant> you read his mail? 
[22:28]  * flocculant leaves
[22:28] <knome> lol
[22:29] <knome> i don't... except those that are sent to both of us :)
[22:29] <knome> well i also read the mail he sends that is sent to me... considering you consider that "his mail" ;)
[22:36] <bluesabre> evening all
[22:36] <bluesabre> missed the meeting :(
[22:36] <flocculant> hi bluesabre :)
[22:37] <Unit193> ...On purpose, but we still gave you a treat.
[22:37] <Unit193> bluesabre: I don't have to care about xfce4-mount-plugin or xfce4-sensors-plugin right? :(
[22:38]  * flocculant saves not marking b1 for release next week - till next week :p
[22:40] <knome> bluesabre, so, thunar SRU... do you need assistance with it, and what would that be?
[22:43] <bluesabre> Unit193, yeah, not important
[22:43] <Unit193> They released, I saw it, I put it on a list, I never touched them to put them in the PPA. :3
[22:44] <Unit193> https://mail.xfce.org/pipermail/xfce/2017-February/035454.html looks important.
[22:44] <bluesabre> knome, will be going by https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[22:44]  * flocculant was just reading that
[22:44] <bluesabre> probably don't need help with it yet, will need some "me toos" later
[22:45] <Unit193> Thanks so much for doing the SRU.
[22:45] <bluesabre> SRU's aren't so bad
[22:45] <knome> oki, thanks - if there is any paperwork you need me to do anyway, feel free to poke
[22:45] <bluesabre> SRU verification is the worst
[22:45] <bluesabre> usually goes: 6 people say it's fixed, 1 person tests it wrong perpetually and keeps commenting that it broke and sold their dog
[22:46] <knome> :D
[22:46] <flocculant> :)
[22:46] <bluesabre> thanks knome
[22:46] <Unit193> "Oh I didn't enable proposed, nevermind" after 3 months.
[22:47] <bluesabre> :D
[22:53] <bluesabre> so glad to have thunar back... nautilus is quite a bit slower
[22:53] <bluesabre> nicer to look at
[22:53] <bluesabre> but slow
[22:53] <flocculant> bluesabre: yea 
[23:18] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r491 Add preliminary support for the dark theme variant... (by Simon Steinbeiß)
[23:18] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r492 Try to get the square buttons in headerbars right (Fixes #17... (by Simon Steinbeiß)
[23:18] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r493 Fix the sidebar color in the dark variant (#168)... (by Simon Steinbeiß)
[23:20] <Unit193> Silly ochosi, hiding.
[23:21] <knome> indeed
[23:23] <bluesabre> :o
[23:23] <bluesabre> dark theme variant, that sounds neat
[23:23] <flocculant> but dark
[23:23] <bluesabre> xfwm still doesn't support that, I think
[23:23] <flocculant> very very dark
[23:23] <flocculant> Xubuntu goes over to the dark side - \o/ 
[23:23] <bluesabre> like ochosi's soul
[23:24] <flocculant> ha