[00:17] or that's just the way those panel plugins are designed and the icons will always scale up to the panel size? [00:51] ok never mind, I got an answer on Xfce forums that I need to add CSS rules for every plugin in ~/.config/gtk-3.0/gtk.css [01:36] ochosi: think that's something we might be able to do from the panel itself? ^ [01:54] https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1766746 [01:54] Launchpad bug 1766746 in xfpanel-switch (Ubuntu) "Cannot save customized configurations - can only copy defaults" [Undecided,New] [01:54] this bug describes the third issue i was talking about the other day - the one i said i didn't fix [01:55] but reporter says it works with the latest release so i am puzzled by that [02:01] bluesabre: did you pull any other changes in the last release? [02:05] ali1234: nope, just that one MR [02:05] hmm [02:06] well, see the comment i just wrote on that bug... i can really see no way how my patched fixed it, and i think the reporter is wrong about it being fixed [02:08] the real problem is it seems to be a bug in the gui code which i didn't write and don't understand :( [02:08] and i dont think i will have time to figure it out before release [02:09] furretuber saw the same problem while testing my patch [02:09] more evidence it isnt fixed. and also it's why i made it check for orphans when loading the config [02:09] not just saving [02:11] I'm not sure it's a bug. The save button is a toolbar attached to the treeview... so clicking save should save what the current selected item is... I would think [02:11] perhaps then it is a UI design issue :) [02:12] i must say i was not able to reproduce it myself, but i did not try very hard [02:12] Yeah [02:12] It's contextual. If you click save on current configuration, you should save current configuration [02:12] save on gnome, save gnome, etc [02:13] furretuber was loading an old bad configuration to check my patch (which correctly identified the orphans) [02:13] but then on saving the configuration, the orphans always came back because it was copying his old config [02:13] but it could definitely be as you say, if he left the old config selected [02:14] I could make it more verbose, but tooltips with paragraphs inside are bad tooltips :) [02:14] maybe we need a "save active config" button and a separate "make copy" button, with the latter doing what the save button does currently [02:15] idk, but i think it's too late to fix now [02:15] yeah [02:15] not arriving for bionic :) [02:16] just noticed on new bionic ISO in VM, Network Manager Applet is sometimes duplicated on the panel, so I have two icons now, one from Notification Are and one from Status Notifier Items, but I guess this is a well known bug [02:16] tbh, why would you even save an existing configuration? you need to export it if you want the actual file, and there doesn't seem to be any way to save over an existing config [02:18] I use it to save current and then load something else [02:18] I like my panel config, but I gotta make screenshots for releases :) [02:19] yes, i think that's why most people would use it, but i don't see how saving anything other than the real current xfconf is useful? [02:19] Exporting is handy, but only needed if you're sharing or reinstalling [02:20] dunno [02:21] if 5 buttons in the toolbar act on the treeview and one doesn't, I'd say that one isn't working correctly [02:21] if saving current needs to be a separate action, needs to be separate [02:21] it does act on the tree view though - it creates a new entry on it [02:22] i dunno, UI is not my thing. i usually use the command line interface anyway :) [02:22] rephrased... if the other five act on the currently selected item, the other should too [02:22] :) [02:22] It's a bad UI [02:22] i don't think it would be particularly unusual for what is effectively a "new" button to be grouped with the others [02:23] But it's a config app for an app that already has a config app :) [02:23] Really, ochosi needs to add it to the panel :) [02:24] But yeah, we can revisit in b+1 [02:24] tired from the busy cycle... ready to release and relax [02:24] agreed [02:25] the core xfconf code could use some love too [02:25] can't remember if this started out as python3 but it doesn't use a lot of nice py3 features where it could [02:26] Liley started out supporting both. [02:26] nah it definitely didn't support both [02:26] unless it was by accident [02:27] ah... i did write it with python3... just didn't know what i was doing then :) [02:29] Hah, nice. [02:52] :) [15:02] has anybody noticed that panel-xkb is a cpu hog? Has been eating up to 40% of CPU since early alpha 18.04? [16:38] Volkodav: I assume that you have a bug number from back then> [16:39] ? [17:22] leigh [17:22] * willem facepalms [17:22] sorry about that. Was trying to find out if leigh was online. [17:22] LOL :D [17:23] * willem silently moves away - runs out of the channel [17:23] Oh nooo! [17:23] :-) [18:07] another respin looking likely [18:59] what they respining this time? [19:00] not really sure tbh - not anting xubuntuish for sure [19:02] aslong as they don't break anything xubuntuish.. :-) [19:02] :) [19:04] ubiquity and misc ... [19:04] akxwi-dave: ^^ [19:04] ahhh [19:06] Now I deffo hope they don't break anythiny xubuntish..... :-) [20:11] bluesabre_: adding xfpanelswitch to the panel is a bit hard without porting to C (which probably wouldn't be much fun) [20:11] bluesabre_: and regarding the css, would be interesting to see what ppl add there and whether it's the gtk3 panel or the gtk2 panel [20:38] i've started putting all my customizations in git: https://github.com/ali1234/dotfiles [20:56] ah right, you're still using Orion? [20:56] yes [20:57] only xfwm window decorations though [21:08] oh ok