date:20160922

[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1605802

Title:
  Software Center still fails to install third-party .deb packages

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Bug #1573206 is persisting in 16.04.1. Clean installation of 16.04.1
  downloaded from Ubuntu website. Attempted to install Chrome using the
  .deb downloaded from their website. Software Center doesn't install,
  begins to hang just as it did before it was marked as fixed. Fix was
  supposed to be rolled into the point one ISO per comments in that
  tracker, but I am still experiencing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1605802/+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 1595414] Re: Awful generic selection for zh in Firefox

[Expired for fonts-arphic-uming (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: fonts-arphic-uming (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Awful generic selection for zh in Firefox

Status in fonts-arphic-ukai package in Ubuntu:
  Expired
Status in fonts-arphic-uming package in Ubuntu:
  Expired
Status in language-selector package in Ubuntu:
  Expired

Bug description:
  In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts-
  arphic-ukai/wily/revision/6, UMing and UKai are set as generics for
  fonts. However, this set of generics is completely intolerable --
  setting UKai as a generic is like setting Zapfino and/or Comic Sans as
  a system-wise generic, while UMing as a normal (just a bit thin) serif
  sounds a bit better. This yields terrible results on non-Chinese
  systems with non-Chinese lang-attributed websites, like Twitter, on
  Ubuntu 14.04 LTS after installing Chinese language support which
  includes the two arphic fonts mentioned in this report.

  This problem is similar to
  https://bugs.freedesktop.org/show_bug.cgi?id=20911, a long-standing
  system-global fontconfig non-latin fallback problem. See also bug
  #1560548 where these generic settings are considered as 'redundant'
  and proposed for deletion. I have mentioned a third-person report
  about such selection in #1560548 previously, but I have just
  reproduced this bug by myself by installing zh-cn support by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1595414/+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 1595414] Re: Awful generic selection for zh in Firefox

[Expired for fonts-arphic-ukai (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: fonts-arphic-ukai (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Awful generic selection for zh in Firefox

Status in fonts-arphic-ukai package in Ubuntu:
  Expired
Status in fonts-arphic-uming package in Ubuntu:
  Expired
Status in language-selector package in Ubuntu:
  Expired

Bug description:
  In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts-
  arphic-ukai/wily/revision/6, UMing and UKai are set as generics for
  fonts. However, this set of generics is completely intolerable --
  setting UKai as a generic is like setting Zapfino and/or Comic Sans as
  a system-wise generic, while UMing as a normal (just a bit thin) serif
  sounds a bit better. This yields terrible results on non-Chinese
  systems with non-Chinese lang-attributed websites, like Twitter, on
  Ubuntu 14.04 LTS after installing Chinese language support which
  includes the two arphic fonts mentioned in this report.

  This problem is similar to
  https://bugs.freedesktop.org/show_bug.cgi?id=20911, a long-standing
  system-global fontconfig non-latin fallback problem. See also bug
  #1560548 where these generic settings are considered as 'redundant'
  and proposed for deletion. I have mentioned a third-person report
  about such selection in #1560548 previously, but I have just
  reproduced this bug by myself by installing zh-cn support by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1595414/+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 1595414] Re: Awful generic selection for zh in Firefox

[Expired for language-selector (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: language-selector (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Awful generic selection for zh in Firefox

Status in fonts-arphic-ukai package in Ubuntu:
  Expired
Status in fonts-arphic-uming package in Ubuntu:
  Expired
Status in language-selector package in Ubuntu:
  Expired

Bug description:
  In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts-
  arphic-ukai/wily/revision/6, UMing and UKai are set as generics for
  fonts. However, this set of generics is completely intolerable --
  setting UKai as a generic is like setting Zapfino and/or Comic Sans as
  a system-wise generic, while UMing as a normal (just a bit thin) serif
  sounds a bit better. This yields terrible results on non-Chinese
  systems with non-Chinese lang-attributed websites, like Twitter, on
  Ubuntu 14.04 LTS after installing Chinese language support which
  includes the two arphic fonts mentioned in this report.

  This problem is similar to
  https://bugs.freedesktop.org/show_bug.cgi?id=20911, a long-standing
  system-global fontconfig non-latin fallback problem. See also bug
  #1560548 where these generic settings are considered as 'redundant'
  and proposed for deletion. I have mentioned a third-person report
  about such selection in #1560548 previously, but I have just
  reproduced this bug by myself by installing zh-cn support by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1595414/+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 1626820] [NEW] Shows duplicate upgrade notification - existing notification system exists

Public bug reported:

[Impact]
GNOME Software shows a notification when updates are available. This is 
unnecessary as we already have a notification system for updates in Ubuntu.

[Test Case]
1. Start GNOME Software
2. Update system:
$ sudo apt update

Expected result:
If updates are available, the normal Ubuntu notification is shown.

Observed result:
Both the normal notification and one from GNOME Software is shown.

[Regression Potential]
Low. We just stop showing the GNOME Software notification.

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Yakkety)
 Importance: Medium
 Status: Triaged

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: Medium
   Status: Triaged

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

-- 
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/1626820

Title:
  Shows duplicate upgrade notification - existing notification system
  exists

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  GNOME Software shows a notification when updates are available. This is 
unnecessary as we already have a notification system for updates in Ubuntu.

  [Test Case]
  1. Start GNOME Software
  2. Update system:
  $ sudo apt update

  Expected result:
  If updates are available, the normal Ubuntu notification is shown.

  Observed result:
  Both the normal notification and one from GNOME Software is shown.

  [Regression Potential]
  Low. We just stop showing the GNOME Software notification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626820/+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 1616943] Re: Can't auth against U1 in g-s

This is currently blocked on a security review for snapd-glib.

** Description changed:

- Use case:
+ [Impact]
+ Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.
  
- Don't be already authenticated against U1 in g-s.
- Search for nmap
- See the top result is a snap.
- Try and install it
- Get prompted to log in to U1
- Type in your credentials
- Get told "incorrect email or password" even though you are typing in the 
correct info
+ [Test Case]
+ 1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
+ 2. Start GNOME Software
+ 3. Search for a snap (e.g. "moon-buggy")
+ 4. Install Snap
+ 5. Enter Ubuntu One credentials when prompted
+ 
+ Expected result:
+ 
+ Observed result:
+ Dialog says "Incorrect email or password".
+ 
+ Expected result:
+ Authentication completes and the snap is installed.
+ 
+ [Regression Potential]
+ The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

** No longer affects: snapd (Ubuntu)

** No longer affects: snapd (Ubuntu Xenial)

** No longer affects: snapd (Ubuntu Yakkety)

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: High => Critical

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: High => Critical

-- 
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/1616943

Title:
  Can't auth against U1 in g-s

Status in gnome-software package in Ubuntu:
  In Progress
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Expected result:

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1568935] Re: notify-send shows "application has been installed" even when authenticate window is cancelled

Fixed in upstream commit:

commit 8d15294552b1b47888f16222db2cf1c17482faee
Author: Richard Hughes 
Date:   Mon Sep 12 16:50:58 2016 +0100

Only show the external installed notification on success

diff --git a/src/gs-page.c b/src/gs-page.c
index 852b7e3..8cce6e5 100644
--- a/src/gs-page.c
+++ b/src/gs-page.c
@@ -172,7 +172,7 @@ gs_page_app_installed_cb (GObject *source,
}
 
/* only show this if the window is not active */
-   if (gs_app_get_state (helper->app) != AS_APP_STATE_QUEUED_FOR_INSTALL &&
+   if (gs_app_is_installed (helper->app) &&
!gs_shell_is_active (priv->shell))
gs_app_notify_installed (helper->app);


** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: Medium
   Status: Triaged

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: Medium => Low

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Yakkety)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

-- 
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/1568935

Title:
  notify-send shows "application has been installed" even when
  authenticate window is cancelled

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  $  lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $  apt-cache policy gnome-software
  gnome-software:
Instalados: 3.20.1~git20160331.78d1aab-0ubuntu2
Candidato:  3.20.1~git20160331.78d1aab-0ubuntu2
Tabla de versión:
   *** 3.20.1~git20160331.78d1aab-0ubuntu2 500
  500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce:
  1. Open gnome-software. Search for any non-installed program.
  2. Click on "Install"
  3. On authenticate window, don't enter a password. Simply Cancel.

  Expected result:
  A message showing the authentication was refused, or the application couldn't 
be installed

  Current result:
  A notification "ProgramX has been installed"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 10:38:08 2016
  InstallationDate: Installed on 2016-03-27 (14 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/+source/gnome-software/+bug/1568935/+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 1596378] Re: Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many messages in log

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

-- 
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/1596378

Title:
  Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many
  messages in log

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Using the old snapd search API causes messages to be written to the systemd 
log.

  [Test Case]
  1. Start GNOME Software
  2. Search for some apps (e.g. "moon")

  Expected result:
  Results are shown, no significant logs written to systemd journal.

  Observed result:
  Many logs like this written:
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:474: jumping to "find" to 
better support legacy request "/v2/snaps?q=wikipe
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:393: DEBUG: use of 
obsolete "q" parameter: "/v2/snaps?q=wikipedia.org"
  Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: daemon.go:181: DEBUG: uid=1000;@ 
GET /v2/snaps?q=wikipedia 170.9766ms 200

  [Regression potential]
  Low. We just use the new request name in snapd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1596378/+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 1564076] Re: Can't launch snaps

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

-- 
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/1564076

Title:
  Can't launch snaps

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in snapd source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  No method of launching snaps from GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for a snap (e.g. "moon-buggy")
  3. Click on snap description
  4. Click install

  Expected result:
  Snap is installed and launch button is shown (as for .deb apps)

  Observed result:
  Snap is installed; no launch button shown.

  [Regression potential]
  Low. We now take advantage of new snapd API to make snaps launchable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1564076/+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 1573061] Re: gnome-software wants to upgrade held packages

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

-- 
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/1573061

Title:
  gnome-software wants to upgrade held packages

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows .deb packages marked as held as updatable.

  [Test Case]
  1. Hold a package that is available for update, e.g.
  $ sudo apt-mark hold gnome-calculator
  2. Open GNOME Software
  3. Click on Updates tab

  Expected result:
  Held package(s) are not shown

  Observed result:
  Held package(s) are shown

  [Regression potential]
  Low. We now just check the Apt flag for held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573061/+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 1574666] Re: Slow to start when many updates available

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

-- 
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/1574666

Title:
  Slow to start when many updates available

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software is slow to show anything when updates are available due to 
downloading Changelog information.

  [Test Case]
  1. Open GNOME Software when you have many updates to make and/or a very slow 
connection to changelogs.ubuntu.com

  Expected result:
  The home screen is quickly shown

  Observed result:
  The home screen takes many seconds to show

  [Regression potential]
  Low. We now just download these on demand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1574666/+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 1626803] Re: Search results show snaps not installed

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

-- 
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/1626803

Title:
  Search results show snaps not installed

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sometimes when searching for snaps the results may show as not installed when 
they are.

  [Test Case]
  1. Search in gnome-software (e.g. "moon")
  2. Install not the first search result (e.g. "moon-buggy" which is after 
"sl-moon127")
  3. Search again

  Exepected result:
  The installed snap is marked as such

  Observed result:
  The installed snap is marked as not installed.

  [Regression potential]
  Low. GNOME Software was stopping checking local snaps on the first result 
(since it is not installed). We now ignore not installed snaps and keep 
checking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626803/+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 1574666] Re: Slow to start when many updates available

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

-- 
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/1574666

Title:
  Slow to start when many updates available

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software is slow to show anything when updates are available due to 
downloading Changelog information.

  [Test Case]
  1. Open GNOME Software when you have many updates to make and/or a very slow 
connection to changelogs.ubuntu.com

  Expected result:
  The home screen is quickly shown

  Observed result:
  The home screen takes many seconds to show

  [Regression potential]
  Low. We now just download these on demand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1574666/+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 1564076] Re: Can't launch snaps

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

-- 
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/1564076

Title:
  Can't launch snaps

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in snapd source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  No method of launching snaps from GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for a snap (e.g. "moon-buggy")
  3. Click on snap description
  4. Click install

  Expected result:
  Snap is installed and launch button is shown (as for .deb apps)

  Observed result:
  Snap is installed; no launch button shown.

  [Regression potential]
  Low. We now take advantage of new snapd API to make snaps launchable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1564076/+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 1596378] Re: Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many messages in log

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

-- 
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/1596378

Title:
  Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many
  messages in log

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Using the old snapd search API causes messages to be written to the systemd 
log.

  [Test Case]
  1. Start GNOME Software
  2. Search for some apps (e.g. "moon")

  Expected result:
  Results are shown, no significant logs written to systemd journal.

  Observed result:
  Many logs like this written:
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:474: jumping to "find" to 
better support legacy request "/v2/snaps?q=wikipe
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:393: DEBUG: use of 
obsolete "q" parameter: "/v2/snaps?q=wikipedia.org"
  Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: daemon.go:181: DEBUG: uid=1000;@ 
GET /v2/snaps?q=wikipedia 170.9766ms 200

  [Regression potential]
  Low. We just use the new request name in snapd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1596378/+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 1573061] Re: gnome-software wants to upgrade held packages

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

-- 
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/1573061

Title:
  gnome-software wants to upgrade held packages

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows .deb packages marked as held as updatable.

  [Test Case]
  1. Hold a package that is available for update, e.g.
  $ sudo apt-mark hold gnome-calculator
  2. Open GNOME Software
  3. Click on Updates tab

  Expected result:
  Held package(s) are not shown

  Observed result:
  Held package(s) are shown

  [Regression potential]
  Low. We now just check the Apt flag for held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573061/+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 1626803] Re: Search results show snaps not installed

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

-- 
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/1626803

Title:
  Search results show snaps not installed

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sometimes when searching for snaps the results may show as not installed when 
they are.

  [Test Case]
  1. Search in gnome-software (e.g. "moon")
  2. Install not the first search result (e.g. "moon-buggy" which is after 
"sl-moon127")
  3. Search again

  Exepected result:
  The installed snap is marked as such

  Observed result:
  The installed snap is marked as not installed.

  [Regression potential]
  Low. GNOME Software was stopping checking local snaps on the first result 
(since it is not installed). We now ignore not installed snaps and keep 
checking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626803/+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 1564076] Re: Can't launch snaps

** Description changed:

- Clicking the "launch" button from GNOME Software has no effect for
- snaps. This is because snapd doesn't provide any mechanism to determine
- what binaries / .desktop files a snap contains.
+ [Impact]
+ No method of launching snaps from GNOME Software.
+ 
+ [Test Case]
+ 1. Open GNOME Software
+ 2. Search for a snap (e.g. "moon-buggy")
+ 3. Click on snap description
+ 4. Click install
+ 
+ Expected result:
+ Snap is installed and launch button is shown (as for .deb apps)
+ 
+ Observed result:
+ Snap is installed; no launch button shown.
+ 
+ [Regression potential]
+ Low. We now take advantage of new snapd API to make snaps launchable.

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

** Also affects: snapd (Ubuntu Yakkety)
   Importance: High
   Status: Fix Released

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: snapd (Ubuntu Xenial)
   Importance: Undecided => High

** No longer affects: snappy

-- 
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/1564076

Title:
  Can't launch snaps

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in snapd source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  No method of launching snaps from GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for a snap (e.g. "moon-buggy")
  3. Click on snap description
  4. Click install

  Expected result:
  Snap is installed and launch button is shown (as for .deb apps)

  Observed result:
  Snap is installed; no launch button shown.

  [Regression potential]
  Low. We now take advantage of new snapd API to make snaps launchable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1564076/+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 1574666] Re: Slow to start when many updates available

** Changed in: gnome-software (Ubuntu Yakkety)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

-- 
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/1574666

Title:
  Slow to start when many updates available

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software is slow to show anything when updates are available due to 
downloading Changelog information.

  [Test Case]
  1. Open GNOME Software when you have many updates to make and/or a very slow 
connection to changelogs.ubuntu.com

  Expected result:
  The home screen is quickly shown

  Observed result:
  The home screen takes many seconds to show

  [Regression potential]
  Low. We now just download these on demand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1574666/+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 1573061] Re: gnome-software wants to upgrade held packages

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: High => Medium

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Description changed:

- [Steps to Reproduce]
- 
- 1. $ sudo apt-mark hold 
- (substitute name of the package you want held
- 2. GNOME Software should not notify about held package(s) as an available 
update. Maybe it shouldn't list held packages in the Updates page either.
+ [Impact]
+ GNOME Software shows .deb packages marked as held as updatable.
  
- GNOME Software does not actually upgrade held packages but it's
- confusing that it looks like it's going to.
+ [Test Case]
+ 1. Hold a package that is available for update, e.g.
+ $ sudo apt-mark hold gnome-calculator
+ 2. Open GNOME Software
+ 3. Click on Updates tab
  
- Update Manager shows held packages in the update list but they are
- unchecked (and unable to be checked).
+ Expected result:
+ Held package(s) are not shown
  
- [Original Bug Description]
- ==
- I have a held package, and gnome-software keeps popping up the "upgrades are 
available" notification.  Looking at it what it wants to upgrade, there is only 
the held package.  I haven't clicked 'install' to see if it will actually do 
so, but held packages should not be upgraded by gnome-software.
+ Observed result:
+ Held package(s) are shown
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: gnome-software 3.20.1+git20160419.2.b8d2e40.ubuntu-xenial-0ubuntu1
- 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: GNOME
- Date: Thu Apr 21 07:10:17 2016
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2015-08-21 (243 days ago)
- InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: gnome-software
- UpgradeStatus: Upgraded to xenial on 2016-02-16 (64 days ago)
+ [Regression potential]
+ Low. We now just check the Apt flag for held packages.

-- 
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/1573061

Title:
  gnome-software wants to upgrade held packages

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows .deb packages marked as held as updatable.

  [Test Case]
  1. Hold a package that is available for update, e.g.
  $ sudo apt-mark hold gnome-calculator
  2. Open GNOME Software
  3. Click on Updates tab

  Expected result:
  Held package(s) are not shown

  Observed result:
  Held package(s) are shown

  [Regression potential]
  Low. We now just check the Apt flag for held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573061/+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 1596378] Re: Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many messages in log

** Description changed:

- I seared for "wikipedia" and "wikipedia.org" in the Software app and was
- surprised to see all of this in my systemd journal:
+ [Impact]
+ Using the old snapd search API causes messages to be written to the systemd 
log.
  
+ [Test Case]
+ 1. Start GNOME Software
+ 2. Search for some apps (e.g. "moon")
+ 
+ Expected result:
+ Results are shown, no significant logs written to systemd journal.
+ 
+ Observed result:
+ Many logs like this written:
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:474: jumping to "find" to 
better support legacy request "/v2/snaps?q=wikipe
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:393: DEBUG: use of 
obsolete "q" parameter: "/v2/snaps?q=wikipedia.org"
  Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: daemon.go:181: DEBUG: uid=1000;@ 
GET /v2/snaps?q=wikipedia 170.9766ms 200
- Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: api.go:474: jumping to "find" to 
better support legacy request "/v2/snaps?q=wikipe
- Jun 26 18:55:43 snapd[1085]: 2016/06/26 18:55:43.082461 api.go:474: jumping 
to "find" to better support legacy request "/v2/sn
- Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: api.go:393: DEBUG: use of 
obsolete "q" parameter: "/v2/snaps?q=wikipedia"
- Jun 26 18:55:39 /usr/lib/snapd/snapd[1085]: daemon.go:181: DEBUG: uid=1000;@ 
GET /v2/snaps?q=ipedia 3.484227633s 200
- Jun 26 18:55:42 snapd[1085]: 2016/06/26 18:55:41.632050 api.go:474: jumping 
to "find" to better support legacy request "/v2/sn
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.10
- Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
- ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
- Uname: Linux 4.4.0-25-generic x86_64
- ApportVersion: 2.20.2-0ubuntu1
- Architecture: amd64
- CurrentDesktop: GNOME
- Date: Sun Jun 26 19:19:51 2016
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2016-04-09 (77 days ago)
- InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
- SourcePackage: gnome-software
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Regression potential]
+ Low. We just use the new request name in snapd.

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Medium => Low

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: Medium => Low

-- 
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/1596378

Title:
  Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many
  messages in log

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Using the old snapd search API causes messages to be written to the systemd 
log.

  [Test Case]
  1. Start GNOME Software
  2. Search for some apps (e.g. "moon")

  Expected result:
  Results are shown, no significant logs written to systemd journal.

  Observed result:
  Many logs like this written:
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:474: jumping to "find" to 
better support legacy request "/v2/snaps?q=wikipe
  Jun 26 18:55:43 /usr/lib/snapd/snapd[1085]: api.go:393: DEBUG: use of 
obsolete "q" parameter: "/v2/snaps?q=wikipedia.org"
  Jun 26 18:55:41 /usr/lib/snapd/snapd[1085]: daemon.go:181: DEBUG: uid=1000;@ 
GET /v2/snaps?q=wikipedia 170.9766ms 200

  [Regression potential]
  Low. We just use the new request name in snapd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1596378/+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 1574666] Re: Updates tab slow to load due to downloading changelog information

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Description changed:

- Changelog information is downloaded from changelogs.ubuntu.com. These
- must all be loaded before the updates tab is populated.
+ [Impact]
+ GNOME Software is slow to show anything when updates are available due to 
downloading Changelog information.
  
- This is slow because:
- - Changelogs are downloaded for non-GUI packages (bug 1554166)
- - Changelogs are downloaded sequentially.
+ [Test Case]
+ 1. Open GNOME Software when you have many updates to make and/or a very slow 
connection to changelogs.ubuntu.com
  
- Downloading in parallel would speed this up significantly.
+ Expected result:
+ The home screen is quickly shown
+ 
+ Observed result:
+ The home screen takes many seconds to show
+ 
+ [Regression potential]
+ Low. We now just download these on demand.

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Summary changed:

- Updates tab slow to load due to downloading changelog information
+ Slow to start due to downloading changelog information

** Summary changed:

- Slow to start due to downloading changelog information
+ Slow to start when many updates available

-- 
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/1574666

Title:
  Slow to start when many updates available

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software is slow to show anything when updates are available due to 
downloading Changelog information.

  [Test Case]
  1. Open GNOME Software when you have many updates to make and/or a very slow 
connection to changelogs.ubuntu.com

  Expected result:
  The home screen is quickly shown

  Observed result:
  The home screen takes many seconds to show

  [Regression potential]
  Low. We now just download these on demand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1574666/+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 1626803] [NEW] Search results show snaps not installed

Public bug reported:

[Impact]
Sometimes when searching for snaps the results may show as not installed when 
they are.

[Test Case]
1. Search in gnome-software (e.g. "moon")
2. Install not the first search result (e.g. "moon-buggy" which is after 
"sl-moon127")
3. Search again

Exepected result:
The installed snap is marked as such

Observed result:
The installed snap is marked as not installed.

[Regression potential]
Low. GNOME Software was stopping checking local snaps on the first result 
(since it is not installed). We now ignore not installed snaps and keep 
checking.

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Yakkety)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
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/1626803

Title:
  Search results show snaps not installed

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sometimes when searching for snaps the results may show as not installed when 
they are.

  [Test Case]
  1. Search in gnome-software (e.g. "moon")
  2. Install not the first search result (e.g. "moon-buggy" which is after 
"sl-moon127")
  3. Search again

  Exepected result:
  The installed snap is marked as such

  Observed result:
  The installed snap is marked as not installed.

  [Regression potential]
  Low. GNOME Software was stopping checking local snaps on the first result 
(since it is not installed). We now ignore not installed snaps and keep 
checking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626803/+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 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2016-09-22 Thread Robert M. Muncrief

I can confirm the same problem exists with Xubuntu x64 16.04 as well.
However I can also confirm that this has been a problem with all Ubuntu
flavors for many years.

The difference now is that nothing can be done on the user side to fix
it. After all these years I'd become quite adept at editing display.xml
and monitor.xml files, xorg.conf files, etc. but now none of that works.
The only thing I haven't tried is changing Compiz settings, but that's
because Xubuntu doesn't run Compiz by default, and people running Compiz
have already reported that it can't be fixed their anyway.

I know the developers work hard and always have their plates full, but
if they could at least fix it enough that we could edit conf files again
it would be great.

** Also affects: xfwm4 (Ubuntu)
Importance: Undecided
Status: New

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

Title:
Cannot set right monitor as primary in dual monitor configuration

Status in unity-settings-daemon package in Ubuntu:
Confirmed
Status in xfwm4 package in Ubuntu:
New

Bug description:
Unity always considers the left monitor as the default/primary one when in a
dual-monitor configuration. By this I mean that:
- Desktop icons appear only on the left monitor
- An opened app (eg libreoffice writer) is opened on the left screen, even if
I launch it via the launcher on the right monitor

The current configuration can be seen at

http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

The .config/monitors.xml file is shown below. Notice that the HDMI
display (green in the photo) is set asyes.
Nevertheless, this seems to be ignored - the behaviour is the one
mentioned above (desktop icons on the left and writer opening on the
left) .

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no

GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1425000/+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 1551191] Re: gnome-software crashed with SIGSEGV in GS_IS_PLUGIN_LOADER()

** Changed in: gnome-software (Ubuntu)
   Status: Fix Committed => Confirmed

-- 
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/1551191

Title:
  gnome-software crashed with SIGSEGV in GS_IS_PLUGIN_LOADER()

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160225.dbf5b5d-0ubuntu3
  Uname: Linux 4.4.3-040403-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Feb 29 14:17:54 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-01-17 (42 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x44065f :  
cmp(%rdx),%rax
   PC (0x0044065f) ok
   source "(%rdx)" (0x2e66001f0fc3f889) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   gs_plugin_loader_get_updates_async ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in 
gs_plugin_loader_get_updates_async()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1551191/+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 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

2016-09-22 Thread Matthias Klumpp

Will never be fixed in appstream-dep11, but is already fixed in 
appstream-generator (or rather, has never been a bug there).
So, as soon as we switch to asgen, this bug should be gone.

** Changed in: appstream-dep11 (Ubuntu)
   Status: New => Confirmed

-- 
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/1626494

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in appstream-dep11 package in Ubuntu:
  Confirmed
Status in appstream-generator package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-dep11/+bug/1626494/+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 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

** Also affects: appstream-generator (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: appstream-generator (Ubuntu)
   Status: New => Fix Released

** Also affects: appstream-dep11 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: appstream-generator (Ubuntu)
   Importance: Undecided => Medium

** Changed in: appstream-dep11 (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1626494

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in appstream-dep11 package in Ubuntu:
  New
Status in appstream-generator package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-dep11/+bug/1626494/+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 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

gnome-software / appstream has picked this URL since it most closely
matches the desired size:

http://appstream.ubuntu.com/media/main/g/gn/gnome-
calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/624x351/scr-1.png

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1626494

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626494/+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 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

I'll pick gnome-calculator as an example since it shows stretched in
both Xenial and Yakkety.

The issue seems to be the appstream generator is making stretched
thumbnails and gnome-software / appstream-glib is choosing these over
the original images. For gnome-calculator (which shows the problem in
both Xenial and Yakkety) the dep11 data [1] gives:

>From 
source-image:
  height: 285
  url: 
g/gn/gnome-calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/source/scr-1.png
  width: 312
thumbnails:
  - height: 702
url: 
g/gn/gnome-calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/1248x702/scr-1.png
width: 1248
  - height: 423
url: 
g/gn/gnome-calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/752x423/scr-1.png
width: 752
  - height: 351
url: 
g/gn/gnome-calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/624x351/scr-1.png
width: 624
  - height: 63
url: 
g/gn/gnome-calculator.desktop/849e24a42d3d86f364e068fc3be7f680/screenshots/112x63/scr-1.png
width: 112

The large thumbnails are distorted and should not be used/generated.

[1] /var/lib/apt/lists/archive.ubuntu
.com_ubuntu_dists_yakkety_main_dep11_Components-amd64.yml.gz

-- 
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/1626494

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626494/+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 1568996] Re: Duplex printing does not work properly for HP printers

2016-09-22 Thread Till Kamppeter

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

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

Title:
  Duplex printing does not work properly for HP printers

Status in hplip package in Ubuntu:
  Fix Committed

Bug description:
  I am reporting this as a new bug because I want to avoid adding
  further to the mish mash of half fixed bugs that is duplex printing on
  hp printers via cups.

  I will warn readers that this will sound like a bit of a rant. But
  these issues have been outstanding for years

  1. Take the hpcups.drv driver information from the upstream part of
  the current source package and run it throught the cups ppd compiler
  in test mode, anbd filter the output for failures.

  roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL
  roger@dragon:~/ppd-testing$

  Result a nice clean file.

  2. Take this file and run it through the script debian/local/make-
  duplex-page-sizes-default.sh that is run when this file is installed
  on a system. Then repeat the above test.

  roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL

  --- Other FAILS removed

  hp-photosmart_6510_series.ppd: FAIL
    **FAIL**  Multiple occurrences of option PageRegion choice name Card4x6.
    **FAIL**  Multiple occurrences of option PageRegion choice name Hagaki.
    **FAIL**  Multiple occurrences of option PageRegion choice name Card5x8.
    **FAIL**  Multiple occurrences of option PageRegion choice name Oufuku.
    **FAIL**  Multiple occurrences of option PageRegion choice name 
Executive.
    **FAIL**  Multiple occurrences of option PageRegion choice name A4.
    **FAIL**  Multiple occurrences of option PageSize choice name Card4x6.
    **FAIL**  Multiple occurrences of option PageSize choice name Hagaki.
    **FAIL**  Multiple occurrences of option PageSize choice name Card5x8.
    **FAIL**  Multiple occurrences of option PageSize choice name Oufuku.
    **FAIL**  Multiple occurrences of option PageSize choice name Executive.
    **FAIL**  Multiple occurrences of option PageSize choice name A4.

  --Other FAILS removed

  I have removed the many other printer types that fail for clarity. It
  is a feature of the cups ppdc compiler that if you do not specify the
  -t option it will blithely go on and produce the compiled ppds errors
  and all. I personally think that this is a bug and the compiler should
  refuse to produce erroneous ppds, but putting that to one side. Taking
  A4 as an exmaple the hp6510 ppd file now has two definitions for
  PageSize A4.

  *PageSize A4/A4 210x297mm: "<>setpagedevice"
  and
  *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice"

  Same name but different page dimensions. Only the first one will ever
  be seen by the cups system.

  3. This above often does not matter when printing from the command
  line. Because PageSize options are not often specified. However,
  taking as an example a gnome desktop application such as  Evince
  printing a pdf using the gtk+ print options with duplex printing
  selected. In this case a PageSize option will be passed to Cups and it
  will look like this.

  D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper
  number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal
  ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed-
  e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date-
  time-at-creation= date-time-at-processing= time-at-creation=1460393994
  time-at-processing=1460393994"

  So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so
  what is passed down for matching is "A4" which matches the first
  occurrence of A4. Depending on what other defaults are set in the pdd
  it might print something, but it will most likely be clipped. In the
  case of the 6510 it results in this.

  D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error:
  rangecheck in setpagedevice

  Of course the above line only appears in the error_log if you have
  debugging turned on. So the job just appears to stuck in the print
  queue for no reason at all. This is probably another bug.

  The work around. This has been mentioned many times in various bug
  reports. You need page sizes, page regions, imageable areas, and paper
  dimensions  with names ending in .Duplex in your ppd. Rename the
  duplicate which has the biggest bottom margin, hopefully this is the
  one with AutoDuplex in the descriptive text. It is probably best to
  make these entries default as well. You might make the corresponding
  changes in the drv file if you wish. That will save you having to
  reapply them every time the ppd file is regenerated.

  I realise that I have broken just about every rule in the "bug laws".
  I offer no excuse:-)

  Comments please.

  Roger

  ProblemType: Bug

[Desktop-packages] [Bug 418242] Re: Incorrect call to output plugins (with persistent error message) on copy

2016-09-22 Thread Hachmann

Sonya, I've just taken a look (so you can delete the file if you need
to).

The reason why it still doesn't work is that the number nodes extension
only works on a single path. Your image, however, consists of a group of
331 objects and paths.

If you *really* want to number all nodes in the treasure chest, you need
to ungroup everything first, then then select everything, convert
everything to path by doing 'Path -> Object to path', then combine
everything into a single path (Path -> Combine).

The numbering you will get then will, however, not be the most logical
one for drawing from node to node (if that's what you want as an end
result). The path will consist of 3157 nodes, which is a bit complex,
and choosing a font size for this may become difficult...

The treasure chest image is not an ideal object for draw-by-numbers, I
think - better to choose something simpler. You can draw it yourself if
you use the Bezier tool and the original chest as a 'template' to copy
(manually, by drawing) from.

Kind Regards,
 Maren

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

Title:
  Incorrect call to output plugins (with persistent error message) on
  copy

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape package in Arch Linux:
  New
Status in inkscape package in Debian:
  Confirmed
Status in Gentoo Linux:
  Unknown

Bug description:
  UPDATE: After further investigation it turned out to be a problem related to 
the copy operation, in combination with a totally unrelated running Java 
program (FreeRapid).
  Reading some followups and other bug reports, it seems to be caused by the 
new clipboard management system (introduced as a fix for the bug #170185), as 
reported in bug #421597

  So far these applications are known to randomly trigger an input/output 
extension (on linux):
  - FreeRapid Downloader
  - jDownloader
  - xfce4-clipman-plugin 1.1.3
  - Netbeans
  - xfce4-settings-helper (Xfce 4.8)
  - Team Viewer (teamviewerd 10.0.36)

  -

  The original report was this:
  I'm getting this error when I try to edit a text object created previously 
with a font that's not available in this system.
  It looks like Inkscape has problems to resolve the font substitution and 
displays the error message in a popup window that keeps appearing again and 
again, leaving no other remedy than closing inkscape and reopening it.

  The error message is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/418242/+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 1621157] Re: No window handles on non-Unity desktops

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gedit (Ubuntu)
   Status: New => Confirmed

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

Title:
  No window handles on non-Unity desktops

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  When using gedit in Ubuntu 16.04 on other desktop environments (eg.
  gnome-flashback with Metacity), sometimes the window handles are gone.

  For example, if gedit window is maximized, there is no header and no
  icons to undo maximisation anymore.

  All instances of gedit need to be closed and reopened to get the
  window header again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1621157/+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 1623126] Re: Application icons don't follow the theme

2016-09-22 Thread Fabio

No, the same behaviour happens on Yakkety.. I tried it with the Paper
icon theme

-- 
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/1623126

Title:
  Application icons don't follow the theme

Status in gnome-software package in Ubuntu:
  Won't Fix

Bug description:
  Icons of applications within the store are fixed and don't follow the
  theme chosen by the user. This makes the icons ugly and out of place
  when using any icon theme different from the default.

  Expected:
  Icons of common applications to follow the custom icon theme chosen by the 
user.

  What happens:
  Icons are displayed according to the default theme (ubuntu-mono-*).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1623126/+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 1613042] Re: No shortcut texts are displayed next to menu items

2016-09-22 Thread Richard

The problem is still there with firefox 49.0+build4-0ubuntu0.16.04.1

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

Title:
  No shortcut texts are displayed next to menu items

Status in firefox package in Ubuntu:
  New

Bug description:
  No shortcuts are displayed next to menu items like 'New Private Window' or 
'Show all bookmarks' in Firefox 48, whether menus are shown in the global menu 
bar or in the window's title bar.
  I am on Ubuntu 16.04.1 The shortcuts still work.

  I checked Safe Mode, and the same problem occurs in a 16.04.1 virtual
  machine.

  Package version: firefox 48.0+build2-0ubuntu0.16.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 48.0+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mystic13017 F pulseaudio
  BuildID: 20160728203720
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Aug 14 12:28:35 2016
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-26 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 10.0.1.1 dev wlp2s0  proto static  metric 600 
   10.0.1.0/24 dev wlp2s0  proto kernel  scope link  src 10.0.1.201  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
  MostRecentCrashID: bp-b6b869b2-9019-45d2-bf4e-dcbfa2151221
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=Safe Mode/Safe Mode (Out of date)
   Profile1 (Default) - LastVersion=48.0/20160728203720 (In use)
  RelatedPackageVersions:
   google-talkplugin  5.41.3.0-1
   browser-plugin-freshplayer-pepperflash 0.3.5-1~webupd8~xenial~3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-b6b869b2-9019-45d2-bf4e-dcbfa2151221
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Pangolin Performance
  dmi.board.vendor: System76, Inc.
  dmi.board.version: panp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: Pangolin Performance
  dmi.product.version: panp9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1613042/+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 1626757] [NEW] package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2016-09-22 Thread marcos

Public bug reported:

atualization failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsm6:i386 2:1.2.2-1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep 22 18:37:39 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2016-07-08 (76 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libsm
Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libsm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in libsm package in Ubuntu:
  New

Bug description:
  atualization failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsm6:i386 2:1.2.2-1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 18:37:39 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-07-08 (76 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libsm
  Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsm/+bug/1626757/+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 299918] amazing adventure

2016-09-22 Thread payo

Hey friend,

We've had an amazing summer adventure this year and I  wanted to share
some photos with you, here, take a look


Sincerely yours, parfaitg

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

Title:
  Cannot print duplex in intrepid with Ricoh Aficio 2060, Ricoh Aficio
  MPC3000 or Brother HL-4050cdn using the openprinting drivers

Status in foomatic-filters package in Ubuntu:
  Fix Released
Status in foomatic-filters source package in Intrepid:
  Fix Released

Bug description:
  Binary package hint: openprinting-ppds-extra

  We recently upgraded to Intrepid from hardy. All the printers could duplex no 
problem in hardy, but now they cannot.
  I have tried a fresh install with no luck. I have also tried the versions in 
the openprinting repos (deb 
http://www.openprinting.org/download/printdriver/debian/ lsb3.2 main) these did 
not resolve the problem. Bug 21 appears to be similar but this is marked as 
fixed.

  2.6.27-8-generic #1 SMP Thu Nov 6 17:38:14 UTC 2008 x86_64 GNU/Linux
  openprinting-ppds-extra:
Installed: 20080918-0ubuntu4
Candidate: 20080918-0ubuntu4
Version table:
   *** 20080918-0ubuntu4 0
  500 http://archive.ubuntu.com intrepid/main Packages
  100 /var/lib/dpkg/status

  Please advise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-filters/+bug/299918/+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 224421] Re: ornaments

2016-09-22 Thread payo

*** This bug is a duplicate of bug 238755 ***
https://bugs.launchpad.net/bugs/238755

Hello,


What do you  think about  that ornaments? Please take a look  and  tell  me 
whether you like  them, here is the link 

Sent from my iPhone, parfaitg

-- 
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/224421

Title:
  package update-manager 1:0.87.24 failed to install/upgrade:
  ErrorMessage: SystemError in cache.commit(): E:Sub-process
  /usr/bin/dpkg returned an error code (1)

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: update-manager

  Similarly to an apparently "invalid" bug report ( #176629 ), my installation 
too was aborted.
  Please also see my bug report #224415 (occured during the same upgrade 
process and possibly related).

  ProblemType: Package
  Architecture: i386
  Date: Tue Apr 29 17:04:37 2008
  DistroRelease: Ubuntu 8.04
  ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process 
/usr/bin/dpkg returned an error code (1)

  Package: update-manager 1:0.87.24
  PackageArchitecture: all
  SourcePackage: update-manager
  Title: package update-manager 1:0.87.24 failed to install/upgrade: 
ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg 
returned an error code (1)
  Uname: Linux 2.6.22-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/224421/+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 235135] great news or you

2016-09-22 Thread payo

Greetings!

I've  got good news for  you,  you'll like  it for sure! Read it here
please 

Yours truly, parfaitg

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

Title:
  [MASTER] Please backport flashplugin-nonfree version 10 beta and
  asound-plugins from Intrepid so we can drop libflashsupport and the
  crashes it causes

Status in Gutsy Backports:
  Invalid
Status in Hardy Backports:
  Fix Released
Status in flashplugin-nonfree package in Ubuntu:
  Invalid
Status in flashplugin-nonfree source package in Gutsy:
  Invalid
Status in flashplugin-nonfree source package in Hardy:
  Fix Released

Bug description:
  Binary package hint: flashplugin-nonfree

  Please backpor tlatest flash version 10 as it fixes some problems that
  were seen in version 9 like the libflashsupport sound/crash issues.
  Now it depends on libflashsupport  this has landed in Intrepid nad
  will backport to Hardy Gutsy maybe feistty and dapper but but for now
  just Hardy and Gutsy than we can talk about feisty and dapper.

  Please mark all bugs on updating flash to version 10 to this bug
  please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gutsy-backports/+bug/235135/+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 1557173] Re: pulseaudio crashed with SIGABRT in pa_cvolume_set()

2016-09-22 Thread chila

I have the same problem when trying to add my bluetooth headset. It ends
up adding it but can't connect to it afterwards. It disconnects. I have
Ubuntu 16.04.

-- 
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/1557173

Title:
  pulseaudio crashed with SIGABRT in pa_cvolume_set()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Same problems have been in avahi and systemd content recently.
  Is 16.04 getting released in April and are these problematic and certainly 
buggy root daemons being removed in future releases of Ubuntu?

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a  4280 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 14 23:21:33 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-11-06 (129 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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.
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_cvolume_set () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-bluez5-device.so
   pa_hook_fire () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libbluez5-util.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_cvolume_set()
  UpgradeStatus: Upgraded to xenial on 2016-01-11 (63 days ago)
  UserGroups: sudo
  dmi.bios.date: 02/27/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETD0WW (2.30 )
  dmi.board.name: 76641FG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETD0WW(2.30):bd02/27/2012:svnLENOVO:pn76641FG:pvrThinkPadT61:rvnLENOVO:rn76641FG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 76641FG
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1557173/+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 1626732] Re: gnome software does not warn on removing packages during install

2016-09-22 Thread liamdawe

** Description changed:

- I accidentally installed a 32bit dev of the "google music desktop
+ I accidentally installed a 32bit .deb of the "google music desktop
  player", this seemed to remove libappindicator and fuck a few things up
  (my indicators vanished, google chrome wouldn't load etc).
  
  This software installer is dangerous, it doesn't warn people on
  dependencies other apps need being removed or replaced.

-- 
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/1626732

Title:
  gnome software does not warn on removing packages during install

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I accidentally installed a 32bit .deb of the "google music desktop
  player", this seemed to remove libappindicator and fuck a few things
  up (my indicators vanished, google chrome wouldn't load etc).

  This software installer is dangerous, it doesn't warn people on
  dependencies other apps need being removed or replaced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626732/+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 1626732] [NEW] gnome software does not warn on removing packages during install

2016-09-22 Thread liamdawe

Public bug reported:

I accidentally installed a 32bit dev of the "google music desktop
player", this seemed to remove libappindicator and fuck a few things up
(my indicators vanished, google chrome wouldn't load etc).

This software installer is dangerous, it doesn't warn people on
dependencies other apps need being removed or replaced.

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1626732

Title:
  gnome software does not warn on removing packages during install

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I accidentally installed a 32bit dev of the "google music desktop
  player", this seemed to remove libappindicator and fuck a few things
  up (my indicators vanished, google chrome wouldn't load etc).

  This software installer is dangerous, it doesn't warn people on
  dependencies other apps need being removed or replaced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626732/+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 1626729] [NEW] Evolution keeps using wrong password instead of asking it again

2016-09-22 Thread giacof

Public bug reported:

I sent an email via SMTP and mistyped the password, so the server
rejected the message. Then I tried to send again the same message.

Expected behavior: a new dialog should have prompted for the correct
password.

What happened instead: Evolution did NOT ask the password again, but
tried to send the message reusing the wrong one! The following popup was
then displayed:

The reported error was "AUTH command failed: ...authentication rejected"

Below the message are three buttons, the last of which is "Retry", but
it keeps using the wrong password

I even tried to exit Evolution and restart it, but it was still
remembering the wrong password instead of asking it!

Package Version: 3.18.5.2
OS: Ubuntu Gnome 16.04.1 LTS

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Evolution keeps using wrong password instead of asking it again

Status in evolution package in Ubuntu:
  New

Bug description:
  I sent an email via SMTP and mistyped the password, so the server
  rejected the message. Then I tried to send again the same message.

  Expected behavior: a new dialog should have prompted for the correct
  password.

  What happened instead: Evolution did NOT ask the password again, but
  tried to send the message reusing the wrong one! The following popup
  was then displayed:

  The reported error was "AUTH command failed: ...authentication
  rejected"

  Below the message are three buttons, the last of which is "Retry", but
  it keeps using the wrong password

  I even tried to exit Evolution and restart it, but it was still
  remembering the wrong password instead of asking it!

  Package Version: 3.18.5.2
  OS: Ubuntu Gnome 16.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1626729/+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 1626724] Re: Extracting iso changes target directory's permissions

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: file-roller (Ubuntu)
   Status: New => Confirmed

-- 
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/1626724

Title:
  Extracting iso changes target directory's permissions

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  I have an ISO archive and opened it with file-roller. Then I clicked
  the big [Extract] button, selected my Desktop as target directory
  (options "Extract: All files" and "Actions: Keep directory structure"
  checked) and confirmed. It extracted the files successfully, but also
  changed the permissions of the target directory itself (to r-xr-xr-x).

  This is not expected and not intended. Actually I could no longer
  create or delete files in my Desktop directory after that, until I
  fixed the permissions again. I confirmed the behaviour with a
  different location as well.

  Extracting anything into a location should never modify permissions of
  the target location itself!

  
  


  If you're interested, here's what I did (extracting to
  ~/Desktop/testdir ; the "Extract" dialog window can be seen at
  https://i.stack.imgur.com/rlUvS.png):

  $ ls -l Desktop/
  total 4
  drwxrwxr-x  2 bytecommander bytecommander 4096 Sep 22 21:58 testdir/

  $ file-roller test.iso

  $ ls -l Desktop/
  total 4
  dr-xr-xr-x  4 bytecommander bytecommander 4096 Sep 22 16:20 testdir/

  
  


  System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt policy file-roller
  file-roller:
Installed: 3.16.5-0ubuntu1.2
Candidate: 3.16.5-0ubuntu1.2
Version table:
   *** 3.16.5-0ubuntu1.2 500
  500 http://ftp.uni-stuttgart.de/ubuntu xenial-updates/main amd64 
Packages
  500 http://ftp.uni-stuttgart.de/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.16.4-1ubuntu3 500
  500 http://ftp.uni-stuttgart.de/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1626724/+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 1626724] [NEW] Extracting iso changes target directory's permissions

2016-09-22 Thread Byte Commander

Public bug reported:

I have an ISO archive and opened it with file-roller. Then I clicked the
big [Extract] button, selected my Desktop as target directory (options
"Extract: All files" and "Actions: Keep directory structure" checked)
and confirmed. It extracted the files successfully, but also changed the
permissions of the target directory itself (to r-xr-xr-x).

This is not expected and not intended. Actually I could no longer create
or delete files in my Desktop directory after that, until I fixed the
permissions again. I confirmed the behaviour with a different location
as well.

Extracting anything into a location should never modify permissions of
the target location itself!




If you're interested, here's what I did (extracting to ~/Desktop/testdir
; the "Extract" dialog window can be seen at
https://i.stack.imgur.com/rlUvS.png):

$ ls -l Desktop/
total 4
drwxrwxr-x  2 bytecommander bytecommander 4096 Sep 22 21:58 testdir/

$ file-roller test.iso

$ ls -l Desktop/
total 4
dr-xr-xr-x  4 bytecommander bytecommander 4096 Sep 22 16:20 testdir/




System info:

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

$ apt policy file-roller
file-roller:
  Installed: 3.16.5-0ubuntu1.2
  Candidate: 3.16.5-0ubuntu1.2
  Version table:
 *** 3.16.5-0ubuntu1.2 500
500 http://ftp.uni-stuttgart.de/ubuntu xenial-updates/main amd64 
Packages
500 http://ftp.uni-stuttgart.de/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.16.4-1ubuntu3 500
500 http://ftp.uni-stuttgart.de/ubuntu xenial/main amd64 Packages

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
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/1626724

Title:
  Extracting iso changes target directory's permissions

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  I have an ISO archive and opened it with file-roller. Then I clicked
  the big [Extract] button, selected my Desktop as target directory
  (options "Extract: All files" and "Actions: Keep directory structure"
  checked) and confirmed. It extracted the files successfully, but also
  changed the permissions of the target directory itself (to r-xr-xr-x).

  This is not expected and not intended. Actually I could no longer
  create or delete files in my Desktop directory after that, until I
  fixed the permissions again. I confirmed the behaviour with a
  different location as well.

  Extracting anything into a location should never modify permissions of
  the target location itself!

  
  


  If you're interested, here's what I did (extracting to
  ~/Desktop/testdir ; the "Extract" dialog window can be seen at
  https://i.stack.imgur.com/rlUvS.png):

  $ ls -l Desktop/
  total 4
  drwxrwxr-x  2 bytecommander bytecommander 4096 Sep 22 21:58 testdir/

  $ file-roller test.iso

  $ ls -l Desktop/
  total 4
  dr-xr-xr-x  4 bytecommander bytecommander 4096 Sep 22 16:20 testdir/

  
  


  System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt policy file-roller
  file-roller:
Installed: 3.16.5-0ubuntu1.2
Candidate: 3.16.5-0ubuntu1.2
Version table:
   *** 3.16.5-0ubuntu1.2 500
  500 http://ftp.uni-stuttgart.de/ubuntu xenial-updates/main amd64 
Packages
  500 http://ftp.uni-stuttgart.de/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.16.4-1ubuntu3 500
  500 http://ftp.uni-stuttgart.de/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1626724/+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 1385271] Re: Error authenticating some packages

2016-09-22 Thread Claes Wallin

Still getting this when going 14.04->16.04. It complained about my
kernel image package. I upgraded to the latest kernel, removed all older
kernel packages, now it complained about my fresh installed kernel
package.

What does this even mean? What is it authenticating?

Trying the disabling config from the comments above.

-- 
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/1385271

Title:
  Error authenticating some packages

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  during realese upgrade 14.04 -> 14.10 have following issue

  

  $ do-release-upgrade

  [...]

  Checking package manager
  Reading package lists... Done
  Building dependency tree  
  Reading state information... Done
  Building data structures... Done 

  Calculating the changes

  Calculating the changes

  Error authenticating some packages

  It was not possible to authenticate some packages. This may be a 
  transient network problem. You may want to try again later. See below 
  for a list of unauthenticated packages. 

  libgbm1

  
  Restoring original system state

  Aborting
  Reading package lists... Done
  Building dependency tree  
  Reading state information... Done
  Building data structures... Done

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgdm1 3.10.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 16:08:35 2014
  InstallationDate: Installed on 2012-03-08 (960 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gdm
  UpgradeStatus: Upgraded to trusty on 2014-10-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1385271/+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 204202] Re: gnome-terminal ignores current keyboard layout for ctrl+key shortcuts

2016-09-22 Thread Bug Watch Updater

** Changed in: gnome-terminal
   Status: New => Confirmed

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

Title:
  gnome-terminal ignores current keyboard layout for ctrl+key shortcuts

Status in GNOME Terminal:
  Confirmed
Status in Gnome Virtual Terminal Emulator:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in gnome-terminal source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: gnome-terminal

  In Ubuntu 7.10 (Gutsy Gibbon), Gnome Terminal (2.18.2-0ubuntu1)
  doesn't respect the Dvorak keyboard layout correctly. When pressing
  Ctrl+Z to suspend a process the text size is instead decreased. Ctrl+Z
  on Dvorak is on top of the '-' key on Qwerty so I assume that it is
  somehow interpreted on the key code level.

  Operation: Pressing Ctrl+Z in the terminal window
  Expected behavior: The currently running program is suspended
  Current behaviour: Text size is decreased

  Note that the text size can be decreased by Pressing Ctrl+- on the Dvorak 
layout (the correct behavior for this command).
  Note also that the same is valid for Ctrl+'+', i.e. pressing the physical key 
of Qwerty plus is interpreted as plus but it should use the Dvorak layout 
equivalent key.

  == Regression details ==
  Discovered in version: 2.29.6-0ubuntu1
  Last known good version:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/204202/+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 1626714] [NEW] package ubuntu-drivers-common 1:0.4.17.2 failed to install/upgrade

2016-09-22 Thread torzsmokus

Public bug reported:

telepítve post-installation parancsfájl alfolyamat 1 hibakóddal kilépett

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-drivers-common 1:0.4.17.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep 22 21:31:34 2016
ErrorMessage: telepítve post-installation parancsfájl alfolyamat 1 hibakóddal 
kilépett
InstallationDate: Installed on 2016-08-08 (45 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ubuntu-drivers-common
Title: package ubuntu-drivers-common 1:0.4.17.2 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 1 hibakóddal kilépett
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
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/1626714

Title:
  package ubuntu-drivers-common 1:0.4.17.2 failed to install/upgrade

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  telepítve post-installation parancsfájl alfolyamat 1 hibakóddal
  kilépett

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 21:31:34 2016
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 1 hibakóddal 
kilépett
  InstallationDate: Installed on 2016-08-08 (45 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ubuntu-drivers-common
  Title: package ubuntu-drivers-common 1:0.4.17.2 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 1 hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1626714/+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 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

On the u-s-d side there is some potential optimization: Ideally the
brightness would always be set through xrandr XBACKLIGHT, which works
unprivileged, and only fall back to the helper if that is not available
and the brightness needs to be set via sysfs properties. However, even
then there is no reason why --get-brightness would need particular
privileges: these sysfs attributes are world-readable, and only --set-
brightness (writing the attribute) needs root. This would already cut
away half of the overhead.

** Changed in: policykit-1 (Ubuntu)
Milestone: None => ubuntu-16.10

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in policykit-1 package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 fork  1 parent  /sbin/init splash
  16:35:36 fork   2654 child   /sbin/init splash
  Time Event  PID  Info  Duration Process
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2656 child

[Desktop-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

Changing tasks as this is somewhere between unity-settings-daemon and
polkit.

** Package changed: linux (Ubuntu) => unity-settings-daemon (Ubuntu)

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Incomplete => Triaged

** Package changed: systemd (Ubuntu) => policykit-1 (Ubuntu)

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in policykit-1 package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 fork  1 parent  /sbin/init splash
  16:35:36 fork   2654 child   /sbin/init splash
  Time Event  PID  Info  Duration Process
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2656 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2657 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36

[Desktop-packages] [Bug 1626651] [NEW] brightness keys are handled slower in Yakkety than Xenial

You have been subscribed to a public bug:

I've noticed on Lenovo X220 and X230 laptops that pressing brightness
keys on Yakkety seems less responsive and slower than Xenial.  I ran
forkstat on Xenial and just observed udev being forked off:

Xenial:
$ sudo forkstat
Time Event  PID  Info  Duration Process
17:37:35 fork273 parent  /lib/systemd/systemd-udevd
17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

Whereas on Yakkety, there is far more activity:
Time Event  PID  Info  Duration Process
16:35:34 fork   2626 parent  update-notifier
16:35:34 fork   2645 child   update-notifier
16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
16:35:34 fork   2626 parent  update-notifier
16:35:34 fork   2646 child   update-notifier
16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 fork  1 parent  /sbin/init splash
16:35:36 fork   2654 child   /sbin/init splash
Time Event  PID  Info  Duration Process
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2656 child   /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2657 child   /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2658 child   /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2659 child   /lib/systemd/systemd-udevd
16:35:36 exit   2659  00.005 /lib/systemd/systemd-udevd
16:35:36 exit   2658  00.006 /lib/systemd/systemd-udevd
16:35:36 exit   2657  00.007 /lib/systemd/systemd-udevd
16:35:36 exit   2656  00.008 /lib/systemd/systemd-udevd
16:35:36 exit   2655  00.008 /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2660 child   /lib/systemd/systemd-udevd
16:35:36 exit   2660  00.001 /lib/systemd/systemd-udevd
16:35:36 fork233 parent  /lib/systemd/systemd-udevd
16:35:36 fork   2661 child

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-22 Thread Anthony

Found a workaround that worked for me. I've seen a lot of this issue
just googling around and a few different threads lead to "hda-jack-
retask" (evidently a part of alsa-tools-gui now) as a fix. Install alsa-
tools-gui, run "hdajackretask" and switch the "front green jack" to "not
connected"

It's not a perfect fix but my system is an HTPC and that jack doesn't
get used anyway. Hope this helps.

--
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/1585084

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

[Desktop-packages] [Bug 1606238] Re: gnome-software won't open

2016-09-22 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1606238

** Tags added: iso-testing

-- 
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/1606238

Title:
  gnome-software won't open

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I upgrade the system from Ubuntu 14.04 to 16.04 some time ago.
  At beginning, gnome-software refused to open and I had to remove old ubuntu 
software and "--reinstall" the gnome-software.
  Everything was fine, except for many sorts of packages it can't install so I 
installed synaptic.

  Some days ago, gnome software went on a strike but claimed nothing !
  I can open a terminal and call gnome-software : nothing 
  The launcher turns around in the dock.

  Any Idea ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 15:28:05 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606238/+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 1578673] Re: [Touch] Volume level is not maintained per output device

2016-09-22 Thread John McAleely

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: High => Wishlist

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
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/1578673

Title:
  [Touch] Volume level is not maintained per output device

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I'm not mistaken this issue was not present before OTA-10. I
  usually like to keep the volume at around 80% on speaker and around
  50% on earphones. Previously the device used to remember these choices
  and adjust them accordingly. But now it only remembers the previously
  set volume level and hence I have to adjust manually all the time
  while switching output devices.

  Device: bq E5, OTA-10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578673/+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 1591935] Re: [CTA] audio record works for call audio

2016-09-22 Thread John McAleely

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
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/1591935

Title:
  [CTA] audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591935/+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

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

---
ubuntu-drivers-common (1:0.4.17.2) xenial-proposed; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

-- 
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:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

---
ubuntu-drivers-common (1:0.4.17.2) xenial-proposed; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

-- 
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 Released

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 1586933] Update Released

The verification of the Stable Release Update for ubuntu-drivers-common
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 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 Released

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] Update Released

The verification of the Stable Release Update for ubuntu-drivers-common
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 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 Released

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] Update Released

The verification of the Stable Release Update for ubuntu-drivers-common
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 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:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

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 1586933] Re: gpu-manager's drm output detection affects boot time

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

---
ubuntu-drivers-common (1:0.4.17.2) xenial-proposed; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

-- 
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 Released

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 1626245] Re: [MIR] fonts-android

2016-09-22 Thread Joshua Powers

Here is my back-of-the-envelope calculation:

If the target size is 703MiB, today we are 812MiB, over by 109MiB.

If the GCC6 packages do indeed shrink down to GCC5 sizes (~90 -> ~30)
that will save 60MiB and removing fonts-noto-cjk and adding fonts-
android removes another (76 - 2) 74MiB. The new total would be 678MiB.

Adding another 20MiB, would take us right up to 698MiB with 5MiB to
spare.

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Fix Committed
Status in ghostscript package in Ubuntu:
  In Progress

Bug description:
  Please include the fonts-android package in Ubuntu's component main.

  fonts-android includes the fonts-droid-fallback binary, and as a
  result of the discussion at bug 1625734, the server team wants that
  libgs9-common, which currently recommends fonts-noto-cjk, is changed
  to instead recommend fonts-droid-fallback.

  fonts-android is a Debian package and included in Debian's component
  main. It was included in Ubuntu's component main between trusty and
  wily.

  Bugs:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android

  https://bugs.launchpad.net/ubuntu/+source/fonts-android

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1626245/+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 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

This bug was fixed in the package samba - 2:4.3.9+dfsg-0ubuntu0.16.04.3

---
samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) xenial; urgency=medium

  * debian/patches/git_smbclient_cpu.patch:
- backport upstream patch to fix smbclient users hanging/eating cpu on
  trying to contact a machine which is not there (lp: #1572260)

 -- Sebastien Bacher   Thu, 11 Aug 2016 10:39:10
+0200

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

-- 
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:
  Invalid
Status in samba source package in Xenial:
  Fix Released

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 1572260] Update Released

The verification of the Stable Release Update for samba 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/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:
  Invalid
Status in samba source package in Xenial:
  Fix Released

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 1620557] Re: weather.noaa.gov was shut down

2016-09-22 Thread Hans Joachim Desserud

Thanks for resolving this issue :)

Could someone please take a look at bug 1610210 and bug 1621179 which
concerns two other packages which use the same (old) url?

-- 
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 Released
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 1626248] Re: libunistring0 has not been updated since 2010

2016-09-22 Thread Hans Joachim Desserud

** Tags added: upgrade-software-version

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

Title:
  libunistring0 has not been updated since 2010

Status in libunistring package in Ubuntu:
  New

Bug description:
  Libunistring is updated by FSF for every new version of Unicode. The
  current version of libunistring is 0.9.6 and has support for unicode
  version 9. The version shipped with Ubuntu is 0.9.3 which supports
  Unicode 7. Since the lib was last updated Unicode has added more than
  14,000 new code points which includes emoji support. Because of the
  number of Ubuntu packages that depend on libunistring I believe that
  it should be updated every time a new version is released, which is
  usually yearly following the release schedule of Unicode versions.

  Libunistring in Ubuntu has not been updated since 2010.

  Thank You for Ubuntu.

  Bob Pendleton

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunistring0 0.9.3-5.2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 21 14:35:34 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu3
  InstallationDate: Installed on 2015-01-16 (613 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libunistring
  UpgradeStatus: Upgraded to xenial on 2016-05-19 (124 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1626248/+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 1626627] [NEW] FFe: Build e-d-s with libphonenumber support

2016-09-22 Thread Jeremy Bicha

Public bug reported:

Debian builds evolution-data-server with libphonenumber support. Ubuntu
doesn't because libphonenumber was in main. Now that libphonenumber is
approved to be in main ( bug 1618178 ), I am requesting permission to
build evolution-data-server with libphonenumber.

** Affects: evolution-data-server (Ubuntu)
 Importance: Wishlist
 Status: New

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

Title:
  FFe: Build e-d-s with libphonenumber support

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Debian builds evolution-data-server with libphonenumber support.
  Ubuntu doesn't because libphonenumber was in main. Now that
  libphonenumber is approved to be in main ( bug 1618178 ), I am
  requesting permission to build evolution-data-server with
  libphonenumber.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1626627/+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 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"

2016-09-22 Thread Francesco Strappini

Same here with Xubuntu 16.04 on RPi 3

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

Title:
  Chromium-browser armhf crashes with "InitializeSandbox() called with
  multiple threads in process gpu-process"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  crashes on startup with

  [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() 
called with multiple threads in process gpu-process
  Segmentation fault

  System ODROID XU3 armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+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 1285444] Re: Login Successful, Desktop Never Loads

2016-09-22 Thread Coeur Noir

https://forum.ubuntu-fr.org/viewtopic.php?pid=21594335#p21594335

( sorry - why can't we edit comments ? )

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1588878] Re: CanoScan Lide 220 doesn't work

2016-09-22 Thread csola48

sane-find-scanner -q
found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan], 
chip=GL848+) at libusb:003:002
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient 
permissions)

CanoScan Lide 220 chip now: gl848+ !

Older CanoScan Lide 220: gl124.

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

Title:
  CanoScan Lide 220 doesn't work

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 14.04 I used to scan with CanoScan Lide 220, it worked fine.
  In Ubuntu 16.04 it doesn't work. XSane says "Failed to start scanner:
  Error during device I/O".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Jun  3 18:30:53 2016
  InstallationDate: Installed on 2016-04-26 (38 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1588878/+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 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

2016-09-22 Thread Amr Ibrahim

** Changed in: gvfs (Ubuntu Xenial)
   Status: Confirmed => Invalid

-- 
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:
  Invalid
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 1626605] Re: xorg error when waking up after suspend in YY

2016-09-22 Thread Victor gonzalez

** Attachment added: "xorg_logs+crash file.zip"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626605/+attachment/4746295/+files/xorg_logs+crash%20file.zip

** Description changed:

  Enviroment: latest image of yy
  
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety
  
- 
- HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD 
+ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD
  
  Steps to reproduce:
  
  1º Boot or reboot your laptop
  2º Once you're in log in screen go to indicator-session and suspend it
- 3º Once suspended, wake it up be pressin power button for example
+ 3º Once suspended, wake it up be pressing power button for example
  
  Current result: My mouse can move but clicking is not working on
  anything, then black screen and window error saying "The system is
  running on low graphics mode", finally it lets me choose how to start
  session again. Pics 1 and 2 attached
  
  Expected result: Laptop should wake up and let the user enter his
  session with out any issue.
  
  Add info: please find attached xorg logs, crash file saved in
  /sys/class/drm/card0/error and here is the dmesg output (line 938)
  https://pastebin.canonical.com/166279/

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

Title:
  xorg error when waking up after suspend in YY

Status in xorg package in Ubuntu:
  New

Bug description:
  Enviroment: latest image of yy

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD

  Steps to reproduce:

  1º Boot or reboot your laptop
  2º Once you're in log in screen go to indicator-session and suspend it
  3º Once suspended, wake it up be pressing power button for example

  Current result: My mouse can move but clicking is not working on
  anything, then black screen and window error saying "The system is
  running on low graphics mode", finally it lets me choose how to start
  session again. Pics 1 and 2 attached

  Expected result: Laptop should wake up and let the user enter his
  session with out any issue.

  Add info: please find attached xorg logs, crash file saved in
  /sys/class/drm/card0/error and here is the dmesg output (line 938)
  https://pastebin.canonical.com/166279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626605/+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

This bug was fixed in the package libgweather - 3.10.2-0ubuntu3

---
libgweather (3.10.2-0ubuntu3) trusty-proposed; urgency=medium

  * Switch to the new METAR data provider, the previous one was shut down
(update_metar_provider.patch, LP: #1620557).

 -- Dmitry Shachnev   Sat, 10 Sep 2016 17:10:21
+0300

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

-- 
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 Released
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 1626605] [NEW] xorg error when waking up after suspend in YY

2016-09-22 Thread Victor gonzalez

Public bug reported:

Enviroment: latest image of yy

Distributor ID: Ubuntu
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Codename:   yakkety

HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD

Steps to reproduce:

1º Boot or reboot your laptop
2º Once you're in log in screen go to indicator-session and suspend it
3º Once suspended, wake it up be pressing power button for example

Current result: My mouse can move but clicking is not working on
anything, then black screen and window error saying "The system is
running on low graphics mode", finally it lets me choose how to start
session again. Pics 1 and 2 attached

Expected result: Laptop should wake up and let the user enter his
session with out any issue.

Add info: please find attached xorg logs, crash file saved in
/sys/class/drm/card0/error and here is the dmesg output (line 938)
https://pastebin.canonical.com/166279/

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: yakkety

** Attachment added: "pics.zip"
   https://bugs.launchpad.net/bugs/1626605/+attachment/4746293/+files/pics.zip

** Tags added: yakkety

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

Title:
  xorg error when waking up after suspend in YY

Status in xorg package in Ubuntu:
  New

Bug description:
  Enviroment: latest image of yy

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD

  Steps to reproduce:

  1º Boot or reboot your laptop
  2º Once you're in log in screen go to indicator-session and suspend it
  3º Once suspended, wake it up be pressing power button for example

  Current result: My mouse can move but clicking is not working on
  anything, then black screen and window error saying "The system is
  running on low graphics mode", finally it lets me choose how to start
  session again. Pics 1 and 2 attached

  Expected result: Laptop should wake up and let the user enter his
  session with out any issue.

  Add info: please find attached xorg logs, crash file saved in
  /sys/class/drm/card0/error and here is the dmesg output (line 938)
  https://pastebin.canonical.com/166279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626605/+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 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

2016-09-22 Thread Amr Ibrahim

** Tags removed: verification-failed 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:
  Invalid
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 1285444] Re: Login Successful, Desktop Never Loads

2016-09-22 Thread Coeur Noir

And here are some other examples where removing
~/.cache/compizconfig-1
also helped.

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-22 Thread Henry J. Douglas

The arrows are not gone. I just made a clean install and update.

-- 
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/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-22 Thread Hansen

Are there any progress on this bug, i still have to runs scripts several
time a day to get the applet working.

-- 
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/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-09-22 Thread Gavin Dandridge

POST EDIT:

An edit to my post #48 as I made a typo, delive = device

-- 
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/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-09-22 Thread Gavin Dandridge

Thanks Luke! I followed your suggestion but sadly the kernel still
reports:

[ 6.822519] intel_sst_acpi 808622A8:00: No matching machine driver found

But thanks anyway, I really appreciate your help.

-- 
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/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1626245] Re: [MIR] fonts-android

2016-09-22 Thread Gunnar Hjalmarsson

On 2016-09-22 15:18, Michael Terry wrote:
> Is there another way to solve bug 1625734 than going back to
> fonts-android?
> 
> Is it possible to split fonts-noto-cjk into smaller chunks for
> example?

Yes it is. We did consider doing so last spring, but decided not to;
please see .

For the Z series it would be possible to pick up that idea again. In
that case we would get:

* fonts-noto-cjk
  Providing the weights regular and bold; approx. 22 MiB archive space

* fonts-noto-cjk-extras
  Providing the other font weights; approx. 50 MiB archive space

fonts-noto-cjk would then require approx. 22 - 2 = 20 MiB more archive
space comapred to fonts-droid-fallback. If that's something which the
server team can 'live with', it's one way to handle this.

> But for yakkety sure, let's promote this again.

Thanks!

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Fix Committed
Status in ghostscript package in Ubuntu:
  In Progress

Bug description:
  Please include the fonts-android package in Ubuntu's component main.

  fonts-android includes the fonts-droid-fallback binary, and as a
  result of the discussion at bug 1625734, the server team wants that
  libgs9-common, which currently recommends fonts-noto-cjk, is changed
  to instead recommend fonts-droid-fallback.

  fonts-android is a Debian package and included in Debian's component
  main. It was included in Ubuntu's component main between trusty and
  wily.

  Bugs:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android

  https://bugs.launchpad.net/ubuntu/+source/fonts-android

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1626245/+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 1626568] Re: rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module

Fixed: https://git.launchpad.net/~network-manager/network-
manager/+git/ubuntu/commit/?id=5fbc4bdf5dd

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1626568

Title:
  rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown
  symbol in module

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, 
like in in
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
 .

  It still builds fine:
  $ sudo make -f debian/tests/Makefile fake-rfkill
  make -C /lib/modules/4.8.0-15-generic/build 
KBUILD_SRC=/lib/modules/4.8.0-15-generic/build 
M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
Building modules, stage 2.
MODPOST 1 modules

  But it can't be loaded:
  $ sudo insmod debian/tests/fake-rfkill.ko
  insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown 
symbol in module
  $ dmesg
  [ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
  [ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
  [ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
  [ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1626568/+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 1626568] Re: rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module

"modprobe rfkill" fixes this -- the built .ko already declares that
dependency properly, it just doesn't get loaded by "insmod".

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

-- 
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/1626568

Title:
  rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown
  symbol in module

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, 
like in in
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
 .

  It still builds fine:
  $ sudo make -f debian/tests/Makefile fake-rfkill
  make -C /lib/modules/4.8.0-15-generic/build 
KBUILD_SRC=/lib/modules/4.8.0-15-generic/build 
M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
Building modules, stage 2.
MODPOST 1 modules

  But it can't be loaded:
  $ sudo insmod debian/tests/fake-rfkill.ko
  insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown 
symbol in module
  $ dmesg
  [ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
  [ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
  [ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
  [ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1626568/+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 1626568] Re: rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module

2016-09-22 Thread Andy Whitcroft

** Tags added: kernel-4.8

-- 
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/1626568

Title:
  rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown
  symbol in module

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, 
like in in
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
 .

  It still builds fine:
  $ sudo make -f debian/tests/Makefile fake-rfkill
  make -C /lib/modules/4.8.0-15-generic/build 
KBUILD_SRC=/lib/modules/4.8.0-15-generic/build 
M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
Building modules, stage 2.
MODPOST 1 modules

  But it can't be loaded:
  $ sudo insmod debian/tests/fake-rfkill.ko
  insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown 
symbol in module
  $ dmesg
  [ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
  [ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
  [ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
  [ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1626568/+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 1626568] [NEW] rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module

Public bug reported:

The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, like 
in in
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
 .

It still builds fine:
$ sudo make -f debian/tests/Makefile fake-rfkill
make -C /lib/modules/4.8.0-15-generic/build 
KBUILD_SRC=/lib/modules/4.8.0-15-generic/build 
M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
  Building modules, stage 2.
  MODPOST 1 modules

But it can't be loaded:
$ sudo insmod debian/tests/fake-rfkill.ko
insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown 
symbol in module
$ dmesg
[ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
[ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
[ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
[ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-4.8

-- 
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/1626568

Title:
  rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown
  symbol in module

Status in network-manager package in Ubuntu:
  New

Bug description:
  The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, 
like in in
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
 .

  It still builds fine:
  $ sudo make -f debian/tests/Makefile fake-rfkill
  make -C /lib/modules/4.8.0-15-generic/build 
KBUILD_SRC=/lib/modules/4.8.0-15-generic/build 
M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
Building modules, stage 2.
MODPOST 1 modules

  But it can't be loaded:
  $ sudo insmod debian/tests/fake-rfkill.ko
  insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown 
symbol in module
  $ dmesg
  [ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
  [ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
  [ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
  [ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1626568/+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 1626245] Re: [MIR] fonts-android

2016-09-22 Thread Michael Terry

I mean, it's fine to put this back if we need it.  It used to be in
main, it's just fonts, etc.

But for the same reasons that we downgraded it (has a replacement), it
would still be nice to drop it again in the future.  Is there another
way to solve bug 1625734 than going back to fonts-android?

Is it possible to split fonts-noto-cjk into smaller chunks for example?

But for yakkety sure, let's promote this again.

** Changed in: fonts-android (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Fix Committed
Status in ghostscript package in Ubuntu:
  In Progress

Bug description:
  Please include the fonts-android package in Ubuntu's component main.

  fonts-android includes the fonts-droid-fallback binary, and as a
  result of the discussion at bug 1625734, the server team wants that
  libgs9-common, which currently recommends fonts-noto-cjk, is changed
  to instead recommend fonts-droid-fallback.

  fonts-android is a Debian package and included in Debian's component
  main. It was included in Ubuntu's component main between trusty and
  wily.

  Bugs:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android

  https://bugs.launchpad.net/ubuntu/+source/fonts-android

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1626245/+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 1365432] Re: llvm doesn't install any LLVMConfig.cmake file

2016-09-22 Thread layus

llvm-dev provides LLVMConfig.cmake (see 
http://packages.ubuntu.com/search?mode=exactfilename=xenial=all=any=LLVMConfig.cmake=contents),
 which is found by cmake if you use `find_package(LLVM CONFIG)`.
This is enough for LLVM to find its components and such.


However, the bug is still not solved for Clang. I think the correct bug for 
Clang is https://bugs.launchpad.net/ubuntu/+source/clang/+bug/1365434

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

Title:
  llvm doesn't install any LLVMConfig.cmake file

Status in One Hundred Papercuts:
  Confirmed
Status in clang package in Ubuntu:
  Confirmed
Status in llvm package in Ubuntu:
  Confirmed
Status in llvm-defaults package in Ubuntu:
  Confirmed
Status in llvm-toolchain-3.5 package in Ubuntu:
  Confirmed

Bug description:
  Cmake cannot find llvm because LLVMConfig.cmake is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1365432/+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 1621203] Re: evolution/totem/gthumb crashes when run in vnc session

2016-09-22 Thread Christopher Weber

** Summary changed:

- evolution crashes when run in vnc session
+ evolution/totem/gthumb crashes when run in vnc session

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

Title:
  evolution/totem/gthumb crashes when run in vnc session

Status in evolution package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu
     Description:   Ubuntu 16.04.1 LTS
     Release:   16.04

  2) The version of the package I am using:
     evolution 3.18.5.2-0ubuntu3
     vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2
     xfwm4 4.12.3-1ubuntu2
     fluxbox 1.3.5-2

  3) What I expect to happen:
     evolution runs so I can access mail/calendar.

  4) What happened:
     I'm running vnc4server with xfce4 as the window manager/desktop.
     When I attempt to start evolution the following happens.

     [cweber@usacwebera ~]: evolution

     (evolution:22961): Gdk-ERROR **: The program 'evolution' received an X 
Window System error.
     This probably reflects a bug in the program.
     The error was 'BadRequest (invalid request code or no such operation)'.
   (Details: serial 95 error_code 1 request_code 149 (RANDR) minor_code 8)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the GDK_SYNCHRONIZE environment
    variable to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() 
function.)
     Trace/breakpoint trap (core dumped)

     This happened using fluxbox too, but does not happen if I'm at the local
 desktop using either xfce4 or fluxbox. Nor does it happen in an 
 ssh session using X Tunnelling.

     Only when in a vnc4 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Sep  7 14:34:00 2016
  InstallationDate: Installed on 2014-11-10 (666 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: evolution
  UpgradeStatus: Upgraded to xenial on 2016-08-31 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1621203/+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 1626135] Re: not create when create schedule to use google account

2016-09-22 Thread Rakugou

Sorry to lack my bug report.
And may too difficut to understand my report because of not goot at English

GNOME Calender press key [Ctrl + N], displayed to create schedule. write
schedule with google calender(already entried google account to
[設定]→[オンラインアカウント]), and click [追加] in Japanese, and try to add schedule, can't
add schedule. In GNOME Calendar, schedule I added is not displayed and confirm
google calendar in browser. not displayed schedule I added.
But add achedule without google calendar (for example default calendar "個人"
displayed in Japanese ), can add schedule and displayed gnome calendar.

I think do not sync google calender in GNOME Calender(or have a problem
in "Evolution データサーバー" to access google calendar...).

Please tell me to solve this situation.

In addition, I use Ubuntu 16.04 LTS

--
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/1626135

Title:
not create when create schedule to use google account

Status in gnome-calendar package in Ubuntu:
Incomplete

Bug description:
not create when create schedule in calendar with google account, but
can create schedule when create by calendar without google account
(for example default calendar "個人" displayed in Japanese )

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

[Desktop-packages] [Bug 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

-- 
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/1626494

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626494/+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 1151844] Re: [MIR] google-glog

2016-09-22 Thread Sebastien Bacher

The component was demoted in previous cycles and needs to be promoted
back, there is no action needed on the bug but changing to fix-commited
to help with the component mismatch summary of the situation

** Changed in: google-glog (Ubuntu)
   Status: Fix Released => Fix Committed

** Changed in: gflags (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  [MIR] google-glog

Status in gflags package in Ubuntu:
  Fix Committed
Status in google-glog package in Ubuntu:
  Fix Committed

Bug description:
  Rationale
  

  There is currently no C++ compatible logging package in main.

  Canonical projects that require logging should not be resolving the
  requirement.

  The mir project is an an example - and glog seems the most lightweight
  solution to its logging requirements. As a system component, mir
  requires all dependencies to be in main. Other components will have
  the same requirements.

  
  Violations of UbuntuMainInclusionRequirements
  

  There's a dependency on libgflags, but no violations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gflags/+bug/1151844/+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 1588533] Re: Mobile Data Network not working after screen is off for more then 2 min

2016-09-22 Thread eviweb

Hi,

the problems still remains after upgrade to OTA-12 (sorry for the delay, I'm 
busy...)
Mobile networks fail to reconnect after a long sleep, and switching airplane 
mode off/on solves this issue.
And the solution to re enable phone calls is still to reboot the phone as I 
don't find which service to restart.
More details :
- incoming and outgoing phone calls don't work
- for incoming calls, people are directly routed to the voice mailbox
- for outgoing calls, they stop quickly and you return to the phone keyboard
- during the phone attempt the volume, microphone, numpad buttons... of the 
phone keyboard don't work
- only receiving and sending SMS are possible
- Internet connection needs to switch the airplane mode off/on

The OTA-13 just have been published and I didn't have time to apply it for now.
I will take time to post a feedback after upgrading.

Eric

-- 
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/1588533

Title:
  Mobile Data Network not working after screen is off for more then 2
  min

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  With OTA-11 the Mobile Network 3G and H do not come back into working
  mode after MX4 comes back from turning off the screen.

  Example:
  I reboot the MX4 and when it powers up all is working I get WiFi and Mobile 
Network 3G working great.
  I press the button to turn off the screen and leave it off for 2 or more 
minutes, when I turn it back on and unlock the device the Data network is not 
working. 

  I can make calls and SMS but MMS and Data has no connection, at this
  point i can toggle the Data switch in the mobile configuration or put
  the phone into airplane mode and back into active and it works until
  next time.

  Thank You

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588533/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-09-22 Thread kabeza

Hi

I'm having this same issue in my desktop PC with ElementaryOS Freya
Also have a Intel based graphics board

Updated everything to 22 sept. 2016 and issue is still active

Solving temporarily with Ctrl+Alt+F1 then Alt+F7

** Attachment added: "imagen_499.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1568604/+attachment/4746169/+files/imagen_499.jpg

-- 
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/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-intel-lts-xenial (Ubuntu)
   Status: New => Confirmed

-- 
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/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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