[Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4104 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4104 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1918738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4105 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4105 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4105 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1918666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816674] Re: Update-mime-database is getting very slow during apps installation
@Sebastien Sorry for the late reply. I recall that the workaround consisted in adding a random delay to the apt-daily task, so that it would not happen *right* at startup. How exactly this was done, unfortunately, I did write it down :-/ but I think it was adding or creating the file ./system/apt-daily.timer, ensuring that it contained the RandomizedDelaySec directive. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1816674 Title: Update-mime-database is getting very slow during apps installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923459] [NEW] evince doesn't show filename or PDF title on the title bar
Public bug reported: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Captura de pantalla de 2021-04-12 10-42-58.png" https://bugs.launchpad.net/bugs/1923459/+attachment/5486925/+files/Captura%20de%20pantalla%20de%202021-04-12%2010-42-58.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1923459 Title: evince doesn't show filename or PDF title on the title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
It happened after a fresh install of Ubuntu 21.04 Beta on ZFS. Only the updates have been run and I was just installing or starting to install the Virtualbox Guest Additions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
Unfortunately I can't reproduce this bug, even with the 0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2. Also note that the [test case] in the description is wrong, that would be correct with the systemd change made earlier, but that change was reverted upstream and in ubuntu, so the test case steps aren't an accurate indication that the bug is fixed or not. Anyone on this bug able to reproduce the main problem, of key output (e.g. passwords) being printed on the console and visible between login sessions, and/or during shutdown? If not, I think we should consider this bug fixed. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
I'm marking this invalid for systemd (the patch there was reverted) and fix released for plymouth, with the assumption this was fixed with the patch for bug 1817738. If anyone is able to reproduce the problem please add a comment. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Some observations: /etc/bluetooth/main.conf: AutoEnable is set to "true". This causes BT to be enabled upon boot REGARDLESS of any GNOME settings the user might have set. When I set it to "false", I've tried rebooting in these two scenarios: 1. If the GNOME setting is OFF prior to reboot..., BT stays OFF upon reboot. 2. If the GNOME setting is ON prior to reboot..., BT turns ON upon reboot. HOWEVER..., in ALL suspend/wake scenarios, regardless of the AutoEnable setting or the GNOME setting, OR even if a "systemctl stop bluetooth" is performed prior to suspend/wake, (or any permutation of all 3)..., BT is re-enabled upon wake. This SEEMS to be some sort of lack of coordination between systemd configuration and some GNOME component. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Correction: "systemctl stop bluetooth" appears to have more durable results wrt suspend/wake than I first thought, though I thought I tested it pretty thoroughly. If I stop the service..., it appears to stay stopped following suspend/wake. For the moment then, my workaround is to set AutoEnable=false and whenever I want to turn BT off..., do a "systemctl stop bluetooth". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Sigh. So I repeatedly testing suspend/wake following a systemctl stop bluetooth..., and BT stayed off. Until now. I left the machine to sleep for maybe an hour..., just woke it..., boom..., BT is back on. So..., I guess I retract my prior "correction". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923525] [NEW] gnome-control-center sound won't set hdmi 5.1
Public bug reported: gnome-control-center sound Shows output device: hdmi-audio configure: stereo I change configure to 5.1 output device changes to "dummy" and the configure UI goes away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 18:47:39 2021 InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210412) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1923525 Title: gnome-control-center sound won't set hdmi 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923525] Re: gnome-control-center sound won't set hdmi 5.1
this line looks relevent 18:57:44.0656 Gvc:DEBUG gvc_mixer_control_lookup_device_from_stream - Could not find a device for stream 'Built-in Audio Digital Stereo (HDMI)' ** Attachment added: "gnome-control-center -v > .log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+attachment/5487068/+files/gnome-control-center.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1923525 Title: gnome-control-center sound won't set hdmi 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923323] Re: Bluetooth will not stay OFF upon resume
So..., I think I figured out why "systemctl stop bluetooth" sometimes works to disable BT thru a suspend/wake cycle, and sometimes not. If you turn OFF BT using the GNOME settings, regardless of whether or not you do a "systemctl stop bluetooth"..., BT will ALWAYS be turned back ON after a suspend/wake cycle. If you leave the GNOME BT setting as ON however, and if you do a "systemctl stop bluetooth", BT will stay OFF following a suspend/wake cycle, presumably because the GNOME power management code thinks BT is already ON..., and so takes no action to enable it. Basically..., the left hand doesn't know what the right hand is doing. My inclination is to pin this bug on the GNOME power management code at this point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? + + [Testcase] + + 1. Launch Nautilus to home directory + 2. Right click > "Open in Terminal" + 3. Run "printenv" to see full list of env variables + 4. Click new tab button, or ctrl-shift-t + 5. Run "printenv" see the lack of env variables + + I have a test package available in the below ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test + + The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + reverted. + + If you install this package, environment variables will be set + correctly. + + [Where problems could occur] + + I think there is some risk with re-instating a commit which has been + reverted, and users could run into similar issues as found in the + upstream bug. + + We do have some supporting evidence that the commit isn't too harmful, + since it is applied to Groovy currently, things work as intended there, + and users haven't complained about the issues in the upstream bug + applying to Groovy. + + If a regression were to occur, then launching a new gnome-terminal or + opening a new tab could land the user with a terminal with little to no + environment variables set. A workaround will be to launch gnome-terminal + from gnome-shell overview. + + [Other info] + + Groovy has the following commit applied: + + commit fd5ac772154426e2da5afd633b336414bca33be9 + Author: Christian Persch + Date: Mon Mar 23 09:57:56 2020 +0100 + Subject: screen: Use clean env when creating new tab + Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 + + This was then reverted in 3.38.1 due to the upstream bug: + + https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 + + The reverted commit is: + + commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + Author: Christian Persch + Date: Thu Sep 17 17:10:47 2020 +0200 + Subject: Revert "screen: Use clean env when creating new tab" + Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + + This revert seems to have broken Hirsute. If we revert the revert, that is, + apply the commit again, things work as intended. + + To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922772] Re: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922772 Title: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
Attached is a debdiff for Hirsute which re-applies "screen: Use clean env when creating new tab" and is the same patch in the PPA. ** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview. [Other info] - Groovy has the following commit applied: + Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac - This revert seems to have broken Hirsute. If we revert the revert, that is, - apply the commit again, things work as intended. + This revert seems to have broken Hirsute. If we revert the revert, that + is, apply the commit again, things work as intended. To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. ** Patch added: "gnome-terminal debdiff for hirsute" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+attachment/5487098/+files/lp1922839_hirsute.debdiff ** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
[Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
The attachment "gnome-terminal debdiff for hirsute" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923130] Re: duplicate folders in "show application" menu
** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923130 Title: duplicate folders in "show application" menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
