[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
** Changed in: evolution (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964922] Re: evolution crashed with SIGSEGV
** Description changed: - and it's not possible to write an E-Mail with evolution. Typing in Text - is not possible. + Impact + --- + The new/edit email dialog in Evolution crashes the app when it is closed. + + Test Case + - + Install the update + Open the Settings app. Click the About button at the bottom of the left sidebar (you may need to scroll down to see it). Verify that the Windowing System is Wayland. + Open Evolution. + Click the New Email button. + Add some text to the draft email. + Close the dialog. + Choose Discard. + The edit email window should close but Evolution should remain open. + + Regression Potential + + One line fix to stop a really annoying crash by disabling hardware acceleration. + + The webkitgtk and Ubuntu Desktop developers suspect that switching + webkit2gtk to build with the wpebackend will avoid this crash, but it + requires main inclusion for additional libraries. The main inclusion + will be worked on over the next few months. + + Original Bug Report + --- + and it's not possible to write an E-Mail with evolution. Typing in Text is not possible. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: evolution 3.43.3-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 11:17:02 2022 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2022-01-21 (52 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) ProcCmdline: evolution ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fb628e6edb6:mov(%rdi),%rax - PC (0x7fb628e6edb6) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fb628e6edb6:mov(%rdi),%rax + PC (0x7fb628e6edb6) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: - ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 - ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 - ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 - ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 - ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 + ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 + ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 + ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 + ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 + ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 Title: evolution crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Description changed: Impact --- The new/edit email dialog in Evolution crashes the app when it is closed. Test Case - Install the update Open the Settings app. Click the About button at the bottom of the left sidebar (you may need to scroll down to see it). Verify that the Windowing System is Wayland. Open Evolution. Click the New Email button. Add some text to the draft email. Close the dialog. Choose Discard. The edit email window should close but Evolution should remain open. Regression Potential One line fix to stop a really annoying crash by disabling hardware acceleration. The webkitgtk and Ubuntu Desktop developers suspect that switching webkit2gtk to build with the wpebackend will avoid this crash, but it requires main inclusion for additional libraries. The main inclusion will be worked on over the next few months. + + Related Bug + --- + See also https://launchpad.net/bugs/1969584 Original Bug Report --- and it's not possible to write an E-Mail with evolution. Typing in Text is not possible. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: evolution 3.43.3-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 11:17:02 2022 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2022-01-21 (52 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) ProcCmdline: evolution ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
** Description changed: - This is very similar to bug #1966418, but only concerns the email edit - window. + Impact + --- + The new/edit email dialog in Evolution crashes the app when it is closed. + + Test Case + - + Install the update + Open the Settings app. Click the About button at the bottom of the left sidebar (you may need to scroll down to see it). Verify that the Windowing System is Wayland. + Open Evolution. + Click the New Email button. + Add some text to the body section of the draft email. + The text should be visible. + Close the dialog. + Choose Discard. + The edit email window should close but Evolution should remain open. + + Regression Potential + + One line fix to stop a really annoying crash by disabling hardware acceleration. + + The webkitgtk and Ubuntu Desktop developers suspect that switching + webkit2gtk to build with the wpebackend will avoid the invisible text + and the crash (LP: #1964922), but it requires main inclusion for + additional libraries. The main inclusion will be worked on over the next + few months. + + Original Bug Report + --- + This is very similar to bug #1966418, but only concerns the email edit window. Before bug #1966418 was fixed, Evolution did not display email contents when running under Wayland. Starting Evolution with WEBKIT_DISABLE_COMPOSITING_MODE=1 worked around the issue. Now that #1966418 is fixed, displaying email contents works again even without the workaround. However, it's still not possible to write/edit an email. The message area is greyed out and unresponsive. When running under X or using the above workaround, editing emails works. So the issue seems to be the same as in #1966418, but for the edit window. Workaround #1 - Open a terminal and run this command: WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964922] Re: evolution crashed with SIGSEGV
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1964922/+attachment/5569167/+files/JournalErrors.txt ** Information type changed from Private to Public ** Changed in: evolution (Ubuntu) Status: Confirmed => In Progress ** Also affects: evolution (Ubuntu Jammy) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964922 Title: evolution crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1964922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Description changed: (initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell- does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] - Use Extension manager to install gnome extensions - https://flathub.org/apps/details/com.mattjakeman.ExtensionManager + If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. + + sudo apt install gnome-shell-extension-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969488] Re: ITP: text-engine -- Rich-text editing framework for GTK 4
** Changed in: ubuntu Status: New => Fix Released ** Package changed: ubuntu => text-engine (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969488 Title: ITP: text-engine -- Rich-text editing framework for GTK 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/text-engine/+bug/1969488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
** Description changed: - Desired Functionality + Impact - Systems using Nvidia graphics drivers should have an option to use Wayland but Xorg should be the default. Hybrid systems using Nvidia graphics drivers should use Wayland by default. - - Impact - -- Test Case - Create a new user (since existing users can choose their own session). Restart your system after applying the update. Select your name on the login screen. A gear button should appear in the lower right of the screen. - Click the gear button. Ubuntu should be selected unless you are using a system with only an Nvidia graphics card where Ubuntu on Xorg should be selected. + Click the gear button. Ubuntu should be selected. - Remaining concerns - - - Upgrades may still use Wayland? + If you are using a system with only an Nvidia graphics card (so your + system is not a hybrid), there should be an Ubuntu on Wayland option. - There are some suspend & resume issues with Wayland for Nvidia graphics - drivers in Ubuntu. + Otherwise, there should be an Ubuntu on Xorg option. + + What Could Go Wrong + --- + Hybrid systems should actually be using the Intel graphics for to run GNOME Shell so that's why it should be safe to use Wayland by default. + + There are some suspend & resume issues, an issue with gsync, etc. which + is why Nvidia are requesting that we don't enable Wayland by default for + systems that are only using the Nvidia graphics driver. We do still make + it available in case someone really wants to try without needing to edit + system files. + + Before last week, we were actually using Wayland by default for Nvidia + systems so this upload returns most systems back to that status quo. + + Priority + + This is a high priority for the Desktop and OEM Teams and it's requested that this update be available as soon as possible after release. + + The desktop live session defaults to Xorg not Wayland so this doesn't + impact that session at all. We are not going to delay the release to get + this fix on the Ubuntu 22.04 desktop ISO. Original Bug Report --- - I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics. The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused. I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system. So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
** Also affects: gdm3 (Ubuntu Jammy) Importance: High Status: In Progress ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967630] Re: gnome-weather fails to use dark theme
** Description changed: - Launching gnome-weather results in it using the light variant of - whatever Yaru theme is assigned. + Impact + -- + GNOME Weather uses the light theme regardless of whether the dark theme is selected in the GNOME Settings app. + + Also, GNOME Weather won't run correctly if gir1.2-gweather-4.0 or + gir1.2-gnomedesktop-4.0 are installed because the code wasn't specific + about which it needed. + + It would show a warning like this when run from the command line: + Requiring GnomeDesktop but it has 2 versions available; use imports.gi.versions to pick one + + Test Case + + sudo apt install --mark-auto gir1.2-gweather-4.0 gir1.2-gnomedesktop-4.0 + + Run gnome-weather and verify that the app works correctly. + + Open gnome-control-center. Switch to the Appearance panel and change the + color style from light to dark and verify that the app changes its + appearance to match. + + sudo apt autoremove + + What Could Go Wrong + --- + These are minimal fixes. + + GNOME Weather is shipped by default with Ubuntu MATE. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-weather 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 12:20:22 2022 InstallationDate: Installed on 2021-08-19 (226 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-weather UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-weather (Ubuntu Jammy) Importance: Low => Medium ** Changed in: gnome-weather (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967630 Title: gnome-weather fails to use dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1967630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969511] Re: gnome-tweaks shouldn't require gnome-shell-extension-prefs
** Changed in: gnome-tweaks (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969511 Title: gnome-tweaks shouldn't require gnome-shell-extension-prefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1969511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969511] Re: gnome-tweaks shouldn't require gnome-shell-extension-prefs
** Description changed: Impact -- There are now 2 apps in 22.04 LTS which allow configuring installed GNOME Shell Extensions: - gnome-shell-extension-prefs -- built as part of gnome-shell (but in universe & not installed by default) - gnome-shell-extension-manager -- this one additionally allows installing new extensions. Neither Firefox nor Chromium in Ubuntu have the Native Messaging Portal hooked up to allow chrome-gnome-shell to work. This makes gnome-shell-extension-manager the only GUI way in 22.04 LTS currently to install extensions from extensions.gnome.org. GNOME Tweaks has a hard dependency on only the first app. The dependency was added years ago when Tweaks had a code dependency on the extensions app. The Tweaks app no longer has any features to manage installed Extensions. Therefore, I'm demoting this dependency to Suggests. + Also, this new version disables the notice on first run that extension management has moved to a different app. The notice has a link to + https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/HEAD/subprojects/extensions-app/README.md + + which has a prominent Download on Flathub button which is unnecessary + since the app is already in Ubuntu. There are 2 apps and the message + only mentions one of them. Also, I believe the message is untranslated. + Test Case - Install the new GNOME Tweaks version. sudo apt remove gnome-shell-extension-prefs should work. + A new user shouldn't see a popup when they first start the Tweaks app. + + You can replicate the new user experience by running + gsettings reset org.gnome.tweaks show-extensions-notice + What Could Go Wrong + Users upgrading from Ubuntu 20.04 LTS won't be able to manage extensions unless they install one of the two extension apps. I will mention this in the Jammy Release Notes now. + + Users who only had the one extension app because it was a hard + dependency may have the app autoremoved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969511 Title: gnome-tweaks shouldn't require gnome-shell-extension-prefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1969511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
Łukasz, Yes, just opening the Sharing panel with gnome-control-center 1:41.4-1ubuntu12 is enough to attempt to start the RDP service. systemctl --user status gnome-remote-desktop reports this error: RDP TLS certificate and key not configured properly I didn't check open ports but it makes sense that it would open the RDP port even though the RDP service isn't completely working. ** Description changed: - Summary - === - 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. - 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. + Impact + == + 1. It looks like RDP Sharing is turned on but it is not. + 2. To actually turn on RDP Sharing, you would need to turn it off then turn it on. - On further investigation, it is not actually on. + This bugfix fixes it so that it correctly shown as off by default and + turning it on works. - More details + Test Case + = + 0. Start with a clean Ubuntu 22.04 install. + Or you can create a new user and log in as the new user. + 1. Open the Settings app. + 2. In the left sidebar, click Sharing. The switch at the top of the page needs to be off. + 3. Turn the switch on. Then click Remote Desktop and turn it on. + 4. Close the Settings app. + 5. Open the Settings app and verify that Sharing is on and Remote Desktop is on. + 6. Close the Settings app. + 7. From a terminal, run + systemctl --user status gnome-remote-sharing.service + + It should show the service as active (running) and + a line at the bottom should say RDP server started + 8. Then run + systemctl --user stop gnome-remote-sharing.service + 9. Open the Settings app. It should show that Remote Desktop sharing is off. + 10. Turn on Sharing and turn on Remote Desktop sharing. + 11. Run + systemctl --user status gnome-remote-sharing.service + + It should show the service as active (running) and + a line at the bottom should say RDP server started + + What Could Go Wrong + === + This is a minimal fix proposed upstream. + The original implementation was insufficient. + The bugfix will allow Remote Desktop to be turned on and work correctly from the beginning. + + More Details - This issue affects both the live session and the initial install. (Probably would show up for any new user.) - - 1. Before opening the Settings app, the gnome-remote-desktop service is - running. I think this is expected. - - $ systemctl status --user gnome-remote-desktop.service - \u25cf gnome-remote-desktop.service - GNOME Remote Desktop - Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> - Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago - Main PID: 1611 (gnome-remote-de) - Tasks: 4 (limit: 4603) - Memory: 13.8M - CPU: 66ms - CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> - \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon - - Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... - Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) - Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. - - Also, the RDP enable gsettings key is turned off. - - $ gsettings get org.gnome.desktop.remote-desktop.rdp enable - false - - 2. When I open the Sharing page, the gsettings key turns to true - - and systemctl shows me an error where it tried to enable RDP: - Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly - - 3. So then I open Remote Desktop Sharing and turn it off then on and - then systemctl shows me that is working correctly. - - Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... - Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> - Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. - Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started - - Note in particular the final line: "RDP server started". That tells us - whether RDP is running or not. There would be a similar line for VNC. - This line didn't show in the initial state in step 1. - - What should happen - == - Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. - - There is no gsettings for the Sharing master on/off switch (in the - headerbar). It shows as On if any of the services are On. None of the - services should be On by default so this should show Off by default. - - A Bug Trigger - = - It looks like this bug was triggered by - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - - I have reported this issue to GNOME. That patch fixes an important issue - so maybe we need to keep that patch but fix the logic in gnome-control- - center. + To simplify this bug report, I
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: gnome-control-center (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** No longer affects: gnome-remote-desktop (Ubuntu) ** Project changed: gnome-remote-desktop => gnome-control-center ** No longer affects: gnome-remote-desktop (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
** Description changed: This is very similar to bug #1966418, but only concerns the email edit window. Before bug #1966418 was fixed, Evolution did not display email contents when running under Wayland. Starting Evolution with WEBKIT_DISABLE_COMPOSITING_MODE=1 worked around the issue. Now that #1966418 is fixed, displaying email contents works again even without the workaround. However, it's still not possible to write/edit an email. The message area is greyed out and unresponsive. When running under X or using the above workaround, editing emails works. So the issue seems to be the same as in #1966418, but for the edit window. + + Workaround #1 + - + Open a terminal and run this command: + WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution + + Workaround #2 + - + Log out. + Select your name on the login screen. + Click the gear button and choose Ubuntu on Xorg. + Enter your password to finish logging in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969253] Re: Emails in email body is blank
*** This bug is a duplicate of bug 1966418 *** https://bugs.launchpad.net/bugs/1966418 I am marking this a duplicate of the now fixed bug https://launchpad.net/bugs/1966418 But note that there is a similar issue with composing emails. See https://launchpad.net/bugs/1969584 ** This bug has been marked a duplicate of bug 1966418 [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969253 Title: Emails in email body is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
** Changed in: evolution (Ubuntu) Status: Confirmed => Triaged ** Changed in: evolution (Ubuntu) Importance: Undecided => High ** Changed in: evolution (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Also affects: evolution (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969622] [NEW] save file dialog doesn't allow saving to a directory without files
Public bug reported: Impact -- Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4 This issue also affects gnome-text-editor which uses gtk4 directly. Attempting to save a file to an empty folder won't work in many cases because the Save button is insensitive (unable to be clicked). Test Case - View this page with the Firefox or Chromium snaps. Press Ctrl+S to try to save this page. Navigate to a folder without any files in it. (It can have other folders in it.) The Save button should stay lit up. Save the file. Note that I wasn't able to reproduce the bug for bookmarked folders in the left sidebar so just navigate using the main view area. What Could Go Wrong This is a one-line bug fix from the stable gtk-4-6 branch targeted to directly fix this issue. Other Notes --- I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue. I do request a 0-day SRU since this is a small high impact fix that affects the usability of the Firefox snap. ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk4 (Ubuntu) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags: jammy ** Summary changed: - save file dialog doesn't allow saving to empty directory + save file dialog doesn't allow saving to a directory without files ** Description changed: Impact -- Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4 This issue also affects gnome-text-editor which uses gtk4 directly. Attempting to save a file to an empty folder won't work in many cases because the Save button is insensitive (unable to be clicked). Test Case - View this page with the Firefox or Chromium snaps. Press Ctrl+S to try to save this page. - Navigate to an empty folder. + Navigate to a folder without any files in it. (It can have other folders in it.) The Save button should stay lit up. Save the file. Note that I wasn't able to reproduce the bug for bookmarked folders in the left sidebar so just navigate using the main view area. What Could Go Wrong This is a one-line bug fix from the stable gtk-4-6 branch targeted to directly fix this issue. Other Notes --- I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue. I do request a 0-day SRU since this is a small high impact fix that affects the usability of the Firefox snap. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4851 https://gitlab.gnome.org/GNOME/gtk/-/issues/4851 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4851 Importance: Unknown Status: Unknown ** Changed in: gtk4 (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969622 Title: save file dialog doesn't allow saving to a directory without files To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1969622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #94 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/94 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/94 Importance: Unknown Status: Unknown ** Also affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => High ** Project changed: gnome-control-center => gnome-remote-desktop ** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. - Guesses and Further Investigation Needed - == - I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. + A Bug Trigger + = + It looks like this bug was triggered by + https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off - by default. - - Also, we did add this patch: - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. + I have reported this issue to GNOME. That patch fixes an important issue + so maybe we need to keep that patch but fix the logic in gnome-control- + center. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-remote-desktop/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == - The Sharing master witch should be off by default. + Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. - Remote Desktop should show off by default and should not attempt to turn - on just by opening the Sharing page. + There is no gsettings for the Sharing master on/off switch (in the + headerbar). It shows as On if any of the services are On. None of the + services should be On by default so this should show Off by default. Guesses and Further Investigation Needed == - Is there a gsettings key for the master sharing on/off switch? - - I think there may have been a logic bug when the RDP sharings were - backported from gnome-control-center 42. This code was originally in - gtk4 so some rewriting was necessary. + I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off by default. Also, we did add this patch: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] [NEW] RDP Sharing appears on by default in jammy
Public bug reported: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == The Sharing master witch should be off by default. Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. Guesses and Further Investigation Needed == Is there a gsettings key for the master sharing on/off switch? I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off by default. Also, we did add this patch: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. ** Affects: gnome-control-center (Ubuntu) Importance: High Status: Triaged ** Affects: gnome-control-center (Ubuntu Jammy) Importance: High Status: Triaged ** Tags: jammy ** Also affects: gnome-control-center (Ubuntu Jammy) Importance: High Status: Triaged ** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. - $ systemctl status --user gnome-remote-desktop.service + $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop - Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> - Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago -Main PID: 1611 (gnome-remote-de) - Tasks: 4 (limit: 4603) - Memory: 13.8M - CPU: 66ms - CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> - \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon + Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> + Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago + Main PID: 1611 (gnome-remote-de) + Tasks: 4 (limit: 4603) + Memory: 13.8M + CPU: 66ms + CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> + \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop...
[Bug 1969524] Re: Broken login on jammy VM using wayland, on a jammy host
** Changed in: osinfo-db (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969524 Title: Broken login on jammy VM using wayland, on a jammy host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osinfo-db/+bug/1969524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969524] Re: Broken login on jammy VM using wayland, on a jammy host
** Description changed: - I have a jammy laptop I installed today, and I used the same iso to - create a jammy VM using virt-manager. In that VM, after the installation - is complete, I cannot login. The screen either stays black, or throws me - back to the login prompt. If I switch to Xorg login type, then it works. + Impact + -- + If you use virt-manager or gnome-boxes from a 22.04 host to install a 22.04 VM, the VM tries to use Wayland by default and only shows a black screen. - More data coming up. + Test Case + - + 1. Install the osinfo-db update and gnome-boxes + 2. Close GNOME Boxes if it's running. Open GNOME Boxes. + 3. Click the + icon, then Create virtual machine from file. Select your Ubuntu 22.04 desktop ISO. + 4. Follow the prompts to create your box. + 5. After it finishes installing, click the box. Log in. The screen should show like normal. - Suggested fix - - - I think we're going to want to revert - https://gitlab.com/libosinfo/osinfo-db/-/commit/6ef9c9d4979d8 + What Could Go Wrong + --- + This disables the 3D Acceleration (virgl) feature. The 3D Acceleration feature is disabled by default (you have to manually enable it even after installing a distro where it is offered). - Try removing that section from your - /usr/share/osinfo/os/ubuntu/ubuntu-18.04.xml before creating a jammy VM. + And you have to toggle the switch to keep it working: + https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/759#note_1386057 + + It's not clear why this black screen bug occurs, but there is an easy + fix to revert a not very useful feature that only landed in 22.04 about + a week ago. ** Changed in: osinfo-db (Ubuntu) Importance: Undecided => Critical ** Changed in: osinfo-db (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969524 Title: Broken login on jammy VM using wayland, on a jammy host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osinfo-db/+bug/1969524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969524] Re: Broken login on jammy VM using wayland, on a jammy host
** Description changed: I have a jammy laptop I installed today, and I used the same iso to create a jammy VM using virt-manager. In that VM, after the installation is complete, I cannot login. The screen either stays black, or throws me back to the login prompt. If I switch to Xorg login type, then it works. More data coming up. + + Suggested fix + - + I think we're going to want to revert + https://gitlab.com/libosinfo/osinfo-db/-/commit/6ef9c9d4979d8 + + Try removing that section from your + /usr/share/osinfo/os/ubuntu/ubuntu-18.04.xml before creating a jammy VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969524 Title: Broken login on jammy VM using wayland, on a jammy host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osinfo-db/+bug/1969524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969511] [NEW] gnome-tweaks shouldn't require gnome-shell-extension-prefs
Public bug reported: Impact -- There are now 2 apps in 22.04 LTS which allow configuring installed GNOME Shell Extensions: - gnome-shell-extension-prefs -- built as part of gnome-shell (but in universe & not installed by default) - gnome-shell-extension-manager -- this one additionally allows installing new extensions. Neither Firefox nor Chromium in Ubuntu have the Native Messaging Portal hooked up to allow chrome-gnome-shell to work. This makes gnome-shell-extension-manager the only GUI way in 22.04 LTS currently to install extensions from extensions.gnome.org. GNOME Tweaks has a hard dependency on only the first app. The dependency was added years ago when Tweaks had a code dependency on the extensions app. The Tweaks app no longer has any features to manage installed Extensions. Therefore, I'm demoting this dependency to Suggests. Test Case - Install the new GNOME Tweaks version. sudo apt remove gnome-shell-extension-prefs should work. What Could Go Wrong ** Affects: gnome-tweaks (Ubuntu) Importance: Low Assignee: Jeremy Bicha (jbicha) Status: Triaged ** Affects: gnome-tweaks (Ubuntu Jammy) Importance: Low Assignee: Jeremy Bicha (jbicha) Status: Triaged ** Tags: jammy ** Changed in: gnome-tweaks (Ubuntu) Status: New => Triaged ** Also affects: gnome-tweaks (Ubuntu Jammy) Importance: Low Assignee: Jeremy Bicha (jbicha) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969511 Title: gnome-tweaks shouldn't require gnome-shell-extension-prefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1969511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** Description changed: + Desired Functionality + - + Systems using Nvidia graphics drivers should have an option to use Wayland but Xorg should be the default. + + Hybrid systems using Nvidia graphics drivers should use Wayland by + default. + + Impact + -- + + Test Case + - + Create a new user (since existing users can choose their own session). + Restart your system after applying the update. + Select your name on the login screen. + A gear button should appear in the lower right of the screen. + Click the gear button. Ubuntu should be selected unless you are using a system with only an Nvidia graphics card where Ubuntu on Xorg should be selected. + + Remaining concerns + - + Upgrades may still use Wayland? + + There are some suspend & resume issues with Wayland for Nvidia graphics + drivers in Ubuntu. + + Original Bug Report + --- + I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics. The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused. I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system. So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967629] Re: gnome-sound-recorder 42 is not wanted for jammy
Somehow, this removal didn't stick. I wonder why. It is an arch: all package. https://launchpad.net/ubuntu/+source/gnome-sound-recorder/+publishinghistory https://launchpad.net/ubuntu/jammy/amd64/gnome-sound-recorder But I guess I'll let it stay since 1. It's unseeded 2. revert version numbers don't look great 3. Ubuntu's libadwaita was updated to support the Yaru color schemes LP: #196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967629 Title: gnome-sound-recorder 42 is not wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1967629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Please use https://launchpad.net/bugs/1968929 as the tracker for Wayland not being an option for Ubuntu 22.04 with Nvidia graphics. ** Description changed: Impact -- Ubuntu Desktop 22.04 no longer offers Wayland Test Case - Install the update on a desktop or laptop without Nvidia or hybrid graphics that normally supports Wayland. Restart the computer. On the login screen, select your name. A gear button should appear in the bottom right giving you the option for Ubuntu or Ubuntu on Xorg. Continue logging in to the Ubuntu session. After log in, open the Settings app. Click at the bottom of the sidebar to open the About panel. The Windowing system should say Wayland. Note - It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.). This issue is currently being tracked with LP: #1968929 + It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. This issue is currently being tracked with LP: #1968929 How this was broken and fixed - I took gdm 42.0-1ubuntu3 and removed the one cherrypicked patch we no longer needed. That required rebasing later patches. I made a mistake when rebasing. To fix this, I returned to the known working 42.0-1ubuntu3, kept the patch but added a new patch at the end to revert the patch we don't need. This is a cleaner fix and will work better when we package the new GDM release where we will probably still need the revert patch. Release Team, see the more minimal debdiff in comment 10. Original Bug Report --- After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no longer shows any sessions in the bottom-right corner. When I log in, I am dropped into an X11 session, with no way to switch to Wayland. Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to 42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions and defaults to Wayland again. Looking at the changelog: gdm3 (42.0-1ubuntu4) jammy; urgency=medium * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. It's not needed for Ubuntu 22.04 LTS (LP: #1968809) -- Jeremy Bicha Thu, 14 Apr 2022 14:29:35 -0400 However, all my machines are i915-only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
Tim, please update to gdm3 42.0-1ubuntu6 when it's available in a few hours. After it's installed, restart your computer and see if you still experience this issue. The earlier gdm3 42.0-1ubuntu4 had some other bad side effects which might have inadvertently made your issue not show up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
** Changed in: gdm3 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Yes, this bug disabled Wayland for everyone. So we don't need more reports confirming that it affects your Intel or AMD system. The bugfix is waiting for someone from the Ubuntu Release Team to accept it but it's a holiday weekend so it may take until tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899224] Re: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?
It doesn't look like Chrome needs pipewire 0.2 any more so I'm closing this bug. ** Changed in: pipewire (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899224 Title: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1899224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
I wasn't able to read the debdiff from Matthijs but I did read the comment so I've uploaded an updated version to the unapproved jammy queue. Here's the minimal debdiff from the working ubuntu3 version. ** Patch added: "debdiff-from-working-gdm3_42.0-1ubuntu3-to-ubuntu6.diff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+attachment/5581071/+files/debdiff-from-working-gdm3_42.0-1ubuntu3-to-ubuntu6.diff ** Description changed: Impact -- Ubuntu Desktop 22.04 no longer offers Wayland Test Case - Install the update on a desktop or laptop without Nvidia or hybrid graphics that normally supports Wayland. Restart the computer. On the login screen, select your name. A gear button should appear in the bottom right giving you the option for Ubuntu or Ubuntu on Xorg. Continue logging in to the Ubuntu session. After log in, open the Settings app. Click at the bottom of the sidebar to open the About panel. The Windowing system should say Wayland. Note It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.). This issue is currently being tracked with LP: #1968929 How this was broken and fixed - I took gdm 42.0-1ubuntu3 and removed the one cherrypicked patch we no longer needed. That required rebasing later patches. I made a mistake when rebasing. To fix this, I returned to the known working 42.0-1ubuntu3, kept the patch but added a new patch at the end to revert the patch we don't need. This is a cleaner fix and will work better when we package the new GDM release where we will probably still need the revert patch. - Release Team, see the more minimal debdiff in comment 5. + Release Team, see the more minimal debdiff in comment 10. Original Bug Report --- After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no longer shows any sessions in the bottom-right corner. When I log in, I am dropped into an X11 session, with no way to switch to Wayland. Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to 42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions and defaults to Wayland again. Looking at the changelog: gdm3 (42.0-1ubuntu4) jammy; urgency=medium * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. It's not needed for Ubuntu 22.04 LTS (LP: #1968809) -- Jeremy Bicha Thu, 14 Apr 2022 14:29:35 -0400 However, all my machines are i915-only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 ** This bug has been marked a duplicate of bug 1969243 gdm 42.0-1ubuntu4 no longer shows Wayland option -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
This was worked around with gdm3 42.0-1ubuntu4 (which caused a regression but will be fixed in 42.0-1ubuntu5) Maybe we want to use a different bug to track the Nvidia drivers needing to be updated to support suspend and resume correctly so that Wayland can be offered again? I suggest https://launchpad.net/bugs/1968929 ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Here is the minimal debdiff ** Patch added: "debdiff-from-working-gdm3_42.0-1ubuntu3.diff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+attachment/5581005/+files/debdiff-from-working-gdm3_42.0-1ubuntu3.diff ** Description changed: Impact -- Ubuntu Desktop 22.04 no longer offers Wayland Test Case - Install the update on a desktop or laptop without Nvidia or hybrid graphics that normally supports Wayland. Restart the computer. On the login screen, select your name. A gear button should appear in the bottom right giving you the option for Ubuntu or Ubuntu on Xorg. Continue logging in to the Ubuntu session. After log in, open the Settings app. Click at the bottom of the sidebar to open the About panel. The Windowing system should say Wayland. Note It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.). This issue is currently being tracked with LP: #1968929 How this was broken and fixed - I took gdm 42.0-1ubuntu3 and removed the one cherrypicked patch we no longer needed. That required rebasing later patches. I made a mistake when rebasing. To fix this, I returned to the known working 42.0-1ubuntu3, kept the patch but added a new patch at the end to revert the patch we don't need. This is a cleaner fix and will work better when we package the new GDM release where we will probably still need the revert patch. + Release Team, see the more minimal debdiff in comment 5. + Original Bug Report --- After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no longer shows any sessions in the bottom-right corner. When I log in, I am dropped into an X11 session, with no way to switch to Wayland. Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to 42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions and defaults to Wayland again. Looking at the changelog: gdm3 (42.0-1ubuntu4) jammy; urgency=medium * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. It's not needed for Ubuntu 22.04 LTS (LP: #1968809) -- Jeremy Bicha Thu, 14 Apr 2022 14:29:35 -0400 However, all my machines are i915-only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969197] Re: 42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card
*** This bug is a duplicate of bug 1968929 *** https://bugs.launchpad.net/bugs/1968929 ** This bug has been marked a duplicate of bug 1968929 No Wayland support on my NVIDA laptop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969197 Title: 42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
** Description changed: + Impact + -- + Ubuntu Desktop 22.04 no longer offers Wayland + + Test Case + - + Install the update on a desktop or laptop without Nvidia or hybrid graphics that normally supports Wayland. + + Restart the computer. + + On the login screen, select your name. + + A gear button should appear in the bottom right giving you the option + for Ubuntu or Ubuntu on Xorg. Continue logging in to the Ubuntu session. + + After log in, open the Settings app. Click at the bottom of the sidebar + to open the About panel. The Windowing system should say Wayland. + + Note + + It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.) + + How this was broken and fixed + - + I took gdm 42.0-1ubuntu3 and removed the one cherrypicked patch we no longer needed. That required rebasing later patches. I made a mistake when rebasing. + + To fix this, I returned to the known working 42.0-1ubuntu3, kept the + patch but added a new patch at the end to revert the patch we don't + need. This is a cleaner fix and will work better when we package the new + GDM release where we will probably still need the revert patch. + + + Original Bug Report + --- + After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no longer shows any sessions in the bottom-right corner. When I log in, I am dropped into an X11 session, with no way to switch to Wayland. Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to 42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions and defaults to Wayland again. Looking at the changelog: gdm3 (42.0-1ubuntu4) jammy; urgency=medium - * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. - It's not needed for Ubuntu 22.04 LTS (LP: #1968809) + * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. + It's not needed for Ubuntu 22.04 LTS (LP: #1968809) - -- Jeremy Bicha Thu, 14 Apr 2022 14:29:35 -0400 - + -- Jeremy Bicha Thu, 14 Apr 2022 14:29:35 -0400 However, all my machines are i915-only. ** Changed in: gdm3 (Ubuntu Jammy) Status: Triaged => In Progress ** Description changed: Impact -- Ubuntu Desktop 22.04 no longer offers Wayland Test Case - Install the update on a desktop or laptop without Nvidia or hybrid graphics that normally supports Wayland. Restart the computer. On the login screen, select your name. A gear button should appear in the bottom right giving you the option for Ubuntu or Ubuntu on Xorg. Continue logging in to the Ubuntu session. After log in, open the Settings app. Click at the bottom of the sidebar to open the About panel. The Windowing system should say Wayland. Note - It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.) + It is known that Wayland is not currently offered for Nvidia because the Nvidia drivers don't meet GNOME's standards for suspend and resuming from suspend. It is intended that that will be fixed in a stable release update for 22.04 LTS. Once that happens, Wayland should work without needing any change from GDM. (Just a reboot.). This issue is currently being tracked with LP: #1968929 How this was broken and fixed - I took gdm 42.0-1ubuntu3 and removed the one cherrypicked patch we no longer needed. That required rebasing later patches. I made a mistake when rebasing. To fix this, I returned to the known working 42.0-1ubuntu3, kept the patch but added a new patch at the end to revert the patch we don't need. This is a cleaner fix and will work better when we package the new GDM release where we will probably still need the revert patch. - Original Bug Report --- After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no longer shows any sessions in the bottom-right corner. When I log in, I am dropped into an X11 session, with no way to switch to Wayland. Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to 42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions and defaults to Wayland again. Looking at the changelog: gdm3 (42.0-1ubuntu4) jammy; urgency=medium * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers. It's not needed for Ubuntu 22.04 LTS (LP: #1968
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
** Changed in: gdm3 (Ubuntu) Importance: Undecided => Critical ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Triaged ** Also affects: gdm3 (Ubuntu Jammy) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966945] Re: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head()
** Description changed: - Crash happened a short time after starting a screen cast / remote - desktop session using the Freedesktop portal API in a Wayland session - with mouse and keyboard input. Screen cast continues to run (i.e., - PipeWire stream), but input stops. + Impact + -- + xdg-desktop-portal 1.14.3 has a single change fixing a consistent crash when using the experimental Wayland feature in TeamViewer. + + Original Bug Report + --- + Crash happened a short time after starting a screen cast / remote desktop session using the Freedesktop portal API in a Wayland session with mouse and keyboard input. Screen cast continues to run (i.e., PipeWire stream), but input stops. Can be reproduced by using the experimental Wayland support of TeamViewer (https://community.teamviewer.com/English/discussion/122410/teamviewer- support-on-wayland-experimental-state-%F0%9F%A7%AA) Reported upstream as well: https://github.com/flatpak/xdg-desktop- portal/issues/771 - lsb_release -rd: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 14:04:48 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x7fcf54779d7b:mov0x8(%rax),%rcx PC (0x7fcf54779d7b) ok source "0x8(%rax)" (0x7fcf0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:73 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:22 start_thread (arg=) at ./nptl/pthread_create.c:453 Title: xdg-desktop-portal crashed with SIGSEGV in __GI___nptl_deallocate_tsd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966945 Title: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966945] Re: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head()
** Also affects: xdg-desktop-portal (Ubuntu Jammy) Importance: Medium Status: New ** Changed in: xdg-desktop-portal (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966945 Title: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969148] Re: [UIFe] Jammy default wallpaper update
** Changed in: ubiquity-slideshow-ubuntu (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969148 Title: [UIFe] Jammy default wallpaper update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
Xavier, this bug is closed. Please file a new bug for any other issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
Yes, Menno, this is a regression in that Ubuntu 21.10 enabled Wayland for Nvidia and Ubuntu 22.04 now does not. An issue was identified with suspend not working for GNOME requirements. Once the Nvidia drivers are updated to fix that issue in a future stable release update, Wayland should be available again. See https://launchpad.net/bugs/1969198 or file a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
** Changed in: gdm3 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969198] Re: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card
*** This bug is a duplicate of bug 1968929 *** https://bugs.launchpad.net/bugs/1968929 I'm marking this a duplicate of https://launchpad.net/bugs/1968929 since there is more detail there and it was filed earlier. ** This bug has been marked a duplicate of bug 1968929 No Wayland support on my NVIDA laptop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969198 Title: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Chris, yes, the snapd update isn't in Jammy currently. The correct command to check what version of snapd you are running is snap info snapd I think you'll need to restart once snapd is updated to get the fix. It's correct for this bug to be Fix Released because there is nothing left to do on the LibreOffice side. The snapd update should be released soon (I don't have an exact schedule for it.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
Marcos, that is intended behavior. https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on- nvidia-if-suspend-is-broken.patch I believe Canonical is going to work on getting suspend working for the Nvidia drivers as required by GNOME for Wayland support. That will be a future stable release update for 22.04 LTS. You'll need to open a new bug if you need to discuss this further since we don't really follow closed bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508617] Re: Build with multiarch support
** Changed in: gtk-vnc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508617 Title: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk-vnc/+bug/1508617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969198] Re: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card
Sorry, there are issues with the Nvidia drivers when used on Wayland. https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on- nvidia-if-suspend-is-broken.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969198 Title: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969148] Re: [UIFe] Jammy default wallpaper update
** Changed in: ubuntu-wallpapers (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969148 Title: [UIFe] Jammy default wallpaper update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969115] Re: Update glib to 2.72.1
** Changed in: glib2.0 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969115 Title: Update glib to 2.72.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1969115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969148] Re: [UIFe] Jammy default wallpaper update
** Changed in: ubuntu-wallpapers (Ubuntu) Status: Triaged => In Progress ** Changed in: ubiquity-slideshow-ubuntu (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969148 Title: [UIFe] Jammy default wallpaper update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
** No longer affects: nautilus (Ubuntu Jammy) ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Changed in: nautilus (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867320] Re: bad kerning
Could you attach the PDF here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867320 Title: bad kerning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1867320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969148] Re: [UIFe] Jammy default wallpaper update
** Description changed: Based on community feedback and internal review, we need to tweak the Jammy Jellyfish mascot wallpapers. Sorry for the inconvenience but it's important that things look as great as possible for the next LTS. Notifications: + https://lists.ubuntu.com/archives/ubuntu-doc/2022-April/020839.html + + + https://lists.ubuntu.com/archives/ubuntu-translators/2022-April/007836.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969148 Title: [UIFe] Jammy default wallpaper update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969148] [NEW] [UIFe] Jammy default wallpaper update
Public bug reported: Based on community feedback and internal review, we need to tweak the Jammy Jellyfish mascot wallpapers. Sorry for the inconvenience but it's important that things look as great as possible for the next LTS. Notifications: https://lists.ubuntu.com/archives/ubuntu-doc/2022-April/020839.html https://lists.ubuntu.com/archives/ubuntu-translators/2022-April/007836.html ** Affects: ubiquity-slideshow-ubuntu (Ubuntu) Importance: Low Status: Confirmed ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Low Status: Confirmed ** Tags: jammy ** Also affects: ubiquity-slideshow-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity-slideshow-ubuntu (Ubuntu) Status: New => Confirmed ** Changed in: ubiquity-slideshow-ubuntu (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969148 Title: [UIFe] Jammy default wallpaper update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
** Description changed: - I need to check to make sure that we do in fact want the gdm3 cherry- - picks for Jammy so filing this bug to hold things for a moment. + Earlier this week, I cherry-picked commits from GDM. One of those + commits isn't needed because we distro-patched some fixes for Nvidia + hybrid graphics in Ubuntu 22.04. - I cherrypicked all the March 23 commits with - https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu3 - https://gitlab.gnome.org/GNOME/gdm/-/commits/main - - The upstream merge proposal with some explanation in the comments was - https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171 - - We plan to do a partial revert on April 14 in time for Ubuntu 22.04 - Final Freeze. + The GDM commit disabled Wayland in that situation but since Wayland + works, we don't want to disable it. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => In Progress ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
*** This bug is a duplicate of bug 1968809 *** https://bugs.launchpad.net/bugs/1968809 ** This bug has been marked a duplicate of bug 1968809 Verify that the gdm cherry-picks are wanted for jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960546] Re: [snap] can't view html documentation in /usr/share/gtk-doc/
Fixed in snapd master so this will roll out automatically soon. ** Changed in: firefox (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960546 Title: [snap] can't view html documentation in /usr/share/gtk-doc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967632] Re: apparmor denied when trying to load pkcs11 module for smart card authentication
** Tags added: snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: apparmor denied when trying to load pkcs11 module for smart card authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969145] [NEW] oss4 autopkgtest regression: unrecognized command-line option ‘-mfloat-abi=hard’
Public bug reported: The oss4 autopkgtest is failing now on Jammy which is holding back a few packages (dkms, glib2.0) in jammy-proposed. https://autopkgtest.ubuntu.com/packages/o/oss4/jammy/amd64 It's interesting that the error message looks similar to the last oss4 upload in Ubuntu: https://launchpad.net/ubuntu/+source/oss4/4.2-build2010-5ubuntu9 I think if I retried the oss4 autopkgtest with migration-reference/0 that it would fail so I might do that to get the other fixes into jammy. E: oss4/4.2-build2010 failed to build for 5.15.0-25-generic == /var/lib/dkms/oss4/4.2-build2010/build/make.log == DKMS make.log for oss4-4.2-build2010 for kernel 5.15.0-25-generic (x86_64) Wed Apr 13 13:01:42 UTC 2022 make: Entering directory '/usr/src/linux-headers-5.15.0-25-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ ** Affects: oss4 (Ubuntu) Importance: High Status: New ** Tags: jammy ** Description changed: The oss4 autopkgtest is failing now on Jammy which is holding back a few packages (dkms, glib2.0) in jammy-proposed. + + https://autopkgtest.ubuntu.com/packages/o/oss4/jammy/amd64 It's interesting that the error message looks similar to the last oss4 upload in Ubuntu: https://launchpad.net/ubuntu/+source/oss4/4.2-build2010-5ubuntu9 I think if I retried the oss4 autopkgtest with migration-reference/0 that it would fail so I might do that to get the other fixes into jammy. - E: oss4/4.2-build2010 failed to build for 5.15.0-25-generic == /var/lib/dkms/oss4/4.2-build2010/build/make.log == DKMS make.log for oss4-4.2-build2010 for kernel 5.15.0-25-generic (x86_64) Wed Apr 13 13:01:42 UTC 2022 make: Entering directory '/usr/src/linux-headers-5.15.0-25-generic' - CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o + CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969145 Title: oss4 autopkgtest regression: unrecognized command-line option ‘-mfloat-abi=hard’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Tags added: rls-jj-incoming ** Changed in: openssl (Ubuntu) Importance: Undecided => High ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
I feel like I experience the same bug. - My system has only Intel graphics. No NVIDIA. Only the single GPU. - Happens in both the Ubuntu [Wayland] and the Ubuntu on Xorg sessions - I get sent to the login screen the first time I connect an external monitor. Or I get sent to the login screen the first time I disconnect an external monitor that was connected when I started Ubuntu. ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962699 Title: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968903] Re: evince: include fixes from gnome-42 branch
** Changed in: evince (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968903 Title: evince: include fixes from gnome-42 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1968903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
I uploaded this to jammy unapproved for you and am unsubscribing ubuntu- sponsors. The tarball name isn't really an issue. If we used debian/source/format 3.0 (quilt), I think the tarball would look more like what you'd expect. But it's too late to change that for jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962699 Title: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969115] [NEW] Update glib to 2.72.1
Public bug reported: Impact -- glib has a new bugfix release as part of their GNOME 42 series https://gitlab.gnome.org/GNOME/glib/-/blob/glib-2-72/NEWS Test Case - Ensure that the autopkgtests complete successfully. The autopkgtests run installed tests. Where Problems Could Occur -- This is believed to be part of the GNOME micro-release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969115 Title: Update glib to 2.72.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1969115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969097] Re: connecting interfaces with a udev rule triggers return to gdm login screen
This was cherry-picked as part of https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu3 I will be doing another gdm3 upload today to unblock gdm3 from jammy- proposed. ** Changed in: gdm (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969097 Title: connecting interfaces with a udev rule triggers return to gdm login screen To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1969097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969098] Re: [22.04 Regression] network login page not working at all
*** This bug is a duplicate of bug 1966418 *** https://bugs.launchpad.net/bugs/1966418 The captive portal page is part of gnome-shell powered by webkit2gtk which means this is a duplicate of LP: #1966418 ** This bug has been marked a duplicate of bug 1966418 [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969098 Title: [22.04 Regression] network login page not working at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968915] [NEW] osinfo-db: update jammy to latest version
Public bug reported: https://gitlab.com/libosinfo/osinfo-db/-/commits/master ** Affects: osinfo-db (Ubuntu) Importance: Undecided Status: In Progress ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968915 Title: osinfo-db: update jammy to latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osinfo-db/+bug/1968915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968903] [NEW] evince: include fixes from gnome-42 branch
Public bug reported: I am cherry-picking commits from https://gitlab.gnome.org/GNOME/evince/-/commits/gnome-42 ** Affects: evince (Ubuntu) Importance: Undecided Status: In Progress ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968903 Title: evince: include fixes from gnome-42 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1968903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968405] Re: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory]
** Changed in: yaru-theme (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg- new": No such file or directory] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
** Description changed: I need to check to make sure that we do in fact want the gdm3 cherry- picks for Jammy so filing this bug to hold things for a moment. + + I cherrypicked all the March 23 commits with + https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu3 + https://gitlab.gnome.org/GNOME/gdm/-/commits/main + + The upstream merge proposal with some explanation in the comments was + https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171 + + We plan to do a partial revert on April 14 in time for Ubuntu 22.04 + Final Freeze. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964600] Re: [MIR] gnome-bluetooth3
Christian, sorry it hasn't fully been published yet: https://launchpad.net/ubuntu/+source/gnome-shell/42.0-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR] gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968780] Re: evolution crashes at startup
** This bug is no longer a duplicate of bug 1966418 [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968780 Title: evolution crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968812] Re: email content display blank
*** This bug is a duplicate of bug 1966418 *** https://bugs.launchpad.net/bugs/1966418 ** This bug has been marked a duplicate of bug 1966418 [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968812 Title: email content display blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878998] Re: Value in Yaru-dark/gnome-shell/gnome-shell.css not used
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878998 Title: Value in Yaru-dark/gnome-shell/gnome-shell.css not used To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1878998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964600] Re: [MIR] gnome-bluetooth3
** Changed in: gnome-bluetooth3 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR] gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-bluetooth (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
Yes, details were minimal because I just wanted to get a block-proposed bug in so we could discuss more. Initial thinking is that we should remove the 440d6f9ecc151fbcf8c852d500c5cc5add168b94 patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968809] [NEW] Verify that the gdm cherry-picks are wanted for jammy
Public bug reported: I need to check to make sure that we do in fact want the gdm3 cherry- picks for Jammy so filing this bug to hold things for a moment. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968405] Re: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory]
** Changed in: yaru-theme (Ubuntu Jammy) Importance: Undecided => High ** Changed in: yaru-theme (Ubuntu Jammy) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg- new": No such file or directory] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968747] [NEW] Cherry-pick fixes from the gnome-42 branch
Public bug reported: I'm cherry-picking some fixes from the gnome-42 branch since epiphany 42.1 won't be released before 22.04 LTS. Uploading directly to jammy instead of to unstable to not further delay Epiphany 42.0 reaching Testing. ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: In Progress ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968747 Title: Cherry-pick fixes from the gnome-42 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1968747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
MIR Team approved at today's meeting so I'm setting to Triaged. ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-bluetooth (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964600] Re: [MIR] gnome-bluetooth3
** Changed in: gnome-bluetooth3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR] gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968720] Re: Missing font on the Flutter installer UI in WSL
https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=f49eb32c75f5fb4bed6f3316d1e558998dc264a8 ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968720 Title: Missing font on the Flutter installer UI in WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1968720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
** Description changed: Why It's Needed --- This will fix LP: #1738838 gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier since we don't have to revert all the bluetooth-related commits. Why, More Details - GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: #1738838 The API changes were not practical to forward-port (switch to a new GListModel API). Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the older gnome-bluetooth library, which is more awkward to maintain. Because of how GNOME Shell extensions work, if an extension tries to modify the bluetooth part of the system status menu in the top right corner of the screen, the extension may not work because Ubuntu's GNOME Shell 42 is different than what every other distro provides. I assess this concern as very low since extensions are "use at your own risk" and there aren't many working bluetooth extensions. The new gnome-bluetooth3 series has an expanded build test suite and has received lots of fixes that won't be ported to the older gnome-bluetooth series. Why It Wasn't Done Before - We needed to get a MIR to allow gnome-bluetooth3 in to main while the old gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 . Sorry this is a bit late. Still about a week before Final Freeze to revert these changes is issues are identified but we're feeling confident this will be a worthwhile improvement. Other Change If this FFE is approved, we'd like to go ahead and drop the gir package built by the old gnome-bluetooth since nothing is using it. It is believed that gnome-shell is the only user of the gnome-bluetooth gir bindings. + + https://tracker.debian.org/media/packages/g/gnome- + bluetooth/changelog-3.34.5-8 + + Build Log for gnome-shell + - + This is from our git master so it includes a few other pending changes + + https://launchpad.net/~ubuntu- + desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Yes, it is buildable. I was running it yesterday. It was just missing one build-dependency so I added it and have done a PPA build for you: https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+sourcepub/13423577/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Gunnar, it looks like the GNOME did update their sharing-desktop.page for the bullet points I mentioned. Maybe you can use their version for jammy if this FFe is approved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
