[02:30] duflu: do you ever have gnome-shell hang when resuming from suspend? [02:31] jbicha, after years of bugs I still fear suspend too much to ever suspend :/ [02:31] Also don't need to. I can either stay powered on, or just power off [02:31] well anyway, I believe Jonas's "headless" work in mutter helps fix some of those hangs/crashes [02:32] there are 2 more commits in the gnome-3-26 branch for that, that we didn't cherry-pick yet [02:35] 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] chobitslinux, there is actually a Classic mode in Gnome3. Just: apt install gnome-shell-extensions [02:37] or: sudo apt install gnome-shell-extensions [02:37] and then select the classic session on the login screen [02:46] duflu, Oh,thanks,I just has nostalgic idea. [02:48] 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:48] bug 1722195 in gnome-software (Ubuntu Artful) "no policy kit auth dialog to install or remove a snap" [Critical,Triaged] https://launchpad.net/bugs/1722195 [02:58] wa, net stability is not well these days. === chobitslinux_ is now known as chobitslinux [03:05] robert_ancell: I tried installing the moon-buggy snap and at 99% it's maxing out my cpu for several minutes :( [03:05] jbicha: from the ppa version [03:05] ? [03:06] no, from gnome-software in artful [03:06] * jbicha wonders what happens if I press Cancel [03:06] jbicha: can you confim the versioN? [03:06] is the problem of CPU poor? [03:06] gnome-software 3.26.1-0ubuntu1, any other versions you want? [03:08] I'd hoped the CPU issues were resolved in that release... :( [03:09] jbicha: does it reliably reproduce? [03:16] well when I killed it, it had actually finished installing and it didn't happen when I installed oh my giraffe [05:48] good morning desktoppers [07:20] good morning [07:20] Morning didrocks, oSoMoN [07:20] hey duflu [07:37] good morning desktopers [07:37] hey duflu oSoMoN, re didrocks [07:37] Hi seb128 [07:38] 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:47] Ubuntu bug 1723577 in gdm3 (Ubuntu) "Artful won't start with Wayland activated" [Undecided,Confirmed] [07:48] brb, moving location [07:49] <_amano> Looks like a showstopper bug. A fresh install freezing during/after displaying the Ubuntu splash screen. [07:49] jibel: do we have other similar reports ? ^ [07:50] * didrocks looks at the comments meanwhile [07:52] _amano: you told it worked until the week of the 7th October, are you able to downgrade some packages to help bisecting? [07:55] morning all [07:56] Morning willcooke. Back in the land of the living yet? [07:56] duflu, I'm doing my best impression of someone who is awake [07:56] it's not terribly convincing [07:56] good morning willcooke, had an uneventful trip back? [07:57] On IRC it is convincing. At least for a chatbot [07:57] :) Thanks $PERSON. How about that $LOCAL_SPORTS_TEAM [07:57] (only with set -e) [07:58] Go ${TEAM_NAME}s [08:01] moin [08:02] hey Laney, you middly awake too? [08:02] hey Laney, how are you? had a good week in n.y, trip back and beer festival/w.e? [08:03] Morning(ish?) Laney [08:03] hey willcooke, Laney, welcome back to the old world [08:04] is there any way to tell mailman to shup up about "moderator request waiting" daily emails? [08:04] hey willcooke [08:04] seb128, for the desktop list? [08:04] willcooke, yes [08:05] it's annoying that they changed the config when they upgraded/did maintainance [08:05] ok, 2 people on the french forum have that issue + _amano at least [08:05] I found options to disable the emails it was sending about every new request coming [08:05] hi didrocks seb128 duflu oSoMoN [08:05] * didrocks tries to get some help from them for bisecting [08:05] but not about the daily nag [08:05] * Laney is mostly alive [08:06] didrocks, having issue with gdm/wayland on some drivers? [08:06] yep [08:06] since the 07/10 [08:07] Aha! didrocks, using an AMD GPU? [08:07] what changed then? [08:07] GNOME 3.26.1, so, a lot :p [08:07] :-/ [08:07] (they aren't sure if it's the 05 or 07) [08:07] (me saw some complaints about AMD today where people said it happened around 7/10) [08:07] trying to get them on IRC to bisect [08:07] yeah [08:07] saw your typo fix on "artful*l*" duflu :p [08:08] no gdm upload at least around those dates [08:08] yeah, could be mutter/G-S… [08:10] didrocks, Mesa is often the cause of sudden graphical failures. And it got an upgrade on 5 Oct [08:11] good hint [08:11] yeah, it's a valid candidate [08:11] tjaalton, ^ [08:13] 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] 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] bug 1722427 in Ubuntu Kylin "[error-report]error occurs when reading /etc/profile" [Critical,Confirmed] https://launchpad.net/bugs/1722427 [08:17] https://launchpad.net/ubuntu/+source/im-config/0.32-1ubuntu3 [08:17] Is it acceptable for 17.10? [08:30] GunnarHj: I guess the concern is hiding real errors there, right? [08:30] like, why is that junk in stderr? [08:31] but as for acceptable for release - well, someone on the release team accepted it so there's your answer :P [08:33] 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] probably silence dbus-update-activation-environment and the other stuff [08:34] that would involve hunting down where they are called from though [08:35] 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] 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:35] bug 1723619 in linux (Ubuntu) "Ubuntu Desktop ISO fails to boot with nouveau on a displayport" [Undecided,Confirmed] https://launchpad.net/bugs/1723619 [08:37] seb128: ahah, nicely spotted! Yeah, so that could be confusing [08:37] hey all [08:37] 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] Ubuntu bug 1613158 in linux (Ubuntu) "Booting with Nvidia GTX 970 hangs with an orange/corrupt screen in kernels 4.8-4.11 (but works with 4.4.0)" [High,Confirmed] [08:37] hey andyrock [08:38] hey didrocks [08:38] how are you? [08:39] good thanks! but tired (didn't get a restful week-end due to son being sick), and you? [08:40] :/ [08:40] I had a productive w-e [08:40] I finally found a new room [08:40] to move in [08:41] oh great! when are you planning to move? [08:41] so I don't have to spend next w-e looking for a flat [08:41] next monday [08:41] \o/ [08:42] didrocks: seb128: sorry, got jumped on for like 5 things so didn't reply to you properly [08:42] beer fest was great as usual [08:42] Laney, no worry :-) [08:43] unusually warm, like 20° [08:43] hey andyrock [08:43] so we hung around outside for a while [08:43] and I had the row to myself on the plane back so could sleep across the chairs [08:43] was just like business class [08:43] Nice! [08:44] hey willcooke [08:44] get back ok? [08:44] free upgrade © [08:44] andyrock: waow, that's quick! [08:44] 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] andyrock: enjoy moving in :) [08:44] btw I found a way to reproduce [08:44] https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a [08:52] andyrock, how do you trigger it? [08:52] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720400/comments/2 [08:52] Ubuntu bug 1720400 in gnome-control-center (Ubuntu) "/usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render" [High,Triaged] [08:52] seb128: ^^^ [08:52] I'm working on it [08:52] andyrock, thanks [08:53] trying to understand if I can fix it otherwise I'll ping the gnome-control-center guys [08:53] andyrock, when you write "system should crash" do you mean g-c-c or the session or the kernel? [08:54] just g-c-c [08:54] I'll update that [08:55] thanks [08:57] thx [09:00] brb [09:12] jibel, would you be able to test https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723312 today? [09:12] Ubuntu bug 1723312 in gnome-software (Ubuntu Artful) "/usr/bin/gnome-software:11:g_variant_is_trusted:g_variant_builder_add_value:g_variant_valist_new:g_variant_new_va:g_variant_new" [Critical,Fix committed] [09:13] 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] willcooke, I'm on it [09:15] willcooke, everything looks good so far [09:17] merci jibel [09:24] ooh [09:24] gcal now has an option for UTC (no DST) [09:28] Ugh. Europe morning. [09:28] * duflu gives up retrying Launchpad timeouts [09:28] heh [09:29] seb128, I select French / TZ=Paris and Ubiquity proposed an English kb. Hasn't it been fixed? [09:29] today's build [09:33] jibel, I don't know, it hasn't been worked on that I though [09:33] we were unsure if the keyboard was supposed to match the tz selection [09:33] the one which was fixed is that the layout was not changing when you selected another one [09:53] 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] GunnarHj, yeah but it is not working. If I select French the default keyboard layout is english [10:02] associating the layout to the tz does not make a lot of sense anyway [10:05] 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] GunnarHj, No I don't think it was. [10:08] But I couldn't find any spec that describes the expected behaviour [10:23] looks like someone broke wpa2 [10:24] andyrock, in Ubuntu or just generally? [10:25] in generally [10:25] ohhhhhh shii........ [10:25] https://www.krackattacks.com/ [10:25] there are news around [10:26] * didrocks unplugs his router until a fix come in! EOW then? ;) [10:29] heh, night didrocks [10:29] * duflu -> dinner [10:29] ;) [10:29] if only! [10:30] ok, so discourse integration is broken again, opening a topic manually [10:32] https://community.ubuntu.com/t/ubuntu-gnome-shell-in-artful-day-15/662 [10:33] updated the blog post to point to it (at least, only people reading the blog post will have the link to comment ;)) [10:46] 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] 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] didrocks: ok, thanks [10:55] it was a bugfix update, would be surprising if it broke in this way [10:56] yeah, if not, I'll ask to restart on an older kernel [10:56] log diff https://pastebin.com/N9DtzfKp [10:57] at least, there 3 people we can get in touch with having the issue, this is the positive side of it :) [11:01] yup [11:31] jibel, btw I can't confirm that layout selection bug, if I boot in french then Français/azerty is pre-selected [11:31] jibel, I pick the lang from the syslinux early boot and tried install only mode [11:38] seb128, where do you select french? [11:38] right in syslinugx [11:39] but if you select french in ubiquity it's english [11:41] oh, ok [11:41] did that work in the past? [11:41] I always use the syslinux first menu to select the language [11:44] I think it did. I'll try in xenial [11:49] thx [12:14] 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] amano: artful had 4.12 not too long ago.. [12:19] 4.13.0-12 was the first release of the series that got in artful iirc [12:20] Oki. Will try to downgrade. [12:28] And it is not [12:30] Amd only, I have got an ION chipset which is nv50 [12:33] ventrical has an old nvidia card as well [12:57] 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] Launchpad bug 1719043 in gtk+3.0 (Ubuntu) "Gnome web urlbar very slow to show typed input" [Medium,In progress] https://launchpad.net/bugs/1719043 [12:57] hi all, where (which channel) is the community iso testing happening? [12:58] I saw omething fly by on my twitter feed but can't find it again :/ [12:58] jbicha_: alright, trying to work on that bug [12:58] cheers [13:06] amano: so, not radeon which the bug was about? [13:26] Tribaal, we are having an UbuntuOnAir tonight at 3PM UTC [13:27] Tribaal, more infos on https://community.ubuntu.com/t/ubuntu-17-10-community-iso-testing/458 [13:27] jibel: thanks, that's what I was looking for :) [13:27] yw :) [13:28] I've been doing some of that over the weekend already, wanted to report/retest my findings [13:29] thanks. It's the right place to go. I saw your bug with nouveau, in the meantime continue filing bugs [13:35] tjaalton, i can confirm now that it is still freezing on on 4.12.0.13 which is from early September [13:39] amano: so another bug then === amano_ is now known as amano [13:46] tjaalton: ok, mesa doesn't seem to be the issue for the ATI users [13:46] I'm asking them to revert the kernel now [14:04] didrocks: cool [14:10] 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] There are just some smaller issues [14:11] mbiebl_, nice, thanks for the feedback :) [14:11] E.g. in libreoffice, when I browse through the menu [14:11] mbiebl_, do you have a list? [14:11] and the window is not maximised (i.e. translucent) [14:11] it quickly switches between transparent and black [14:12] i.e. the top bar flickers [14:12] does anyone else see this or could this be a local configuration issue (this system has seen a few dist-upgrades) [14:13] mbiebl_: does the menu touch or is near the top panel by any chance when you are browing through it? [14:15] 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] 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] didrocks, I guess menus are a special type of surface and they made the panel change state when they open [14:15] so window placements and detection… [14:15] make [14:15] but the panel should only change state when in proximity from the panel [14:16] (or the dock in our case) [14:16] didrocks, you are on an empty workspace? like no maximized win under yours? [14:16] like [14:16] yes [14:16] k, maybe wayland specific [14:16] and no, my glade is no near of any board [14:16] it's a small win in the middle [14:16] so, wherever is the menu it's happening, interesting [14:16] 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] 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] so we don't have any distro-patch for this [14:17] let me see if there was a fix in the shell for proximity that dash to dock didn't backport [14:17] seb128: https://people.debian.org/~biebl/gnome-shell-topbar.webm [14:17] (as they did code copy) [14:18] didrocks: ^ [14:18] didrocks, it's a top panel issue, not a dock one [14:18] seb128: unsure, their state is linked [14:18] k [14:18] actually, both the dock and the topbar flicker [14:18] right [14:18] let me confirm it quickly with a second user, brb [14:18] it's more visible on the panel with the text [14:18] yeah, the handler is "hooked" [14:19] 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] mbiebl_: seb128: confirming, happening only on Wayland, and on the vanilla session as well (with no dock), so upstream issue [14:20] mbiebl_: mind opening a bugzilla issue against the Shell? (the presence detection code is there) [14:21] (and hey! long time no see ;)) [14:21] didrocks: wasn't sure if it's an upstream issue [14:21] I didn't see it much here, my flickering is way faster [14:21] haven't seen this under debian [14:21] same machine ? [14:21] will try to confirm that there as well [14:21] yeah [14:21] didrocks, could it be theme specific? [14:21] yeah, I guess you should have it too in debian [14:22] seb128: not really, well, maybe it's less visible with default theme because it's not a gradient [14:22] so quicker to paint [14:22] but there is no css magic or anything changing the behavior [14:22] (and nothing in the js) [14:23] didrocks: that the sidebar(dock) changes translucency as well is an Ubuntu specific change for now, right? [14:23] I don't see that in the default dash-to-dock as available on extensions.g.o [14:23] mbiebl_: indeed, the dock is, it syncs its state with the top bar one [14:24] mbiebl_: ah, it's in dash to dock, but they didn't release it yet AFAIK [14:24] we don't have any patch against dash to dock apart from changing the default with gsettings override [14:24] ok, maybe that's the reason I don't see that under debian then [14:24] (and removing the prefs) [14:25] you should still have the top bar flickering [14:25] in debian [14:25] I did try on a GNOME vanilla session [14:25] and still see it [14:25] (apt install gnome-session -> choose the gnome session in gdm) [14:25] no dock there [14:25] and default upstream theme [14:26] (unfortunately, you need to generally restart the gdm systemd service to get the session option showing up) [14:28] confirmed, happens under Debian as well [14:28] ah :) [14:28] it was just not as visible [14:28] good [14:28] and, more importantly [14:28] I forgot that I did run the Xorg session there :-) [14:28] jibel, btw I tried a xenial issue, your keyboard selection bug is already there so it's nothing new [14:28] haha, double confirmation :-) [14:29] but yeah, harder to see with the default theme, I think it's the gradient being slower to paint [14:29] didrocks: will file an upstream gnome-shell bug report [14:29] thanks for the hint [14:30] 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] seb128, thanks, nothing critical anyway [14:30] indeed not [14:31] mbiebl_, did you have other issues on your list? [14:31] seb128: tseliot: keeping you posted, kernel is out on the ATI issue, asking now to revert mutter [14:31] if you see anything else on the archive at that time that could be the cause, please shout [14:31] didrocks, thanks (and you probably meant tjaalton ^) [14:31] oupsss [14:31] ;) [14:31] :) [14:31] mbiebl_: the monitor config was gone after the upgrade [14:31] right, another GNOME issue [14:32] I think they changed the format what they moved the handling away from g-s-d [14:32] I have an external monitor [14:32] I wonder if that's worth trying to do a migration :-/ [14:32] when docked, I disable the internal one [14:32] (from the laptop) [14:32] after the upgrade both were active again [14:33] the input-field-follows-mouse on multi monitors was something I liked in lightdm btw [14:33] would be great if you could port that to gdm :-) [14:34] didrocks: what would be the right keyword / bug description for the gnome-shell bug? [14:35] mbiebl_: "[Wayland] top bar dynamic transparency flickers between transparent and solid when browing through menus" ? [14:36] or something along those lines [14:36] k, will use that one [14:40] my machine is 6 years old :-) [14:40] https://bugzilla.gnome.org/show_bug.cgi?id=789060 [14:40] Gnome bug 789060 in general "[Wayland] top bar dynamic transparency flickers between transparent and solid when browing through menus" [Normal,New] [14:40] fwiw [14:41] thx [14:41] perfect! I'll try to get a friend on fedora confirming as well [14:51] didrocks: what ATI issue? [14:52] didrocks: or was that meant for tjaalton? ^ [14:52] tseliot: yep [14:52] ok [15:09] didrocks: another small issue: the scrollbar in gnome-terminal shows a black border on the right side [15:09] which is one or two pixels larger then the window size [15:11] https://people.debian.org/~biebl/gnome-terminal-scrollbar.png [15:15] hi guys [15:15] hey Trevinho [15:15] hi ken [15:15] mbiebl_: I believe that's upstream too (check with Adwaita on Wayland) [15:15] 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] it is extremely unhappy with the config [15:16] oh... monitors.xml... [15:16] whe should move usd to use another file I gues too [15:16] mbiebl_: file a bug please [15:17] Trevinho: which component? [15:30] jbicha_: hm, no, can't reproduce under Debian/GNOME/Wayland [15:38] mbiebl_: I don't know, Debian is giving me X11 even when I choose "GNOME", see LP: #1720651 [15:38] Launchpad bug 1720651 in gnome-terminal (Ubuntu) "Scrollbar drawing broken on wayland sesssion" [Undecided,Confirmed] https://launchpad.net/bugs/1720651 === jbicha_ is now known as jbicha [15:47] mbiebl_: nicely spotted! Could be our theme on that one, Trevinho wdyt ^ (https://people.debian.org/~biebl/gnome-terminal-scrollbar.png) [15:50] tjaalton: https://launchpadlibrarian.net/341059901/Upgrades the issue started between the 5 and the 7th, this is what was updated, any idea? [15:50] mutter was ruled out of scope [15:50] more specifically, the terminal issue could be in our gnome-terminal patches [15:54] didrocks: and this is booting to gdm which uses wayland? [15:54] tjaalton: apparently yes (not showing up gdm). If they set EnabledWayland=false, it works from that day [15:55] ok, so that should rule out xserver I guess [15:55] that's why I ruled out https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu [15:55] yep [15:55] xserver synced from the stable tree in 2:1.19.3-1ubuntu7 [15:55] apart if something like a fallback detection doesn't work anymore? [15:56] thinking if something in xwayland support would cause it, but can't see how [15:56] hum, maybe not totally stupid to make them roll back xorg + affinities [15:56] at least to give a try [15:58] 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] right [16:01] dmj_s76: what fix? [16:01] this patch to the bug I pasted above:: https://bugzilla.gnome.org/attachment.cgi?id=361491 [16:03] dmj_s76: ok, didn't see the paste [16:04] 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] The patch allows a scale factor to be set if *any* monitor supports it, rather than *every* monitor. [16:23] tjaalton: I'm out of ideas, xorg didn't work either [16:35] 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] see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for the bug template [16:36] *attach bug numbers to uploads [16:38] jbicha: on it [16:38] 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] ack [16:42] oops wrong channel [16:42] willcooke is never in the wrong channel even if it's #xubuntu-devel :) [16:43] :) [17:11] night all [17:23] jbicha: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024 [17:23] Ubuntu bug 1724024 in mutter (Ubuntu) "can't set usable scale for hidpi internal display if when using external display less than 1600x1200" [Undecided,New] [17:28] good night all [17:33] dmj_s76: oh I forgot to mention that patch does not apply to the gnome-3-26 branch [17:34] jbicha: I'll rebase it [17:57] rbasak: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1710637 sounds related to what you found last week [17:57] Ubuntu bug 1710637 in console-setup (Ubuntu) "Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland" [High,Fix released] [18:09] 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] https://www.dropbox.com/s/4wiyinog9969ibm/dash-dock-security.jpg?dl=0 [18:19] Looks like it's the "Disable ubuntu dock" one... [18:37] 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] rbasak: excellent [18:55] Back again. Found the source for the extension:- https://github.com/Maestroschan/Disable-Ubuntu-Dock/blob/master/extension.js [18:55] 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] Gargoyle: https://github.com/Maestroschan/Disable-Ubuntu-Dock/issues/2 [18:57] Ubuntu doesn't maintain or provide support for third-party extensions like that [18:57] Check the JS file. It's a whopping 21 lines. [18:57] and it's not Ubuntu's bug [19:03] I thought Ubuntu was using a customised version of DashToDock? [19:04] sorry, I don't have experience writing GNOME Shell extensions [19:05] I'm guessing that that extension doesn't have *enough* lines of code to work properly [19:09] jbicha, to me, it looks like it just proxies to "something" that looks like an official Ubuntu extension. [19:09] Looking into the official extension... Looks like it's just a fork of dash-to-dock. [19:11] 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] By modify, all it is doing is disabling it. [19:16] but it's obviously not doing that correctly :( [19:45] 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] jbicha: try the new patch in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024 [20:07] Ubuntu bug 1724024 in mutter (Ubuntu) "can't set usable scale for hidpi internal display if when using external display less than 1600x1200" [Medium,In progress]