[Bug 1806697] Re: Status of interface connections not properly updated in the UI
** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806697] Re: Status of interface connections not properly updated in the UI
** Changed in: gnome-software (Ubuntu Disco) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting
Sounds like a fix is on the way: https://gitlab.gnome.org/GNOME/mutter/merge_requests/626 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #643 https://gitlab.gnome.org/GNOME/mutter/issues/643 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/643 Importance: Unknown Status: Unknown ** Tags removed: artful yakkety -- 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/1652282 Title: Xwayland not using XAUTHORITY, prevents root applications from connecting To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1652282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
It also sounds like VirtualBox might allow me to reproduce the bug... ** Changed in: mutter (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Because it was mentioned in comment #15 & #34 that this bug cannot be reproduced, I decided to create a VMWare VM from scratch which managed to be affected on my first attempt. I started with ubuntu-18.04.1-desktop-amd64.iso (19e10acddd14af9a9150399d876b02933c0ee724) and created a snapshot with all the live packages, as of today (06/19/2019), except for the 4 I noted in comment #28. Simply start the VM, update the out of date packages via the internet or via the provided copies of the deb files on the desktop, and reboot to reproduce the bug (infinite UI hang before login). Bug1832138VM.zip (3fd83148ebeceacd48bca7b9f02c1d714c9391ca) Download from: https://pride-rock-labs.com/Bug1832138VM.zip VM Credentials: vmuser | vmpassword I made this VM under near identical conditions to the original poster (Pat). This means I now have reproduced the issue under ESXi and Fusion. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
** Changed in: mutter (Ubuntu Bionic) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
** Changed in: mutter (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
My reproducer: 1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't really matter but I prefer giving more details than less ;) 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 3) Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 'lspci -nnvv' command. 4) apt-get dist-upgrade Then reboot and the login screen won't be shown again using v4.15 kernel. Switch to 4.18 will work. Regards, Eric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
> Do you know what change could have introduced this vmwgfx/wayland interaction problem inside mutter in the first place ? Technically it was a whole point release. The trigger could be any change that went into mutter 3.28.4 as well as any Ubuntu patch. As mentioned in comment #31, my suspicion is this specific change: https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72 > Just to look at our option (since a kernel fix might be not end up being trivial) does a revert of the change could be a possibility here ? If the issue turns out to be commit e9e4b2b72 above then no. Because too many people benefit vs the possible number of people affected by this bug. But we also aren't completely sure that's the relevant mutter commit. If only I could reproduce this bug I could probably write a workaround (or fix) for it in mutter. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832988] Re: Intel 8260 Bluetooth not working
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1832988 Title: Intel 8260 Bluetooth not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816396] Re: Starting snap from the after-install notification fails
** Also affects: gnome-software (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Disco) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu Disco) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1816396 Title: Starting snap from the after-install notification fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1816396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833471] Re: Can not enable Wifi Hotspot
Thank you for your bug report. Could you add your 'journalctl -b 0' log after getting the issue? When you say that the screen goes black, are you speaking about the settings part of the session? Does it come back after a while? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1833471 Title: Can not enable Wifi Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Changed in: gnome-shell Status: New => Fix Released -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833471] [NEW] Can not enable Wifi Hotspot
Public bug reported: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1833471 Title: Can not enable Wifi Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
To continue on my comment #59 ... One user has been impacted on a physical machine (non-vmware) with the same symptom but can't provide public details unfortunately, but I witnessed the problem from my own eye via remote session, and again upgrading to 4.18 kernel did the trick. So it really seems like 4.15 is possibly incompatible at some point with the current mutter package. That is my believe with the level of details that I know for now and what has been shared to me. Daniel, any thoughts on this ? I will try to contact you on irc tonight if we can manage to fight the TZ gap between us. ;) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
as an fyi ... It has been brought to my attention that this could impact other system (outside vmware context) so I still suspect a userspace change (possibly mutter) that introduce behaviour change and break the interaction with certain part of the 4.15 kernel. Do we know if the recent point release has been tested with different kernel series ? 4.15, 4.18, ... or only 4.18 ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
This bug was fixed in the package evince - 3.28.4-0ubuntu1.2
---
evince (3.28.4-0ubuntu1.2) bionic-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus system bus (we allow full
access to session, translation and accessibility buses for compatibility)
+ allow Get* to anything polkit allows
+ allow talking to avahi (for printing)
+ allow talking to colord (for printing)
- make the thumbnailer more restrictive (LP: #1794848) (Closes: #909849)
+ remove evince abstraction and use only what is needed from it
+ limit access to DBus session bus
+ generally disallow writes
+ allow reads for non-hidden files
* debian/apparmor-profile.abstraction: apply hardening from Ubuntu 18.10
- disallow access to the dirs of private files (LP: #1788929)
* debian/apparmor-profile: allow /bin/env ixr
-- Jamie Strandboge Tue, 18 Jun 2019 19:15:55 +
** Changed in: evince (Ubuntu Bionic)
Status: In Progress => Fix Released
--
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/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1788929/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
This bug was fixed in the package evince - 3.18.2-1ubuntu4.5
---
evince (3.18.2-1ubuntu4.5) xenial-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus system bus (we allow full
access to session, translation and accessibility buses for compatibility)
+ allow Get* to anything polkit allows
+ allow talking to avahi (for printing)
+ allow talking to colord (for printing)
- make the thumbnailer more restrictive (LP: #1794848) (Closes: #909849)
+ remove evince abstraction and use only what is needed from it
+ limit access to DBus session bus
+ generally disallow writes
+ allow reads for non-hidden files
* debian/apparmor-profile.abstraction: apply hardening from Ubuntu 18.10
- disallow access to the dirs of private files (LP: #1788929)
* debian/apparmor-profile: allow /bin/env ixr
-- Jamie Strandboge Tue, 18 Jun 2019 19:28:02 +
** Changed in: evince (Ubuntu Xenial)
Status: In Progress => Fix Released
--
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/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1788929/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832988] Re: Intel 8260 Bluetooth not working
Kai-Heng: thanks for the suggestion, bluetooth now switches on & I can pair with devices. Output of "dmesg | grep -i bluetooth" looks healthier too: martin@martin-N15-17RD:~$ dmesg | grep -i bluetooth [ 18.577708] Bluetooth: Core ver 2.22 [ 18.577724] Bluetooth: HCI device and connection manager initialized [ 18.577728] Bluetooth: HCI socket layer initialized [ 18.577730] Bluetooth: L2CAP socket layer initialized [ 18.577733] Bluetooth: SCO socket layer initialized [ 18.604676] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 18.609699] Bluetooth: hci0: Device revision is 5 [ 18.609700] Bluetooth: hci0: Secure boot is enabled [ 18.609701] Bluetooth: hci0: OTP lock is enabled [ 18.609702] Bluetooth: hci0: API lock is enabled [ 18.609702] Bluetooth: hci0: Debug lock is disabled [ 18.609704] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 18.616186] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 20.040219] Bluetooth: hci0: Waiting for firmware download to complete [ 20.040662] Bluetooth: hci0: Firmware loaded in 1403163 usecs [ 20.040696] Bluetooth: hci0: Waiting for device to boot [ 20.051673] Bluetooth: hci0: Device booted in 10735 usecs [ 20.053532] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 20.057675] Bluetooth: hci0: Applying Intel DDC parameters completed [ 20.153462] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.153463] Bluetooth: BNEP filters: protocol multicast [ 20.153466] Bluetooth: BNEP socket layer initialized [ 31.673667] Bluetooth: RFCOMM TTY layer initialized [ 31.673673] Bluetooth: RFCOMM socket layer initialized [ 31.673677] Bluetooth: RFCOMM ver 1.11 I guess the next time there's a kernel update for Ubuntu though it will wipe out the one you provided? -- 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/1832988 Title: Intel 8260 Bluetooth not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832988] Re: Intel 8260 Bluetooth not working
Hi Daniel & Kei-Heng, thanks for the suggestions. rfkill doesn't do much > martin@martin-N15-17RD:~$ rfkill unblock 0 > rfkill: invalid identifier: 0 I'll try the kernel you suggested next. -- 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/1832988 Title: Intel 8260 Bluetooth not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832457] Re: [SRU] 2.60.4
Hello Iain, or anyone else affected, Accepted glib2.0 into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.60.4-0ubuntu0.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832374] Re: Media keys stop working due to missing service file
This bug was fixed in the package gnome-settings-daemon - 3.32.1-1ubuntu1 --- gnome-settings-daemon (3.32.1-1ubuntu1) eoan; urgency=medium * New upstream version Media-keys: - Fix MPRIS issues with disconnecting clients (lp: #1832374) * Merge with Debian. Remaining changes: + debian/control.in: - Build-depend on accountsservice + debian/patches: - 45_suppress-printer-may-not-be-connected-notification.patch - 53_sync_input_sources_to_accountsservice.patch - 64_restore_terminal_keyboard_shortcut_schema.patch - correct_logout_action.patch display the logout action on ctrl-alt-del - ubuntu-lid-close-suspend.patch Reimplement support for setting lid close suspend actions - revert-wacom-migration.patch - revert-gsettings-removals.patch Revert gsettings keys that were dropped since 3.8, for u-s-d - revert-mediakeys-dbus-interface-drop.patch - ubuntu_ibus_configs.patch - git_binary_encoding.patch - ubuntu_calculator_snap.patch + debian/gnome-settings-daemon.install: - Install apport hook * debian/patches/*: Refresh gnome-settings-daemon (3.32.1-1) experimental; urgency=medium * New upstream release -- Sebastien Bacher Wed, 19 Jun 2019 15:48:01 +0200 ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833433] Re: nautilus crashed with SIGSEGV after system update + restart
*** This bug is a duplicate of bug 1822195 *** https://bugs.launchpad.net/bugs/1822195 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1822195, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1833433/+attachment/5271579/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271581/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271585/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271586/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271587/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271588/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1833433/+attachment/5271589/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1822195 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1833433 Title: nautilus crashed with SIGSEGV after system update + restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833431] Re: Update gnome-settings-daemon to 3.32.1
https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/3.32.1-1ubuntu1 ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1833431 Title: Update gnome-settings-daemon to 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833431] [NEW] Update gnome-settings-daemon to 3.32.1
Public bug reported: * Impact There is a new bugfix GNOME update available with some bugs fixed, details on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS * Test case Log into a Ubuntu/GNOME session and make sure that the session has the correct theme, that the screen resolution is correct, that the keybinding work as they should. * Regression potential The main changes are in the plugins to handle the monitor, night mode and multimedia keys, make sure those keep working The update is covered by the GNOME standing exception. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Low Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1833431 Title: Update gnome-settings-daemon to 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833192] Re: VMware: post custom script isn't run correctly
** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Xiaofeng Wang (xiaofengw) ** No longer affects: evince (Ubuntu) -- 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/1833192 Title: VMware: post custom script isn't run correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768166] Re: Random crashes
This bug was fixed in the package ibus-libpinyin - 1.11.0-1ubuntu0.18.10.1 --- ibus-libpinyin (1.11.0-1ubuntu0.18.10.1) cosmic; urgency=medium * Backport of the disco version as an SRU in an attempt to reduce the number of crashes (LP: #1768166). -- Gunnar Hjalmarsson Wed, 22 May 2019 17:06:00 +0200 ** Changed in: ibus-libpinyin (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: libpinyin (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768166] Re: Random crashes
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.04.1 --- libpinyin (2.2.2-1~ubuntu18.04.1) bionic; urgency=medium * Backport of the disco version as an SRU in an attempt to reduce the number of crashes (LP: #1768166). -- Gunnar Hjalmarsson Mon, 22 May 2019 16:54:00 +0200 ** Changed in: ibus-libpinyin (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768166] Re: Random crashes
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.10.1 --- libpinyin (2.2.2-1~ubuntu18.10.1) cosmic; urgency=medium * Backport of the disco version as an SRU in an attempt to reduce the number of crashes (LP: #1768166). -- Gunnar Hjalmarsson Mon, 22 May 2019 16:54:00 +0200 ** Changed in: libpinyin (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
of if we identify the offending userspace change, then we can look at the kernel again and try to find what bit are missing, and if we limit the kernel change then maybe the side-effect won't be present too. I think the next step is really to find what userspace change started all this so we can find the related kernel change to backport (without doing that massive 6 commits backport, which as a side-effect and who know what else). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
or if we identify the offending userspace change, then we can look at the kernel again with and try to find what bit are missing, and if we limit the kernel change then maybe the side-effect might not be present again. (assumption here) I think the next step is really to find what userspace change started all this so we can related kernel known fix to be part of the final backport (without doing that massive 6 commits backport, which as a side-effect and who know what else). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1584465] Re: I closed the window but the sound is still playing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1584465 Title: I closed the window but the sound is still playing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1584465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Daniel van Vugt (vanvugt), Do you know what change could have introduced this vmwgfx/wayland interaction problem inside mutter in the first place ? I have strong believe, that something userspace has been changed and no longer interact well with the vmware driver since then. Just to look at our option (since a kernel fix might be not end up being trivial) does a revert of the change could be a possibility here ? or else. Ideally, I agree I would have prefer to fix the kernel and I'm also going to pursue that direction, but just looking other avenues in case of ... Thanks - Eric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
The patchset is significant already without knowing yet what is missing to address the side-effect. I would need kernel team review/approval before thinking to SRU this into Ubuntu 4.15. I can't SRU this as-is, now knowing this will introduce a regression. I'll keep you guys posted. - Eric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764156] Re: Make all gnome-session-properties AppStream strings translatable
Still not fixed in latest Ubuntu release. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1764156 Title: Make all gnome-session-properties AppStream strings translatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1764156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832374] Re: Media keys stop working due to missing service file
Thanks for reporting it upstream, they haven't rolled out an update with the fix yet but they will do it now ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Description changed: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an unused Intel GPU). WORKAROUNDS (you only need one): * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf * Disable integrated graphics/GPU in your BIOS * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. + + * Add a line to /usr/lib/udev/rules.d/61-gdm.rules: + DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/gdm3/+git/gdm3/+merge/369024 -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Changed in: mutter (Ubuntu) Status: Won't Fix => In Progress -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832374] Re: Media keys stop working due to missing service file
According to upstream, the fix is in 3.32.1 not in 3.32.0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
Oops. It appears upstream already fixed this bug. And we removed their fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you revert that revert then the bug is fixed. ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gdm3 (Ubuntu) Status: Invalid => In Progress ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: In Progress => Won't Fix -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832457] Re: [SRU] 2.60.4
It was clear that the sync was what I was going for (comment #1), so it would have been nice if the SRU would have been accepted by the way. Brian could have synced it if necessary as well. Now we have to wait for another go-round. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832457] Re: [SRU] 2.60.4
It's there now. The sync must have failed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245473]
yanp.b...@gmail.com: Why did you reopen this task without any comment explaining the reason? See comment 201? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245473]
Hi! I have the same issue i would like to know the solution Castro B, gratisdatingsite.nl -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
