[Bug 1526877] Re: Dbus errors in the console when closing the music-app
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Fix Committed ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1526877 Title: Dbus errors in the console when closing the music-app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write
** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: mediaplayer-app (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided => Critical ** Changed in: dbus-cpp (Ubuntu) Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1524131 Title: /usr/bin/mediaplayer- app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1293629] Re: [Regression] [Trusty] Unity can't be started from kdm
This doesn't seem like it's getting any traction after 2 years and kdm is not even shipped anymore so as reporter i'm closing this bug to have a cleaner "reported bugs" view in launchpad. ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1293629 Title: [Regression] [Trusty] Unity can't be started from kdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1293629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534520] [NEW] gnome-terminal.desktop isn't shown on nautilus desktop
Public bug reported: 1、sudo apt-get install gnome-session-flashback 2、Goto flashback Session 3、Dragging Gnome Terminal App to Desktop, it isn't shown. A brief solution is to modify this file "/usr/share/applications/gnome- terminal.desktop", from -- "OnlyShowIn=GNOME;Unity;" to -- "OnlyShowIn=GNOME;Unity;GNOME-Flashback:Unity;" since the XDG_CURRENT_DESKTOP value under gnome-flashback session is GNOME-Flashback:Unity ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.2-1ubuntu2 [modified: usr/share/applications/gnome-terminal.desktop] ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jan 15 17:22:03 2016 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: 1、sudo apt-get install gnome-session-flashback 2、Goto flashback Session 3、Dragging Gnome Terminal App to Desktop, it isn't shown. A brief solution is to modify this file "/usr/share/applications/gnome- terminal.desktop", from -- "OnlyShowIn=GNOME;Unity;" to -- "OnlyShowIn=GNOME;Unity;GNOME-Flashback:Unity;" since the XDG_CURRENT_DESKTOP value under gnome-flashback session is GNOME-Flashback:Unity ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.2-1ubuntu2 [modified: usr/share/applications/gnome-terminal.desktop] ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jan 15 17:22:03 2016 - JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1534520 Title: gnome-terminal.desktop isn't shown on nautilus desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1534520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1509711] Re: Screen temporarily not locked when coming out of suspend
The problem does no longer show up with kernel 4.4.0. @hjwp2: perhaps you could try out the mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/ too? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1509711 Title: Screen temporarily not locked when coming out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1509711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk "Requires Authorization" after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1259422] Re: Google authentication error in empathy
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1259422 Title: Google authentication error in empathy To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1259422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1524131 Title: /usr/bin/mediaplayer- app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)
I can confirm, that this bug is still present on LTS version 14.04.3 with all. Can someone please use the fix from Saucy for Trusty? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1196177 Title: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1196177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534645] [NEW] Cannot easily preserve a keyring to be only unlocked manually
Public bug reported: Assume you want to create a keyring for secrets that you only need rarely and thus want to access only on demand (not unlock on every login session). Whenever you access/unlock the keyring for the first, second, etc. time, the "Unlock keyring" dialog asks for the password and has a preselected checkbox "Automatically unlock this keyring whenever I'm logged in". This is however not the current setting for this keyring, so it constitutes a change of a setting, which counteracts the (likely) intention of the user. It is to easily to type the password and hit enter, thereby changing this keyring to an automatically unlocked one, and this risk happens repeatedly everytime you unlock it. In case you forgot to uncheck the checkbox, the only way to restore the original setting is hidden (not in keyring → properties, but only by setting a new password). A security-focused application should also not have defaults that tend to decrease security in favor of usability. Having the checkbox preselected gains less extra usability (for the case the user wants to change the keyring to be automatically unlocked: 1 click saved) than that it decreases usability (in case the user wants to keep the keyring manual: 1 click everytime to unselect it). A possible fix is to not preselect the checkbox. version 3.10.2 in Ubuntu 14.04 as well as in the version in Ubuntu 15.10 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1534645 Title: Cannot easily preserve a keyring to be only unlocked manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1534645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534672] Re: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1534672 Title: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1534672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534672] [NEW] package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: the package cannot be reinstaled nor eliminated by apt-get ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shotwell-common 0.18.0-0ubuntu4.4 ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Jan 13 11:39:23 2016 DuplicateSignature: package:shotwell-common:0.18.0-0ubuntu4.4:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-10 (96 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: shotwell Title: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1534672 Title: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1534672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 11334] Re: MASTER Copy-Paste doesn't work if the source is closed before the paste
bug-bounty ** Changed in: kdeutils Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (36165). https://bugs.launchpad.net/bugs/11334 Title: MASTER Copy-Paste doesn't work if the source is closed before the paste To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/11334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 263822] Re: RTL (right to left) support in terminal (BiDi)
** Changed in: vte (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/263822 Title: RTL (right to left) support in terminal (BiDi) To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/263822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
I'm having the same problem with both my 2012 Nexus 7 and my HTC One M8. If I connect the device, I get the error message "Unable to mount Android Phone: Unable to open MTP device '[usb:005,120]'" for my HTC One M8. The message changes to "Unable to mount Nexus 7" when I plug the Nexus 7 in. The '[usb:005,120]' identifier also changes. (All of the following was done with the HTC phone...) But here's the interesting part: if I run "lsusb" with the error message on the screen, the device is detected one ID higher. Right now, "lsusb" is showing "Bus 005 Device 121: ID 0bb4:061a HTC (High Tech Computer Corp.)" for the phone. Using "ls -l /dev/bus/usb/X/Y" gives: $ ls -l /dev/bus/usb/005/120 ls: cannot access /dev/bus/usb/005/120: No such file or directory $ ls -l /dev/bus/usb/005/121 crw-rw+ 1 root audio 189, 632 Jan 15 20:59 /dev/bus/usb/005/121 dmesg gives the following: $ dmesg [ 3202.628185] usb 5-2: new high-speed USB device number 122 using xhci_hcd [ 3202.650762] usb 5-2: New USB device found, idVendor=0bb4, idProduct=061a [ 3202.650769] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3202.650773] usb 5-2: Product: Android Phone [ 3202.650777] usb 5-2: Manufacturer: HTC [ 3202.653957] usb-storage 5-2:1.2: USB Mass Storage device detected [ 3202.654251] scsi11 : usb-storage 5-2:1.2 [ 3202.796549] usb 5-2: USB disconnect, device number 122 [ 3203.576177] usb 5-2: new high-speed USB device number 123 using xhci_hcd [ 3203.598656] usb 5-2: New USB device found, idVendor=0bb4, idProduct=061a [ 3203.598663] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3203.598667] usb 5-2: Product: Android Phone [ 3203.598670] usb 5-2: Manufacturer: HTC (I've deleted the 'SerialNumber' lines; I don't know if they're sensitive or not) Another time I tried to reproduce the dmesg output, I got: [ 3271.638047] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88056c19e040 [ 3271.638049] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88056c19e000 [ 3271.638051] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88057ad043c0 [ 3271.638052] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88056c19e080 [ 3271.638053] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88057ad041c0 [ 3271.638055] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88057ad04380 [ 3271.638056] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with disabled ep 88057ad04180 I don't know if that's related. It doesn't always appear in dmesg. I'm actually using Linux Mint, as follows: $ uname -a Linux roger-pc 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 17 Qiana Release:17 Codename: qiana $ lsb_release -au No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534783] Re: trackpad doenst turn on/off by keyboard
Hi Carlos, Please only assign yourself to a bug if you plan to work on fixing the bug! Can you check what keycode is sent when you press the shortcut, it should be XF86TouchpadToggle ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-gnome Assignee: Carlos V Ferrer (carlosvferrer) => (unassigned) -- 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/1534783 Title: trackpad doenst turn on/off by keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1534783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468027] Re: change default CJK fonts to Noto CJK
This bug was fixed in the package language-selector - 0.154 --- language-selector (0.154) xenial; urgency=medium * data/pkg_depends, fontconfig/69-language-selector-zh-*.conf: Default font for Chinese changed from "Droid Sans Fallback" to "Noto Sans CJK" (LP: #1468027). -- Gunnar Hjalmarsson Sat, 16 Jan 2016 00:43:00 +0100 ** Changed in: language-selector (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto-cjk in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto CJK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1468027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 341725] Re: Can't save changes in VirtualBox Shared Folder. Nano, OOo do it.
My use case is a Mint 17.x VM using a VirtualBox vboxsf to a Win8.1 host. I had this same problem in Geany and it was driving me insane until I found http://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving and then "Edit > Prefs > Various > use_atomic_file_saving: checked" fixed it for me. Be sure to read the URL as there are implications. Obviously this does not fix Gedit but it may be an acceptable work- around for some people. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/341725 Title: Can't save changes in VirtualBox Shared Folder. Nano, OOo do it. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/341725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34813] Re: gedit fails to save files over smbfs/cifs
My use case is a Mint 17.x VM using a VirtualBox vboxsf to a Win8.1 host. I had this same problem in Geany and it was driving me insane until I found http://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving and then "Edit > Prefs > Various > use_atomic_file_saving: checked" fixed it for me. Be sure to read the URL as there are implications. Obviously this does not fix Gedit but it may be an acceptable work- around for some people. -- 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/34813 Title: gedit fails to save files over smbfs/cifs To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/34813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
