[Desktop-packages] [Bug 576669] Re: Document Viewer has no support for common office document file formats

[Jeff Lane ]

** Changed in: evince (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Document Viewer has no support for common office document file formats

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: evince

  Working on creating some new checkbox tests and I've discovered that
  evince, at least as shipped in 10.04 LTS has no support for MS Office
  formats.  I've tried the .xls and .doc files that are shipped in
  /usr/share/example-content.

  In both cases, evince opens with an error that says:

  File type OLE2 compound document storage (application/x-ole-storage)
  is not supported.

  For kicks, I then tried .odt files and got this error:

  File type OpenDocument Text (application/vnd.oasis.opendocument.text)
  is not supported.

  Nor does it support .rtf documents:

  File type RTF document (application/rtf) is not supported.

  Nor does it like ods documents:

  File type OpenDocument Spreadsheet
  (application/vnd.oasis.opendocument.spreadsheet) is not supported

  
  It DOES open odp documents. at least...

  I did not have a pdf file on hand to try...

  BUT, in any case, it does not seem to support ANYTHING right now
  beyond Open Office Presentation files...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Thu May  6 18:07:43 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince

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


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

[Desktop-packages] [Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected

[Jeff Lane ]

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gnome-control-center
   Status: New => Invalid

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

Title:
  Logic needed to disable built in pointing devices when external
  devices are connected

Status in gnome-control-center:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xserver-xorg-input-mouse

  Just about every laptop and netbook these days comes with an built in
  trackpad.  These are often very frustrating as just brushing against
  them, or in some cases even just moving a hand over them can trigger a
  mouse movement or click event.  This is especially frustrating when
  the user is using an external pointing device such as a bluetooth or
  wireless mouse.

  Windows has provided the functionality to disable onboard pointing
  devices when an external mouse is connected/attached, Ubuntu should as
  well.  This is a welcome feature in Windows that saves a lot of
  hassle.  Currently, I have to manually disable my onboard trackpad,
  which leads to issues should my mouse drop connection for whatever
  reason.

  It would be awesome if Ubuntu could recognize that external mouse and
  turn off the trackpad, then turn the trackpad back on when the mouse
  has been detached.

  Just a wishlist item for Natty.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xserver-xorg-input-mouse 1:1.5.0-2build1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  260.19.06  Mon Sep 13 
04:29:19 PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
  Architecture: amd64
  Date: Wed Oct  6 09:18:10 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: Alienware M15x
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-input-mouse
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: Alienware
  dmi.bios.version: A05
  dmi.board.vendor: Alienware
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnAlienware:bvrA05:bd03/11/2010:svnAlienware:pnM15x:pvrA05:rvnAlienware:rn:rvrA05:cvnAlienware:ct8:cvrA05:
  dmi.product.name: M15x
  dmi.product.version: A05
  dmi.sys.vendor: Alienware
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Changed in: gnome-screensaver (Ubuntu Quantal)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Changed in: gnome-screensaver (Ubuntu Wily)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Changed in: gnome-shell (Ubuntu Quantal)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Changed in: gnome-shell (Ubuntu Wily)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Changed in: unity (Ubuntu Wily)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane ]

Release EOL

** Also affects: gnome-screensaver (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: unity (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: gnome-screensaver (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: unity (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: unity (Ubuntu Quantal)
   Status: New => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in gnome-shell source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Quantal:
  Won't Fix
Status in gnome-shell source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in gnome-screensaver source package in Wily:
  Won't Fix
Status in gnome-shell source package in Wily:
  Won't Fix
Status in unity source package in Wily:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in gnome-shell source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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


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

[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'

[Jeff Lane ]

** Tags added: servcert-565

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

Title:
  Traceback during 'ubuntu-drivers list'

Status in Ubuntu Drivers Common:
  Unknown
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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


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

[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'

[Jeff Lane ]

** Bug watch added: github.com/tseliot/ubuntu-drivers-common/issues #78
   https://github.com/tseliot/ubuntu-drivers-common/issues/78

** Also affects: ubuntu-drivers-common via
   https://github.com/tseliot/ubuntu-drivers-common/issues/78
   Importance: Unknown
   Status: Unknown

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

Title:
  Traceback during 'ubuntu-drivers list'

Status in Ubuntu Drivers Common:
  Unknown
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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


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

[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'

[Jeff Lane ]

I made a PR on github to address the exception handling which I think is
the best course here.  Adding a dependency on alsa-utils will result in
adding further unwanted desktop packages on systems where they don't
really belong (anything with Ubuntu Server installed).

Just removing the traceback to clean the output and providing a helpful
error message is sufficient, IMO.

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

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Jeff Lane  (bladernr)

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

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

Title:
  Traceback during 'ubuntu-drivers list'

Status in Ubuntu Drivers Common:
  Unknown
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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


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

[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

https://pastebin.ubuntu.com/p/nzxSG3DMVF/

This remains broken in ubuntu-drivers.  There is absolutely no
difference between what is installed when doing

ubuntu-drivers install

and

ubuntu-drivers install --gpgpu

but significant difference when using

ubuntu-drivers install nvidia:470-server

the first two install exactly the same package set and the latter
installs a much smaller subset.

If you actually expect that the first two install the exact same package
set, why does --gpgpu exist in the first place?  If the expectation is
that --gpgpu means VER-server, then this remains broken since last year.
And if the expectation exists in the middle, then perhaps we need a
--gpgpu-server to install the packages from the last example?

I guess the first question for this bug is "What EXACTLY is expected
when installing using --gpgpu" and then "how do we resolve this bug"

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

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

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

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


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

[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

This is still broken as of 1:0.8.6.3~0.18.04.2

$ ubuntu-drivers --gpgpu devices
This is gpgpu mode
== /sys/devices/pci:c9/:c9:02.0/:ca:00.0/:cb:01.0/:cd:00.0 
==
modalias : pci:v10DEd20B5sv10DEsd1533bc03sc02i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-470 - distro non-free recommended
driver   : xserver-xorg-video-nouveau - distro free builtin

This system has 8x A100 compute GPUs, is running Ubuntu Server, and I
specified --gpgpu because I want the server compute drivers.  But U/D is
still insisting on installing the desktop graphics driver instead

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

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

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

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


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

[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.8.6.3~0.18.04.2
  Candidate: 1:0.8.6.3~0.18.04.2
  Version table:
 *** 1:0.8.6.3~0.18.04.2 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:0.5.2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

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

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

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


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

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

Added Hirsute before I realized it is fixed in Hirsute:

 ubuntu-drivers-common | 1:0.9.0~0.21.04.1   | hirsute-updates | source,
amd64, arm64, armhf, ppc64el, riscv64, s390x

So I just set it to fix-released for H as well, ignore me.

** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
   Status: Won't Fix => Confirmed

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

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

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Won't Fix
Status in ubuntu-drivers-common source package in Hirsute:
  Fix Released

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
    gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
    gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
    language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
    libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 

[Desktop-packages] [Bug 1936679] [NEW] ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

Public bug reported:

Discovered while testing the ubuntu-drivers-common package in -proposed
for bug LP:1898601

While waiting on bionic to deploy for verification, something was
bugging me about Focal verification from the other day so I re-deployed
a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed.
What I missed when verifying the other day was that it actually isn't
installing the -server package on my server in gpgpu mode.  After
chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-
driver-VER-server package. Instead, the version in -proposed is actually
installing nvidia-driver-VER which is incorrect.

Attached is a tarball from a fresh focal install that includes the
output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
--gpgpu debug' after installing the driver.

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

** Attachment added: "ubuntu-drivers-gpgpu-focal-logs.tar"
   
https://bugs.launchpad.net/bugs/1936679/+attachment/5511458/+files/ubuntu-drivers-gpgpu-focal-logs.tar

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

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

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

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


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

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

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

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
    gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
    gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
    language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
    libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
    libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
    libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

Also on Groovy, trying to install the -server package fails:
$ ubuntu-drivers --gpgpu list
This is gpgpu mode
ERROR:root:could not open aplay -l
Traceback (most recent call last):
  File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
nvidia-driver-460-server, (kernel modules provided by 
linux-modules-nvidia-460-server-generic)
nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic)
nvidia-driver-450-server, (kernel modules provided by 
linux-modules-nvidia-450-server-generic)
ubuntu@torchtusk:~$ sudo ubuntu-drivers --gpgpu install 
nvidia-driver-460-server |tee -a install-server.log
This is gpgpu mode
ERROR:root:could not open aplay -l
Traceback (most recent call last):
  File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
No drivers found for installation.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

Groovy:
$ ubuntu-drivers --gpgpu list
This is gpgpu mode
ERROR:root:could not open aplay -l
Traceback (most recent call last):
  File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
nvidia-driver-460-server, (kernel modules provided by 
linux-modules-nvidia-460-server-generic)
nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic)
nvidia-driver-450-server, (kernel modules provided by 
linux-modules-nvidia-450-server-generic)

This is gpgpu mode
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460
  libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460
  libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460
  libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxpm4 libxt6
  linux-image-5.8.0-61-generic linux-modules-5.8.0-61-generic
  linux-modules-nvidia-460-5.8.0-61-generic
  linux-objects-nvidia-460-5.8.0-61-generic
  linux-signatures-nvidia-5.8.0-61-generic mesa-vdpau-drivers
  nvidia-compute-utils-460 nvidia-kernel-common-460 nvidia-kernel-source-460
  nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome
  screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base
  xfonts-encodings xfonts-utils xserver-common xserver-xorg-core
  xserver-xorg-video-nvidia-460
Suggested packages:
  fdutils linux-doc | linux-source-5.8.0 linux-tools
  linux-headers-5.8.0-61-generic libvdpau-va-gl1 xfs | xserver xfonts-100dpi
  | xfonts-75dpi xfonts-scalable
Recommended packages:
  libnvidia-compute-460:i386 libnvidia-decode-460:i386
  libnvidia-encode-460:i386 libnvidia-ifr1-460:i386 libnvidia-fbc1-460:i386
  libnvidia-gl-460:i386
The following NEW packages will be installed:
  libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460
  libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460
  libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460
  libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxpm4 libxt6
  linux-image-5.8.0-61-generic linux-modules-5.8.0-61-generic
  linux-modules-nvidia-460-5.8.0-61-generic linux-modules-nvidia-460-generic
  linux-objects-nvidia-460-5.8.0-61-generic
  linux-signatures-nvidia-5.8.0-61-generic mesa-vdpau-drivers
  nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460
  nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460
  pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core xserver-xorg-video-nvidia-460
0 upgraded, 45 newly installed, 0 to remove and 38 not upgraded.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless 

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

Tested Bionic, and the spirit of this bug is resolved, I think?
However, it couldn't be completely verified since ubuntu-drivers doesn't
install the -server package when --gpgpu is being called:


This is gpgpu mode
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460
  libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460
  libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460
  libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxnvctrl0 libxpm4
  libxt6 mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-kernel-common-460
  nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460
  pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core-hwe-18.04 xserver-xorg-video-nvidia-460
Suggested packages:
  libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver xfs
  | xserver xfonts-100dpi | xfonts-75dpi xfonts-scalable
Recommended packages:
  libnvidia-compute-460:i386 libnvidia-decode-460:i386
  libnvidia-encode-460:i386 libnvidia-ifr1-460:i386 libnvidia-fbc1-460:i386
  libnvidia-gl-460:i386
The following NEW packages will be installed:
  libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460
  libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460
  libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460
  libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxnvctrl0 libxpm4
  libxt6 mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-dkms-460
  nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460
  nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome
  screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base
  xfonts-encodings xfonts-utils xserver-common xserver-xorg-core-hwe-18.04
  xserver-xorg-video-nvidia-460
0 upgraded, 41 newly installed, 0 to remove and 0 not upgraded.

I'm not sure if that is correct.  When I install manually, I look for these:
linux-modules-nvidia-$NVDRV_MJR_VER-server-generic 
nvidia-kernel-common-$NVDRV_MJR_VER-server datacenter-gpu-manager 
libnvidia-nscq-$NVDRV_MJR_VER ca-certificates curl software-properties-common 
nvidia-container-toolkit nvidia-docker2 unzip libgfortran4 swig autotools-dev 
bison gfortran automake libnl-route-3-200 quilt tcl tk libnl-route-3-dev 
chrpath m4 debhelper dpatch libltdl-dev libnl-3-dev graphviz flex autoconf 
sosreport nvidia-utils-$NVDRV_MJR_VER-server 
nvidia-compute-utils-$NVDRV_MJR_VER-server libnvidia-cfg1-$NVDRV_MJR_VER-server

which is the minimal set to run the nVidia GPGPU tests.  What I don't
see being installed on Bionic when I run 'ubuntu-drivers --gpgpu
install' is the -server package.  I haven't run this on Bionic in ages,
but ISTR previously it DID install the -server package.  I'm not sure if
the *compute* packages installed are being pulled in due to a -server
package, or because --gpgpu was called.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

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

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU Request

  [Impact]

  * ubuntu-drivers installs unnecessary packages when using the "--
  gpgpu" argument. Also, it should not depend on alsa-utils, its
  relevant test should.

  [Fix]

  * Passing in "--no-install-recommends" by default with the "--gpgpu"
  argument will solve the problem. Also, moving the alsa-utils
  dependency into the test avoids installing an unneeded dependency on
  servers.

  [Test Case]

  * Install ubuntu-drivers-common from -proposed.

  * Make sure it doesn't pull in alsa-utils.

  * Install the nvidia driver using "sudo ubuntu-drivers install
  --gpgpu", and check that the desktop related dependencies are not
  pulled in.

  [Regression Risk]
  Low, since it changes the amount of dependencies we install on servers.

  

  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
    gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
    gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
    language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
    libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
    libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
    libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 

[Desktop-packages] [Bug 1935070] [NEW] Traceback during 'ubuntu-drivers list'

[Jeff Lane]

Public bug reported:

ubuntu@doubletusk:~$ sudo ubuntu-drivers list
ERROR:root:could not open aplay -l
Traceback (most recent call last):
  File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
  File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.9.0~0.20.04.1
  Candidate: 1:0.9.0~0.20.04.1
  Version table:
 *** 1:0.9.0~0.20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:0.8.6.5~0.20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 1:0.8.1 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
ubuntu@doubletusk:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

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

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

Title:
  Traceback during 'ubuntu-drivers list'

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

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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

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

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

dpuble post

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Focal:
  Triaged
Status in ubuntu-drivers-common source package in Groovy:
  Triaged

Bug description:
  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.  

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
    gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
    gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
    language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
    libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
    libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
    libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
    libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 
libical3 libice6
    libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 
libnvidia-decode-435
    libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 
libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 
libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common 
libpwquality1
    librygel-core-2.6-2 librygel-db-2.6-2 

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

When can this be finally pulled back at least as far as Focal?  We are
not going to be doing nVidia testing on Bionic, so that task can be
dropped I think, unless it's worthwhile, but for Focal - Hirsute, this
would be very helpful to cut down on the amount of stuff being
installed, as well as speed up installation time.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Focal:
  Triaged
Status in ubuntu-drivers-common source package in Groovy:
  Triaged

Bug description:
  +++Update+++
  I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.  

  To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
  -

  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
    evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
    gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
    gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
    gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
    language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
    libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
    libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
    libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
    libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 
libical3 libice6
    libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 

[Desktop-packages] [Bug 1933878] [NEW] Traceback when trying to install drivers as normal user

[Jeff Lane]

Public bug reported:

Forgot to use sudo and discovered an ugly traceback.

ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu install
This is gpgpu mode
Traceback (most recent call last):
  File "/usr/bin/ubuntu-drivers", line 480, in 
greet()
  File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 73, in 
new_func
return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
  File "/usr/bin/ubuntu-drivers", line 399, in install
command_install(config)
  File "/usr/bin/ubuntu-drivers", line 160, in command_install
pm_fd = open('/run/nvidia_runtimepm_supported', 'w')
PermissionError: [Errno 13] Permission denied: '/run/nvidia_runtimepm_supported'

This is because I forgot to use sudo to do the install

ubuntu-drivers can do somethings as a non-privileged driver but other
things (install) requires root escalation.

ubuntu-drivers should either always require root via sudo, or "ubuntu-
drivers install" should do a user check and exit with a simple helpful
message like "You must use sudo when installing drivers".

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-drivers-common 1:0.8.6.3~0.20.10.1
ProcVersionSignature: User Name 5.8.0-60.67-generic 5.8.18
Uname: Linux 5.8.0-60-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 28 20:06:09 2021
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy uec-images

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

Title:
  Traceback when trying to install drivers as normal user

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

Bug description:
  Forgot to use sudo and discovered an ugly traceback.

  ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu install
  This is gpgpu mode
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 480, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
  return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 73, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
  return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 399, in install
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 160, in command_install
  pm_fd = open('/run/nvidia_runtimepm_supported', 'w')
  PermissionError: [Errno 13] Permission denied: 
'/run/nvidia_runtimepm_supported'

  This is because I forgot to use sudo to do the install

  ubuntu-drivers can do somethings as a non-privileged driver but other
  things (install) requires root escalation.

  ubuntu-drivers should either always require root via sudo, or "ubuntu-
  drivers install" should do a user check and exit with a simple helpful
  message like "You must use sudo when installing drivers".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-drivers-common 1:0.8.6.3~0.20.10.1
  ProcVersionSignature: User Name 5.8.0-60.67-generic 5.8.18
  Uname: Linux 5.8.0-60-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun 28 20:06:09 2021
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

** Description changed:

+ +++Update+++
+ I am in a position where I need to run regression testing using the nVidia 
drivers on systems configured for GPU compute.  This bug prevents me from using 
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.  
+ 
+ To resolve this, ubuntu-drivers would need to honor --no-install-recommends 
and not install all those unnecessary desktop environment packages that make no 
sense on a headless server
+ -
+ 
  When I install the packaged nVidia drivers using --gpgpu, I expect that
  I am getting compute related GPGPU drivers.  Instead, I find that on a
  fresh Focal installation of Ubuntu Server, I also get a full desktop
  environment.
  
  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559
  
  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is no
  user activity (even when it's running workloads on the GPGPU, the server
  can still autosuspend).
  
  Additionally, this adds a software stack that causes unnecessary CPU and
  memory usage on a machine that is meant to run headless and devote all
  resources to handling GPGPU compute activities.
  
- This is gpgpu mode
  
- Reading package lists... Done 
  
- Building dependency tree  
   
- Reading state information... Done 
  
- The following additional packages will be installed:  

-   apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
-   evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
-   gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
-   gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
-   gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
-   language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
-   libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
-   libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
-   libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
-   libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 
libical3 libice6
-   libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 
libnvidia-decode-435
-   libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 
libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 
libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common 
libpwquality1
-   librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 
librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 
libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 

[Desktop-packages] [Bug 1920232] Re: ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted packages

[Jeff Lane]

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

** This bug has been marked a duplicate of bug 1898601
   'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, 
including a full desktop environment on Ubuntu Server

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

Title:
  ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted
  packages

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

Bug description:
  when I use --gpgpu mode to install gpgpu drivers using ubuntu-drivers,
  I want ONLY apropriate drivers for GPU compute functions. I do NOT
  need, nor want, desktop packages that I have no need for to be
  installed.

  Start-Date: 2021-03-19  15:43:24
  Commandline: apt-get install -o DPkg::options::=--force-confnew -y 
nvidia-driver-460 linux-modules-nvidia-460-generic
  Requested-By: ubuntu (1000)
  Install: libmpc3:amd64 (1.1.0-1, automatic), gkbd-capplet:amd64 (3.26.1-1, 
automatic), libgoa-backend-1.0-1:amd64 (3.36.0-1ubuntu1, automatic), 
xserver-xorg-input-all:amd64 (1:7.7+19ubuntu14, automatic), hunspel
  l-en-us:amd64 (1:2018.04.16-1, automatic), libqmi-proxy:amd64 (1.24.8-1, 
automatic), network-manager-pptp:amd64 (1.2.8-2, automatic), 
libsoup-gnome2.4-1:amd64 (2.70.0-1, automatic), bluez:amd64 (5.53-0ubuntu3, a
  utomatic), python3-defer:amd64 (1.0.6-2.1, automatic), 
gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, automatic), 
evolution-data-server-common:amd64 (3.36.4-0ubuntu1, automatic), 
libgdata-common:amd64 (0.17
  .12-1, automatic), libwebp6:amd64 (0.6.1-2, automatic), gnome-keyring:amd64 
(3.36.0-1ubuntu1, automatic), libldb2:amd64 (2:2.0.10-0ubuntu0.20.04.2, 
automatic), gnome-settings-daemon-common:amd64 (3.36.1-0ubuntu1
  , automatic), xserver-xorg:amd64 (1:7.7+19ubuntu14, automatic), 
libnl-route-3-200:amd64 (3.4.0-1, automatic), libteamdctl0:amd64 (1.30-1, 
automatic), libcogl20:amd64 (1.22.6-1, automatic), xserver-xorg-video-qxl
  :amd64 (0.1.5+git20200331-1, automatic), python3-cupshelpers:amd64 
(1.5.12-0ubuntu1.1, automatic), python3-ibus-1.0:amd64 (1.5.22-2ubuntu2.1, 
automatic), xserver-xorg-video-vesa:amd64 (1:2.4.0-2, automatic), lib
  openjp2-7:amd64 (2.3.1-1ubuntu4.20.04.1, automatic), libpangoft2-1.0-0:amd64 
(1.44.7-2ubuntu4, automatic), dbus-x11:amd64 (1.12.16-2ubuntu2.1, automatic), 
libaa1:amd64 (1.4p5-46, automatic), libgphoto2-port12:am
  d64 (2.5.25-0ubuntu0.1, automatic), libcrack2:amd64 (2.9.6-3.2, automatic), 
libraw1394-11:amd64 (2.1.2-1, automatic), libieee1284-3:amd64 (0.2.11-13build1, 
automatic), libfontenc1:amd64 (1:1.1.4-0ubuntu1, automa
  tic), libclutter-1.0-0:amd64 (1.26.4+dfsg-1, automatic), libxcb-icccm4:amd64 
(0.4.1-1.1, automatic), gir1.2-nm-1.0:amd64 (1.22.10-1ubuntu2.2, automatic), 
libplist3:amd64 (2.1.0-4build2, automatic), libvte-2.91-0
  :amd64 (0.60.3-0ubuntu1~20.04, automatic), libedataserverui-1.2-2:amd64 
(3.36.4-0ubuntu1, automatic), libcups2:amd64 (2.3.1-9ubuntu1.1, automatic), 
libvulkan1:amd64 (1.2.131.2-1, automatic), libwayland-egl1:amd6
  4 (1.18.0-1, automatic), libgtop2-common:amd64 (2.40.0-2, automatic), 
xserver-xorg-video-nouveau:amd64 (1:1.0.16-1, automatic), 
libclutter-gst-3.0-0:amd64 (3.0.27-1, automatic), 
mobile-broadband-provider-info:am
  d64 (20190618-3, automatic), libdrm-nouveau2:amd64 (2.4.102-1ubuntu1~20.04.1, 
automatic), xserver-xorg-video-amdgpu:amd64 (19.1.0-1, automatic), 
gnome-session-common:amd64 (3.36.0-2ubuntu1, automatic), gir1.2-gt
  k-3.0:amd64 (3.24.20-0ubuntu1, automatic), system-config-printer:amd64 
(1.5.12-0ubuntu1.1, automatic), gir1.2-mutter-6:amd64 
(3.36.7+git20201123-0.20.04.1, automatic), libpcsclite1:amd64 (1.8.26-3, 
automatic), l
  ibxklavier16:amd64 (5.4-4, automatic), gnome-control-center:amd64 
(1:3.36.5-0ubuntu1, automatic), session-migration:amd64 (0.3.5, automatic), 
libgcr-base-3-1:amd64 (3.36.0-2build1, automatic), gir1.2-notify-0.7:
  amd64 (0.7.9-1ubuntu2, automatic), xserver-common:amd64 
(2:1.20.9-2ubuntu1.2~20.04.1, automatic), gir1.2-secret-1:amd64 
(0.20.3-0ubuntu1, automatic), libxcb-xfixes0:amd64 (1.14-2, automatic), 
libwacom-common:amd
  64 (1.3-2ubuntu1, automatic), gir1.2-soup-2.4:amd64 (2.70.0-1, automatic), 
libgtk2.0-bin:amd64 (2.24.32-4ubuntu4, automatic), libnvidia-compute-460:amd64 
(460.39-0ubuntu0.20.04.1, automatic), libegl1:amd64 (1.3.
  2-1~ubuntu0.20.04.1, automatic), gcc-9-base:amd64 (9.3.0-17ubuntu1~20.04, 
automatic), sgml-base:amd64 (1.29.1, automatic), xserver-xorg-core:amd64 
(2:1.20.9-2ubuntu1.2~20.04.1, automatic), libdv4:amd64 (1.0.0-12
  , automatic), libgphoto2-6:amd64 (2.5.25-0ubuntu0.1, automatic), 
gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2, automatic), 
libcogl-path20:amd64 (1.22.6-1, automatic), libgdk-pixbuf2.0-0:amd64 
(2.40.0+dfsg-
  3ubuntu0.2, automatic), sane-utils:amd64 (1.0.29-0ubuntu5.2, 

[Desktop-packages] [Bug 1920225] [NEW] ubuntu-drivers should not run unless user is root

[Jeff Lane]

Public bug reported:

one cannot install drivers unless one is root (or has root priv
escalation via sudo).

For that reason, ubuntu-drivers should not run without a priv check.

ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu autoinstall
This is gpgpu mode
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission 
denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are 
you root?


This shouldn't trigger the apt privilege error, ubuntu-drivers itself should 
check to see if it's running as root and then prompt the user.

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

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

Title:
  ubuntu-drivers should not run unless user is root

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

Bug description:
  one cannot install drivers unless one is root (or has root priv
  escalation via sudo).

  For that reason, ubuntu-drivers should not run without a priv check.

  ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu autoinstall
  This is gpgpu mode
  E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: 
Permission denied)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), 
are you root?

  
  This shouldn't trigger the apt privilege error, ubuntu-drivers itself should 
check to see if it's running as root and then prompt the user.

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

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

[Desktop-packages] [Bug 1920232] [NEW] ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted packages

[Jeff Lane]

Public bug reported:

when I use --gpgpu mode to install gpgpu drivers using ubuntu-drivers, I
want ONLY apropriate drivers for GPU compute functions. I do NOT need,
nor want, desktop packages that I have no need for to be installed.

Start-Date: 2021-03-19  15:43:24
Commandline: apt-get install -o DPkg::options::=--force-confnew -y 
nvidia-driver-460 linux-modules-nvidia-460-generic
Requested-By: ubuntu (1000)
Install: libmpc3:amd64 (1.1.0-1, automatic), gkbd-capplet:amd64 (3.26.1-1, 
automatic), libgoa-backend-1.0-1:amd64 (3.36.0-1ubuntu1, automatic), 
xserver-xorg-input-all:amd64 (1:7.7+19ubuntu14, automatic), hunspel
l-en-us:amd64 (1:2018.04.16-1, automatic), libqmi-proxy:amd64 (1.24.8-1, 
automatic), network-manager-pptp:amd64 (1.2.8-2, automatic), 
libsoup-gnome2.4-1:amd64 (2.70.0-1, automatic), bluez:amd64 (5.53-0ubuntu3, a
utomatic), python3-defer:amd64 (1.0.6-2.1, automatic), 
gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, automatic), 
evolution-data-server-common:amd64 (3.36.4-0ubuntu1, automatic), 
libgdata-common:amd64 (0.17
.12-1, automatic), libwebp6:amd64 (0.6.1-2, automatic), gnome-keyring:amd64 
(3.36.0-1ubuntu1, automatic), libldb2:amd64 (2:2.0.10-0ubuntu0.20.04.2, 
automatic), gnome-settings-daemon-common:amd64 (3.36.1-0ubuntu1
, automatic), xserver-xorg:amd64 (1:7.7+19ubuntu14, automatic), 
libnl-route-3-200:amd64 (3.4.0-1, automatic), libteamdctl0:amd64 (1.30-1, 
automatic), libcogl20:amd64 (1.22.6-1, automatic), xserver-xorg-video-qxl
:amd64 (0.1.5+git20200331-1, automatic), python3-cupshelpers:amd64 
(1.5.12-0ubuntu1.1, automatic), python3-ibus-1.0:amd64 (1.5.22-2ubuntu2.1, 
automatic), xserver-xorg-video-vesa:amd64 (1:2.4.0-2, automatic), lib
openjp2-7:amd64 (2.3.1-1ubuntu4.20.04.1, automatic), libpangoft2-1.0-0:amd64 
(1.44.7-2ubuntu4, automatic), dbus-x11:amd64 (1.12.16-2ubuntu2.1, automatic), 
libaa1:amd64 (1.4p5-46, automatic), libgphoto2-port12:am
d64 (2.5.25-0ubuntu0.1, automatic), libcrack2:amd64 (2.9.6-3.2, automatic), 
libraw1394-11:amd64 (2.1.2-1, automatic), libieee1284-3:amd64 (0.2.11-13build1, 
automatic), libfontenc1:amd64 (1:1.1.4-0ubuntu1, automa
tic), libclutter-1.0-0:amd64 (1.26.4+dfsg-1, automatic), libxcb-icccm4:amd64 
(0.4.1-1.1, automatic), gir1.2-nm-1.0:amd64 (1.22.10-1ubuntu2.2, automatic), 
libplist3:amd64 (2.1.0-4build2, automatic), libvte-2.91-0
:amd64 (0.60.3-0ubuntu1~20.04, automatic), libedataserverui-1.2-2:amd64 
(3.36.4-0ubuntu1, automatic), libcups2:amd64 (2.3.1-9ubuntu1.1, automatic), 
libvulkan1:amd64 (1.2.131.2-1, automatic), libwayland-egl1:amd6
4 (1.18.0-1, automatic), libgtop2-common:amd64 (2.40.0-2, automatic), 
xserver-xorg-video-nouveau:amd64 (1:1.0.16-1, automatic), 
libclutter-gst-3.0-0:amd64 (3.0.27-1, automatic), 
mobile-broadband-provider-info:am
d64 (20190618-3, automatic), libdrm-nouveau2:amd64 (2.4.102-1ubuntu1~20.04.1, 
automatic), xserver-xorg-video-amdgpu:amd64 (19.1.0-1, automatic), 
gnome-session-common:amd64 (3.36.0-2ubuntu1, automatic), gir1.2-gt
k-3.0:amd64 (3.24.20-0ubuntu1, automatic), system-config-printer:amd64 
(1.5.12-0ubuntu1.1, automatic), gir1.2-mutter-6:amd64 
(3.36.7+git20201123-0.20.04.1, automatic), libpcsclite1:amd64 (1.8.26-3, 
automatic), l
ibxklavier16:amd64 (5.4-4, automatic), gnome-control-center:amd64 
(1:3.36.5-0ubuntu1, automatic), session-migration:amd64 (0.3.5, automatic), 
libgcr-base-3-1:amd64 (3.36.0-2build1, automatic), gir1.2-notify-0.7:
amd64 (0.7.9-1ubuntu2, automatic), xserver-common:amd64 
(2:1.20.9-2ubuntu1.2~20.04.1, automatic), gir1.2-secret-1:amd64 
(0.20.3-0ubuntu1, automatic), libxcb-xfixes0:amd64 (1.14-2, automatic), 
libwacom-common:amd
64 (1.3-2ubuntu1, automatic), gir1.2-soup-2.4:amd64 (2.70.0-1, automatic), 
libgtk2.0-bin:amd64 (2.24.32-4ubuntu4, automatic), libnvidia-compute-460:amd64 
(460.39-0ubuntu0.20.04.1, automatic), libegl1:amd64 (1.3.
2-1~ubuntu0.20.04.1, automatic), gcc-9-base:amd64 (9.3.0-17ubuntu1~20.04, 
automatic), sgml-base:amd64 (1.29.1, automatic), xserver-xorg-core:amd64 
(2:1.20.9-2ubuntu1.2~20.04.1, automatic), libdv4:amd64 (1.0.0-12
, automatic), libgphoto2-6:amd64 (2.5.25-0ubuntu0.1, automatic), 
gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2, automatic), 
libcogl-path20:amd64 (1.22.6-1, automatic), libgdk-pixbuf2.0-0:amd64 
(2.40.0+dfsg-
3ubuntu0.2, automatic), sane-utils:amd64 (1.0.29-0ubuntu5.2, automatic), 
gnome-user-docs:amd64 (3.36.2+git20200704-0ubuntu0.1, automatic), 
liblcms2-2:amd64 (2.9-4, automatic), libgoa-1.0-0b:amd64 (3.36.0-1ubuntu
1, automatic), cracklib-runtime:amd64 (2.9.6-3.2, automatic), 
libnvidia-encode-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), 
libegl-mesa0:amd64 (20.2.6-0ubuntu0.20.04.1, automatic), 
libcairo-gobject2:amd64 (1.
16.0-4ubuntu1, automatic), python3-macaroonbakery:amd64 (1.3.1-1, automatic), 
libgoa-1.0-common:amd64 (3.36.0-1ubuntu1, automatic), 
nvidia-kernel-common-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), libcdparan
oia0:amd64 (3.10.2+debian-13, automatic), libfprint-2-2:amd64 

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

+1 Dann's suggestion works great when manually installing the packages
via apt.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

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

Bug description:
  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  
  Reading package lists... Done 
  
  Building dependency tree  
   
  Reading state information... Done 
  
  The following additional packages will be installed:  

apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 
libical3 libice6
libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 
libnvidia-decode-435
libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 
libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 
libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common 
libpwquality1
librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 
librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 
libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 libspeexdsp1 

[Desktop-packages] [Bug 1898601] [NEW] 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[Jeff Lane]

Public bug reported:

When I install the packaged nVidia drivers using --gpgpu, I expect that
I am getting compute related GPGPU drivers.  Instead, I find that on a
fresh Focal installation of Ubuntu Server, I also get a full desktop
environment.

This sets us up nicely for this bug:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

because this pulls in gdm3 and a whole host of unnecessary desktop
packages but does nothing to mitigate the gdm3 propensity to
autosuspend, which makes the server become unresponsive when there is no
user activity (even when it's running workloads on the GPGPU, the server
can still autosuspend).

Additionally, this adds a software stack that causes unnecessary CPU and
memory usage on a machine that is meant to run headless and devote all
resources to handling GPGPU compute activities.

This is gpgpu mode  

Reading package lists... Done   

Building dependency tree
 
Reading state information... Done   

The following additional packages will be installed:
  
  apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez 
bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
  evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
  gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
  gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
  gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
  language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
  libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
  libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
  libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
  libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 
libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common 
libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6
  libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 
libnvidia-decode-435
  libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 
libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 
libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common 
libpwquality1
  librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 
librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 
libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 libspeexdsp1 
libstartup-notification0 libtalloc2
  libtevent0 libupower-glib3 libusbmuxd6 libvdpau1 libwbclient0 
libwebkit2gtk-4.0-37 libwebrtc-audio-processing1 libwhoopsie-preferences0 
libwhoopsie0 libwoff1 libxatracker2 libxaw7 libxcb-icccm4 libxcb-image0 
libxcb-keysyms1
  libxcb-render-util0 libxcb-res0 libxcb-shape0 libxcb-util1 libxcb-xkb1 
libxcb-xv0 libxfont2 libxkbcommon-x11-0 libxkbfile1 libxklavier16 libxmu6 
libxpm4 libxss1 libxt6 libxvmc1 libyelp0 
linux-modules-nvidia-435-5.4.0-48-generic
  mesa-vdpau-drivers 

[Desktop-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

[Jeff Lane]

** Tags added: ubuntu-certified

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

Title:
  [Focal] No HDMI output through thunderbolt docking station

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I can find monitor in display list, but no output from it.
  Also, I can't switch to extend mode, it failed to apply the setting and 
switched back to mirror mode.

  [Steps]
  1. Connect a thunderbolt docking station to thunderbolt port.
  2. Connect HDMI monitor to HDMI port on the docking station.
  3. Switch mode in display setting

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 16:44:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane]

Precise is EOL

** Changed in: unity (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Jeff Lane]

Precise is EOL

** Changed in: gnome-screensaver (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Won't Fix
Status in unity source package in Precise:
  Won't Fix
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1216059] Re: Firefox difficulties with https and IPv6 addresses

[Jeff Lane]

Very old bug, won't fix as it's not a server issue

** Changed in: dell-poweredge
   Status: Confirmed => Invalid

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

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

Title:
  Firefox difficulties with https and IPv6 addresses

Status in The Dell-poweredge project:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When a webserver uses an untrusted certificate (such as a self-signed
  certificate), Firefox encounters multiple bugs trying to use https
  over IPv6. The main upstream bug report is
   but
   also seems
  relevant.

  On Ubuntu 12.04 with firefox package 23.0+build2-0ubuntu0.12.04.1, I
  am not even prompted to add a security exception. I found that with
  Firefox on Ubuntu 10.04, I am prompted to add a security exception but
  have no way to click "add exception" (though we only care about Ubuntu
  12.04 for PowerEdge). This is problematic for Dell because iDRAC and
  CMC ship with self-signed certificates, so there is no way to reach
  the iDRAC or CMC web interface over IPv6 from Firefox. I see the same
  behavior whether entering an IPv6 address (e.g.
  https://[2001:DB8::1]/), when manually specifying the port (e.g.
  https://[2001:DB8::1]:443/) or when specifying a hostname with only an
   record (e.g. https://host-ipv6.example.com/). The same URLs work
  with Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1216059/+subscriptions

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

[Desktop-packages] [Bug 1767185] [NEW] Must click logout twice to log out.

[Jeff Lane]

Public bug reported:

Upgraded from Xenial to Bionic.  Now, when I select Logout from the menu
(on both Unity and Gnome) I must do so twice before the logout is
initiated.

Steps:
click the menu in the upper right corner
click the Logout option
Menu closes
Click the menu again
Click the logout option again
Logout dialog appears

Expected steps: Same as above, without having to repeat myself.

Note I tried this in both Unity and Gnome3 and the results are the same
in both.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session-bin 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Apr 26 15:58:16 2018
InstallationDate: Installed on 2016-02-11 (805 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Must click logout twice to log out.

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Upgraded from Xenial to Bionic.  Now, when I select Logout from the
  menu (on both Unity and Gnome) I must do so twice before the logout is
  initiated.

  Steps:
  click the menu in the upper right corner
  click the Logout option
  Menu closes
  Click the menu again
  Click the logout option again
  Logout dialog appears

  Expected steps: Same as above, without having to repeat myself.

  Note I tried this in both Unity and Gnome3 and the results are the
  same in both.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:58:16 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Jeff Lane]

FWIW, it's entirely possible I had other issues that just also included
this one, or just exposed this one where I may not have seen it
otherwise.  This just happened to be the only one that Apport was able
to create and submit.

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, 

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Jeff Lane]

@seb, per discussion via IRC, here are my logs from /var/log/dist-
upgrade (upgrade started last night and finally wrapped up this morning
after a lot of coffee and swearing).

To answer the questions:

I started off with 'do-release-upgrade -d' last night and ended up this
morning with a reboot into rescue mode and a lot of 'apt-get -f
install', 'dpkg --reconfigure -a' and finally an 'apt-get dist-upgrade'
(or was it a -f install again?) to get the remaining held 2400+ packages
updated.

NOW I believe I'm finally updated to Bionic and running again.

Also, will asked if I had manually modified anything in
/etc/apt/sources.list and the answer is no, all that was handled by the
upgrader.

** Attachment added: "xenial-bionic-upgrade-logs.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127748/+files/xenial-bionic-upgrade-logs.tgz

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  

[Desktop-packages] [Bug 1767145] [NEW] Power status says my battery is fully charged. I'm on a desktop. I have no battery

[Jeff Lane]

Public bug reported:

Just upgraded to bionic.  Gnome says my battery is fully charged.  ONly
thing is, this isn't a laptop.  I have no batter.  It is impossible for
my battery to be fully charged, since it doesn't exist.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-power-manager 3.26.0-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 26 11:38:12 2018
InstallationDate: Installed on 2016-02-11 (804 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "See my non-existent battery's status."
   
https://bugs.launchpad.net/bugs/1767145/+attachment/5127725/+files/gnome-power-panel.png

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

Title:
  Power status says my battery is fully charged. I'm on a desktop. I
  have no battery

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

Bug description:
  Just upgraded to bionic.  Gnome says my battery is fully charged.
  ONly thing is, this isn't a laptop.  I have no batter.  It is
  impossible for my battery to be fully charged, since it doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 11:38:12 2018
  InstallationDate: Installed on 2016-02-11 (804 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Jeff Lane]

FWIW, this error (my bug was marked a duplicate) completely broke my
Xenial - Bionic upgrade, leaving me with a nearly unbeatable system.  I
had to boot into Rescue Mode and do a lot of ctrl-C ing to get around
this, and once I thought it had finally installed all the bionic
packages, I rebooted into the OS proper, and STILL found it hadn't
actually upgraded so I had to run 'apt-get -f install' again to finish
the other 2400+ package updates.

I spent most of my morning just trying to get back to a bootable system
that was only half-way upgraded (lsb-release told me I was in 18.04,
name -a said I was still on 4.13 from 16.04.4, and apt said I still had
2400+ packages to update).

If I was not an experienced user who knew roughly how to manually kick
this stuff to get around broken package updates, I'd have been
considerably more upset than I already am.

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Jeff Lane]

Grr... autocorrect on OSX while I wait for Ubuntu to work again (finish
upgrading).  That should have said "leaving me with a nearly unbootable
system."

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  

[Desktop-packages] [Bug 1767129] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Jeff Lane]

Public bug reported:

I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT
of broken package upgrades.  I've finally managed to get through a lot
of them and this one prompted apart once I had rebooted into a rescue
shell and tried to run 'apt-get -f install'

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 16:43:42 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-02-11 (804 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  I am desperately trying to fix a Xenial to Bionic upgrade that had a
  LOT of broken package upgrades.  I've finally managed to get through a
  lot of them and this one prompted apart once I had rebooted into a
  rescue shell and tried to run 'apt-get -f install'

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 16:43:42 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-11 (804 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647334] JournalErrors.txt

[Jeff Lane]

apport information

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

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1647334] ProcEnviron.txt

[Jeff Lane]

apport information

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

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1647334] Dependencies.txt

[Jeff Lane]

apport information

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

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1647334] [NEW] datetime does not autoupdate clock based on geolocation

[Jeff Lane]

Public bug reported:

See attached screenshots.

I am currently in Spain, and unity-control-center datetime is configurd
to automatically update the timezone based on IP geolocation.

This does not work (and honestly hasn't worked for quite some time, well
before 16.04).

In one screenshot, you can see that my timezone is set as New York, and
the "Automatically from the Internet" button is selected for "Set the
time".

In the other screenshot, you can clearly see that my geolocation shows
that I am in Spain, but the time has NOT updated to reflect that I'm on
a different European timezone.

This has never worked in Ubuntu that I can recall, I always have to
manually change the location.

Expected Behaviour:

Timezone is updated automatically whenever I am connected to the internet in a 
different timezone.
--- 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-10-21 (410 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
NonfreeKernelModules: wl
Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Tags:  xenial
Uname: Linux 4.4.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected xenial

** Attachment added: "timedate-settings.png"
   
https://bugs.launchpad.net/bugs/1647334/+attachment/4787539/+files/timedate-settings.png

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1647334] Re: datetime does not autoupdate clock based on geolocation

[Jeff Lane]

This screenshot shows the geolocation data for where I currently sit

** Attachment added: "geolocation-data.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+attachment/4787540/+files/geolocation-data.png

** Tags added: apport-collected xenial

** Description changed:

  See attached screenshots.
  
  I am currently in Spain, and unity-control-center datetime is configurd
  to automatically update the timezone based on IP geolocation.
  
  This does not work (and honestly hasn't worked for quite some time, well
  before 16.04).
  
  In one screenshot, you can see that my timezone is set as New York, and
  the "Automatically from the Internet" button is selected for "Set the
  time".
  
  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm on
  a different European timezone.
  
  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.
  
  Expected Behaviour:
  
- Timezone is updated automatically whenever I am connected to the
- internet in a different timezone.
+ Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2015-10-21 (410 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
+ NonfreeKernelModules: wl
+ Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
+ Tags:  xenial
+ Uname: Linux 4.4.0-51-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1632373] ProcEnviron.txt

[Jeff Lane]

apport information

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

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

Title:
  Time settings do not automatically update

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  In timedate settings, I have it configured to "Set the time  ___
  Automatically from the internet"

  However, this does not work, I always have to manually change the
  timezone whenever I travel.

  This is a bit annoying, as I do expect this to just work.

  I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (355 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1632373/+subscriptions

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

[Desktop-packages] [Bug 1632373] Dependencies.txt

[Jeff Lane]

apport information

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

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

Title:
  Time settings do not automatically update

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  In timedate settings, I have it configured to "Set the time  ___
  Automatically from the internet"

  However, this does not work, I always have to manually change the
  timezone whenever I travel.

  This is a bit annoying, as I do expect this to just work.

  I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (355 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1632373/+subscriptions

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

[Desktop-packages] [Bug 1632373] JournalErrors.txt

[Jeff Lane]

apport information

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

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

Title:
  Time settings do not automatically update

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  In timedate settings, I have it configured to "Set the time  ___
  Automatically from the internet"

  However, this does not work, I always have to manually change the
  timezone whenever I travel.

  This is a bit annoying, as I do expect this to just work.

  I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (355 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1632373/+subscriptions

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

[Desktop-packages] [Bug 1632373] [NEW] Time settings do not automatically update

[Jeff Lane]

Public bug reported:

In timedate settings, I have it configured to "Set the time  ___
Automatically from the internet"

However, this does not work, I always have to manually change the
timezone whenever I travel.

This is a bit annoying, as I do expect this to just work.

I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
--- 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-10-21 (355 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
NonfreeKernelModules: wl
Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Tags:  xenial
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected xenial

** Tags added: apport-collected xenial

** Description changed:

  In timedate settings, I have it configured to "Set the time  ___
  Automatically from the internet"
  
  However, this does not work, I always have to manually change the
  timezone whenever I travel.
  
  This is a bit annoying, as I do expect this to just work.
  
- I do, however, expect maybe some short delay in updating TZ settings
- when I travel, but it's sat for several days before on the wrong
- timezine becuase it didn't automatically update.  In this most recent
- case, I felw to the west coast and had to manually set the time to
- "Seattle".  When I flew back to the East Coast, I had to set it manually
- to "NYC" after several hours as it had not automatically updated to the
- correct timezone.
+ I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2015-10-21 (355 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
+ NonfreeKernelModules: wl
+ Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
+ Tags:  xenial
+ Uname: Linux 4.4.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Time settings do not automatically update

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  In timedate settings, I have it configured to "Set the time  ___
  Automatically from the internet"

  However, this does not work, I always have to manually change the
  timezone whenever I travel.

  This is a bit annoying, as I do expect this to just work.

  I do, however, expect maybe some short delay in updating TZ settings when I 
travel, but it's sat for several days before on the wrong timezine becuase it 
didn't automatically update.  In this most recent case, I felw to the west 
coast and had to manually set the time to "Seattle".  When I flew back to the 
East Coast, I had to set it manually to "NYC" after several hours as it had not 
automatically updated to the correct timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (355 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage 

[Desktop-packages] [Bug 1576364] Re: NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

Gonna set this to invalid.  After the third or fourth reboot, NM started
loading on it's own and I no longer needed to manually do so.  I don't
know why, but I'm unable to recreate the original fail state now :(

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetDevice.virbr0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650576/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetDevice.lo.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650574/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] nmcli-dev.txt

[Jeff Lane]

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650585/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] JournalErrors.txt

[Jeff Lane]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650573/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] Dependencies.txt

[Jeff Lane]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650569/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] IpRoute.txt

[Jeff Lane]

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650571/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] WifiSyslog.txt

[Jeff Lane]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650583/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] IwConfig.txt

[Jeff Lane]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650572/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] ProcEnviron.txt

[Jeff Lane]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650581/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] RfKill.txt

[Jeff Lane]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650582/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] PciNetwork.txt

[Jeff Lane]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650580/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetDevice.tun0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.tun0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650575/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] nmcli-con.txt

[Jeff Lane]

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650584/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetDevice.wlp3s0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650578/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetDevice.virbr0-nic.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650577/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] NetworkManager.conf.txt

[Jeff Lane]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650579/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] IpAddr.txt

[Jeff Lane]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650570/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] Re: NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

apport information

** Tags added: apport-collected xenial

** Description changed:

  Running Xenial on a Macbook Air.  This was running Wily and was upgraded
  to Xenial using do-release-upgrade.  Network Manager works, and can
  manage NICs, WiFI and VPNs that I have configured, however, the service
  no longer starts on boot like it did under Wily and like it should by
  default in any case.
  
  I have to manually start NetworkManager after each reboot using "service
  NetworkManager start".
  
  After that step, network is restored and works as it should.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2015-10-21 (189 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
+ NonfreeKernelModules: wl
+ Package: network-manager 1.1.93-0ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ Tags:  xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650568/+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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1576364] [NEW] NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

Public bug reported:

Running Xenial on a Macbook Air.  This was running Wily and was upgraded
to Xenial using do-release-upgrade.  Network Manager works, and can
manage NICs, WiFI and VPNs that I have configured, however, the service
no longer starts on boot like it did under Wily and like it should by
default in any case.

I have to manually start NetworkManager after each reboot using "service
NetworkManager start".

After that step, network is restored and works as it should.

** 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/1576364

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

H... ok.  I didn't realize there was a second pulseaudio config.

I have no idea how it got there, nor where it came from, and I do not
recall ever setting it, but sure enough:

### Make some devices default
#set-default-sink output
set-default-source 2
set-source-mute 2 0

So this is likely cruft left over from an older version... to build this
machine, I did a fresh Xenial install and then installed a backup of
/home/$USER via rsync.

However, I do not ever remember configuring this file at any point in
the past, AND this worked just fine in Trusty, and also worked fine in
Xenial until it stopped working, then it started working, then it
stopped working.

Is there some sort of race condition where ~/.pulse/default.pa may or
may not be the default.pa Pulse uses?

Anyway, I'm removing the file and restarting to see what happens.

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

et viola, it's working.

Still, no idea where that second, edited version came from :/

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

On Tue, Mar 1, 2016 at 8:10 AM, David Henningsson
<1547...@bugs.launchpad.net> wrote:
> You haven't changed any configuration files (e g such as
> /etc/pulse/default.pa ) so they now reference a hard-coded "source #2",
> have you?

I have only changed the autospawn line in /etc/pulse/client.conf:

; autospawn = no

That at least stopped it from continuously respawning and flooding
syslog, until I rebooted, apparently that doesn't apply when it starts
as a daemon at boot time.

> If not, could you reproduce this with a higher log level (e g by
> following https://wiki.ubuntu.com/PulseAudio/Log ) and see if you get
> more information out of this error? Thanks.

Log attached... it died pretty quickly.


** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => New

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/bugs/1547585/+attachment/4586622/+files/pulseverbose.log

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1551273] [NEW] Software Center only provides a subset of software available in repos

[Jeff Lane]

Public bug reported:

I needed to re-install recordmydesktop for some debug usage and opened
up the Software Center in Xenial and attempted to do so.

Searches for 'recordmydesktop' in the software-center returned nothing,
as the screenshot shows.

However, it's plainly available if you do an apt-cache search:

bladernr@galactica:~$ apt-cache search recordmydesktop
gtk-recordmydesktop - Graphical frontend for recordMyDesktop screencast tool
recordmydesktop - Captures audio-video data of a Linux desktop session

So it seems that the software-center is not aware of some things (maybe
only in Universe?)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-center (not installed)
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 29 10:09:46 2016
InstallationDate: Installed on 2016-02-11 (17 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "software-center.png"
   
https://bugs.launchpad.net/bugs/1551273/+attachment/4584450/+files/software-center.png

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

Title:
  Software Center only provides a subset of software available in repos

Status in software-center package in Ubuntu:
  New

Bug description:
  I needed to re-install recordmydesktop for some debug usage and opened
  up the Software Center in Xenial and attempted to do so.

  Searches for 'recordmydesktop' in the software-center returned
  nothing, as the screenshot shows.

  However, it's plainly available if you do an apt-cache search:

  bladernr@galactica:~$ apt-cache search recordmydesktop
  gtk-recordmydesktop - Graphical frontend for recordMyDesktop screencast tool
  recordmydesktop - Captures audio-video data of a Linux desktop session

  So it seems that the software-center is not aware of some things
  (maybe only in Universe?)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 29 10:09:46 2016
  InstallationDate: Installed on 2016-02-11 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1551273/+subscriptions

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

** Summary changed:

- Pulseaudio stopped working but sound still comes out LOUDLY
+ Pulseaudio stopped working but sound still works at the low level (can be 
controlled with alsamixer)

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Syslog is flooded with this series of messages

Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: Source 2 does 
not exist.
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: No sink found 
by this name or index.
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: Failed to 
initialize daemon.
Feb 19 11:42:07 galactica pulseaudio[22206]: [pulseaudio] main.c: Daemon 
startup failed.

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547651] [NEW] Network Manager shows no VPNs after reboot

[Jeff Lane]

Public bug reported:

After updating packages, I rebooted the system to load the new libc.  ON
reboot I discovered after login that I was unable to connect any
configured VPNs because NetworkManager showed no VPNs.

I eventually figured out that clicking "Enable Networking" to disable
and re-enable networking caused NetMan to reload and THEN I could see my
VPNs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu9
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 19 13:54:07 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-11 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
IpRoute:
 default via 192.168.0.1 dev enp2s0  proto static  metric 100 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
 192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.104  metric 
100 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Network Manager shows no VPNs after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  After updating packages, I rebooted the system to load the new libc.
  ON reboot I discovered after login that I was unable to connect any
  configured VPNs because NetworkManager showed no VPNs.

  I eventually figured out that clicking "Enable Networking" to disable
  and re-enable networking caused NetMan to reload and THEN I could see
  my VPNs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 13:54:07 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-11 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.104  
metric 100 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1547585] [NEW] Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Public bug reported:

Not sure if it was an update or what that broke, but I suddenly have no
ability to control sound.

Sound settings no longer show any output devices and syslog is flooded
with pulseaudio messages.

Haven't tried a reboot, that's next.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
 /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
 /dev/snd/controlC0:  bladernr   2773 F chrome
 /dev/snd/timer:  bladernr   2773 f chrome
CurrentDesktop: Unity
Date: Fri Feb 19 11:10:11 2016
InstallationDate: Installed on 2016-02-11 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170MX-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170MX-Gaming 5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
   Importance: Critical => High

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Rebooted system and still no audio devices, but I am listening to a
video play RIGHT NOW, despite the fact that pulseaudio thinks I have no
audio devices now.

This was working until I did a dist-upgrade earlier (maybe yesterday or
today).

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

I AM able to control sound levels with alsamixer directly, FWIW.

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

This may be related to bug #1547589

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1547589] [NEW] rtkit-daemon flooding syslog

[Jeff Lane]

Public bug reported:

rtkit is flooding syslog with the following:

Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.

This may be related to but #1547585

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rtkit 0.11-4
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 19 11:42:58 2016
InstallationDate: Installed on 2016-02-11 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: rtkit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  rtkit-daemon flooding syslog

Status in rtkit package in Ubuntu:
  New

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1545905] [NEW] PyGIWrning messages when running ubuntu-bug

[Jeff Lane]

Public bug reported:

Whenever I run ubuntu-bug on this newly installed and updated Xenial
destktop system, I get the following PyGIWarning messages dumped to
console:

bladernr@critical-maas:~$ ubuntu-bug apport
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

These should be cleaned up, it looks bad when your bug reporting tool
has bugs like this.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportLog:
 
ApportVersion: 2.20-0ubuntu2
Architecture: amd64
CrashReports: 640:108:116:1558842:2016-02-13 15:22:29.722635241 
-0500:2016-02-13 15:22:27.726586970 
-0500:/var/crash/_usr_lib_unity-settings-daemon_unity-settings-daemon.108.crash
CurrentDesktop: Unity
Date: Mon Feb 15 21:05:35 2016
InstallationDate: Installed on 2016-02-12 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  PyGIWrning messages when running ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  Whenever I run ubuntu-bug on this newly installed and updated Xenial
  destktop system, I get the following PyGIWarning messages dumped to
  console:

  bladernr@critical-maas:~$ ubuntu-bug apport
  sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
  sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. 
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

  These should be cleaned up, it looks bad when your bug reporting tool
  has bugs like this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CrashReports: 640:108:116:1558842:2016-02-13 15:22:29.722635241 
-0500:2016-02-13 15:22:27.726586970 
-0500:/var/crash/_usr_lib_unity-settings-daemon_unity-settings-daemon.108.crash
  CurrentDesktop: Unity
  Date: Mon Feb 15 21:05:35 2016
  InstallationDate: Installed on 2016-02-12 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1545904] [NEW] Several regex warnings when installing latest postgres update

[Jeff Lane]

Public bug reported:

Noticed during an update of PostgreSQL via apt-get this evening:

Setting up postgresql-9.5 (9.5.0-3) ...
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/(?https://bugs.launchpad.net/bugs/1545904

Title:
  Several regex warnings when installing latest postgres update

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Noticed during an update of PostgreSQL via apt-get this evening:

  Setting up postgresql-9.5 (9.5.0-3) ...
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1545904/+subscriptions

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

[Desktop-packages] [Bug 1540591] [NEW] fontconfig breaks Trusty - Xenial upgrade

[Jeff Lane]

Public bug reported:

Attempting to upgrade a fully updated 14.04.3 system to Xenial using the
do-release-upgrade tool.

The upgrade proceeds until it attempts to install fontconfig.  This
fails and causes a cascading set of failures for 160+ more packages
resulting in a system that boots, and has console access, but no Unity,
and other things that either fail to work or only work halfway.

Attempts after the failed upgrade to fix the issues via "apt-get -f
install" fail with the same errors as seen during the upgrade.

Here's the apt term log showing the errors, starting with fontconfig:

http://paste.ubuntu.com/14852379/

And here's the contents of fontconfig.log as suggested by trying to
manually install fontconfig vai "apt-get install fontconfig"

/usr/share/fonts: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11/Type1: caching, new cache contents: 9 fonts, 0 dirs
/usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/X11/encodings/large: caching, new cache contents: 0 fonts, 0 
dirs
/usr/share/fonts/X11/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/share/fonts/X11/util: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap: caching, new cache contents: 0 fonts, 5 dirs
/usr/share/fonts/cmap/adobe-cns1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-gb1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan2: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-korea1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/truetype: caching, new cache contents: 1 fonts, 19 dirs
/usr/share/fonts/truetype/abyssinica: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/dejavu: caching, new cache contents: 6 fonts, 0 dirs
/usr/share/fonts/truetype/droid: caching, new cache contents: 18 fonts, 0 dirs
/usr/share/fonts/truetype/freefont: caching, new cache contents: 12 fonts, 0 
dirs
/usr/share/fonts/truetype/kacst: caching, new cache contents: 15 fonts, 0 dirs
/usr/share/fonts/truetype/kacst-one: caching, new cache contents: 2 fonts, 0 
dirs
/usr/share/fonts/truetype/lao: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/liberation: caching, new cache contents: 16 fonts, 0 
dirs
/usr/share/fonts/truetype/nanum: caching, new cache contents: 6 fonts, 0 dirs
/usr/share/fonts/truetype/openoffice: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/padauk: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/truetype/sinhala: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/takao-gothic: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/tibetan-machine: caching, new cache contents: 1 
fonts, 0 dirs
/usr/share/fonts/truetype/tlwg: caching, new cache contents: 54 fonts, 0 dirs
/usr/share/fonts/truetype/ttf-indic-fonts-core: caching, new cache contents: 17 
fonts, 0 dirs
/usr/share/fonts/truetype/ttf-khmeros-core: caching, new cache contents: 2 
fonts, 0 dirs
/usr/share/fonts/truetype/ttf-punjabi-fonts: caching, new cache contents: 2 
fonts, 0 dirs
/usr/share/fonts/truetype/ubuntu-font-family: caching, new cache contents: 13 
fonts, 0 dirs
/usr/share/fonts/type1: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/type1/gsfonts: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/type1/mathml: caching, new cache contents: 1 fonts, 0 dirs
/usr/local/share/fonts: caching, new cache contents: 0 fonts, 0 dirs
/.local/share/fonts: skipping, no such directory
Re-scanning /usr/share/fonts: fc-cache: symbol lookup error: fc-cache: 
undefined symbol: FcDirCacheRescan

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

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

Title:
  fontconfig breaks Trusty - Xenial upgrade

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Attempting to upgrade a fully updated 14.04.3 system to Xenial using
  the do-release-upgrade tool.

  The upgrade proceeds until it attempts to install fontconfig.  This
  fails and causes a cascading set of failures for 160+ more packages
  resulting in a system that boots, and has console access, but no
  Unity, and other things that either fail to work or only work halfway.

  Attempts after the failed upgrade to fix the issues via "apt-get -f
  install" fail with the same errors as seen during the upgrade.

  Here's the apt term log showing the errors, starting with fontconfig:

  http://paste.ubuntu.com/14852379/

  And here's the contents of fontconfig.log as suggested by trying to
  manually install fontconfig vai "apt-get install fontconfig"

  

[Desktop-packages] [Bug 1515354] [NEW] netman icon does not show VPN status when VPN connected automatically at boot time

[Jeff Lane]

Public bug reported:

I have VPNs configured in Network Manager, one of which is a default
work VPN.  That VPN is configured to connect whenever the network
connection is active on my desktop, thus every time I reboot, the
connection for eth0 is active and the VPN connects automatically.

I've noticed, however, that the NM icon in the tray does not show this
connected status when the automatic connection is made.

Ordinarily, if I manually connect to a VPN, the status icon changes from
two arrows (this is a wired connection) to two arrows with a padlock
indicating a secured VPN connection.

When I boot this system and the VPN connection is established
automatically, however, the icon does not display the padlock, BUT if
you look at NM/VPN Connections/ you can clearly see the connection
marked as active by the check mark next to it.

If I boot the machine and the NM icon is in this state, I can manually
shut down and restart the VPN link and the icon changes to show the VPN
connection as it should.

The screen shot attached shows the icon after a boot, as well as the VPN
connections list with the currently active VPN highlighted by the
checkmark.

Additionally, If I manually disconnect the wired connection and
reconnect it, again, the icon shows the secure established VPN
connection.


Expected Behaviour:

The NM status icon should ALWAYS show the padlock when a VPN connection
is made, regardless of whether it is automatic or not.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 11 13:16:05 2015
IfupdownConfig:
 auto lo
 iface lo inet loopback
 
 iface eth1:foo inet dhcp
InstallationDate: Installed on 2012-03-15 (1335 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-04-20 (569 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-07-30T16:31:50.821388
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth1   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug third-party-packages trusty

** Attachment added: "vpn-status.jpg"
   
https://bugs.launchpad.net/bugs/1515354/+attachment/4517104/+files/vpn-status.jpg

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

Title:
  netman icon does not show VPN status when VPN connected automatically
  at boot time

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have VPNs configured in Network Manager, one of which is a default
  work VPN.  That VPN is configured to connect whenever the network
  connection is active on my desktop, thus every time I reboot, the
  connection for eth0 is active and the VPN connects automatically.

  I've noticed, however, that the NM icon in the tray does not show this
  connected status when the automatic connection is made.

  Ordinarily, if I manually connect to a VPN, the status icon changes
  from two arrows (this is a wired connection) to two arrows with a
  padlock indicating a secured VPN connection.

  When I boot this system and the VPN connection is established
  automatically, however, the icon does not display the padlock, BUT if
  you look at NM/VPN Connections/ you can clearly see the connection
  marked as active by the check mark next to it.

  If I boot the machine and the NM icon is in this state, I can manually
  shut down and restart the VPN link and the icon changes to show the
  VPN connection as it should.

  The screen shot attached shows the icon after a boot, as well as the
  VPN connections list with the currently active VPN highlighted by the
  checkmark.

  Additionally, If I manually disconnect the wired connection and
  reconnect it, again, the icon shows the secure established VPN
  connection.

  
  Expected Behaviour:

  The NM status icon should ALWAYS show the padlock when a VPN
  connection is made, regardless of whether it is automatic or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 

[Desktop-packages] [Bug 1510091] Re: ubuntu-bug in wily fails to open a bug page when reporting bugs

[Jeff Lane]

Accidentally added the Ubuntu apport package... apparently xdg-utils
doesn't track bugs here... now what?

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

** No longer affects: apport (Ubuntu)

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

Title:
  ubuntu-bug in wily fails to open a bug page when reporting bugs

Status in Apport:
  New

Bug description:
  Fresh install of Wily.  Attempting to file a bug against Unity using
  ubuntu-bug.

  ubuntu-bug prompts me with the expected prompts for a Unity/Gfx bug
  and then says it will open a new window to complete the bug process.

  Normally, this would open a window to a launchpad bug in progress so I
  can update the bug with final details before completing the bug filing
  process.

  Instead, it opens a new browser window with NOTHING in the address
  bar.  Since Ubuntu-Bug does NOT give me the URL in the console where
  it was launched, I have NO way of completing any bugs using ubuntu-
  bug.

  I attempted to file a bug twice with ubuntu-bug and failed both times
  as it does NOT actually open a window that opens the bug's page on
  launchpad:

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

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

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

[Desktop-packages] [Bug 1508719] [NEW] 15.10 does not offer broadcom drivers for BCM4360 wireless on macbook air

[Jeff Lane]

Public bug reported:

Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
unable to use the wireless device.  The wifi is a broadcom BCM4360 based
device on a late 2013 Macbook Air.

Wily wants to load b43 and dmesg only shows this:

b43-phy0: Broadcom 4360 WLAN found (core revision 42)
Broadcom 43xx driver loaded [ Features: PNL ]

Netman does not list the wifi device at all.

lspci says:

03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
kernel driver in use: bcma-pci-bridge

If I use ubuntu-drivers, it also does not list the broadcom device.

I had to manually install bcmwl-kernel-source from Restricted via apt.  
Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

So expected behaviour:

running ubuntu-drivers will show/install the necessary proprietary bits
for the BMC43xx device.

Observed behaviour:

ubuntu-drivers does not list the BCM43xx device at all.
--- 
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2015-10-21 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
NonfreeKernelModules: wl
Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Tags: third-party-packages wily
Uname: Linux 4.2.0-16-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected third-party-packages wily

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

** Description changed:

  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360 based
  device on a late 2013 Macbook Air.
  
  Wily wants to load b43 and dmesg only shows this:
  
  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]
  
  Netman does not list the wifi device at all.
  
  lspci says:
  
  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge
  
  If I use ubuntu-drivers, it also does not list the broadcom device.
  
  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.
  
  So expected behaviour:
  
  running ubuntu-drivers will show/install the necessary proprietary bits
  for the BMC43xx device.
  
  Observed behaviour:
  
  ubuntu-drivers does not list the BCM43xx device at all.
+ --- 
+ ApportVersion: 2.19.1-0ubuntu3
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.10
+ InstallationDate: Installed on 2015-10-21 (0 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
+ NonfreeKernelModules: wl
+ Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
+ Tags: third-party-packages wily
+ Uname: Linux 4.2.0-16-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  15.10 does not offer broadcom drivers for BCM4360 wireless on macbook
  air

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

Bug description:
  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360
  based device on a late 2013 Macbook Air.

  Wily wants to load b43 and dmesg only shows this:

  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]

  Netman does not list the wifi device at all.

  lspci says:

  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge

  If I use ubuntu-drivers, it also does not list the broadcom device.

  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

  So expected behaviour:

  running ubuntu-drivers will show/install the necessary proprietary
  bits for the BMC43xx device.

  Observed 

[Desktop-packages] [Bug 1508719] Dependencies.txt

[Jeff Lane]

apport information

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

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

Title:
  15.10 does not offer broadcom drivers for BCM4360 wireless on macbook
  air

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

Bug description:
  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360
  based device on a late 2013 Macbook Air.

  Wily wants to load b43 and dmesg only shows this:

  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]

  Netman does not list the wifi device at all.

  lspci says:

  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge

  If I use ubuntu-drivers, it also does not list the broadcom device.

  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

  So expected behaviour:

  running ubuntu-drivers will show/install the necessary proprietary
  bits for the BMC43xx device.

  Observed behaviour:

  ubuntu-drivers does not list the BCM43xx device at all.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-10-21 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags: third-party-packages wily
  Uname: Linux 4.2.0-16-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1508719] ProcEnviron.txt

[Jeff Lane]

apport information

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

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

Title:
  15.10 does not offer broadcom drivers for BCM4360 wireless on macbook
  air

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

Bug description:
  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360
  based device on a late 2013 Macbook Air.

  Wily wants to load b43 and dmesg only shows this:

  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]

  Netman does not list the wifi device at all.

  lspci says:

  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge

  If I use ubuntu-drivers, it also does not list the broadcom device.

  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

  So expected behaviour:

  running ubuntu-drivers will show/install the necessary proprietary
  bits for the BMC43xx device.

  Observed behaviour:

  ubuntu-drivers does not list the BCM43xx device at all.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-10-21 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags: third-party-packages wily
  Uname: Linux 4.2.0-16-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1508719] JournalErrors.txt

[Jeff Lane]

apport information

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

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

Title:
  15.10 does not offer broadcom drivers for BCM4360 wireless on macbook
  air

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

Bug description:
  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360
  based device on a late 2013 Macbook Air.

  Wily wants to load b43 and dmesg only shows this:

  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]

  Netman does not list the wifi device at all.

  lspci says:

  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge

  If I use ubuntu-drivers, it also does not list the broadcom device.

  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

  So expected behaviour:

  running ubuntu-drivers will show/install the necessary proprietary
  bits for the BMC43xx device.

  Observed behaviour:

  ubuntu-drivers does not list the BCM43xx device at all.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-10-21 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags: third-party-packages wily
  Uname: Linux 4.2.0-16-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1508719] UbuntuDriversDebug.txt

[Jeff Lane]

apport information

** Attachment added: "UbuntuDriversDebug.txt"
   
https://bugs.launchpad.net/bugs/1508719/+attachment/4502080/+files/UbuntuDriversDebug.txt

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

Title:
  15.10 does not offer broadcom drivers for BCM4360 wireless on macbook
  air

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

Bug description:
  Installed Wily from todays daily (4.2.0-16.19).  After booting, I am
  unable to use the wireless device.  The wifi is a broadcom BCM4360
  based device on a late 2013 Macbook Air.

  Wily wants to load b43 and dmesg only shows this:

  b43-phy0: Broadcom 4360 WLAN found (core revision 42)
  Broadcom 43xx driver loaded [ Features: PNL ]

  Netman does not list the wifi device at all.

  lspci says:

  03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 03)
  kernel driver in use: bcma-pci-bridge

  If I use ubuntu-drivers, it also does not list the broadcom device.

  I had to manually install bcmwl-kernel-source from Restricted via apt.  
  Once dkms had worked it's magic, I was able to use the wifi device on my 
macbook under Wily.

  So expected behaviour:

  running ubuntu-drivers will show/install the necessary proprietary
  bits for the BMC43xx device.

  Observed behaviour:

  ubuntu-drivers does not list the BCM43xx device at all.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-10-21 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: ubuntu-drivers-common 1:0.4.11 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags: third-party-packages wily
  Uname: Linux 4.2.0-16-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1387488] Re: periodic compiz freezes with no logs or error messages, requires me to kill compiz

[Jeff Lane]

** Changed in: compiz (Ubuntu)
   Status: New = Invalid

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

Title:
  periodic compiz freezes with no logs or error messages, requires me to
  kill compiz

Status in compiz package in Ubuntu:
  Invalid

Bug description:
  To start, unfortunately, I have no idea how to reproduce this, nor how
  to trigger it.  All I know is that occasionally I will go away and
  come back hours later to discover that compiz is locked up tight.

  What I see when this happens is the lock screen (screen locks when the
  screensaver engages or screen blanks).  I can still get mouse cursor
  movements which is enough to trigger the monitor to turn back on, BUT
  the password entry box is FULL of dots and while I can move the
  pointer around, clicks are not registered anywhere, nor is any
  keypress.

  When this happens, I can restore the session by sshing into the
  system, and killing the compiz process which I always find consuming
  between 96 and 99% CPU and hung.  Once I kill compiz, it reloads and I
  am able to get back into the system and continue on.

  This happens at least once a week, it seems and I have no idea what
  triggers it as the system is always left idle when it occurs.

  System is an Alienware M15x with an nVidia GT240M card using the
  proprietary nVidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 29 22:30:39 2014
  DistUpgraded: 2014-04-20 14:24:15,941 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:02a2]
  InstallationDate: Installed on 2012-03-15 (958 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120307)
  MachineType: Alienware M15x
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=e7eedf5d-5aad-4230-b123-47162b1acea6 ro
  SourcePackage: compiz
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (192 days ago)
  dmi.bios.date: 08/24/2010
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.vendor: Alienware
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08:
  dmi.product.name: M15x
  dmi.product.version: A08
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Oct  6 14:54:57 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Desktop-packages] [Bug 1334752] Re: Lockscreen timeouts need less ambiguous description in system settings

[Jeff Lane]

** Changed in: unity-control-center (Ubuntu)
   Status: New = Invalid

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

Title:
  Lockscreen timeouts need less ambiguous description in system settings

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  This is really, very, VERY annoying and a potential security problem.

  Looking at System Settings now for my 14.04 install on this desktop at
  Brightness  Lock, it very simply says:

  Lock: ON
  Lock screen after: 5 minutes

  I EXPECT that this means, after 5 minutes of inactivity, the screen
  will lock.

  However, all too often, my screen apparently does not lock.  It blanks
  first, and so expecting it to be locked, I type my password and hit
  enter (because I'm all to often faster at this than the OS is).  Only
  to find out that THIS time, the screen didn't lock, it was still under
  the 5 minute rule, perhaps, and I just typed my password into an IRC
  window and sent it to the world.

  The ONLY other thing I can find that seems to MAYBE have some control
  over screen blanking is the nVidia settings tool.  But that has no
  option for setting a screen blank timeout.

  I'm not the only person who experiences this, I know others who also
  have inadvertently typed a password and hit enter, expecting to unlock
  a locked screen, only to discover it was not locked and their password
  was transmitted to whatever open application currently has focus.

   I also just tried a small test. I hit the space bar to serve as some
  activity, then started a timer on my cellphone and waited.  After
  5'30, the screen STILL had not blanked.  So apparently, the 5 minutes
  is more of a guideline rather than a rule?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1334752/+subscriptions

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

[Desktop-packages] [Bug 1428738] [NEW] update of postgresql-common fails, causes all dep packages to also fail update

[Jeff Lane]

Public bug reported:

Did a simple apt-get update and apt-get dist-upgrade this morning.
postgresql-common failed to update and this caused other related
packages to not be configured.  Here is the console output: (NOTE: this
is the second attempt after the first try failed).

bladernr@klaatu:~$ sudo apt-get dist-upgrade
[sudo] password for bladernr: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libtcl8.5 linux-image-3.11.0-18-generic linux-image-3.13.0-24-generic
  linux-image-3.13.0-26-generic linux-image-3.13.0-29-generic
  linux-image-3.13.0-32-generic linux-image-3.13.0-36-generic
  linux-image-3.13.0-38-generic linux-image-extra-3.11.0-18-generic
  linux-image-extra-3.13.0-24-generic linux-image-extra-3.13.0-26-generic
  linux-image-extra-3.13.0-29-generic linux-image-extra-3.13.0-32-generic
  linux-image-extra-3.13.0-36-generic linux-image-extra-3.13.0-38-generic
  mgetty tcl8.5
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up postgresql-common (154ubuntu1) ...
 * Starting PostgreSQL 9.3 database server  
 * Use of uninitialized value $logsize in numeric gt () at 
/usr/bin/pg_ctlcluster line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at /usr/bin/pg_ctlcluster 
line 224.
Use of uninitialized value $logsize in numeric gt () at 

[Desktop-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

[Jeff Lane]

Can someone please close this bug?

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

Title:
  Gdk-WARNING **: XID collision, trouble ahead

Status in Chromium Browser:
  New
Status in The Mozilla Firefox Browser:
  Invalid
Status in GTK+ GUI Toolkit:
  Expired
Status in Modular X11 Libraries:
  Confirmed
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “firefox-3.5” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “firefox” source package in Lucid:
  Invalid
Status in “firefox-3.5” source package in Lucid:
  Invalid
Status in “gtk+2.0” source package in Lucid:
  Invalid
Status in “firefox” source package in Karmic:
  Invalid
Status in “firefox-3.5” source package in Karmic:
  Won't Fix
Status in “gtk+2.0” source package in Karmic:
  Fix Released

Bug description:
  karmic testing

  in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble 
ahead
  previously, have had this one: (nautilus:3572):
   GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' 
failed (bug report 401822)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions

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

[Desktop-packages] [Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected

[Jeff Lane]

Can someone please close this, it is obviously not necessary after all
this time.

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

Title:
  Logic needed to disable built in pointing devices when external
  devices are connected

Status in GNOME Control Center:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xserver-xorg-input-mouse

  Just about every laptop and netbook these days comes with an built in
  trackpad.  These are often very frustrating as just brushing against
  them, or in some cases even just moving a hand over them can trigger a
  mouse movement or click event.  This is especially frustrating when
  the user is using an external pointing device such as a bluetooth or
  wireless mouse.

  Windows has provided the functionality to disable onboard pointing
  devices when an external mouse is connected/attached, Ubuntu should as
  well.  This is a welcome feature in Windows that saves a lot of
  hassle.  Currently, I have to manually disable my onboard trackpad,
  which leads to issues should my mouse drop connection for whatever
  reason.

  It would be awesome if Ubuntu could recognize that external mouse and
  turn off the trackpad, then turn the trackpad back on when the mouse
  has been detached.

  Just a wishlist item for Natty.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xserver-xorg-input-mouse 1:1.5.0-2build1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  260.19.06  Mon Sep 13 
04:29:19 PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
  Architecture: amd64
  Date: Wed Oct  6 09:18:10 2010
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: Alienware M15x
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-input-mouse
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: Alienware
  dmi.bios.version: A05
  dmi.board.vendor: Alienware
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnAlienware:bvrA05:bd03/11/2010:svnAlienware:pnM15x:pvrA05:rvnAlienware:rn:rvrA05:cvnAlienware:ct8:cvrA05:
  dmi.product.name: M15x
  dmi.product.version: A05
  dmi.sys.vendor: Alienware
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions

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

[Desktop-packages] [Bug 1134069] Re: [HP Envy 4 Sleekbook] external audio jacks are reversed

[Jeff Lane]

Daniel, can you please hand this off?

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

Title:
  [HP Envy 4 Sleekbook] external audio jacks are reversed

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Looking at the outside of the system, the external audio jacks  are in
  this order:

  Mic ___Headphone ___

  However, on testing, it appears that they are either mislabled, or the
  outputs are reversed internally.  I had to plug the headphones into
  the Mic jack to hear sound, and plug the mic into the headphone jack
  to record sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
  ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 1545 F...m pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x5071 irq 48'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:111d76e0,103c1894,00100102 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Wed Feb 27 03:05:29 2013
  HibernationDevice: RESUME=UUID=286b25cc-7928-4406-854e-6c1cae69a6e6
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic 
root=UUID=0c6af5a9-e287-43f5-8ce6-647a4ae228f2 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-25-generic N/A
   linux-backports-modules-3.5.0-25-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1894
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 72.66
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.38:bd10/31/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr088810250E102:rvnHewlett-Packard:rn1894:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 088810250E102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1134069/+subscriptions

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