[Desktop-packages] [Bug 2004241] Re: Update to glib >= 2.75.1
I was using the latest version of glib 2.75 as packaged in Debian experimental for a few days, but my sound broke. See https://gitlab.gnome.org/GNOME/glib/-/issues/2769 There probably are other things that broke because of that behavior change. Also, recent changes made glib break on other architectures (endian issue?) which means it would be stuck in lunar-proposed until that is fixed. https://buildd.debian.org/status/package.php?p=glib2.0=experimental ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Medium ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2769 https://gitlab.gnome.org/GNOME/glib/-/issues/2769 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Triaged Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
You shouldn't build the package from source; it is already built in the
proposed updates repository.
miguelquiros, please specify what version of Ubuntu you are using. There
are proposed packages for both Ubuntu 22.04 LTS and Ubuntu 22.10
available now to fix this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003732] [NEW] Update mutter to 43.2
Public bug reported: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS The current version in Ubuntu 22.10 is 43.0 Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update introduces a behavior change. Fullscreen apps can no longer be transparent or translucent. However, this behavior change was made to comply with the Wayland spec and better protects against apps trying to work around intentional Wayland restrictions. See the upstream bugs for https://launchpad.net/bugs/2003104 for more background. ** Affects: mutter (Ubuntu) Importance: High Status: Fix Released ** Affects: mutter (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: kinetic upgrade-software-version ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: mutter (Ubuntu Kinetic) Status: New => Triaged ** Description changed: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS The current version in Ubuntu 22.10 is 43.0 Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + Other Info + -- + This update introduces a behavior change. Fullscreen apps can no longer be transparent or translucent. However, this behavior change was made to comply with the Wayland spec and better protects against apps trying to work around intentional Wayland restrictions. See the upstream bugs for https://launchpad.net/bugs/2003104 for more background. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003732 Title: Update mutter to 43.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Kinetic: Triaged Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS The current version in Ubuntu 22.10 is 43.0 Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update introduces a behavior change. Fullscreen apps can no longer be transparent or translucent. However, this behavior change was made to comply with the Wayland spec and better protects against apps trying to work around intentional Wayland restrictions. See the upstream bugs for https://launchpad.net/bugs/2003104 for more background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
I installed gjs 1.74.0-0ubuntu1 (which pulled in libmozjs-102-0) on Ubuntu 22.04 LTS and successfully completed Test Case 1 and Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs I installed libmozjs-102-0 102.6.0-0ubuntu0.22.10.1 on Ubuntu 22.10 and successfully completed Test Case 1 and Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003387] Re: ubuntu-desktop-minimal should depend on cryptsetup, lvm2
Marking all packages as 'auto' like that is not supported. Besides cryptsetup and lvm2, there are several other packages that are available for the installer and only kept on the system if they are needed: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/ship-live The installer also includes support for many languages but only English and the configured language is kept on the installed system. We will likely close this bug since this is intended behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2003387 Title: ubuntu-desktop-minimal should depend on cryptsetup, lvm2 Status in ubuntu-meta package in Ubuntu: New Bug description: The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on everything needed for a functioning desktop / server installation respectively. Well, almost everything. Two packages that they don't depend on, but should, or at least it should recommend them are: - cryptsetup - lvm2 The reason is that if Ubuntu was installed with disk encryption and/or LVM turned on, these packages are essential. The system won't even boot without cryptsetup, for example (found this out the hard way). The release of Ubuntu you are using: 22.10 The version of the package you are using: ubuntu-desktop-minimal 1.497 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003387] Re: ubuntu-desktop-minimal should depend on cryptsetup, lvm2
Could you provide exact steps for how you installed Ubuntu where it wasn't able to boot? ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2003387 Title: ubuntu-desktop-minimal should depend on cryptsetup, lvm2 Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on everything needed for a functioning desktop / server installation respectively. Well, almost everything. Two packages that they don't depend on, but should, or at least it should recommend them are: - cryptsetup - lvm2 The reason is that if Ubuntu was installed with disk encryption and/or LVM turned on, these packages are essential. The system won't even boot without cryptsetup, for example (found this out the hard way). The release of Ubuntu you are using: 22.10 The version of the package you are using: ubuntu-desktop-minimal 1.497 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
I verified that this regression also shows in Fedora 37. I verified there because Fedora and Ubuntu ship a patch to enable transparency in gnome-terminal; gnome-terminal upstream does not have that feature. I also verified that this regression was introduced in mutter 43.1. (transparency works in 43.0 but not in 43.1). With that information, I found an upstream bug report. The initial response was that the new behavior conforms to the specification and it was suggested to maximize gnome-terminal instead of using fullscreen mode if you want this feature. ** Changed in: mutter (Ubuntu) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2520 https://gitlab.gnome.org/GNOME/mutter/-/issues/2520 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2520 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2003104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
Thank you for reporting this bug and helpinig to make Ubuntu better. I'm going to collect more data to report this issue upstream since this issue is blocking us from being able to successfully SRU 43.2 to Ubuntu 22.10. ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Tags added: regression-release ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
Sergio, you mean that it looks like this bug was triggered when your system updated from mutter 43.0-1ubuntu5 to https://launchpad.net/ubuntu/+source/mutter/43.2-4ubuntu1 right? ** Summary changed: - Transparency ignored in full screen mode + gnome-terminal transparency ignored in full screen mode ** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002926] Re: GNOME Console doesn't copy last line
** Description changed: Impact -- - GNOME Console 43 has switched to GTK4 and the last line of text isn't being copied. + GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - + Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. + + All the lines should be copied including the final line. What Could Go Wrong --- + This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). + + Neither GNOME Builder nor GNOME Console are included by default in any + Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default + terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was + a blocker for that happening. ** Changed in: vte2.91 (Ubuntu Kinetic) Status: New => In Progress ** Description changed: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - - Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. + Install the updated vte packages and gnome-console. - All the lines should be copied including the final line. + Run the Console app. + + Run this command: + cat /etc/os-release + + Copy a selection that includes the end of the line. One easy way to do + this is to triple-click the line. Then right-click and choose Copy. + + Then right-click and choose Paste. + + All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Committed Status in vte2.91 source package in Kinetic: In Progress Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002926] [NEW] GNOME Console doesn't copy last line
Public bug reported: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. ** Affects: vte2.91 (Ubuntu) Importance: High Status: Fix Committed ** Affects: vte2.91 (Ubuntu Kinetic) Importance: High Status: In Progress ** Tags: kinetic ** Also affects: vte2.91 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: vte2.91 (Ubuntu Kinetic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Committed Status in vte2.91 source package in Kinetic: In Progress Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999100] Re: Update gnome-characters to 43.1
I'm removing the tag since glib2.0 is ready now. ** Tags removed: block-proposed block-proposed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1999100 Title: Update gnome-characters to 43.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Kinetic: Fix Committed Bug description: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999098] Re: Update glib to 2.74.3
The autopkgtests all pass now. I installed glib 2.74.3-0ubuntu1, restarted my computer and ensured that epiphany-browser, the file browser and the terminal all appear to work correctly. I also installed gnome-characters 43.1-0ubuntu1 and verified that I was able to search for the moose emoji and copy it. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they are functionally equivalent. Ubuntu 23.04 will get newer glib versions before 23.04 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
The Device Security panel has been simplified in GNOME 44 Alpha and Ubuntu 23.04 no longer disables showing the panel. https://launchpad.net/ubuntu/+source/gnome-control- center/1:44~alpha-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Changed in: mozjs102 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gjs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002575] Re: Update nautilus to 43.2
** Changed in: nautilus (Ubuntu Kinetic) Status: Triaged => In Progress ** Description changed: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Nautilus 43 switched to GTK4 which was a major change for a complex app. Many regressions have been fixed in the new point release updates. Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update - Ensure that Nautilus still works well + Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus + Run Nautilus and ensure that it still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. - As a component of GNOME core, there is a micro-release exception for + As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2002575 Title: Update nautilus to 43.2 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Nautilus 43 switched to GTK4 which was a major change for a complex app. Many regressions have been fixed in the new point release updates. Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002845] [NEW] debhelper 13.11.4ubuntu1 broke dh-translations
Public bug reported:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' --targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line
518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
** Affects: debhelper (Ubuntu)
Importance: Critical
Status: Triaged
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: gnome-text-editor (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: pkgbinarymangler (Ubuntu)
Importance: Undecided
Status: Triaged
** Tags: block-proposed ftbfs lunar
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-text-editor (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pkgbinarymangler (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** Changed in: gnome-text-editor (Ubuntu)
Status: New => Triaged
** Changed in: pkgbinarymangler (Ubuntu)
Status: New => Triaged
** Tags added: ftbfs
** Description changed:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
+
+ https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
- jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
- No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
+ jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
+ No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
- --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
- sub(\"-pot\"; \"\")'") failed: No such file or directory
+ --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
+ sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
- --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
- sub(\"-pot\"; \"\")'" returned exit code 25
+ --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
+ sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Triaged
Status in gnome-control-center package in Ubuntu:
Triaged
Status in gnome-text-editor package in Ubuntu:
Triaged
Status in pkgbinarymangler package in Ubuntu:
Triaged
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
[Desktop-packages] [Bug 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first
This is fixed in gnome-control-center 44 Alpha. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Committed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2277 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2277 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2277 Importance: Unknown Status: Unknown ** Tags added: focal jammy kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871320 Title: Switching alert sound will not take effect unless you switch to Default alert first Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: I installed April 5th's nightly build, of Ubuntu Focal Fossa (development branch). Description: Ubuntu Focal Fossa (development branch) Release: 20.04 The issue is, Whichever the notification sound we choose after default, only that sound will take effect. Directly changing to another type of alert sound will not take effect. To reproduce the problem, 1. Open terminal, 2. Open sound settings, initially it will be "default". Change that to some other alert sound, say, "Drip". 3. Switch to terminal and press backspace, you will hear "Drip". 4. Switch to sound settings, this time select "Glass". 5. Switch to terminal and press backspace, here is the issue. You will not hear "Glass". You will still hear "Drip". 6. Switch to sound settings, now select default first and then select "Glass". 7. Switch to terminal and press backspace, now you will hear "Glass". So to summarize, if you want to change the alert sound, first you have to switch back to "Default" and then only whichever other alert sound you select, will take effect. Since the release time is near, I thought it would be helpful to fix this before release. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1871320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997996] Re: when in Trash, no dedicated top banner
This was an intentional change. https://gitlab.gnome.org/GNOME/nautilus/-/commit/5b954ee5354 Therefore, I'm closing this bug. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1997996 Title: when in Trash, no dedicated top banner Status in nautilus package in Ubuntu: Invalid Bug description: Hi, Ubuntu 22.10 here. When in Trash, Nautilus no longer displays a top banner in main window offering to empty or restore. Files attached : screenshots from 22.10 and 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002575] Re: Update nautilus to 43.2
** Description changed: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) + + Nautilus 43 switched to GTK4 which was a major change for a complex app. + Many regressions have been fixed in the new point release updates. + + Test Case 0 + --- + Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2002575 Title: Update nautilus to 43.2 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Nautilus 43 switched to GTK4 which was a major change for a complex app. Many regressions have been fixed in the new point release updates. Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988622] Re: gnome-sushi stopped working
** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988622 Title: gnome-sushi stopped working Status in nautilus package in Ubuntu: Fix Released Bug description: Click a file, press space bar: nothing happens, sushi does not start. It was working few days ago. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-sushi 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:48:06 2022 InstallationDate: Installed on 2022-08-11 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-sushi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995311] Re: seahorse-nautilus not working on ubuntu 22.10
seahorse-nautilus needs to be ported from GTK3 to GTK4 before it can be reintroduced to Ubuntu ** Package changed: nautilus (Ubuntu) => seahorse-nautilus (Ubuntu) ** Changed in: seahorse-nautilus (Ubuntu) Importance: Undecided => High ** Changed in: seahorse-nautilus (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1995311 Title: seahorse-nautilus not working on ubuntu 22.10 Status in seahorse-nautilus package in Ubuntu: Triaged Bug description: impossible to install seahorse-nautilus on ubuntu 22.10 so I cannot encrypt/decrypt files (except with line commands) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/1995311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995412] Re: Expandable folders option disappeared
This feature was added to Nautilus 44 Alpha which is expected to be part of Ubuntu 23.04 in April. ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1995412 Title: Expandable folders option disappeared Status in nautilus package in Ubuntu: Fix Committed Bug description: Ubuntu 22.10 nautilus: Installed: 1:43.0-1ubuntu1 Nautilus click on 'Preferences' Expandable folders option was present in Ubuntu 22.04 now disappeared in Ubuntu 22.10. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 1 18:54:22 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 879)' InstallationDate: Installed on 2022-10-25 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002575] [NEW] Update nautilus to 43.2
Public bug reported: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: nautilus (Ubuntu) Importance: High Status: Fix Committed ** Affects: nautilus (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: kinetic upgrade-software-version ** Also affects: nautilus (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: nautilus (Ubuntu Kinetic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2002575 Title: Update nautilus to 43.2 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999100] Re: Update gnome-characters to 43.1
Yes, let's wait for glib2.0 to be ready first. I'm setting the block tag now. ** Tags added: block-proposed block-proposed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1999100 Title: Update gnome-characters to 43.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Kinetic: Fix Committed Bug description: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999335] Re: Please remove vte from Ubuntu
It can't be removed from Debian until someone ports debian-installer away from GTK2. :( ** Tags removed: lucid ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1999335 Title: Please remove vte from Ubuntu Status in vte package in Ubuntu: New Bug description: The vte source package is an old version of vte that hasn't been maintained in many years. The current version is packaged with source package name vte2.91 vte is still around in Debian because debian-installer has not yet switched to GTK3. However, Ubuntu no longer supports debian-installer and nothing in Ubuntu uses the old vte. Therefore, please remove vte from Ubuntu. $ reverse-depends src:vte $ reverse-depends -b src:vte No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1999335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Marc, 102.6 was officially released today, so I've gone ahead and updated my jammy mozjs branch for it. I added the CVEs you mentioned and found one more I found from 102.4. I don't see any new ones for 102.6 I've also created a ubuntu/102/kinetic branch for mozjs102 for kinetic. Since it doesn't have the gjs major update issue, I believe it could be pushed sooner than jammy. For Jammy, I think the general plan is for this update to be built in security-proposed and then published/copied to jammy-proposed for wider testing before being pushed to jammy-security. My understanding is that the Ubuntu Desktop and Ubuntu SRU teams have come to an agreement that we will test all the gnome-shell extensions that are available in the official Ubuntu repositories (for 22.04 LTS and later). Extensions installed outside of the official Ubuntu repositories are unsupported, just like anything that is user-installed outside of Ubuntu. However, we aren't aware of any likely breakage for any GNOME Shell extensions caused by this proposed update. There is no formal API for GNOME Shell extensions which allows extensions to have tremendous power but it's easily possible for an extension to break GNOME Shell so that it's not possible for GNOME Shell to run correctly or even start. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Confirmed Status in mozjs102 package in Ubuntu: Confirmed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997481] Re: Update gnome-shell to 43.1
I installed gnome-shell 43.1-0ubuntu1 on Ubuntu 22.10 and successfully completed all 3 test cases (ensuring all the GNOME sessions still work, ensuring all the packaged GNOME Shell extensions still work, and ensuring the captive portal popup still works). ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1997481 Title: Update gnome-shell to 43.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
I installed gnome-shell 43.1-0ubuntu1 on Ubuntu 22.10. After logging in and logging out, I verified that the login page popup correctly showed and worked when I connected to a captive portal. The popup correctly did not show when I connected to a Wifi point that didn't require logging in. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: Fix Committed Bug description: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 Original Bug Report --- After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1995134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998286] Re: Release mutter 42.7 to jammy
I think we'll likely wait for 42.8 instead, expected around January 7, because of expected SRU team availability around the end of the year. Sorry for the delay. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.7 to jammy Status in mutter package in Ubuntu: Triaged Bug description: Release mutter 42.7 to jammy At least 42.6 is required to fix bug 1961563 (Xilinx Wayland support) and bug 1988256 https://gitlab.gnome.org/GNOME/mutter/-/tags/42.6 https://gitlab.gnome.org/GNOME/mutter/-/tags/42.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999335] [NEW] Please remove vte from Ubuntu
Public bug reported: The vte source package is an old version of vte that hasn't been maintained in many years. The current version is packaged with source package name vte2.91 vte is still around in Debian because debian-installer has not yet switched to GTK3. However, Ubuntu no longer supports debian-installer and nothing in Ubuntu uses the old vte. Therefore, please remove vte from Ubuntu. $ reverse-depends src:vte $ reverse-depends -b src:vte No reverse dependencies found ** Affects: vte (Ubuntu) Importance: Undecided Status: New ** Tags: lucid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1999335 Title: Please remove vte from Ubuntu Status in vte package in Ubuntu: New Bug description: The vte source package is an old version of vte that hasn't been maintained in many years. The current version is packaged with source package name vte2.91 vte is still around in Debian because debian-installer has not yet switched to GTK3. However, Ubuntu no longer supports debian-installer and nothing in Ubuntu uses the old vte. Therefore, please remove vte from Ubuntu. $ reverse-depends src:vte $ reverse-depends -b src:vte No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1999335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999098] Re: Update glib to 2.74.3
** Description changed: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. + + Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they + are functionally equivalent. Ubuntu 23.04 will get newer glib versions + before 23.04 is released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they are functionally equivalent. Ubuntu 23.04 will get newer glib versions before 23.04 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Also affects: firefox (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gtk (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gtk (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gtk4 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Kinetic) Importance: Undecided Status: New ** No longer affects: chromium-browser (Ubuntu Jammy) ** No longer affects: chromium-browser (Ubuntu Kinetic) ** No longer affects: firefox (Ubuntu Jammy) ** No longer affects: firefox (Ubuntu Kinetic) ** No longer affects: gnome-shell (Ubuntu Jammy) ** No longer affects: gnome-shell (Ubuntu Kinetic) ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Jammy) ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Kinetic) ** No longer affects: xdg-desktop-portal-gtk (Ubuntu Jammy) ** No longer affects: xdg-desktop-portal-gtk (Ubuntu Kinetic) ** Changed in: gtk4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gtk4 (Ubuntu Jammy) Status: New => Triaged ** Changed in: gtk4 (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: gtk4 (Ubuntu Kinetic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: New Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: New Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999167] Re: Backport two patches from the GTK 4.6 maintenance branch
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 ** This bug has been marked a duplicate of bug 1949340 [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1999167 Title: Backport two patches from the GTK 4.6 maintenance branch Status in gtk4 package in Ubuntu: New Bug description: This is a request to update the libgtk-4-1 package to include two important patches merged upstream into the gtk-4-6 stable branch: * https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4714 * https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5288 See https://gitlab.gnome.org/GNOME/gtk/-/issues/2638#note_1612970 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1999167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999100] [NEW] Update gnome-characters to 43.1
Public bug reported: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. ** Affects: gnome-characters (Ubuntu) Importance: Low Status: Fix Released ** Affects: gnome-characters (Ubuntu Kinetic) Importance: Low Status: In Progress ** Tags: kinetic upgrade-software-version ** Also affects: gnome-characters (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-characters (Ubuntu Kinetic) Importance: Undecided => Low ** Changed in: gnome-characters (Ubuntu Kinetic) Status: New => In Progress ** Description changed: + NOTE TO SRU TEAM + + Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. + Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. - Test Case 2 (Extra) + Test Case 2 --- - If the glib2.0 SRU is available, install glib 2.74.3-0ubuntu1 and then complete Test Case 3 (Extra) from https://launchpad.net/bugs/1999098 + Open the Characters app. + Use the search feature to search for "moose" + A moose emoji should show up. This is one of the new Emoji 15. + https://blog.emojipedia.org/whats-new-in-unicode-15-0/ + + (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1999100 Title: Update gnome-characters to 43.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Kinetic: In Progress Bug description: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME
[Desktop-packages] [Bug 1999098] [NEW] Update glib to 2.74.3
Public bug reported: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. ** Affects: glib2.0 (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: glib2.0 (Ubuntu Kinetic) Importance: Medium Status: In Progress ** Tags: kinetic upgrade-software-version ** Also affects: glib2.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu Kinetic) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Kinetic) Importance: Undecided => Medium ** Description changed: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. + + Other Info + -- + Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 + + glib and gnome-characters are the only 2 late pieces that the Ubuntu + Desktop team plans to SRU for Ubuntu 22.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop,
[Desktop-packages] [Bug 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - utf8proc node-unicode-property-aliases node-unicode-property-aliases-ecmascript node-unicode-property-value-aliases node-unicode-property-value-aliases-ecmascript node-unicode-data which will start a small transition node-esutils node-json5 node-regenerate-unicode-properties node-regexpu-core node-regjsparser maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
** Changed in: tiff (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: Fix Released Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999062] [NEW] orc build test failure on arm64
Public bug reported: . ** Affects: orcformat Importance: Unknown Status: Unknown ** Affects: orc (Ubuntu) Importance: High Status: New ** Tags: ftbfs lunar rls-ll-incoming update-excuse ** Changed in: orc (Ubuntu) Importance: Undecided => High ** Bug watch added: gitlab.freedesktop.org/gstreamer/orc/-/issues #45 https://gitlab.freedesktop.org/gstreamer/orc/-/issues/45 ** Also affects: orcformat via https://gitlab.freedesktop.org/gstreamer/orc/-/issues/45 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orc in Ubuntu. https://bugs.launchpad.net/bugs/1999062 Title: orc build test failure on arm64 Status in ORC: Unknown Status in orc package in Ubuntu: New Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/orcformat/+bug/1999062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995245] Re: Update gnome-remote-desktop to 43.2
** Description changed: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop - except for the "New Audio Forwarding Feature" test case. + except for the "New Audio Forwarding Feature" test case and the "Basic + VNC Test Case (for Ubuntu 22.04 LTS only) What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case and the "Basic VNC Test Case (for Ubuntu 22.04 LTS only) What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998966] [NEW] Update gnome-remote-desktop to 42.7
Public bug reported: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release, 42.4: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-remote-desktop (Ubuntu) Importance: High Status: Fix Released ** Affects: gnome-remote-desktop (Ubuntu Jammy) Importance: High Status: In Progress ** Tags: jammy upgrade-software-version ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1998966 Title: Update gnome-remote-desktop to 42.7 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release, 42.4: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1998966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995245] Re: Update gnome-remote-desktop to 43.2
** Changed in: gnome-remote-desktop (Ubuntu Kinetic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995245] Re: Update gnome-remote-desktop to 43.2
** Summary changed: - Update gnome-remote-desktop to 43.1 + Update gnome-remote-desktop to 43.2 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Released => Fix Committed ** Description changed: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- - desktop/-/compare/43.0...43.1 + desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283397] Re: videos only take up 1/4 (one quarter/fourth) of the window
Ubuntu GNOME 14.04 LTS is no longer supported. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. If you are still experiencing this issue on a supported Ubuntu release like Ubuntu 22.04 LTS, please file a new bug. ** Changed in: gnome-sushi (Ubuntu) Status: Confirmed => Invalid ** No longer affects: gnome-sushi ** Changed in: totem (Ubuntu) Status: Confirmed => Invalid ** Package changed: totem (Fedora) => gnome-sushi ** No longer affects: gnome-sushi ** Project changed: totem => gnome-sushi ** No longer affects: gnome-sushi ** Package changed: gnome-sushi (Fedora) => gnome-sushi ** No longer affects: gnome-sushi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1283397 Title: videos only take up 1/4 (one quarter/fourth) of the window Status in gnome-sushi package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: On Lenovo Yoga 2 Pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1283397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" - mkdir -p tarballs; cd tarballs + mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Confirmed Status in mozjs102 package in Ubuntu: Confirmed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
I installed the Chromium snap and verified that the show in folder feature doesn't highlight the downloaded file. I installed xdg-desktop- portal 1.6.0-1ubuntu2, logged out and logged back in and verified that the show in folder feature now works. I installed the Firefox snap (from the stable channel). The show in folder feature did not work at all with either version of xdg-desktop- portal. I had difficulty testing whether the Wallpaper portal works. I didn't see Wallpaper in the portal-test snap. I ended up installing the NautilusDevel Flatpak from GNOME Nightly. I know that Nautilus 43+ only uses the Wallpaper portal to set the Wallpaper. I successfully used NautilusDevel to set my Wallpaper. I believe this fix is verified now. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: Fix Committed Bug description: [Impact] * The OpenDirectory method of the OpenURI portal opens a file manager window showing the requested directory, but it doesn't select the passed file in that directory. This affects all users of this API, particularly the chromium and firefox snaps. * This is an upstream bug that was fixed in later versions of xdg- desktop-portal, this SRU backports the fix to the 1.6 series that's in focal. [Test Plan] * On a focal machine, install the chromium snap, launch it and download any file from a web page (from e.g. https://kernel.org/) * Once the download is complete, browse to chrome://downloads * Click the "Show in folder" link for the downloaded file, this opens a Nautilus window showing the contents of the default downloads directory (e.g. $HOME/Downloads) * Expected result: the downloaded file is selected in the Nautilus window * Actual result without the patch: no file is selected * Similarly for the firefox snap, downloading a file and clicking the "Show in Folder" button in the downloads panel should select the downloaded file * General functionality of all other portals (including the wallpaper portal) should be thoroughly tested to look out for regressions [Where problems could occur] * The backported patches potentially affect other portals (not just OpenURI), including the Wallpaper portal. * Therefore the functionality of all other portals should be thoroughly tested to ensure there are no functional regressions. [Other Info] * The firefox snap wasn't using this API before version 103.0, which at the time of writing this hasn't officially been released yet (it is due for release tomorrow, 2022-07-26). In the meantime it can be installed from the candidate channel. [Original Description] This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945856] Re: Need update to 3.21.8 for ARM
Ubuntu 22.04 LTS has hplip 3.21.12 ** Changed in: hplip (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1945856 Title: Need update to 3.21.8 for ARM Status in hplip package in Ubuntu: Fix Released Bug description: Need update to 3.21.8 for ARM because in this version HP added HP Smart Tank 500 and more printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997979] Re: Merge grilo-plugins 0.3.15-1 from Debian unstable
** Changed in: grilo-plugins (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems
I thought the fix was worth cherry-picking for Kinetic. It should land in Lunar when 43.2 is released, possibly as early as next week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998017 Title: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Kinetic: Fix Committed Status in gnome-shell source package in Lunar: Confirmed Bug description: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6107 Without that fix it is impossible to use same system shortcuts (Alt+Shift, etc.) in main system and in VM in virt-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems
Thanks for fixing the bug status! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998017 Title: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Kinetic: Fix Committed Status in gnome-shell source package in Lunar: Confirmed Bug description: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6107 Without that fix it is impossible to use same system shortcuts (Alt+Shift, etc.) in main system and in VM in virt-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
** Description changed: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 - Other Info - -- - There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. And when it doesn't work, it opens a popup window pointing to help.ubuntu.com - - See https://launchpad.net/bugs/1998082 - - This is not really a regression in this update. The unreliable - connectivity check also affected Ubuntu 22.10 before this update but - users would never see a popup window. - Original Bug Report --- - - After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer - recognizes captive portals. + After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: In Progress Bug description: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 Original Bug Report --- After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
The RT ticket has been fixed so I'm closing this bug.
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in NetworkManager:
New
Status in gnome-shell package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
Original Report
---
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
Workaround
--
sudo apt install network-manager-config-connectivity-debian
sudo apt remove network-manager-config-connectivity-ubuntu
sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993834] Re: Update evolution-data-server to 3.46.1
I installed evolution-data-server 3.46.1-0ubuntu1 on Ubuntu 22.10 I completed the Calendar test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar I also installed Evolution 3.46.0 and verified that my Google email and calendar still work. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Kinetic: Fix Committed Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980408] Re: Update glib to 2.72.4
The autopkgtests completed successfully. I installed glib 2.72.4-0ubuntu1 on Ubuntu 22.04 LTS. I logged out and logged back in and verified that the desktop works and the terminal, file browser, and epiphany-browser work normally. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
** Description changed: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 Other Info -- - There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. See - https://discourse.ubuntu.com/t/network-manager-connectivity-check-problem/26729 + There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. And when it doesn't work, it opens a popup window pointing to help.ubuntu.com + + See https://launchpad.net/bugs/1998082 + + This is not really a regression in this update. The unreliable + connectivity check also affected Ubuntu 22.10 before this update but + users would never see a popup window. Original Bug Report --- After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: In Progress Bug description: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 Other Info -- There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. And when it doesn't work, it opens a popup window pointing to help.ubuntu.com See https://launchpad.net/bugs/1998082 This is not really a regression in this update. The unreliable connectivity check also affected Ubuntu 22.10 before this update but users would never see a popup window. Original Bug Report --- After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
** Tags added: kinetic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in NetworkManager:
New
Status in gnome-shell package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Original Report
---
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
Workaround
--
sudo apt install network-manager-config-connectivity-debian
sudo apt remove network-manager-config-connectivity-ubuntu
sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935663] Re: The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4+git20200505-0ubuntu18.04.2 is to be installed E: E
I believe this bug is caused because you are using Ubuntu 18.04 LTS but you have set up apt repositories from a PPA (or something else) that are incompatible with Ubuntu 18.04 LTS. Because your issue isn't in the official Ubuntu 18.04 LTS packages, I am closing this bug. ** Changed in: mutter (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1935663 Title: The following packages have unmet dependencies: gsettings-desktop- schemas : Breaks: mutter (< 3.31.4) but 3.28.4+git20200505-0ubuntu18.04.2 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Status in mutter package in Ubuntu: Invalid Bug description: The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4+git20200505-0ubuntu18.04.2 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4+git20200505-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-67.75~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 9 11:23:54 2021 InstallationDate: Installed on 2021-02-27 (131 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: mutter UpgradeStatus: Upgraded to bionic on 2021-03-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
I reported this issue to NetworkManager upstream. The upstream developer
suggested that this is a problem with the Ubuntu connectivity checker
web service so I opened RT ticket C154876 for it.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in NetworkManager:
New
Status in gnome-shell package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Original Report
---
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
Workaround
--
sudo apt install network-manager-config-connectivity-debian
sudo apt remove network-manager-config-connectivity-ubuntu
sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1149
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1149
** Also affects: gnome-shell via
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1149
Importance: Unknown
Status: Unknown
** Description changed:
- Hotspot Login window [gnome-shell-portal-helper] randomly opens with
- https://help.ubuntu.com
+ Original Report
+ ---
+ Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
+
+ Workaround
+ --
+ sudo apt install network-manager-config-connectivity-debian
+ sudo apt remove network-manager-config-connectivity-ubuntu
+ sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
- b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
- b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
- b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
- b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
+ b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
+ b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
+ b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
- SHELL=/bin/bash
- XDG_RUNTIME_DIR=
- PATH=(custom, no user)
- LANGUAGE=en_AU:en
- LANG=en_AU.UTF-8
+ SHELL=/bin/bash
+ XDG_RUNTIME_DIR=
+ PATH=(custom, no user)
+ LANGUAGE=en_AU:en
+ LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Project changed: gnome-shell => network-manager
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in NetworkManager:
Unknown
Status in gnome-shell package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Original Report
---
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
Workaround
--
sudo apt install network-manager-config-connectivity-debian
sudo apt remove network-manager-config-connectivity-ubuntu
sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems
*** This bug is a duplicate of bug 1997481 *** https://bugs.launchpad.net/bugs/1997481 I am marking this a duplicate of https://launchpad.net/bugs/1997481 since gnome-shell 43.1 includes this fix and I've already prepared the Stable Release Update for Ubuntu 22.10 using that bug number in the changelog. ** Tags removed: fixed-in-gnome-shell-43.2 ** Tags added: fixed-in-gnome-shell-43.1 ** Also affects: gnome-shell (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: gnome-shell (Ubuntu Kinetic) Status: New => In Progress ** This bug has been marked a duplicate of bug 1997481 Update gnome-shell to 43.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998017 Title: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: In Progress Bug description: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6107 Without that fix it is impossible to use same system shortcuts (Alt+Shift, etc.) in main system and in VM in virt-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998099] Re: gnome-shell doesn't recognise Inhibit shortcuts permission
*** This bug is a duplicate of bug 1997481 *** https://bugs.launchpad.net/bugs/1997481 ** This bug is no longer a duplicate of bug 1998017 inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems ** This bug has been marked a duplicate of bug 1997481 Update gnome-shell to 43.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998099 Title: gnome-shell doesn't recognise Inhibit shortcuts permission Status in gnome-shell package in Ubuntu: New Bug description: When trying to use a program that tries to make use of the `Inhibit Shortcuts` permission, for example a virtual machine program like virt-manager, gnome-shell ignores the permission and the shortcuts you press which should be inhibited/changed to do something else by the program, activate the gnome-shell's system shortcut instead. This means that when I am trying to alt+tab inside my virtual machine, it instead alt tabs to a different window on my host rather than on my guest OS. I believe this problem is fixed on gnome-shell 43.1. Could you please update gnome-shell43.1 to fix this issue. System Info: OS Name: Ubuntu 22.10 GNOME Version 43.0 Windowing System: Wayland Gnome Shell: 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
NetworkManager's connectivity check is very flaky on Ubuntu 22.10 now.
You can force retries by running this command in a terminal.
nmcli networking connectivity check
I don't understand why there is a redirect to help.ubuntu.com since that
website isn't in the NetworkManager or GNOME Shell or webkit2gtk source
code. Maybe it's a configuration issue with http://connectivity-
check.ubuntu.com ? (In a normal web browser, that site returns a blank
or nonexistant page with status code 204, as intended.)
I also tried NetworkManager 1.40.4 from Ubuntu 23.04 but it didn't fix
this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in gnome-shell package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in gnome-shell package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
** Description changed: + Impact + -- + + Test Case + - + Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell + + What Could Go Wrong + --- + This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 + + Other Info + -- + There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. See + https://discourse.ubuntu.com/t/network-manager-connectivity-check-problem/26729 + + Original Bug Report + --- + After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 - - This may be normal because of the environment, but it is the best I have to go on now. + This may be normal because of the environment, but it is the best I have + to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) ** Description changed: Impact -- + Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. + + This popup window was broken and doesn't currently show up in Ubuntu + 22.10. Test Case - Complete Test Case 3 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- This fix is included in the upstream gnome-shell 43.1. For more information about this update, see LP: #1997481 Other Info -- There appears to be a reliability issue with Ubuntu's default network connectivity provider, which will cause this popup to show up much more frequently than it ought to. See https://discourse.ubuntu.com/t/network-manager-connectivity-check-problem/26729 Original Bug Report --- After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) ** Description changed: Impact -- Ubuntu is supposed to show a browser popup window when a user connects to a network with a "captive portal". The popup window makes it easy for the user to log in or accept the user agreement. This popup window was broken and doesn't currently show up in Ubuntu 22.10. Test
[Desktop-packages] [Bug 1997481] Re: Update gnome-shell to 43.1
** Changed in: gnome-shell (Ubuntu Kinetic) Status: Triaged => In Progress ** Description changed: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell + + Other Info + -- + gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1997481 Title: Update gnome-shell to 43.1 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Kinetic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
** Changed in: gnome-shell (Ubuntu Kinetic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Kinetic: In Progress Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1995134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
I adjusted your changelog entry to include the remaining differences in the changelog message. I think that makes things more clear to the next person who will work on merging new versions. I did a second upload because we accidentally missed the symbols file update when we manually merged later. I am unsubscribing ubuntu-sponsors now because I have uploaded this to Ubuntu. Feel free to resubscribe if you have something else that needs to be sponsored. I saw that you opened a Debian bug for the security patch. Could you forward the patch there too? ** Changed in: tiff (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: Fix Committed Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997481] [NEW] Update gnome-shell to 43.1
Public bug reported: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-shell (Ubuntu) Importance: High Status: Fix Committed ** Affects: gnome-shell (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: kinetic upgrade-software-version ** Also affects: gnome-shell (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Kinetic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1997481 Title: Update gnome-shell to 43.1 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Kinetic: Triaged Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997338] Re: libatk-bridge2.0-0 uninstallable on i386
Thank you for reporting this issue. This seems to be affecting a lot more stuff than just libatk-bridge2.0-0 and more architectures than just i386. See https://lists.ubuntu.com/archives/ubuntu- devel/2022-November/042352.html ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Changed in: dbus (Ubuntu) Importance: Undecided => Critical ** Changed in: at-spi2-core (Ubuntu) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** No longer affects: at-spi2-core (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1997338 Title: libdbus-1-3 uninstallable on autopkgtest Status in dbus package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib > Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib > Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib > Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib > Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib > Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 @un uH > (>= 7.28.0) Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is not going to be installed libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libpu
[Desktop-packages] [Bug 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy
Debian says the jbig bug isn't a critical security issue: https://security-tracker.debian.org/tracker/CVE-2022-1210 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy Status in tiff package in Ubuntu: In Progress Bug description: The versions in Trusty, Xenial, Bionic, Focal and Jammy may be vulnerable to all CVEs below. Debian released an advisory on March 24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993834] Re: Update evolution-data-server to 3.46.1
** Also affects: evolution-data-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu) Status: In Progress => Fix Committed ** Changed in: evolution-data-server (Ubuntu Kinetic) Status: New => In Progress ** Changed in: evolution-data-server (Ubuntu Kinetic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade
** Also affects: gnome-shell (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Kinetic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Kinetic: Triaged Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1995134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1995457 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags removed: regression-release ** Changed in: gnome-calendar (Ubuntu) Importance: Critical => High ** No longer affects: ubuntu-gnome ** Changed in: gnome-calendar (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
** Also affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic regression-release ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in Ubuntu GNOME: New Status in gnome-calendar package in Ubuntu: New Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993308] Re: Update gnome-calendar to 43.1
I installed gnome-calendar 43.1-0ubuntu1 and successfully completed the test case. I noticed that dragging an event to a different time slot didn't save to the correct time, depending on the system timezone. I reported that issue to GNOME. I verified that the issue also affects Calendar 43.0 currently in Kinetic so this is not a regression. Therefore, I am marking this SRU as verified. https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/903 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #903 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/903 ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 Status in gnome-calendar package in Ubuntu: Fix Committed Status in gnome-calendar source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995245] [NEW] Update gnome-remote-desktop to 43.1
Public bug reported: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.1 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-remote-desktop (Ubuntu) Importance: High Status: Fix Committed ** Affects: gnome-remote-desktop (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: upgrade-software-version ** Also affects: gnome-remote-desktop (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Kinetic) Status: New => Triaged ** Changed in: gnome-remote-desktop (Ubuntu Kinetic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.1 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.1 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993831] Re: gnome-shell does not contain gjs dependence
After I started typing this comment, upstream left a later comment "gnome-shell includes some small external D-Bus services - namely org.gnome.Shell.Extensions.service, org.gnome.Shell.Notifications.service and org.gnome.Shell.Screencast.service - that require the standalone gjs executable. The package that provides /usr/bin/gjs should therefore be a dependency of the package that includes those services (gnome- shell/gnome-shell-common)." Having working notifications and screencasting is important, so I'm reopening this bug. Thank you for taking the time to help make Ubuntu better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993831 Title: gnome-shell does not contain gjs dependence Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I updated from Ubuntu 22.04 to Ubuntu 22.10 and I had an issue with GNOME shell "Extensions" app. I replaced "Extensions" (gnome-shell-extension-prefs) with Flatpak version of it from Flathub using GNOME "Software" center. After this, I'm not sure, I might have used the "sudo apt auto-remove" command. After these changes, Flatpak version of the "Extensions" app gave an error: (https://github.com/flathub/org.gnome.Extensions/issues/13) After a bit of digging, I realized removing "Extensions" packages also removes gjs dependence. So I installed gjs package and "Extensions" works again. 1) OS OS: Ubuntu 22.10 Desktop: GNOME 2) Package gnome-shell: 43.0-1ubuntu2 gnome-shell-extension-prefs: 43.0-1ubuntu2 3) What you expected to happen Removing the package and installing Flatpak version without any error. 4) What happened instead I replaced the app with Flatpak version and it removed gjs and gnome- shell extension support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993831] Re: gnome-shell does not contain gjs dependence
I am closing this bug. In the upstream report, upstream confirms that gnome-shell itself does not need 'gjs', only the gjs library. The gnome-shell-extension-prefs app packaged as a .deb correctly depends on gjs. A default Ubuntu Desktop install includes gjs. For you to remove gjs, you will have needed to remove the GNOME Characters app and the Desktop Icons NG extension and the ubuntu-desktop metapackage. At that point, you're outside the fully supported Ubuntu Desktop experience. Maybe the Flatpak needs to bundle 'gjs' if it requires gjs. ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993831 Title: gnome-shell does not contain gjs dependence Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I updated from Ubuntu 22.04 to Ubuntu 22.10 and I had an issue with GNOME shell "Extensions" app. I replaced "Extensions" (gnome-shell-extension-prefs) with Flatpak version of it from Flathub using GNOME "Software" center. After this, I'm not sure, I might have used the "sudo apt auto-remove" command. After these changes, Flatpak version of the "Extensions" app gave an error: (https://github.com/flathub/org.gnome.Extensions/issues/13) After a bit of digging, I realized removing "Extensions" packages also removes gjs dependence. So I installed gjs package and "Extensions" works again. 1) OS OS: Ubuntu 22.10 Desktop: GNOME 2) Package gnome-shell: 43.0-1ubuntu2 gnome-shell-extension-prefs: 43.0-1ubuntu2 3) What you expected to happen Removing the package and installing Flatpak version without any error. 4) What happened instead I replaced the app with Flatpak version and it removed gjs and gnome- shell extension support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993834] [NEW] Update evolution-data-server to 3.46.1
Public bug reported: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: In Progress ** Tags: kinetic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: In Progress Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993809] Re: Update gnome-shell to 42.5
** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + Other Info + -- + I also cherry-picked a fix from kinetic: + gsettings org.gnome.settings-daemon.peripherals.mouse + no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop trying to report customizations for that gsettings schema. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993809 Title: Update gnome-shell to 42.5 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- I also cherry-picked a fix from kinetic: gsettings org.gnome.settings-daemon.peripherals.mouse no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop trying to report customizations for that gsettings schema. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: Fix Committed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993809] [NEW] Update gnome-shell to 42.5
Public bug reported: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Fix Released ** Affects: gnome-shell (Ubuntu Jammy) Importance: Medium Status: In Progress ** Tags: jammy upgrade-software-version ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993809 Title: Update gnome-shell to 42.5 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: Fix Committed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs - Prerequisite - - We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS - Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. - Only issue is that mozjs102 was not built for i386 but it's needed. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. ** Changed in: mozjs102 (Ubuntu) Status: New => Confirmed ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Confirmed Status in mozjs102 package in Ubuntu: Confirmed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. + + Updating mozjs in stable Ubuntu releases was recommended when Ubuntu + first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. Only issue is that mozjs102 was not built for i386 but it's needed. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: New Status in mozjs102 package in Ubuntu: New Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. Only issue is that mozjs102 was not built for i386 but it's needed. I
[Desktop-packages] [Bug 1993308] Re: Update gnome-calendar to 43.1
** Description changed: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - + Complete the test case from + https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 Status in gnome-calendar package in Ubuntu: In Progress Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993308] [NEW] Update gnome-calendar to 43.1
Public bug reported: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-calendar (Ubuntu) Importance: High Status: Incomplete ** Tags: kinetic upgrade-software-version ** Changed in: gnome-calendar (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. + + Security Impact + --- + I looked through + https://github.com/mozilla/gecko-dev/commits/esr102/js + and searched for referenced bug numbers in + https://www.mozilla.org/en-US/security/advisories/ + for Firefox ESR releases since Ubuntu's 91.10 + + and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE + issued) mentioned at + + https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. + + Initial Testing Done + + I built the packages in my PPA. + Only issue is that mozjs102 was not built for i386 but it's needed. + I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: New Status in mozjs102 package in Ubuntu: New Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. Only issue is that mozjs102 was not built for i386 but it's needed. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS + + Security Sponsoring + --- + sudo apt install git-buildpackage + gbp clone https://salsa.debian.org/gnome-team/gjs + cd gjs + git checkout ubuntu/jammy + gbp buildpackage --git-builder="debuild -S -nc" + + mkdir -p tarballs; cd tarballs + pull-lp-source mozjs102 kinetic + cd .. + gbp clone https://salsa.debian.org/gnome-team/mozjs + cd mozjs + git checkout ubuntu/102/jammy + gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs + # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: New Status in mozjs102 package in Ubuntu: New Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir -p tarballs; cd tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] [NEW] [jammy] Update gjs to 1.74 using mozjs102 102.3
*** This bug is a security vulnerability *** Public security bug reported: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Affects: mozjs102 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy upgrade-software-version ** Summary changed: - Update gjs to 1.74 using mozjs102 102.3 + [jammy] Update gjs to 1.74 using mozjs102 102.3 ** Also affects: mozjs102 (Ubuntu) Importance: Undecided Status: New ** Description changed: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. + mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs + + Prerequisite + + We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: New Status in mozjs102 package in Ubuntu: New Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Prerequisite We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5
** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS Test Case - - sudo apt install budgie-desktop gnome-session gnome-shell-extensions - Install the update. - Log out. - Select your name on the login screen. - Click the gear button to choose a session to log in to. - Finish logging in. + Complete the test case from - Verify that things continue to work well for all these sessions: - Budgie - GNOME - GNOME Classic - Ubuntu - Ubuntu on Xorg + https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5
** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS - - It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Changed in: mutter (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992852] Re: Update gnome-desktop to 42.5
** Changed in: gnome-desktop (Ubuntu) Status: New => Fix Released ** Also affects: gnome-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-desktop (Ubuntu Jammy) Importance: Undecided => Low ** Description changed: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.4 to 42.5 - That's desired because in general we are running 42.5 + That's desired because in general we are running 42.5. + + This update also adds a Croatian (hr) translation. Because we use Ubuntu + language packs, the new translation won't actually be used until the + next language pack update, which is expected shortly before the Ubuntu + 22.04.2 LTS release. Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About - The GNOME Version should be 42.3 + The GNOME Version should be 42.5 What Could Go Wrong --- Because this is part of core GNOME, it falls under the https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 will use gnome-shell to display the version number so that's one less SRU required for future Ubuntu releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1992852 Title: Update gnome-desktop to 42.5 Status in gnome-desktop package in Ubuntu: Fix Released Status in gnome-desktop source package in Jammy: In Progress Bug description: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.4 to 42.5 That's desired because in general we are running 42.5. This update also adds a Croatian (hr) translation. Because we use Ubuntu language packs, the new translation won't actually be used until the next language pack update, which is expected shortly before the Ubuntu 22.04.2 LTS release. Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.5 What Could Go Wrong --- Because this is part of core GNOME, it falls under the https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 will use gnome-shell to display the version number so that's one less SRU required for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1992852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990207 Title: "Night Light unavailable" in Settings (but the quick settings toggle for it works) Status in gnome-control-center: Fix Released Status in Mutter: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: "Night Light unavailable" in Settings (but the quick settings toggle for it works). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993114] Re: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_p
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1993114 Title: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Debian: New Bug description: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Tracking in https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f This is one of the most common gnome-shell crash reports on Ubuntu 22.10 but there are only a few reports of it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1993114/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993114] Re: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_p
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1993114 Title: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Debian: New Bug description: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Tracking in https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f This is one of the most common gnome-shell crash reports on Ubuntu 22.10 but there are only a few reports of it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1993114/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993114] Re: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_p
** Description changed: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Tracking in https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f + + This is one of the most common gnome-shell crash reports on Ubuntu 22.10 + but there are only a few reports of it. ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1993114 Title: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter package in Debian: New Bug description: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_profile → on_cd_device_created Tracking in https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f This is one of the most common gnome-shell crash reports on Ubuntu 22.10 but there are only a few reports of it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1993114/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
@Symax, that patch is already included in Ubuntu 22.10 but I still experience this issue there so that patch doesn't actually fix this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1971632 Title: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Jammy: Fix Committed Bug description: * Impact On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. * Test case Connect a bluetooth headset to the computer, try to change the active profile. The selection should be reflected and the quality match, the pairing and service should be stable * Regression potential The changes are in the bluetooth a2dp/sbc functions so any potential regression would impact the connectivity with bluetooth devices using an a2dp profile (aptX, SBC, AAC). Check with different devices using the previously listed profiles. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1
[Desktop-packages] [Bug 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990207 Title: "Night Light unavailable" in Settings (but the quick settings toggle for it works) Status in gnome-control-center: Fix Released Status in Mutter: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: "Night Light unavailable" in Settings (but the quick settings toggle for it works). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
