[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Chris J Arges]

Hello Adam, or anyone else affected,

Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.4 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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!

** Changed in: console-setup (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-bionic

** Tags removed: verification-done-bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1762952

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

[Chris J Arges]

Hello Marco, or anyone else affected,

Accepted xdg-user-dirs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xdg-user-
dirs/0.15-2ubuntu6.16.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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Changed in: xdg-user-dirs (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1754356

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  Fix Released
Status in xdg-user-dirs source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1704533] Please test proposed package

[Chris J Arges]

Hello NoOne, or anyone else affected,

Accepted libgweather into artful-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu0.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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1704533] Please test proposed package

[Chris J Arges]

Hello NoOne, or anyone else affected,

Accepted libgweather into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.2 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-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed-artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Chris J Arges]

Hello NoOne, or anyone else affected,

Accepted libgweather into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.18.2-0ubuntu0.2 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libgweather (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: libgweather (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-zesty

** Changed in: libgweather (Ubuntu Artful)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Chris J Arges]

Does this also affect Artful? Looks like Zesty is also affected.

** Also affects: evince (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: evince (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: evince (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: evince (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: evince (Ubuntu)
   Importance: Low => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1716357

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Xenial:
  New
Status in evince source package in Zesty:
  New

Bug description:
  * Impact
  there is an extra ";" in the mimetype list leading to a buggy mailcap entry

  * Test case:
  check if /etc/mailcap contains a line
  "; evince-previewer %s; test=test -n "$DISPLAY""

  * regression potentiel
  check that evince is correcly used when trying to open file associated to it

  -

  
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1716357/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Chris J Arges]

Is there a fix required for zesty as well?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1539209

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Chris J Arges]

Hello MrRomanze, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1539209

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_proce

[Chris J Arges]

Hello TBS, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1562817

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_write_volume_cb() from source_set_port_cb() from
  pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
 headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
 older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  This error is there when i get back to the computer after a while of
  no use, and at login after restart. haven't seen this error while the
  system is "active"/in use.

  I have been unable to provoke the error to come.

  I'm not sure it is related, but when i plug in a headset, the audio volume 
goes through the roof, and a loud (painfully so) scratching sound is coming 
from the headset until i press Vol+. Vol- does nothing till i have pressed up 
at least once.
  But the bug report thing does not pop up when the sound issue is there.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  pulseaudio:
    Installed: 1:8.0-0ubuntu2
    Candidate: 1:8.0-0ubuntu2
    Version table:
   *** 1:8.0-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbs   22776 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 28 12:39:45 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-14 (73 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   pa_source_process_msg () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo 
vboxusers
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  

[Desktop-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler()

[Chris J Arges]

Hello bikram, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1672171

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  Bluetooth device keep disconnect and audio output tab is empty

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bikram14994 F pulseaudio
   /dev/snd/controlC0:  bikram14994 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 12 21:52:24 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_set_state () from 
/usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0Y004V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1672171/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_hand

[Chris J Arges]

Hello errors.ubuntu.com, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1690028

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1690028/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1643789] Update Released

[Chris J Arges]

The verification of the Stable Release Update for libdrm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1643789

Title:
  Backport packages for 16.04.2 hwe-16.04 -stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  Since the xserver is already at 1.18.4, the full stack from 16.10 will
  not be backported as a renamed set of packages. Instead, only the
  drivers with bugfix releases will be backported, plus the libraries
  and mesa that complement the set.

  [Test case]

  Run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - this release was already tested by cert team on a handful of intel/amd 
machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1641017] Update Released

[Chris J Arges]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1641017

Title:
  Mesa 12.0.6 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1641017/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1652564] Update Released

[Chris J Arges]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1652564

Title:
  [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Yakkety:
  Fix Released

Bug description:
  There was a regression in intel mesa driver that caused raise of
  SIGFPE signal which resulted in startup error messages (about division
  by zero or invalid floating point operation) in some applications and
  games sensitive to this behavior.

  Currently it resolved in upstream:
  https://bugs.freedesktop.org/show_bug.cgi?id=95419
  By following commit:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93
  Is it possible to include foregoing patch to avoid bug in current 
distributions?

  Distribution: Ubuntu 16.04
  Video card: Intel HD 4600
  Mesa version: 11.2.0-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1652564/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1652486] Update Released

[Chris J Arges]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1652486

Title:
  mesa gpu lockup

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1652486/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1453336] Re: shotwell fails to import iphone photos

[Chris J Arges]

** Patch added: "trusty-fix-lp1453336.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1453336/+attachment/4797918/+files/trusty-fix-lp1453336.debdiff

** Also affects: shotwell (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: shotwell (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: shotwell (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Description changed:

- Shotwell when view my photos on iPhone see double and fails to import.
+ [Impact]
+ Shotwell fails to import photos from an iPhone using iOS 8+.
+ 
+ [Test Case]
+ Plug in iPhone with iOS8+ and try to import photos.
+ 
+ [Regression Potential]
+ This patch is not yet mainline shotwell, but has already been applied in 
Debian.
+ 
+ ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: shotwell 0.20.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  8 21:26:59 2015
  InstallationDate: Installed on 2015-05-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1453336

Title:
  shotwell fails to import iphone photos

Status in Shotwell:
  Unknown
Status in shotwell package in Ubuntu:
  Triaged
Status in shotwell source package in Trusty:
  New
Status in shotwell source package in Xenial:
  New
Status in shotwell source package in Yakkety:
  New

Bug description:
  [Impact]
  Shotwell fails to import photos from an iPhone using iOS 8+.

  [Test Case]
  Plug in iPhone with iOS8+ and try to import photos.

  [Regression Potential]
  This patch is not yet mainline shotwell, but has already been applied in 
Debian.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: shotwell 0.20.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  8 21:26:59 2015
  InstallationDate: Installed on 2015-05-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+bug/1453336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 918489] Update Released

[Chris J Arges]

The verification of the Stable Release Update for deja-dup has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/918489

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  Fix Released
Status in deja-dup source package in Xenial:
  Fix Released
Status in deja-dup source package in Yakkety:
  Fix Released

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1482938] Update Released

[Chris J Arges]

The verification of the Stable Release Update for im-config has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1482938

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Committed
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  Fix uploaded to yakkety queue; xenial patch attached to bug #1642001.

  [Test Case]

  After the change, this command:

  grep -A3 QT_IM_MODULE /usr/share/im-config/data/26_gcin.rc

  should output:

  QT_IM_MODULE=xim
  # use immodule when available for Qt5
  for IM_CONFIG_MARKER in 
/usr/lib/*/qt5/plugins/platforminputcontexts/libgcinplatforminputcontextplugin.so
 ; do
  if [ -e $IM_CONFIG_MARKER ]; then
  QT_IM_MODULE=gcin
  break
  fi
  done

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1482938/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1642001] Update Released

[Chris J Arges]

The verification of the Stable Release Update for im-config has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1642001

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Committed
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  XIM support check for Qt5 in UIM is broken — it uses the same paths as
  for Qt4, but they've been changed.

  Fix uploaded to yakkety queue; xenial patch attached.

  [Test Case]

  After the change, this command:

  grep platforminputcontexts /usr/share/im-config/data/24_uim.rc

  should output:

  for IM_CONFIG_MARKER in
  
/usr/lib/*/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
  ; do

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1642001/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1614050] Update Released

[Chris J Arges]

The verification of the Stable Release Update for metacity has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1614050

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released

Bug description:
  # Test Case
  Described in comment 
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/comments/16

  # Impact
  Sometimes the window depth order is wrong, for example the desktop icons 
appear above all windows. Also sometimes windows disappear and the only way to 
bring them back to life is restarting Metacity. This can result in loss of work 
results for users who do not know how to deal with this bug.

  # Fix
  The Xenial fix is composed of two upstream commits, in gnome-3-18 branch:
  - https://git.gnome.org/browse/metacity/commit/?id=d5f9e42e30c67d07
  - https://git.gnome.org/browse/metacity/commit/?id=72488dc76ee24a3e

  # Regression Potential
  The patch has been in Yakkety for almost a month, and nobody complained.
  [bdmurray] - That's not a description of what could go wrong, rather one of 
what hasn't gone wrong in Yakkety.  Please add some possible regressions and 
what users testing this fix should look out for.

  =
  Using the gome-flashback session with metacity is totally messed up since I 
updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  I guess all those effects originate from a similiar reason. None of
  these problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1633757] Update Released

[Chris J Arges]

The verification of the Stable Release Update for file-roller has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1633757

Title:
  Update file-roller to 3.22.1

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Yakkety:
  Fix Released
Status in file-roller source package in Zesty:
  Fix Released

Bug description:
  Impact
  ==
  - Fix bug that prevented opening additional archives when file-roller was 
already open
  - Handle Source RPMs. Don't handle Comic Book archives.
  - Fixes for working with archives on remote computers
  - Translation fixes

  https://git.gnome.org/browse/file-roller/tree/NEWS
  https://git.gnome.org/browse/file-roller/log

  Test Case
  ==
  Make sure that you can still open, extract and create .zip and .tar.xz files.

  To check if the additional archive bug is fixed:
  1. From the Files app (Nautilus), double click on an archive to open it with 
file-roller
  2. Double click another archive to open it. The second archive should 
display. Before the fix, the second archive window would be blank.

  Regression Potential
  
  Low. The stable 3.22 series is actively supported and this update will be 
included in all 3.22 distros.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: file-roller 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 15 13:04:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (64 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1633757/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1622379] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-calculator has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1622379

Title:
  SRU: sin(0)/sin(0) crash the the calculator

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-calculator source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  It is possible to cause gnome-calcualtor segfault when elements of
  division to zero have null assigned tokens. For example, the following
  calculation will trigger a segfault:

  sin(0)/sin(0)

  [Test Case]

  Open a terminal with CTRL+ALT+t and launch 'gnome-calculator'. Type
  the following into the equation entry area 'sin(0)/sin(0)' and press
  enter, gnome-calculator will segfault.

  When the patched 'gnome-calculator' package is installed performing
  the same calculation described above will not cause 'gnome-calculator'
  to crash and instead the following will be displayed: Division by zero
  is undefined

  A debdiff for Xenial is attached in comment #2:

* https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1622379/comments/2

  [Regression Potential]

  None expected. The applied patch is taken directly from the following
  upstream commit:

    * https://git.gnome.org/browse/gnome-
  calculator/commit/?id=647eb687821fd74764a55767bf1e34f68f5df940

  gnome-calculator packages have been built in a PPA and tested.

  [Other Info]

  dw3@linux:~$ gnome-calculator

  (gnome-calculator:29011): GLib-CRITICAL **: g_str_has_prefix:
  assertion 'str != NULL' failed

  (gnome-calculator:29011): GLib-CRITICAL **: g_str_has_prefix: assertion 'str 
!= NULL' failed
  Segmentation fault (core dumped)
  dw3@linux:~$

  sin(0)/sin(0) = NaN, but it crash the calculator

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1622379/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

[Chris J Arges]

@ddstreet,
Can you propose a patch for network manager to adjust test cases to this new 
behavior? I'm wondering if there are other parts of network-manager that may 
expect /64 instead of /128 and break existing users.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1609898

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  New
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  New
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1621539] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-calendar has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1621539

Title:
  Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  Users who have their computer time set to 12-hour time (AM/PM) instead of 
24-hour are unable to schedule PM events in gnome-calendar. 12-hour time is the 
default in the United States.

  The update fixes this issue and a few more.

  https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-20
  https://git.gnome.org/browse/gnome-calendar/log/?h=gnome-3-20

  Test Case
  =
  1. Open the Calendar app.
  2. Click on a date to schedule a new event. Click Edit Details.
  3. Are you able to set an event that starts and ends in the afternoon?

  Open the System Settings app. Click Time & Date. Switch time from
  12-hour to 24-hour (or the opposite). Repeat steps 1-3.

  4. Schedule a new event that starts on one day and ends on the next.
  Click the all-day box and hit Done.

  The event should span both days on the calendar.

  Regression Potential
  
  Low. This is a new upstream stable bugfix release and is recommended for all 
distros shipping GNOME 3.20.

  The 3.20.3 release was insufficient and might have made things worse (
  https://bugzilla.gnome.org/770679 ), but for 3.20.4 I helped identify
  the git commits already applied in the 3.21 series to fix this issue.

  Original Bug Report
  ===
  The bug is 100% reproducible. I can schedule "AM" events and all day events, 
but no "PM" events. I would expect the part of to advance after I had passed 
noon, but I can keep cycling through the first 12 hours of the day.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.20.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep  8 10:56:05 2016
  InstallationDate: Installed on 2013-04-26 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to xenial on 2016-04-02 (159 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1621539/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1620557] Update Released

[Chris J Arges]

The verification of the Stable Release Update for libgweather has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1620557

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Fix Committed
Status in libgweather source package in Xenial:
  Fix Released

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1620557/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1621539] Re: Unable to schedule "PM" events in Gnome Calendar 3.20.2

[Chris J Arges]

Hello Sam, or anyone else affected,

Accepted gnome-calendar into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
calendar/3.20.4-0ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gnome-calendar (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1621539

Title:
  Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
  Confirmed
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ==
  Users who have their computer time set to 12-hour time (AM/PM) instead of 
24-hour are unable to schedule PM events in gnome-calendar. 12-hour time is the 
default in the United States.

  The update fixes this issue and a few more.

  https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-20
  https://git.gnome.org/browse/gnome-calendar/log/?h=gnome-3-20

  Test Case
  =
  1. Open the Calendar app.
  2. Click on a date to schedule a new event. Click Edit Details.
  3. Are you able to set an event that starts and ends in the afternoon?

  Open the System Settings app. Click Time & Date. Switch time from
  12-hour to 24-hour (or the opposite). Repeat steps 1-3.

  4. Schedule a new event that starts on one day and ends on the next.
  Click the all-day box and hit Done.

  The event should span both days on the calendar.

  Regression Potential
  
  Low. This is a new upstream stable bugfix release and is recommended for all 
distros shipping GNOME 3.20.

  The 3.20.3 release was insufficient and might have made things worse (
  https://bugzilla.gnome.org/770679 ), but for 3.20.4 I helped identify
  the git commits already applied in the 3.21 series to fix this issue.

  Original Bug Report
  ===
  The bug is 100% reproducible. I can schedule "AM" events and all day events, 
but no "PM" events. I would expect the part of to advance after I had passed 
noon, but I can keep cycling through the first 12 hours of the day.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.20.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep  8 10:56:05 2016
  InstallationDate: Installed on 2013-04-26 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to xenial on 2016-04-02 (159 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1621539/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1620557] Re: weather.noaa.gov was shut down

[Chris J Arges]

Hello Dmitry, or anyone else affected,

Accepted libgweather into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.18.2-0ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libgweather (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1620557

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Fix Committed
Status in libgweather source package in Xenial:
  Fix Committed

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1620557/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1620557] Re: weather.noaa.gov was shut down

[Chris J Arges]

Hello Dmitry, or anyone else affected,

Accepted libgweather into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.10.2-0ubuntu3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libgweather (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1620557

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Fix Committed
Status in libgweather source package in Xenial:
  In Progress

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1620557/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586933] Re: gpu-manager's drm output detection affects boot time

[Chris J Arges]

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.4.17.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1586933

Title:
  gpu-manager's drm output detection affects boot time

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed

Bug description:
  SRU request:

  [Impact]
  The current drm code to probe the connected outputs is too resource 
intensive, and slow down the boot process.

  [Test Case]
  1) Boot Ubuntu and run the following command, looking for gpu-manager:
  systemd-analize blame

  This will show how long gpu-manager took. Write down the number

  2) Install the package from -proposed, and run systemd-analize blame.
  See if the number has become smaller.

  [Regression Potential]
  Low, all the changes are already included in Yakkety.

  
  _
  Rather than calling drm directly, gpu-manager should simply check the outputs 
connector status by using the sysfs filesystem (e.g. 
/sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is 
already available.

  This should make gpu-manager a bit less resource intensive, especially
  on boot.

  The attached perf shows the problem in gpu-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

[Chris J Arges]

Hello Dwi, or anyone else affected,

Accepted ubuntu-drivers-common into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.4.17.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1320868

Title:
  "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
  0: invalid start byte" when removing nvidia-current package

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed

Bug description:
  $sudo apt-get remove nvidia-current
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'nvidia-current' is not installed, so not removed
  The following package was automatically installed and is no longer required:
linux-image-generic
  Use 'apt-get autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up nvidia-331 (331.38-0ubuntu7) ...
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 65, in 
  operation_status = main(options)
File "/usr/bin/quirks-handler", line 44, in main
  quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, 
path=quirks_path)
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in 
__init__
  self._system_info = self.get_system_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in 
get_system_info
  return quirk_info.get_dmi_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in 
get_dmi_info
  'class', 'dmi', 'id', item)).read().strip()
File "/usr/lib/python3.4/codecs.py", line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  dpkg: error processing package nvidia-331 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nvidia-331
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

[Chris J Arges]

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.4.17.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: ubuntu-drivers-common (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-367 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1619306

Title:
  SRU request: Include the 367 driver in Ubuntu 16.04

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-367 source package in Xenial:
  New
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 16.04 do not support recent NVIDIA GPUs.

  The new driver also requires changes in ubuntu-drivers-common, as gpu-
  manager needs to be able to unload the nvidia-drm module in order to
  power down the dGPU in hybrid systems.

  
  [Test Case]
  1) Enable the xenial-proposed repository, and install the nvidia-367 package

  2) Restart and see if the system boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the packages are already in Yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

[Chris J Arges]

Hello Pascal, or anyone else affected,

Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.2
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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: accountsservice (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1577049

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1577049/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1591868] Re: fwupd consuming 100% CPU

[Chris J Arges]

Hello Dustin, or anyone else affected,

Accepted appstream-glib into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/appstream-
glib/0.5.13-1ubuntu3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: appstream-glib (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1591868

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in fwupd package in Ubuntu:
  Invalid
Status in appstream-glib source package in Xenial:
  Fix Committed
Status in fwupd source package in Xenial:
  Invalid
Status in libyaml source package in Xenial:
  Invalid
Status in appstream-glib source package in Yakkety:
  Fix Released
Status in fwupd source package in Yakkety:
  Invalid
Status in libyaml source package in Yakkety:
  Invalid

Bug description:
  [Impact]

   * Corrupt yaml data is causing consumers of appstream data (such as
  gnome-software or fwupd) to get stuck in a spin and consume CPU and
  battery.

  [Test Case]

   * Introduce corrupt data into /var/lib/app-info/yaml/
   * Execute sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v
   * Check CPU usage calms down after initialization

  [Regression Potential]

   * This patch has been backported from a newer stable release upstream.
   * Due to the nature of backporting, it doesn't directly apply to Ubuntu and 
will need some adjustments made.
   * Regressions would occur in gnome-software not displaying software or fwupd 
not running properly.

  [Other Info]
   
  Original bug report: 

  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207,
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
    0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20",
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category = 
166588464,
    localename = 0x556509ededa8 "p\362\355\teU", counter = 166589040, 
domain = 0x23,
    translation = 0x5565fffb ,
    translation_length = 93892446493792, msgid = {appended = 

[Desktop-packages] [Bug 1483276] Update Released

[Chris J Arges]

The verification of the Stable Release Update for xdiagnose has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1483276

Title:
  Unable to launch xdiagnose through the Activities Overview in the
  normal way

Status in gnome-shell:
  Confirmed
Status in Ubuntu GNOME:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid
Status in xdiagnose package in Ubuntu:
  Fix Released
Status in xdiagnose source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  Clicking the icon in GNOME Shell's Activities Overview for xdiagnose fails 
silently. Nothing happens. xdiagnose is a default app in Ubuntu GNOME so this 
is a major papercut.

  Another bug being fixed in this upload is that xdiagnose hard-coded
  its app icon location making it impossible for icon themes to override
  it.

  Test Case
  =
  1. From Ubuntu GNOME 16.04, install the update.
  2. Note that GNOME Shell caches app icons so the xdiagnose icon will probably 
disappear. You can fix this by logging out and logging back or by running 
Alt-F2 and entering the letter r in the popup. Wait a few moments for 
gnome-shell to reload.
  3. Open the Activies Overview. Search for xdiagnose and click the app in the 
results.
  4. Does xdiagnose run? Does its icon display ok?
   
  Regression Potential
  
  Low. The primary change basically just copies what Synaptic does with its 
synaptic-pkexec launcher. Except for the minor glitch with the icon 
disappearing until GNOME Shell is reloaded, the icon switch is simple.

  Original Bug Report
  ===
  I am in need of doing some diagnostics work with "xdiagnose", however when 
searching for it in the Activities Overview, and then clicking on it, 
absolutely nothing happens, when in the past it would ask me for my password so 
that I could run it as root.

  I looked further into the issue and when trying to run it through
  Terminal:

  xdiagnose

  This was the output I got:

  Error: Must run as superuser

  But when running it in Terminal like so:

  pkexec xdiagnose

  It prompted for the password as it normally would and should (so
  pkexec is not the issue).

  There was also no output from the command:

  grep -r 'xdiagnose' ~/.local/share/applications

  And the output of this command "grep -r 'xdiagnose'
  /usr/share/applications" was:

  /usr/share/applications/xdiagnose.desktop:Name=xdiagnose
  /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose
  
/usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg
  
/usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose

  The contents of the file is this:

  [Desktop Entry]
  Name=xdiagnose
  GenericName=Diagnose Graphics Issues
  Comment=X.org Diagnostic and Repair Utility
  Exec=pkexec xdiagnose
  Icon=/usr/share/xdiagnose/icons/microscope.svg
  Terminal=false
  Type=Application
  Categories=System;Settings;
  X-Ubuntu-Gettext-Domain=xdiagnose

  I have reinstalled it with "sudo apt-get install --reinstall
  xdiagnose", however this seems to have made no difference at all to
  anything.

  I have also attempted to launch another application via the Activities
  Overview that uses 'pkexec' to start, and it works fine as normal.

  I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME
  3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu
  GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue
  wasn't present (probably when I was running Ubuntu GNOME 15.04 with
  GNOME 3.14).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1483276/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1594681] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1594681

Title:
  Don't override IM variables

Status in gnome-session:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently these variable settings are hardcoded in gnome-session and
  gnome-settings-daemon:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. The variables should only be set if they are empty, so the
  values set by im-config are honored.

  [Test Case]

  * Install Ubuntu GNOME
  * Install both the gnome-session and gnome-settings-daemon proposed updates
  * Install fcitx
  * Set fcitx as the input method:
    im-config -n fcitx
  * Relogin
  * Check the IM-related environment variables:
    env | grep -E '_IM|XMOD'

  After the proposed uploads of gnome-session and gnome-settings-daemon,
  those variables are consistently (unlike before) set to "fcitx".

  [Regression Potential]

  Low. im-config sets "ibus" by default in Ubuntu GNOME anyway. This
  change prevents an inconsistent input method configuration for users
  who have actively chosen some other IM framework.

  The gnome-settings-daemon change was included upstream in 3.19.3 and
  the gnome-session change was included upstream in 3.21.90.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1594681/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1579905] Update Released

[Chris J Arges]

The verification of the Stable Release Update for cups-filters has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1579905

Title:
  cups-browsed causes shutdown hang/delay in Ubuntu 16.04

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]

  When the system is shut down CUPS and cups-browsed are not shut down
  in a determined order, but cups-browsed needs CUPS still running to
  perform its shutdown, for removing the print queues it has generated
  and for saving information about these queues for use in the next
  session. With CUPS already shut down cups-browsed simply hangs and
  gets killed after a certain timeout. This can be fixed by defining the
  correct relationships in the systemd .service files and so the
  annoying hang can be avoided.

  [Test case]

  To reproduce the bug run

  sudo systemctl stop cups

  and after some seconds

  sudo systemctl stop cups-browsed

  with the shutdown of cups-browsed hanging.

  On system shutdown one gets the hang, but not always as it can happen
  that on some shutdowns cups-browsed shuts down before cups.

  After installing the fixed package, hhutting down cups requires
  shutting down cups-browsed before, so that the shutdown of cups
  triggers the shutdown of cups-browsed, making all shutdowns having the
  two services shut down in the right order avoiding a hang.

  [Regression potential]

  None. We only define a dependency between two services to make them
  shit down in the correct order.

  [Original report]

  Using the debug process found here
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917 I have
  determined that the cause of my 16.04 install's shutdown hang is cups-
  browsed.  It was the only process running when I did a systemctl list-
  jobs in the VT9 shell.  If I do sudo service cups-browsed stop and
  then shutdown, I do not get a hang.

  I have confirmed this on a virtual machine and a real system.  If I
  disable cups-browsed from ever starting, my problem is fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1579905/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1581229] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-system-monitor
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1581229

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-system-monitor package in Ubuntu:
  Fix Released
Status in gnome-system-monitor source package in Xenial:
  Fix Released

Bug description:
  * Impact
  some columns have a default width of 0 pixels which is buggy

  * Test case
  - go to preference and enable one of the memory/started column
  you should have list with a decent width

  * Regression potential
  the change is only one in the default value of a schema, if the UI looks fine 
there it's working

  --

  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was
  not found when attempting to remove it

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while allocating gadget (node
  button, owner GtkButton)

  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content
  width -12 (allocation 1, extents 6x7) while 

[Desktop-packages] [Bug 1607937] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-font-viewer has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1607937

Title:
  Font Viewer fails to start from dash: Unknown option --gapplication-
  service

Status in GNOME Font Viewer:
  Fix Released
Status in gnome-font-viewer package in Ubuntu:
  Fix Released
Status in gnome-font-viewer source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  While gnome-font-viewer can be started from command line, it fails to
  start via the .desktop file. The issue was fixed upstream via this
  commit:

  https://git.gnome.org/browse/gnome-font-viewer/commit/?id=acf919c

  The attached patch cherry picks that commit.

  [Test Case]

  Try to start gnome-font-viewer from the Dash and find that the launch
  fails.

  After having installed the proposed upload, starting the application
  from the Dash works fine.

  [Regression Potential]

  gnome-font-viewer is an independent tool, which doesn't affect other
  parts of the system. Hence the regression risk should be low.

  [Original description]

  Ubuntu 16.04.1 Fully updated.

  $ gnome-font-viewer  --version
  GNOME Font Viewer 3.16.2

  - starting from command-line: no problems.
  - starting from dash: application is shown in launcher but kills itself.
  - /var/log/syslog shows ...

 Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Unknown option 
--gapplication-service
 Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Run 
'/usr/bin/gnome-font-viewer --help' to see a full list of available command 
line options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1607937/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Chris J Arges]

Hello Sebastien, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apparmor (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = SRU apparmor =
  [Impact]
  The upload that adjusts ibus-daemon to start with "--address 
'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be 
sufficient due to the lack of a rule for the new socket path. This upload adds 
such a rule.

  [Test Case]
  1. Start a unity session after updating to the im-config package in -proposed 
but 

[Desktop-packages] [Bug 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

[Chris J Arges]

Hello AndreK, or anyone else affected,

Accepted samba into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.3.9+dfsg-
0ubuntu0.16.04.3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: samba (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1572260

Title:
  gvfs-smb-browse hogs CPU after only opening nautilus

Status in gvfs package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Xenial:
  New
Status in samba source package in Xenial:
  Fix Committed

Bug description:
  upgraded to 16.04 from 15.10 
  - the process in subject hogs 25% CPU after only starting nautilus, and keeps 
hogging it "forever"   - no samba browsing needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 19 20:03:12 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2012-10-15 (1281 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121015.2)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1572260/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

[Chris J Arges]

Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.67-1ubuntu0.16.04.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libdrm (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1600124

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1605117] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1605117

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1605117/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1605408] Update Released

[Chris J Arges]

The verification of the Stable Release Update for language-selector has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1605408

Title:
  Don't set IM "xim" by default

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Since the fix of  "cjkv" has been
  the system default in im-config for some flavors (e.g. Xubuntu,
  Lubuntu), which means that an IM framework is started and configured
  only if one of the CJKV languages is the selected display language.
  For other languages "cjkv" means that no IM related environment
  variables are set (value "none"). However, when starting gnome-
  language-selector first time after installation of one of those
  flavors, the selected IM method is set to "xim" automatically. This is
  undocumented behavior, and the background is commented in the bug
  description of .

  As illustrated in , the "xim"
  input method occasionally causes hard to debug keyboard problems. For
  this reason gnome-language-selector should not set "xim", but simply
  confirm the "none" default value from im-config.

  Some users need "xim" to access X11 dead key and compose key variants,
  and this means that they will always need to set it explicitly. The
  upside is that users who encounter problems with "xim" will do so as a
  result of an active measure, which increases the chance that they
  understand the causality.

  [Test Case]

  On a Xubuntu or Lubuntu system with a non-CJKV display language:

  * Remove already set user specific IM configuration:

rm -f ~/.xinputrc

  * Open gnome-language-selector, and find that the selected "keyboard
input method system" is "XIM".

  After installing the proposed version of language-selector-gnome,
  those steps instead result in the value "none".

  [Regression Potential]

  Low. This is only about the default value applied by gnome-language-
  selector, so it doesn't change an already set user specific IM
  configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1605408/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

[Chris J Arges]

Hello Andrew, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1509031

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  Windows can not be moved above the top of screen because the coordinates 
system used is wrong.

  [Test Case]
  * Launch a non-CSD application, such as Firefox or Thunderbird;
  * Try Alt-dragging it above the top of the screen.

  [Regression Potential]
  The fix is changing the coordinates system to the right one and should not 
cause any regressions.

  -

  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect

  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1592953] Re: Nautilus bookmarks folders leave permanent 'icon' on desktop

[Chris J Arges]

Hello Alexandros, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1592953

Title:
  Nautilus bookmarks folders leave permanent 'icon' on desktop

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
    https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
    https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  When using drag-and-drop, the temporary windows are unmapped but never 
destroyed. This makes the compositor still draw them, which leads to unwanted 
artifacts on desktop.

  [Test Case]
  * Try dragging a bookmark from nautilus window to desktop;
  * There should be no artifacts remaining on the desktop.

  [Regression Potential]
  The fix is adding two lines and should not cause any regressions.

  -

  I'm using metacity in 16.04.

  Having opened nautilus with some folders on the left area (with favorite 
locations) if a accidentaly drag one location a permanent rectangular area with
  the name of that folder will remain on desktop in that location that the drop 
was 'made' and sits on top of every windwos sth very annoyning.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1592953/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1596574] Re: Cannot resize window by dragging the top edge

[Chris J Arges]

Hello Cui, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1596574

Title:
  Cannot resize window by dragging the top edge

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  This affects only users of Metacity with compositing mode disabled (which are 
usually users on old hardware or virtualized systems).

  [Test Case]
  * gsettings set org.gnome.metacity compositing-manager false;
  * Try resizing a window by dragging its top edge.

  [Regression Potential]
  The fix is one-line and should not cause any regressions.

  -

  Bug Version: 1:3.18.4-0ubuntu0.3

  Metacity running without composite manager.

  Users cannot resize window by dragging its top edge.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.4-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jun 27 23:18:31 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: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1596574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Chris J Arges]

Hello william, or anyone else affected,

Accepted upower into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.4-2ubuntu0.3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: upower (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1546641

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  SRU TEST CASE (upower)
  --
  On affected machines, unity-settings-daemon crashes immediately on login, as 
due to a kernel bug upowerd takes a very long time to start. With the fixed 
package the crash is fixed. Power status information will still be wrong, but 
at least theme, hotkeys, and all other unity-settings-daemon functionality will 
work.

  This can be synthetically tested with:

     DBUS_SYSTEM_BUS_ADDRESS=foo upower --dump

  With the current xenial version this causes a segfault, while with the
  fix you get a proper error message.

  Fix: https://cgit.freedesktop.org/upower/commit/?id=932a6a39e3
 https://cgit.freedesktop.org/upower/commit/?id=4e83fabac
  (The second one is not crucial, but provides a much better failure mode for 
the "upower" CLI tool).

  Regression potential: This changes the core behaviour of libupower.
  The patch is carefully written to be backwards compatible to the
  extent possible, but changing the behaviour is necessary to fix this
  bug (see commit log for details). Thus clients such as unity-control-
  center, unity-settings-daemon, or mate-power-manager should be tested
  as part of the verification.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1546641/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 1582687] Update Released

[Chris J Arges]

The verification of the Stable Release Update for metacity has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1582687

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1539694] Update Released

[Chris J Arges]

The verification of the Stable Release Update for libopenobex has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libopenobex in Ubuntu.
https://bugs.launchpad.net/bugs/1539694

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  Fix Released
Status in libopenobex source package in Xenial:
  Fix Released
Status in libopenobex package in Debian:
  Fix Released

Bug description:
  * Impact
  obex-check-device segfaults when called with the wrong number of arguments, 
which is done sometimes on device insertion

  * Test case
  $ /usr/sbin/obex-check-device "one"

  shouldn't segfault

  * Regression potential
  it changes the invalid number of argument case, shouldn't impact on anything 
else

  ---

  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  the ubuntu software center doesn't run
  I think that the update from ubuntu 14.10ls to 16.04ls fail in my pc

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex1 1.7.1-3
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic i686
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Fri Jan 29 16:44:34 2016
  Dependencies:
   gcc-5-base 5.3.1-7ubuntu1
   libc6 2.21-0ubuntu5
   libgcc1 1:5.3.1-7ubuntu1
   libusb-0.1-4 2:0.1.12-28
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2016-01-20 (8 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcCmdline: /usr/sbin/obex-check-device 0bda
  ProcEnviron:

  SegvAnalysis:
   Segfault happened at: 0xb754196e <__GI_strtoul_l_internal+110>:  movsbl 
(%eax),%edx
   PC (0xb754196e) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=0, 
loc=0xb76c8d00 <_nl_global_locale>) at strtol_l.c:297
   __strtoul (nptr=0x0, endptr=0x0, base=16) at strtol.c:109
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to xenial on 2016-01-25 (4 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1539694/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586260] Update Released

[Chris J Arges]

The verification of the Stable Release Update for xorg-server-lts-vivid
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1586260

Title:
  System freeze & no display if set External monitor as primary
  (Performance mode)

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Trusty:
  Invalid
Status in xorg-server-lts-vivid source package in Trusty:
  Fix Released
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  System freeze & no display if set External monitor as primary
  (Performance mode)

  [Test case]

  1. Setup Graphic mode to Performance mode
  2. Plug External monitor with HDMI
  3. Set display mode to External monitor only is pass
  4. Set display mode to Extend/ Mirror mode

  Expected results: External monitor can be set as primary normally

  Actual results: System freeze & no display if set External monitor as
  primary (Performance mode)

  [Regression potential]

  Unknown right now, upstream review pending.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1586260/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Chris J Arges]

Hello Dantali0n, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.4-0ubuntu0.3 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1582687

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1433013] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-session has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in gnome-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Released
Status in upstart source package in Xenial:
  Fix Committed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started processes lack them.

  [Impact]
  Some environment variables are missing from apps that are launcher from 
Alt+f2 command lens, or in general with dbus-activation (an example might be 
gnome-terminal, global menu not working).

  [Test case]
  Super Key -> "xterm" -> Enter -> env | grep SSH

  it should return something like:
  SSH_AUTH_SOCK=/run/user/$UID/keyring-/ssh

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  The returned values should match the results got from the xterm
  instance that has been ran from unity dash application lens (the one
  opened with Super).

  The same should be checked for the variable XDG_MENU_PREFIX

  Before this fix happened we had this result:
    via Super Key -> the environment is correct
    via Alt-F2 -> it is not

  [Regression potential]

  Nothing known. Some variables could be overridden, but this is
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1551897] Update Released

[Chris J Arges]

The verification of the Stable Release Update for ccid has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897

Title:
  Excessive CPU utilization

Status in ccid package in Ubuntu:
  Fix Released
Status in pcsc-lite package in Ubuntu:
  Invalid
Status in ccid source package in Xenial:
  Fix Released
Status in pcsc-lite source package in Xenial:
  Invalid
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  [Impact]

  When hotplugging a composite USB device that expose multiple
  interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not
  correctly de-initialize the USB library when it skips over the non-
  CCID interface.

  This subsequently results in pcscd (or, presumably, anything that
  loads libccid, though I don't think anything else does) either using
  100% CPU or segfaulting when the device is unplugged.

  This seems worthy of an SRU as it is an easily reproducible bug with a
  simple, targeted fix.

  [Test Case]

  1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo 
systemctl restart pcscd if a potentially fixed package has just been installed)
  2. Plug and then unplug a composite USB device that includes a CCID interface 
(such as a Yubikey NEO)
  3. Observe that pcscd has crashed with a segfault (sudo systemctl status 
pcscd)

  [Regression Potential]

  The patch is quite narrow, and thus the potential for regression
  should be limited. The new code adds calls to close_libusb_if_needed,
  which is already written to be fairly conservative.

  The worst case here is likely an unexpected call to libusb_exit, which
  could cause libusb to get into an inconsistent state. However, in
  practice the call seems quite safe, and the likelihood of regression
  low.

  ==
  Original bug description:

  In xenial, pcscd CPU utilization occasionally goes haywire:

    PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1551897/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1565267] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-calendar has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1565267

Title:
  Gnome Calendar has white corners

Status in GNOME Calendar:
  Fix Released
Status in Ubuntu theme:
  New
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Released

Bug description:
  * Impact

  the gnome-calendar window corners don't look right (white squares
  instead of rounded)

  * Test case
  start gnome-calendar under unity and look at the windows corner, they should 
be rounded. The update also include a bugfix new revesion so make sure calendar 
events are correctly listed and that the calendar works correctly

  * Regression potential
  the update has only small bugfixes and should be safe but keep an eye for new 
issues

  --

  Gnome Calendar still looks like it is not using the proper CSD that
  other Gnome apps do (maps, weather, etc.) nor does it look like a
  patched Unity app.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.19.92-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  2 07:12:41 2016
  InstallationDate: Installed on 2016-03-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1565267/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1562822] Update Released

[Chris J Arges]

The verification of the Stable Release Update for unity-control-center
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1562822

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth source package in Xenial:
  New
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1555170] Update Released

[Chris J Arges]

The verification of the Stable Release Update for adwaita-icon-theme has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1555170

Title:
  [SRU] Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Invalid
Status in adwaita-icon-theme source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  New

Bug description:
  [Impact]

   * Bluetooth connected speakers appear in the Bluetooth settings and
  the Sound settings of System Settings with a broken icon.

   * This change simply moves the missing icon in to the default set.

  
  [Test Case]

   * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
   * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
   * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.

  [Regression Potential]

   * Very low.  This patch simply adds the missing icon to the default
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1555170] Re: [SRU] Bad icon for bluetooth sound device

[Chris J Arges]

** Also affects: unity-control-center (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: adwaita-icon-theme (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1555170

Title:
  [SRU] Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Invalid
Status in adwaita-icon-theme source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  New

Bug description:
  [Impact]

   * Bluetooth connected speakers appear in the Bluetooth settings and
  the Sound settings of System Settings with a broken icon.

   * This change simply moves the missing icon in to the default set.

  
  [Test Case]

   * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
   * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
   * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.

  [Regression Potential]

   * Very low.  This patch simply adds the missing icon to the default
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1575152] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gst-plugins-base1.0
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1575152

Title:
  [SRU] gstreamer 1.8.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 13:16:04 2016
  InstallationDate: Installed on 2015-06-05 (325 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1575152/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

[Chris J Arges]

Hello Marco, or anyone else affected,

Accepted upower into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.4-2ubuntu0.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: upower (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  New
Status in unity-settings-daemon source package in Xenial:
  New
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1487148] Re: [MIR] fonts-stix -- to replace xfonts-mathml

[Chris J Arges]

Hi, 'fonts-stix' is not in main for wily. Is there another way to fix
this for wily without pulling in a universe package?

** Also affects: libreoffice (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: fonts-stix (Ubuntu Wily)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1487148

Title:
  [MIR] fonts-stix -- to replace xfonts-mathml

Status in fonts-stix package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in fonts-stix source package in Wily:
  New
Status in libreoffice source package in Wily:
  New

Bug description:
  [Availability]
  already in xenial

  
  [Rationale]
  The libreoffice-common package currently recommends xfonts-mathml, which was 
removed from Debian in 2014 with the rationale that it is superseded by 
fonts-stix (and that it has a license problem).  Please replace it with 
fonts-stix.

  [Security]
  no executable code

  [Quality assurance]
  no executable code

  [Dependencies]
  no further deps needed: see 
http://people.canonical.com/~ubuntu-archive/component-mismatches.txt

  [Standards compliance]
  trivial package, maintained by Debian

  [Maintenance]
  no executable code, maintained by Debian, stable/low frequency updates

  [Background information] 
  Since xfonts-mathml is only a Recommends: rather than Depends:, I'm going to 
go ahead and remove xfonts-mathml from wily.  If for some reason fonts-stix is 
not a suitable replacement and xfonts-mathml is still needed, please feel free 
to reupload it to the archive and close this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-stix/+bug/1487148/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1578821] Re: I'm not able to install galician language in Ubuntu 16.04

[Chris J Arges]

Hello Marcos, or anyone else affected,

Accepted language-selector into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.165.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: language-selector (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1578821

Title:
  I'm not able to install galician language in Ubuntu 16.04

Status in language-selector package in Ubuntu:
  Fix Released
Status in libreoffice-dictionaries package in Ubuntu:
  In Progress
Status in language-selector source package in Xenial:
  Fix Committed
Status in libreoffice-dictionaries source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Installing the Galician language via Language Support fails. The
  reason is that there is currently two hunspell spellchecking packages
  in the archive:

  * hunspell-gl-es, provided by the hunspell-gl-es source package
  * hunspell-gl, provided by the libreoffice-dictionaries source package

  Even if hunspell-gl-es conflicts to hunspell-gl, having both of them
  available in the archive is not compatible with the way the writing
  aids is pulled via Language Selector. The proposed upload in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/lo-dicts-symlinks

  drops the hunspell-gl binary from libreoffice-dictionaries.

  [Test Case]

   * Open Language Support
   * Try to install Galician

  [Regression Potential]

  Low.

  [Original description]

  Hi

  I just installed Ubuntu 16.04. So as I try to install galician
  language I get this notification:

  Transaction failed: Package dependencies cannot be resolved
   The following packages have unmet dependencies:

  hunspell-gl-es:

  Then nothing happens. Several fellows got the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1578821/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1576656] Update Released

[Chris J Arges]

The verification of the Stable Release Update for file-roller has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1576656

Title:
  [SRU] 3.16.5 stable update

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Xenial:
  Fix Released

Bug description:
  That's a new stable bugfix GNOME update

  * Impact

  it fixes some small bugs and leaks and has updated translations

  * Test case

  Try to open/compressed/extract some archives

  * Regression potential

  There are no specific change to watch out for, just make sure things
  keep working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1576656/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1575248] Update Released

[Chris J Arges]

The verification of the Stable Release Update for fwupd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1575248

Title:
  "AppStream cache update completed, but some metadata was ignored due
  to errors." on "sudo apt-get update"

Status in AppStream:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in appstream package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Checks for apt updates using apt or apt-get also update the
  appstream cache.  Some of the appstream metadata installed locally
  isn't strictly valid as it's missing two fields.

  [Test Case]

   * fwupdmgr refresh
   * apt update
   * check for errors about metadata being ignored

  [Regression Potential]

   * This is just changing the XML metadata locally, I don't see any
  regression potential.

  [Other Info]
   
   * This fix has been applied upstream: 
https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96

  [Original report]

  I have found that when there are new packages available which my
  machine doesn't know about yet, if I run "sudo apt-get update" this is
  the output:

  Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
  Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 
kB]
  Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages [28 B]
  Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease 
[82.2 kB]
  Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 
Packages [28 B]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [28 B]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages [28 B]
  Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 
Packages [28 B]
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
Translation-en [28 B]
  Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 
[1,201 kB]
  Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 
[1,196 kB]
  Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB 
[426 kB]
  Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en 
[568 kB]
  Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 
Metadata [733 kB]
  Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons 
[409 kB]
  Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages [8,344 B]
  Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 
Packages [8,684 B]
  Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en_GB [2,556 B]
  Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en [2,908 B]
  Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 
Metadata [186 B]
  Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 
[7,532 kB]
  Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 
[7,512 kB]
  Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe 
Translation-en_GB [3,040 kB]
  Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en 
[4,354 kB]
  Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 
Metadata [3,410 kB]
  Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 
Icons [7,448 kB]
  Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages [144 kB]
  Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages [140 kB]
  Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en_GB [88.1 kB]
  Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en [106 kB]
  Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 
Metadata [63.8 kB]
  Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 
Icons [230 kB]
  Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages [28 B]
  Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages [28 B]
  Get:36 http://gb.archive.ubuntu.com/ubuntu 

[Desktop-packages] [Bug 1559284] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1559284

Title:
  Increase the number of displayed reviews

Status in GNOME Software:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  * Impact
  gnome-software displays only 10 reviews and doesn't give you a way to load 
more

  * Test case
  open a popular application (eg. Audacity, GIMP) in g-s and look at the 
reviews, there should be more than 10

  * Regression potential
  we load more data so the details page might be a bit slower to load

  

  Using xenial it seems there is no way to load more review? I reported
  that upstream but it might be a choice for them since they don't have
  lot of reviews on their server

  That commit suggests the UI exists
  
https://git.gnome.org/browse/gnome-software/commit/?id=a92da2e47478ef9c124367ad2a87efcd3f2375c0

  There might be a need to write the backend side though

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1559284/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1559185] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1559185

Title:
  Doesn't understand apt: urls

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact:
  gnome-software doesn't understand apturls

  Test case:
  start "gnome-software apt:gedit", it should opens the gedit page, clicking on 
an "apt:" url in firefox should open gnome-software on the corresponding 
package 
  one limitation, it only works for apps gnome-software knows about though (so 
mostly graphical softwares)

  Regression potential:
  it only adds support for a new type or url shouldn't regress existing code

  -

  Doing the same in software-center opens the gedit details page

  software-center used to the default handler for apt: urls, I've
  changed that to apturl but if we want to keep the previous user
  experience we should have gnome-software handle those

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1559185/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571414] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1571414

Title:
  Size of not-installed applications is "Calculating..." in Details
  section

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact:
  the details view doesn't display a size for non installed softwares

  Test case:
  open gnome-software, click on an non-installed software, look at the Size 
information, it should have a value

  Regression potential:
  having this information requires adding infos to items which didn't have 
some, so means more backend work which might slow down things

  -

  The size of not-installed applications stays "Calculating..." in the
  Details section, and apparently never changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160415.1.9c08d97.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 17 23:06:38 2016
  InstallationDate: Installed on 2016-03-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571414/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1562033] Update Released

[Chris J Arges]

The verification of the Stable Release Update for xinit has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1562033

Title:
  package xinit 1.3.4-3 failed to install/upgrade: subprocess installed
  post-installation script returned error exit status 1

Status in xinit package in Ubuntu:
  Fix Released
Status in xinit source package in Xenial:
  Fix Released
Status in xinit source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  upgrade fails if /etc/X11/xinit/xinitrc is missing because the
  postinst script doesn't check for it's existence before running chmod
  on it.

  [Test case]

  rm /etc/X11/xinit/xinitrc
  /var/lib/dpkg/info/xinit.postinst configure 1

  [Regression potential]

  nope

  --

  During remote do-release-upgrade -d from a wily box.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar 25 15:06:11 2016
  DistUpgraded: 2016-03-25 15:10:36,689 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-15-generic, x86_64: installed
   nvidia-340, 340.96, 4.2.0-34-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-15-generic, x86_64: installed
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1044]
  InstallationDate: Installed on 2013-03-11 (1109 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=467f6a66-74b5-4070-90db-2150245db2cf ro quiet splash radeon.audio=1 
radeon.dpm=1 clocksource=hpet hpet=enable nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: xinit
  Title: package xinit 1.3.4-3 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago)
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Mar 17 18:05:50 2016
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  

[Desktop-packages] [Bug 1564621] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1564621

Title:
  Version unknown of not-installed applications, it appears for
  installed ones

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  non-installed software don't have a version info

  Test case
  start gnome-software, click on a non installed software, the version should 
be a number instead of "unknown"

  Regression potential
  having this information requires adding infos to items which didn't have 
some, so means more backend work which might slow down things

  --

  Applications show their version unknown in the Details section when
  they are not installed. The version shows up for installed
  applications.

  Version should appear for both not-installed and installed
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1564621/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1573408] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1573408

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1573408/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1575104] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1575104

Title:
  SRU including some fixes/improvements/enabling snap backend

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  gnome-software just landed in Ubuntu this cycle and still has some 
reliability issues

  Test case

  deb backend
  In addition of testing specific fixes listed in the changelog also make sure 
there is no functional regressions.

  snap backend
  the new backend is going to be enable starting with that version, searching 
for a snap (e.g "hello-world") should work, installing it should prompt for u1 
credentials and successfully install

  Regression impact
  the snap backend was not enabled before so that shouldn't create new issues, 
the deb changes are mostly covered by specific bug reports and the other small 
tweaks shouldn't create issues

  -

  The first gnome-software SRU is going to include some fixes and code
  improvements not matching referenced bugs, we also wants to enable the
  snaps backend since it's working well enough for that now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1575104/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1361764] Update Released

[Chris J Arges]

The verification of the Stable Release Update for open-gram has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to open-gram in Ubuntu.
https://bugs.launchpad.net/bugs/1361764

Title:
  Update sunpinyin-data to >=20130220

Status in open-gram package in Ubuntu:
  Fix Released
Status in open-gram source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * fails to convert ue and iong syllables,
  Ref: https://github.com/sunpinyin/sunpinyin/issues/42

  [Test Case]

   * ibus-sunpinyin will display correct candidate choices for yue,
  jiong, qiong, and xiong.

  [Regression Potential]

   * This is a pure data package, only potential is other wrong data,
  but the updated version has been used for almost two years without new
  issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-gram/+bug/1361764/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1310346] Update Released

[Chris J Arges]

The verification of the Stable Release Update for open-gram has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to open-gram in Ubuntu.
https://bugs.launchpad.net/bugs/1310346

Title:
  "jue","que","xue" mapped to "jiong", "qiong", "xiong" in 14.04

Status in open-gram package in Ubuntu:
  Fix Released
Status in open-gram source package in Trusty:
  Fix Released

Bug description:
  OS: Ubuntu Desktop 14.04

  When inputting Chinese by SunPinYin, I found following item are mapped
  in wrong way:

  ```
  jue => jiong
  que => qiong
  xue => xiong
  ```

  I found same issue at
  https://github.com/sunpinyin/sunpinyin/issues/31#issuecomment-12486150

  And as the owner said, it might be 'dict.utf8' is not up to date.

  It is an important bug, I have to switch to another IM for a
  workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-gram/+bug/1310346/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1564268] Please test proposed package

[Chris J Arges]

Hello Martin, or anyone else affected,

Accepted postgresql-9.3 into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.3/9.3.12-0ubuntu0.14.04
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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: postgresql-9.4 (Ubuntu Wily)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1564268

Title:
  New upstream microreleases 9.1.21, 9.3.12, 9.4.7, 9.5.2

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Committed
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Wily:
  Fix Committed
Status in postgresql-9.5 source package in Xenial:
  Fix Committed

Bug description:
  PostgreSQL announced new microreleases, which also fix a few CVEs:
  http://www.postgresql.org/about/news/1656/

  However, the security issues only affect 9.5 (xenial), thus for
  stables we only need normal SRUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1564268/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1564268] Please test proposed package

[Chris J Arges]

Hello Martin, or anyone else affected,

Accepted postgresql-9.4 into wily-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.7-0ubuntu0.15.10
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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1564268

Title:
  New upstream microreleases 9.1.21, 9.3.12, 9.4.7, 9.5.2

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Committed
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Wily:
  Fix Committed
Status in postgresql-9.5 source package in Xenial:
  Fix Committed

Bug description:
  PostgreSQL announced new microreleases, which also fix a few CVEs:
  http://www.postgresql.org/about/news/1656/

  However, the security issues only affect 9.5 (xenial), thus for
  stables we only need normal SRUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1564268/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1564268] Please test proposed package

[Chris J Arges]

Hello Martin, or anyone else affected,

Accepted postgresql-9.1 into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.21-0ubuntu0.14.04
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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1564268

Title:
  New upstream microreleases 9.1.21, 9.3.12, 9.4.7, 9.5.2

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Committed
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Wily:
  Fix Committed
Status in postgresql-9.5 source package in Xenial:
  Fix Committed

Bug description:
  PostgreSQL announced new microreleases, which also fix a few CVEs:
  http://www.postgresql.org/about/news/1656/

  However, the security issues only affect 9.5 (xenial), thus for
  stables we only need normal SRUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1564268/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1564268] Re: New upstream microreleases 9.1.21, 9.3.12, 9.4.7, 9.5.2

[Chris J Arges]

Hello Martin, or anyone else affected,

Accepted postgresql-9.1 into precise-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.21-0ubuntu0.12.04
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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: postgresql-9.1 (Ubuntu Precise)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: postgresql-9.1 (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1564268

Title:
  New upstream microreleases 9.1.21, 9.3.12, 9.4.7, 9.5.2

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Committed
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Wily:
  Fix Committed
Status in postgresql-9.5 source package in Xenial:
  Fix Committed

Bug description:
  PostgreSQL announced new microreleases, which also fix a few CVEs:
  http://www.postgresql.org/about/news/1656/

  However, the security issues only affect 9.5 (xenial), thus for
  stables we only need normal SRUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1564268/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1409032] Re: gvfsd-smb: very high CPU utilisation

[Chris J Arges]

Just did a fresh ISO install of xenial and discovered this same issue.
'killall gvfsd-smb-browse' temporarily solved my issue.

** Changed in: gvfs (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1409032

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1554004] Update Released

[Chris J Arges]

The verification of the Stable Release Update for xserver-xorg-video-
openchrome has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-openchrome in
Ubuntu.
https://bugs.launchpad.net/bugs/1554004

Title:
  Segfault on X startup with VX900

Status in openchrome:
  Fix Released
Status in xserver-xorg-video-openchrome package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-openchrome source package in Trusty:
  Fix Released
Status in xserver-xorg-video-openchrome source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Prevents from using X at all with some VIA chipsets - a segfault
  occurs and is logged in Xorg.log

  [Test Case]

   * Start X on a affected hw (e.g. VX900).

   * Examine Xorg.log after crash.

  [Regression Potential]

   * This is a bug fixed upstream
  (https://cgit.freedesktop.org/openchrome/xf86-video-
  openchrome/commit/?id=ecb1695ac2de1d840c036f64b5b71602e0f522a4).

   * The fix is a one-liner with minimal impact.

  [Other Info]

   * Original bug description:

  There is a segfault in Xorg.log visible when starting X on Trusty
  14.04 with the following hardware:

  00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX900 
Graphics [Chrome9 HD] [1106:7122] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- https://bugs.launchpad.net/openchrome/+bug/1554004/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1520229] Update Released

[Chris J Arges]

The verification of the Stable Release Update for simple-scan has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1520229

Title:
  Wrong Epson URL

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.18 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Dialog that prompts user to install Epson drivers goes to an invalid URL.

  [Test Case]
  1. Connect an Epson scanner
  2. Open Simple Scan
  3. Click "Install drivers" link
  4. Follow link to Epson website

  Expected result:
  Browser goes to Epson website

  Observed result:
  Browser goes to invalid URL www.epsom.com/support

  [Regression Potential]
  Low. URL just corrected for typo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1520229/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1515446] Update Released

[Chris J Arges]

The verification of the Stable Release Update for network-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1515446

Title:
  network file systems in FSTAB no longer mount at boot with
  NetworkManager

Status in One Hundred Papercuts:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Wily:
  Fix Released
Status in network-manager package in Debian:
  New

Bug description:
  [Impact]

   * This breaks NFS mounts coming up reliably.  In some cases this can
  be quite intermittent.

  [Test Case]

   1. Add a mountpoint to an NFS share by name to fstab.
   2. See that it mounts with the mount command.
   3. Reboot 5+ times, note that it doesn't come up all (or the majority of the 
time).  

  [Regression Potential]

   * There could be a regression for the same reason it's blocked in
  Debian, because of dependency issues with packages not converted to
  systemd that want to run /etc/rcS.d/.

  You can check for this by looking for breaking/disable services during
  bootup.  Ubuntu is in a much better state than Debian, but there is a
  possibility we missed something.

  Otherwise, this will increase boot time, but when the user logs the
  networking will be more likely to be ready.

  
  -Previous description-
  After a fresh install of 15.10, nfs shares no longer mount on boot.   I'm 
using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
    Installed: 1:1.2.8-9ubuntu10
    Candidate: 1:1.2.8-9ubuntu10
    Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
     Loaded: loaded (/etc/fstab)
     Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
     man:systemd-fstab-generator(8)
    Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1515446/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1495828] Re: xchat-gnome crashed with SIGFPE in gtk_xtext_check_ent_visibility()

[Chris J Arges]

Hello Daniel, or anyone else affected,

Accepted xchat-gnome into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xchat-
gnome/1:0.30.0~git20141005.816798-0ubuntu6.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: xchat-gnome (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: xchat-gnome (Ubuntu Wily)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1495828

Title:
  xchat-gnome crashed with SIGFPE in gtk_xtext_check_ent_visibility()

Status in xchat-gnome package in Ubuntu:
  Fix Released
Status in xchat-gnome source package in Wily:
  Fix Committed

Bug description:
  * Impact
  xchat-gnome sometime segfaults on start

  * Test case
  no easy way to trigger the issue so just make sure that xchat-gnome starts 
without issue

  * Regression potential
  the change only returns when widgets are not ready yet, shouldn't create any 
issue

  -

  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep 15 09:09:35 2015
  ExecutablePath: /usr/bin/xchat-gnome
  InstallationDate: Installed on 2015-04-30 (137 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: xchat-gnome
  Signal: 8
  SourcePackage: xchat-gnome
  StacktraceTop:
   ?? ()
   gtk_xtext_check_marker_visibility ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: xchat-gnome crashed with SIGFPE in gtk_xtext_check_marker_visibility()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio autopilot cdrom dip libvirtd lpadmin plugdev sambashare 
sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1495828/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1315442] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1315442

Title:
  Extra "fi" in /etc/init.d/gdm

Status in Ubuntu GNOME:
  Triaged
Status in gdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Released
Status in gdm source package in Utopic:
  Won't Fix

Bug description:
  Ubuntu release 14.04 LTS
  gdm 3.10.0.1-0ubuntu3

  I just tried to start gdm with "/etc/init.d/gdm start " and got the
  message:

  /etc/init.d/gdm: 79: /etc/init.d/gdm: Syntax error: "fi" unexpected
  (expecting "}")

  I'm aware of service(8) but cjwatson said I should report this as a
  bug anyway!

  Owen

  SRU Information:

  [Impact]

   * Anyone who tries to use the sysv style /etc/init.d/gdm script to control
 gdm may get a syntax error which disallows the script from running,
 bombing out to the command line with an unfriendly error

   * This problem effects vivid, utopic and trusty.  Without this fix
 backported, the functionality of the sysv style script for controlling
 the gdm service is broken under certain circumstances.  The resulting
 unfriendly error is also unprofessional and gives a feeling of
 brokenness to Ubuntu in all three of these releases, including the
 ones to be backported to.

   * This upload is a series of three patches.  The syntax error
 results from a single line in each of the debian/gdm.init files which get
 installed as the /etc/init.d/gdm shell script.  The problem is an extra
 unmatched "fi" that results in a syntax error if the corresponding line
 is interpreted

  [Test Case]

   * To test the fix in vivid, type the following commands before and after
 the updated package is installed:

 cd /etc/init.d
 sudo ./gdm

 If the script exits with a syntax error before the package with
 the fix is installed, you have verified the bug.

 If the script exits with a syntax error after the package is installed,
 the fix did not work.
 If the script does not indicate a syntax error after the package
 is installed, the fix worked

 To test the fix on utopic, do the identical test as in vivid above
 but instead use the following single command to invoke the script:

 sudo /etc/init.d/gdm

 To test the fix on trusty, do the test as in vivid and utopic,
 but use the following commands to change directories and invoke
 the script:

 cd /etc/init.d
 sudo ./gdm
 sudo ./gdm start

 In this case, both times you run the script it should exit with
 the syntax error before installing the package and neither time
 after installing the package.

  [Regression Potential]

   * Any scripts which may call this script which happen to mistakenly
 rely on it to fail could perhaps behave differently, with unknown
 results possible

  [Other Info]
   
   * Using or not using sudo before each command may affect the tests
 with varying output that may be unexpected.  In all cases, however,
 if the script bombs on a syntax error happens mentioning a line number
 and "fi" the test definitely either verified the bug or definitively
 showed the package did not fix the bug (or was not installed correctly).

 A situation which arose during the testing is that depending on the
 whether the patch is on vivid, utopic or trusty, calling the script
 in different ways (fully qualified path vs. changing the current
 directory to /etc/init.d and using ./gdm, for instance, or
 including or not including the 'start' parameter) causes the
 test to behave differently, for instance failing silently or working
 depending on how the script is called even with the syntax error present. 
 This is why there are different command lines for each version of the
 patch for testing.

 I did some tracing on why this happened, and the reasons seem buried deep
 within the trees of scripts called beneath /etc/init.d/gdm and are outside
 the scope of this fix and do not invalidate this fix.  This fix deals
 with a simple top level shell script syntax error that can be successfully
 tested for as indicated above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1315442/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : 

[Desktop-packages] [Bug 1547109] [NEW] [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] Underruns, dropouts or crackling sound

[Chris J Arges]

Public bug reported:

To reproduce play Audio CD using Rhythmbox.
I noticed that the audio is crackling (not overdriven, nor skipping.)
However I can play the audio tracks fine with Totem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   arges  1968 F...m pulseaudio
 /dev/snd/controlC0:  arges  1968 F pulseaudio
CurrentDesktop: Unity
Date: Thu Feb 18 11:01:16 2016
InstallationDate: Installed on 2015-09-04 (167 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150903)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SKLSE2R1.R00.B089.B00.1506160228
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Skylake DT DDR4 RVP8
dmi.board.vendor: Intel Corp.
dmi.board.version: 1
dmi.chassis.asset.tag: Un-Supported
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSKLSE2R1.R00.B089.B00.1506160228:bd06/16/2015:svnIntelCorporation:pnSkylakeClientplatform:pvr0.1:rvnIntelCorp.:rnSkylakeDTDDR4RVP8:rvr1:cvnIntelCorporation:ct3:cvr0.1:
dmi.product.name: Skylake Client platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1547109

Title:
  [Skylake Client platform, Realtek ALC898, Green Line Out, Rear]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  To reproduce play Audio CD using Rhythmbox.
  I noticed that the audio is crackling (not overdriven, nor skipping.)
  However I can play the audio tracks fine with Totem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   arges  1968 F...m pulseaudio
   /dev/snd/controlC0:  arges  1968 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 18 11:01:16 2016
  InstallationDate: Installed on 2015-09-04 (167 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150903)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SKLSE2R1.R00.B089.B00.1506160228
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Skylake DT DDR4 RVP8
  dmi.board.vendor: Intel Corp.
  dmi.board.version: 1
  dmi.chassis.asset.tag: Un-Supported
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSKLSE2R1.R00.B089.B00.1506160228:bd06/16/2015:svnIntelCorporation:pnSkylakeClientplatform:pvr0.1:rvnIntelCorp.:rnSkylakeDTDDR4RVP8:rvr1:cvnIntelCorporation:ct3:cvr0.1:
  dmi.product.name: Skylake Client platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547109/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1240198] Update Released

[Chris J Arges]

The verification of the Stable Release Update for ibus has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1240198

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1539774] [NEW] /usr/lib/lbdb/mutt_ldap_query throws deprecated warnings

[Chris J Arges]

Public bug reported:

When using lbdb with mutt for ldap queries you'll get various warnings
about not escaping brackets properly.

Here is another example of the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1259881

** Affects: lbdb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lbdb in Ubuntu.
https://bugs.launchpad.net/bugs/1539774

Title:
  /usr/lib/lbdb/mutt_ldap_query throws deprecated warnings

Status in lbdb package in Ubuntu:
  New

Bug description:
  When using lbdb with mutt for ldap queries you'll get various warnings
  about not escaping brackets properly.

  Here is another example of the issue:
  https://bugzilla.redhat.com/show_bug.cgi?id=1259881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lbdb/+bug/1539774/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1501300] Re: [SRU] Wily (15.10) this package got not compiled with __cxx11 support

[Chris J Arges]

Hello Matthias, or anyone else affected,

Accepted llvm-toolchain-3.4 into wily-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.4/1:3.4.2-13ubuntu2.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: llvm-toolchain-3.4 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: llvm-toolchain-3.4 (Ubuntu Wily)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1501300

Title:
  [SRU] Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.4 source package in Wily:
  Fix Committed

Bug description:
  [Impact]

  * with gcc-5 default, and llvm-3.4 built with the gcc-4.9, people
  can't link programs using cxx11 support

  [Test Case]

  * compile a program using cxx11 e.g. using boost libraries

  [Regression Potential]

  * llvm-3.4 is a compiler, and the change should affect only cxx11
  support (since the library is ABI compatible).

  So, fixing cxx11 support shouln't have any regression, only the
  feature will start working, while it wasn't before

  [Other Info]
   
  * Doko ack'd the SRU, and it should be the best voice here, for sure better 
than mine :)


  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529454] Re: dm-tool add-nested-seat fails

[Chris J Arges]

Hello Petter, or anyone else affected,

Accepted lightdm into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.16.7-0ubuntu1 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Wily)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1529454

Title:
  dm-tool add-nested-seat fails

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Won't Fix
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  dm-tool add-nested-seat doesn't work anymore.

  [Test Case]
  1. Log in
  2. From a terminal run "dm-tool add-nested-seat"

  Expected result:
  A window opens with a login screen

  Observed result:
  A window opens with a black screen. An error is reported in the terminal:
  Unable to add seat: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to 
start seat

  [Regression Potential]
  The code change could affect other remote X server configurations, though 
this seems unlikely. Regression tests confirm other behaviour still works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1529454/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1525554] Re: [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

[Chris J Arges]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1525554

Title:
  [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound on brand new HP ProBook 470 G3 after installing Ubuntu 14.04
  on headphones or internal speakers.

  Connecting a USB headphone and microphone both work, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ronald 2199 F pulseaudio
ronald 2513 F alsamixer
  CurrentDesktop: Unity
  Date: Sat Dec 12 19:36:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
127: Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.02
  dmi.board.name: 8102
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.1F
  dmi.chassis.asset.tag: 5CD54286XY
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.02:bd09/30/2015:svnHP:pnHPProBook470G3:pvr:rvnHP:rn8102:rvrKBCVersion16.1F:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 470 G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525554/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1506107] Update Released

[Chris J Arges]

The verification of the Stable Release Update for xserver-xorg-video-
intel has completed successfully and the package has now been released
to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1506107

Title:
  Bad webcam video rendering when using XV acceleration on Skylake gpus.

Status in HWE Next:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-vivid source package in Trusty:
  In Progress
Status in xserver-xorg-video-intel source package in Vivid:
  Fix Released

Bug description:
  CPU: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
  GPU: Intel Corporation Device [8086:1916] (rev 07)
  Webcam: 0bda:57e3 Realtek Semiconductor Corp.

  [Impact] 
  We noticed that webcam output on a wide range of skylake systems contained 
corruption during certification testing of OEM machines which uses a certain 
gstreamer pipeline. An example of the corruption is attached.

  [Test Case]
  1. Boot ubuntu 14.04.3 or 15.04 on a machine with a skylake intel GPU and a 
webcam
  2. Login system and open a terminal.
  4. Execute '$ gst-launch-0.10 v4l2src ! xvimagesink'

  Expect result:
  There should be no visual artifacts during video playing.  The artifacts will 
look like the attached video and be very obvious in the unfixed package.

  [Regression Potential] 
  Low, the fix is very minimal was included immediately after the 2.99.917 
release was made. It consists of 2 parts, a small patch 
(http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=cc9d7f603037d0d7eff346dd350f4d8b3f31)
 and a configure option change. The configure option change was in lieu of 
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=986cb2335c30792e24a7e2b930ecaa3fa051809a
 which flipped it on unconditionally and only affects i915_bpo in both of these 
releases as it requires a 4.0 or newer kernel (i915_bpo is a backport of i915 
from 4.2 that is only used on skylake). Both of these changes are already in 
wily's xserver-xorg-video-intel.

  It has been tested on a large number of machines during certification,
  and also by me on sandybridge, ivybridge, broadwell and skylake
  machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1506107/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1481561] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1470587] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1470587

Title:
  dm-tool manpage has a typo

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.12 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Small typo in dm-tool man page.

  [Test Case]
  1. View man page:
  $ man dm-tool

  Expected result:
  Says "switch"

  Observed result:
  Says "swith"

  [Regression potential]
  About as low as you can get...

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1470587/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1517685] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1517685

Title:
  XDMCP server starts without authentication if configured key does not
  exist

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  An incorrectly configured XDMCP server will start without authentication 
instead of disabling XDMCP / stopping LightDM.

  [Test Case]
  1. Set up LightDM to run an XDMCP server using an XDM authentication key, 
i.e. in lightdm.conf:
  [XDMCPServer]
  enabled=true
  key=key-name
  2. Do not create /etc/lightdm/keys.conf or do not define 'key-name' in 
keys.conf.
  3. Start LightDM
  4. Connect XDMCP client.

  Expected result:
  Either LightDM doesn't start or the XDMCP server doesn't start.

  Observed result:
  XDMCP server starts without authentication, any XDMCP client is able to 
connect. Debug message printed to log warning about missing key, but not easy 
to spot.

  [Regression Potential]
  Low - change is to not start LightDM if this case occurs. This could affect 
someone who currently has a misconfigured LightDM. In this case a warning 
message is printed to the log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1517685/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1504049] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1504049

Title:
  Chromium not working in guest session (need more AppArmor rules)

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Unable to run Chromium from guest session.

  [Test Case]
  1. Start Ubuntu
  2. From greeter select guest session
  3. Load Chromium

  Expected result:
  Chromium runs.

  Observed result:
  Chromium does not run.

  [Regression Potential]
  Low. The change is a few additional apparmor rules. There is a low risk that 
the new rules might allow a guest program to access a flaw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1390808] Update Released

[Chris J Arges]

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1390808

Title:
  VNC / XDMCP server cannot be configured to listen on specific
  interfaces

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  The XDMCP and VNC servers in LightDM allow connections on any network 
interface. It is desirable for these to be limited to a particular interface to 
limit who can connect (i.e. only allow local connections on 127.0.0.1).

  [Test Case]
  1. Enable the VNC server in LightDM in lightdm.conf:
  [VNCServer]
  enabled=true
  listen-address=127.0.0.1
  2. Start LightDM
  With this setup you should only be able to make a local connection.

  [Regression potential]
  Low. If the option is not set LightDM has the old behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1522955] [NEW] nm-applet not installed with xenial daily iso

[Chris J Arges]

Public bug reported:

I just did a fresh install of Xenial using the Desktop amd64 iso
(20151204). Upon boot I am connected to the wireless network (as I setup
in the install), but I do not see the nm-applet icon in the top right
corner in Unity.  If I type 'nm-applet' in a console it does not exist
and I need to install 'network-manager-gnome'.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec  4 14:05:28 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-12-04 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151204.1)
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.146  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Wired connection 1  21a117f2-4f13-47d3-94a5-9d927fe03c8c  802-3-ethernet   
1449259452  Fri 04 Dec 2015 02:04:12 PM CST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 -- 
 roareynet   3853fecf-75ee-460b-8952-4e387b07a299  802-11-wireless  
1449259456  Fri 04 Dec 2015 02:04:16 PM CST  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
roareynet   3853fecf-75ee-460b-8952-4e387b07a299  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --  
----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1522955

Title:
  nm-applet not installed with xenial daily iso

Status in network-manager package in Ubuntu:
  New

Bug description:
  I just did a fresh install of Xenial using the Desktop amd64 iso
  (20151204). Upon boot I am connected to the wireless network (as I
  setup in the install), but I do not see the nm-applet icon in the top
  right corner in Unity.  If I type 'nm-applet' in a console it does not
  exist and I need to install 'network-manager-gnome'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  4 14:05:28 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151204.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.146  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH  

[Desktop-packages] [Bug 1522955] Re: nm-applet not installed with xenial daily iso

[Chris J Arges]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1522955

Title:
  nm-applet not installed with xenial daily iso

Status in network-manager package in Ubuntu:
  New

Bug description:
  I just did a fresh install of Xenial using the Desktop amd64 iso
  (20151204). Upon boot I am connected to the wireless network (as I
  setup in the install), but I do not see the nm-applet icon in the top
  right corner in Unity.  If I type 'nm-applet' in a console it does not
  exist and I need to install 'network-manager-gnome'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  4 14:05:28 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151204.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.146  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  21a117f2-4f13-47d3-94a5-9d927fe03c8c  802-3-ethernet   
1449259452  Fri 04 Dec 2015 02:04:12 PM CST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 -- 
   roareynet   3853fecf-75ee-460b-8952-4e387b07a299  802-11-wireless  
1449259456  Fri 04 Dec 2015 02:04:16 PM CST  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
roareynet   3853fecf-75ee-460b-8952-4e387b07a299  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1522955/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1500516] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gvfs has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1500516

Title:
  /usr/lib/gvfs/gvfs-udisks2-volume-
  
monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  * Impact
  the gvfs disk monitors segfaults sometimes

  * Test case 
  no defined one, but the e.u.c reports should stop with the update

  * Regression potential
  check if disks and external storage devices are still correctly handled 
(listed in the launcher, included in nautilus, etc)

  -

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with version 1.24.1-1ubuntu1, the 
problem page at 
https://errors.ubuntu.com/problem/5d8e0bd14d691af888168ae3ff6a80e7fa95ebf4 
contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1500516/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1453174] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gvfs has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1453174

Title:
  Opening of magnet links broken

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  * Impact
  some urls are not correctly handled

  * Test case
  $ xdg-open "magnet:?xt=urn:btih:9BE2..."

  that should open a working dialog and not an error one

  * Regression potential
  check that the desktop handling of urls is correct (using xdg-open or click 
on e.g in website handlers in about dialogs)

  ---

  When clicking on a magnet link, transmission-remote-gtk always
  displays the error "invalid or corrupt torrent file".  This seems to
  be caused by xdg-open slightly modifying the link:

  $ xdg-open "magnet:?xt=urn:btih:9BE2..."

  results in

  $ transmission-remote-gtk "magnet:///?xt=urn:btih:9BE2..."

  which causes the problem mentioned.

  I'm using transmission-remote-gtk 1.1.1-1 from vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1453174/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1175947] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gvfs has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1175947

Title:
  gvfs-copy --preserve doesn't work with MTP devices

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  * When using gvfs-copy --preserve from a MTP device to local, the timestamp
is not preserved.

  * touch "localfile" --reference="MTP file" works OK.

  * I assume --preserve is not working.

  [Test Case]

  * Copy files from a MTP device using the --preserve option and check
timestamps.

  [Regression Potential]

  * Verify files copied from MTP devices and their attributes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1175947/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1517685] Re: XDMCP server starts without authentication if configured key does not exist

[Chris J Arges]

Hello Robert, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1517685

Title:
  XDMCP server starts without authentication if configured key does not
  exist

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  New
Status in lightdm source package in Wily:
  New

Bug description:
  [Impact]
  An incorrectly configured XDMCP server will start without authentication 
instead of disabling XDMCP / stopping LightDM.

  [Test Case]
  1. Set up LightDM to run an XDMCP server using an XDM authentication key, 
i.e. in lightdm.conf:
  [XDMCPServer]
  enabled=true
  key=key-name
  2. Do not create /etc/lightdm/keys.conf or do not define 'key-name' in 
keys.conf.
  3. Start LightDM
  4. Connect XDMCP client.

  Expected result:
  Either LightDM doesn't start or the XDMCP server doesn't start.

  Observed result:
  XDMCP server starts without authentication, any XDMCP client is able to 
connect. Debug message printed to log warning about missing key, but not easy 
to spot.

  [Regression Potential]
  Low - change is to not start LightDM if this case occurs. This could affect 
someone who currently has a misconfigured LightDM. In this case a warning 
message is printed to the log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1517685/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp