[02:30] <jbicha> duflu: do you ever have gnome-shell hang when resuming from suspend?
[02:31] <duflu> jbicha, after years of bugs I still fear suspend too much to ever suspend :/
[02:31] <duflu> Also don't need to. I can either stay powered on, or just power off
[02:31] <jbicha> well anyway, I believe Jonas's "headless" work in mutter helps fix some of those hangs/crashes
[02:32] <jbicha> there are 2 more commits in the gnome-3-26 branch for that, that we didn't cherry-pick yet
[02:35] <chobitslinux> Well, hope ubuntu18 can use a brilliant gui, but the gnome3 overview is not fluent than the gnome2, I used to use ubuntu11.04 with the typical unity,at some way, mate-like desktop is good.
[02:36] <duflu> chobitslinux, there is actually a Classic mode in Gnome3. Just: apt install gnome-shell-extensions
[02:37] <duflu> or: sudo apt install gnome-shell-extensions
[02:37] <duflu> and then select the classic session on the login screen
[02:46] <chobitslinux> duflu, Oh,thanks,I just has nostalgic idea.
[02:48] <jamesh> robert_ancell: for bug 1722195, the only way I can understand him getting a polkit prompt on the command line but not in gnome-software is if he's running against an old libsnapd-glib.  I'm just going to fire up a clean VM to see if I can reproduce
[02:58] <chobitslinux_> wa, net stability is not well these days.
[03:05] <jbicha> robert_ancell: I tried installing the moon-buggy snap and at 99% it's maxing out my cpu for several minutes :(
[03:05] <robert_ancell> jbicha: from the ppa version
[03:05] <robert_ancell> ?
[03:06] <jbicha> no, from gnome-software in artful
[03:06]  * jbicha wonders what happens if I press Cancel
[03:06] <robert_ancell> jbicha: can you confim the versioN?
[03:06] <chobitslinux> is the problem of CPU poor?
[03:06] <jbicha> gnome-software 3.26.1-0ubuntu1, any other versions you want?
[03:08] <robert_ancell> I'd hoped the CPU issues were resolved in that release... :(
[03:09] <robert_ancell> jbicha: does it reliably reproduce?
[03:16] <jbicha> well when I killed it, it had actually finished installing and it didn't happen when I installed oh my giraffe
[05:48] <oSoMoN> good morning desktoppers
[07:20] <didrocks> good morning
[07:20] <duflu> Morning didrocks, oSoMoN
[07:20] <didrocks> hey duflu
[07:37] <seb128> good morning desktopers
[07:37] <seb128> hey duflu oSoMoN, re didrocks
[07:37] <duflu> Hi seb128
[07:38] <didrocks> re seb128
[07:47] <_amano> Good morning desktoppers, can you have a look at https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577 please?
[07:48] <seb128> brb, moving location
[07:49] <_amano> Looks like a showstopper bug. A fresh install freezing during/after displaying the Ubuntu splash screen.
[07:49] <didrocks> jibel: do we have other similar reports ? ^
[07:50]  * didrocks looks at the comments meanwhile
[07:52] <didrocks> _amano: you told it worked until the week of the 7th October, are you able to downgrade some packages to help bisecting?
[07:55] <willcooke> morning all
[07:56] <duflu> Morning willcooke. Back in the land of the living yet?
[07:56] <willcooke> duflu, I'm doing my best impression of someone who is awake
[07:56] <willcooke> it's not terribly convincing
[07:56] <didrocks> good morning willcooke, had an uneventful trip back?
[07:57] <duflu> On IRC it is convincing. At least for a chatbot
[07:57] <willcooke> :) Thanks $PERSON. How about that $LOCAL_SPORTS_TEAM
[07:57] <didrocks> (only with set -e)
[07:58] <duflu> Go ${TEAM_NAME}s
[08:01] <Laney> moin
[08:02] <didrocks> hey Laney, you middly awake too?
[08:02] <seb128> hey Laney, how are you? had a good week in n.y, trip back and beer festival/w.e?
[08:03] <duflu> Morning(ish?) Laney
[08:03] <oSoMoN> hey willcooke, Laney, welcome back to the old world
[08:04] <seb128> is there any way to tell mailman to shup up about "moderator request waiting" daily emails?
[08:04] <seb128> hey willcooke
[08:04] <willcooke> seb128, for the desktop list?
[08:04] <seb128> willcooke, yes
[08:05] <seb128> it's annoying that they changed the config when they upgraded/did maintainance
[08:05] <didrocks> ok, 2 people on the french forum have that issue + _amano at least
[08:05] <seb128> I found options to disable the emails it was sending about every new request coming
[08:05] <Laney> hi didrocks seb128 duflu oSoMoN
[08:05]  * didrocks tries to get some help from them for bisecting
[08:05] <seb128> but not about the daily nag
[08:05]  * Laney is mostly alive
[08:06] <seb128> didrocks, having issue with gdm/wayland on some drivers?
[08:06] <didrocks> yep
[08:06] <didrocks> since the 07/10
[08:07] <duflu> Aha! didrocks, using an AMD GPU?
[08:07] <seb128> what changed then?
[08:07] <didrocks> GNOME 3.26.1, so, a lot :p
[08:07] <seb128> :-/
[08:07] <didrocks> (they aren't sure if it's the 05 or 07)
[08:07] <duflu> (me saw some complaints about AMD today where people said it happened around 7/10)
[08:07] <didrocks> trying to get them on IRC to bisect
[08:07] <didrocks> yeah
[08:07] <didrocks> saw your typo fix on "artful*l*" duflu :p
[08:08] <seb128> no gdm upload at least around those dates
[08:08] <didrocks> yeah, could be mutter/G-S…
[08:10] <duflu> didrocks, Mesa is often the cause of sudden graphical failures. And it got an upgrade on 5 Oct
[08:11] <didrocks> good hint
[08:11] <didrocks> yeah, it's a valid candidate
[08:11] <seb128> tjaalton, ^
[08:13] <duflu> To be fair, that should read "for cases of sudden graphical failures, a mesa upgrade is often the cause". More generally mesa does not "often" cause failures
[08:17] <GunnarHj> Hi Laney, There might be some noise about bug #1722427 in your mailbox. Even if I succeeded in getting a fix into the archive yesterday, I'd appreciate your view on it.
[08:17] <GunnarHj> https://launchpad.net/ubuntu/+source/im-config/0.32-1ubuntu3
[08:17] <GunnarHj> Is it acceptable for 17.10?
[08:30] <Laney> GunnarHj: I guess the concern is hiding real errors there, right?
[08:30] <Laney> like, why is that junk in stderr?
[08:31] <Laney> but as for acceptable for release - well, someone on the release team accepted it so there's your answer :P
[08:33] <GunnarHj> Laney: Precisely. Something I'm not sure about is if possible errors when using Fcitx later also will be discarded. If so, it's not ideal, and if there is a better solution I can SRU it.
[08:34] <Laney> probably silence dbus-update-activation-environment and the other stuff
[08:34] <Laney> that would involve hunting down where they are called from though
[08:35] <GunnarHj> Laney: That would be over my head. My impression is that /etc/profile.d is a temporary thing for 17.10, and that the graphical systemd service will be working again in 18.04.
[08:35] <seb128> didrocks, duflu, just for info there seems to be a least a kernel regression when using nouveau with displayp, bug #1723619, it's different from the issue discussed earlier but I'm mentioning it in case somebody on nouveau joins the bug with a "me too" so we can redirect him
[08:37] <didrocks> seb128: ahah, nicely spotted! Yeah, so that could be confusing
[08:37] <andyrock> hey all
[08:37] <duflu> seb128, Thanks. I used to have a GTX970 but not any more. Sounds like it's not a huge regression though, because AFAIK it hasn't worked in a while: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158
[08:37] <didrocks> hey andyrock
[08:38] <andyrock> hey didrocks
[08:38] <andyrock> how are you?
[08:39] <didrocks> good thanks! but tired (didn't get a restful week-end due to son being sick), and you?
[08:40] <andyrock> :/
[08:40] <andyrock> I had a productive w-e
[08:40] <andyrock> I finally found a new room
[08:40] <andyrock> to move in
[08:41] <didrocks> oh great! when are you planning to move?
[08:41] <andyrock> so I don't have to spend next w-e looking for a flat
[08:41] <andyrock> next monday
[08:41] <andyrock> \o/
[08:42] <Laney> didrocks: seb128: sorry, got jumped on for like 5 things so didn't reply to you properly
[08:42] <Laney> beer fest was great as usual
[08:42] <seb128> Laney, no worry :-)
[08:43] <Laney> unusually warm, like 20°
[08:43] <seb128> hey andyrock
[08:43] <Laney> so we hung around outside for a while
[08:43] <Laney> and I had the row to myself on the plane back so could sleep across the chairs
[08:43] <Laney> was just like business class
[08:43] <willcooke> Nice!
[08:44] <Laney> hey willcooke
[08:44] <Laney> get back ok?
[08:44] <didrocks> free upgrade ©
[08:44] <didrocks> andyrock: waow, that's quick!
[08:44] <willcooke> I got an empty seat next to me, but the person in front of me had their chair back right away.  So I stuck my knees in their back to make myself feel better.
[08:44] <didrocks> andyrock: enjoy moving in :)
[08:44] <andyrock> btw I found a way to reproduce
[08:44] <andyrock> https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a
[08:52] <seb128> andyrock, how do you trigger it?
[08:52] <andyrock> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720400/comments/2
[08:52] <andyrock> seb128: ^^^
[08:52] <andyrock> I'm working on it
[08:52] <seb128> andyrock, thanks
[08:53] <andyrock> trying to understand if I can fix it otherwise I'll ping the gnome-control-center guys
[08:53] <seb128> andyrock, when you write "system should crash" do you mean g-c-c or the session or the kernel?
[08:54] <andyrock> just g-c-c
[08:54] <andyrock> I'll update that
[08:55] <andyrock> thanks
[08:57] <seb128> thx
[09:00] <seb128> brb
[09:12] <willcooke> jibel, would you be able to test https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723312 today?
[09:13] <didrocks> ok, I got on the impacted french guy not being able to start gdm on AMD to test during his lunch time at home some reverts, gave him instructions on the forum
[09:15] <jibel> willcooke, I'm on it
[09:15] <jibel> willcooke, everything looks good so far
[09:17] <willcooke> merci jibel
[09:24] <Laney> ooh
[09:24] <Laney> gcal now has an option for UTC (no DST)
[09:28] <duflu> Ugh. Europe morning.
[09:28]  * duflu gives up retrying Launchpad timeouts
[09:28] <willcooke> heh
[09:29] <jibel> seb128, I select French / TZ=Paris and Ubiquity proposed an English kb. Hasn't it been fixed?
[09:29] <jibel> today's build
[09:33] <seb128> jibel, I don't know, it hasn't been worked on that I though
[09:33] <seb128> we were unsure if the keyboard was supposed to match the tz selection
[09:33] <seb128> the one which was fixed is that the layout was not changing when you selected another one
[09:53] <GunnarHj> jibel, seb128: Previously the proposed kb was due to the selected language, while the tz selection added regional LC_* settings in /etc/default/locale.
[10:01] <jibel> GunnarHj, yeah but it is not working. If I select French the default keyboard layout is english
[10:02] <jibel> associating the layout to the tz does not make a lot of sense anyway
[10:05] <GunnarHj> jibel: I see. Then it's a new bug. Agree that tz -> kb wouldn't make much sense, but that relation was not present previously either, right?
[10:07] <jibel> GunnarHj, No I don't think it was.
[10:08] <jibel> But I couldn't find any spec that describes the expected behaviour
[10:23] <andyrock> looks like someone broke wpa2
[10:24] <willcooke> andyrock, in Ubuntu or just generally?
[10:25] <andyrock> in generally
[10:25] <willcooke> ohhhhhh shii........
[10:25] <andyrock> https://www.krackattacks.com/
[10:25] <andyrock> there are news around
[10:26]  * didrocks unplugs his router until a fix come in! EOW then? ;)
[10:29] <willcooke> heh, night didrocks
[10:29]  * duflu -> dinner
[10:29] <didrocks> ;)
[10:29] <didrocks> if only!
[10:30] <didrocks> ok, so discourse integration is broken again, opening a topic manually
[10:32] <didrocks> https://community.ubuntu.com/t/ubuntu-gnome-shell-in-artful-day-15/662
[10:33] <didrocks> updated the blog post to point to it (at least, only people reading the blog post will have the link to comment ;))
[10:46] <tjaalton> seb128: diff between mesa 17.2.1..17.2.2 doesn't seem too alarming, maybe could've been the kernel too. added a comment on the bug
[10:52] <didrocks> tjaalton: could be, people mention that it broke between the 5th and 7th, I asked on the french forum for someone to try older mesa with detailed instructions on how to downgrade, we'll see how this work…
[10:55] <tjaalton> didrocks: ok, thanks
[10:55] <tjaalton> it was a bugfix update, would be surprising if it broke in this way
[10:56] <didrocks> yeah, if not, I'll ask to restart on an older kernel
[10:56] <tjaalton> log diff https://pastebin.com/N9DtzfKp
[10:57] <didrocks> at least, there 3 people we can get in touch with having the issue, this is the positive side of it :)
[11:01] <tjaalton> yup
[11:31] <seb128> jibel, btw I can't confirm that layout selection bug, if I boot in french then Français/azerty is pre-selected
[11:31] <seb128> jibel, I pick the lang from the syslinux early boot and tried install only mode
[11:38] <jibel> seb128, where do you select french?
[11:38] <jibel> right in syslinugx
[11:39] <jibel> but if you select french in ubiquity it's english
[11:41] <seb128> oh, ok
[11:41] <seb128> did that work in the past?
[11:41] <seb128> I always use the syslinux first menu to select the language
[11:44] <jibel> I think it did. I'll try in xenial
[11:49] <seb128> thx
[12:14] <amano> tjaalton, I was on 4.13.0.12 when noticing the regression. And reverted back to 4.13.0.11, which didn't change anything. So I don't think that a kernel update broke my Wayland on October 6th. I will try downgrading later in the evening anyway, but I don't have time now (my GF was just taken to the hospital with breathing probs).
[12:18] <tjaalton> amano: artful had 4.12 not too long ago..
[12:19] <tjaalton> 4.13.0-12 was the first release of the series that got in artful iirc
[12:20] <amano> Oki. Will try to downgrade.
[12:28] <amano> And it is not
[12:30] <amano> Amd only, I have got an ION chipset which is nv50
[12:33] <amano> ventrical has an old nvidia card as well
[12:57] <jbicha_> Laney: fyi I pushed a fix for LP: #1719043 to our gtk3 bzr repo in case you manage to figure out the software-properties issue
[12:57] <Tribaal> hi all, where (which channel) is the community iso testing happening?
[12:58] <Tribaal> I saw omething fly by on my twitter feed but can't find it again :/
[12:58] <Laney> jbicha_: alright, trying to work on that bug
[12:58] <Laney> cheers
[13:06] <tjaalton> amano: so, not radeon which the bug was about?
[13:26] <jibel> Tribaal, we are having an UbuntuOnAir tonight at 3PM UTC
[13:27] <jibel> Tribaal, more infos on https://community.ubuntu.com/t/ubuntu-17-10-community-iso-testing/458
[13:27] <Tribaal> jibel: thanks, that's what I was looking for :)
[13:27] <jibel> yw :)
[13:28] <Tribaal> I've been doing some of that over the weekend already, wanted to report/retest my findings
[13:29] <jibel> thanks. It's the right place to go. I saw your bug with nouveau, in the meantime continue filing bugs
[13:35] <amano> tjaalton, i can confirm now that it is still freezing on on 4.12.0.13 which is from early September
[13:39] <tjaalton> amano: so another bug then
[13:46] <didrocks> tjaalton: ok, mesa doesn't seem to be the issue for the ATI users
[13:46] <didrocks> I'm asking them to revert the kernel now
[14:04] <tjaalton> didrocks: cool
[14:10] <mbiebl_> I just upgraded a test system from 17.04 to 17.10. The upgrade from Unity to GNOME was suprisingly smooth. Nice job
[14:11] <mbiebl_> There are just some smaller issues
[14:11] <seb128> mbiebl_, nice, thanks for the feedback :)
[14:11] <mbiebl_> E.g. in libreoffice, when I browse through the menu
[14:11] <seb128> mbiebl_, do you have a list?
[14:11] <mbiebl_> and the window is not maximised (i.e. translucent)
[14:11] <mbiebl_> it quickly switches between transparent and black
[14:12] <mbiebl_> i.e. the top bar flickers
[14:12] <mbiebl_> does anyone else see this or could this be a local configuration issue (this system has seen a few dist-upgrades)
[14:13] <didrocks> mbiebl_: does the menu touch or is near the top panel by any chance when you are browing through it?
[14:15] <seb128> mbiebl_, I see that as well, it does it with any application so not specific to libreoffice (just tried glade as well), I think it's a GNOME 3.26 bug
[14:15] <seb128> it does the same when opening a menu
[14:15]  * didrocks can't confirm, but I'm in a Xorg session right now
[14:15] <seb128> didrocks, I guess menus are a special type of surface and they made the panel change state when they open
[14:15] <didrocks> so window placements and detection…
[14:15] <seb128> make
[14:15] <didrocks> but the panel should only change state when in proximity from the panel
[14:16] <didrocks> (or the dock in our case)
[14:16] <seb128> didrocks, you are on an empty workspace? like no maximized win under yours?
[14:16] <didrocks> like
[14:16] <didrocks> yes
[14:16] <seb128> k, maybe wayland specific
[14:16] <seb128> and no, my glade is no near of any board
[14:16] <seb128> it's a small win in the middle
[14:16] <didrocks> so, wherever is the menu it's happening, interesting
[14:16] <seb128> I think the menus just open maybe a surface in one position and then move it to dock to the cursor or something
[14:17] <didrocks> I think upstream Shell issue, indeed (you should have the same in debian mbiebl_) as the dock only "plugs" itself proximity detection on it
[14:17] <didrocks> so we don't have any distro-patch for this
[14:17] <didrocks> let me see if there was a fix in the shell for proximity that dash to dock didn't backport
[14:17] <mbiebl_> seb128: https://people.debian.org/~biebl/gnome-shell-topbar.webm
[14:17] <didrocks> (as they did code copy)
[14:18] <mbiebl_> didrocks: ^
[14:18] <seb128> didrocks, it's a top panel issue, not a dock one
[14:18] <didrocks> seb128: unsure, their state is linked
[14:18] <seb128> k
[14:18] <mbiebl_> actually, both the dock and the topbar flicker
[14:18] <seb128> right
[14:18] <didrocks> let me confirm it quickly with a second user, brb
[14:18] <seb128> it's more visible on the panel with the text
[14:18] <didrocks> yeah, the handler is "hooked"
[14:19] <flexiondotorg> We're live at 15:00 UTC (in ~40 mins) over at UbuntuOnAir with some final ISO testing for #ubuntu 17.10. Join us! http://ubuntuonair.com/
[14:20] <didrocks> mbiebl_: seb128: confirming, happening only on Wayland, and on the vanilla session as well (with no dock), so upstream issue
[14:20] <didrocks> mbiebl_: mind opening a bugzilla issue against the Shell? (the presence detection code is there)
[14:21] <didrocks> (and hey! long time no see ;))
[14:21] <mbiebl_> didrocks: wasn't sure if it's an upstream issue
[14:21] <didrocks> I didn't see it much here, my flickering is way faster
[14:21] <mbiebl_> haven't seen this under debian
[14:21] <didrocks> same machine ?
[14:21] <mbiebl_> will try to confirm that there as well
[14:21] <mbiebl_> yeah
[14:21] <seb128> didrocks, could it be theme specific?
[14:21] <didrocks> yeah, I guess you should have it too in debian
[14:22] <didrocks> seb128: not really, well, maybe it's less visible with default theme because it's not a gradient
[14:22] <didrocks> so quicker to paint
[14:22] <didrocks> but there is no css magic or anything changing the behavior
[14:22] <didrocks> (and nothing in the js)
[14:23] <mbiebl_> didrocks: that the sidebar(dock) changes translucency as well is an Ubuntu specific change for now, right?
[14:23] <mbiebl_> I don't see that in the default dash-to-dock as available on extensions.g.o
[14:23] <didrocks> mbiebl_: indeed, the dock is, it syncs its state with the top bar one
[14:24] <didrocks> mbiebl_: ah, it's in dash to dock, but they didn't release it yet AFAIK
[14:24] <didrocks> we don't have any patch against dash to dock apart from changing the default with gsettings override
[14:24] <mbiebl_> ok, maybe that's the reason I don't see that under debian then
[14:24] <didrocks> (and removing the prefs)
[14:25] <didrocks> you should still have the top bar flickering
[14:25] <didrocks> in debian
[14:25] <didrocks> I did try on a GNOME vanilla session
[14:25] <didrocks> and still see it
[14:25] <didrocks> (apt install gnome-session -> choose the gnome session in gdm)
[14:25] <didrocks> no dock there
[14:25] <didrocks> and default upstream theme
[14:26] <didrocks> (unfortunately, you need to generally restart the gdm systemd service to get the session option showing up)
[14:28] <mbiebl_> confirmed, happens under Debian as well
[14:28] <seb128> ah :)
[14:28] <mbiebl_> it was just not as visible
[14:28] <seb128> good
[14:28] <mbiebl_> and, more importantly
[14:28] <mbiebl_> I forgot that I did run the Xorg session there :-)
[14:28] <seb128> jibel, btw I tried a xenial issue, your keyboard selection bug is already there so it's nothing new
[14:28] <didrocks> haha, double confirmation :-)
[14:29] <didrocks> but yeah, harder to see with the default theme, I think it's the gradient being slower to paint
[14:29] <mbiebl_> didrocks: will file an upstream gnome-shell bug report
[14:29] <mbiebl_> thanks for the hint
[14:30] <didrocks> thanks mbiebl_! do not hesitate if you see anything weird on our session compared to debian, we are not free of some issues on our sides :)
[14:30] <jibel> seb128, thanks, nothing critical anyway
[14:30] <seb128> indeed not
[14:31] <seb128> mbiebl_, did you have other issues on your list?
[14:31] <didrocks> seb128: tseliot: keeping you posted, kernel is out on the ATI issue, asking now to revert mutter
[14:31] <didrocks> if you see anything else on the archive at that time that could be the cause, please shout
[14:31] <seb128> didrocks, thanks (and you probably meant tjaalton ^)
[14:31] <didrocks> oupsss
[14:31] <didrocks> ;)
[14:31] <seb128> :)
[14:31] <mbiebl_> mbiebl_: the monitor config was gone after the upgrade
[14:31] <seb128> right, another GNOME issue
[14:32] <seb128> I think they changed the format what they moved the handling away from g-s-d
[14:32] <mbiebl_> I have an external monitor
[14:32] <seb128> I wonder if that's worth trying to do a migration :-/
[14:32] <mbiebl_> when docked, I disable the internal one
[14:32] <mbiebl_> (from the laptop)
[14:32] <mbiebl_> after the upgrade both were active again
[14:33] <mbiebl_> the input-field-follows-mouse on multi monitors was something I liked in lightdm btw
[14:33] <mbiebl_> would be great if you could port that to gdm :-)
[14:34] <mbiebl_> didrocks: what would be the right keyword / bug description for the gnome-shell bug?
[14:35] <didrocks> mbiebl_: "[Wayland] top bar dynamic transparency flickers between transparent and solid when browing through menus" ?
[14:36] <didrocks> or something along those lines
[14:36] <mbiebl_> k, will use that one
[14:40] <mbiebl_> my machine is 6 years old :-)
[14:40] <mbiebl_> https://bugzilla.gnome.org/show_bug.cgi?id=789060
[14:40] <mbiebl_> fwiw
[14:41] <seb128> thx
[14:41] <didrocks> perfect! I'll try to get a friend on fedora confirming as well
[14:51] <tseliot> didrocks: what ATI issue?
[14:52] <tseliot> didrocks: or was that meant for tjaalton? ^
[14:52] <tjaalton> tseliot: yep
[14:52] <tseliot> ok
[15:09] <mbiebl_> didrocks: another small issue: the scrollbar in gnome-terminal shows a black border on the right side
[15:09] <mbiebl_> which is one or two pixels larger then the window size
[15:11] <mbiebl_> https://people.debian.org/~biebl/gnome-terminal-scrollbar.png
[15:15] <Trevinho> hi guys
[15:15] <kenvandine> hey Trevinho
[15:15] <Trevinho> hi ken
[15:15] <jbicha_> mbiebl_: I believe that's upstream too (check with Adwaita on Wayland)
[15:15] <mbiebl_> I'm also not sure, if unity is still supported in 17.10, but after recreating my monitor setup with g-c-c and trying to start the unity session (which was still installed after the dist-upgrade)
[15:16] <mbiebl_> it is extremely unhappy with the config
[15:16] <Trevinho> oh... monitors.xml...
[15:16] <Trevinho> whe should move usd to use another file I gues too
[15:16] <Trevinho> mbiebl_: file a bug please
[15:17] <mbiebl_> Trevinho: which component?
[15:30] <mbiebl_> jbicha_: hm, no, can't reproduce under Debian/GNOME/Wayland
[15:38] <jbicha_> mbiebl_: I don't know, Debian is giving me X11 even when I choose "GNOME", see LP: #1720651
[15:47] <didrocks> mbiebl_: nicely spotted! Could be our theme on that one, Trevinho wdyt ^ (https://people.debian.org/~biebl/gnome-terminal-scrollbar.png)
[15:50] <didrocks> tjaalton: https://launchpadlibrarian.net/341059901/Upgrades the issue started between the 5 and the 7th, this is what was updated, any idea?
[15:50] <didrocks> mutter was ruled out of scope
[15:50] <jbicha> more specifically, the terminal issue could be in our gnome-terminal patches
[15:54] <tjaalton> didrocks: and this is booting to gdm which uses wayland?
[15:54] <didrocks> tjaalton: apparently yes (not showing up gdm). If they set EnabledWayland=false, it works from that day
[15:55] <tjaalton> ok, so that should rule out xserver I guess
[15:55] <didrocks> that's why I ruled out https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu
[15:55] <didrocks> yep
[15:55] <tjaalton> xserver synced from the stable tree in 2:1.19.3-1ubuntu7
[15:55] <didrocks> apart if something like a fallback detection doesn't work anymore?
[15:56] <tjaalton> thinking if something in xwayland support would cause it, but can't see how
[15:56] <didrocks> hum, maybe not totally stupid to make them roll back xorg + affinities
[15:56] <didrocks> at least to give a try
[15:58] <dmj_s76> It would be good to get this fix into artful (either on the iso or at least as a zero-day SRU) so users can actually configure their multi-monitor setups.
[16:00] <tjaalton> right
[16:01] <tjaalton> dmj_s76: what fix?
[16:01] <dmj_s76> this patch to the bug I pasted above:: https://bugzilla.gnome.org/attachment.cgi?id=361491
[16:03] <tjaalton> dmj_s76: ok, didn't see the paste
[16:04] <dmj_s76> currently mutter refuses to set a scaling factor when any display is below 800x600 resolution.  This means gnome control center (or any other method) will refuse to configure displays when you have a 1080p display plugged into a hidpi laptop (unless the user manually sets the hidpi screen to show insanely small)
[16:05] <dmj_s76> The patch allows a scale factor to be set if *any* monitor supports it, rather than *every* monitor.
[16:23] <didrocks> tjaalton: I'm out of ideas, xorg didn't work either
[16:35] <jbicha> dmj_s76: could you open an Ubuntu bug for that issue? at this point in the release cycle, we need to attach LP bug numbers to issues and treat them like SRUs
[16:36] <jbicha> see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for the bug template
[16:36] <jbicha> *attach bug numbers to uploads
[16:38] <dmj_s76> jbicha: on it
[16:38] <amano> didrocks, i am happy to help bisecting the GDM/Mesa/X/Plymouth/whatever regression. Sorry, that I didn't notice your request but things got out of control when my girlfriend had to be taken to the hospital. She is fine now BTW, :)
[16:42] <willcooke> ack
[16:42] <willcooke> oops wrong channel
[16:42] <flocculant> willcooke is never in the wrong channel even if it's #xubuntu-devel :)
[16:43] <willcooke> :)
[17:11] <willcooke> night all
[17:23] <dmj_s76> jbicha: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024
[17:28] <oSoMoN> good night all
[17:33] <jbicha> dmj_s76: oh I forgot to mention that patch does not apply to the gnome-3-26 branch
[17:34] <dmj_s76> jbicha: I'll rebase it
[17:57] <sarnold> rbasak: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1710637 sounds related to what you found last week
[18:09] <Gargoyle> Think I found a big security hole after installing "dash to panel" and "disable ubuntu dock" extensions. Just searching and looking if it exists....
[18:13] <Gargoyle> https://www.dropbox.com/s/4wiyinog9969ibm/dash-dock-security.jpg?dl=0
[18:19] <Gargoyle> Looks like it's the "Disable ubuntu dock" one...
[18:37] <rbasak> sarnold: thanks. That sounds like exactly what I have. I have a high enough console-setup now, so let's see and hopefully it won't happen again.
[18:38] <sarnold> rbasak: excellent
[18:55] <Gargoyle> Back again. Found the source for the extension:- https://github.com/Maestroschan/Disable-Ubuntu-Dock/blob/master/extension.js
[18:55] <Gargoyle> All it's doing is disabling 'ubuntu-dock@ubuntu.com' so I guess there's someone in an Ubuntu team that needs to fix it?
[18:56] <jbicha> Gargoyle: https://github.com/Maestroschan/Disable-Ubuntu-Dock/issues/2
[18:57] <jbicha> Ubuntu doesn't maintain or provide support for third-party extensions like that
[18:57] <Gargoyle> Check the JS file. It's a whopping 21 lines.
[18:57] <jbicha> and it's not Ubuntu's bug
[19:03] <Gargoyle> I thought Ubuntu was using a customised version of DashToDock?
[19:04] <jbicha> sorry, I don't have experience writing GNOME Shell extensions
[19:05] <jbicha> I'm guessing that that extension doesn't have *enough* lines of code to work properly
[19:09] <Gargoyle> jbicha, to me, it looks like it just proxies to "something" that looks like an official Ubuntu extension.
[19:09] <Gargoyle> Looking into the official extension... Looks like it's just a fork of dash-to-dock.
[19:11] <jbicha> yes, Ubuntu supports Ubuntu Dock (which is just a variation on Dash to Dock) but we don't support other extensions that try to modify Ubuntu Dock
[19:12] <Gargoyle> By modify, all it is doing is disabling it.
[19:16] <jbicha> but it's obviously not doing that correctly :(
[19:45] <bittin_> popey or Wimpy or someone else that might know is it possible to update Ubuntu MATE to the 17.10 RC without reinstalling a laptop?
[20:07] <dmj_s76> jbicha: try the new patch in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024