[09:18] <bluesabre> TJ-: lots of people have requested including https://github.com/hanschen/ksuperkey for better keyboard integration, that might do the trick
[09:19] <TJ-> bluesabre: thanks; it turned out the keyboard model selected was turning the "win" key into "multi_key"
[09:19] <bluesabre> TJ-: If I enter Super+Space and then type a letter, it appears... so there might be a running app that has claimed it
[09:19] <bluesabre> aha
[09:21] <TJ-> bluesabre: the problem being, in "dpkg-reconfigure keyboard-configuration" there is no bloody way to know what a keyboard model name either looks like, or the keycodes it generates! This is on an Asus T300CHI so originally I selected, quite obvisouly, "Asus Laptop" - der, WRONG! switched it to Generic PC101 and it now generate L_Super 
[09:21] <bluesabre> oh wow
[09:21] <bluesabre> I also have an Asus laptop, glad I didn't look around in there :)
[09:21] <TJ-> so now I can Super_Space and get unicode emojis by typing their common-names :)
[09:22] <TJ-> Using https://github.com/salty-horse/ibus-uniemoji
[09:22] <bluesabre> neat
[09:23] <TJ-> it's very useful... Super+Space "soccer" => ⚽ 
[09:23] <bluesabre> That's pretty awesome actually
[09:23] <TJ-> indeed, saves faffing about trying to look-up unicodes in hex
[09:23] <bluesabre> maybe we can get some more folks in the team *cough* knome *cough* to go for color emojis
[09:24] <TJ-> 👨❤💻 <== was "man" "heart" "computer"
[09:25] <TJ-> bluesabre: ha! when you said "color" I thought I was generating colour and just couldn't see it due to the terminal :)
[09:26] <Unit193> bluesabre: He's the one you've got a chance to win over at least.
[09:26] <bluesabre> Unit193: :D
[09:26] <bluesabre> TJ-: `sudo apt install fonts-noto-color-emoji` and you should have color emojis in your terminal too, if you want them
[09:27] <TJ-> bluesabre: I have powerline fonts not sure if they extend that one; I'll check
[09:29] <TJ-> doesn't look like it
[09:44] <TJ-> 🏓 thanks bluesabre - it works though not sure I need it :)
[09:44] <bluesabre> :)
[09:45] <TJ-> bluesabre: now if they'd only fix this DPMS off issue...!!!
[09:45] <TJ-> I may be able to see them :D
[09:49] <jphilips> hi all, how to report problems with the xubuntu website
[09:53] <bluesabre> jphilipz: https://bugs.launchpad.net/xubuntu-website/+filebug
[09:59] <jphilipz> bluesabre: thanks
[10:13] <jphilipz> are all xfce components in 18.04 gtk2?
[10:13] <jphilipz> want to test xfce gtk2 vs gtk3 and wonder which xubuntu release would have it
[10:22] <brainwash> jphilipz: what is there to test?
[10:22] <jphilipz> brainwash: functionality/behaviour of the old vs new
[10:26] <guiverc> jphilipz, Xfce 4.12 (early 2015) started the move from gtk2 to gtk3 so for an all gtk2 xfce it'd have to be before 2015 (thus EOL).
[10:27] <jphilipz> guiverc: i checked and 4.12 first got release with xubuntu 15.04, so from what you are saying the 4.12 with xubuntu 18.04 isnt all gtk2
[10:30] <guiverc> Nope; 17.10 introduced some new gtk+3 features that prior releases had, 18.04 refined & added more  (note: I'm not a dev, only a user) .  16.04 should have more but 18.04 is too late in my opinion if you wanted mostly gtk2
[10:38] <guiverc> jphilipz, fyi: Xubuntu 16.04 is EOL (3 years as a flavor); sorry I forgot..
[10:40] <jphilipz> guiverc: even if EOL its just for testing purposes :D
[10:41] <jphilipz> seems 16.10 also had some gtk3 bits - https://xubuntu.org/news/xubuntu-16-10-release
[11:00] <M_aD> i'd take it to the support channel instead of chatting about it in the dev channel.
[11:04] <guiverc> sorry M_aD, I wrongly thought this was #xubuntu 
[11:48] <M_aD> :)
[18:38] <jphilipz> an older bug i reported was set from incomplete to expired and i've just added additional info to it, so how to get its status changed from expired?