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