[00:02] <brainwash> elfy: bug 1395720 has been marked as security issue
[00:03] <brainwash> that's probably incorrect, or?
[00:03] <elfy> mmm
[00:03] <elfy> welll 
[00:04] <elfy> who marked it ? Alberto again? 
[00:04] <elfy> oh 
[00:04] <elfy> lol :p
[00:04] <brainwash> ofc, he likes to mess with our bug reports
[00:06] <elfy> posted
[00:06] <elfy> afaik bluesabre is aware and dealing with it - I can't mark the importance 
[00:07] <brainwash> it's a minor thing anyway
[00:07] <elfy> brainwash: does the bug importance change do anything other than annoy *us* 
[00:08] <elfy> if not - I'd shrug and wait for it to get a fix :)
[00:08] <elfy> I actually only reported it so there was a paper trail for us 
[00:08] <brainwash> bug importance is almost meaningless to us :)
[00:09] <elfy> it almost always is when alberto starts fiddling 
[00:09] <elfy> karma whoring 
[00:10] <elfy> bluesabre: while I think about it - got the new xfpm and ll tab
[00:11] <elfy> exactly what do we want people to test with this - seems like a really good choice for doing specific testing this cycle rather than the previous 'here's the package tracker' 
[00:11] <elfy> I'm about over the weekend if you are at the same time - if not maybe mail me 
[00:11] <elfy> thanks 
[00:12] <elfy> e.g. I'd like to be able to say something like 
[00:12] <elfy> please test these scenario's 
[00:12] <elfy> ochosi: ^^
[00:14] <elfy> mmm think that makes sense lol
[01:33] <elfy> brainwash: so - who does have bug powers to set importance to a sensible level? 
[01:33] <brainwash> elfy: alberto does :>
[01:34] <elfy> ha ha ha 
[01:34] <elfy> is there not one of us who can?
[01:35] <elfy> thought there was 
[01:35] <elfy> if not perhaps we should get xpl to talk to someone about it 
[01:36] <brainwash> we shouldn't bother with the importance, but at least remove the security issue status
[01:36] <elfy> yea
[01:36] <elfy> mmmm
[01:37] <elfy> really? 
[01:37] <elfy> other's look then surely?
[01:37] <elfy> I can see changing private to public as being useful :)
[01:38] <elfy> oh good lord a security bug - oh nvm ignore that :)
[01:38] <brainwash> btw did you see the updates to bug 1363540 ?
[01:39] <brainwash> I don't know if you are actually affected by this, or just happen to noticed this while testing parole
[01:39] <brainwash> to notice
[01:39] <elfy> I did of course, but didn't take much notice of the intervening months
[01:40] <elfy> random changes to bug titles - mean that I don't see them the same anymore ... 
[01:40] <elfy> didn't catch that as the parole bug 
[01:41] <brainwash> ah, well, it's not a parole specific bug anymore :)
[01:41] <elfy> then not my bag L:)
[01:41] <elfy> :)
[01:42] <elfy> and I've never got a satisfactory explanation as to what to do with patches 
[01:42] <elfy> and I guess that lots of people see patches and think - oh yea a patch ... 
[01:43] <brainwash> I've attached the patched script file, you just download it, make it executable and test it
[01:43] <elfy> should be an 'Idiot's guide to pacthes and linux'
[01:43] <brainwash> it's a plain shell script
[01:43] <elfy> brainwash: glad you understand that - this is *buntu :D
[01:44] <elfy> linux for people :)
[01:44] <brainwash> applying patches is not that complicated. there are some ubuntu wiki articles you could read
[01:45] <elfy> I don't write docs
[01:46] <elfy> people who do - don't generally think about the end user
[01:46] <elfy> and I am NOT talking about *our* docs people there 
[01:47] <elfy> there really should be a usable wiki for that stuff given that people often leave patches
[02:37] <elfy> so
[02:37] <knome> yes
[02:37] <knome> what can i do for you
[02:38] <elfy> when we look at the slideshow 
[02:38] <knome> yeppers
[02:38] <elfy> how about pointing people to -offtopic as well at least 
[02:38] <elfy> maybe cut out some of the 
[02:39] <elfy> 'hey I installed' peeps in support
[02:39] <knome> they're mainly fine
[02:39] <elfy> so we see a greater % of people in support actaully needing help
[02:39] <knome> but i see your point..
[02:39] <elfy> if we at least advertised both on the slides ... 
[02:40] <knome> since #x isn't huge traffic, it's nice to see somebody say "hey, nice work" once in a while
[02:40] <knome> we could do that definitely
[02:40] <elfy> what does iot ake 
[02:40] <knome> nothing
[02:40] <knome> :P
[02:40] <knome> well, we can do it
[02:40] <elfy> yea yea - understand that
[02:40] <elfy> but
[02:40] <knome> it's just a matter of changing the wording
[02:41] <knome> i have work items for the slideshow already, i'll keep that in mind
[02:41] <elfy> imagine bert - really pissed off in support - waitinig for someone to help - seeing a bunch of people come and go saying 'woohoo - works for me' 
[02:41] <knome> ...when i work with them :)
[02:41] <elfy> and he still gets no help 
[02:41] <knome> yeah... but that is unfair sometimes
[02:41] <elfy> just saying - perceptions
[02:42] <knome> bert might be in the channel for 5 hours, and dozens of other people have their problems solved
[02:42] <knome> but bert not, because he might have an odd problem or one that doesn't have a solution
[02:42] <elfy> of course it is, but many are new and don't understand the bus principle involved in IRC
[02:42] <knome> yep
[02:43] <elfy> for the sake of one line - however worded
[02:43] <knome> so maybe the better solution would be to point to an URL that explains, XYZ
[02:43] <elfy> go her for help - go here to gloat 
[02:43] <knome> yep
[02:43] <knome> something like that
[02:43] <knome> could even make a playful slide out of that
[02:44] <knome> not too playful if something isn't working but..
[02:44] <elfy> yea yea - but slideshow - people read that stuff then then read the paper till the next shot
[02:44] <knome> yup
[02:44] <elfy> 2 cycles to go - try stuff - we now know *where* people come *from*
[02:46] <knome> yep
[02:46] <knome> i should gather those stats as well i guess
[02:46] <elfy> I'd not yet
[02:47] <elfy> change slide
[02:47] <elfy> then get stats
[02:48] <knome> i'll make them month-based anyway
[02:48] <knome> so we can even track the effect of the change
[02:48] <elfy> yea 
[02:49] <elfy> but keep quiet then give us 18 months of it :)]
[02:50] <knome> haha, i'll make a note not to tell you
[02:50] <elfy> too late - expecting it now ... 
[02:54] <knome> i didn't know you were carrying a baby
[02:54] <knome> but congrats ;>
[03:00] <elfy> too late - expecting it now ... 
[03:00] <elfy> just so long as it's not a !conga-rat
[13:09] <ali12341> ochosi: any idea how i fix squashed up menus?
[13:38] <bluesabre> brainwash: if it was a problem, wouldn't there be more complaints... or no?
[13:38] <bluesabre> elfy: it only requires light testing... if the tab shows up, and functions as expected, all is well
[13:38] <bluesabre> Unit193: thanks, I'll tweak it to get the builds going again
[13:39] <bluesabre> brainwash: yeah, I'm going to fix the auth issue by switching to polkit inside of catfish and mugshot
[13:40] <bluesabre> ali12341: I think that is/was an issue with monitor struts and xfwm, or is it something different?
[13:41] <bluesabre> ochosi, ali12341: let me know when you have something release worthy for greybird/orion :)
[14:43] <brainwash> bluesabre: I guess so.. some people do complain that they still see the black screen issue
[14:43] <brainwash> bluesabre: but I'm just questioning the logic
[14:47] <bluesabre> we can flip the switch and see what happens
[14:47] <bluesabre> :D
[15:01] <brainwash> bluesabre: it's just a bit confusing. TRUE or FALSE.. logind or not logind..
[15:17] <brainwash> bluesabre: logind-handle-lid-switch is set to FALSE by default, xubu default settings sets it to FALSE although it's the default value anyway
[15:18] <brainwash> I guess I'll have to bother you with this until the mystery is solved :)
[15:54] <ali12341> ochosi: i don't get this. half the reason why orion looks different in gtk 3.14 is because it contains css tat does nothing in gtk 3.12
[15:54] <ali12341> for example the notebook styles do nothing in 3.12
[15:54] <ali12341> "fixing" it in 3.14 involves... deleting a bunch of rules and nothing else
[16:10] <ali12341> cool... notebook tabs fixed
[16:11] <ali12341> i'm just making the gtk3 theme look like the gtk2 theme at this point, because i don't understand what it is actually supposed to look like
[16:11] <ali12341> and because in 14.04 the gtk3 theme does look the same as the gtk2 theme
[16:18] <ali12341> https://github.com/ali1234/Orion/tree/gtk3.14try2
[16:31] <ali12341> that just leaves the squashed up menus
[22:33] <Unit193> Oh, and xfdashboard 0.3.5-0ubuntu1 has been uploaded.
[22:52] <ochosi> evening all
[22:53] <ochosi> ali1234: not sure what the problem with the menus might be tbh
[22:53] <knome> hullo ochosi 
[22:53] <Unit193> Howdy.
[22:56] <ali1234> ochosi: seems like a bunch of elements have slightly less padding, not just menus
[22:57] <ochosi> right
[22:57] <ochosi> it's possible that this is an older thing even, orion hasn't received too many gtk3 updates lately
[22:57] <ochosi> so i'm not quite sure what state it is in
[22:57] <ali1234> yeah that would explain the weird non-working css stuff too probably
[22:57] <ochosi> but i remember some similar issues with greybird a longer while back
[22:58] <ali1234> do you think it's reasonable to just make the gtk3 look like the gtk2?
[22:58] <ochosi> yeah, that's the ideal imo
[22:58] <ali1234> cos the gtk2 should not change, right?
[22:58] <ochosi> gtk2 isn't very flexible is all
[22:58] <ochosi> with gtk3 you have a lot more options, but if you really use them, gtk2 will look out of place
[22:58] <ochosi> so i tried to find a compromise with greybird
[23:00] <ali1234> also, those transitions...
[23:00] <ali1234> is that new in 3.14?
[23:00] <ali1234> i should be able to put transition: none; somewhere right?
[23:01] <ali1234> and kill them all
[23:06] <ochosi> yeah, i guess
[23:06] <ochosi> in one of the global styles
[23:06] <ochosi> frankly, i've never really touched orion much
[23:06] <ochosi> it was always satya's theme
[23:07] <ochosi> i just helped with the xfce parts
[23:08] <ali1234> what's the connection between shimmer and numix, btw?
[23:09] <ali1234> i mean, numix project is a separate thing, right? with commercial stuff...
[23:12] <ochosi> yeah, i don't know, we cooperate on the themes and as far as our cooperation goes, that's in shimmer
[23:12] <ochosi> i'm not involved with the numix project in general
[23:13] <ochosi> bluesabre: i just tagged greybird 1.5 after fixing the last visual glitches i found in 3.14. if we find more, i can always do point releases, but this one is ready for upload
[23:14] <ochosi> bluesabre: https://github.com/shimmerproject/Greybird/releases/tag/v1.5
[23:46] <ochosi> elfy: you still awake?
[23:47] <ochosi> or anyone else having a vivid install at their disposal
[23:47] <ochosi> just need a very quick bug confirmation over here
[23:48] <Unit193> "Disposal"?  No, and if it's filing a bug report, then I also don't.
[23:51] <ochosi> nah, this is one i'd fix myself
[23:51] <ochosi> just wanna confirm it first since it's really easy to check
[23:52] <ochosi> pull either of the "blank after" scales in xfpm-settings > display tab around and then look at the value saved in xfconf (e.g. with xfce4-settings-editor)
[23:52] <ali1234> i've got a vm...
[23:52] <ochosi> if the value is the same, then there's a bug. (it should be multiplied with 60)
[23:53] <ochosi> ali1234: that'd work too
[23:54] <ochosi> just wanna make sure i don't have some leftover mumbojumbo pieces of xfpm lying around on my drive that are interfering before i dig into the code
[23:54] <ali1234> this is the daily from earlier today
[23:55] <ochosi> yeah, that should be fine
[23:57] <ali1234> what am i looking at in the xfconf?
[23:57] <ali1234> blank-on-ac?
[23:57] <ali1234> if so, it is notmultiplied by 60 here
[23:57] <ochosi> yup
[23:57] <ochosi> ok
[23:57] <ochosi> then i have something to fix i guess
[23:58] <ochosi> first i gotta find who introduced that regression and when
[23:58] <ochosi> thanks for checking ali1234 
[23:58] <ali1234> also dpms-on-ac-sleep which is "put to sleep after" i guess
[23:58] <ochosi> rly?
[23:58] <ochosi> meh
[23:58] <ali1234> and "switch off after" -> dpms-on-ac-off
[23:59] <ochosi> thing is, dpms seemed fine when checked with xset q
[23:59] <ali1234> basically none of those sliders is multiplied by 60
[23:59] <ochosi> but screensaver was wrong
[23:59] <ali1234> the one on system tab isn't either
[23:59] <ochosi> so maybe the dpms values are multiplied elsewhere but saved as is