[07:01] <seb128> good morning desktopers
[07:01] <jibel> morning seb128
[07:02] <seb128> lut jibel, ça va ? une journée et le w.e !
[07:04] <jibel> seb128, ça va bien, le w.e approche. et toi?
[07:04] <jibel> seb128, des choses de prévu?
[07:04] <seb128> ça va bien, j'ai dormi jusqu'à 8h et c'est vendredi !
[07:05] <seb128> tennis ce soir, on va à un mariage demain, rien de spécial dimanche
[07:05] <seb128> et vous ?
[07:05] <jibel> demain kayak et dimanche j'ai une salle de bain à finir de carreler, repos en qq sorte
[07:06] <seb128> :)
=== pstolowski|afk is now known as pstolowski
[07:11] <duflu> Morning seb128, jibel
[07:11] <seb128> hey duflu, happy friday! how are you?
[07:12] <duflu> seb128, I'm OK. How bout you?
[07:15] <seb128> I'm good
[07:15] <Mirv> aware of any bug or reports about keyboard randomly stopping to work in a desktop session on 18.04? it has happened a couple of times, I can switch to terminal and back and I can use touchpad to eg close windows and log out, but I haven't figured out how to restore keyboard into working state other than logging out
[07:15] <Mirv> IOW if you know of such and need me to do something when it happens the next time, let me know
[07:15] <sarnold> Mirv: please forgive me for asking "did you check if it's plugged in"-level question...
[07:15] <Mirv> otherwise I'll just continue to think about it on my own when it happens
[07:16] <sarnold> Mirv: did you bychance hit ^Q and neglect to hit ^S?
[07:16] <seb128> duflu and tjaalton discussed that the other day iirc
[07:16] <Mirv> sarnold: lol, it's useful to ask that level of questions, but it's the internal keyboard
[07:16] <seb128> Mirv, do you use any shell extension?
[07:16] <seb128> if so I would start by disabling those
[07:16] <Mirv> sarnold: none of keys work, but I still have that workrave extension, I hope it's also not causing this :D
[07:16] <Mirv> yeah, I guess I should try to keep breaks without workrave for a while and see if it still happens
[07:16] <seb128> disable it and see?
[07:17] <Mirv> yep, good idea
[07:17] <duflu> Mirv, I think some people are reporting that for the Super key..?
[07:17] <sarnold> Mirv: okay. I just know that for some reason people's keypresses keep falling through to the 'terminal' behind X and then *nothing* works correctly.
[07:17] <Mirv> duflu: for me I can't type anywhere, alt-tab, super, ie nothing works
[07:17] <Mirv> sarnold: ok, I'll keep that mind, I know of such behavior from the past but I think my keys went nowhere
[07:18] <Mirv> thanks for the ideas
[07:18] <duflu> Mirv: No, Super was the cause. Or entering the Activities Overview was. Try and remember what you did last next time it happens
[07:18] <Mirv> the good thing, other than to my physical health, would be if it's just workrave
[07:18] <Mirv> duflu: ah... ok, right
[07:25] <Mirv> ok people it's just happening again, this is from text console...
[07:25] <Mirv> and it's not just keyboard, I can't also select text in eg terminal windows with mouse
[07:26] <Mirv> but Dock and system menus work etc
[07:26] <Mirv> and what I was doing I think was just idling (using another laptop for a few minutes), then I started using this computer again
[07:26] <Mirv> ideas welcome
[07:27] <Mirv> eg when terminal window is selected, the focus is not there ie cursor is not solid rectangle
[07:28] <Mirv> and this happened after disabling the workrave extension
[07:28] <Mirv> sarnold: duflu: seb128: sorry for pinging but if you want me to try something ^
[07:29] <duflu> Mirv, starting to sound a little like bug 1181666, which is in active discussion
[07:29] <ubot5> bug 1181666 in GNOME Shell "gnome-shell randomly blocks mouse clicks from working in app windows" [Critical,Confirmed] https://launchpad.net/bugs/1181666
[07:33] <sarnold> Mirv: wow..
[07:33] <Mirv> duflu: ctrl-alt-t is mentioned there as working, but it's not for me
[07:34] <seb128> Mirv, I woul;d recommend filing a bug upstream, they know their project better and be more able to help debugging than us
[07:34] <sarnold> that bug is from 2013? oof
[07:34] <duflu> Mirv, I think that's a different issue although haven't seen it in a while: bug 1705348
[07:34] <ubot5> bug 1705348 in gnome-terminal (Ubuntu) "Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later" [Undecided,Incomplete] https://launchpad.net/bugs/1705348
[07:34] <Mirv> no keyboard or mouse presses are recognized by windows. but interesting, it's not that keyboard does not work - I can open Activities, focus the search field and type there normally
[07:35] <Mirv> duflu: no, this is more like "keyboard and mouse do not work anywhere but Shell itself"
[07:35] <Mirv> seb128: yeah, I should do that
[07:35] <duflu> Mirv, sounds like bug 1181666 still
[07:35] <ubot5> bug 1181666 in GNOME Shell "gnome-shell randomly blocks mouse clicks from working in app windows" [Critical,Confirmed] https://launchpad.net/bugs/1181666
[07:36] <Mirv> interesting, Super does not bring up Activities but if I open Activities with mouse, I can close it with Super
[07:36] <Mirv> duflu: ok
[07:36] <Mirv> anyway, I start to have a good collection of symptoms for now
[07:38] <Mirv> and I have finally a workaround not requiring log out, thank goodness. 1. Open Activities with touchpad, 2. Press Alt-F2 (only works if Activities is open), 3. gnome-shell -r
[08:31] <GunnarHj> Good morning seb128!
[08:31] <GunnarHj> seb128: Time to look at a (very simple) g-c-c MP?
[08:31] <GunnarHj> https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/353670
[08:46] <GunnarHj> Good morning seb128!
[08:46] <GunnarHj> seb128: Time to look at a (very simple) g-c-c MP?
[08:46] <GunnarHj> https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/353670
[08:46] <seb128> hey GunnarHj, happy friday! how are you?
[08:46] <GunnarHj> seb128: I'm fine, thanks. Hope you are as well.
[08:47] <seb128> GunnarHj, yes, I saw that one when I moderated the ubuntu-desktop@ email just a bit earlier, it's on my list now for this morning
[08:47] <seb128> I'm good thanks
[08:47] <GunnarHj> seb128: Ok, great. Maybe upload to, so the region module starts working again?
[08:48] <seb128> yes, let me just finish the n-m work I'm doing
[08:48] <GunnarHj> seb128: Sure, no emergency. :)
[09:19] <duflu> seb128, do you have any idea why your comments about the radeon card appears in email and notifcations, but not on the card itself?
[09:19]  * duflu wonders what other comments he's missed over the years
[09:20] <seb128> duflu, my web browser acted weird and wasn't displaying the content of the comment so I deleted and tried to add again
[09:20] <duflu> OK. You found a Trello bug
[09:20] <seb128> but I think it's just firefox that was in a weird state, I noticed other rendering issue then
[09:20] <seb128> it seems fine again after restarting
[09:20] <seb128> got figure :/
[09:20] <seb128> go*
[09:21] <seb128> so yeah, I did actually delete to add them again, hopefully there is no bug that made anyone miss content :)
=== czajkows1i is now known as czajowski
[09:22] <duflu> I don't read notifcations, but follow the link straight to the card. Hopefully that bug won't happen often
[09:22] <seb128> yeah
[09:23] <seb128> duflu, commented again, seems all fine on my side now
[09:23] <seb128> sorry for the noise/weirdness
[09:23] <duflu> Yes I got it now
[09:24] <duflu> I also can't spell notification today
[09:24] <duflu> That's the 4th time at least
[09:40] <andyrock> seb128: https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-online-accounts/+git/gnome-online-accounts/+merge/353636
[09:41] <andyrock> and hey! :)
[09:41] <seb128> hey andyrock, yes you are next on my list :)
[09:41] <seb128> I just replied to the snapd comment on the trello
[09:41] <andyrock> thx! <3
[09:41] <seb128> might be worth checking with mvo but I don't think 3.25.1 is out yet
[09:41] <seb128> I'm pretty sure cosmic will get it once it is though
[09:45] <seb128> andyrock, the diff looks weird
[09:45] <seb128> oh ignore that
[09:45] <seb128> "Binary files a/debian/patches/0001-ubuntu-sso-provider.patch and b/debian/patches/0001-ubuntu-sso-provider.patch differ"
[09:45] <seb128> that's why there is no actual diff
[09:45] <duflu> UTF-8 maybe?
[09:46] <seb128> binary content in the patch
[09:46] <seb128> that patch has png icons included
[09:48] <andyrock> seb128: yeah :(  not sure it there is a better way to deal with this
[09:48] <seb128> split the patch in 2 I would say
[09:48] <seb128> one with the icons that can't be diffed
[09:48] <seb128> and one with the code
[09:48] <seb128> so at least the code changes can be easily reviewed
[09:49] <andyrock> makes sense to me
[09:49] <andyrock> I'll do next time I need to edit something
[09:49] <seb128> thx
[09:53] <seb128> andyrock, uploaded
[09:53] <seb128> (&merged)
[09:59] <seb128> GunnarHj_, yours as well
[10:03] <seb128> GunnarHj_, which is failing to build because "locales" can't be installed :/
[10:04] <seb128> andyrock, btw did you also do the totem merge/rebase for Ubuntu or only the Debian update?
[10:11] <andyrock> seb128: only the debian one
[10:11] <andyrock> do you want me to look at it?
[10:11] <GunnarHj> seb128: Saw that. Is it because the latest glibc is stuck in -proposed?
[10:11] <seb128> andyrock, k
[10:11] <seb128> GunnarHj, could be, but it builds against proposed so it should get anything available there
[10:17] <andyrock> seb128: do you use dpkg-mergechangelogs to merge changelogs?
[10:18] <seb128> no, maybe I should? ;)
[10:18] <seb128> I don't merge changelogs in fact
[10:18] <seb128> I usually just drop the old entries and put the merge summary one as the only diff on top
[10:18] <andyrock> ah ok
[10:19] <andyrock> using this I get http://manpages.ubuntu.com/manpages/trusty/man1/dpkg-mergechangelogs.1.html
[10:20] <seb128> andyrock, you mean? you get the mangpage where?
[10:20] <andyrock> https://paste.ubuntu.com/p/gHp8xzsdkf/
[10:20] <andyrock> i mean using what's written in the manpage :)
[10:20] <andyrock> wrong order of links
[10:20] <andyrock> wondering if it's ok too
[10:20] <andyrock> or just one entry on top is fine
[10:21] <seb128> andyrock, I think that diff is right
[10:21] <GunnarHj> seb128: locales was not built...
[10:22] <seb128> it looks like that by design they sort it by date of changes
[10:22] <seb128> so you get a chronological order
[10:22] <seb128> not a versioned order
[10:23] <seb128> or maybe not?
[10:23] <andyrock> seb128: line 84 of the diff
[10:23] <seb128> andyrock, anyway, I would just trust the tools/accept that what is does it right, it doesn't matter much anyway, as long as the first entry in the upload one
[10:23] <andyrock> kk
[10:26] <seb128> GunnarHj, in fact it's due to https://launchpad.net/ubuntu/+source/glibc/2.28-0ubuntu1
[10:27] <seb128> tjaalton, hey, another minor xorg stack update availabe is xbitmaps if you feel like doing it :) and xserver-xorg-input-evdev and  xserver-xorg-input-synaptics needs merging to cosmic (I can do those if you want)
[10:28] <GunnarHj> seb128: Right. Which does not include the locales binary. Suppose that infinity will attend to it soon.
[10:28] <seb128> GunnarHj, did you point that to him yet?
[10:29] <GunnarHj> seb128: No. I pinged him now. :)
[10:29] <tjaalton> seb128: I'm not sure the diff makes much sense anymore, since evdev isn't used by default
[10:29] <tjaalton> evdev diff that is
[10:29] <seb128> tjaalton, syncing wfm
[10:29] <seb128> I just want those red lines off my summary :p
[10:30] <tjaalton> evdev synced
[10:30] <seb128> GunnarHj, well, it's not that update doesn't include locales, it's just that this binary is arch all so built on amd64 and that just finished building
[10:30] <seb128> GunnarHj, https://launchpad.net/ubuntu/+source/glibc/2.28-0ubuntu1/+build/15300579 has it
[10:31] <seb128> GunnarHj, so already solved, just need to wait for a publisher cycle
[10:31] <seb128> well, the ftbfs on some of the archs might be problematic still though
[10:31] <tjaalton> seb128: you can merge -synaptics if you need it soon
[10:32] <tjaalton> i can't get to my work desktop machine atm, seems to be having network issues
[10:32] <seb128> tjaalton, I don't especially "need" it, just tried to get that summary clean but at the end it's probably not really useful and red lines are going to stack again now that we hit ff
[10:32] <seb128> I just tried to get in shape at the ff point
[10:32] <seb128> tjaalton, k, it's a pretty simple merge, I'm going to do it :)
[10:33] <tjaalton> btw I have mesa 18.2.0~rc4 on a staging ppa
[10:33] <seb128> ha, nice
[10:33] <seb128> shame you missed ff now
[10:33] <seb128> (unless they shift it as being discussed on other channels)
[10:33] <tjaalton> business as usual with mesa
[10:34] <seb128> tjaalton, also do you know what's the deal with wayland? 1.15.0 vs 1.15.94?
[10:34] <seb128> debian/we avoid to update for a reason or it just didn't happen?
[10:35] <tjaalton> guess it's just because of summer
[10:37] <seb128> do we want the update in cosmic?
[10:37] <tjaalton> I don't know
[10:37] <tjaalton> and it's "just" a release candidate
[10:38] <tjaalton> not many actual changes in it
[10:38] <seb128> right, I just had a look
[10:39] <seb128> some overflow fixes that seems that could be useful but otherwise almost nothing
[10:39] <seb128> tjaalton, thx for the replies to my not-so-interesting questions :)
[10:39] <tjaalton> yw
[10:52] <tjaalton> another thing I'd like to get in cosmic is the split vulkan packaging.. vulkan-headers is in but the rest is not uploaded to debian yet
[10:53] <GunnarHj> seb128: Ah, thanks for explaining.
=== pstolowski is now known as pstolowski|lunch
[11:32] <andyrock> seb128: https://salsa.debian.org/gnome-team/totem/merge_requests/4/diffs
[11:32] <gitbot> GNOME issue (Merge request) 4 in totem "debian/control*: Drop dependency on libxtst-dev" [Opened]
[11:32] <andyrock> I just noticed this
[11:32] <andyrock> not a priority
[12:05] <seb128> andyrock, thx
=== pstolowski|lunch is now known as pstolowski
[12:43] <andyrock> Trevinho: seb128: do we need to rename python-compizconfig to python3-compizconfig here? https://code.launchpad.net/~muktupavels/compiz/ccsm-python3/+merge/351940
[12:44] <Trevinho> I guess so... However since we only have one...
[12:45] <andyrock> Trevinho: it's used here
[12:45] <andyrock> https://www.irccloud.com/pastebin/FuNt7Q5C/
[12:45] <andyrock> unity-autopilot it's using a bunch of python2 packages
[12:47] <seb128> andyrock, we should rename, also if there are rdepends still needing the python2 bindings we should still have a python2 version
[12:47] <seb128> or port those
[12:47] <seb128> in any case that sounds like that needs a ffe to land that late in any case
[12:47] <andyrock> muktupavels ^^^
[12:48] <andyrock> I suggest renaming it and port unity-autopilot
[12:48] <muktupavels> where are sources for unity-autopilot?
[12:50] <andyrock> unity
[12:50] <andyrock> just try to modify the config file using python3- instead of python-
[12:52] <andyrock> muktupavels: ah you did rename it
[12:53] <andyrock> so you need to propose a change for unity too
[12:56] <muktupavels> unity-autopilot is all python2, right?
[13:04] <andyrock> I guess
[13:05] <andyrock> so maybe just keeping the python-compizconfig around should be fine too
[13:07] <andyrock> I mean both python-compizconfig and python3-compizconfig
[13:07] <andyrock> in case the changes you made are not retro-compatible with python2 you need further changes
[13:11] <muktupavels> can you add that as comment in merge proposal?
[13:24] <andyrock> kk
[13:24] <muktupavels> pylint --py3k * in autopilot dir says - Your code has been rated at 9.85/10
[13:24] <muktupavels> has anyone used that, does that mean that it is more or less compatible with python3?
[13:29] <andyrock> I guess, but I would suggest you to go with option 1) in my comment
[13:29] <andyrock> just build both packages
[13:31] <andyrock> seb128: totem almost ready
[13:31] <andyrock> I tested in a schroot, I'll try it on a VM just to be sure it works properly
[13:32] <muktupavels> well, I dont know how to do that...
[13:35] <andyrock> muktupavels: take a look to another packages that does the same
[13:35] <andyrock> most of them actually have support for both
[13:37] <muktupavels> andyrock, did you want to push something? https://code.launchpad.net/~azzar1/unity/python3-autopilot
[13:37] <andyrock> muktupavels: just wanted to try to build with bileto but I saw later that there is some python2 code there
[13:38] <muktupavels> where did you see that?
[13:43] <seb128> andyrock, k, seeing the changes it's not very likely to be problematic so minimal testing is probably ok
[13:43] <seb128> epecially that it's not a key component to the session and not a stable serie
[13:45] <seb128> brb, changing location
[14:03] <andyrock> muktupavels: found a print without ( and I realized it :P
[14:09] <seb128> tjaalton,  libxinerama also has a new minor revision available :)
[14:09] <seb128> tjaalton, & libxkbcommon
[14:09] <seb128> & libxss
[14:09] <seb128> that's it :p
[14:25] <GunnarHj> seb128: There seems to be a need to start the g-c-c build again for some archs.
[14:27] <seb128> GunnarHj, done
[14:37] <GunnarHj> seb128: Great, keeping my fingers crossed. :)
[14:37] <GunnarHj> seb128: Btw, do you know if the team generally has dropped the ninja() workaround in the affected Meson packages?
[14:38] <seb128> I don't think we did actively
[14:40] <GunnarHj> seb128: Would be good if that could be accomplished in 18.10. In some cases it doesn't matter at all, but in some cases it affects .desktop files etc.
[14:40] <seb128> k, I'm going to keep on that when do the updates to stable GNOME
[14:40] <GunnarHj> seb128: Ok, thanks!
[14:40] <seb128> thank you for the reminder!
[14:41] <GunnarHj> np
[14:41] <seb128> GunnarHj, https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.29.90-1~ubuntu2 nudging worked
[14:41] <GunnarHj> Yay!
[15:52] <seb128> have a nice w.e desktopers
[15:53] <Trevinho> bye seb128 enjoy your we
[15:53] <seb128> thanks Trevinho, you too
[15:53] <Trevinho> still some hours to get there :D
[16:08] <muktupavels> andyrock, Trevinho: can you look / comment why unity fails? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3336/+packages
[16:24] <muktupavels> andyrock, Trevinho: arm64 fails to build, all other fails running tests...
[16:59] <andyrock> mmm muktupavels are they failing on a local build too?
[17:01] <muktupavels> andyrock, did not try... I dont have install compiz and/or unity.
[17:02] <andyrock> muktupavels: https://code.launchpad.net/~muktupavels/unity/fix-build/+merge/353719 what's this for?
[17:03] <muktupavels> andyrock: because cmake fails... because of this - https://code.launchpad.net/~muktupavels/compiz/cmp0002/+merge/350723
[17:04] <andyrock> kk
[17:04] <muktupavels> failing build and/or tests does not seems to be related to my changes...
[17:05] <andyrock> I guess so but still we need to make those tests pass :)
[17:06] <muktupavels> arm64 does not build.
[17:08] <muktupavels> I will try to build unity in vm.
[17:08] <muktupavels> how to run tests / unity-autotest?
[17:17] <andyrock> muktupavels: you need to install python3-autopilot
[17:18] <andyrock> muktupavels: and then autopilot run unity
[17:18] <andyrock> 'autopilot run unity'
[17:19] <andyrock> of course you also need unity-autopilot installed
[17:19] <muktupavels> I am building unity with bzr builddeb now.
[18:22] <muktupavels> andyrock: https://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/unity-shared/BamfApplicationManager.cpp#L258
[18:23] <muktupavels> andyrock: any change it should be manager without underscore?
[18:23] <muktupavels> andyrock: that is about arm64 build failure.
[19:06] <om26er> Is Ubuntu defaulting to Wayland in 18.10 ?
[19:09] <tsimonq2> I doubt it, personally.
[19:19] <jbicha> om26er: not without a FFe at this point :)
[19:27] <muktupavels> andyrock, finally was able to build deb packages, but after installing autopilot3 says that it did not find any tests...