[07:33] <knome> bluesabre, not ready yet :P
[07:33] <knome> bluesabre, i can prepare the artwork branch once i'm ready with it as well
[11:53] <bluesabre> brainwash: thanks, added the changelogs
[13:13] <bluesabre> ochosi: https://bugs.launchpad.net/ubuntu/+source/greybird-gtk-theme/+bug/1795135
[14:12] <bluesabre> ochosi: an interesting one, https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1795138
[21:33] <ochosi> bluesabre: i'm not sure i understand the bugreport about greybird/panel. can you describe simple steps to reproduce?
[21:34] <ochosi> the xfpm bug sounds like a upower issue
[21:34] <ochosi> please check the output of the upower cli to be sure
[21:34] <bluesabre> ochosi: move the mouse cursor to the top of the screen (0px) (where the panel is), and you cannot click on any of the window buttons
[21:34] <ochosi> (xfpm simply presumes it's not a laptop if it doesnt have a battery
[21:34] <ochosi> )
[21:35] <ochosi> right, i presume because of padding/widget border of 1px
[21:35] <ochosi> could probably be tackled by removing any border for those buttons in the theme
[21:36] <ochosi> have you tried that with gtkinspector?
[21:39] <bluesabre> trying now
[21:40] <bluesabre> always a pain to get the css override to work
[21:43] <bluesabre> no luck
[21:43] <bluesabre> Guessing that's probably the case though since adwaita is unaffected
[21:44] <ochosi> yeah possible
[21:45] <ochosi> i can try to quickly test that myself
[21:45]  * ochosi starts up laptop...
[21:48] <ochosi> right
[21:49] <ochosi> bluesabre: you know about the bug with whiskermenu flickering when you hover it with the mouse?
[21:49] <bluesabre> ochosi: yes
[21:49] <bluesabre> this seems related, but moreso
[21:50] <ochosi> that's when it's at the top border and stuff and it seems that gtk cannot decide whether/how to process the mouse position/signals
[21:50] <ochosi> if i drop the "margin: 1px" from greybird, i don't only get the same effect for the window buttons, they also look a bit crappier
[21:50] <ochosi> because there is no margin between the buttons
[21:51] <ochosi> and if you want to support vertical and horizontal buttons you cannot conditionally decide which margin to add
[21:51] <ochosi> (unless i add .horizontal and .vertical classes in the panel, which may be a good idea anyway)
[21:51] <bluesabre> Was just about to suggest that
[21:51] <bluesabre> :)
[21:51] <ochosi> but still, you'll get the same flickering as with whisker
[21:51] <ochosi> not sure that makes the situation a lot better
[21:52] <bluesabre> right, but that means it will work more than 0% of the time
[21:52] <bluesabre> :D
[21:52] <ochosi> i can reproduce that with adwaita btw
[21:52] <ochosi> you get the same flickering there
[21:52] <bluesabre> the flicker, yeah
[21:52] <ochosi> and that is most likely a gtk+3 bug
[21:52] <bluesabre> is there any frame_extents hacking we could employ here?
[21:52] <ochosi> because the panel is definitely at the location 0x0 and doesn't have any borders set
[21:53] <ochosi> uff, maybe
[21:53] <ochosi> not sure
[21:53] <ochosi> one could also ask olivier about this kind of bug
[21:53] <ochosi> not sure he uses the panel though
[21:54] <ochosi> anyway, adding the classes to the panel -> certainly a good idea
[21:54] <ochosi> (btw, switching to different themes and the panel icons still being correctly colored because of gtk+3 and symbolic stuff is quite noice)
[22:23] <bluesabre> Indeed
[22:24] <bluesabre> ochosi, BTW, I'm starting to work on an Xfce screen saver based on early light-locker by your suggestion
[22:25] <bluesabre> I think it could be nice to have in -core, and less of a pain than light-locker
[22:26] <ochosi> right
[22:26] <ochosi> i guess people will be happy to have a replacement for xscreensaver
[22:26] <ochosi> especially a less-ugly one
[22:26] <ochosi> ok, i have a working patch for setting orientation related classes on the panel
[22:27] <bluesabre> Sweet
[22:27] <ochosi> i'll try to clean it up and push it
[22:30] <brainwash> bluesabre: what makes early light-locker special?
[22:31] <ochosi> brainwash: it doesnt rely on lightdm but locks inside the session
[22:32] <ochosi> in theory one could try to provide both features in one locker
[22:32] <ochosi> with an option to either lock within the session or switch to the greeter
[22:32] <ochosi> (the latter is probably the securer method)
[22:33] <ochosi> bluesabre: so i have the final patch, but no git server to push it to...
[22:33] <brainwash> reskinning mate-screensaver would not be an option?
[22:34] <ochosi> it's not about skinning
[22:34] <ochosi> early light-locker was gnome-screensaver without depends
[22:34] <ochosi> that's why i called it *light* locker
[22:34] <ochosi> bluesabre: if you wanna give it a try: http://dpaste.com/2QKSTR8
[22:34] <brainwash> ah. so, mate-screensaver still depends on mate services
[22:35] <ochosi> i would guess so
[22:35] <bluesabre> Yes
[22:35] <ochosi> but i haven't ever tried it or taken a look
[22:35] <bluesabre> I tried porting mate-screensaver earlier
[22:35] <bluesabre> Lots of mate-specific bits
[22:36] <ochosi> anyway, i'll push that panel commit another time and then i can also "fix" that bug in greybird
[22:36] <bluesabre> ochosi: cool. Will test it later, currently on the go
[22:38] <ochosi> bluesabre: i guess you can start about somewhere here: https://github.com/the-cavalry/light-locker/commit/6bde1f1785c131617f53df2a6fa195eb4ae1c9e9
[22:38] <ochosi> that may be one of the last meaningful commits with a lock dialog
[22:39] <ochosi> night y'all
[22:41] <bluesabre> ochosi: that's exactly where I've started :D
[23:25] <Spass> bluesabre, ochosi, that flickering bug is not Xfce-only, see more here: https://ubuntuforums.org/showthread.php?t=2397371
[23:25] <Spass> and not GTK-only, since Plank flickers on Kubuntu also
[23:27] <Spass> and here's a recent post on r/xfce subreddit, same issue https://www.reddit.com/r/xfce/comments/9jgztj/bug_in_xfces_panel_causes_weird_flickering_is/
[23:52] <Spass> (well... Plank is a GTK app, so in fact it still could be a GTK bug)