[04:49] <hikiko> hi
[05:13] <PaulePanter> Hi. Where can I find documentation, what Unity does if I press the brightness keys for the laptop monitor? Does it use D-Bus?
[05:36] <hikiko> PaulePanter hi
[05:37] <hikiko> Brightness is not controlled by unity but
[05:38] <hikiko> Either from vendor specific hotkey that has no interface for the os
[05:38] <hikiko> Or acpi or graphic driver
[05:39] <hikiko> Or through hardware register through setpci i think
[05:40] <hikiko> https://wiki.archlinux.org/index.php/backlight
[05:40] <hikiko> This might help
[05:59] <seb128> good morning desktopers!
[05:59] <flocculant> morning seb128
[06:08] <seb128> hey flocculant
[06:30] <PaulePanter> hikiko: Thank you. It’s a Lenovo W541 laptop, and pressing the brightness keys `acpi_listen` shows events, and also there is a popup in Unity. Unfortunately, the brightness does not change though, so I wondered how Unity got the event.
[06:30] <PaulePanter> hikiko: But I see that’s it is probably another component. I’ll look into the graphics driver next.
[06:30] <PaulePanter> hikiko: Thank you very much!
[06:35] <hikiko> PaulePanter, the pop-up is just a notification, the brightness is not controlled by unity
[06:38] <hikiko> PaulePanter, you might want to look at this too: https://bbs.archlinux.org/viewtopic.php?pid=981217#p981217
[06:38] <hikiko> although it's quite old
[06:39] <hikiko> just to get an idea how pop-up notifications work
[06:40] <hikiko> and this: https://wiki.ubuntu.com/NotifyOSD#Brightness_and_backlight_changes
[06:42] <PaulePanter> hikiko: Awesome. Thank you. I’ll wait for my colleague to arrive with the device.
[06:42] <hikiko> good luck :)
[08:03] <Laney> moinonononon
[08:04] <seb128> hey Laney, happy friday!
[08:04] <seb128> how are you?
[08:05] <happyaron> hey guys
[08:05] <happyaron> for yakkety, :) https://launchpad.net/~happyaron/+archive/ubuntu/network-manager/+sourcepub/6419268/+listing-archive-extra
[08:06] <willcooke> morning all
[08:07] <Laney> seb128: good thanks, did some nice climbing last night ;-)
[08:08] <Laney> and today we are going camping for one night!
[08:08] <Laney> how are you?
[08:08] <seb128> happyaron, thanks, going to look at that toay!
[08:08] <willcooke> thanks happyaron
[08:08] <Laney> hi willcooke & happyaron too
[08:08] <Laney> what is the happening
[08:08] <seb128> Laney, I'm good, didn't find anybody to play tennis yesterday evening though, which was frustrating because neither was nice and I had nothing else to do
[08:08] <willcooke> g'day.  Summer is over.
[08:08] <seb128> oh, well
[08:08] <seb128> hey willcooke
[08:09] <seb128> today is going to be "SRU drum day"
[08:09] <willcooke> seb128, but at least you got to teach me about deb diff :)
[08:09] <seb128> :-)
[08:09] <willcooke> not quite tennis though
[08:09] <seb128> and sponsored the libreoffice SRU from Sweet5hark
[08:09] <seb128> right
[08:09] <seb128> I'm going to try to motivate others to SRU a bit as well
[08:09]  * seb128 looks at Laney attente Trevinho :p
[08:09] <Sweet5hark> seb128: are we getting cookies?
[08:09] <happyaron> ah and we get zfs accepted in debian, so starting the merging work
[08:10] <willcooke> happyaron, Woo!  Nice
[08:12] <seb128> willcooke, I wonder if it would make sense to have a SRU trello board?
[08:12]  * willcooke ponders
[08:12] <seb128> we could have a stack of updates we need to SRU, libreoffice/file-roller/gnome-calendar/n-m/gnome-software-/glib/gvfs/...
[08:13] <seb128> + the oem bugs
[08:13] <seb128> it might give some visibility on those
[08:13] <willcooke> sure thing.
[08:13] <seb128> not sure how to do better
[08:13] <willcooke> It's easy to set up now
[08:13] <seb128> but I've a feeling we don't get much LTS work traction atm
[08:13] <willcooke> so we can at least try - there's no harm done
[08:13] <seb128> I don't know how to solve that and if the trello would help though
[08:14] <willcooke> seb128, what do you mean by not much traction?  Like we should be pushing more SRUs?
[08:14] <Sweet5hark> seb128: yeah, and it also helps seeing when a SRU starts rotting away in review ... (I,for one easily loose sight of that)
[08:14] <seb128> Sweet5hark, right
[08:15] <seb128> willcooke, yeah, we are not doing a good job at keeping the fixes/updates rolling for the LTS
[08:16] <willcooke> oh, I thought we were doing ok.  In which case, yes, lets track
[08:16] <willcooke> https://trello.com/b/ySwNniD5/sru-board
[08:17] <willcooke> seb128, let's add the tag "desktop-trello-import" to the bugs
[08:17] <seb128> willcooke, how does your script know to which board to import?
[08:17] <willcooke> (I changed the tag to include desktop otherwise I was worried we'd clash with others)
[08:17] <willcooke> seb128, you have to tell it - I tried to be clever, but it just wasnt flexible enough
[08:20] <seb128> willcooke, can't edit that board
[08:20] <willcooke> seb128, you have to "join" it first I think
[08:21] <willcooke> click "show menu" on the rhs
[08:21] <willcooke> then you should have "join board" at the top
[08:21] <seb128> k
[08:21] <seb128> done
[08:21] <willcooke> oh, there is also a button I can click here...
[08:21] <willcooke> add add team members
[08:21] <willcooke> done that too
[08:22] <willcooke> *add all
[08:22] <Laney> wow
[08:27] <willcooke> seb128, added a "In review queue" list
[08:28] <seb128> good :-)
[08:29] <willcooke> seb128, just thinking about this...
[08:30] <willcooke> I was going to say we should add bugs to the board, but...
[08:30] <willcooke> is it the case that sometimes more than one bug combine to become an SRU?
[08:30] <willcooke> like, should we track each bug in the baord, or each "SRU Case"
[08:31] <seb128> bugs
[08:31] <willcooke> oki
[08:31] <seb128> if you fix 3 bugs in one upload it's fine to move the 3 cards
[08:31] <willcooke> in which case, let's add "desktop-trello-import" tags and then I can import them
[08:31] <seb128> k, I'm doing that
[08:32] <willcooke> once the import is run the tags are removed, so if we want to import it in to someones board we can just retag and run the script again
[08:34] <Laney> sooooooooo
[08:34] <Laney> what am I supposed to do?
[08:34] <willcooke> Laney, couple of things potentially
[08:34] <Laney> I got emailed by trello about some updates from this week that I would have done anyway
[08:34] <willcooke> Laney, tag bugs which need to be SRU'd "desktop-trello-import"
[08:35] <willcooke> Laney, or pick things from the backlog to work on them
[08:35] <seb128> willcooke, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=desktop-trello-import
[08:35] <seb128> looks good?
[08:36] <seb128> Laney, just put things you plan to do in the trello/take the cards if they are already there
[08:36] <seb128> Laney, it's useful so others also know you plan to do those
[08:36] <willcooke> seb128,  thanks!  Just going through my mental list to see if I can think of anything else
[08:37] <seb128> Laney, also it gives us a list of things people can "help on" and help us tracking/make sure we don't forget to work on e.G issues raised by the oem team
[08:37] <Laney> seb128: OK it sounded like drum banging and not doing a good job and trying to motivate means that you think I'm not doing enough work already
[08:38] <Laney> when actually I have a very big list of things to work on
[08:38] <seb128> I know, I never implied that you were not working hard
[08:38] <seb128> but atm imho we have issues
[08:38] <willcooke> Laney, not the case.  We're just trying to get organsied.  Sorry if you got the impression we were moaning
[08:38] <seb128> - having a view of what people are working on/what is their todolist
[08:38] <seb128> - making sure things don't fall into the cracks/get forgotten
[08:39] <willcooke> Trevinho - is the missing menus ready for SRU yet?  Still some things to do there?
[08:41] <seb128> Laney, I think it's going to help to have a "pool" of "issues we need to work on", some people like robert_ancell said in the past that they would be happy to tackle on some of those but they just don't have good visibility on what got oem escalated/flagged as important
[08:47] <seb128> willcooke, maybe rename the board to include "desktop" in the name?
[08:47] <willcooke> done
[08:47] <seb128> thanks
[08:47] <seb128> the current set looks good?
[08:48] <seb128> +1 from me
[09:15] <andyrock> morning
[09:16] <seb128> hey andyrock! how are you?
[09:17] <andyrock> seb128: not bad not bad you?
[09:17] <seb128> andyrock, I'm good thanks ;-)
[09:17] <seb128> it's friday!
[09:27] <seb128> andyrock, is your gnome-menus fix submitted upstream? if we land it without the libunity fix does it make things more buggy or not?
[09:28] <andyrock> it's more buggy unity side
[09:31] <seb128> :-(
[09:38] <seb128> willcooke, can you reimport, I added bug #1571574
[09:39] <willcooke> python getopt examples
[09:39] <willcooke> err
[09:39] <willcooke> I mean yes
[09:39] <willcooke> seb128, done
[09:43] <seb128> willcooke, thanks
[09:43] <willcooke> just trying to add cmd line args to my script
[09:44] <seb128> to specify the board?
[09:44] <willcooke> getopt is ace
[09:44] <willcooke> yeah, the board, the project etc
[09:44] <seb128> nice!
[09:44] <willcooke> I decided against just doing a global import of anything in "ubuntu" with the tag
[09:44] <willcooke> because each run of the script is bugs -> one board
[09:44] <seb128> yeah, probably be better to be explicit
[09:44] <willcooke> n bugs -> 1 board
[09:44] <willcooke> so if we do it on a per project level
[09:45] <willcooke> we can have a big tag fest
[09:45] <willcooke> and then work through them in a more granular fasion
[09:45] <willcooke> fashion
[09:46] <seb128> yeah
[09:46] <seb128> k, I'm out for lunch with friends
[09:46] <seb128> back in ~1.5h
[09:46] <willcooke> seb128, have fun!
[09:46] <seb128> thanks!
[09:47] <Laney> pitti: do you know if there's a general problem with dkms tests on yakkety/amd64?
[09:47] <Laney> see glib2.0
[09:48] <pitti> Laney: yes, there is; all kernel module builds currently fail on amd64 due to the new -fPIE
[09:49] <pitti> Laney: kernel team is aware of/working on it
[09:49] <Laney> ack
[09:49] <pitti> Laney: in the meantime, I keep force-skiptest'ing packages which get broken by this
[09:49] <Laney> thanks, I'll do so for glib then
[09:49] <pitti> annoying, I know
[09:49] <pitti> cheers
[09:49] <Laney> is there a bug to spy on?
[09:50] <pitti> I'm not aware of one, /me searches
[09:50] <Laney> doesn't matter
[10:58] <larsu> pitti: I guess this is a false positive? https://github.com/systemd/systemd/pull/3245
[10:59]  * larsu doesn't understand the error
[10:59] <larsu> also, hi pitti!
[10:59] <pitti> hey larsu
[10:59] <larsu> and hi everyone else. happy sunny friday!
[10:59] <pitti> larsu: ITYM "false negative" :)
[10:59] <pitti> larsu: it was raning since yesterday :/
[10:59] <pitti> but en route to Dresden where it's sunny
[10:59] <larsu> pitti: oh, yeah, of course false negative :)
[11:00] <pitti> larsu: yep, tests are PASS, just the cloud acting up
[11:00] <larsu> pitti: ok cool. Should I mention that on the bug or what's the process?
[11:00] <larsu> retrigger?
[11:00] <pitti> larsu: I just dif
[11:01] <pitti> did
[11:01] <pitti> larsu: it's fine, we merge stuff with these kind of noise
[11:01] <larsu> thanks! :)
[11:01] <larsu> pitti: we do too in cockpit, but I wanted to make sure
[11:01] <pitti> larsu: doing systemd now, as part of cockpit?
[11:02] <larsu> pitti: not really. I just use busctl a lot to debug things :)
[11:02] <larsu> my other systemd patch is in the same function :)
[11:02] <larsu> we have a summer of code student that's working on making time units work from cockpit
[11:03] <larsu> which will need some changes in systemd that we're just discussing
[11:35] <Sweet5hark> schni ... scha ...
[11:36] <Sweet5hark> +n
[11:36]  * pitti runs away screaming
[11:36] <pitti> hate that song!
[11:37]  * Sweet5hark follows pitti with a giant plush crocodile
[11:38] <pitti> dieu merci il est vendredi
[12:00] <desrt> hello europeans!  i am no longer with you
[12:02] <pitti> hey desrt! made it back home in one piece?
[12:02] <desrt> yes.  2 hours and 50 minutes late.
[12:03] <desrt> SO ANGRY
[12:03] <desrt> i would have strongly preferred 3 hours late :)
[12:03] <Laney> j-u-s-t-g-o-a-b-i-t-s-l-o-w-e-r-p-l-e-a-s-e
[12:03]  * desrt is out 600€ on account of 10 minutes
[12:03]  * Laney suspects it was the other way
[12:04] <desrt> hm?
[12:04] <Laney> justgoabitfaster
[12:04] <desrt> ya.  indeed.
[12:04] <desrt> i'm sure they made damn sure to come in under the 3 hour mark
[12:06] <Laney> :)
[12:06] <Laney> well welcome back anyway
[12:09] <seb128> hey desrt, wb!
[12:10] <desrt> thanks :)
[12:10]  * desrt gets the first crackrock new API proposal of the day, decides that it's not quite crackrock enough, seeks to improve it
[13:20] <GunnarHj> seb128: Hi Sebastien, do you have time to sponsor bug #1574745 (yakkety and xenial)? Would be good to get rid of that regression.
[13:22] <seb128> GunnarHj, hey, sorry but I don't think I know enough about those/understand the problem to be confident the changes are correct without spending some time trying to understand what you did, and I don't think I'm going to be able to allocate that slot today ... maybe try to see with the day patch pilots?
[13:25] <GunnarHj> seb128: I see. No pilot on duty, as it seems. Not emergency, but me being impatient as usual. ;)
[13:25] <seb128> GunnarHj, I'm going to try to have a look on monday if nobody picked up by then
[13:26] <GunnarHj> seb128: Would appreciate that, thanks. Have a nice weekend!
[13:26] <seb128> thanks, you too!
[14:00] <willcooke> desrt, would you have time to take a look at https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1503758 today, or early next week?
[14:00] <desrt> i looked at this briefly yesterday
[14:01] <desrt> i don't really understand the problem (or the domain)
[14:03]  * desrt reads the workaround patch to get a feel
[14:05] <willcooke> thanks desrt
[15:05] <Trevinho> seb128: hey...
[15:05] <Trevinho> seb128: how are you?
[15:06] <Trevinho> seb128: I was looking at the keyboard backlight thing some time ago, and I think we'd need also http://pastebin.ubuntu.com/16389938/
[15:06] <seb128> Trevinho, feel free to put a mp up for it?
[15:06] <seb128> Trevinho, mario verified that the <= 0 to <0 change fix the boot case
[15:07] <seb128> what does your patch do?
[15:07] <seb128> also why didn't you propose the change back then?
[15:07] <Trevinho> however... I can't really test this here... Since in my TPs there are no ubus events fired, so, i didn't test it directly. A friend of mine with an asus laptop BTW, and fixes things
[15:07] <Trevinho> seb128: well I did this some days ago, but I wanted to test it better wih him, and since I don't have a machine under my fingers with full upower support I can't do that
[15:08] <seb128> ah, ok
[15:08] <seb128> well I upload the upstream patch for now
[15:08] <Trevinho> seb128: however.. The change basically listens for upower changes of the kbd backlight, fired when you press the keys, and then it remembers that value when you suspend
[15:08] <seb128> but we can replace by a better version
[15:08] <Trevinho> in this way, when you get back to your session or after idle, it goes back to the proper value
[15:08] <seb128> nice
[15:08] <seb128> can you add the patch to the bug?
[15:09] <Trevinho> seb128: well, that's fine... i also was thinking that that = here was wrong :)
[15:09] <seb128> maybe superm1 can test it
[15:09] <Trevinho> seb128: ok
[15:09] <seb128> thanks
[15:09] <seb128> oh, and I'm good otherwise
[15:09] <seb128> a bit too warm here though!
[15:09] <seb128> but I'm not going to complain, tomorrow is like 12°C
[15:09] <Trevinho> seb128: the only thing that maybe I should include, is that I should ignore the changes while suspended... Otherwise we'll save the brightness change to 0... Although this kind of change shouldn't be emitted by upower, since there's no manual intervention
[15:10] <Trevinho> seb128: yeah.. Here as well we've some winter-reloaded
[15:11] <willcooke> heh, same here
[15:11] <Trevinho> it's still almost 20 though
[15:11] <willcooke> 14 here
[15:11] <Trevinho> but cloudy, windy and rainy... :-/
[15:12] <Trevinho> willcooke: ah, is there a tag to get sru bugs being added to the SRU board?
[15:13] <Laney> Trevinho: doesn't u-s-d already set that when it calls SetBrightness?
[15:14] <Trevinho> Laney: the problem is when you change the kbd backlight using your ACPI keys
[15:14] <Trevinho> Laney: in that case there's no SetBrightness call
[15:14] <willcooke> Trevinho, not, just add the desktop-trello-import tag, and I will import it for you
[15:14] <Trevinho> Laney: but there are events fired from ubus
[15:14] <Trevinho> willcooke: will it go in the SRU board or then I shouldd copy it there?
[15:15] <Laney> k
[15:15] <willcooke> Trevinho, it will go direct to that board (I'll tell the script to do that)
[15:15] <Trevinho> willcooke: ok
[15:15] <Trevinho> willcooke: thanks
[15:16] <willcooke> Trevinho, np, if you want, just paste the bug link here and I'll do it
[15:16] <Trevinho> seb128, Laney: here what happens when you change the kbd backlight in fully upower aware laptops (not mine): http://i.imgur.com/stBtIUk.png
[15:19] <Trevinho> I also was thinking how I could manage my case... Thinkpads doesn't notify for kbd backlight changes, since it's something at system level. So We'd need to make upower to check the actual status when doing GetBrightness (instead of using a cached value as it's doing right now).. But.. well not sure upower upstream would be happy about that. But neither the
[15:19] <Trevinho> kernel module devs want to emit any key event for thinkpad_acpi (being something that will change despite userspace deamon settings, it's reasonable)
[16:22] <willcooke> news just in, Design have +1d the terminal tabs styling.  So I will SRUify that bug
[16:22] <willcooke> next week
[16:22] <willcooke> by which I mean, explict +1 on the bug
[16:27] <willcooke> Laney, going to meet Adam Hart-Davis on Sunday :)
[16:30] <flocculant> willcooke: tell him he's awesome :)
[16:33] <willcooke> flocculant, will do :)
[16:34] <davmor2> willcooke: he's the really interesting history type bloke right glasses beard and stuff?
[16:34] <flocculant> davmor2: yea
[16:34] <willcooke> davmor2, https://www.youtube.com/watch?v=8ODCBYVdxiM
[16:36] <willcooke> right, swimming lessons duty.  bbl
[16:36] <davmor2> nice
[16:38] <seb128> willcooke, enjoy!
[16:38] <seb128> calling it a week here
[16:38] <seb128> have a nice w.e everyone
[16:39] <seb128> with monday off here (and in some other countries as well I think?)
[19:00] <willcooke> night all
[19:00] <willcooke> happy weekend
[19:52] <a1fa> hello, i've hit on the title bar bug again :0
[19:53] <a1fa> same thing, window was open for long time (maximized), i unmaximed it, and i was no longer able to to anything with the window ;)