[02:03] <Unit193> albinard: Heya!  Finally popping on when I'm active!
[02:03] <albinard> joining in
[02:04] <albinard> Hey, I'm old - need my sleep:)
[02:05] <albinard> I like your latest Core ISO - really smooth, takes everything I've thrown at it
[02:07] <Unit193> I can't remember if I've asked before, but do you happen to have EFI hardware?
[02:07] <Unit193> And one would hope, it's getting close to release time!
[02:07] <albinard> Yes, but I've always used the BIOS alternative
[02:08] <albinard> Seems to work with limited tech smarts
[02:10] <Unit193> Yeah, BIOS is a bit easier to set up.
[02:11] <Unit193> For EFI/secure boot tests, I've either had to use qemu or rely on other people to test as I just have the older BIOS stuff.
[02:12] <albinard> Good to hear - I thought I was the only one left!
[02:17] <albinard> I'd try to help you out, but the learning curve would be a bit too steep 
[02:17] <albinard> for a timely answer.
[02:20] <Unit193> Yeah that's all fine, thanks though.
[02:23] <albinard> Isn't the installer part the same as for other *buntus
[02:23] <albinard> except for the branding or lack of it?
[02:24] <Unit193> Yeah it uses ubiquity, same as everything else.  Just doesn't include the slideshow.
[02:25] <albinard> Then wouldn't an EFI test of any *buntu serve, since
[02:26] <albinard> once it's partitioned, it should be all set to go?
[02:26] <Unit193> Ubiquity would just be the installer, casper and other aspects would be more what we're looking at for EFI.
[02:28] <albinard> Oops - I guess I never look further into things todistinguish the components that thoroughly.
[02:32] <albinard> Guess I haven't much helpful to add, so I'll say goodnight and thanks for great ISOs!
[04:16] <FurretUber> Hi, I`m testing the Live System of Xubuntu http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/170812/testcases/1303/results and it failed. Ubiquity never opens and the system is entirely in English. Was this reported already?
[04:18] <FurretUber> The grub options when booting in UEFI mode don`t allow the user to choose the language
[04:19] <FurretUber> Instead of two menu entries, one to try and another to install, there should be only one to start Xubuntu, and that entry must use maybe-ubiquity instead of only-ubiquity
[04:19] <FurretUber> Then the user would be able to choose the language
[06:58] <flocculant> knome pleia2 - can we have some testing love on twitter/g please :)
[07:33] <flocculant> anyone got efi enabled machine to test bug 1766047
[07:39] <knome> flocculant, tweeted
[07:39] <knome> flocculant, https://twitter.com/Xubuntu/status/987958981300715520
[07:39] <flocculant> knome: thanks :)
[07:41] <knome> clearly twitter shouldn't have extended the allowed character count... now you just start writing these long poems :P
[07:42] <flocculant> ha ha ha 
[07:42] <flocculant> you politely said what I was a bit blunter about on facebook
[07:42] <knome> ;)
[07:42] <knome> dunno about that world, i tend to be able to avoid that domain for the most part :P
[07:43] <flocculant> well I kind of do it to keep in contact with a few people - and pleia2 didn't like doing it, so I was friendly to her :p
[07:43] <knome> yeah, it's mostly good to split things anyway
[07:43] <flocculant> "Thanks for any likes and shares - but what we really need so that we can actually release in a few days is for people to actually follow through and test. "
[07:43] <knome> anyway... bbabl/bbl
[07:44] <knome> have a fun sunday
[07:49] <flocculant> yea - you too
[10:21] <flocculant> bluesabre: mailed lists for rc/final and did facebook, knome did twitting 
[10:22] <bluesabre> flocculant: nice
[10:22] <bluesabre> I'm working on catching up on a month's worth of release announcements for my apps
[10:22] <flocculant> :D
[10:25] <flocculant> don't think there's much nastiness hiding in installs now
[10:26] <flocculant> some oddities installing from uefi apparently - but no hardware I can look on there
[10:28] <flocculant> !team | you will hopefully have seen leigh and willem around over the last few weeks - both new testers, they had more problems trying to deal with our tester info than anything else. To that end I asked them both to look -they are. Once the dust has settled post-release there will be stuff for you all to look at
[10:29] <bluesabre> very nice
[10:29] <flocculant> indeed - they've both put in a lot of time for it :)
[12:09] <ochosi> bluesabre: nice work on the release posts!
[12:13] <bluesabre> ochosi: thanks! going to try to be better going forward with release announcements happening at the same time as releases :)
[12:13] <ochosi> hehe
[12:14] <ochosi> btw, a cli interface for mugshot would be nice
[12:14] <ochosi> so you can automate setting up stuff
[12:14] <ochosi> (would come in handy @work)
[12:14] <bluesabre> ochosi: that would basically be the thing that powers mugshot, chfn
[12:14] <ochosi> right, but does chfn have a nice cli?
[12:15] <ochosi> oh, it's actually not that bad 
[12:15] <bluesabre> apparently it's different between fedora and ubuntu for some reason, but yeah, pretty usable
[12:15] <ochosi> the avatarr is missing
[12:15] <bluesabre> indeed
[12:15] <bluesabre> might be something to add in the future
[12:15] <ochosi> is that more than saving the pic as .face?
[12:15] <bluesabre> That's basically it, but it might do something with accountsservice as well
[12:16] <bluesabre> and syncing pidgin to .face
[12:16] <ochosi> right
[12:16] <ochosi> does lightdm still use .face?
[12:16] <ochosi> or some accountsservice stuff now
[12:16] <ochosi> (haven't dealt with it for so long...)
[12:16] <bluesabre> I think so... not sure atm :D
[12:16] <ochosi> haha
[12:16] <ochosi> alrighty, nvm
[12:16] <bluesabre> haven't really touched the codebase in quite some time :)
[12:17] <ochosi> as long as mugshot works all is good ;)
[12:19] <flocculant> hi ochosi 
[12:20] <ochosi> hey flocculant 
[12:21] <ochosi> and thanks for chipping in on the release ml
[12:21] <flocculant> ochosi: no worries - something I have opinions on ;)
[12:23] <ochosi> :>
[14:27] <FurretUber> flocculant: qemu-system-x86_64 -m 1536 -cdrom xubuntu-bionic-desktop-amd64-2018-04-21.iso  -bios /usr/share/ovmf/OVMF.fd -enable-kvm -cpu host
[14:28] <FurretUber> Of course there should be qemu-system-x86, qemu-kvm and ovmf installed
[14:30] <FurretUber> The issue is the grub configuration, so that affects all flavors of Ubuntu 
[14:30] <flocculant> aaah
[14:31] <flocculant> must be ovmf I was missing - always got errors trying to uefi with kvm
[14:32] <flocculant> FurretUber: the bug has been pinged to people in -release btw
[14:34] <flocculant> apparently not, still get errors trying to uefi with the virt manager setup
[14:35] <FurretUber> virt-manager? Video QXL? Another bug
[14:36] <flocculant> not sure 
[14:37] <flocculant> FurretUber: tbh I'm not that bothered - have a hard enough time getting people to do testing on actual Xubuntu bits
[14:37] <flocculant> booting the iso is canonical problem 
[14:41] <FurretUber> The Xfce4 part is mostly OK. I would tell xfce4-volumed should handle better if pulseaudio daemon is restarted, but now the pulseaudio plugin is being used by default. From the components I use I reported what I've noticed (the screenshooter, taskmanager)
[14:42] <flocculant> FurretUber: I know - I see bugs, you in here, you in #u+1 :)
[14:43] <FurretUber> I have not reported a lot of things related to Xfce4 because simply there are very few problems I noticed. Many are not related to Xfce4, so I end talking a lot in #ubuntu+1
[14:43] <pleia2> flocculant: g+ done
[14:44] <flocculant> FurretUber: ack - I always read though - have pings for xubuntu and xfce in some channels
[14:44] <flocculant> pleia2: thanks :)
[16:45] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-whiskermenu-plugin 2.1.7 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-whiskermenu-plugin-2-1-7-released-tp50937.html (by Graeme Gott)
[16:45] <Unit193> - Fix memory leak when recreating window.
[16:47] <Unit193> That'd seem a bit important...
[17:21] <flocculant> perhaps :)
[17:23] <flocculant> then again 
[17:24] <flocculant> - Fix crash when last search action is deleted. probably does as well
[17:42] <FurretUber> Hi, what may be the cause of this: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1765768 ?
[17:49] <flocculant> ochosi did say something a while ago about small icons in the new notifier 
[17:49] <flocculant> other than that - no idea
[17:50] <FurretUber> It's strange this happens only on boinc, Discord and xfce4-power-manager are fine
[17:50] <flocculant> and it's a bit late in the day for things like that - if you get installer crashes or something else critical I'll be a bit more positive about it
[17:50] <flocculant> FurretUber: I see similar with transmission
[17:59] <FurretUber> Transmission icon is fine here, strange
[18:18] <ochosi> flocculant: small icons where?
[18:20] <flocculant> ochosi: on the new notifier plugin 
[18:20] <flocculant> not really sure what the end of that discussion was - nine tls was involved perhaps
[18:20] <ochosi> but in what context? in the bubbles?
[18:21] <ochosi> or in the menu?
[18:21] <flocculant> ochosi: oh sorry - sn plugin - not notifications
[18:21] <ochosi> ah
[18:21] <ochosi> right
[18:21] <ochosi> cant remember saying anything about that, but who knows - its been a long cycle :)
[18:21] <flocculant> forgot your relationship with the other notify thing :D
[18:22] <flocculant> anyway - this close ot Thursday *I* really aren't worried about an odd icon - an exploding install - yep I'll worry ;)
[18:23] <flocculant> s/aren't worried/can't worry is probably a better way to say that 
[18:24] <Unit193> But a memleak...
[18:25] <flocculant> I did say perhaps :p
[18:25] <Unit193> But meh, I don't use whisker, soo.
[18:25] <flocculant> and there's another nasyish fix in the previous release of whisker 
[18:26] <flocculant> ochosi: sn plugin is on the far right of the panel http://i.imgur.com/UMMfT0m.png
[18:26] <flocculant> bbl
[20:21] <ochosi> flocculant: does it only happen with transmission or with other icons too? also, what do the settings of sn-plugin say?
[20:24] <flocculant> ochosi: network manager is the same - doesn't matter what different settings I use there
[20:34] <flocculant> ochosi: oh ... I see there's an icon sie tool then :p
[20:35] <flocculant> size
[20:42] <ochosi> flocculant: does that make a difference then?
[20:42] <flocculant> yea
[20:43] <flocculant> unless I make it too big for panel - then it gets cut
[20:43] <ochosi> so we need different default settings..?
[20:43] <ochosi> or does it look ok ootb in the default session
[20:43] <flocculant> just checked the iso actually - looks ok there
[20:44] <flocculant> shame it doesn't take icon size from panel size - it is what it is - and I'll not complain cos I can't fix it myself :)
[20:45] <ochosi> it's strange that it doesnt
[20:46] <ochosi> i thought it does
[20:46] <ochosi> maybe something to ask ninetls about
[20:46] <flocculant> pretty sure I'd not set it to 13px locally - or I'd know why it was so small :D
[20:46] <ochosi> anyway, in the gtk3 panel there is an api call for querying the icon size in the panel
[20:46] <ochosi> so all plugins should behave/scale the same
[20:47] <flocculant> ok - that sounds good 
[20:47] <flocculant> as you know - flocculant wants all the gtk3 stuff in the iso as soon as practical :D
[20:47] <ochosi> yup, it should be fine for 18.10
[20:47] <flocculant> looking forward to that 
[20:49] <Unit193> Have fun with that.. ;P
[20:49] <flocculant> :)_
[20:50] <ochosi> we will :)
[20:59] <knome> re: flavor-specific cdimage stylesheets, let's start iterating from here: https://temp.knome.fi/xubuntu/cdimage/cdimage_xubuntu.png
[20:59] <knome> ping flocculant, ochosi ^
[20:59] <knome> this is without any changes to the markup...
[21:02] <ochosi> looks quite nice already
[21:07] <knome> yep
[21:07] <knome> this is throwing our generic stuff at it
[21:10] <ochosi> do we want to highlight any of the lines?
[21:10] <knome> well
[21:10] <ochosi> like the zsync or the ISO lines
[21:10] <knome> that's a regular apache file listing
[21:10] <ochosi> right
[21:10] <ochosi> in that case no :)
[21:10] <knome> probably not, no
[21:11] <knome> i mean, it would be impossible without tweaks to the code
[21:11] <knome> since everything else except the .html files are of unknown type
[21:13] <ochosi> other than this i have no complaints
[21:13] <ochosi> looks good!
[21:13] <knome> going to put our logo somewhere
[21:13] <knome> and look at the possibility to have a link back to our website
[21:13] <knome> that likely needs changes in the code
[21:14] <knome> but it's doable since lubuntu is doing it already
[21:14] <knome> and i think that's an important enough thing to introduce some delta
[21:15] <ochosi> oh, i thought the page was going to get our website header too
[21:15] <knome> well... nope
[21:15] <knome> not without hacking
[21:16] <knome> and no, it's not going to be the live header
[21:16] <knome> :(
[21:17] <ochosi> righty
[21:17] <ochosi> nvm then
[21:17] <ochosi> just do a reduced header with only a link back to our website
[21:17] <knome> probably something like the docs
[21:56] <ali1234> ochosi, bluesabre: can we talk about panel-switch please?
[21:57] <ali1234> i sent some more patches a couple of days ago
[21:58] <ochosi> right, sry, was out helping friends move
[21:58] <ochosi> anything dramatic that needs immediate attention?
[21:58] <knome> ochosi, with logo: https://temp.knome.fi/xubuntu/cdimage/cdimage_xubuntu_logo.png
[21:58] <ali1234> maybe, i'm not sure
[21:58] <ali1234> that's what i want to talk about :)
[21:59] <ochosi> knome: noice!
[21:59] <knome> the code bit we need to change is to make the header image link to xubuntu.org instead of ubuntu.com
[21:59] <knome> and we can fix the favicon at the same time...
[22:03] <ali1234> basically i found two bugs in panel-switch, and possibly a third that i haven't fixed
[22:03] <ali1234> one bug causes it to crash, the other can cause it to corrupt your config, and the third one might cause it to miss changes you made
[22:12] <ochosi> that all sounds sucky
[22:12] <knome> Unit193, hullo? [:
[22:12] <ochosi> ali1234: not sure we can still upload in time, you gotta get to bluesabre with those patches. to the worst we can do an SRU
[22:12] <Unit193> Eh?  I didn't do anything?
[22:12] <knome> not yet..
[22:13] <knome> how does one create a new git repo in launchpad? just push to git+ssh://git.launchpad.net/.. ?
[22:13] <Unit193> Push to create, correct.
[22:14] <knome> anything else i should be aware of?
[22:14] <knome> projects can take git and bzr repositories at the same time?
[22:14] <Unit193> Just make sure to push correctly.
[22:15] <knome> meaning what?
[22:16] <Unit193> https://help.launchpad.net/Code/Git#Repository_URLs
[22:16] <krytarik> ..Plz to gitify the docs too!
[22:18] <knome> ugh
[22:18] <Unit193> knome: https://git.launchpad.net/~unit193/xubuntu-docs
[22:20] <knome> for things that are "completely in our control", i'd go all git or all bzr, so if you want things to happen (and think i'm the right person to listen for advice), then start working on a proposal to move completely to git