date:20180118

** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I was installing Wine and then this error showed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 01:26:57 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-jlfYFS/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1744219/+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 1744219] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-01-18 Thread Isaiah Banks

Public bug reported:

I was installing Wine and then this error showed.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 19 01:26:57 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-jlfYFS/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I was installing Wine and then this error showed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 01:26:57 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-jlfYFS/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1744219/+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 1744206] Re: package emacs24-el (not installed) failed to install/upgrade: unable to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation not permitted

** Tags removed: need-duplicate-check

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

Title:
  package emacs24-el (not installed) failed to install/upgrade: unable
  to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new':
  Operation not permitted

Status in emacs24 package in Ubuntu:
  New

Bug description:
  I have no idea what I'm doing in Ubuntu. I have been following online
  guides to tweak. I think I added unsafe update repositories. I have
  since deleted the sources.list and used the Software Updater settings
  to create a new one. I have been trying to install git gui, but
  running into problems.

  Ubuntu 16.04 LTS
  ~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: emacs24-el (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 18 23:25:46 2018
  DuplicateSignature:
   package:emacs24-el:(not installed)
   Unpacking emacs24-common (24.5+1-6ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/emacs24-common_24.5+1-6ubuntu1_all.deb (--unpack):
unable to open '/usr/share/emacs/24.5/lisp/leim/quail/lao.elc.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation not 
permitted
  InstallationDate: Installed on 2018-01-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: emacs24
  Title: package emacs24-el (not installed) failed to install/upgrade: unable 
to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1744206/+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 1744206] [NEW] package emacs24-el (not installed) failed to install/upgrade: unable to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation not permitte

2018-01-18 Thread Tina Taylor

Public bug reported:

I have no idea what I'm doing in Ubuntu. I have been following online
guides to tweak. I think I added unsafe update repositories. I have
since deleted the sources.list and used the Software Updater settings to
create a new one. I have been trying to install git gui, but running
into problems.

Ubuntu 16.04 LTS
~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: emacs24-el (not installed)
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Jan 18 23:25:46 2018
DuplicateSignature:
 package:emacs24-el:(not installed)
 Unpacking emacs24-common (24.5+1-6ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/emacs24-common_24.5+1-6ubuntu1_all.deb (--unpack):
  unable to open '/usr/share/emacs/24.5/lisp/leim/quail/lao.elc.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation not 
permitted
InstallationDate: Installed on 2018-01-08 (11 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: emacs24
Title: package emacs24-el (not installed) failed to install/upgrade: unable to 
open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation 
not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: emacs24 (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 emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1744206

Title:
  package emacs24-el (not installed) failed to install/upgrade: unable
  to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new':
  Operation not permitted

Status in emacs24 package in Ubuntu:
  New

Bug description:
  I have no idea what I'm doing in Ubuntu. I have been following online
  guides to tweak. I think I added unsafe update repositories. I have
  since deleted the sources.list and used the Software Updater settings
  to create a new one. I have been trying to install git gui, but
  running into problems.

  Ubuntu 16.04 LTS
  ~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: emacs24-el (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 18 23:25:46 2018
  DuplicateSignature:
   package:emacs24-el:(not installed)
   Unpacking emacs24-common (24.5+1-6ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/emacs24-common_24.5+1-6ubuntu1_all.deb (--unpack):
unable to open '/usr/share/emacs/24.5/lisp/leim/quail/lao.elc.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation not 
permitted
  InstallationDate: Installed on 2018-01-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: emacs24
  Title: package emacs24-el (not installed) failed to install/upgrade: unable 
to open '/usr/share/emacs/24.5/lisp/textmodes/bibtex.el.gz.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1744206/+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 1733181] Re: Gksu doesn't automatically focus the password field when run from terminal

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

** Changed in: gksu (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Gksu doesn't automatically focus the password field when run from
  terminal

Status in gksu package in Ubuntu:
  Expired

Bug description:
  OS: Ubuntu 17.10
  gksu: 2.0.2-9ubuntu1

  If you run:
  $ gksu echo foo

  the focus is still on the terminal, and if a user types their password
  quickly it will be displayed in clear text in the terminal in the
  background.

  Moreover, clicking with the mouse on the password field doesn't focus
  it. A workaround to that is to manually do an +.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1733181/+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 1744178] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

2018-01-18 Thread Daniel van Vugt

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

** This bug is no longer a duplicate of private bug 1744063
** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash occurred after reboot from installing gnome-shell-extensions and
  then upgrading to 4.13.0-30-generic.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Jan 18 18:54:49 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-13 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744178/+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 1743736] Re: In overview, windows from all workspaces are shown for the second display

2018-01-18 Thread Daniel van Vugt

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=652580
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Fix Committed

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

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

Title:
  In overview, windows from all workspaces are shown for the second
  display

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have disabled workspaces on primary display only, and I have enabled
  workspaces to span displays, in tweak tool.

  Now things mostly work how I expect. Windows are isolated to the
  workspace they are and I can move them between displays (monitors).
  The issue is if I go into an overview mode. Then, for the primary
  display, I see only windows from my current workspace. But for the
  secondary display, I see windows from all workspaces being shown in
  the overview mode.

  I would expect that only the windows from the current workspace are
  shown also on the secondary display in the overview mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 02:19:13 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-11-20 (57 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1743736/+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 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

2018-01-18 Thread Daniel van Vugt

I think this bug is about the single monitor case. Please open a new bug
for the multi-monitor case.

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Even when doing nothing at all, gnome-shell uses around 70% CPU.

  ```
  inxi -t cm
  Processes: CPU: % used - top 5 active
 1: cpu: 68.6% command: gnome-shell pid: 1399
 2: cpu: 50.4% command: Xwayland pid: 1405
 3: cpu: 19.7% command: firefox pid: 3684
 4: cpu: 2.4% command: gnome-shell pid: 1859
 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
  ```

  It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
  ```
  echo $XDG_SESSION_TYPE
  x11
  ```

  While searching I found a recent problem with AMD GPUs, but I'm using an 
Intel GPU
  ```
  glxinfo 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
  GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
  GLX_SGI_make_current_read, GLX_SGI_swap_control
  client glx vendor string: Mesa Project and SGI
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 1536MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.1
  OpenGL vendor string: Intel Open Source Technology Center
  OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0
  OpenGL core profile shading language version string: 4.50
  OpenGL core

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-01-18 Thread Hui Wang

Just checked the pulseaudio_11.1-1ubuntu4_amd64.deb, the dell-dock-tb16
-usb-audio.conf is in it, and will be put to the folder
/usr/share/pulseaudio/alsa-mixer/profile-sets when installing this
package. That is expected, so the bug 1718824 should be fixed in this
version.

I didn't test it on real hardware since I don't have the hardware, the
hardware is in Taipei office.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1744178] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1744063, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039204/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039206/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039209/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039210/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039211/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039212/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1744178/+attachment/5039213/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1744063

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash occurred after reboot from installing gnome-shell-extensions and
  then upgrading to 4.13.0-30-generic.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Jan 18 18:54:49 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-13 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744178/+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 1740508] Re: Web fonts take a considerable amount of time to load [over a high-speed connection]

2018-01-18 Thread Bug Watch Updater

** Changed in: firefox
   Status: New => Expired

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

Title:
  Web fonts take a considerable amount of time to load [over a high-
  speed connection]

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Even over a high-speed connection, web fonts seem to take far too long
  to download for websites in which the default font is not installed on
  the drive of my system.

  
  Example site with issue on my system: 'https://www.kraken.com/'
  Basic font family information, extracted from CSS: 'font-family:sans-serif'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 57.0.1+build2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
  Uname: Linux 4.13.0-21-lowlatency x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeb1236 F pulseaudio
  BuildID: 20171129230227
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 29 09:23:41 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.86.1 dev wlp1s0 proto static metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.86.0/24 dev wlp1s0 proto kernel scope link src 192.168.86.30 metric 
600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1c664c74-b6f2-471a-9aa4-e303d1171129
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-1c664c74-b6f2-471a-9aa4-e303d1171129
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 01DC01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd09/14/2017:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn01DC01:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1740508/+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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

2018-01-18 Thread Brendan Brewster

I too am desperate for a solution (100+ Docker containers each with a
veth)

How do we apply Sergey Tikhonov's patch to our local system?

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

I believe what Robie is looking for is an answer to the question -
"Should we reject the uploads currently in the -proposed queue?"

>From my skimming of the bug report it seems like the fix in
1:11.1-1ubuntu3 was incomplete hence the need for the upload of
1:11.1-1ubuntu4 and why we are asking about the existing SRUs.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1743797] Re: Xorg not recognizing AMD graphics card

2018-01-18 Thread Greta Regan

I installed 'linux-generic-hwe-16.04', as suggested, but there's no
change. Perhaps because the radeon.modeset=0 is still in my system - but
I can't find where. My boot sequence no longer shows radeon.modeset=0,
but it came up when I ran dmesg | egrep | 'drm|radeon'. I've included
both outputs below.

I checked all versions of the boot sequence, including the 4.4.0-104
versions, specified in the dmesg output. The recovery mode has
'nomodeset', but no radeon.modeset=0.  I included outputs of the
4.4.0-104 generic and recovery boot sequences below, in case they'd be
of use.

Can you tell me how to get at the radeon.modeset=0 settings to remove
them, or if you think that's not the problem, offer any other
suggestions? My knowledge of Linux is miniscule.

Thanks.
 

My boot sequence:

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
123f436f-0331-4097-8a8e-54cc927298c4
else
  search --no-floppy --fs-uuid --set=root 123f436f-0331-4097-8a8e-54cc927298c4
fi
        linux
/boot/vmlinuz-4.13.0-26-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 
ro  drm.debug=0xe plymouth:debug
initrd
/boot/initrd.img-4.13.0-26-generic


dmesg | egrep | 'drmradeon':

greta@NSH-HP-Compaq-nc6400-RB523UA-ABA:~$ dmesg | egrep 'drm|radeon'
[    0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
[    0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
[    2.935307] [drm] Initialized drm 1.1.0 20060810
[    3.022679] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
[   21.247887] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!


4.4.0-104 generic boot sequence:

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
123f436f-0331-4097-8a8e-54cc927298c4
else
  search --no-floppy --fs-uuid --set=root 123f436f-0331-4097-8a8e-54cc927298c4
fi
echo
'Loading Linux 4.4.0-104-generic ...'
        linux
/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 
ro  drm.debug=0xe plymouth:debug
echo
'Loading initial ramdisk ...'
initrd
/boot/initrd.img-4.4.0-104-generic


4.4.0-104 generic (recovery mode) boot sequence:

Recovery mode
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
123f436f-0331-4097-8a8e-54cc927298c4
else
  search --no-floppy --fs-uuid --set=root 123f436f-0331-4097-8a8e-54cc927298c4
fi
echo
'Loading Linux 4.4.0-104-generic ...'
        linux
/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 
ro recovery nomodeset 
echo
'Loading initial ramdisk ...'
initrd
/boot/initrd.img-4.4.0-104-generic

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

Title:
  Xorg not recognizing AMD graphics card

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A few months after upgrading to Ubuntu 16.04, my graphics card stopped
  working. I got a black screen after booting. I was able to work around
  that problem, and then around the problem of losing my external
  display when I closed my laptop lid, so I can now boot normally and
  have only one problem - I still only have software rendering, which
  isn't up to the job.

  I checked my graphics card and it was on the list of fully supported
  versions. I found work-arounds online for my other problems, but no
  way to fix this one, which results in choppy video with audio out of
  sync.

  I trust the apport report which should be attached will give you the
  specs you need.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'

[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2018-01-18 Thread Ryan Lounsbury

I am also getting this in 17.10 on a Dell Optiplex 9020. It works fine
for about 20-30 minutes and then I can't ping the network and all
network connected jobs stop responding. It stays that way for 2-5
minutes and then it comes back up. Network status shows connected and
never indicates that the network connection itself stopped working. It
is driving me batty.

  *-network 
   description: Ethernet interface
   product: Ethernet Connection I217-LM
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: eno1
   version: 04
   serial: f8:b1:56:dc:f7:f2
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.120.85 latency=0 
link=yes multicast=yes port=twisted pair speed=100Mbit/s
   resources: irq:28 memory:f7c0-f7c1 memory:f7c3d000-f7c3dfff 
ioport:f080(size=32)

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600

[Desktop-packages] [Bug 1744155] [NEW] found while checking

2018-01-18 Thread Berkok Baybas

Public bug reported:

i can't give details

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jan 18 23:15:30 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GT216GLM [Quadro FX 880M] [103c:1521]
InstallationDate: Installed on 2016-10-01 (473 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP EliteBook 8540w
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=825aca86-4595-48d6-84b4-ed29a6020695 ro splash quiet plymouth:debug=1 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CVD Ver. F.24
dmi.board.name: 1521
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 32.35
dmi.chassis.asset.tag: CND1164H6Z
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8540w
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Jan 18 09:27:10 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  found while checking

Status in xorg package in Ubuntu:
  New

Bug description:
  i can't give details

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 18 23:15:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company GT216GLM [Quadro FX 880M] [103c:1521]
  InstallationDate: Installed on 2016-10-01 (473 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=825aca86-4595-48d6-84b4-ed29a6020695 ro splash quiet plymouth:debug=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.asset.tag: CND1164H6Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

[Desktop-packages] [Bug 1744131] Re: misleading ubuntu help (German/Deutsch) on screen dimming

2018-01-18 Thread Gunnar Hjalmarsson

Thanks for your report!

This seems to be an inconsistency in the German translations of "Power",
and yes, I suppose it should better be changed in the documentation. So
what's needed is a correction of the German translation of gnome-user-
docs (which happens upstream at GNOME).

https://git.gnome.org/browse/gnome-user-docs/tree/gnome-help/de/de.po

I get the impression that there is a need to replace "Leistung" with
"Energie" in the translations of more pages but power-whydim.page.

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

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

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => Triaged

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu German Translators (ubuntu-l10n-de)

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

Title:
  misleading ubuntu help (German/Deutsch) on screen dimming

Status in Ubuntu Translations:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  The German-language version of the online-help on screen dimming:  
https://help.ubuntu.com/stable/ubuntu-help/power-whydim.html
  points to non-existing configuration. It says:

  So verhindern Sie die automatische Abdunklung des Bildschirms:
  Öffnen Sie die Aktivitäten-Übersicht und tippen Sie Leistung ein.
  Klicken Sie auf Leistung, um das Panel zu öffnen.
  ...

  However in Artful Aardvark (Ubuntu 17.10) there is no such configuration 
entry "Leistung". Therefore the help guide leads nowhere, and frustrates users.
  Instead, the config section is named "Energie". Please update the help page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1744131/+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 1744131] [NEW] misleading ubuntu help (German/Deutsch) on screen dimming

You have been subscribed to a public bug:

The German-language version of the online-help on screen dimming:  
  https://help.ubuntu.com/stable/ubuntu-help/power-whydim.html
points to non-existing configuration. It says:

So verhindern Sie die automatische Abdunklung des Bildschirms:
Öffnen Sie die Aktivitäten-Übersicht und tippen Sie Leistung ein.
Klicken Sie auf Leistung, um das Panel zu öffnen.
...

However in Artful Aardvark (Ubuntu 17.10) there is no such configuration entry 
"Leistung". Therefore the help guide leads nowhere, and frustrates users.
Instead, the config section is named "Energie". Please update the help page.

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

-- 
misleading ubuntu help (German/Deutsch) on screen dimming
https://bugs.launchpad.net/bugs/1744131
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs in Ubuntu.

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

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

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1725432/+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 1725432] Re: Restore failed due to missing source option

This bug was fixed in the package deja-dup - 36.3-0ubuntu0.1

---
deja-dup (36.3-0ubuntu0.1) artful; urgency=medium

  * New upstream bug fix release
- Fixes restore dialog being blank on fresh install (LP: #1725432)

 -- Michael Terry   Fri, 20 Oct 2017 16:46:43 -0400

** Changed in: deja-dup (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1725432/+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 1744137] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just booted to pc and got the error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Jan 18 01:49:02 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UPx3dY/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1744137/+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 1744137] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-01-18 Thread William Biggs

Public bug reported:

I just booted to pc and got the error

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Jan 18 01:49:02 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-UPx3dY/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-18 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just booted to pc and got the error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Jan 18 01:49:02 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UPx3dY/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1744137/+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 1724871] Update Released

The verification of the Stable Release Update for nvidia-graphics-
drivers-304 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 nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1724871

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.16.04.2) xenial; urgency=medium

  * Support for kernel 4.11 and 4.12. (LP: #1724871)
- debian/dkms/patches/buildfix_kernel_4.11.patch
- debian/dkms/patches/buildfix_kernel_4.12.patch

 -- Marcelo Henrique Cerri   Wed, 01 Nov
2017 16:57:45 -0200

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: Incomplete => Fix Released

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-01-18 Thread chris pollock

Crash happened again this morning update of:

Commandline: apt-get -y install binutils libpython2.7 libpython2.7-dev 
libpython2.7-minimal libpython2.7-stdlib python2.7 python2.7-dev 
python2.7-minimal
Upgrade: python2.7-dev:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), python2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), binutils:amd64 (2.26.1-1ubuntu1~16.04.5, 
2.26.1-1ubuntu1~16.04.6), libpython2.7:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), python2.7:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), libpython2.7-dev:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3), libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.2, 
2.7.12-1ubuntu0~16.04.3)

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

Title:
  gnome-shell crashed with heap corruption in g_strfreev() from
  g_themed_icon_finalize()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Happened during update of these packages
  Start-Date: 2017-07-24  16:09:37
  Commandline: apt-get -y install imagemagick imagemagick-6.q16 
imagemagick-common libimage-magick-perl libimage-magick-q16-perl 
libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra 
libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr 
xserver-xorg-core xserver-xorg-legacy
  Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8)
  End-Date: 2017-07-24  16:12:37

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next 
size (fast): 0x05eed540 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 16:11:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1496068513
  InstallationDate: Installed on 2014-10-24 (1004 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/chris
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at 
malloc.c:5006
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3867
   __GI___libc_free (mem=) at malloc.c:2968
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid next size (fast): 0x05eed540 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+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 1725432] Re: Restore failed due to missing source option

** Tags removed: verification-failed verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1725432/+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 1727653] Re: error: can't start new thread

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

** Changed in: deja-dup (Ubuntu)
   Status: New => Confirmed

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1743013] Re: deja-dup fails when launched automatically

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

** This bug has been marked a duplicate of bug 1727653
   error: can't start new thread

** Tags added: bot-stop-nagging

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

Title:
  deja-dup fails when launched automatically

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  In #1727653 an error was reported that stated that backup using
  duplicity failed.

  However, the error only manifests in duplicity but is triggered by the
  calling Deja-Dup.

  Launching Deja-Dup automatically will ALWAYS lead to the error.

  Launching Deja-Dup from the console/bash will NEVER lead to the error.

  Any attempts to set number of open file limits do not remedy the
  issue.

  Please refer to #1727653 and associated errors as all analysis have
  gone into duplicity so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 18:55:12 2018
  InstallationDate: Installed on 2017-10-20 (84 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1743013/+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 1730451] Re: MemoryError while verifying backup

2018-01-18 Thread Olivier Crête

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-
Chain start time: Fri Jan  5 18:45:00 2018
Chain end time: Wed Jan 17 16:44:04 2018
Number of contained backup sets: 2
Total number of contained volumes: 1741
 Type of backup set:Time:  Num volumes:
Full Fri Jan  5 18:45:00 2018  1628
 Incremental Wed Jan 17 16:44:04 2018   113
-

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-01-18 Thread Balint Reczey

** Changed in: update-manager (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

** Changed in: update-manager (Ubuntu Artful)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

** Changed in: update-manager (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: update-manager (Ubuntu Artful)
   Status: Confirmed => In Progress

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+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 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

2018-01-18 Thread Marco Bianchi

I am truly sorry to say that I have tried many of the recommended
solutions for this problem but to no avail. I am running Ubuntu 16.04 on
a AMD 8-core desktop machine and if I ever ever ever even try to give a
command like sudo apt-get update and apt-get upgrade I inevitably find
myself with an operating system without ethernet connection. I have been
unable to fix that no matter what I have tried so far. I have spent DAYS
reading the blogs and trying to get a fix for this bug. In the end the
only solution I could find so far was to use the original ssd back up
disk to get back to the original system, before the sudo apt-get update
etc commands. Can anyone in this forum or elsewhere explain in a simple
and clear manner how to fix this major issue with ubuntu upgrades?

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

2018-01-18 Thread Marco Bianchi

Also not to mention that even when I use my 16.04 without ever using the
sudo apt-get update command, the wifi network is also not detected by
ubuntu.

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2018-01-18 Thread Marcelo Cerri

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

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

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1713457/+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 1730451] Re: MemoryError while verifying backup

2018-01-18 Thread Kenneth Loafman

Also, would you please provide the duplicity command line for the
incremental?


** Changed in: duplicity
Milestone: None => 0.8.00

** Changed in: duplicity
 Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)

** Changed in: duplicity
   Importance: Undecided => High

** Changed in: duplicity
   Status: New => In Progress

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1743975] Re: "Power Statistics" UI become grey and have no respond after launch it about 30 seconds

** Changed in: gnome-power-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "Power Statistics" UI become grey and have no respond after launch it
  about 30 seconds

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Install Ubuntu 16.04 and launch Power Statistics,
  After the application launched for a while(about 30 sec),
  the UI become gray and has no response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1743975/+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 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

Status in evince package in Ubuntu:
  New

Bug description:
  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.

  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops
  working for some files.

  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for
  some files. Some files I can click and they open in Evince each time,
  whereas other files will never open in Evince. They open fine in other
  applications and under X.

  When I try to open the file from the command line, I get the following
  error message:

  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

  If I rename the file (e.g. by adding the number "2" to the file name),
  make a copy or move it to another directory, it opens without
  problems. However, after some time the renamed or new file will fail
  to open with the same error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+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 1730451] Re: MemoryError while verifying backup

2018-01-18 Thread Kenneth Loafman

OK, sounds like the distro is keeping up.  I like that.

One way to find out how many incrementals you have is "--collection-
status", like so:

$ duplicity --collection-status 

and then counting the number of incrementals for the current backup.  As
a rule of thumb, you should have fewer that 30 incrementals before doing
a full backup.


** Also affects: duplicity
   Importance: Undecided
   Status: New

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1743985] Re: color icon have no change

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  color icon have no change

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  1. The color of calendar color icon have no change in "Calendar Settings" 
after change "Birthdays" calendar color
  a. Boot into desktop. Launch the "calendar", click "Manage your 
calendars"-->"Calendar Settings"-->"Birthdays"-->"color", 
  b. change color and save. Return to the "Calendar Settings", find the color 
of "Birthdays" color icon have no change. => So issue occurs.

  
  2. Two identical color icon appear after Picked a new color under the 
"Custom" on Calendar
  a. Launch the calendar from Ubuntu software, click "Manage your 
calendars"-->"Calendar Settings"-->"Birthdays"-->"color"-->"+" to 
select one color successfully.
  b. Return to the "Calendar Settings"
  c. once again into "Birthdays"-->"color".
  d. find two identical color icon appear under "custom" item. => So issue 
occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1743985/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate

Thank you for your bug report, that's not really a bug or a new
behaviour, automatic login is about login not about unlock. In any case
not a control center issue

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Package changed: gnome-control-center (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Automatic login still requires user password after suspend/hibernate

Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  gnome-control-center 3.26.2

  When I set Ubuntu to automatically login a user the user still has to
  enter their password when resuming from a suspended session. The only
  option I can find to fix this is to disable the lock-screen
  completely, which I don't want to since I still want it to be an
  option to manually lock it. Setting Privacy > Screen Lock to off
  doesn't affect this behavior at all.

  The solution seems to be to use dconf-editor and change
  org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got
  the solution after asking on askubuntu.com:
  https://askubuntu.com/questions/990056/turn-off-requesting-user-
  password-after-suspend-17-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1740792/+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 1743985] Re: color icon have no change

When reporting a bug it's useful to include some details on the system,
at least including the Ubuntu serie and software version you are using

** Changed in: gnome-calendar (Ubuntu)
   Status: New => Incomplete

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

Title:
  color icon have no change

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  1. The color of calendar color icon have no change in "Calendar Settings" 
after change "Birthdays" calendar color
  a. Boot into desktop. Launch the "calendar", click "Manage your 
calendars"-->"Calendar Settings"-->"Birthdays"-->"color", 
  b. change color and save. Return to the "Calendar Settings", find the color 
of "Birthdays" color icon have no change. => So issue occurs.

  
  2. Two identical color icon appear after Picked a new color under the 
"Custom" on Calendar
  a. Launch the calendar from Ubuntu software, click "Manage your 
calendars"-->"Calendar Settings"-->"Birthdays"-->"color"-->"+" to 
select one color successfully.
  b. Return to the "Calendar Settings"
  c. once again into "Birthdays"-->"color".
  d. find two identical color icon appear under "custom" item. => So issue 
occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1743985/+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 1744076] Re: IPv6 property path is too long

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1730451] Re: MemoryError while verifying backup

2018-01-18 Thread Olivier Crête

For some reason, a manually triggered backup from deja-dup worked this
time, and it did an incremental backup. I'm not sure what changed, as it
had failed multiple times today.

- When you upgraded to 0.7.15, did you remove the distro's version?

I use the distro's package (Fedora has 0.7.15)

- How much memory do you have? Is it the same as previous?

Yeah, I have 16 GB of RAM, so I doubt that's the problem.

- How long of an incremental change list do you have?

How do I get that?

- Have you tried making a full backup?

Making full backups works fine it seems, it's only incremental that's
broken.

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

Title:
  MemoryError while verifying backup

Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1730451/+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 1743429] Re: GNOME Software doesn't support animated Gifs for screenshots

2018-01-18 Thread Bug Watch Updater

** Changed in: gnome-software
   Importance: Medium => Wishlist

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

Title:
  GNOME Software doesn't support animated Gifs for screenshots

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

Bug description:
  I am running GNOME Software on Ubuntu 16.04. If I look for Tizonia, it
  shows the app description and a static screenshot. The media uploaded
  to the store is actually a gif, but GNOME Software doesn't seem to
  support it.

  Steps to reproduce

  * Open GNOME Software
  * Search for tizonia
  * Wait for screenshot to load

  Expected behaviour

  * Animated gif plays in the page for the application

  Actual behaviour

  * Only the first frame of the animated gif is displayed.

  See screenshot attached.

  This is the media as it has been uploaded to the store:-
  https://dashboard.snapcraft.io/site_media/appmedia/2017/12/tizonia-
  usage-screencast.gif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 15 17:15:51 2018
  InstallationDate: Installed on 2017-07-03 (196 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1743429/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

2018-01-18 Thread Łukasz Zemczak

The current ubuntu-drivers-common package in xenial-proposed fails to
build on s390x:

https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.4.17.5/+build/14214850

I have re-run the build once already and it's still failing on unit-
tests. Could someone take a look and try to resolve that? This SRU can't
get published if it's not built for all supported architectures.

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

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

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

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1744076] Re: IPv6 property path is too long

** Description changed:

  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:
  
  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'
  
  These 2 messages occur for all of:
  
  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr
  
- In this case the device is a mini-PICe GSM cellular modem - not quite sure 
why it is showing up with a Bluetooth path though!
- --- 
+ In this case the device is a (currently disconnected) cellular phone:
+ 
+ bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)
+ 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  # Include files from /etc/network/interfaces.d:
-  source-directory /etc/network/interfaces.d
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  # Include files from /etc/network/interfaces.d:
+  source-directory /etc/network/interfaces.d
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=false
-  WimaxEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=false
+  WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
-  running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+subscriptions

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

[Desktop-packages] [Bug 1744076] modified.conffile..etc.dbus-1.system.d.nm-ofono.conf.txt

apport information

** Attachment added: "modified.conffile..etc.dbus-1.system.d.nm-ofono.conf.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039044/+files/modified.conffile..etc.dbus-1.system.d.nm-ofono.conf.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] modified.conffile..etc.dbus-1.system.d.nm-dispatcher.conf.txt

apport information

** Attachment added: 
"modified.conffile..etc.dbus-1.system.d.nm-dispatcher.conf.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039043/+files/modified.conffile..etc.dbus-1.system.d.nm-dispatcher.conf.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039045/+files/nmcli-con.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039046/+files/nmcli-dev.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.enp0s29f7u5i6.txt

apport information

** Attachment added: "NetDevice.enp0s29f7u5i6.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039028/+files/NetDevice.enp0s29f7u5i6.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.wlp3s0.txt

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039036/+files/NetDevice.wlp3s0.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039027/+files/JournalErrors.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.lxcbr0.txt

apport information

** Attachment added: "NetDevice.lxcbr0.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039031/+files/NetDevice.lxcbr0.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039023/+files/Dependencies.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1744076/+attachment/5039024/+files/IpAddr.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039037/+files/NetworkManager.conf.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039042/+files/WifiSyslog.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.virbr0.txt

apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039033/+files/NetDevice.virbr0.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] IpRoute.txt

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039025/+files/IpRoute.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.tun0.txt

apport information

** Attachment added: "NetDevice.tun0.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039032/+files/NetDevice.tun0.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.enp2s0.txt

apport information

** Attachment added: "NetDevice.enp2s0.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039029/+files/NetDevice.enp2s0.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039030/+files/NetDevice.lo.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039039/+files/ProcCpuinfoMinimal.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] Re: IPv6 property path is too long

apport information

** Tags added: apport-collected third-party-packages xenial

** Description changed:

  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:
  
  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'
  
  These 2 messages occur for all of:
  
  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr
  
- In this case the device is a mini-PICe GSM cellular modem - not quite
- sure why it is showing up with a Bluetooth path though!
+ In this case the device is a mini-PICe GSM cellular modem - not quite sure 
why it is showing up with a Bluetooth path though!
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  # Include files from /etc/network/interfaces.d:
+  source-directory /etc/network/interfaces.d
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=false
+  WimaxEnabled=true
+ Package: network-manager 1.2.6-0ubuntu0.16.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
+ Tags: third-party-packages xenial
+ Uname: Linux 4.13.0-25-lowlatency x86_64
+ UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
+ UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
+ _MarkForUpload: True
+ mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
+ mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
+  running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1744076/+attachment/5039022/+files/CRDA.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1744076/+attachment/5039041/+files/RfKill.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039026/+files/IwConfig.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.vlan99.txt

apport information

** Attachment added: "NetDevice.vlan99.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039035/+files/NetDevice.vlan99.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] NetDevice.virbr0-nic.txt

apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039034/+files/NetDevice.virbr0-nic.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039040/+files/ProcEnviron.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1744076/+attachment/5039038/+files/PciNetwork.txt

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a (currently disconnected) cellular phone:

  bluez: BT device HTC One M8 (2C:8A:72:15:A8:55) added (DUN NAP)

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-25-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
  UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd 
plugdev root sudo users video wireshark
  _MarkForUpload: True
  mtime.conffile..etc.dbus-1.system.d.nm-dispatcher.conf: 
2015-11-04T09:44:08.042438
  mtime.conffile..etc.dbus-1.system.d.nm-ofono.conf: 2015-11-04T09:44:08.042438
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1744076] [NEW] IPv6 property path is too long

Public bug reported:

On 16.04 there are lots of warnings for paths generated under
/proc/sys/net/ipv6/conf/ of the form:

NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

These 2 messages occur for all of:

accept_ra
accept_ra_defrtr
accept_ra_pinfo
accept_ra_rtr_pref
disable_ipv6
hop_limit
use_tempaddr

In this case the device is a mini-PICe GSM cellular modem - not quite
sure why it is showing up with a Bluetooth path though!

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

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

Title:
  IPv6 property path is too long

Status in network-manager package in Ubuntu:
  New

Bug description:
  On 16.04 there are lots of warnings for paths generated under
  /proc/sys/net/ipv6/conf/ of the form:

  NetworkManager[2043]:  [1516281647.5546] Failed asserting path 
component: "hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55"
  NetworkManager[2043]:   [1516281647.5546] IPv6 property path is too 
long: 
'/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_2C_8A_72_15_A8_55/accept_ra'

  These 2 messages occur for all of:

  accept_ra
  accept_ra_defrtr
  accept_ra_pinfo
  accept_ra_rtr_pref
  disable_ipv6
  hop_limit
  use_tempaddr

  In this case the device is a mini-PICe GSM cellular modem - not quite
  sure why it is showing up with a Bluetooth path though!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744076/+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 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

2018-01-18 Thread Jean-Baptiste Lallement

** Tags added: wayland

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

Status in evince package in Ubuntu:
  New

Bug description:
  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.

  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops
  working for some files.

  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for
  some files. Some files I can click and they open in Evince each time,
  whereas other files will never open in Evince. They open fine in other
  applications and under X.

  When I try to open the file from the command line, I get the following
  error message:

  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

  If I rename the file (e.g. by adding the number "2" to the file name),
  make a copy or move it to another directory, it opens without
  problems. However, after some time the renamed or new file will fail
  to open with the same error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+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 1744026] Re: [bionic] Connection issues are not possible to debug in the UI

2018-01-18 Thread Jean-Baptiste Lallement

** Tags removed: wayland-session

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

Title:
  [bionic] Connection issues are not possible to debug in the UI

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When using a graphical VPN client, one expects a concise error
  message, and/or graphical log viewer (specific to the failed
  connection) to explain what went wrong.

  This does not happen when using the OpenVPN gnome plugin. Instead, I
  have observed two possible behaviors:

  (1) A few seconds after toggling the VPN to "on", (after some timeout)
  the VPN automatically toggles back off, leaving the user with no
  indication about what happened.

  (2) The VPN remains in "on" state but not connected. Instead, it
  reconnects repeatedly (per the auto-reconnect settings), but continues
  to fail repeatedly, without any indication to the user that anything
  went wrong (except for the fact that the VPN never actually connects).

  In either case, the only way to troubleshoot the issue is to do
  something like tail /var/log/syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 12:13:53 2018
  InstallationDate: Installed on 2017-12-20 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1744026/+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 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

2018-01-18 Thread Heinz Dieter

I also experienced increases load on my laptop with an external monitor
in addition to the built-in screen. The load is low initially, then
increases such that the fan turns on. Disconnecting the extra monitor
reduced the load 30s after unplugging for me.

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Even when doing nothing at all, gnome-shell uses around 70% CPU.

  ```
  inxi -t cm
  Processes: CPU: % used - top 5 active
 1: cpu: 68.6% command: gnome-shell pid: 1399
 2: cpu: 50.4% command: Xwayland pid: 1405
 3: cpu: 19.7% command: firefox pid: 3684
 4: cpu: 2.4% command: gnome-shell pid: 1859
 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
  ```

  It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
  ```
  echo $XDG_SESSION_TYPE
  x11
  ```

  While searching I found a recent problem with AMD GPUs, but I'm using an 
Intel GPU
  ```
  glxinfo 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
  GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
  GLX_SGI_make_current_read, GLX_SGI_swap_control
  client glx vendor string: Mesa Project and SGI
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 1536MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.1
  OpenGL vendor string: Intel Open Source Technology Center
  OpenGL renderer string: Mesa DRI Intel(R)

[Desktop-packages] [Bug 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2018-01-18 Thread Audun Gangsto

We're looking forward to getting this implemented, we have many
workstations using this driver and we'd like to use the newer kernels.

Thank you for your good work!

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Incomplete

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1702029] Re: package thunderbird 1:45.8.0+build1-0ubuntu1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/thunderbird/icudt58l.dat » vers

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: thunderbird (Ubuntu)
   Status: New => Invalid

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

Title:
  package thunderbird 1:45.8.0+build1-0ubuntu1 failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./usr/lib/thunderbird/icudt58l.dat » vers «
  /usr/lib/thunderbird/icudt58l.dat.dpkg-new » : fin de fichier ou de
  flux inattendue

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  I can not install the packages by running "apt-get update"

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:45.8.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  appsoft1597 F pulseaudio
  BuildID: 20170327113256
  Channel: Unavailable
  Date: Mon Jul  3 08:39:50 2017
  ErrorMessage: impossible de copier les données extraites pour « 
./usr/lib/thunderbird/icudt58l.dat » vers « 
/usr/lib/thunderbird/icudt58l.dat.dpkg-new » : fin de fichier ou de flux 
inattendue
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-07-02 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.8.1 dev enx0c5b8f279a64 proto static metric 100 
   169.254.0.0/16 dev enx0c5b8f279a64 scope link metric 1000 
   192.168.8.0/24 dev enx0c5b8f279a64 proto kernel scope link src 192.168.8.100 
metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:45.8.0+build1-0ubuntu1 failed to 
install/upgrade: impossible de copier les données extraites pour « 
./usr/lib/thunderbird/icudt58l.dat » vers « 
/usr/lib/thunderbird/icudt58l.dat.dpkg-new » : fin de fichier ou de flux 
inattendue
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PVI Ver. F.08
  dmi.board.name: 1526
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.0D
  dmi.chassis.asset.tag: 23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PVIVer.F.08:bd12/07/2010:svnHewlett-Packard:pnHP620:pvrF.08:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP 620
  dmi.product.version: F.08
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1702029/+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 1690280] Proposed package upload rejected

2018-01-18 Thread Łukasz Zemczak

An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "The changelog is very
confusing, not really fitting the actual changes. The addition of 0018
-Backport-GS_APP_KUDO_SANDBOXED.patch is not mentioned anywhere - is it
required? It needs to be made clear. Also, a lot of changes have been
made to the existing patches and things split out of some of them into a
separate patch, but the changelog doesn't indicate the actual real
reason for that ('part of xxx moved upstream' gives someone without
context no real information). Please adjust the changelog and make sure
that all those patch changes are necessary and re-submit.".

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

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

  [Regression Potential]
  Patch changes the code path used to request installation of all snap 
packages.  Ensure that strict confined snaps continue to be installed with 
correct confinement.

  For example, try installing "ohmygiraffe" via gnome-software, then run
  "snap info ohmygiraffe" from a terminal.  The "installed:" line should
  not include the word "classic".

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1690280/+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 1702393] Re: information!!

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  information!!

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  these are the bugs in my system, I am new in ubuntu for that i need
  help. thanks!!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jul  4 21:15:41 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
  InstallationDate: Installed on 2017-06-26 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80GA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=2b7d12b4-a5b9-4bff-82a5-e1baa1ae40fe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50515STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN26WW:bd07/31/2014:svnLENOVO:pn80GA:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoG40-70:
  dmi.product.name: 80GA
  dmi.product.version: Lenovo G40-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git1706301830.3095cc~gd~z
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1707031930.6158c0~gd~z
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1707031930.6158c0~gd~z
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Tue Jul  4 20:44:22 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702393/+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 1702840] Re: package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: libaccounts-glib (Ubuntu)
   Status: New => Invalid

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

Title:
  package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to
  install/upgrade: подпроцесс новый сценарий pre-removal возвратил код
  ошибки 1

Status in libaccounts-glib package in Ubuntu:
  Invalid

Bug description:
  gnome-terminal have been crashed then I am type new shortcut in
  parameters of gnome-terminal. I have been entering shortcut based on
  Shift-Alt-...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Wed Jul  5 23:34:05 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-06-27 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libaccounts-glib
  Title: package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1702840/+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 1703264] Re: [USB-Audio - USB Device 0x46d:0x819, recording] "chipmunk" noise on logitech webcam input when video also recording

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [USB-Audio - USB Device 0x46d:0x819, recording] "chipmunk" noise on
  logitech webcam input when video also recording

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  On upgrade to 17.04, my webcam stopped properly working, in the sense
  that when video chatting with others, they hear a chipmunk-like noise.
  I used the word chipmunk because I saw this:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/858412

  This issue happens with every video chat application I've tried:
  hangout (chrome), viber, also cheese. I went through some Ubuntu wiki
  page about fixing sound issues which made "cheese" record once ok
  after some force-reset of audio, but not the second time (some crashes
  seemed to happen as well, where the audio was completely disabled
  globally until restart).

  I know the above is not very precise, so here's what I can tell for
  sure: When video chatting, the audio from my logitech webcam (C210)
  sounds like a chipmunk after I upgraded to Ubuntu 17.04. This is with
  the 4.10 kernel. If I boot the same Ubuntu with kernel 4.8 (leftover
  from Ubuntu 16.10), it works correctly!

  The above experiments suggest that there is nothing wrong with my
  config files or package installation. But that it's a regression in
  the kernel/drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sciabaz1860 F pulseaudio
   /dev/snd/controlC1:  sciabaz1860 F pulseaudio
   /dev/snd/controlC0:  sciabaz1860 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Jul  9 18:58:57 2017
  InstallationDate: Installed on 2017-04-23 (76 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:U0x46d0x819 
failed
  Symptom_Card: Webcam C210 - USB Device 0x46d:0x819
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [USB-Audio - USB Device 0x46d:0x819, recording] Sound is distorted
  UpgradeStatus: Upgraded to zesty on 2017-07-05 (4 days ago)
  dmi.bios.date: 02/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B150 PC MATE (MS-7971)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd02/23/2016:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnB150PCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7971
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-23T21:54:23.554412

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1703264/+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 1703443] Re: software center does not install downloaded deb

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

Usually done via dpkg -i or gdebi

** Changed in: software-center-aptdaemon-plugins (Ubuntu)
   Status: New => Invalid

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

Title:
  software center does not install downloaded deb

Status in software-center-aptdaemon-plugins package in Ubuntu:
  Invalid

Bug description:
  I've downloaded google-chrome-stable_current_amd64.deb. Double
  clicking on the deb-file launches the software center. Pressing
  "Install" does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-center-aptdaemon-plugins (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 10 21:24:59 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center-aptdaemon-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center-aptdaemon-plugins/+bug/1703443/+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 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2018-01-18 Thread Marcelo Cerri

I have tested the version 340.104-0ubuntu0.16.04.1 and the DKMS package
successfully builds and loads on kernels 4.13, which was the issue
reported in this bug.

I also have run the ADT tests for the following kernels to ensure
there's no regressions:

- linux-generic 4.4
- linux-hwe 4.10
- linux-hwe-edge 4.11
- linux-hwe-edge 4.13

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

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1703588] Re: package rarian-compat 0.8.1-6 failed to install/upgrade: problemas com dependências - a deixar por configurar

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

Title:
  package rarian-compat 0.8.1-6 failed to install/upgrade: problemas com
  dependências - a deixar por configurar

Status in rarian package in Ubuntu:
  Invalid

Bug description:
  Help me

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: rarian-compat 0.8.1-6
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Tue Jul 11 04:27:59 2017
  ErrorMessage: problemas com dependências - a deixar por configurar
  InstallationDate: Installed on 2017-06-15 (25 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: rarian
  Title: package rarian-compat 0.8.1-6 failed to install/upgrade: problemas com 
dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rarian/+bug/1703588/+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 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2018-01-18 Thread Marcelo Cerri

I have tested the version 304.135-0ubuntu0.16.04.2 and the DKMS package
successfully builds and loads on kernels 4.13, which was the issue
reported in this bug.

I also have run the ADT tests for the following kernels to ensure
there's no regressions:

- linux-generic 4.4
- linux-hwe 4.10
- linux-hwe-edge 4.11
- linux-hwe-edge 4.13
- linux-azure 4.11
- linux-azure-edge 4.13

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

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Incomplete

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-01-18 Thread Jean_Lagouarde

Another problem occurred : serious inconsistencies in the i-node table
causing a crash and a grub-rescue error. Eventually I reverted to ISO
release. Maybe later, I'll try the release 16.04.4...

Material : Acer Aspire 7715Z Ubuntu 16.04 LTS (double boot with Windows
10).

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

Title:
  [regression] compiz crashes after Mesa upgrade

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

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1731296] Re: GNOME Software app not shown as "Ubuntu Software" in Unity 17.10

2018-01-18 Thread Jeremy Bicha

Seb, I'm reopening this bug since it is still not fixed. It is not a
problem for the default Ubuntu session but for every other desktop
session such as Unity. I haven't fixed it yet because there are several
ways to fix it and I wasn't sure which option we want.

** Tags added: artful bionic

** Changed in: gnome-software (Ubuntu)
   Status: Fix Released => 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/1731296

Title:
  GNOME Software app not shown as "Ubuntu Software" in Unity 17.10

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  =
  Install Ubuntu 17.10.
  sudo apt install unity
  Restart your computer.
  On the login screen, click your name then click the gear button and select 
Unity. Log in.
  In the Launcher on the left side of the screen, GNOME Software is shown but 
not Ubuntu Software

  Background Info
  ===
  There is an interesting per-desktop override feature. The primary .desktop is 
installed as /usr/share/applications/org.gnome.Software.desktop . That .desktop 
file can be overriden for the ubuntu desktop by shipping 
/usr/share/applications/Ubuntu/org.gnome.Software.desktop or for the gnome 
desktop by shipping /usr/share/applications/gnome/org.gnome.Software.desktop.

  Until now, this override was only done for the Ubuntu session (which
  in 17.10 is no longer Unity).

  Proposal #1
  ===
  Have the ubuntu-software packaging install the override .desktop to 
/usr/share/unity/applications/ too.

  Proposal #2
  ===
  Have the ubuntu-software packaging install the override .desktop to 
/usr/share/FOO/applications/ where FOO is every desktop session in Ubuntu. Then 
it's up to users and flavors whether they want the Ubuntu or GNOME branding 
based on whether they install the ubuntu-software package.

  Proposal #3
  ===
  Rework the packaging to install the Ubuntu Software .desktop to 
/usr/share/applications/
  Install the GNOME Software .desktop to /usr/share/gnome/applications/ so that 
GNOME (as in the vanilla GNOME session) alone gets the GNOME branding.

  In this case, the ubuntu-software package is not needed any more
  (after a transitional period for upgrades).

  The question is whether there is any reason why someone not using
  vanilla GNOME would want the GNOME branding instead of the Ubuntu
  branding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1731296/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate

2018-01-18 Thread Ted Fry

I've got this issue as well. Automatic login, no requirement for a
password on the screen lock. When resuming from suspend, the password is
required. The user account used for this is not an administrator user.
Fresh install, no changes.

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

Title:
Automatic login still requires user password after suspend/hibernate

Status in gnome-control-center package in Ubuntu:
Confirmed

Bug description:
Description: Ubuntu 17.10
Release: 17.10
gnome-control-center 3.26.2

When I set Ubuntu to automatically login a user the user still has to
enter their password when resuming from a suspended session. The only
option I can find to fix this is to disable the lock-screen
completely, which I don't want to since I still want it to be an
option to manually lock it. Setting Privacy > Screen Lock to off
doesn't affect this behavior at all.

The solution seems to be to use dconf-editor and change
org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got
the solution after asking on askubuntu.com:
https://askubuntu.com/questions/990056/turn-off-requesting-user-
password-after-suspend-17-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1740792/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate

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

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

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

Title:
  Automatic login still requires user password after suspend/hibernate

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  gnome-control-center 3.26.2

  When I set Ubuntu to automatically login a user the user still has to
  enter their password when resuming from a suspended session. The only
  option I can find to fix this is to disable the lock-screen
  completely, which I don't want to since I still want it to be an
  option to manually lock it. Setting Privacy > Screen Lock to off
  doesn't affect this behavior at all.

  The solution seems to be to use dconf-editor and change
  org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got
  the solution after asking on askubuntu.com:
  https://askubuntu.com/questions/990056/turn-off-requesting-user-
  password-after-suspend-17-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1740792/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-01-18 Thread spencer davies

Logged separate bug for this issue per 

https://bugs.launchpad.net/bugs/1744029

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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

Re: [Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-18 Thread Kenneth Loafman

@Olivier,

- When you upgraded to 0.7.15, did you remove the distro's version?

- How much memory do you have?  Is it the same as previous?

- How long of an incremental change list do you have?

- Have you tried making a full backup?


On Wed, Jan 17, 2018 at 2:22 PM, Olivier Crête 
wrote:

> This isn't a duplicate of the previous, I can reproduce the same exact
> stack trace with 0.7.15 when trying to make a backup from deja-dup.
>
>
> Traceback (innermost last):
>   File "/usr/bin/duplicity", line 1559, in 
> with_tempdir(main)
>   File "/usr/bin/duplicity", line 1545, in with_tempdir
> fn()
>   File "/usr/bin/duplicity", line 1394, in main
> do_backup(action)
>   File "/usr/bin/duplicity", line 1526, in do_backup
> check_last_manifest(col_stats)  # not needed for full backup
>   File "/usr/bin/duplicity", line 1228, in check_last_manifest
> last_backup_set.check_manifests()
>   File "/usr/lib64/python2.7/site-packages/duplicity/collections.py",
> line 208, in check_manifests
> remote_manifest = self.get_remote_manifest()
>   File "/usr/lib64/python2.7/site-packages/duplicity/collections.py",
> line 249, in get_remote_manifest
> return manifest.Manifest().from_string(manifest_buffer)
>   File "/usr/lib64/python2.7/site-packages/duplicity/manifest.py", line
> 201, in from_string
> for match in vi_iterator:
>  MemoryError
>
> ** This bug is no longer a duplicate of bug 1720159
>Cannot allocate memory with large manifest file since 0.7.03
>
> --
> You received this bug notification because you are subscribed to
> duplicity in Ubuntu.
> https://bugs.launchpad.net/bugs/1730451
>
> Title:
>   MemoryError while verifying backup
>
> Status in duplicity package in Ubuntu:
>   New
>
> Bug description:
>   While trying to verify a backup (launched from deja-dup), I receive
>   the following error.  My system currently shows 11G of RAM available
>   plus 23G of swap.  Possibly related to #1720159?
>
>   Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1546, in 
>   with_tempdir(main)
> File "/usr/bin/duplicity", line 1540, in with_tempdir
>   fn()
> File "/usr/bin/duplicity", line 1391, in main
>   do_backup(action)
> File "/usr/bin/duplicity", line 1468, in do_backup
>   restore(col_stats)
> File "/usr/bin/duplicity", line 731, in restore
>   restore_get_patched_rop_iter(col_stats)):
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 560, in Write_ROPaths
>   for ropath in rop_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 523, in integrate_patch_iters
>   for patch_seq in collated:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 389, in yield_tuples
>   setrorps(overflow, elems)
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 378, in setrorps
>   elems[i] = iter_list[i].next()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 107, in filter_path_iter
>   for path in path_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 121, in difftar2path_iter
>   tarinfo_list = [tar_iter.next()]
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 339, in next
>   self.set_tarfile()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 333, in set_tarfile
>   self.current_fp = self.fileobj_iter.next()
> File "/usr/bin/duplicity", line 763, in get_fileobj_iter
>   manifest = backup_set.get_manifest()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 250, in get_manifest
>   return self.get_local_manifest()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 224, in get_local_manifest
>   return manifest.Manifest().from_string(manifest_buffer)
> File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line
> 214, in from_string
>   for match in vi_iterator:
>   MemoryError
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: duplicity 0.7.12-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.1
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Mon Nov  6 10:50:12 2017
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2014-08-03 (1190 days ago)
>   InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
>   SourcePackage: duplicity
>   UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/
> 1730451/+subscriptions
>

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

Title:
  MemoryError

[Desktop-packages] [Bug 1744037] [NEW] ubuntu software center-diappeared

2018-01-18 Thread jayantilal chauhan

Public bug reported:

"ubuntu software center", which was installed automatically, is lost. i
can not see at menu, can not get the icon on launcher. i tried  to
search from dashboard also , but failed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jan 18 16:33:03 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2017]
InstallationDate: Installed on 2018-01-15 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61WW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG23116-203
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jan 18 15:50:33 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB OPTICAL MOUSEMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  ubuntu software center-diappeared

Status in xorg package in Ubuntu:
  New

Bug description:
  "ubuntu software center", which was installed automatically, is lost.
  i can not see at menu, can not get the icon on launcher. i tried  to
  search from dashboard also , but failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 18 16:33:03 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2017]
  InstallationDate: Installed on 2018-01-15 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128
  dmi.board.asset.tag: To be filled by

[Desktop-packages] [Bug 1744029] Re: Session logout after screen turned off

2018-01-18 Thread spencer davies

Btw, the attached apport.log captures two crash events -the first was
from manually switching off the monitor; the second was the screen saver
cutting in.

Spencer.

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

Title:
  Session logout after screen turned off

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Duplicate of Bug 1721428

  Logging separate bug for this issue per
  

  Fresh install of 17.10 with all updates applied. Running on HP Compaq
  8200 Elite with HP Z27n monitor attached via displayport and running
  at 2560x1440. Turning off monitor crashes current session.

  Same behavior has been seen on Asrock Deskmini.

  Attached a tar file containing:

  apport.log
  _usr_bin_gnome-shell.1000.crash
  _usr_bin_Xwayland.1000.crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744029/+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 1744029] [NEW] Session logout after screen turned off

2018-01-18 Thread spencer davies

Public bug reported:

Duplicate of Bug 1721428

Logging separate bug for this issue per 

Fresh install of 17.10 with all updates applied. Running on HP Compaq
8200 Elite with HP Z27n monitor attached via displayport and running at
2560x1440. Turning off monitor crashes current session.

Same behavior has been seen on Asrock Deskmini.

Attached a tar file containing:

apport.log
_usr_bin_gnome-shell.1000.crash
_usr_bin_Xwayland.1000.crash

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

** Attachment added: "apport log, gnome-shell crash, Xwayland crash"
   
https://bugs.launchpad.net/bugs/1744029/+attachment/5038815/+files/CrashFiles.tar.gz

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

Title:
  Session logout after screen turned off

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Duplicate of Bug 1721428

  Logging separate bug for this issue per
  

  Fresh install of 17.10 with all updates applied. Running on HP Compaq
  8200 Elite with HP Z27n monitor attached via displayport and running
  at 2560x1440. Turning off monitor crashes current session.

  Same behavior has been seen on Asrock Deskmini.

  Attached a tar file containing:

  apport.log
  _usr_bin_gnome-shell.1000.crash
  _usr_bin_Xwayland.1000.crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744029/+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 1744026] [NEW] [bionic] Connection issues are not possible to debug in the UI

Public bug reported:

When using a graphical VPN client, one expects a concise error message,
and/or graphical log viewer (specific to the failed connection) to
explain what went wrong.

This does not happen when using the OpenVPN gnome plugin. Instead, I
have observed two possible behaviors:

(1) A few seconds after toggling the VPN to "on", (after some timeout)
the VPN automatically toggles back off, leaving the user with no
indication about what happened.

(2) The VPN remains in "on" state but not connected. Instead, it
reconnects repeatedly (per the auto-reconnect settings), but continues
to fail repeatedly, without any indication to the user that anything
went wrong (except for the fact that the VPN never actually connects).

In either case, the only way to troubleshoot the issue is to do
something like tail /var/log/syslog.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 18 12:13:53 2018
InstallationDate: Installed on 2017-12-20 (29 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic wayland-session

** Description changed:

  When using a graphical VPN client, one expects a concise error message,
  and/or graphical log viewer (specific to the failed connection) to
  explain what went wrong.
  
  This does not happen when using the OpenVPN gnome plugin. Instead, I
  have observed two possible behaviors:
  
  (1) A few seconds after toggling the VPN to "on", (after some timeout)
  the VPN automatically toggles back off, leaving the user with no
  indication about what happened.
  
- (2) The VPN start in the "on" state, reconnecting per the auto-reconnect
- settings, but continues to fail repeatedly.
+ (2) The VPN remains in "on" state but not connected. Instead, it
+ reconnects repeatedly (per the auto-reconnect settings), but continues
+ to fail repeatedly, without any indication to the user that anything
+ went wrong (except for the fact that the VPN never actually connects).
  
  In either case, the only way to troubleshoot the issue is to do
  something like tail /var/log/syslog.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 12:13:53 2018
  InstallationDate: Installed on 2017-12-20 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [bionic] Connection issues are not possible to debug in the UI

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When using a graphical VPN client, one expects a concise error
  message, and/or graphical log viewer (specific to the failed
  connection) to explain what went wrong.

  This does not happen when using the OpenVPN gnome plugin. Instead, I
  have observed two possible behaviors:

  (1) A few seconds after toggling the VPN to "on", (after some timeout)
  the VPN automatically toggles back off, leaving the user with no
  indication about what happened.

  (2) The VPN remains in "on" state but not connected. Instead, it
  reconnects repeatedly (per the auto-reconnect settings), but continues
  to fail repeatedly, without any indication to the user that anything
  went wrong (except for the fact that the VPN never actually connects).

  In either case, the only way to troubleshoot the issue is to do
  something like tail /var/log/syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl

[Desktop-packages] [Bug 1744015] Re: [bionic] Locating necessary Network Manager plugins (for example, OpenVPN) is not a good experience

** Summary changed:

- [bionic] Installing network-manager-openvpn is not enough to add OpenVPN 
options to the connection editor
+ [bionic] Locating necessary Network Manager plugins (for example, OpenVPN) is 
not a good experience

** Description changed:

  Steps to reproduce:
  
  (0) Install Bionic desktop
  (1) Observe that only PPTP connection type is available when adding a VPN in 
the UI (using any method).
  (2) Run `sudo apt-get install network-manager-openvpn`.
  (3) Observe that in the top panel "VPN Settings" option, clicking the "+" 
next to "VPN" does not reveal any new VPN type options.
  (4) Run `nm-connection-editor` from the command-line, and observe that not 
only is there no option to add an OpenVPN connection, but in addition, the 
following message is printed on the console:
  
  ** Message: vpn: (openvpn,/usr/lib/NetworkManager/VPN/nm-openvpn-
  service.name) file "libnm-vpn-plugin-openvpn.so" not found. Did you
  install the client package?
+ 
+ Installing `network-manager-openvpn-gnome` seems to do the right thing,
+ but the process of finding what should be installed isn't obvious to the
+ user.

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

Title:
  [bionic] Locating necessary Network Manager plugins (for example,
  OpenVPN) is not a good experience

Status in network-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  (0) Install Bionic desktop
  (1) Observe that only PPTP connection type is available when adding a VPN in 
the UI (using any method).
  (2) Run `sudo apt-get install network-manager-openvpn`.
  (3) Observe that in the top panel "VPN Settings" option, clicking the "+" 
next to "VPN" does not reveal any new VPN type options.
  (4) Run `nm-connection-editor` from the command-line, and observe that not 
only is there no option to add an OpenVPN connection, but in addition, the 
following message is printed on the console:

  ** Message: vpn: (openvpn,/usr/lib/NetworkManager/VPN/nm-openvpn-
  service.name) file "libnm-vpn-plugin-openvpn.so" not found. Did you
  install the client package?

  Installing `network-manager-openvpn-gnome` seems to do the right
  thing, but the process of finding what should be installed isn't
  obvious to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744015/+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 1744015] Re: [bionic] Installing network-manager-openvpn is not enough to add OpenVPN options to the connection editor

IMHO, it would be nice if the Desktop install supported all the VPN
plugins out-of-the-box. Users shouldn't need to hunt for plugin packages
to install.

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

Title:
  [bionic] Locating necessary Network Manager plugins (for example,
  OpenVPN) is not a good experience

Status in network-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  (0) Install Bionic desktop
  (1) Observe that only PPTP connection type is available when adding a VPN in 
the UI (using any method).
  (2) Run `sudo apt-get install network-manager-openvpn`.
  (3) Observe that in the top panel "VPN Settings" option, clicking the "+" 
next to "VPN" does not reveal any new VPN type options.
  (4) Run `nm-connection-editor` from the command-line, and observe that not 
only is there no option to add an OpenVPN connection, but in addition, the 
following message is printed on the console:

  ** Message: vpn: (openvpn,/usr/lib/NetworkManager/VPN/nm-openvpn-
  service.name) file "libnm-vpn-plugin-openvpn.so" not found. Did you
  install the client package?

  Installing `network-manager-openvpn-gnome` seems to do the right
  thing, but the process of finding what should be installed isn't
  obvious to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744015/+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 1744015] [NEW] [bionic] Locating necessary Network Manager plugins (for example, OpenVPN) is not a good experience