qenghoZaoshanghao, good morning, everyone.00:44
qenghohikiko: hi ki ko04:44
=== JanC is now known as Guest89378
=== JanC_ is now known as JanC
hikikohi qengho05:40
pittiGood mornning05:50
hikikogood morning pitti06:00
=== Guest41563 is now known as fredp
=== fredp is now known as Guest24509
willcookehey Trevinho08:01
andyrockmorning all08:19
seb128hey andyrock, how are you?08:24
andyrockhey seb128 trying to finish the branch of the copy dialog by the end of the day :D08:24
seb128I'm good thanks08:26
hikikoTrevinho, since I accidentally fixed compiz's show desktop too I did an MP here: https://code.launchpad.net/~hikiko/compiz/compiz.shodesktop-skip-anim-option/+merge/299276 maybe people who use compiz on mate or other DEs want to skip the fade in showdesktop :)08:39
willcookeseb128, I'm trying to rebuild u-c-c, but I don't want to make a whole .deb package, just a binary so I can test a patch.08:48
willcookewhen I run autogen and then make it's looking in /usr/local/share/foo for the ui instead of /usr/share/foo08:49
willcookeI had a look at the rules file, but I can't work out how to tweak that at build time08:49
willcookehm, I tried that and it didnt work08:49
willcookeseb128, do that with ./configure --prefix=/usr right?08:49
willcookeI'll try again08:50
Trevinhoseb128: hey08:52
Trevinhoseb128: can you publish this too https://requests.ci-train.ubuntu.com/#/ticket/1614 ?08:52
* Trevinho fixes the bugs in the mean time08:53
Trevinhohikiko: ok thanks.08:53
seb128Trevinho, you ignored my comment about the upstart job and g-s-d, let's see if the SRU team blocks the SRU due to it08:54
Trevinhoseb128: I didn't ignore...08:54
seb128well I said that it needs to go or to be documented in the changelog08:55
Trevinhoseb128: I really hope not... They're generally good people :-P08:55
seb128it's still there and still undocumented08:55
seb128well, if they do their work they should08:55
seb128their job is to catch undocumented changes08:55
seb128because those have no business being in a SRU08:55
seb128they are more often than not errors08:55
seb128they can't mind read that you wanted to remove that alternative and why08:56
seb128and you didn't asset the potential impact08:56
seb128anyway pressing the button, let's see08:56
willcookeseb128, grr - make clean08:56
seb128willcooke, ;-)08:56
seb128willcooke, working now?08:57
willcookeFailed to look up menu_file for "/usr/etc/xdg/menus/unitycc.menu"08:57
Trevinhoseb128: triggering a rebuild because of that .... Mh, ok08:57
Trevinhoseb128: I'll add itt08:57
seb128Trevinho, I published08:57
seb128so too late for this round08:58
Trevinhoseb128: ah ok.08:58
seb128sorry, you didn't seem open to do the change08:58
seb128let's see what SRU team says08:58
seb128willcooke, --sysconfdir=/etc08:58
seb128willcooke, unsure why you don't simply build the package which use all the right flags/options08:58
seb128easier than building 10 times and poking for what to do manually08:58
willcookebut then I have to do the install / remove dance08:59
willcookeI have to install the .deb right?08:59
seb128why would you?08:59
willcookemaybe I dont08:59
willcookebecause the binaries will still be there right?08:59
seb128to build the deb it does a source build08:59
seb128also you can ctrl-C before the end of the build09:00
seb128just let it do the configure for you09:00
seb128then ctrl-C and do make09:00
seb128at least you get all the flags set up for you09:00
willcookeah, interesting09:00
willcookeoki, I'll read up on that.  It's been a long while.  I remember something about fakeroot and that's abou tit09:00
willcookeabout it09:00
seb128sudo apt-get install debscripts09:02
seb128sudo apt-get build-dep unity-control-center09:02
seb128sudo apt-get install devscripts09:02
seb128was a typo09:02
seb128if you use the vcs you can install bzr-buildpackage and bzr bd09:03
seb128if you get the source just use "debuild"09:03
seb128in the srcdir09:03
willcookewoo! thanks seb12809:03
seb128works now?09:04
willcookeif this doesnt work though, I give up :)09:04
willcookeI tried just commenting out the xml, but that didnt work09:04
willcookeneeds a change in corresponding panel code too09:05
willcookewhich I think is just a couple of lines commented out09:05
willcookeline 1010 in cc-power-panel.c09:06
willcookeand 101109:06
willcookebut at least it built ok :)09:11
seb128willcooke, it doesn't load the panel .so from the local build09:13
seb128you need to copy panel/power/.libs/libpower.so over the system one09:13
seb128dpkg -S libpower.so09:14
willcookehidden directories, of course :)09:14
flexiondotorgwillcooke, I've rounded up all the duplicates for LP: #158586309:16
ubot5Launchpad bug 1585863 in network-manager (Ubuntu) "WiFi malfunction after suspend & resume stress" [High,Confirmed] https://launchpad.net/bugs/158586309:16
flexiondotorgAnd have seen this LP: #158955709:17
ubot5Launchpad bug 1589557 in network-manager (Ubuntu) "[SRU]upstream stable point release 1.2.2" [Medium,Triaged] https://launchpad.net/bugs/158955709:17
flexiondotorgIt that SRU intended as the actual solution?09:17
popeywillcooke: maybe worth keeping an eye on https://bugzilla.gnome.org/show_bug.cgi?id=764841 - GNOME Maps uses a tile provider which is changing T&C, so we may get an update from them which changes to a different tile set09:22
ubot5Gnome bug 764841 in general "Stop Using MapQuest Tile Server" [Normal,New]09:22
popeybecause AIUI (I think) GNOME Maps will break on Monday.09:22
willcookeflexiondotorg, I think that wifi/resume issue was fixed in upstream 1.2.2, so SRUing the new version is the intended fix.  But happyaron should comment further09:26
willcookepopey, thanks.  We get gnome-maps from Debian, so we might need to resync09:26
flexiondotorgwillcooke, Thanks.09:26
willcookeflexiondotorg, did I understand the question correctly?09:27
flexiondotorgYep :-)09:27
flexiondotorgThere is so much mis-information flying around about the Network Manager issues in "the community".09:27
flexiondotorgI'm just trying to get a handle on the main issues and the road to solutions.09:28
flexiondotorgBasically, trying to quite down the peanut gallery.09:28
willcookethank you flexiondotorg09:28
willcookeseb128, sucess - of sorts10:05
willcookenow meeting, then try again10:05
willcookeand make it a bit tidier10:05
seb128willcooke, working but not really as you wanted??10:15
willcookeseb128, working, but I might have found an easier way10:17
seb128k, good10:17
seb128popey, gnome-maps is a direct sync from debian and in universe/not something we maintain, any reason it should be a concern for us?10:18
popeyOnly that AIUI it will break on monday. So expect bug reports in launchpad if they haven't already been reported10:19
seb128well, we are not subscribed to that component10:19
seb128so I guess it can go to the launchpad spam box :p10:20
seb128but thanks for pointing it out10:20
seb128also it's likely that Debian fixes it and than we get a direct sync10:20
popeywouldn't that need an SRU?10:20
seb128if that has users who care on stable series I guess10:20
seb128unsure how used that app is10:21
seb128I never tried it nor saw it mentioned on this channel before today10:21
=== hikiko is now known as hikiko|bbi
=== hikiko|bbi is now known as hikiko|bbl
Trevinhoseb128: I don't see anything changed on that silo, is publication pending or what?11:26
Trevinhoseb128: ah.11:26
Trevinho Publish failed: bamf has merges in bad states.11:26
Trevinholibunity has merges in bad states.11:26
Trevinhounity has merges in bad states.11:26
Trevinhounity-lens-applications has merges in bad states11:26
seb128I pressed the button11:27
seb128didn't check the logs11:27
seb128so it failed? what is bad state?11:27
Trevinhoseb128: yeah, not approved :)11:27
Trevinhoseb128: andyrock is on them, once he ACK'ed I ping you again11:28
seb128you can maybe fix the upstart job, or at least the commit msg ;-)11:29
andyrockseb128 Trevinho done11:31
pittidoes anyone know how we start a Mir session exactly? I. e. the parts between lightdm and running the session leader?11:33
pittiI suppose we don't have any Xsession.d equivalent there11:33
Trevinhopitti: mh, you want the clean way then?11:34
pittiis that just calling the equivalent of /usr/share/xsessions/my_DE.desktop?11:34
pittiwhich then starts the session leader, and as  soon as that stops teh session is gone?11:34
pittiTrevinho: just interested in how it works today, and how it's meant to work (they might not necessarily be the same, yes: :) )11:34
Trevinhopitti: AFAIK using unity-system-compositor you need to pass to it the FDs of lightdm for securty purposes11:34
TrevinhoSo you launch that trhough lightdm, but I'm not that aware of the internals11:35
seb128pitti, you would need robert_ancell for somebody who masters the details11:35
TrevinhoSaviq knows that better for sure ^11:35
seb128or maybe mterry11:35
pittiso apparently if gdm wants to start a wayland session, the only thing it does is to run the corresponding .desktop from /usr/share/wayland-sessions/11:35
Trevinhoyeah, these too11:35
pittiTrevinho: not interested in the details, just how a "session" is defined from the POV of the DM11:36
pittifor X it's currently "run the Exec= from the session .desktop through Xsession.d/" (or very similar)11:36
Trevinhopitti: looking at unity8-desktop-session should help you11:37
Trevinhowe've /usr/share/lightdm/sessions/unity8.desktop11:37
Trevinhowith X-LightDM-Session-Type=mir and Exec=lightdm-unity8-session11:37
pittiah, so lightdm-unity8-session is the "session leader" shell script11:38
Trevinhowhere lightdm-unity8-session is just a script that calls lightdm-session with some qt/mir related enviromnet var sets11:38
Saviqpitti, yeah and lightdm has dedicated code paths for mir to make sure it sets up unity-system-compositor11:38
pittiso lightdm doesn't really need to know about Mir, the only interface is the unity8.desktop, and no Xsession.d/11:38
pittiI'm glad the Xsession.d/ shell script madness is gone :)11:39
pittithanks Saviq and Trevinho!11:39
Trevinhoyeah, I think upstart/systemd usage is the future for that11:39
pittithat's what I'm currently discussing with upstream, yes11:39
pitticleaning up my initial prototype11:40
pittiand I was wondering what to replace the Xsession.d wrapper with11:40
pittiI think we mostly just want to put that into the .desktop Exec= instead11:40
TrevinhoI guess just having a trigger for events, then it's up to scripts..11:40
willcookeLaney, seb128 - any chance of a review and merge of this this week? https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/159481612:07
ubot5Launchpad bug 1594816 in ubuntu-themes (Ubuntu) "GtkSwitch button background overflows the border" [Medium,Confirmed]12:07
seb128willcooke, let's see if Laney replies, I can have a look tomorrow otherwise12:08
seb128it's simple enough that I can probably approve it if needed12:08
willcookethanks seb128.  I guess this is tricky because it won't go in to 16.10 because of Gtk versions12:08
seb128but by css foo is weak, Laney probably has a much better understanding of the theme by now12:08
seb128well, Gtk isn't update12:08
seb128so we can land it now12:08
seb128even if it gets changed later12:08
willcookeseb128, also I did only need to change the power.ui file to get rid of the "when power is critically low" issue:  https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/159926412:09
ubot5Launchpad bug 1599264 in unity-control-center (Ubuntu) ""When power is critically low" setting does nothing" [Undecided,New]12:09
seb128willcooke, do you want that in the .1?12:10
willcookeseb128, hmmmmmmm12:10
seb128willcooke, Trevinho is having a u-c-c update with the compiz lowgfx changeset12:10
seb128so we need to merge them/respin12:10
willcookeYeah, I think so, but it's a UI change - so might need special exceptions?12:10
seb128if you want it included12:11
willcookeseb128, I'd be +1, what do you think?12:11
seb128yeah, good point12:11
seb128well if the settings is not working should be fine for a SRU12:11
seb128but we should talk to the documentation team12:11
willcookeI'll ask for a UI freeze exception anyway12:11
seb128is that setting documented there?12:11
willcookeasked in #ubuntu-doc12:14
seb128k, let me know if you get a reply12:16
willcookeseb128, would you mind testing that real quick?12:16
seb128the .ui change?12:17
willcookeyeah, just apply the patch and see if it's gone12:17
seb128can do12:17
seb128did you see the upstream commit I pointed yesterday evening when we discussed it?12:17
seb128they removed a bit of backend code which isn't needed without the ui as well12:17
seb128we might want to do the same12:18
willcookeah, no, I missed that12:18
willcookelemme see12:18
seb128I think I pointed one?12:18
* seb128 looks at log12:18
seb128oh, I pointed to the bugzilla bug12:19
willcookeso I could remove the same bits and add another patch, is that OK?12:20
willcookeor should we sync from u/s12:21
willcookehrm, this one is waaay different to anything we have: https://bugzilla.gnome.org/attachment.cgi?id=303524&action=diff12:28
willcookehrm, seb128 I'm out of my depth patching cc-power-panel.c12:30
ricotzhey desktopers12:32
ricotzwillcooke, hi, do you mind a pm?12:32
seb128willcooke, I guess it's just a matter of removing the callback for the UI bit ... where is your .ui change?12:34
willcookericotz, sure12:39
willcookeseb128, https://launchpadlibrarian.net/271261080/powerui.patch12:42
willcookeis that what you meant?12:42
willcookeI think I've found the bit in cc-power-panel.c12:42
seb128willcooke, the .ui change looks fine ... k, let me know if you need help with the .c12:46
willcookeseb128, looks like we're a little way behind with out fork, but I think I got it now12:48
seb128yeah, we are way behind12:48
seb128which was sort of why we forked, they redesign the UI and we didn't want the new look12:48
willcookedoesnt matter too much though I think, as long as it works, it's not something we need to keep on the cutting edge with12:48
willcookeI see12:49
=== hikiko|bbl is now known as hikiko
desrtgood morning people13:10
seb128hey desrt, wb!13:10
seb128how are you?13:11
seb128how was Canada day?13:11
desrti'm not sure13:12
desrtprobably pretty good, though :)13:12
seb128that was not monday?13:12
* seb128 is unsure13:12
desrtno.  friday was the holiday13:12
desrtwhich, indeed, is odd13:13
desrtnormally they make it on monday, but i guess because it was natively on friday, which already made it a 3-day weekend, they just left it there13:13
seb128ah ok13:13
desrtthat entire long weekend was the pride parades, anyway13:14
desrtwhich i mostly stayed home for13:14
* desrt hasn't been feeling 100% lately13:14
seb128oh :-/ hope you are going to feel better soon!13:15
desrti should be.  i think the problem has been identified :)13:15
seb128good :-)13:15
=== tyhicks` is now known as tyhicks
willcookeseb128, I'm down a rabbit hole now with u-c-c :( - I think I do need to build and install a .deb because I'm trying to copy libs around to test and getting it very wrong14:34
willcookeonce I do a debuild - what's the next step to get a .deb I can install?14:35
seb128what lib? how wrong?14:35
seb128debuild procudes a deb14:35
didrocks(if the build succeed :p)14:40
willcookeseb128, @ libs - I think I need to copy new ones in to the right place after I made changes to the power panel C code14:40
willcookeseb128, and wrong - like I might have deleted the proper ones and replaced them with garbage14:41
seb128willcooke, well, the panel is libpower.so14:41
willcookeI was getting warnings from libunity-control-center.so.1.0.014:42
willcookeso I tried to copy that over as well14:42
seb128and now?14:42
seb128you get an error?14:42
willcookewell, I'm getting some warnings which I think are related to the changes14:42
willcookeit's not building a deb because:14:42
willcookeoh, it's trying to sign it as you14:43
seb128that's not an error14:45
seb128it should still produce the deb14:45
seb128in the maindir, like outside the srcdir14:45
seb128or in build-area/14:45
willcookewarnings gone14:59
flocculantwillcooke: or are they ...15:06
flocculantjust thought I would throw that in there :p15:06
willcookegee, thanks pal15:06
Sweet5hark1ricotz: thanks for your enthusiasm on updating https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-yakkety-5.2&id=97262150e06b39605a4a63b6921a4010371da6ad15:53
Sweet5hark1ricotz: a few things though:15:53
Sweet5hark1ricotz: a/ please dont push changes I wrote onto the branch. All changes I push to lp are already locally commited in git, so when you recreate those changes with a newly created commit, that just creates conflicts. Also, if I have pushed something to lp, but not to the git repo, there is a good chance that there either is a problem with the change or it wasnt tested yet. As such please assume it to be _intentionally_ not pushed yet --15:53
Sweet5hark1ricotz: b/ Also, if you push changes written by others, please use --author to properly mark them for git blame etc. If you do changes inspired by someone, but which are not verbatim their work, it might be better to just name/thank the author in the commit message.15:53
Sweet5hark1ricotz: I also noted you asked upstream about rc2. Thats good in general as upstream should stick to its schedule unless there are good reasons. However, please refrain from creating tarballs from upstream tags for Ubuntu unless I am very late with that (read: like half a week). If you create the tarballs, that is not helping, because it actually creates _more_ work for me to diff/check/verify those against some I independantly created15:53
Sweet5hark1ricotz: if you want to help with the upstream tarballs, as cloph said upstream: the best way is to get into reviewing the outstanding patches that still block the tag. Alternatively, if you want to help with the Ubuntu tarballs, recreating them and verifying that there is no diff to when I upload isnt corrupted (and thus has no diff beyond e.g. fetch.log) would help too.15:57
Sweet5hark1ricotz: but -- as said in the opening, your work is much welcome, but keep in mind that packaging LibreOffice is and should be a rather slow business: Its like navigating an oil tanker. --- If you prefer something moving faster, upstream _development_ (not releng) might be something for you, and I most happily would give you an intro on how to get started ;)16:01
willcookeseb128, pour vous?  https://code.launchpad.net/~willcooke/ubuntu-themes/gtkswitchoverflow/+merge/29802816:04
ricotzSweet5hark1, hi, thanks for the flaming and not answering to my previous messages -- I noted your complaints, but slow as in weeks-later is not helping, and you not pushing your changes is not unusual, just rebase the branch as you wish16:05
seb128sorry can't read you, hate that bug16:06
ricotzSweet5hark1, I simply asked for an eta for the new tag nothing more16:06
seb128I can see notifications with text though :p16:07
seb128need to reboot but I was testing something in a snap env and didn't want to close it16:07
seb128willcooke, +116:11
Sweet5hark1ricotz: yes, In general I need to change my unhelpful custom of pushing only rarely now that I am not alone there. But that is not what is happened here: https://launchpad.net/~bjoern-michaelsen/+archive/ubuntu/libreoffice-staging/+sourcepub/6496156/+listing-archive-extra ftbfs, so I didnt commit/push before investigating that. So umm, taking changes from someone elses private ppa that apparently broke and pushing it to the branch with16:15
ricotzSweet5hark1, the way I did it you can easily see what I changed and you can simply rebase to your local branch by skipping the squashed commit16:17
seb128going for some exercice, bbiab16:20
jbichapopey: Ubuntu GNOME 15.10 and 16.04 ships gnome-maps16:25
popeyjbicha: i thought they might16:26
=== dpm is now known as dpm-afk
ricotzSweet5hark1, why didn't you rebase it?17:38
ricotzSweet5hark1, also a transitional package for libreoffice-gtk might be wise to ease updating17:40
Sweet5hark1ricotz: rebase your changes on top of mine? because that would then create a different branch and thus require a forced push, "changing history"/diverted history. One should _never_ force push to a public branch.17:43
ricotzSweet5hark1, as you said there are like 2 people working on it, so just do it17:45
ricotzSweet5hark1, rebasing public branch is done all the time or over the places17:45
Sweet5hark1ricotz: rebasing published branches might be done. however, its never done in sane places.17:46
ricotzSweet5hark1, dont call this branch a sane place ;P17:47
Sweet5hark1ricotz: for the next time, a workable solution, if you urgently want to have something to be included in the packaging branches is that you push to a different named branch (e.g. "feature/$something"). It can then be easily cherry-picked/merged/whatever in the ubuntu-yakkety-5.2 branch. (thats a bit like a "github pull request" -- just without the nice web-UI).17:48
ricotzSweet5hark1, I am aware of what git is capable17:49
ricotzSweet5hark1, and again there were weeks between your upload/changes and me pushing this17:51
Sweet5hark1ricotz: yes, I wanted to squeeze in a rc1 release on friday. but the CVE nonsense pointlessly ate too much time.17:57
ricotzSweet5hark1, https://paste.debian.net/plain/77780118:08
Sweet5hark1ricotz: thx, willdo tomorrow.18:13
willcookenight all18:33
tjaaltonanyone know if unity7 has some autoscaling applied with intel driver? because there's no scaling with the modesetting driver21:20
Trevinhotjaalton: there's no autoscaling by default22:58
Trevinhotjaalton: there's a branch that does that which we'll likely merge soon, though22:58
tjaaltonTrevinho: ok, somehow it does scale with intel.. even on xenial23:10
Trevinhotjaalton: gdk might apply that automatically, but..... it shouldn't23:11

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!