[00:43] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r666 * Fix invalid desktop files (LP: #1754888)... (by Sean Davis)
[00:44] <Unit193> OK...
[00:46] <bluesabre> hi Unit193 
[00:52] <Unit193> >_>
[00:52] <bluesabre> :)
[00:52] <bluesabre> So, symbola?
[00:53] <Unit193> Yeah, I think it'd be good.
[00:53] <bluesabre> cool, want to add it to the seed?
[00:59] <Unit193> Huh, none of the fonts are in core, all are desktop...
[01:00] <Unit193> Honestly I would have thought noto and symbola would be in core.  Well, symbola *was*..
[01:01] <bluesabre> Also feel free to move those to core :)
[01:01] <bluesabre> Fix all the things! :D
[01:01] <Unit193> I wondered why you put numlockx there after fixing the issue where it was missing. :P
[01:02] <bluesabre> Also feel free to move that if it doesn't suit the mission of core
[01:03] <Unit193> 'core' isn't just my baby.  fonts-opensymbol, "This font contains symbols (like fonts as Wingdings(tm)), bullets (needed for bullets in LibreOffice) and non-latin character"  Hmm, think that's fitting too? :3
[01:04] <bluesabre> I understand, but you have a better idea of what fits there
[01:06] <Unit193> I think you're right on this, just struck me as odd initially.
[01:07] <Unit193> (notois in core from elsewhere, so yes moving the fonts over.)
[01:12] <Unit193> bluesabre: All done!
[01:19] <bluesabre> Unit193: thanks!
[01:48] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r667 Fix the copy-paste error (by Sean Davis)
[02:52] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r668 xdg-xubuntu-templates: Fix FileNotFound error (LP: #1694471)... (by Sean Davis)
[02:52] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r669 xdg-xubuntu-templates: Fix UnicodeDecode error (LP: #1668191... (by Sean Davis)
[03:00] <bluesabre> Reasonably productive night
[03:00] <bluesabre> nighty all
[05:58] <flocculant> bluesabre: I don't have bluetooth anything on pc ;) as far as -desktop goes might be better for someone they'd listen to to do it ...
[06:42] <flocculant> bluesabre: did a quick check - see at least 1 24s timeout for this on ubuntu livesession - will do some more looking when I'm back
[07:44] <ochosi> bluesabre: noice, lotsa fixes
[10:17] <tracker1> Hey People, Just wanted to leave a Note here - I read your call to join in Testing (from March 4th) - I'll try to find time to join in the next weeks. I'm also glad to see the beta has been tested at least a few times already.   In Short: thanks for your work and you have been heard ;)
[10:34] <knome> tracker1, nice to hear, thanks for the interest and hope you'll have time to help us :)
[11:54] <knome> slickymasterWork, i updated my slideshow branch, check it out when you have time
[12:30] <slickymasterWork> Thanks knome, I'll check it out later at home
[17:21] <willem> Can I have some advice again please? I updated 18.04 to the latest daily by starting software-manager from cli to check if https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1754986 still exists. Whilst in the update-manager I clicked on one of the links which referred me to the bug that was being repaired by the update; firefox did not start immediately; then it did. In cli I then had a load of messages: http://i.imgur.c
[17:21] <willem> om/SsP7UGg.png
[17:21] <ubottu> Launchpad bug 1754986 in update-manager (Ubuntu) "update-manager: WARNING:root:can not import unity GI Namespace Dbusmenu not available" [Undecided,New]
[17:22] <willem> Is this an update-manager problem, a firefox problem, or ? 
[17:22] <willem> http://i.imgur.com/SsP7UGg.png
[17:43] <flocculant> willem: hi - re the update mangler bug - does it not show up in the panel? It should do - it certainly does here (even if I ignore it). Assuming that it does show up - does it then work from there?
[17:43] <flocculant> That's where it should work from at least.
[17:44] <flocculant> If you want to do cli, then better to use apt or apt-get 
[17:52] <willem> flocculant, hi. Thanks for your quick reply. "does it not show up in the panel"... sorry about being daft, but what "it" do you mean, and which panel? Just to be clear: the updates do get installed, despite the messages.
[17:53] <flocculant> your desktop panel - you should see an icon there for update mangler
[17:53] <flocculant> just grabbing a pic
[17:54] <flocculant> https://i.imgur.com/ERb761E.png
[17:54] <flocculant> the orange thing is update mangler
[17:55] <flocculant> the issue you see is likely because it's looking for root stuff which gets started when it runs normally - I think ;)
[17:55] <willem> ah, thatś what you mean. No I haven't noticed that it's there. But I don't really pay attention to that I'm afraid.
[17:56] <willem> I'll take better note from now on and test what happens then
[17:56] <flocculant> willem - cheers :)
[17:56] <flocculant> and many thanks for staying around for longer than a day \o/
[17:57] <knome> yes, that's useful
[17:57] <knome> (hello all)
[17:57] <willem> Well, I'm really trying to dig in this time. 
[17:57] <flocculant> knome: indeed it is 
[17:57] <flocculant> willem: it's completely appreciated by I would expect the whole team - certainly by me :D
[17:59] <willem> My fear is that you guys are getting tired of me :-( 
[17:59] <willem> I have not yet decided what is more daunting to me: to know where "your" part of Xubuntu starts, where upstream starts, what are XUbuntu-software packages and what are packages from elsewhere, OR how to find out where to enter my bug reports: launchpad, bugzilla, xfce,org, 
[18:00] <willem> and what have you
[18:01] <flocculant> I'd not worry about us getting tired of you at all - akxwi-dave will tell you that once he's been around for a shortish while I dragged him into the https://launchpad.net/~xubuntu-qa team :p
[18:01] <flocculant> willem: you might want to join https://launchpad.net/~xubuntu-testers - sometimes I contact people there 
[18:02] <flocculant> willem: if something in Xubuntu is called xfce-something then lp and upstream 
[18:02] <flocculant> some things are not upstream - but kind of in house by bluesabre 
[18:03] <flocculant> if you go to bugzilla - and can't find the thing you want to report - it's likely not upstream xfce
[18:04] <flocculant> bluesabre ali1234 - ubuntu dbus-daemon[949]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) - so I can see the same issue on Ubuntu, but just apparently the once
[18:05] <willem> sorry, I've been disconnected... I've experienced two unexplained "log outs" just now... 
[18:06] <slickymasterWork> willem, I for one certainly second flocculant feelings of appreciation regarding your perseverance in staying with us 
[18:08] <willem> thanks for saying that. much appreciated!
[18:09] <flocculant> :)
[18:23] <willem> So, just to perservere ;-) where do you advice should I report http://i.imgur.c? firefox, update-manager, or?
[18:25] <flocculant> willem: need the whole imgur url ;)
[18:26] <willem> I thought you all were so clever that I could provide just half the url... :-) http://i.imgur.com/SsP7UGg.png
[18:28] <flocculant> willem: I'd leave that for the moment 
[18:28] <flocculant> eg not report it
[18:29] <willem> right. I won't. Is there are short way to explain why?
[18:29] <flocculant> is this from running update-manager in a terminal?
[18:30] <willem> it's when I started update-manager from terminal, but then, in the update-manager clicking on one the links that directed me to more information about the update of a particular package
[18:30] <flocculant> if so I 'think' it's complaining that root isn't able to create something - you don't want root to do that anyway
[18:30] <flocculant> aah right - tied up I suspect
[18:31] <flocculant> update-manager isn't a cli tool - it's a gui one - run it from panel
[18:31] <willem> right, I will from now on. Thanks for explaining.
[18:31] <flocculant> no problem - I'm probably simplifying things there too - I'm not completely sure 
[18:32] <flocculant> biab - not been home long
[18:33] <willem> last question for tonight... normally I would you apt... if I do: should I do sudo apt update && sudo apt upgrade OR sudo apt dist-upgrade? (people over at OSMC insist one should use dist-upgrade)
[18:33] <willem> flocculant, thanks for help; bye
[18:33] <flocculant> still here
[18:34] <flocculant> apt update and upgrade
[18:34] <flocculant> full-upgrade if it's not upgrading something
[18:34] <flocculant> dist-upgrade is for apt-get
[18:34] <willem> I see. thanks!
[18:34] <flocculant> np
[18:35] <willem> I have to dash now, as well. 
[18:35] <willem> bye
[18:35] <flocculant> night :)
[18:47] <ali1234> flocculant: ubuntu-desktop does not use blueman tho afaik
[18:48] <ali1234> bluez fails to start cos there is no hardware i think
[18:48] <ali1234> but then it is blueman causing the timeout
[18:54] <flocculant> yea - that's why I wondered - jibel has been looking for a slow boot issue in live session - so that's useful 
[18:54] <flocculant> and tbh if we can get them interested enough and we benefit I'm sure Sean will be more than happy :)
[18:55] <flocculant> also - if they've added this module and it's knackered us - they should be helpful - at least that's how I understand the ' we won't break flavours' thing 
[18:55] <flocculant> anyway - biab - really must eat
[18:56] <ali1234> if they dont use blueman at all i don't see why ubuntu-desktop would have added that module
[18:56] <ali1234> blame debian?
[18:56] <flocculant> no idea I'm afraid
[18:57] <flocculant> I didn't even know about the module till sean posted it in the bug
[22:00] <bluesabre> evening all
[22:03] <flocculant> hi bluesabre :)
[22:03] <bluesabre> hey flocculant!
[22:03] <bluesabre> late night for you
[22:03] <flocculant> bluesabre: it's only 10pm here :D
[22:03] <bluesabre> flocculant: that'd be a late night for me
[22:04] <bluesabre> :)
[22:04] <flocculant> ha ha ha 
[22:04] <flocculant> was just thinking bed though lol
[22:04] <flocculant> didja see ^^ and in #u-dev ?
[22:04] <bluesabre> flocculant: I did
[22:04] <bluesabre> Hopefully they just fix it and that's done
[22:05] <flocculant> yea - might be worth someone other than me saying something to them though
[22:05] <flocculant> I'm just glad that finally it's clear I've not been whining about nothing for months :D
[22:05] <bluesabre> :D
[22:06] <flocculant> I guess I might have noticed sooner if I hadn't ditched blueman locally ages ago 
[22:07] <bluesabre> I should ditch the bluetooth card from my laptop so I'm more bothered by it
[22:08] <flocculant> lol
[22:14] <flocculant> at least we know what's up now 
[22:15] <flocculant> anyway - will likely miss willcooke tomorrow - doubt he's out of bed when I leave for work ;)
[22:15] <bluesabre> So we *should* be able to get it fixed in the next month
[22:15] <flocculant> yea - got to hope so :)
[22:15] <flocculant> everytime LTS ... 
[22:16] <Unit193> Yeah, and since it's getting closer to release there seems to be issues cropping up.
[22:16] <flocculant> Unit193: hi - and yea 
[22:16] <Unit193> You know me, always lurking in the shadows.
[22:16] <bluesabre> :)
[22:17] <flocculant> :D
[22:17] <Unit193> Xorg or something seems to randomly be freaking out, which is new and fun.  And it seems printing isn't working out right now.
[22:17] <flocculant> fine here afaik
[22:20] <Unit193> Well, for that computer is new and fun.  I've been having only one good suspend for another, then have to hard reboot.  Also xorg crashes and dumps me back to lightdm if I do somethign wrong (like opening thunar, sometimes that does it.  Restarting xfdesktop, etc.)
[22:21] <flocculant> I can certainly give suspend a go for a few boots
[22:21] <Unit193> Nah it's fine, I only see it one 'Omega' and that's been happening for quite some time.
[22:21] <flocculant> which I'll do the first time now - as bluesabre mentioned the time - I'm now tired :p
[22:21] <flocculant> night peeps
[22:21] <Unit193> G'night.
[22:22] <flocculant> I'll still see if it works for me