Re: lightdm or gdm?
(I know the question wasn't directly relevant to this thread but it's worth clearing up...) Mir /was/ going to support remote desktops eventually. Just as Gnome Shell on Wayland will (if not already) support them. The functionality might not be complete yet, but that's just because it's still too new and nobody has done the work yet. Regardless, you always have the option of running other desktop environments with Ubuntu. If some feature like remote desktop support is broken or missing in Ubuntu 17.10/18.04, please log a bug... - Daniel On 01/05/17 13:35, Khurshid Alam wrote: Hi, On Thu, Apr 27, 2017 at 10:30 PM, Oliver Grawert wrote: thats not a gdm thing ... vnc and any remote desktop feature wont run under any of the new display server technologies (be it wayland or mir ...). a lightdm running under wayland wouldnt be able to provide that feature either. Yes I know. But I was testing under x with 17.04. For me, X+lightdm+shell+mutter works, but X+gdm+shell+mutter doesn't. I know Ubuntu will choose wayland as default session in 17.10/18.04. By then if my vnc session doesn't work I will have to shift to another desktop environment. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
MP3 is free (?)
Are there plans to change the packages included in Ubuntu 17.10 with the end of MP3 licensing? https://www.iis.fraunhofer.de/en/ff/amm/prod/audiocodec/audiocodecs/mp3.html https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedora/ -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Experience on switching to GNOME Shell
I started an attempt at culling the gnome-shell bug list down to a manageable size yesterday. The goal being to formulate a current and shorter list that is not overwhelmingly big or out of date. Then people can start to see the launchpad bug list as achievable and useful. Or at least something we can stop from having unbounded growth. So I would log enhancement ideas in launchpad, with some tag like 'gnome-18.04'... https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs But that's just me. Staying where the users are is best for community involvement. And the community is much bigger (hence more powerful) than Canonical alone. But you have to give them a voice, which AFAIK is best achieved in the log of a launchpad bug. On 18/05/17 06:28, Robert Ancell wrote: Hi all, I've been using GNOME Shell for about a month now and I've had open a Google Doc that I've been using to list down the things that I would like to see resolved by 18.04 to ship a great experience. Now I have a bit of a list, I'm wondering what the most productive way is to use this. I'm hesitant to just post it here, because that will likely end up in a big bikeshedding [1] session... Does anyone else have such a list; should we look for a method to combine them? I know there's a survey in progress for GNOME Shell extensions [1] and someone mentioned a papercut project would be a good idea (can't find a link). We can make a Trello board too. Any other ideas? --Robert [1] https://en.wikipedia.org/wiki/Law_of_triviality [2] http://www.omgubuntu.co.uk/2017/05/ubuntu-desktop-gnome-extensions-survey-1710 -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Poor Gnome-Shell Performance in Artful
Yes indeed. We have a few bugs tracking those problems: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=performance But I was going to wait and see how the optimizations in Gnome 3.25/3.26 work out before worrying about them. - Daniel On 16/06/17 18:06, Khurshid Alam wrote: Hi, I have been trying gnome-shell on artful and the performance of shell is pretty poor compare to Unity. By performance in general I mean: a) jittery animations b) lag when moving windows c) high cpu usge d) high memory usage (gnome-shell process) e) overall smoothness Here is the result I gather so far (without any third-party extensions): 1) Dell XPS 13 X: Somewhat works ok Wayland: Lags with animation 2) i5, Nvidia 940/965, 8 GB RAM X: Lags everywhere even with animation disabled Wayland: Lags everywhere even with animation disabled Cpu: High, Memory: high (> 400 MB) No games on wayland 3) i3, intel hd 5500, 4400, 8 GB RAM X: Lags everywhere with animation disabled + screen flickering Wayland: Lags even more than x (but no screen flickering) Cpu: High, Memory: high (> 400 MB) No games on wayland 4) Core 2 Due (Quad Core), intel 965, 4 GB RAM X: Not usable Wayland: Doesn't boot It has been like this since the beginning with mutterFinally upstream making an effort to improve performance : https://bugzilla.gnome.org/show_bug.cgi?id=782344 It's huge change with ABI break and may land in 3.26, that is why I am thinking may be it's not a bad idea to stay on gnome-shell (3.24) for 17.10 (even with this poor performance). Thanks. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Weekly newsletter 23rd June 2017
The documentation for video acceleration continues to evolve day-to-day as we learn where the bugs are, and errata in external documentation. So if you're interested, please check this page for updates: https://wiki.ubuntu.com/IntelQuickSyncVideo On 23/06/17 22:48, Will Cooke wrote: Hi all, Here's an update from this week: = GNOME = We’ve migrated ubuntu-session to a new unity-session package. This means that the default session is GNOME Shell and people can install Unity 7 and it’s related packages via unity-session. The migration is working well so far, but we still have some more work to do in order to make sure everything “just works”. = LivePatch = We’re now working on the update-manager UI to add the list of kernel CVEs which are handled by the LivePatch service and a brief description of each. = Snaps = We’ve done more work on getting desktop themes working better with Snaps. We’re documenting the problems we’ve encountered and are creating some sample Snaps help with making the improvements we need. = QA = We completed our review of the desktop test plan this week and have set our priorities for this cycle. This will cover installation, upgrades, some core application smoke tests, suspend/resume, Network Manager and translations. We will be publishing a blog on how you can get involved next week. = Updates = A new version of PulseAudio is in Xenial proposed (version 1:8.0-0ubuntu3.3). This brings fixes for Bluetooth A2DP audio devices. We’d appreciate testing and feedback. https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 Updated chromium beta to 60.0.3112.32, dev to 61.0.3128.3. = Video Acceleration = We’ve got hardware accelerated video decoding working in a Proof-Of-Concept using a GStreamer and VA-API pipeline. The result is 3% CPU usage to play an h264 4K 60FPS video on Haswell. 4K h265 HEVC is also playable but requires a Skylake or later processor.This wiki page has been updated with information about how to try it yourself: https://wiki.ubuntu.com/IntelQuickSyncVideo Cheers, Will -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Restricted extra/addons
Bryan, You read my mind. I was in the process of finding out how to add to the list :) Although gstreamer1.0-plugins-bad does have important uses such as providing audio codecs and the GL plugin, totem will install it on demand, anyway. So yes you should be able to drop it. I would like to add a couple to that list though: - va-driver-all (should include i965-va-driver) - gstreamer1.0-vaapi Those together with some fixes I am working on for them will give Totem hardware accelerated video decoding out-of-the box. For more information about my intention see: https://wiki.ubuntu.com/IntelQuickSyncVideo P.S. gstreamer1.0-libav is a misnomer: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1694409 - Daniel On 02/08/17 00:18, Bryan Quigley wrote: Hi all, Been looking at what's brought in by default by the restricted checkbox in the installer and I think we can have better defaults. Here is a brief summary of what we have today: ubuntu-restricted-addons (what the installer checkbox does) - Flash - gstreamer1.0-fluendo-mp3 - chromium-codecs-ffmpeg-extra - gstreamer1.0-libav (and dependencies are 114 MB) - gstreamer1.0-plugins-ugly (just 5 MB) - gstreamer1.0-plugins-bad (314 MB) ubuntu-restricted-extras (what we recommend if on installed system) - the above ubuntu-restricted-addons - libavcodec-extra - ttf-mscorefonts-installer - unrar Proposals (all just affect being in the metapackages, not in archives). I'm envisioning ending the -extras package. Flash - remove Adobe is officially killing it entirely at end of 2020 - https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html Apparently Mac OS may have stopped including it by default in *2010*. Mozilla (and all browser vendors) will make Flash more inconvenient to use in the 2nd half of 2018. Requiring people to specifically install it will make it easier to determine how many Ubuntu users actually really want Flash. gstreamer1.0-fluendo-mp3 - hoping we can provide MP3 support by default soon like Fedora just did (right?). Still on track for 18.04 or can that be pushed up? gstreamer1.0-plugins-bad - remove This is by far the heaviest item we bring in and from what I can tell libav and ugly really cover the majority of codecs most people will run into. Bad plugins also likely provide an easy security target as they say they have code quality issues. unrar - remove One of the biggest uses is with comic books, but apparently that can be done for free these days - http://www.omgubuntu.co.uk/2017/07/evince-3-26-will-let-view-adobe-illustrator-cbr-files I also don't expect the use of unrar to be anywhere near the tasks the other packages enables. libavcodec-extra - remove or move to -addons no preference, doesn't seem like size is the issue ttf-mscorefonts-installer - promote to -addons Fonts missing is one of the biggest reasons documents in LibreOffice don't like they do in MS Office. Thanks! Bryan -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Restricted extra/addons
Doug, I bring good news... gstreamer1.0-vaapi actually does not depend on the "bad" plugins, or any other gstreamer plugins. And yes you are right mpv is much better than totem for performance and smoothness. I hope to bring totem up to the same standard eventually. totem/gst-vaapi will work in a Wayland session after we release my fixes in 17.10. You can try an early version here: https://launchpad.net/~vanvugt/+archive/ubuntu/videoaccel - Daniel On 03/08/17 04:58, doug wrote: gstreamer1.0-vaapi currently deps on the bad plugins, are you all going to change that? For the most part it's worked well over the past couple of years, not nearly as efficient as vaapi in mpv but still a decent reduction in cpu use. (- probably 20 -35% of what totem would use without, similar to what vlc does when vlc happens to work. Though atm it, (totem/gst-vaapi) doesn't seem to work at all in wayland session, actually only mpv does sans window deco.. Doug On 08/02/2017 07:30 AM, Will Cooke wrote: On 2 August 2017 at 02:53, Daniel van Vugt mailto:daniel.van.v...@canonical.com>> wrote: Although gstreamer1.0-plugins-bad does have important uses such as providing audio codecs and the GL plugin, totem will install it on demand, anyway. So yes you should be able to drop it. I would like to add a couple to that list though: - va-driver-all (should include i965-va-driver) - gstreamer1.0-vaapi Is there value in getting them promoted to main for 18.04? I think the codec licensing is taken care of by the graphics hardware vendor so I think we should be ok there. If Totem will pull them in automatically that's good - but I'd love to be able to go one step further and have them "in the box". Cheers, Will -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Restricted extra/addons
Oh, I see, sorry. gstreamer1.0-vaapi depends on: libgstreamer-plugins-bad1.0-0 which is not "the bad plugins" package: gstreamer1.0-plugins-bad but it is an obviously-related support library still. I'm working in this area lately so will see how feasible it is to loosen that dependency. On 03/08/17 23:06, Bryan Quigley wrote: After installing va-driver-all on fresh ubuntu 17.10 install (so ignoring the few packages that brings in) gstreamer1.0-vaapi does still bring in libgstreamer-plugins-bad1.0-0 libopencv-core3.1 libtbb2 libva-drm1 libva-wayland1 libva-x11-1 (only 5 MB). This doesn't block us adding it to the restricted sets, but might complicate getting it in main. (I wonder if opencv might end up heading for main eventually anyway. Definitely useful in embedded/drones but might also be involved in the future of webcams - think Intel RealSense) On Wed, Aug 2, 2017 at 10:12 PM, Daniel van Vugt wrote: Doug, I bring good news... gstreamer1.0-vaapi actually does not depend on the "bad" plugins, or any other gstreamer plugins. And yes you are right mpv is much better than totem for performance and smoothness. I hope to bring totem up to the same standard eventually. totem/gst-vaapi will work in a Wayland session after we release my fixes in 17.10. You can try an early version here: https://launchpad.net/~vanvugt/+archive/ubuntu/videoaccel - Daniel On 03/08/17 04:58, doug wrote: gstreamer1.0-vaapi currently deps on the bad plugins, are you all going to change that? For the most part it's worked well over the past couple of years, not nearly as efficient as vaapi in mpv but still a decent reduction in cpu use. (- probably 20 -35% of what totem would use without, similar to what vlc does when vlc happens to work. Though atm it, (totem/gst-vaapi) doesn't seem to work at all in wayland session, actually only mpv does sans window deco.. Doug On 08/02/2017 07:30 AM, Will Cooke wrote: On 2 August 2017 at 02:53, Daniel van Vugt mailto:daniel.van.v...@canonical.com>> wrote: Although gstreamer1.0-plugins-bad does have important uses such as providing audio codecs and the GL plugin, totem will install it on demand, anyway. So yes you should be able to drop it. I would like to add a couple to that list though: - va-driver-all (should include i965-va-driver) - gstreamer1.0-vaapi Is there value in getting them promoted to main for 18.04? I think the codec licensing is taken care of by the graphics hardware vendor so I think we should be ok there. If Totem will pull them in automatically that's good - but I'd love to be able to go one step further and have them "in the box". Cheers, Will -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Restricted extra/addons
Yeah the naming of "bad" and "ugly" gstreamer plugins is unfortunate. Those names mask the fact that you really do need them to play common media formats. That PPA does work but I failed to mention it requires Ubuntu 17.10 and that you have followed the quick start instructions: https://wiki.ubuntu.com/IntelQuickSyncVideo - Daniel On 05/08/17 05:33, doug wrote: On 08/03/2017 09:50 PM, Daniel van Vugt wrote: Oh, I see, sorry. gstreamer1.0-vaapi depends on: libgstreamer-plugins-bad1.0-0 which is not "the bad plugins" package: gstreamer1.0-plugins-bad but it is an obviously-related support library still. I'm working in this area lately so will see how feasible it is to loosen that dependency. I believe it's 2 .so's used. Any possibility of improving those libs so the can go to the good plugin? (- the vaapi ppa build isn't working here on a Haswell machine. On 03/08/17 23:06, Bryan Quigley wrote: After installing va-driver-all on fresh ubuntu 17.10 install (so ignoring the few packages that brings in) gstreamer1.0-vaapi does still bring in libgstreamer-plugins-bad1.0-0 libopencv-core3.1 libtbb2 libva-drm1 libva-wayland1 libva-x11-1 (only 5 MB). This doesn't block us adding it to the restricted sets, but might complicate getting it in main. (I wonder if opencv might end up heading for main eventually anyway. Definitely useful in embedded/drones but might also be involved in the future of webcams - think Intel RealSense) On Wed, Aug 2, 2017 at 10:12 PM, Daniel van Vugt wrote: Doug, I bring good news... gstreamer1.0-vaapi actually does not depend on the "bad" plugins, or any other gstreamer plugins. And yes you are right mpv is much better than totem for performance and smoothness. I hope to bring totem up to the same standard eventually. totem/gst-vaapi will work in a Wayland session after we release my fixes in 17.10. You can try an early version here: https://launchpad.net/~vanvugt/+archive/ubuntu/videoaccel - Daniel On 03/08/17 04:58, doug wrote: gstreamer1.0-vaapi currently deps on the bad plugins, are you all going to change that? For the most part it's worked well over the past couple of years, not nearly as efficient as vaapi in mpv but still a decent reduction in cpu use. (- probably 20 -35% of what totem would use without, similar to what vlc does when vlc happens to work. Though atm it, (totem/gst-vaapi) doesn't seem to work at all in wayland session, actually only mpv does sans window deco.. Doug On 08/02/2017 07:30 AM, Will Cooke wrote: On 2 August 2017 at 02:53, Daniel van Vugt <mailto:daniel.van.v...@canonical.com>> wrote: Although gstreamer1.0-plugins-bad does have important uses such as providing audio codecs and the GL plugin, totem will install it on demand, anyway. So yes you should be able to drop it. I would like to add a couple to that list though: - va-driver-all (should include i965-va-driver) - gstreamer1.0-vaapi Is there value in getting them promoted to main for 18.04? I think the codec licensing is taken care of by the graphics hardware vendor so I think we should be ok there. If Totem will pull them in automatically that's good - but I'd love to be able to go one step further and have them "in the box". Cheers, Will -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: 64 bit iso with 32 bit uefi ?
I would like to see this happen too. I've got at least one cheap Windows machine here that simply can't boot Ubuntu without the aforementioned awkward hacks. 64-bit CPU but 32-bit UEFI support only... So far I've only been able to boot Android-x86 on such hardware, since it has had UEFI 32-bit support in 64-bit images for some years. On 04/10/17 01:01, Dimitri John Ledkov wrote: On 3 October 2017 at 17:18, Khurshid Alam wrote: Hi Jeremy, On Tue, Oct 3, 2017 at 6:24 PM, Jeremy Bicha wrote: I don't know much about this topic. Can you point to more information about this issue? Specifically, can you find a source for your 10 million claim? I think it varies with country. On some country like here in India most of them come with 32 bit uefi due to oem agreement I guess. Hp claims they ship over 13 million units per 3/4-quarter only in US and more than 80% are windows. That's how I deducted the number. As for 32 bit uefi, Many dell inspiron i3 ($300-$500) still have 32 bit. http://amzn.to/2kjv6Gf Which are certified with UEFI 64bit on Ubuntu, and some of these are even available with Ubuntu preinstalled from Dell direct. https://certification.ubuntu.com/hardware/201508-19149/ Asus X and R series : http://bit.ly/2fHspJG (Only windows 10, dos are fine) All the Asus cheap eebook series , like asus x205ta, https:/ /www.asus.com/in/Laptops/ASUS_EeeBook_X205TA/ Those which are pre-installed with ms-dos are fine. Also I found some are listed in Ubuntu Desktop certified hardware but the are with 32 bit uefi. (Technically it's ok, because on the website, Ubuntu 16.04 is listed as supported and 16.04 has 32 bit. ) And are these devices even suitable for Ubuntu anyway? Please check https://certification.ubuntu.com/ many of these have been certified by Canonical and manufacturer to be explicitly compatible with Ubuntu since like 14.04 LTS using the 64bit / amd64 OS images. I have used hack from https://askubuntu.com/questions/392719/32-bit-uefi-boot-support and from https://askubuntu.com/questions/749306/ After installing everything works out of the box including sd-card reader which never worked prior to 17.10. Suggestion: We only requ ire bootia32.efi on EFI/BOOT/ and i386-efi in boot/grub. May these can be shipped with the iso? That's what debian multiarch iso does (http://cdimage.debian.org/debian-cd/current/multi-arch/). This means both grub-efi-ia32 and grub-efi-amd64 needs to be pre-installed for the live iso. Thoughts? Since none of the machines ship 32bit UEFI anymore, adding support for 32bit UEFI has diminishing returns. Patches to livecd-rootfs / ubuntu-cdimage / d-i / ubiquity would be required to support this in Ubuntu, and so far it has not been a priority to add support for. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Hardware-accelerated video playback (beta 2)
Hi all, Just an update on hardware-accelerated video playback for Intel GPUs... Ubuntu 17.10 beta 2 introduces out-of-the-box support for hardware acceleration as much as possible. However there are some caveats still so please refer to the updated wiki page: https://wiki.ubuntu.com/IntelQuickSyncVideo The remaining totem performance issues are actually separate to the use of hardware acceleration, and additional fixes in that area are coming soon. - Daniel -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Design-Team
There is certainly a hunger within Canonical to make 18.04 something special. When the relevant public discussion happens you will probably see it here: https://community.ubuntu.com On 12/10/17 07:14, Mads Rosendahl wrote: Hi I set out to contact the Canonical design-team, but there doesn't seem to be a design mailinglist nor contact info anywhere (sigh!), and so I hope this thread will be passed on to the right people. What's happening behind the closed design-team doors? :o) Are there any plans for a 18.04 "makeover"? I ask, because I want to contribute! I came across Didrocks post (http://disq.us/p/1lwtm4u) which implies that you (Canonical) are interested. I'm sure there's a ton of passioned people in the community willing to spent their free time working on this. If a Canonical decision already has been made, please communicate that, and if no action has been taken, let's work together (the community and the design-team) to create a beautiful Ubuntu desktop. Some inspiration could be: https://snwh.org/images/screenshots/suru/3.png https://www.behance.net/gallery/28804097/Ubuntu-1604-Stupendously-Hot-Charmander-concept So basically what I'm asking is, how can I help? Best regards /MadsRH/ -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
** Changed in: gnome-shell Importance: Undecided => Unknown ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: None => GNOME Bug Tracker #789166 ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
** Project changed: mutter => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Hi all, There are a number of bugs in gnome-shell that would exhibit symptoms like this bug describes. So I'm going to ask: @koalay only: Please run 'apport-collect 1721428' on the affected machine to help us gather more information. Everyone: Look in /var/crash for some .crash files. If you find any then please use the command: ubuntu-bug /var/crash/YOURFILE.crash to create a new bug. And then mention your new bug ID here. Careful not to attach crash files to existing bugs. Each crash file should create a new bug. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Yes, sorry, that seems to be a missing feature (or bug?) of apport. It tells you a crash happened but not where to follow it up on the web. Here's how to find out where your crash(es) went. In a terminal run the below command. It will ask you for your password because for some (security) reason the machine's unique ID is considered private. Enter you password when asked and it should then open a web page with all the crashes listed from your machine: xdg-open "https://errors.ubuntu.com/user/"`sudo cat /var/lib/whoopsie /whoopsie-id` or as two separate lines ending in a backtick: xdg-open "https://errors.ubuntu.com/user/"` sudo cat /var/lib/whoopsie/whoopsie-id` The page will initially say "No data to display" but wait a second or two and it will then be populated. Clicking on a crash's link in the Received column will open details about that particular instance. Then to follow it up scroll to the bottom of the page and click on the "Problem" link. That will take you to the bucket on errors.ubuntu.com where your crash has been grouped with other people experiencing the same problem. You can also get to the launchpad bug from there, if one exists, or tell it to open a new bug. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
OK, I am assuming "That worked" means you found the bug ID(s) your machine is experiencing, and they were not this one :) Per comment #52, if the original reporter does not reply by early February then this bug will be closed due to lack of response. That doesn't mean this bug doesn't exist, just that we need (other) more detailed bug reports with crash information do be able to do anything with them. And those we have many of already. It's just a matter of finding the right crash report(s). -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
If the bug does get closed due to lack of response from the reporter then that actually doesn't stop us commenting here. Everyone please report your own separate bugs for crashes so that we may diagnose and group them more accurately. If you like, please mention the ID of your new bug(s) here. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Everyone please log your own separate bugs for this issue. Because it's not really one issue - it is multiple different gnome-shell crashes. Logging your own bug will help us to figure out exactly which crash you are experiencing and which fix you need. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Everyone please log your own separate bugs for this issue. Because it's not really one issue - it is multiple different gnome-shell crashes. Logging your own bug will help us to figure out exactly which crash you are experiencing and which fix you need. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Craig, in that case please just: 1. Open a bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+filebug 2. Add tag "xwayland" 3. Change it from Public to Private (top right of the page) 4. Attach your crash file to the bug. Normally we do not recommend doing it that way as there's no guarantee we'll be able to decode it by hand. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Everyone please log your own separate bugs for this issue. Because it's not really one issue - it is multiple different gnome-shell crashes. Logging your own bug will help us to figure out exactly which crash you are experiencing and which fix you need. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Bug 1750773 does not seem to exist (!?) -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
** Project changed: nouveau => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Bug closed, due to no response from the original reporter after over 3 months (see comment #52). Everyone else, please keep logging your own bugs if you have any issues. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
I mean: Bug closed, due to no response from the original reporter after over 2 months (see comment #52). Everyone else please keep logging your own bugs if you have any issues. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug is closed. Please log new bugs if you have any issues at all. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
See comments #52 and #64. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
If 'ubuntu-bug' fails for you then please try applying the workaround from bug 994921 first. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug is closed due to no response from the original reporter, so please don't add further comments. Everyone else should: 1. If using a release older than 18.04 then apply the workaround from bug 994921 first. 2. Run: ubuntu-bug /var/crash/YOURFILE.crash -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
BTW, we have fixed many gnome-shell bugs with these symptoms recently in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any problems. -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug is closed due to no response from the original reporter, so please don't add further comments. Everyone else should: 1. If using a release older than 18.04 then apply the workaround from bug 994921 first. 2. Run: ubuntu-bug /var/crash/YOURFILE.crash ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1075774] Re: [MIR] gstreamer-vaapi
We would love for gstreamer-vaapi to be in main and I'm sure Will Cooke agrees. The problem is a legal one, I think in dependency 'libva'. We'd have to check with legal. -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1075774 Title: [MIR] gstreamer-vaapi To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1075774/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1075774] Re: [MIR] gstreamer-vaapi
What we recommend instead is for anyone who wants to use it install 'ubuntu-restricted-addons', either by ticking the appropriate box during installation or just by installing that package after. https://wiki.ubuntu.com/IntelQuickSyncVideo -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1075774 Title: [MIR] gstreamer-vaapi To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1075774/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1075774] Re: [MIR] gstreamer-vaapi
That's probably too harsh. The list of bugs in gstreamer-vaapi itself is quite short: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1075774 Title: [MIR] gstreamer-vaapi To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1075774/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1702558] Re: [MIR] libsoxr
Yes from me. But I will raise it with management too. In fact pulseaudio 12.0 seems to want libsoxr aswell, so this is its only dependency not yet in main. -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1702558 Title: [MIR] libsoxr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1702558] Re: [MIR] libsoxr
What I mean is that Debian's packaging of PulseAudio 12.0-1 includes a dependency on libsoxr-dev. So it would be nice to have libsoxr in main in order to sync with Debian better. See also bug 1574746. -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1702558 Title: [MIR] libsoxr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
** Changed in: gjs (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Ubuntu Desktop (ubuntu-desktop) ** Changed in: gjs (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => Ubuntu Desktop (ubuntu-desktop) -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Technically, being in cosmic-proposed only makes it Fix Committed. Not yet Fix Released. ** Changed in: gjs (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Needs Fixing (3) So all that needs fixing here is removing of "(LP: #1783363)" from the changelog and removing the bug link from this proposal. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Good news! Neither of those two patches have anything to do with bug 1783363 because the bug remains even after I remove both patches. So this branch might be fine to land but has nothing to do with fixing bug 1783363. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Sorry. I forgot apt-get source had patches pre-quilted. Now retesting. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Approve Yes. Verified this branch works. Bug 1783363 is fixed. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Needs Fixing (2) Unfortunately the fix for bug 1783363 isn't working. I have it installed right now and am still trapped in the activities overview. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
(1) It would be a good idea to mention LP: #1747566 and LP: #1653153 respectively next to those patch names in the changelog. Since there are really three relevant bugs here to test for. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Untangling the mess that gui startup has become
Hi Phillip, If "the gnome-shell greeter does not appear to give you any choice in what login session you get" then that means the 'eglnative' back-end (Wayland) crashed on start-up so the Wayland login option gets silently removed. If you wrote that 3 weeks ago and are using 18.10 then I think it may have been this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883 So just update your system and that will be fixed. If it's not fixed and you still don't get any Wayland login option from gdm3 then please log a bug about that by running: ubuntu-bug gdm3 - Daniel On 12/09/18 03:33, Phillip Susi wrote: Resending this after subscribing since after waiting for 3 weeks, no moderator has released it. Things used to be fairly simple. You ran startx, and it followed ~/.xinitrc which directed it to pick a display number and run XFree86 on that display number, configure it to use an XAUTHORITY file, set the environment variables to point to that display and XAUTHORITY file, then run your window manager and shell ( which were actually separate things ). Fast forward 25 years and now it looks like you have a display manager ( gdm3 or lightdm ). It looks like gdm3 looks in /etc/gdm3/custom.conf, where you can tweak things but by default, it doesn't say much and gdm3 defaults to running gdm-x-session, which has no man page. It looks like it is a clone of gnome-session ( why not just use gnome-session? ) It apparently sets up XAUTHORITY and runs Xorg and tells it which display and XAUTHORITY file to use. At this point under lightdm I think there were some config files that direct it to run unity-greeter to prompt you to login, but it looks like gnome-shell is being run on vt1 and it must have a built in greeter function, in addition to being a shell and window manager. After logging in, gdm3 appears to fork gdm-session-worker ( no man page ) on the next unused vt. It runs gnome-session-binary ( whose man page appears to be just gnome-session ). It is directed to set up a specific type of session chosen at the greeter or defaulted, and how to setup these sessions is defined in files in /usr/share/gnome-session/sessions. These files seem to list a bunch of DBUS names so unlike other kinds of session files used by other display managers that just tell them what programs to launch, gnome-session must somehow punt to DBUS to launch them. Though oddly, it appears that gnome-shell is forked from gdm-session-worker rather than the dbus daemon. That is then both your window manager and shell. Now for some reason, the gnome-shell greeter does not appear to give you any choice in what login session you get ( why? ), but lightdm does, so there you can choose to log in using a wayland session, and it goes through an entirely different set of config files that end up directing it to just run gnome-shell, which now besides being a shell and window manager, is also a wayland compositor, replacing Xorg. gnome-shell appears to automatically fork Xwayland, and forgets to setup an XAUTHORITY for it. A few months ago gdm did give you a choice to log in with wayland and iirc from running it and looking at its code, it decided to run gnome-shell and Xwayland. I guess gnome-shell notices if Xwayland was already running and wouldn't fork one itself if so. Do I have that about right and can anyone fill in the missing pieces? -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic-sru3 into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Approve The green stuff looks good to me. I have no opinion on the red parts. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/358010 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic-sru3 into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Also, the fix for bug 1767648 (and hence bug 1779615) is not in disco or cosmic yet(?) -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/361811 Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Also, the fix is not in disco or cosmic(?) -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/361811 Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
You have been requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. diff --git a/debian/changelog b/debian/changelog index 564d95f..c3875a2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +mutter (3.30.2-1~ubuntu18.10.4) UNRELEASED; urgency=medium + + * Add support for high frame rate displays (LP: #1763892): +- Introduce lp1763892-add-hardware-vsync-support.patch +- Drop erroneous clutter-Smooth-out-master-clock-to-smooth-visuals.patch + + -- Daniel van Vugt Fri, 22 Feb 2019 17:42:49 +0800 + mutter (3.30.2-1~ubuntu18.10.3) cosmic; urgency=medium * d/p/clutter-Avoid-rounding-compensation-when-invalidating-2D-.patch, diff --git a/debian/libmutter-3-0.symbols b/debian/libmutter-3-0.symbols index 81ebd76..eb66e84 100644 --- a/debian/libmutter-3-0.symbols +++ b/debian/libmutter-3-0.symbols @@ -699,6 +699,7 @@ libmutter-3.so.0 libmutter-3-0 #MINVER# (arch=linux-any)meta_gpu_kms_can_have_outputs@Base 3.29.92 (arch=linux-any)meta_gpu_kms_flip_closure_container_free@Base 3.29.4 (arch=linux-any)meta_gpu_kms_flip_crtc@Base 3.28.2 + (arch=linux-any)meta_gpu_kms_get_current_time_ns@Base 3.30.2 (arch=linux-any)meta_gpu_kms_get_fd@Base 3.28.2 (arch=linux-any)meta_gpu_kms_get_file_path@Base 3.28.2 (arch=linux-any)meta_gpu_kms_get_max_buffer_size@Base 3.28.2 diff --git a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch b/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch deleted file mode 100644 index 2239837..000 --- a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch +++ /dev/null @@ -1,225 +0,0 @@ -From: Daniel van Vugt -Date: Fri, 16 Feb 2018 02:50:59 -0600 -Subject: clutter: Smooth out master clock to smooth visuals - -Clutter's master clock was jittery because it included errors in cur_tick -such as dispatch delays due to other sources. Dispatch could also occur up -to 1ms early since GSource can only be timed to the millisecond. All of this -could impact the visual smoothness of animations as they are displayed on -the steady interval of the monitor, but spacially moving in less regular -steps derived from the dispatch times. - -The simple fix is to ignore any jitter in dispatch timing. Try a little -bit harder to use a precise interval that will better match the display -hardware, and smoother visuals will follow. - -Bug: https://gitlab.gnome.org/GNOME/mutter/issues/25 -Forwarded: https://gitlab.gnome.org/GNOME/mutter/merge_requests/70 - clutter/clutter/clutter-master-clock-default.c | 134 + - 1 file changed, 93 insertions(+), 41 deletions(-) - -diff --git a/clutter/clutter/clutter-master-clock-default.c b/clutter/clutter/clutter-master-clock-default.c -index 7b2df0d..97b6d13 100644 a/clutter/clutter/clutter-master-clock-default.c -+++ b/clutter/clutter/clutter-master-clock-default.c -@@ -69,8 +69,10 @@ struct _ClutterMasterClockDefault - /* the previous state of the clock, in usecs, used to compute the delta */ - gint64 prev_tick; - -+ /* the ideal frame interval in usecs (inverse of your max refresh rate) */ -+ gint64 frame_interval; -+ - #ifdef CLUTTER_ENABLE_DEBUG -- gint64 frame_budget; - gint64 remaining_budget; - #endif - -@@ -264,6 +266,41 @@ master_clock_reschedule_stage_updates (ClutterMasterClockDefault *master_clock, - } - } - -+static gint64 -+estimate_next_presentation_time (ClutterMasterClockDefault *master_clock) -+{ -+ gint64 frame_phase, now, now_phase, undershoot; -+ -+ /* In future if this was updated from the backend's (maximum) refresh rate -+ * then that would fix: https://bugzilla.gnome.org/show_bug.cgi?id=781296 -+ */ -+ master_clock->frame_interval = G_USEC_PER_SEC / -+ clutter_get_default_frame_rate (); -+ -+ now = g_source_get_time (master_clock->source); -+ now_phase = now % master_clock->frame_interval; -+ -+ /* To be precise we would like to use: -+ * frame_phase = a_recent_hardware_presentation_time % frame_interval; -+ * where hardware_presentation_time must be using the same clock as -+ * g_source_get_time. Unfortunately they're different clocks right now -+ * so we can't. -+ * Alternatively, we could replace g_source_get_time in future with the -+ * current time in the clutter/cogl presentation clock, but that function -+ * also doesn't exist yet. -+ * Until we can get either of those, zero is fine. It just means latency -+ * will be suboptimal by half a frame on average. We still get maximum -+ * smoothness this
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
The proposal to merge ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic has been updated. Description changed to: For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 -- Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. Commit message: Remove 60 FPS limitation, thus supporting high frame rates For Xorg the only fix required was to remove the spurious patch: clutter-Smooth-out-master-clock-to-smooth-visuals.patch which had the effect of imposing a secondary 60 FPS limitation. That patch never landed upstream. For Wayland you need both the above fix, and the introduction of hardware vsync support which was upstreamed in mutter 3.32 and is backported to 3.30 in the new patch: lp1763892-add-hardware-vsync-support.patch https://bugs.launchpad.net/bugs/1763892 Requested reviews: Ubuntu Server Dev import team (usd-import-team) For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 *** Launchpad is refusing to display a diff right now. But you can still view it by clicking on the last commit ID. -- Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. diff --git a/debian/changelog b/debian/changelog index 564d95f..c3875a2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +mutter (3.30.2-1~ubuntu18.10.4) UNRELEASED; urgency=medium + + * Add support for high frame rate displays (LP: #1763892): +- Introduce lp1763892-add-hardware-vsync-support.patch +- Drop erroneous clutter-Smooth-out-master-clock-to-smooth-visuals.patch + + -- Daniel van Vugt Fri, 22 Feb 2019 17:42:49 +0800 + mutter (3.30.2-1~ubuntu18.10.3) cosmic; urgency=medium * d/p/clutter-Avoid-rounding-compensation-when-invalidating-2D-.patch, diff --git a/debian/libmutter-3-0.symbols b/debian/libmutter-3-0.symbols index 81ebd76..eb66e84 100644 --- a/debian/libmutter-3-0.symbols +++ b/debian/libmutter-3-0.symbols @@ -699,6 +699,7 @@ libmutter-3.so.0 libmutter-3-0 #MINVER# (arch=linux-any)meta_gpu_kms_can_have_outputs@Base 3.29.92 (arch=linux-any)meta_gpu_kms_flip_closure_container_free@Base 3.29.4 (arch=linux-any)meta_gpu_kms_flip_crtc@Base 3.28.2 + (arch=linux-any)meta_gpu_kms_get_current_time_ns@Base 3.30.2 (arch=linux-any)meta_gpu_kms_get_fd@Base 3.28.2 (arch=linux-any)meta_gpu_kms_get_file_path@Base 3.28.2 (arch=linux-any)meta_gpu_kms_get_max_buffer_size@Base 3.28.2 diff --git a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch b/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch deleted file mode 100644 index 2239837..000 --- a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch +++ /dev/null @@ -1,225 +0,0 @@ -From: Daniel van Vugt -Date: Fri, 16 Feb 2018 02:50:59 -0600 -Subject: clutter: Smooth out master clock to smooth visuals - -Clutter's master clock was jittery because it included errors in cur_tick -such as dispatch delays due to other sources. Dispatch could also occur up -to 1ms early since GSource can only be timed to the millisecond. All of this -could impact the visual smoothness of animations as they are displayed on -the steady interval of the monitor, but spacially moving in less regular -steps derived from the dispatch times. - -The simple fix is to ignore any jitter in dispatch timing. Try a little -bit harder to use a precise interval that will better match the display -hardware, and smoother visuals will follow. - -Bug: https://gitlab.gnome.org/GNOME/mutter/issues/25 -Forwarded: https://gitlab.gnome.org/GNOME/mutter/merge_requests/70 - clutter/clutter/clutter-master-clock-default.c | 134 + - 1 file changed, 93 insertions(+), 41 deletions(-) - -diff --git a/clutter/clutter/clutter-master-clock-default.c b/clutter/clutter/clutter-master-clock-default.c -index 7b2df0d..97b6d13 100644 a/clutter/clutter/clutter-master-clock-default.c -+++ b/clutter/clutter/clutter-master-clock-default.c -@@ -69,8 +69,10 @@ struct _ClutterMasterClockDefault - /* the previous state of the clock, in usecs, used to compute the delta */ - gint64 prev_tick; - -+ /* the ideal frame interval in usecs (inverse of your max refresh rate) */ -+ gint64 frame_interval; -+ - #ifdef CLUTTER_ENABLE_DEBUG -- gint64 frame_budget; - gint64 remaining_budget; - #endif - -@@ -264,6 +266,41 @@ master_clock_reschedule_stage_updates (ClutterMasterClockDefault *master_clock, - } - } - -+static gint64 -+estimate_next_presentation_time (ClutterMasterClockDefault *master_clock) -+{ -+ gint64 frame_phase, now, now_phase, undershoot; -+ -+ /* In future if this was updated from the backend's (maximum) refresh rate -+ * then that would fix: https://bugzilla.gnome.org/show_bug.cgi?id=781296 -+ */ -+ master_clock->frame_interval = G_USEC_PER_SEC / -+ clutter_get_default_frame_rate (); -+ -+ now = g_source_get_time (master_clock->source); -+ now_phase = now % master_clock->frame_interval; -+ -+ /* To be precise w
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
The proposal to merge ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic has been updated. Description changed to: For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 -- Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
The proposal to merge ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic has been updated. Commit message changed to: Remove 60 FPS limitation, thus supporting high frame rates For Xorg the only fix required was to remove the spurious patch: clutter-Smooth-out-master-clock-to-smooth-visuals.patch which had the effect of imposing a 60 FPS limitation. That patch never landed upstream. For Wayland you need both the above fix and the introduction of hardware vsync support which was upstreamed in mutter 3.32 and is backported to 3.30 in two commits/patches: lp1763892-a-renderer-native-Add-hardware-presentation-timing.patch lp1763892-b-renderer-native-Advertise-_FEATURE_SWAP_THROTTLE.patch https://bugs.launchpad.net/bugs/1763892 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 -- Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-cosmic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic
All done. (?) -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/cosmic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/gnome-shell:fix-lp1813119-disco into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/gnome-shell:fix-lp1813119-disco into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. Commit message: Update ubuntu/background_login.patch to match disco theme Fixes LP: #1813119 Requested reviews: Ubuntu Desktop (ubuntu-desktop) Related bugs: Bug #1813119 in gnome-shell (Ubuntu): "In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813119 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/363831 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/gnome-shell:fix-lp1813119-disco into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. diff --git a/debian/changelog b/debian/changelog index 0934982..c208428 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +gnome-shell (3.31.90-1ubuntu2) UNRELEASED; urgency=medium + + * Update ubuntu/background_login.patch to match the new login screen +(system background) design from Yaru for a smooth login animation +(LP: #1813119). + + -- Daniel van Vugt Fri, 01 Mar 2019 16:09:30 +0800 + gnome-shell (3.31.90-1ubuntu1) disco; urgency=medium [ Marco Trevisan (Treviño) ] diff --git a/debian/patches/ubuntu/background_login.patch b/debian/patches/ubuntu/background_login.patch index 6f85511..4f509b8 100644 --- a/debian/patches/ubuntu/background_login.patch +++ b/debian/patches/ubuntu/background_login.patch @@ -1,21 +1,17 @@ -From: Didier Roche -Date: Wed, 20 Jun 2018 19:22:06 +0200 -Subject: Change default background color based on session. - -We changed default GDM color for our ubuntu session. Change it as well here -to match Yaru GDM background. -This screen is appearing for a slip second when the Shell is loading. +Description: js/ui/background.js: Use Ubuntu purple to match login screen + This way the login animation will appear to expand over the login + screen (system background) instead of suddenly replacing it. +Original author: Didier Roche +Author: Daniel van Vugt +Bug-Ubuntu: https://launchpad.net/bugs/1813119 +Last-Update: 2019-03-01 Forwarded: not-needed -=== - js/ui/background.js | 21 + - 1 file changed, 21 insertions(+) -diff --git a/js/ui/background.js b/js/ui/background.js -index 874bda3..0a4e9ad 100644 a/js/ui/background.js -+++ b/js/ui/background.js -@@ -101,6 +101,7 @@ const GnomeDesktop = imports.gi.GnomeDesktop; +Index: gnome-shell/js/ui/background.js +=== +--- gnome-shell.orig/js/ui/background.js gnome-shell/js/ui/background.js +@@ -101,6 +101,7 @@ const GnomeDesktop = imports.gi.GnomeDes const Meta = imports.gi.Meta; const Signals = imports.signals; @@ -23,7 +19,7 @@ index 874bda3..0a4e9ad 100644 const LoginManager = imports.misc.loginManager; const Main = imports.ui.main; const Params = imports.misc.params; -@@ -489,6 +490,26 @@ let _systemBackground; +@@ -489,6 +490,25 @@ let _systemBackground; var SystemBackground = class SystemBackground { constructor() { @@ -31,9 +27,8 @@ index 874bda3..0a4e9ad 100644 +if (Desktop.is("ubuntu")) { +if (_systemBackground == null) { +_systemBackground = new Meta.Background({ meta_display: global.display }); -+let [, topColor] = Clutter.Color.from_string('#6D2169'); -+let [, bottomColor] = Clutter.Color.from_string('#370026'); -+_systemBackground.set_gradient(GDesktopEnums.BackgroundShading.VERTICAL, topColor, bottomColor); ++let [, ubuntuColor] = Clutter.Color.from_string('#2C001E'); ++_systemBackground.set_color(ubuntuColor); +} +this.actor = new Meta.BackgroundActor({ meta_display: global.display, +monitor: 0, -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. Commit message: Remove 60 FPS limitation, thus supporting high frame rates For Xorg the only fix required was to remove the spurious patch: clutter-Smooth-out-master-clock-to-smooth-visuals.patch which had the effect of imposing a 60 FPS limitation. That patch never landed upstream. For Wayland you need both the above fix and the introduction of hardware vsync support which was upstreamed in mutter 3.32 and is backported to 3.28 in two commits/patches: lp1763892-a-renderer-native-Add-hardware-presentation-timing.patch lp1763892-b-renderer-native-Advertise-_FEATURE_SWAP_THROTTLE.patch https://bugs.launchpad.net/bugs/1763892 Requested reviews: Ubuntu Desktop (ubuntu-desktop) Related bugs: Bug #1763892 in mutter (Ubuntu): "144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. diff --git a/debian/changelog b/debian/changelog index 9044a2f..15cbb38 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mutter (3.28.3+git20190124-0ubuntu18.04.2) UNRELEASED; urgency=medium + + * Add support for high frame rate displays (LP: #1763892): +- Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch +- Add lp1763892-a-renderer-native-Add-hardware-presentation-timing.patch +- Add lp1763892-b-renderer-native-Advertise-_FEATURE_SWAP_THROTTLE.patch + + -- Daniel van Vugt Wed, 13 Mar 2019 15:34:01 +0800 + mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 diff --git a/debian/libmutter-2-0.symbols b/debian/libmutter-2-0.symbols index 1489074..d64bcdb 100644 --- a/debian/libmutter-2-0.symbols +++ b/debian/libmutter-2-0.symbols @@ -549,6 +549,7 @@ libmutter-2.so.0 libmutter-2-0 #MINVER# meta_gpu_kms_error_quark@Base 3.28.2 meta_gpu_kms_flip_closure_container_free@Base 3.28.3+git20190124 meta_gpu_kms_flip_crtc@Base 3.28.2 + meta_gpu_kms_get_current_time_ns@Base 3.28.3+git20190124-0ubuntu18.04.2 meta_gpu_kms_get_fd@Base 3.28.2 meta_gpu_kms_get_file_path@Base 3.28.2 meta_gpu_kms_get_max_buffer_size@Base 3.28.2 diff --git a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch b/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch deleted file mode 100644 index 2239837..000 --- a/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch +++ /dev/null @@ -1,225 +0,0 @@ -From: Daniel van Vugt -Date: Fri, 16 Feb 2018 02:50:59 -0600 -Subject: clutter: Smooth out master clock to smooth visuals - -Clutter's master clock was jittery because it included errors in cur_tick -such as dispatch delays due to other sources. Dispatch could also occur up -to 1ms early since GSource can only be timed to the millisecond. All of this -could impact the visual smoothness of animations as they are displayed on -the steady interval of the monitor, but spacially moving in less regular -steps derived from the dispatch times. - -The simple fix is to ignore any jitter in dispatch timing. Try a little -bit harder to use a precise interval that will better match the display -hardware, and smoother visuals will follow. - -Bug: https://gitlab.gnome.org/GNOME/mutter/issues/25 -Forwarded: https://gitlab.gnome.org/GNOME/mutter/merge_requests/70 - clutter/clutter/clutter-master-clock-default.c | 134 + - 1 file changed, 93 insertions(+), 41 deletions(-) - -diff --git a/clutter/clutter/clutter-master-clock-default.c b/clutter/clutter/clutter-master-clock-default.c -index 7b2df0d..97b6d13 100644 a/clutter/clutter/clutter-master-clock-default.c -+++ b/clutter/clutter/clutter-master-clock-default.c -@@ -69,8 +69,10 @@ struct _ClutterMasterClockDefault - /* the previous state of the clock, in usecs, used to compute the delta */ - gint64 prev_tick; - -+ /* the ideal frame interval in usecs (inverse of your max refresh rate) */ -+ gint64 frame_interval; -+ - #ifdef CLUTTER_ENABLE_DEBUG -- gint64 frame_budget; - gint64 remaining_budget; - #endif - -@@ -264,6 +266,41 @@ master_clock_reschedule_stage_updates (ClutterMasterClockDefault *master_clock, - } - } - -+static gint64 -+estimate_next_presentation_time (ClutterMasterClockDefault *master_clock) -+{ -+ gint64 frame_phase, now, now_phase, undershoot; -+ -+ /* In future if this was updated from the backend's (maximum) refresh rate -+ * then that would fix: https://bugzilla.gnome.org/show_bug.cgi?id=781296 -+ */ -+ master_c
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
It looks like this might be held up because the previous version is held up (bug 1811900) -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Approve Sounds and looks sensible. Although it's never easy to read the diff-of-a-diff, the fact that the patch is shrinking is also good. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/xrandr-scaling into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Needs Fixing The fix for bug 1822616 isn't working yet, at least: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/comments/11 -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365624 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/xrandr-scaling into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/xrandr-scaling into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Approve Looks OK, but of course it's too hard to be sure. I don't really know this area of code. Notes: (1) The fix for bug 1822616 looks good now. (2) Upstream will (eventually) ask you to reformat function parameters to be one parameter per line. Remember to do that (some time). (3) Another formatting nit: Indentation in apply_crtc_assignments -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365624 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/xrandr-scaling into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Abstain Aside from the size, I'm not familiar with any of the changes here. But I know we're also in a hurry. So maybe land it ASAP and defer to manual testing instead of a code review. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/365834 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Diff 18486 lines (+4062/-3431) Are you sure that's correct? Got the right branch? -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/365834 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Approve Looks like what I was expecting... -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365833 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Needs Fixing Listing things that this release does not change and calling them "changes" is a bit confusing. Maybe don't list such things... +mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium + + * Merge with debian git snapshot (LP: #1820542), remaining changes: ++ debian/control: + - Update VCS flags to point to launchpad + - Update maintainer to ubuntu ++ debian/gbp.conf: update branch to point to ubuntu/master ++ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + - X11: Add support for fractional scaling using Randr -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365833 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Needs Fixing Although... Listing things we didn't change is very confusing. Maybe don't do that: changelog: +gnome-shell (3.32.0+git20190410-1ubuntu1) disco; urgency=medium + + * Merging with debian git snapshot (LP: #1820775, LP: #1818790), +remaining changes: ... + all of these ... -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/365834 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1810316] Re: gnome-control-center SIGABRT when network-manager is not working (G_IS_OBJECT (object))
** Summary changed: - gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) + gnome-control-center SIGABRT when network-manager is not working (G_IS_OBJECT (object)) ** Summary changed: - gnome-control-center SIGABRT when network-manager is not working (G_IS_OBJECT (object)) + gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object] -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1810316 Title: gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Status should be "Merged" now. It looks like it's already merged. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Approve Looks reasonable. Only one note: (1) The change to clutter/clutter/clutter-device-manager.c is out of date already (missing https://gitlab.gnome.org/GNOME/mutter/merge_requests/552). So there is a slight risk without that second part. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/36 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Conflict fixed. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
I guess there are probably conflicts here now. Although LP isn't saying so. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master
Review: Approve I'm not directly familiar with recent changes to gnome-shell 3.32.1. It looks reasonable, except: (1) Again I recommend not including the large section in changelog entries detailing what hasn't changed ("remaining changes:") because it is misleading to document in detail things that are not part of the update. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/38 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/master into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Diff comments: > diff --git a/debian/libmutter-2-0.symbols b/debian/libmutter-2-0.symbols > index 1489074..89b3d01 100644 > --- a/debian/libmutter-2-0.symbols > +++ b/debian/libmutter-2-0.symbols > @@ -549,6 +549,7 @@ libmutter-2.so.0 libmutter-2-0 #MINVER# > meta_gpu_kms_error_quark@Base 3.28.2 > meta_gpu_kms_flip_closure_container_free@Base 3.28.3+git20190124 > meta_gpu_kms_flip_crtc@Base 3.28.2 > + meta_gpu_kms_get_current_time_ns@Base 3.28.3+git20190124-0ubuntu18.04.3 The symbol is used. It is critical. I would not have included it otherwise. P.S. Laney requested that specific symbol version. > meta_gpu_kms_get_fd@Base 3.28.2 > meta_gpu_kms_get_file_path@Base 3.28.2 > meta_gpu_kms_get_max_buffer_size@Base 3.28.2 -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Diff comments: > diff --git a/debian/libmutter-2-0.symbols b/debian/libmutter-2-0.symbols > index 1489074..89b3d01 100644 > --- a/debian/libmutter-2-0.symbols > +++ b/debian/libmutter-2-0.symbols > @@ -549,6 +549,7 @@ libmutter-2.so.0 libmutter-2-0 #MINVER# > meta_gpu_kms_error_quark@Base 3.28.2 > meta_gpu_kms_flip_closure_container_free@Base 3.28.3+git20190124 > meta_gpu_kms_flip_crtc@Base 3.28.2 > + meta_gpu_kms_get_current_time_ns@Base 3.28.3+git20190124-0ubuntu18.04.3 Simply not mentioning the symbol in libmutter-2-0.symbols doesn't work (from memory). The build automatically exports it and adds it to the final .symbols file. > meta_gpu_kms_get_fd@Base 3.28.2 > meta_gpu_kms_get_file_path@Base 3.28.2 > meta_gpu_kms_get_max_buffer_size@Base 3.28.2 -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Approve OK then. I can confirm that last commit 78e6f42 looks correct and is what I expected. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Sorry I keep forgetting to save my inline comments. This is from a few hours ago... Diff comments: > diff --git a/debian/libmutter-2-0.symbols b/debian/libmutter-2-0.symbols > index 1489074..89b3d01 100644 > --- a/debian/libmutter-2-0.symbols > +++ b/debian/libmutter-2-0.symbols > @@ -549,6 +549,7 @@ libmutter-2.so.0 libmutter-2-0 #MINVER# > meta_gpu_kms_error_quark@Base 3.28.2 > meta_gpu_kms_flip_closure_container_free@Base 3.28.3+git20190124 > meta_gpu_kms_flip_crtc@Base 3.28.2 > + meta_gpu_kms_get_current_time_ns@Base 3.28.3+git20190124-0ubuntu18.04.3 The reason it is public seems to be because it is shared between different source files. I see your point about a '_' prefix but I don't think it's appropriate to go making any such design changes here since the existing form is already in disco and cosmic. > meta_gpu_kms_get_fd@Base 3.28.2 > meta_gpu_kms_get_file_path@Base 3.28.2 > meta_gpu_kms_get_max_buffer_size@Base 3.28.2 -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Diff comments: > diff --git a/debian/libmutter-2-0.symbols b/debian/libmutter-2-0.symbols > index 1489074..89b3d01 100644 > --- a/debian/libmutter-2-0.symbols > +++ b/debian/libmutter-2-0.symbols > @@ -549,6 +549,7 @@ libmutter-2.so.0 libmutter-2-0 #MINVER# > meta_gpu_kms_error_quark@Base 3.28.2 > meta_gpu_kms_flip_closure_container_free@Base 3.28.3+git20190124 > meta_gpu_kms_flip_crtc@Base 3.28.2 > + meta_gpu_kms_get_current_time_ns@Base 3.28.3+git20190124-0ubuntu18.04.3 >From memory, the change to libmutter-2-0.symbols was not by choice. It was to >silence a lintian warning. If you know how to unexport the symbol via *.symbols (not changing patches compared to what's already released) and keep lintian happy then I am happy to do so. > meta_gpu_kms_get_fd@Base 3.28.2 > meta_gpu_kms_get_file_path@Base 3.28.2 > meta_gpu_kms_get_max_buffer_size@Base 3.28.2 -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Review: Approve Looking good. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/366676 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Approve -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
The proposal to merge ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic has been updated. Status: Needs review => Work in progress For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
That last commit also looks good. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
OK then. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Hmm, I don't see any close or reject option (any more). I can only delete the MP. So I will wait for the above to land first and then will permanently delete this one. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1763892-bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Approve Oops. Too late. This already merged. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Approve Once again, I was planning on proposing this today. But thanks for beating me to it. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/367149 Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic
Review: Needs Fixing Sorry, please also grab https://gitlab.gnome.org/GNOME/gnome-shell/commit/8702d66 to fix LP: #1827284 -- https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/gnome-shell:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/gnome-shell:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: PPA for Ubuntu 19.04 please.
Hi Pranav, Please clarify what PPA you are talking about, and specifically what bug fix you need. - Daniel On 16/5/19 12:40 am, Pranav bhattarai wrote: Its been a month since the latest stable release. And we need stable PPA ASAP. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
It looks like this has landed. Please close this MP. -- https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/366676 Your team Ubuntu Desktop is requested to review the proposed merge of ~3v1n0/ubuntu/+source/mutter:ubuntu/bionic into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. Commit message: Fix wallpaper corruption on resume from suspend on Nvidia https://bugs.launchpad.net/bugs/1809407 Requested reviews: Ubuntu Desktop (ubuntu-desktop) Related bugs: Bug #1809407 in mutter (Ubuntu): "[nvidia] Corrupted wallpaper after resuming from suspend" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. diff --git a/debian/changelog b/debian/changelog index dd565d9..2c7c657 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +mutter (3.32.2-1ubuntu2) eoan; urgency=medium + + * Add fix-lp1809407-3.32.patch to fix background wallpaper corruption on +Nvidia when resuming from suspend (LP: #1809407) + + -- Daniel van Vugt Fri, 07 Jun 2019 18:01:23 +0800 + mutter (3.32.2-1ubuntu1) eoan; urgency=medium * Merge with debian. Remaining changes: diff --git a/debian/patches/fix-lp1809407-3.32.patch b/debian/patches/fix-lp1809407-3.32.patch new file mode 100644 index 000..ef3177b --- /dev/null +++ b/debian/patches/fix-lp1809407-3.32.patch @@ -0,0 +1,234 @@ +Description: Refresh desktop wallpaper upon resume from suspend + The Nvidia driver loses/corrupts its texture memory upon resuming from + suspend. This is a *feature* that is officially documented in OpenGL + extension "NV_robustness_video_memory_purge". To accomodate this we need + to refresh textures kept long-term in GPU memory, most noticeably the + desktop wallpaper and clutter canvases like the rounded panel corners + (if enabled). +Author: Daniel van Vugt +Origin: https://gitlab.gnome.org/GNOME/mutter/merge_requests/600 +Bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084 +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1809407 +Forwarded: yes +Last-Update: 2019-06-07 + +diff --git a/clutter/clutter/clutter-canvas.c b/clutter/clutter/clutter-canvas.c +index b0f1f080c..e7b8de87e 100644 +--- a/clutter/clutter/clutter-canvas.c b/clutter/clutter/clutter-canvas.c +@@ -76,6 +76,8 @@ struct _ClutterCanvasPrivate + gboolean dirty; + + CoglBitmap *buffer; ++ ++ ClutterStage *stage; + }; + + enum +@@ -129,6 +131,14 @@ clutter_cairo_context_draw_marshaller (GClosure *closure, + cairo_restore (cr); + } + ++static void ++clutter_canvas_dispose (GObject *gobject) ++{ ++ ClutterCanvasPrivate *priv = CLUTTER_CANVAS (gobject)->priv; ++ ++ g_clear_object (&priv->stage); ++} ++ + static void + clutter_canvas_finalize (GObject *gobject) + { +@@ -312,6 +322,7 @@ clutter_canvas_class_init (ClutterCanvasClass *klass) + + gobject_class->set_property = clutter_canvas_set_property; + gobject_class->get_property = clutter_canvas_get_property; ++ gobject_class->dispose = clutter_canvas_dispose; + gobject_class->finalize = clutter_canvas_finalize; + + g_object_class_install_properties (gobject_class, LAST_PROP, obj_props); +@@ -327,6 +338,12 @@ clutter_canvas_init (ClutterCanvas *self) + self->priv->scale_factor = 1.0f; + } + ++static void ++clutter_canvas_video_memory_purged (ClutterCanvas *self) ++{ ++ clutter_content_invalidate (CLUTTER_CONTENT (self)); ++} ++ + static void + clutter_canvas_paint_content (ClutterContent *content, + ClutterActor *actor, +@@ -335,6 +352,7 @@ clutter_canvas_paint_content (ClutterContent *content, + ClutterCanvas *self = CLUTTER_CANVAS (content); + ClutterCanvasPrivate *priv = self->priv; + ClutterPaintNode *node; ++ ClutterActor *stage; + + if (priv->buffer == NULL) + return; +@@ -356,6 +374,17 @@ clutter_canvas_paint_content (ClutterContent *content, + clutter_paint_node_unref (node); + + priv->dirty = FALSE; ++ ++ stage = clutter_actor_get_stage (actor); ++ if (stage != (ClutterActor *) priv->stage) ++{ ++ g_set_object (&priv->stage, CLUTTER_STAGE (stage)); ++ ++ g_signal_connect_object (stage, "gl-video-memory-purged", ++ G_CALLBACK (clutter_canvas_video_memory_purged), ++ self, ++ G_CONNECT_SWAPPED); ++} + } + + static void +diff --git a/clutter/clutter/clutter-stage.c b/clutter/clutter/clutter-stage.c +index 1eea5b305..a83d27b65 100644 +--- a/clutter/clutter/clutter-stage.c b/clutter/clutter/clutter-stage.c +@@ -192,6 +192,7 @@ enum + DELETE_EVENT, + AFTER_PAINT, + PRESENTED, ++ GL_VIDEO_MEMORY_PURGED, + + LAST_SIGNAL + }; +@@ -2268,6 +2269,22 @@ clutter_stage_class_init (ClutterStageClass *klass) + G_TYPE_NONE, 2, +
[Merge] ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master. Commit message: Remove revert_nvidia_wayland_blacklist.patch That patch was completely removing the upstream fix for LP: #1705369. The bug which the patch was meant to solve doesn't seem to exist any more, and even if it did it is lower priority affecting 1 person vs 52 people. Now Nvidia desktops with multiple GPUs get a working login screen. Closes: https://bugs.launchpad.net/bugs/1705369 Requested reviews: Didier Roche (didrocks) Ubuntu Desktop (ubuntu-desktop) Related bugs: Bug #1705369 in gnome-shell (Ubuntu): "Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/gdm3/+git/gdm3/+merge/369024 Separately I am also pursuing a fix to mutter!625 upstream. If that fix lands then this one won't be required. Although it doesn't hurt if both land... -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master. diff --git a/debian/changelog b/debian/changelog index 6f83e1c..381eb51 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +gdm3 (3.32.0-1ubuntu2) eoan; urgency=medium + + * Remove revert_nvidia_wayland_blacklist.patch because it was causing a +much greater problem (LP: #1705369) than it was meant to solve (which +doesn't seem to exist any more either). + + -- Daniel van Vugt Wed, 19 Jun 2019 15:47:11 +0800 + gdm3 (3.32.0-1ubuntu1) disco; urgency=medium * Merge with Debian. Remaining changes: diff --git a/debian/patches/series b/debian/patches/series index bdcdb4c..6055234 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -12,5 +12,4 @@ ubuntu/revert_override_LANG_with_accountservices.patch ubuntu/config_error_dialog.patch ubuntu/dont_set_language_env.patch ubuntu/prefer_ubuntu_session_fallback.patch -ubuntu/revert_nvidia_wayland_blacklist.patch ubuntu/gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch diff --git a/debian/patches/ubuntu/revert_nvidia_wayland_blacklist.patch b/debian/patches/ubuntu/revert_nvidia_wayland_blacklist.patch deleted file mode 100644 index 3f95c1d..000 --- a/debian/patches/ubuntu/revert_nvidia_wayland_blacklist.patch +++ /dev/null @@ -1,27 +0,0 @@ -From: Didier Roche -Date: Thu, 11 Oct 2018 17:45:57 +0100 -Subject: Revert nvidia from wayland blacklist - -With some nvidia hardware using binary driver, if gdm GNOME Shell -instance is running under Xorg, after logged in, turn into an infinite -restart CPU loop, spiking processor usage to 100%. -This is due to an invalid paint context. -As on ubuntu, our main user session is using Xorg, having GDM using -Wayland is fine, as checked with usptream. So, we can revert nvidia from -the blacklist for now. -Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797355 -Bug: https://gitlab.gnome.org/GNOME/gdm/issues/429 - data/61-gdm.rules.in | 2 -- - 1 file changed, 2 deletions(-) - -diff --git a/data/61-gdm.rules.in b/data/61-gdm.rules.in -index ad5b87d..c9f6110 100644 a/data/61-gdm.rules.in -+++ b/data/61-gdm.rules.in -@@ -2,5 +2,3 @@ - ATTR{vendor}=="0x1013", ATTR{device}=="0x00b8", ATTR{subsystem_vendor}=="0x1af4", ATTR{subsystem_device}=="0x1100", RUN+="@libexecdir@/gdm-disable-wayland" - # disable Wayland on Hi1710 chipsets - ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="@libexecdir@/gdm-disable-wayland" --# disable Wayland when using the proprietary nvidia driver --DRIVER=="nvidia", RUN+="@libexecdir@/gdm-disable-wayland" -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Daniel van Vugt has proposed merging ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. Commit message: Add lp1832138-workaround-old-vmwgfx.patch To work around old versions of the vmwgfx kernel driver that could result in the screen freezing immediately on startup. (LP: #1832138) Requested reviews: Ubuntu Desktop (ubuntu-desktop) Related bugs: Bug #1832138 in linux (Ubuntu): "Login screen never appears on vmwgfx using bionic kernel 4.15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. diff --git a/debian/changelog b/debian/changelog index 62c0624..e850e64 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +mutter (3.28.4-0ubuntu18.04.2) bionic; urgency=medium + + * Add lp1832138-workaround-old-vmwgfx.patch to work around old versions +of the vmwgfx kernel driver that could result in the screen freezing +immediately on startup. (LP: #1832138) + + -- Daniel van Vugt Thu, 20 Jun 2019 17:32:53 +0800 + mutter (3.28.4-0ubuntu18.04.1) bionic; urgency=medium * New upstream release: diff --git a/debian/patches/lp1832138-workaround-old-vmwgfx.patch b/debian/patches/lp1832138-workaround-old-vmwgfx.patch new file mode 100644 index 000..0fde5c5 --- /dev/null +++ b/debian/patches/lp1832138-workaround-old-vmwgfx.patch @@ -0,0 +1,25 @@ +Description: renderer-native: Work around broken timing in old vmwgfx + The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using + the wrong clock. This would lead us to wait forever (or at least 49 years) + before rendering the next frame. There's no decisive way to know this kernel + bug is going to happen before it does so just detect timestamps which are + obviously going to cause freezes and ignore them. +Author: Daniel van Vugt +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1832138 +Forwarded: not-needed +Last-Update: 2019-06-20 + +--- a/src/backends/native/meta-renderer-native.c b/src/backends/native/meta-renderer-native.c +@@ -1185,6 +1185,11 @@ on_crtc_flipped (GClosure *closure, +*/ + if (refresh_rate >= frame_info->refresh_rate) + { ++ int64_t drm_now = _meta_gpu_kms_get_current_time_ns (gpu_kms); ++ ++ if (page_flip_time_ns > (drm_now + 10L)) ++page_flip_time_ns = 0; ++ + frame_info->presentation_time = page_flip_time_ns; + frame_info->refresh_rate = refresh_rate; + } diff --git a/debian/patches/series b/debian/patches/series index 5bf1aa6..6c4463e 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -6,6 +6,7 @@ monitor-manager-use-MonitorsConfig-to-track-switch_config.patch monitor-manager-Don-t-use-switch-config-when-ensuring-con.patch lp1763892-a-renderer-native-Add-hardware-presentation-timing.patch lp1763892-b-renderer-native-Advertise-_FEATURE_SWAP_THROTTLE.patch +lp1832138-workaround-old-vmwgfx.patch debian/synaptics-support.patch debian/skip-failing-tests.patch debian/skip-failing-tests-325.patch -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master
The proposal to merge ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master has been updated. Commit message changed to: Remove revert_nvidia_wayland_blacklist.patch That patch was removing the upstream fix for LP: #1705369. And the bug which the patch was meant to solve doesn't seem to exist any more. If it did still exist then it should probably be solved in a different way anyway. Now Nvidia desktops with multiple GPUs get a working login screen. Closes: https://bugs.launchpad.net/bugs/1705369 For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/gdm3/+git/gdm3/+merge/369024 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/gdm3:fix-lp1705369-eoan into ~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
Hmm, in bug 1832138 it now sounds like we might get a kernel fix instead. If so then this workaround can be dropped. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
The fix is for bionic because the bug only exists in kernels older than 4.17. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
The proposal to merge ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic has been updated. Status: Needs review => Work in progress For more details, see: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 -- Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
There are now stylistic changes being made upstream. Nothing of substance though so I probably wouldn't bother reflecting them here. This merge proposal exists to avoid being blocked waiting for upstream. If we are now waiting for upstream then I would more likely close this and just wait for the upstream fix to land via mutter 3.33/3.34 into eoan. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-lp1832138 into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic
"was fixed" is partially correct. The fix has been proposed to the bionic kernel but is not yet Fix Released. My plan was to delete this MP as soon as the kernel fix is released proper. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 Your team Ubuntu Desktop is subscribed to branch ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/bionic. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Forget this MP. A simpler version has now landed in mutter master, so we'll get the fix from there. -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
I would like to reject this instead of deleting it, so we retain history. But Launchpad gives me no Reject option. Can someone else? -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Merge] ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master
Review: Disapprove -- https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536 Your team Ubuntu Desktop is requested to review the proposed merge of ~vanvugt/ubuntu/+source/mutter:fix-1809407-eoan into ~ubuntu-desktop/ubuntu/+source/mutter:ubuntu/master. -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop