date:20171004

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

** Branch linked: lp:~3v1n0/ubuntu-themes/use-inverted-decoration-
gradient-on-maximized-windows

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1721440

Title:
  Window titles / Hederbars use redoundant gradients when maximized

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  With default ubuntu theme in gnome-shell it's like we've two panels
  attached and feels really bad.

  See attached screenshot.

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

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

[Touch-packages] [Bug 997200] Re: Add NetworkManager connectivity config package

I'm closing the artful task for update-manager. If update-manager needs
more work to support the connectivity status, I think that should be
split off to a new bug.

** Changed in: update-manager (Ubuntu Artful)
   Status: Confirmed => Won't Fix

** Changed in: update-manager (Ubuntu Artful)
Milestone: quantal-updates => None

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/997200

Title:
  Add NetworkManager connectivity config package

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Precise:
  Won't Fix
Status in ubuntu-meta source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in update-manager source package in Artful:
  Won't Fix
Status in network-manager package in Debian:
  Fix Released

Bug description:
  How to Disable This Feature
  ===
  Option 1
  
  If you are using the default Ubuntu or GNOME, open the Settings app, browse 
to Privacy and turn off Network Connectivity Checking.

  Option 2
  
  You could also disable it by adding a file to /etc/NetworkManager/conf.d/
  with this content:
  [connectivity]
  enabled=false

  Then restart NetworkManager or your computer, whichever is easier.

  Feature
  ===
  A separate network-manager-config-connectivity-ubuntu package that contains 
the 2-line config snippet to enable NetworkManager's connectivity check. This 
is the same approach taken by Fedora since 2014 (their package is named 
network-manager-config-connectivity-fedora).

  With this config, GNOME Shell will pop up a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals

  This new feature (and how to opt out) will be mentioned in Ubuntu
  17.10's Release Notes.

  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html

  Link to newer discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

  Original Bug Report
  ==
  When in a hotel there is a often a T page that is delivered when 
connecting to the network.  Some combination of network manager and update 
manager (or something else entirely) doesn't seem to be able to handle this, 
and update are left in a non-working state after not being able to read package 
headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1717023] Re: Jarring double gradient when window is maximized

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

** Changed in: ubuntu-themes
   Status: New => In Progress

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

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1717023

Title:
  Jarring double gradient when window is maximized

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  light-themes:
    Installed: 16.10+17.10.20170817-0ubuntu1
    Candidate: 16.10+17.10.20170817-0ubuntu1

  Since windows no longer merge with the top panel when maximized in
  17.10, a jarring double gradient is produced instead.

  Steps to reproduce: Maximize a window

  Actual outcome: A double gradient with a sharp line where the top of
  the title bar meets the top panel is produced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1717023/+subscriptions

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

[Touch-packages] [Bug 1567597] Re: [FFe] implement 'complain mode' in seccomp for developer mode with snaps

2017-10-04 Thread Tyler Hicks

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make developing
  on snappy easier.
  
  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we
  can set complain mode to permit all calls, they are not logged at this
  time. I've discussed this with upstream and we are working together on
  the approach. This may require a kernel patch and an update to
  libseccomp, to filing this bug for now as a placeholder and we'll add
  other tasks as necessary.
  
  UPDATE: ubuntu-core-launcher now supports the '@complain' directive that
  is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).
  
  [Impact]
  
  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).
  
  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a
  number of new symbols and probably isn't appropriate to backport until
  upstream has acked the pull request. However, only a small part of that
  larger pull request is needed by snapd and that change can be safely
  backported since the only added symbol, the SCMP_ACT_LOG macro, must
  match the SECCOMP_RET_LOG macro that has already been approved and
  merged in the upstream Linux kernel.
  
  [Test Case]
  
  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised to
  help catch any regressions. Note that on Artful, there's an existing
  test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
+ $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:
  
  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test
  
  The exit code should be 0 and you should have an entry in the system log
  that looks like this:
  
  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test"
  sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc
  
  [Regression Potential]
  
  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older kernels
  that don't support it.

** Summary changed:

- [FFe] implement 'complain mode' in seccomp for developer mode with snaps
+ implement 'complain mode' in seccomp for developer mode with snaps

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

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

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

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

** Changed in: libseccomp (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: libseccomp (Ubuntu Zesty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: libseccomp (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: libseccomp (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: New => In Progress

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted.

[Touch-packages] [Bug 1717023] Re: Jarring double gradient when window is maximized

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1717023

Title:
  Jarring double gradient when window is maximized

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  light-themes:
    Installed: 16.10+17.10.20170817-0ubuntu1
    Candidate: 16.10+17.10.20170817-0ubuntu1

  Since windows no longer merge with the top panel when maximized in
  17.10, a jarring double gradient is produced instead.

  Steps to reproduce: Maximize a window

  Actual outcome: A double gradient with a sharp line where the top of
  the title bar meets the top panel is produced.

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

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

[Touch-packages] [Bug 1721440] Re: Window titles / Hederbars use redoundant gradients when maximized

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

Let's keep this in bug 1717023

** This bug has been marked a duplicate of bug 1717023
   Jarring double gradient when window is maximized

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1721440

Title:
  Window titles / Hederbars use redoundant gradients when maximized

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  With default ubuntu theme in gnome-shell it's like we've two panels
  attached and feels really bad.

  See attached screenshot.

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

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

[Touch-packages] [Bug 1721440] [NEW] Window titles / Hederbars use redoundant gradients when maximized

2017-10-04 Thread Treviño

Public bug reported:

With default ubuntu theme in gnome-shell it's like we've two panels
attached and feels really bad.

See attached screenshot.

** Affects: ubuntu-themes (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Attachment added: "Schermata del 2017-10-05 00:01:52.png"
   
https://bugs.launchpad.net/bugs/1721440/+attachment/4962446/+files/Schermata%20del%202017-10-05%2000%3A01%3A52.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1721440

Title:
  Window titles / Hederbars use redoundant gradients when maximized

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  With default ubuntu theme in gnome-shell it's like we've two panels
  attached and feels really bad.

  See attached screenshot.

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1718238

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1718238

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

** Attachment added: "usr.sbin.cupsd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+attachment/4962440/+files/usr.sbin.cupsd

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Here's something else you may want to look at: The apparmor profile on
my machine for cups.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721428] [NEW] Artful (17.10) Session logout after screen turned off

2017-10-04 Thread Shu Hung (Koala)

Public bug reported:

Whenever I turn off my screen, the computer (a desktop PC) logs me out
of my session.

Here is a discussion thread with users of similar issue:
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

** Affects: gnome-shell
 Importance: Undecided
 Status: New


** Tags: artful

** Summary changed:

- Session logout after screen turned off
+ Artful (17.10) Session logout after screen turned off

** Tags added: artful

** Also affects: gnome-shell
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-settings (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1721428

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  New

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

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

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

[Touch-packages] [Bug 641479] Re: Surround Sound hisstles (hiss + whistle) when the volume is changed

2017-10-04 Thread quequotion

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/445849/comments/258
>This issue is fixed since long ago.
I'm inclined to believe that, though to be honest I simply got into the habit 
of avoiding changing pulseaudio's main volume.

Does it matter if the fix is done in pulseaudio or the alsa-driver package? 
We're not even talking about the same pulseaudio now.
>pulseaudio 10.0


** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/641479

Title:
  Surround Sound hisstles (hiss + whistle) when the volume is changed

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  This bug has been troublesome since Karmic and also affects Lucid.
  It's more likely a bug in pulseaudio than in alsa-driver.

  Whenever pulseaudio changes the sound level, audio begins to hisstle.

  It only clears up at max volume.

  I've heard that using a 7.1 surround configuration resolves the issue,
  but my card only supports up to 5.1

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34
  Uname: Linux 2.6.34-5-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.22.1.
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 16'
 Mixer name : 'Nvidia GT220 HDMI'
 Components : 'HDA:10de000a,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Card1.Amixer.info:
   Card hw:1 'Live'/'SB Live! 5.1 Dell OEM [SB0228] (rev.10, serial:0x80661102) 
at 0xcc00, irq 19'
 Mixer name : 'SigmaTel STAC9708,11'
 Components : 'AC97a:83847608'
 Controls  : 224
 Simple ctrls  : 45
  Date: Sat Sep 18 01:37:22 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 1 Live EMU10K1 - SB Live! 5.1 Dell OEM [SB0228]
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [EMU10K1 - SB Live! 5.1 Dell OEM [SB0228]] Surround problem
  dmi.bios.date: 12/12/2007
  dmi.bios.vendor: HP
  dmi.bios.version: O11
  dmi.board.name: ProLiant ML115 G1
  dmi.board.vendor: HP
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnHP:bvrO11:bd12/12/2007:svnHP:pnProLiantML115G1:pvr1.0:rvnHP:rnProLiantML115G1:rvr:cvnHP:ct7:cvr1.0:
  dmi.product.name: ProLiant ML115 G1
  dmi.product.version: 1.0
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/641479/+subscriptions

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

[Touch-packages] [Bug 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992

Title:
  Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
  denied.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After updating from 8.04 to 12.04 I cannot use rfcomm without sudo.

  I've already added the user  to group 'dialout' .

  Temporary I tried to change udev.rules (KERNEL=="rfcomm[0-9]*", 
GROUP="dialout", MODE="666")  but this doesn't
  solve the problem so I removed it again.

  Here the commands I used :

  burki@orion:/$ hcitool scan
  Scanning ...
   00:12:6F:08:98:FFGEO LE-71 1

  burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF
  Can't open RFCOMM device: Permission denied

  burki@orion:/$ ls -l /dev/rfcomm1
  ls: cannot access /dev/rfcomm1: No such file or directory

  burki@orion:/$ groups
  burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse 
scanner lpadmin netdev sambashare

  burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF
  Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1
  Press CTRL-C for hangup

  In another terminal while connection is running ...

  burki@orion:/$ ls -l /dev/rfcomm1
  crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1

  burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1)
  (I've stolen this command from another bug report #570692.  Output is very 
long. Please see attachment)

  WORKAROUND: sudo chmod u+s /usr/bin/rfcomm

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  burki  1730 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 56'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0887,10438444,00100302 
HDA:80862805,80862805,0010'
     Controls  : 49
     Simple ctrls  : 21
  Date: Tue Jun 19 09:15:54 2012
  HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae 
root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-25-generic-pae N/A
   linux-backports-modules-3.2.0-25-generic-pae  N/A
   linux-firmware1.79
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1720834] Re: Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons

2017-10-04 Thread Danilo Cominotti Marques

Thanks a lot for the feedback, Daniel! I have just tested it on 17.10
and it doesn't happen anymore in Gnome; it happens only in 16.04 and
Unity. If it might be fixed in 16.04, I can take some screenshots and
post them later.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1720834

Title:
  Insufficient padding in horizontal panes causes a resize of the panes
  when alternating between toggle buttons

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu Software, when clicking on "Updates", the horizontal pane
  that holds the buttons "All", "Installed," and "Updates" gets resized
  vertically in order to accommodate the "Refresh" button that gets
  shown in the "Updates" section, which causes a small visual glitch.

  The same effect happens in System Monitor when alternating between the
  "Processes" section and "Resources" and/or "Filesystem."

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

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

[Touch-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

** Package changed: imagemagick (Ubuntu) => ubuntu-settings (Ubuntu)

** Changed in: ubuntu-settings (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1717951

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Committed
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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

[Touch-packages] [Bug 1716018] Re: nm-applet often disappears from panel at startup

2017-10-04 Thread FilipGH

the output of "sudo systemctl status NetworkManager" is:

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
 Docs: man:NetworkManager(8)

 systemd[1]: NetworkManager.service: Found ordering cycle on 
NetworkManager.service/verify-active
 systemd[1]: NetworkManager.service: Found dependency on dbus.service/start
 systemd[1]: NetworkManager.service: Found dependency on dbus.socket/start
 systemd[1]: NetworkManager.service: Found dependency on sysinit.target/start
 systemd[1]: NetworkManager.service: Found dependency on 
firestarter.service/start
 systemd[1]: NetworkManager.service: Found dependency on 
network-online.target/start
 systemd[1]: NetworkManager.service: Found dependency on 
NetworkManager-wait-online.service/start
 systemd[1]: NetworkManager.service: Found dependency on 
NetworkManager.service/verify-active
 systemd[1]: NetworkManager.service: Breaking ordering cycle by deleting job 
sysinit.target/start

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

Title:
  nm-applet often disappears from panel at startup

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  i am with ubuntu 16.04 desktop (64-bit)

  network-manager.service often doesn't start and nm-applet disappears
  from panel at startup

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

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

[Touch-packages] [Bug 1717951] [NEW] UIFe: Drop imagemagick-display from the default install

You have been subscribed to a public bug:

Impact
==
I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

It is visible in the Show Applications view of the Activities Overview
so this could impact screenshots.

Justification
=
imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

Bundled with imagemagick is the "display" app, which is an app with an
unusual, difficult-to-use UI. It was not intentionally included in the
default Ubuntu install but was only there because it was packaged
together.

I am proposing splitting the display app to a separate binary package so
that it is available for install for the few who do want to use the app.

I tried proposing this to Debian. See comment #60 on the attached Debian
bug but the Debian maintainer doesn't seem interested in accepting my
proposal any time soon. (I emailed him directly a few months ago too.)

List Notifications
==
https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

Other Info
==
I will be attaching a patch for review by the Desktop Team here soon.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: imagemagick (Debian)
 Importance: Unknown
 Status: New

-- 
UIFe: Drop imagemagick-display from the default install
https://bugs.launchpad.net/bugs/1717951
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-settings in Ubuntu.

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

[Touch-packages] [Bug 1712011] Re: Unable to close Printer properties

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1712011

Title:
  Unable to close Printer properties

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  Workaround
  --
  Press the Esc key to close the dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1719047] Re: Unable to resize window after snapped to half screen.

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1719047

Title:
  Unable to resize window after snapped to half screen.

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Unable to resize window after snapped to half screen.  You can see the
  arrow, tempting you to just try and resize the window at the edge, but
  it's just toying with you.

  More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

  This used to work in z+Unity ;(.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 19:15:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-04-25 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1719047/+subscriptions

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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

2017-10-04 Thread Bug Watch Updater

** Changed in: glib
   Status: Unknown => Fix Released

** Changed in: glib
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1701780

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 841672] Re: ssh-add does not always unlock ssh keys

2017-10-04 Thread amk

Ubuntu 16.04 also impacted

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/841672

Title:
  ssh-add does not always unlock ssh keys

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  When I execute ssh-add it asks for my keys passwords and confirms that
  they were unlocked, but when I try to ssh into a server I am asked for
  my password again via the ssh-askpass-gnome prompt.

  Here's an (edited and cut) version of my .ssh/config file:

  =
  VisualHostKey yes
  Host myhost1
Hostname myhost1.url
User user
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_dsa
Compression yes
Compressionlevel 6

  Host myhost2
Hostname myhost2.url
User user
PreferredAuthentications publickey
Compression no

  Host myhost3 myhost4 myhost5
Hostname myhost3.url
User user
PreferredAuthentications publickey
Compression yes
Compressionlevel 6

  [...]

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: ssh-askpass (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  Date: Mon Sep  5 11:29:43 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ssh-askpass
  UpgradeStatus: Upgraded to oneiric on 2011-06-29 (68 days ago)

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

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

[Touch-packages] [Bug 1715792] Re: GTK file picker dialogue shows too many mount points

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

** This bug has been marked a duplicate of bug 1701780
   GTK file chooser shows entries from /sys, /dev, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1715792

Title:
  GTK file picker dialogue shows too many mount points

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I'm running kubuntu 17.10 beta, and the GTK file picker dialogue (for
  all GTK apps - e.g. firefox, thunderbird, GIMP, agave) is listing a
  tonne of useless mount points in the left-most panel:

  https://i.stack.imgur.com/TrJYy.png

  Is there any way to hide these? Other posts suggest adding commands to
  /etc/fstab, but none of these mount points are listed in fstab to
  begin with..

  These entries do not appear in the Qt file picker dialogue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgtk-3-0 3.22.19-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-lowlatency 4.12.8
  Uname: Linux 4.12.0-12-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 13:33:19 2017
  InstallationDate: Installed on 2017-08-19 (19 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1715792/+subscriptions

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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

I think this is a glib2.0 bug fixed in 2.54.1

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: Confirmed => Fix Committed

** Package changed: ubuntu => glib2.0 (Ubuntu)

** Bug watch added: GNOME Bug Tracker #781867
   https://bugzilla.gnome.org/show_bug.cgi?id=781867

** Also affects: glib via
   https://bugzilla.gnome.org/show_bug.cgi?id=781867
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1701780

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1701780

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 1701780] [NEW] GTK file chooser shows entries from /sys, /dev, etc.

You have been subscribed to a public bug:

On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
chooser opened from Firefox, GNOME Disks, etc. At the time of writing, I
haven't tested whether it occurs in the GTK2 chooser as well. I have
attached a screenshot showing the problem.

** Affects: glib2.0 (Ubuntu)
 Importance: Low
 Status: Fix Committed


** Tags: artful gtk kubuntu
-- 
GTK file chooser shows entries from /sys, /dev, etc.
https://bugs.launchpad.net/bugs/1701780
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 in Ubuntu.

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

[Touch-packages] [Bug 1719047] Re: Unable to resize window after snapped to half screen.

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Fix Committed

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Committed

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1719047

Title:
  Unable to resize window after snapped to half screen.

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Unable to resize window after snapped to half screen.  You can see the
  arrow, tempting you to just try and resize the window at the edge, but
  it's just toying with you.

  More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

  This used to work in z+Unity ;(.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 19:15:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-04-25 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1719047/+subscriptions

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

[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2017-10-04 Thread John Cooper

** Description changed:

  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user, is
  unable to perform an iOS device restore. In order to do so currently the
  user needs to have some way of running an up to date iTunes software
  with a usb connection to the iPhone, iPad or iPod Touch.
  
  Which is quite a hassle to go through in order to completely reload the
  device's iOS software. It would be much better if a binary compiled
  version of the software (idevicerestore and libirecovery) could be
  included in the utilities package.
  
  It would allow the Ubuntu user to be able to quickly and easily perform
  software update or device restore functions. Without the need for a
  virtual machine running a compatible version of Windows and iTunes etc.
  While also saving them from having to run Wine, its dependencies, iTunes
  and its own software requirements.
  
  All the would need is what is required to install idevicerestore and run
  its actions (the appropriate iOS release download image file).
  
+ The code for idevice restore is available here
+ (https://cgit.sukimashita.com/idevicerestore.git/) and the library from
+ here (https://cgit.sukimashita.com/libirecovery.git/).
+ 
  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1721398

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  The code for idevice restore is available here
  (https://cgit.sukimashita.com/idevicerestore.git/) and the library
  from here (https://cgit.sukimashita.com/libirecovery.git/).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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

[Touch-packages] [Bug 238755] RE

2017-10-04 Thread Kennedyshead

Win yesterday $7807 
Re: Jag klarar inte plдdar mцte idag

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/238755

Title:
  'Account has expired' message when adding a new user, after "passwd -l
  root"

Status in landscape-client package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in landscape-client source package in Hardy:
  Won't Fix
Status in shadow source package in Hardy:
  Won't Fix
Status in landscape-client source package in Intrepid:
  Invalid
Status in shadow source package in Intrepid:
  Fix Released
Status in shadow package in Debian:
  Fix Released

Bug description:
  Binary package hint: adduser

  I've repeatedly added new users, but receive a seemingly spurious
  error:

  rich@aias:~$ sudo adduser james
  Adding user `james' ...
  Adding new group `james' (1004) ...
  Adding new user `james' (1004) with group `james' ...
  Creating home directory `/home/james' ...
  Copying files from `/etc/skel' ...
  Enter new UNIX password: 
  Retype new UNIX password: 
  passwd: password updated successfully
  Your account has expired; please contact your system administrator
  chfn: PAM authentication failed
  adduser: `/usr/bin/chfn james' returned error code 1. Exiting.

  However, the user can log in.

  rich@aias:~$ finger james
  Login: james  Name: 
  Directory: /home/jamesShell: /bin/bash
  On since Mon Jun  9 21:19 (PDT) on tty1   4 minutes 57 seconds idle
   (messages off)
  No mail.
  No Plan.

  adduser version: 3.105ubuntu1
  ubuntu version: 8.04 , fully updated

  I've marked this as a security issue, since pam is part of the error
  message.

  Update:

  This seems to be related to the use of "passwd -l root".
  Until the Debian fix shows up in hardy, here is a workaround, thanks to 
Nicolas François:

   sudo passwd --unlock root
   sudo usermod --lock root

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/238755/+subscriptions

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

note that one cannot really use bond0 as it will be auto created and
networkd may loose the race to configure it. it is safer to use bond1
until a bugfix is SRUed to set max_bond to zero by default.

pre-tested with artful's netplan on zesty with a backrported systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1709135

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

Please add SRU information to the bug:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1713747

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Fix Committed

Bug description:
  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

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

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

[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

This is about address lables. Sample .network file to verify this is:

[Match]
MACAddress=52:54:00:8c:9d:b8

[Address]
Address=10.3.0.1/24
Label=ens3:xo:xo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714933

Title:
  Xenial: Please roll SRU with upstream fix for networkd to "accept
  colons in network interface names"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  In Progress
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  networkd cannot manage interface names with ':' in them. As used commonly, by 
convention, by other tools.

  [Fix]
  Update networkd validation routines and test-suites to accept network 
interface names with ':' in it.

  [Testcase]
  Create an inteface with ':' in its name and use it anywhere where systemd 
validates ifname. E.g. Socket BindToDevice definition, nspawn network zone 
info, Label= in [Address] section in networkd.

  [Regression Potential]
  This fix will change validation routines, and thus commands or settings that 
were previously rejected or ignored will now take effect. Specifically Label= 
settings in networkd may lead to networking conflicts. The justification for 
this change is that networkd should really use the sensible ':' ifnames that 
the user is requesting systemd to use.

  [Original Bug Reprot]
  PR: https://github.com/systemd/systemd/pull/5117

  issue: https://github.com/systemd/systemd/issues/4057

  Before the networkd from 231 was backported, it was possible to use
  interface alias names that contained a colon, e.g. eth0:1. This is
  commonly used to make legacy tools like "ifconfig" work, because they
  *expect* a colon in the interface name.

  Martin told me to file a bug for this.

  Merging networkd from 231 lead to a regression where valid configs
  were not accepted anymore after the backport. Please merge that fix
  for the regression.

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

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

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

Hello Mathieu, or anyone else affected,

Accepted isc-dhcp into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.5-3ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1713747

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Fix Committed

Bug description:
  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Here's one set:
[  189.457095] audit: type=1400 audit(1507146357.726:48): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cups-browsed" 
pid=2784 comm="apparmor_parser"
[  216.802135] audit: type=1400 audit(1507146385.075:49): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cups-browsed" name="/proc/2864/cmdline" 
pid=2864 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  217.974857] audit: type=1400 audit(1507146386.247:50): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/2871/cmdline" pid=2871 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  217.978903] audit: type=1400 audit(1507146386.251:51): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/2871/cmdline" pid=2871 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=7
[  358.429024] audit: type=1400 audit(1507146526.583:52): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/3294/cmdline" pid=3294 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  358.429102] audit: type=1400 audit(1507146526.583:53): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/3295/cmdline" pid=3295 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  358.429204] audit: type=1400 audit(1507146526.583:54): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/3296/cmdline" pid=3296 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  358.429339] audit: type=1400 audit(1507146526.583:55): apparmor="ALLOWED" 
operation="open" profile="/usr/sbin/cupsd" name="/proc/3297/cmdline" pid=3297 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

I also did 
aa-complain /usr/sbin/cups-browsed

but printing worked before I set that.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721138] Re: APT update fail when using HTTPS

Reassigning to gnutls26. But I'd recommend upgrading to xenial which has
a gnutls version that can actually handle modern HTTPS connections.

** Package changed: apt (Ubuntu) => gnutls26 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpad.net/bugs/1721138

Title:
  APT update fail when using HTTPS

Status in gnutls26 package in Ubuntu:
  New

Bug description:
  ### Ubuntu Release
  root@:~# lsb_release -rd 
  Description:    Ubuntu 14.04.5 LTS
  Release:        14.04
  root@:~#

  ### Expected Behaviors

  Trusty’s version of apt should be able to pull updates from an
  internal mirror using the HTTPS protocol and a SHA256 certificate
  (please check the 2nd link at the end of this description)

  Note: Using the same configuration on Ubuntu Xenial works.

  ### Actual Behavior

  Apt error out with the error: gnutls_handshake() failed: The signature
  algorithm is not supported.

  ### Package Information
  Im not sure if the problem is actually with apt of with a library (I’m 
including libgnutls26 info as well)
  root@:~# apt-cache policy apt
  apt:
    Installed: 1.0.1ubuntu2.17
    Candidate: 1.0.1ubuntu2.17
    Version table:
   *** 1.0.1ubuntu2.17 0
          100 /var/lib/dpkg/status
  root@:~# 

  root@:~# apt-cache policy libgnutls26
  libgnutls26:
    Installed: 2.12.23-12ubuntu2.8
    Candidate: 2.12.23-12ubuntu2.8
    Version table:
   *** 2.12.23-12ubuntu2.8 0
          100 /var/lib/dpkg/status
  root@:~#

  ### Active sources
  root@:~# egrep -R -v '^#|^$' --include=\*.list /etc/apt/
  /etc/apt/sources.list:deb https:///ubuntu/test trusty main 
restricted universe multiverse
  root@:~# 

  ### Apt Update output

  root@:~# apt update -qq
  W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-amd64/Packages  gnutls_handshake() 
failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  E: Some index files failed to download. They have been ignored, or old ones 
used instead.
  root@:~#

  # NMAP output of the current allowed ciphers
  root@:~# nmap --script ssl-enum-ciphers -p 443

   

  Starting Nmap 6.40 ( http://nmap.org ) at 2017-10-03 21:07 GMT
  Nmap scan report for  ()
  Host is up (0.0039s latency).
  PORTSTATE SERVICE
  443/tcp open  https
  | ssl-enum-ciphers: 
  |   SSLv3: No supported ciphers found
  |   TLSv1.0: 
  | ciphers: 
  |   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_SEED_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_RC4_128_SHA - strong
  |   TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
  |   TLS_RSA_WITH_RC4_128_MD5 - strong
  |   TLS_RSA_WITH_RC4_128_SHA - strong
  |   TLS_RSA_WITH_SEED_CBC_SHA - strong
  | compressors: 
  |   NULL
  |   TLSv1.1: 
  | ciphers: 
  |   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_SEED_CBC_SHA - strong
  |

[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2017-10-04 Thread John Cooper

** Description changed:

  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user, is
  unable to perform an iOS device restore. In order to do so currently the
  user needs to have some way of running an up to date iTunes software
  with a usb connection to the iPhone, iPad or iPod Touch.
  
  Which is quite a hassle to go through in order to completely reload the
  device's iOS software. It would be much better if a binary compiled
- version of the software could be included in the utilities package.
+ version of the software (idevicerestore and libirecovery) could be
+ included in the utilities package.
  
  It would allow the Ubuntu user to be able to quickly and easily perform
  software update or device restore functions. Without the need for a
  virtual machine running a compatible version of Windows and iTunes etc.
  While also saving them from having to run Wine, its dependencies, iTunes
  and its own software requirements.
  
  All the would need is what is required to install idevicerestore and run
  its actions (the appropriate iOS release download image file).
  
  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1721398

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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

[Touch-packages] [Bug 1721399] Re: Z LPAR 17.10: DNS server provided during the install process is not configured

** Attachment added: "systemd-resolve.status.out"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962371/+files/systemd-resolve.status.out

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721399

Title:
  Z LPAR 17.10: DNS server provided during the install process is not
  configured

Status in systemd package in Ubuntu:
  New

Bug description:
  The DNS server provided to the debian-installer is not configured

  ubuntu@s5lp7:/var/log/installer$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;10.245.208.1.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 41

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 48

  Works when specifically providing the DNS IP:
  ubuntu@s5lp7:/var/log/installer$ dig @10.245.208.1 us.ports.ubuntu.com
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.245.208.1 us.ports.ubuntu.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; ANSWER SECTION:
  us.ports.ubuntu.com.  299 IN  A   91.189.91.11

  ;; AUTHORITY SECTION:
  ubuntu.com.   76  IN  NS  ns4.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns2.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns3.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns1.p27.dynect.net.

  ;; ADDITIONAL SECTION:
  ns1.p27.dynect.NET.   63971   IN  A   208.78.70.27
  ns1.p27.dynect.NET.   72  IN  2001:500:90:1::27
  ns2.p27.dynect.NET.   63971   IN  A   204.13.250.27
  ns3.p27.dynect.NET.   63971   IN  A   208.78.71.27
  ns4.p27.dynect.NET.   63971   IN  A   204.13.251.27

  ;; Query time: 0 msec
  ;; SERVER: 10.245.208.1#53(10.245.208.1)
  ;; WHEN: Wed Oct 04 16:21:49 UTC 2017
  ;; MSG SIZE  rcvd: 272

  ubuntu@s5lp7:/var/log/installer$ cat /etc/network/interfaces
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.245.208.1
dns-search canonical.com

  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  Can be worked around by directly adding a nameserver entry to /etc/resolv.conf
  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.245.208.1
  #nameserver 127.0.0.53

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

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

[Touch-packages] [Bug 1721399] Re: Z LPAR 17.10: DNS server provided during the install process is not configured

** Attachment added: "s5lp7_installer_logs.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962373/+files/s5lp7_installer_logs.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721399

Title:
  Z LPAR 17.10: DNS server provided during the install process is not
  configured

Status in systemd package in Ubuntu:
  New

Bug description:
  The DNS server provided to the debian-installer is not configured

  ubuntu@s5lp7:/var/log/installer$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;10.245.208.1.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 41

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 48

  Works when specifically providing the DNS IP:
  ubuntu@s5lp7:/var/log/installer$ dig @10.245.208.1 us.ports.ubuntu.com
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.245.208.1 us.ports.ubuntu.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; ANSWER SECTION:
  us.ports.ubuntu.com.  299 IN  A   91.189.91.11

  ;; AUTHORITY SECTION:
  ubuntu.com.   76  IN  NS  ns4.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns2.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns3.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns1.p27.dynect.net.

  ;; ADDITIONAL SECTION:
  ns1.p27.dynect.NET.   63971   IN  A   208.78.70.27
  ns1.p27.dynect.NET.   72  IN  2001:500:90:1::27
  ns2.p27.dynect.NET.   63971   IN  A   204.13.250.27
  ns3.p27.dynect.NET.   63971   IN  A   208.78.71.27
  ns4.p27.dynect.NET.   63971   IN  A   204.13.251.27

  ;; Query time: 0 msec
  ;; SERVER: 10.245.208.1#53(10.245.208.1)
  ;; WHEN: Wed Oct 04 16:21:49 UTC 2017
  ;; MSG SIZE  rcvd: 272

  ubuntu@s5lp7:/var/log/installer$ cat /etc/network/interfaces
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.245.208.1
dns-search canonical.com

  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  Can be worked around by directly adding a nameserver entry to /etc/resolv.conf
  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.245.208.1
  #nameserver 127.0.0.53

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

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

[Touch-packages] [Bug 1721399] Re: Z LPAR 17.10: DNS server provided during the install process is not configured

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962372/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721399

Title:
  Z LPAR 17.10: DNS server provided during the install process is not
  configured

Status in systemd package in Ubuntu:
  New

Bug description:
  The DNS server provided to the debian-installer is not configured

  ubuntu@s5lp7:/var/log/installer$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;10.245.208.1.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 41

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 48

  Works when specifically providing the DNS IP:
  ubuntu@s5lp7:/var/log/installer$ dig @10.245.208.1 us.ports.ubuntu.com
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.245.208.1 us.ports.ubuntu.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; ANSWER SECTION:
  us.ports.ubuntu.com.  299 IN  A   91.189.91.11

  ;; AUTHORITY SECTION:
  ubuntu.com.   76  IN  NS  ns4.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns2.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns3.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns1.p27.dynect.net.

  ;; ADDITIONAL SECTION:
  ns1.p27.dynect.NET.   63971   IN  A   208.78.70.27
  ns1.p27.dynect.NET.   72  IN  2001:500:90:1::27
  ns2.p27.dynect.NET.   63971   IN  A   204.13.250.27
  ns3.p27.dynect.NET.   63971   IN  A   208.78.71.27
  ns4.p27.dynect.NET.   63971   IN  A   204.13.251.27

  ;; Query time: 0 msec
  ;; SERVER: 10.245.208.1#53(10.245.208.1)
  ;; WHEN: Wed Oct 04 16:21:49 UTC 2017
  ;; MSG SIZE  rcvd: 272

  ubuntu@s5lp7:/var/log/installer$ cat /etc/network/interfaces
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.245.208.1
dns-search canonical.com

  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  Can be worked around by directly adding a nameserver entry to /etc/resolv.conf
  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.245.208.1
  #nameserver 127.0.0.53

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

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

[Touch-packages] [Bug 1721399] [NEW] Z LPAR 17.10: DNS server provided during the install process is not configured

Public bug reported:

The DNS server provided to the debian-installer is not configured

ubuntu@s5lp7:/var/log/installer$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename:   artful

ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;10.245.208.1.  IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Oct 04 16:16:33 UTC 2017
;; MSG SIZE  rcvd: 41

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;us.ports.ubuntu.com.   IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Oct 04 16:16:33 UTC 2017
;; MSG SIZE  rcvd: 48

Works when specifically providing the DNS IP:
ubuntu@s5lp7:/var/log/installer$ dig @10.245.208.1 us.ports.ubuntu.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.245.208.1 us.ports.ubuntu.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;us.ports.ubuntu.com.   IN  A

;; ANSWER SECTION:
us.ports.ubuntu.com.299 IN  A   91.189.91.11

;; AUTHORITY SECTION:
ubuntu.com. 76  IN  NS  ns4.p27.dynect.net.
ubuntu.com. 76  IN  NS  ns2.p27.dynect.net.
ubuntu.com. 76  IN  NS  ns3.p27.dynect.net.
ubuntu.com. 76  IN  NS  ns1.p27.dynect.net.

;; ADDITIONAL SECTION:
ns1.p27.dynect.NET. 63971   IN  A   208.78.70.27
ns1.p27.dynect.NET. 72  IN  2001:500:90:1::27
ns2.p27.dynect.NET. 63971   IN  A   204.13.250.27
ns3.p27.dynect.NET. 63971   IN  A   208.78.71.27
ns4.p27.dynect.NET. 63971   IN  A   204.13.251.27

;; Query time: 0 msec
;; SERVER: 10.245.208.1#53(10.245.208.1)
;; WHEN: Wed Oct 04 16:21:49 UTC 2017
;; MSG SIZE  rcvd: 272

ubuntu@s5lp7:/var/log/installer$ cat /etc/network/interfaces
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.245.208.1
dns-search canonical.com

ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

Can be worked around by directly adding a nameserver entry to /etc/resolv.conf
ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 10.245.208.1
#nameserver 127.0.0.53

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


** Tags: s390x

** Attachment added: "apport.systemd.y958ceeu.apport"
   
https://bugs.launchpad.net/bugs/1721399/+attachment/4962369/+files/apport.systemd.y958ceeu.apport

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721399

Title:
  Z LPAR 17.10: DNS server provided during the install process is not
  configured

Status in systemd package in Ubuntu:
  New

Bug description:
  The DNS server provided to the debian-installer is not configured

  ubuntu@s5lp7:/var/log/installer$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;10.245.208.1.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 41

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
  ;; flags: qr rd ra; QUERY: 1,

[Touch-packages] [Bug 1515513] Please test proposed package

Hello Robin, or anyone else affected,

Accepted dkms into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu1.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

Hello Robin, or anyone else affected,

Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

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

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

** Tags added: verification-needed-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721398] [NEW] Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2017-10-04 Thread John Cooper

Public bug reported:

Currently all of the other important utilities are included for
installation on Ubuntu. However currently though a Ubuntu Linux user, is
unable to perform an iOS device restore. In order to do so currently the
user needs to have some way of running an up to date iTunes software
with a usb connection to the iPhone, iPad or iPod Touch.

Which is quite a hassle to go through in order to completely reload the
device's iOS software. It would be much better if a binary compiled
version of the software (idevicerestore and libirecovery) could be
included in the utilities package.

It would allow the Ubuntu user to be able to quickly and easily perform
software update or device restore functions. Without the need for a
virtual machine running a compatible version of Windows and iTunes etc.
While also saving them from having to run Wine, its dependencies, iTunes
and its own software requirements.

All the would need is what is required to install idevicerestore and run
its actions (the appropriate iOS release download image file).

Running Ubuntu 16.04.3
libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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


** Tags: file idevicerestore libimobiledevice-utils libirecovery missing

** Tags added: idevicerestore libirecovery

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1721398

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-10-04 Thread Ryan Harper

I re-ran the recreate on a daily artful image, updated cloud-init in the
image to use the udevadm trigger as before and noticed that it still
fails to apply the MTU to the second interface.

Taking the suggestion of including a udevadm control reload, I further
modified the image to add that reload instruction.

When using the reload then I can confirm that the MTU setting is
applied.  It appears that netplan indeed should run the reload operation
in the 'netplan generate' call.

ubuntu@ubuntu:/$ cat /etc/cloud/build.info 
build_name: server
serial: 20171003
ubuntu@ubuntu:/$ apt-cache policy cloud-init
cloud-init:
  Installed: 17.1-0ubuntu1
  Candidate: 17.1-0ubuntu1
  Version table:
 *** 17.1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu@ubuntu:/$ 
ubuntu@ubuntu:/$ cat /run/systemd/network/*.link
[Match]
MACAddress=52:54:00:12:34:00

[Link]
Name=interface0
WakeOnLan=off
[Match]
MACAddress=52:54:00:12:34:02

[Link]
Name=interface1
WakeOnLan=off
MTUBytes=1492
ubuntu@ubuntu:/$ cat /sys/class/net/interface0/mtu 
1500
ubuntu@ubuntu:/$ cat /sys/class/net/interface1/mtu 
1492
ubuntu@ubuntu:/$ grep udevadm /var/log/cloud-init.log 
2017-10-04 21:05:40,636 - util.py[DEBUG]: Running command ['udevadm', 
'control', '--reload'] with allowed return codes [0] (shell=False, capture=True)
2017-10-04 21:05:40,642 - util.py[DEBUG]: Running command ['udevadm', 
'trigger', '--verbose', '--subsystem-match=net', '--action=add'] with allowed 
return codes [0] (shell=False, capture=True)


** Changed in: nplan (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1669564

Title:
  udevadm trigger subsystem-match=net doesn't always run rules because
  of reconfiguration rate-limiting

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings

  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.

  Here'a log during boot where cloud-init generates a netplan config,
  invokes `netplan generate` which writes the networkd config out 
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.

  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).

  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:

  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02

  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1500
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 35  bytes 3287 (3.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add
  /sys/devices/pci:00/:00:04.0/virtio1/net/interface1
  /sys/devices/pci:00/:00:05.0/virtio2/net/interface2
    ys/devices/pci:00/:00:06.0/virtio3/net/interface0
  /sys/devices/virtual/net/lo

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1492

[Touch-packages] [Bug 1712011] Re: Unable to close Printer properties

** Project changed: gnome-control-center => gtk

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1712011

Title:
  Unable to close Printer properties

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  Workaround
  --
  Press the Esc key to close the dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1721387] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2017-10-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1721387

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-93.101-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-93-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Wed Oct  4 21:14:28 2017
  DuplicateSignature: package:shared-mime-info:1.5-2ubuntu0.1:subprocess 
installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2015-06-21 (836 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1721387/+subscriptions

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

[Touch-packages] [Bug 1721387] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2017-10-04 Thread Brian Antao

Public bug reported:

upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-93.101-lowlatency 3.19.8-ckt22
Uname: Linux 3.19.0-93-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Wed Oct  4 21:14:28 2017
DuplicateSignature: package:shared-mime-info:1.5-2ubuntu0.1:subprocess 
installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2015-06-21 (836 days ago)
InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4.2
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1721387

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-93.101-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-93-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Wed Oct  4 21:14:28 2017
  DuplicateSignature: package:shared-mime-info:1.5-2ubuntu0.1:subprocess 
installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2015-06-21 (836 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1721387/+subscriptions

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

2017-10-04 Thread guysoft

Ok really strange, after running once with aa-complain, it seems to
solve the problem.


In syslog I see this:

golem4 kernel: [188942.996377] audit: type=1400
audit(1507148174.867:125): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/cupsd" name="/proc/20273/cmdline" pid=20273
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0


Before that I see entries that look like this:
Oct  4 12:50:54 golem4 kernel: [151422.393607] audit: type=1400 
audit(1507110654.087:74): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/proc/2399/cmdline" pid=2399 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct  4 12:50:54 golem4 kernel: [151422.393706] cupsd[2399]: segfault at 0 ip 
7fb9ba1f7715 sp 7ffce931b968 error 4 in 
libc-2.24.so[7fb9ba0aa000+1be000]
Oct  4 12:50:54 golem4 systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV

Note it says apparmor="DENIED"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 641479] Re: Surround Sound hisstles (hiss + whistle) when the volume is changed

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/641479

Title:
  Surround Sound hisstles (hiss + whistle) when the volume is changed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This bug has been troublesome since Karmic and also affects Lucid.
  It's more likely a bug in pulseaudio than in alsa-driver.

  Whenever pulseaudio changes the sound level, audio begins to hisstle.

  It only clears up at max volume.

  I've heard that using a 7.1 surround configuration resolves the issue,
  but my card only supports up to 5.1

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34
  Uname: Linux 2.6.34-5-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.22.1.
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 16'
 Mixer name : 'Nvidia GT220 HDMI'
 Components : 'HDA:10de000a,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Card1.Amixer.info:
   Card hw:1 'Live'/'SB Live! 5.1 Dell OEM [SB0228] (rev.10, serial:0x80661102) 
at 0xcc00, irq 19'
 Mixer name : 'SigmaTel STAC9708,11'
 Components : 'AC97a:83847608'
 Controls  : 224
 Simple ctrls  : 45
  Date: Sat Sep 18 01:37:22 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 1 Live EMU10K1 - SB Live! 5.1 Dell OEM [SB0228]
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [EMU10K1 - SB Live! 5.1 Dell OEM [SB0228]] Surround problem
  dmi.bios.date: 12/12/2007
  dmi.bios.vendor: HP
  dmi.bios.version: O11
  dmi.board.name: ProLiant ML115 G1
  dmi.board.vendor: HP
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnHP:bvrO11:bd12/12/2007:svnHP:pnProLiantML115G1:pvr1.0:rvnHP:rnProLiantML115G1:rvr:cvnHP:ct7:cvr1.0:
  dmi.product.name: ProLiant ML115 G1
  dmi.product.version: 1.0
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/641479/+subscriptions

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

2017-10-04 Thread Till Kamppeter

HuaiDan (dhutchison69), if this works for you, please post all the CUPS-
related "audit" lines from your /var/log/syslog file.


** Changed in: cups (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Workaround:

sudo aa-complain /usr/sbin/cupsd

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

See this commit for the implementation and the reasoning:

https://anonscm.debian.org/cgit/apt/apt.git/commit/?h=7c2cc4a7bc999c8e07fba607354bfaa3b09118f9

** Changed in: apt (Ubuntu)
   Status: New => Opinion

** Changed in: apt (Debian)
   Status: New => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  Opinion
Status in apt package in Debian:
  Opinion

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2017-10-04 Thread Ryan Harper

** Branch linked: lp:~raharper/curtin/trunk.vmtest-remove-bug-timers

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  
  Some context from those discussions

  
  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1721378] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@1550:main:get_dpkg_log_content:decode

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1550, in 
main(options)
  File "/usr/bin/unattended-upgrade", line 1488, in main
log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
  File "/usr/bin/unattended-upgrade", line 1124, in get_dpkg_log_content
for line in fp.readlines():
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 6821: 
invalid continuation byte

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1721378

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@1550:main:get_dpkg_log_content:decode

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.93.1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/9cc4adbd103ea3f15d6342d3cbb048179054885d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721378/+subscriptions

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

Conflict or something = If the meta package cannot be kept installed
because a dependency broke, APT will mark the remaining dependencies as
manually installed when removing the meta package.

But if you remove the meta package explicitly, you usually want to
remove the dependencies of it as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Workaround:

sudo aa-complain /usr/sbin/cupsd

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1706052

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

The behavior as specified in the bug report and the comments is
intended.

When installing a package in never mark auto, it is not marked as auto.
On removal, dependencies of it will be

(1) marked as manually if the package was removed as a result of a conflict or 
something
(2) kept as automatic if the package was removed explicitly

The old implementation that just marked all stuff as manual led to the
problem that installing a meta package and explicitly removing it did
not remove any dependencies.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1721378] [NEW] /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@1550:main:get_dpkg_log_content:decode

2017-10-04 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.93.1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/9cc4adbd103ea3f15d6342d3cbb048179054885d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1721378

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@1550:main:get_dpkg_log_content:decode

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.93.1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/9cc4adbd103ea3f15d6342d3cbb048179054885d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721378/+subscriptions

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

I've also confirmed this incorrect behavior with debian/sid and apt 1.5.

$ sudo apt-mark showmanual >before
$ sudo apt-get -o Debug::pkgDepCache::AutoInstall=true install ros-desktop
[...]
$ sudo apt-mark showmanual >after
root@golden-raccoon:~# diff -u before after 
  
--- before  2017-10-04 19:16:05.171917363 +
+++ after   2017-10-04 19:18:06.323914112 +
@@ -116,6 +116,7 @@
 passwd
 perl-base
 procps
+ros-desktop
 sed
 sensible-utils
 systemd


** Also affects: apt (Debian)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

Using the test in debian bug 793360.

$ sudo apt-mark showmanual >before
$ sudo apt-get -o Debug::pkgDepCache::AutoInstall=true install ubuntu-standard
[...]
$ sudo apt-mark showmanual >after
$ diff -u before after
--- before  2017-10-04 11:36:41.967980781 -0700
+++ after   2017-10-04 11:37:47.615979019 -0700
@@ -119,6 +119,7 @@
 tar
 tzdata
 ubuntu-keyring
+ubuntu-standard
 util-linux
 vim
 xz-utils

Only ubuntu-standard was marked as manually installed and none of its
dependencies were.  ubuntu-standard has a section of "metapackages" and
some of my apt-config follows:

# apt-config dump | grep Sections
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

I reported bug 1721364 regarding the Never-MarkAuto-Sections issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  By default settings unattended-upgrade is unable to automatically
  remove packages that become unused in conjunction with updating by
  other software.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1721364] Re: Never-MarkAuto-Sections not working

Similar incorrect behavior is also seen with Ubuntu 16.04 and Ubuntu
17.04.

Ubuntu 16.04 with apt version 1.2.25

# apt-get --purge autoremove ubuntu-standard
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  accountsservice* apt-transport-https* bind9-host* busybox-static* 
ca-certificates* command-not-found* command-not-found-data* cpio* cron* 
distro-info-data* dmidecode*
  dnsutils* friendly-recovery* ftp* fuse* geoip-database* gettext-base* ...

Ubuntu 17.04 with apt version 1.4.6~17.04.1

# apt-get --purge autoremove ubuntu-standard
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  accountsservice* apparmor* apt-transport-https* bind9-host* busybox-static* 
ca-certificates* command-not-found* command-not-found-data* cpio* cron* dbus* 
dh-python*
  distro-info-data* dmidecode* dnsutils* friendly-recovery* ftp* fuse* 
geoip-database* gettext-base* gir1.2-glib-2.0*...

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1720838] Re: Nvidia gnome control center scale gets overridden on reboot

2017-10-04 Thread Treviño

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Bug watch added: GNOME Bug Tracker #788483
   https://bugzilla.gnome.org/show_bug.cgi?id=788483

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=788483
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1720838

Title:
  Nvidia gnome control center scale gets overridden on reboot

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for 
my session.
  If I reboot then the scale is reset back to 100% but the value on the control 
center "displays" section shows "200%".

  To work around it I save the scale to 100% then save it back to 200%.
  After rebooting I have to do this every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:

  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 11:34:59 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230]
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20ENCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET70W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct  2 11:32:23 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu6

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

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

[Touch-packages] [Bug 1721364] [NEW] Never-MarkAuto-Sections not working

Public bug reported:

"apt-get --purge autoremove ubuntu-standard" wants to remove a lot more
packages than just ubuntu-standard. Bug 1479207 is a previous version of
this.

Using apt version 1.5 on Artful Aardvark:

The following packages will be REMOVED:
  accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
  friendly-recovery* ftp* fuse* geoip-database* gettext-base* gir1.2-glib-2.0* 
hdparm* info* iptables* iputils-tracepath* irqbalance* iso-codes* krb5-locales*
  language-selector-common* libaccountsservice0*...

This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  ubuntu-standard*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 61.4 kB disk space will be freed.
Do you want to continue? [Y/n] n

** Affects: apt (Ubuntu)
 Importance: High
 Status: New


** Tags: artful rls-aa-incoming xenial zesty

** Tags added: artful rls-aa-incoming xenial zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1721364

Title:
  Never-MarkAuto-Sections not working

Status in apt package in Ubuntu:
  New

Bug description:
  "apt-get --purge autoremove ubuntu-standard" wants to remove a lot
  more packages than just ubuntu-standard. Bug 1479207 is a previous
  version of this.

  Using apt version 1.5 on Artful Aardvark:

  The following packages will be REMOVED:
accountsservice* apparmor* bind9-host* busybox-static* command-not-found* 
command-not-found-data* cpio* cron* dbus* dh-python* distro-info-data* 
dmidecode* dnsutils*
friendly-recovery* ftp* fuse* geoip-database* gettext-base* 
gir1.2-glib-2.0* hdparm* info* iptables* iputils-tracepath* irqbalance* 
iso-codes* krb5-locales*
language-selector-common* libaccountsservice0*...

  This does work correctly on Trusty with apt version 1.0.1ubuntu2.17.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ubuntu-standard*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 61.4 kB disk space will be freed.
  Do you want to continue? [Y/n] n

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

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

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

2017-10-04 Thread Dan Streetman

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: initramfs-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1712491

Title:
  Add backported bnxt driver to the initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  We're adding a backported bnxt driver to Xenial (LP #1711056). It's an 
alternate for the regular Xenial driver that only manages NICs that are not 
supported by the regular Xenial driver. Since the backported driver lives in 
the special location kernel/ubuntu/bnxt it's not automatically included in the 
initramfs. But it's boot-critical so it needs to be added to the initramfs.

  [Test Case]
  Install the Xenial kernel on hardware that contains a newer Broadcom NIC and 
boots over that NIC. The machine will not come up because the NIC is not 
recognized.

  [Regression Risk]
  The driver is only loaded for newer Broadcom NICs. Older NICs are still 
managed by the regular Xenial driver, so there should be no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1712491/+subscriptions

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

[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

This bug was fixed in the package gcc-5 - 5.4.0-6ubuntu1~16.04.5

---
gcc-5 (5.4.0-6ubuntu1~16.04.5) xenial-proposed; urgency=medium

  * SRU
  * Fix PR target/77267 (x86), taken from the trunk. LP: #1623418.
  * Fix hangs w/ asan binaries on arm64 (Dann Frazier). LP: #1709727.
  * Linaro branch only: Fix PR target/79041, aarch64 backend emitting
R_AARCH64_ADR_PREL_PG_HI21 relocation despite -mpc-relative-literal-loads
option being used (Dan Frazier). LP: #1695093.

 -- Matthias Klose   Wed, 23 Aug 2017 11:35:00 +0200

** Changed in: gcc-5 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1623418

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in binutils source package in Yakkety:
  Won't Fix
Status in gcc-5 source package in Yakkety:
  Won't Fix
Status in gcc-6 source package in Yakkety:
  Won't Fix

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

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

[Touch-packages] [Bug 1720980] Re: Traditional decorations are offsetted when window toggle beetween focus to unfocus when maximized

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20171003-0ubuntu1

---
ubuntu-themes (16.10+17.10.20171003-0ubuntu1) artful; urgency=medium

  * Fix traditional decorations offset when window toggle beetween focus to
unfocus when maximized (LP: #1720980)
  * Fix suggested actions hovering color on unfocused window.

 -- Didier Roche   Wed, 04 Oct 2017 15:41:53 +0200

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1720980

Title:
  Traditional decorations are offsetted when window toggle beetween
  focus to unfocus when maximized

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  1. Open gnome-terminal and maximize it
  2. focus the window
  3. unfocus the window
  -> you will see a 2px shift down once the window is focused. This moves the 
content as well and is visually disturbing, especially when the ncurse 
application like weechat removes and relayout due to this.

  Remove the border for those kind of window, which don't show up real
  headerbar, but a traditional window title bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1720980/+subscriptions

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

[Touch-packages] [Bug 1721294] [NEW] Unattended upgrade fails with "Error in function"

2017-10-04 Thread Marius Gedminas

Public bug reported:

This is the cron email I received today:

From: root 
To: r...@pov.lt
Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False'
Date: Wed,  4 Oct 2017 03:40:19 +0300 (EEST)

Unattended upgrade returned: False

Packages that attempted to upgrade:
 ca-certificates libidn11 libnss3 libnss3-nssdb

Package installation log:
Error in function:

Unattended-upgrades log:
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=trusty-security', 'o=UbuntuESM,a=trusty', 
'o=Ubuntu,a=trusty-security', 'o=Ubuntu,a=trusty-updates', 
'origin=LP-PPA-pov,suite=trusty']
Packages that will be upgraded: ca-certificates libidn11 libnss3 
libnss3-nssdb
Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
Installing the upgrades failed!
error message: 'installArchives() failed'
dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
 for details
Packages that are auto removed: ''
Packages auto-removed

The named log file, var/log/unattended-upgrades/unattended-upgrades-
dpkg_2017-10-04_03:40:17.411277.log contains only this:

Error in function:

That's it.

Now given that ca-certificates is involved, I suspect this may be
related to non-ASCII filenames (see bug 1554365), but unlike that bug,
here the upgrade fails instead of succeeding, and the actual error is
not shown anywhere.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unattended-upgrades 0.82.1ubuntu2.5
Uname: Linux 2.6.32-042stab124.2 x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Wed Oct  4 18:54:54 2017
PackageArchitecture: all
ProcEnviron:
 LC_CTYPE=lt_LT.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1721294

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  This is the cron email I received today:

  From: root 
  To: r...@pov.lt
  Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False'
  Date: Wed,  4 Oct 2017 03:40:19 +0300 (EEST)

  Unattended upgrade returned: False

  Packages that attempted to upgrade:
   ca-certificates libidn11 libnss3 libnss3-nssdb

  Package installation log:
  Error in function:

  Unattended-upgrades log:
  Initial blacklisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=trusty-security', 
'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 
'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty']
  Packages that will be upgraded: ca-certificates libidn11 libnss3 
libnss3-nssdb
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
  Installing the upgrades failed!
  error message: 'installArchives() failed'
  dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
 for details
  Packages that are auto removed: ''
  Packages auto-removed

  The named log file, var/log/unattended-upgrades/unattended-upgrades-
  dpkg_2017-10-04_03:40:17.411277.log contains only this:

  Error in function:

  That's it.

  Now given that ca-certificates is involved, I suspect this may be
  related to non-ASCII filenames (see bug 1554365), but unlike that bug,
  here the upgrade fails instead of succeeding, and the actual error is
  not shown anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.5
  Uname: Linux 2.6.32-042stab124.2 x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 18:54:54 2017
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions

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

[Touch-packages] [Bug 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.

2017-10-04 Thread vbargsten

Have the same problem on opensuse. #17 fixes it for me, thank you for
the info.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992

Title:
  Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
  denied.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After updating from 8.04 to 12.04 I cannot use rfcomm without sudo.

  I've already added the user  to group 'dialout' .

  Temporary I tried to change udev.rules (KERNEL=="rfcomm[0-9]*", 
GROUP="dialout", MODE="666")  but this doesn't
  solve the problem so I removed it again.

  Here the commands I used :

  burki@orion:/$ hcitool scan
  Scanning ...
   00:12:6F:08:98:FFGEO LE-71 1

  burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF
  Can't open RFCOMM device: Permission denied

  burki@orion:/$ ls -l /dev/rfcomm1
  ls: cannot access /dev/rfcomm1: No such file or directory

  burki@orion:/$ groups
  burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse 
scanner lpadmin netdev sambashare

  burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF
  Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1
  Press CTRL-C for hangup

  In another terminal while connection is running ...

  burki@orion:/$ ls -l /dev/rfcomm1
  crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1

  burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1)
  (I've stolen this command from another bug report #570692.  Output is very 
long. Please see attachment)

  WORKAROUND: sudo chmod u+s /usr/bin/rfcomm

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  burki  1730 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 56'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0887,10438444,00100302 
HDA:80862805,80862805,0010'
     Controls  : 49
     Simple ctrls  : 21
  Date: Tue Jun 19 09:15:54 2012
  HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae 
root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-25-generic-pae N/A
   linux-backports-modules-3.2.0-25-generic-pae  N/A
   linux-firmware1.79
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1721260] Re: Bug Report for Canon LBP1120

2017-10-04 Thread Till Kamppeter

Please follow the instructions on

https://wiki.ubuntu.com/DebuggingPrintingProblems

for useful printing-related bug reports. Thanks.

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1721260

Title:
  Bug Report for Canon LBP1120

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Strange nothing has changed, other than updates to Linux KERNEL(S).

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

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

[Touch-packages] [Bug 1721288] [NEW] indicator-network: FTBFS: error: ‘function’ was not declared in this scope

2017-10-04 Thread Andreas Moog

Public bug reported:

The package indicator-network failed to Build in the current Ubuntu
development version:

Full log at: https://launchpadlibrarian.net/338219183/buildlog_ubuntu-
artful-amd64.indicator-
network_0.9.0+17.04.20170322-0ubuntu1_BUILDING.txt.gz

cd 
/<>/indicator-network-0.9.0+17.04.20170322/obj-x86_64-linux-gnu/src/qdbus-stubs
 && /usr/lib/x86_64-linux-gnu/qt5/bin/moc 
@/<>/indicator-network-0.9.0+17.04.20170322/obj-x86_64-linux-gnu/src/qdbus-stubs/NetworkManagerSettingsConnectionInterface.moc_parameters
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:
 In function ‘void runGMainloop(guint)’:
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:30:
 error: ‘function’ was not declared in this scope
 util::ResourcePtr> timer(g_timeout_add(ms,
  ^~~~
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:30:
 note: suggested alternative: ‘GAction’
 util::ResourcePtr> timer(g_timeout_add(ms,
  ^~~~
  GAction
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:50:
 error: template argument 2 is invalid
 util::ResourcePtr> timer(g_timeout_add(ms,
  ^~
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:38:25:
 error: expression list treated as compound expression in initializer 
[-fpermissive]
 _source_remove);
 ^
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:38:25:
 error: invalid conversion from ‘gboolean (*)(guint) {aka int (*)(unsigned 
int)}’ to ‘int’ [-fpermissive]
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:53:
 warning: unused variable ‘timer’ [-Wunused-variable]
 util::ResourcePtr> timer(g_timeout_add(ms,
 ^
[ 30%] Building CXX object 
src/menumodel-cpp/CMakeFiles/menumodel_cpp.dir/action.cpp.o

** Affects: indicator-network (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs

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

** Tags added: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1721288

Title:
  indicator-network: FTBFS: error: ‘function’ was not declared in this
  scope

Status in indicator-network package in Ubuntu:
  New

Bug description:
  The package indicator-network failed to Build in the current Ubuntu
  development version:

  Full log at: https://launchpadlibrarian.net/338219183/buildlog_ubuntu-
  artful-amd64.indicator-
  network_0.9.0+17.04.20170322-0ubuntu1_BUILDING.txt.gz

  cd 
/<>/indicator-network-0.9.0+17.04.20170322/obj-x86_64-linux-gnu/src/qdbus-stubs
 && /usr/lib/x86_64-linux-gnu/qt5/bin/moc 
@/<>/indicator-network-0.9.0+17.04.20170322/obj-x86_64-linux-gnu/src/qdbus-stubs/NetworkManagerSettingsConnectionInterface.moc_parameters
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:
 In function ‘void runGMainloop(guint)’:
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:30:
 error: ‘function’ was not declared in this scope
   util::ResourcePtr> timer(g_timeout_add(ms,
^~~~
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:30:
 note: suggested alternative: ‘GAction’
   util::ResourcePtr> timer(g_timeout_add(ms,
^~~~
GAction
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:50:
 error: template argument 2 is invalid
   util::ResourcePtr> timer(g_timeout_add(ms,
^~
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:38:25:
 error: expression list treated as compound expression in initializer 
[-fpermissive]
   _source_remove);
   ^
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:38:25:
 error: invalid conversion from ‘gboolean (*)(guint) {aka int (*)(unsigned 
int)}’ to ‘int’ [-fpermissive]
  
/<>/indicator-network-0.9.0+17.04.20170322/src/menumodel-cpp/gio-helpers/util.cpp:31:53:
 warning: unused variable ‘timer’ [-Wunused-variable]
   util::ResourcePtr> timer(g_timeout_add(ms,
   ^
  [ 30%] Building CXX object

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-10-04 Thread Thomas

I guess I'll have to go back to 16.04 or 16.10, despite someone
providing a bugfix and several people confirming it, nobody from Ubuntu
seems to care.  Crazy, considering how much corporate employees depend
on such BASIC features like this working.  Very disappointing.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-10-04 Thread Alexander Adam

I can confirm what Jess (jbermudes) wrote: issue can't be solved in
17.04 with the proposal so I hope for the best in 17.10.

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1575078

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions

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

[Touch-packages] [Bug 1721278] [NEW] apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"

2017-10-04 Thread Paul Menzel

Public bug reported:

With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7,
in the system log each second the error message below is printed to.

```
[…]
[Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
[Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
[Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
[Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
[…]
```

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1721278

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"

Status in apparmor package in Ubuntu:
  New

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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

[Touch-packages] [Bug 1721260] Re: Bug Report for Canon LBP1120

2017-10-04 Thread Colin Watson

** Project changed: launchpad => cups (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1721260

Title:
  Bug Report for Canon LBP1120

Status in cups package in Ubuntu:
  New

Bug description:
  Strange nothing has changed, other than updates to Linux KERNEL(S).

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

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

[Touch-packages] [Bug 1721260] [NEW] Bug Report for Canon LBP1120

You have been subscribed to a public bug:

Strange nothing has changed, other than updates to Linux KERNEL(S).

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

-- 
Bug Report for Canon LBP1120
https://bugs.launchpad.net/bugs/1721260
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

2017-10-04 Thread Andreas Hasenack

@aleandrodasilva, which error is the same? We have established that the
"Failed to preset unit" messages are harmless.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1658273

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

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

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

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

2017-10-04 Thread Andy Whitcroft

** Also affects: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1712491

Title:
  Add backported bnxt driver to the initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  New
Status in initramfs-tools source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  We're adding a backported bnxt driver to Xenial (LP #1711056). It's an 
alternate for the regular Xenial driver that only manages NICs that are not 
supported by the regular Xenial driver. Since the backported driver lives in 
the special location kernel/ubuntu/bnxt it's not automatically included in the 
initramfs. But it's boot-critical so it needs to be added to the initramfs.

  [Test Case]
  Install the Xenial kernel on hardware that contains a newer Broadcom NIC and 
boots over that NIC. The machine will not come up because the NIC is not 
recognized.

  [Regression Risk]
  The driver is only loaded for newer Broadcom NICs. Older NICs are still 
managed by the regular Xenial driver, so there should be no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1712491/+subscriptions

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

[Touch-packages] [Bug 1715131] Re: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID

checked with 229-4ubuntu20 aging and priority parsed and set correctly,
DefaultPVID is parsed correctly but not set. Will fix DefaultPVID
setting in the next SRU. This SRU thus doesn't regress any settings and
has only partial DefaultPVID key support.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1715131

Title:
  networkd add support for Bridge Priority, AgeingTimeSec and
  DefaultPVID

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

Bug description:
  [Impact]
  Newer releases of networkd support more optional settings for Bridge 
Priority, AgeingTimeSec and DefaultPVID.

  
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#AgeingTimeSec=
  https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#Priority=
  
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID=

  Backporting these features to xenial, allows to use/set these options
  via netplan for any releases as for example deployed by MAAS.

  [Fix]
  cherrypick these settings for better supportability of networkd on xenial 
with netplan.

  [Testcase]
  1) Create .netdev bridge device
  2) Specify Priority, AgeingTimeSec, DefaultPVID settings in the [Bridge] 
section
  3) Verify that there are no parsing errors in journalctl from systemd-netword
  4) Verify with `ip` command that the bridge device got created
  5) Verify in sysfs that the settings requested have been applied to the device

  [Regression]
  These stanazas are optional, and will be ignored by older networkd if for 
example users start using them, and downgrade networkd to the one in release 
pocket. It is future compatible settings that will not cause upgrade issues, 
nor could result in failure to create the bridge device.

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

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

[Touch-packages] [Bug 1720980] Re: Traditional decorations are offsetted when window toggle beetween focus to unfocus when maximized

2017-10-04 Thread Didier Roche

** Changed in: ubuntu-themes
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1720980

Title:
  Traditional decorations are offsetted when window toggle beetween
  focus to unfocus when maximized

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  1. Open gnome-terminal and maximize it
  2. focus the window
  3. unfocus the window
  -> you will see a 2px shift down once the window is focused. This moves the 
content as well and is visually disturbing, especially when the ncurse 
application like weechat removes and relayout due to this.

  Remove the border for those kind of window, which don't show up real
  headerbar, but a traditional window title bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1720980/+subscriptions

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

Used 229-4ubuntu19, added set +x at the top of the init-top/udev script
and booted with break=bottom to clearly observe initramfs boot messages
and check that there is only one (devices) trigger.

Upgraded to 229-4ubuntu20, added set +x at the top of the init-top/udev
script booted again and clearly boserved that subsystems and devices are
triggered.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713536

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions

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

[Touch-packages] [Bug 1721257] [NEW] System error

2017-10-04 Thread Edwin Fountain

Public bug reported:

not sure what location or why bug accursed...

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct  4 09:45:21 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] RS482M [Mobility Radeon Xpress 200] 
[1025:010f]
InstallationDate: Installed on 2017-09-02 (31 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 1c4f:0034 SiGma Micro 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer, inc. Aspire 5050
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=140a685c-2294-41c1-ac06-e3ffdf19e1ae ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/07
dmi.bios.vendor: Acer
dmi.bios.version: v1.3309
dmi.board.name: Prespa M
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrv1.3309:bd04/17/07:svnAcer,inc.:pnAspire5050:pvrNotApplicable:rvnAcer,Inc.:rnPrespaM:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 5050
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Wed Oct  4 08:59:22 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: radeon

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1721257

Title:
  System error

Status in xorg package in Ubuntu:
  New

Bug description:
  not sure what location or why bug accursed...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct  4 09:45:21 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] RS482M [Mobility Radeon Xpress 200] 
[1025:010f]
  InstallationDate: Installed on 2017-09-02 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 1c4f:0034 SiGma Micro 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer, inc. Aspire 5050
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-10-04 Thread Dr. Thomas Orgis

Oh … this is _another_ bug. We are dealing here with the situation that
mdmon controlling rootfs on RAID is not handled at all with Ubuntu
initrd, while this new CentOS issue is a bug in said handling in the
CentOS initrd …

The reference is valuable nevertheless … not least because I have
systems about to be upgraded to CentOS 7.4 that might get hit by this
bug!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1587142

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio

[Touch-packages] [Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected

** No longer affects: systemd (Ubuntu Zesty)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1698734

Title:
  systemd-resolved spams syslog whenever I'm disconnected

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  Every time I suspend my laptop and resume in a situation where I don't have 
connectivity
  I get big syslog spam from systemd-resolved. See for instance yesterday when 
I went out:

  Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  ...

  And the last messages of the "episode":

  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron NetworkManager[30674]:   [1497809608.0889] 
device (wlp2s0): supplicant interface state: associ
  ated -> 4-way handshake

  So this correspond to roughly 85 minutes of disconnection, during
  which I got...

  $ grep  "fallback DNS" /var/log/syslog.1 | wc -l
  444066

  This correspond to 5224 messages/minute,  87 messages/second

  I had a few other episodes in the last week, including a 4h train
  roundtrip:

  $ zgrep  "fallback DNS" /var/log/syslog* | wc -l
  1964217

  I noticed the bug during the trip, when the SSD activity was slowing
  my machine in a clearly noticeable way.

  I'm running:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print 
$1}')
  systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
   *** 232-21ubuntu3 500
  500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

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

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

[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

** Description changed:

+ [Impact]
+ In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.
+ 
+ [Testcase]
+ Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
+ More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916
+ 
+ [Butfix]
+ Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318
+ 
+ [Regression Potential]
+ The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.
+ 
+ [Original Bug report / request]
+ 
  Hi,
  
  We have a blocking issue in systemd for the following release
  
  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ```
  
  This release runs systemd229, we are affected by the following auto-
  mouting race condition
  
  ```
  https://github.com/systemd/systemd/pull/5916
  ```
  
  Is back porting  the fix to the release 229 an option?
  
  Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1709649

Title:
  229 backport for  race between explicit mount and handling automount

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Triaged
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.

  [Testcase]
  Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
  More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916

  [Butfix]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318

  [Regression Potential]
  The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.

  [Original Bug report / request]

  Hi,

  We have a blocking issue in systemd for the following release

  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ```

  This release runs systemd229, we are affected by the following auto-
  mouting race condition

  ```
  https://github.com/systemd/systemd/pull/5916
  ```

  Is back porting  the fix to the release 229 an option?

  Regards.

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

2017-10-04 Thread Iain Lane

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  By default settings unattended-upgrade is unable to automatically
  remove packages that become unused in conjunction with updating by
  other software.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1685273] Re: Gedit/Text Editor tabs hard to distinguish under Ambiance

2017-10-04 Thread Iain Lane

(cleaning up the tracking list; valid bug but not RC)

** Tags added: rls-aa-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1685273

Title:
  Gedit/Text Editor tabs hard to distinguish under Ambiance

Status in ubuntu-themes package in Ubuntu:
  Triaged
Status in ubuntu-themes source package in Artful:
  Triaged

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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

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

[Touch-packages] [Bug 1718254] Re: please drop url-dispatcher dependencies

2017-10-04 Thread Iain Lane

Not sure desktop is going to have time to work on this for 17.10.

** Tags added: rls-aa-notfixinf

** Tags removed: rls-aa-notfixinf
** Tags added: rls-aa-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1718254

Title:
  please drop url-dispatcher dependencies

Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in unity-greeter-session-broadcast package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  New
Status in indicator-datetime source package in Artful:
  New
Status in indicator-network source package in Artful:
  New
Status in indicator-power source package in Artful:
  New
Status in indicator-sound source package in Artful:
  New
Status in unity-greeter-session-broadcast source package in Artful:
  New
Status in unity-scopes-api source package in Artful:
  New

Bug description:
  please drop url-dispatcher dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1718254/+subscriptions

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

[Touch-packages] [Bug 1708912] Re: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1708912

Title:
  package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  cannot install that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gdbserver 7.11.1-0ubuntu1~16.5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Aug  6 15:38:04 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:gdbserver:7.11.1-0ubuntu1~16.5
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package gdbserver (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-25 (42 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gdb
  Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2017-10-04 Thread Oliver Grawert

** Summary changed:

- Networkd fail to set ip address between leases if ip address changes
+ Networkd fail to set ip address between leases if ip address changes on 
UbuntuCore

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721223

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  Hi there, 
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity. 
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and valid_lft
  fields for the interested network interface.

  Please note that if the ip address setting are the same between leases
  the problem doesn’t jump out.

  Please note that if the ip address setting are different between lease
  the problem jumps out and it is very bad:

  Typically the lease time on consumer router are about some day, then a
  board that change ip between lease loses the network connectivity for
  some day without a direct action.

  Please, after a confirmation from your side of the issue, could you
  fix the problem or escalate the issue at the upstream project?

  We are available for further testing.

  Below syslog annotated with ip address state:

  
  Oct  4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:49:25 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
  Oct  4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
  Oct  4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Oct  4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
  Oct  4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:54:23 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
  Oct  4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Oct  4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
  Oct  4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
  Oct  4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 10:00:17 localhost rsyslogd-2007: action

[Touch-packages] [Bug 1721223] [NEW] Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2017-10-04 Thread Nicolino Curalli

Public bug reported:

Hi there, 
we found a replicable issue that involves the Ubuntu Core networking and causes 
complete loss of connectivity. 
We run a custom board with ubuntu core: the architecure is amrhf.
We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: 
other platform was been tested.
It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

Below steps to replicate the issue.

1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
2)Boot the board and wait for get an ip from dhcp server
3)Before the lease expires, set a reservation for a different ip address

Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
Depending on lease duration before the second lease expires ( for 10 minure we 
have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

During the test the dhcp server records correctly leases and their
duration.

We check directly from console the network interface setting with the
tool ip, checking continuously the value for ip address and valid_lft
fields for the interested network interface.

Please note that if the ip address setting are the same between leases
the problem doesn’t jump out.

Please note that if the ip address setting are different between lease
the problem jumps out and it is very bad:

Typically the lease time on consumer router are about some day, then a
board that change ip between lease loses the network connectivity for
some day without a direct action.

Please, after a confirmation from your side of the issue, could you fix
the problem or escalate the issue at the upstream project?

We are available for further testing.

Below syslog annotated with ip address state:


Oct  4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:49:25 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
Oct  4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
Oct  4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
Oct  4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
Oct  4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:54:23 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
Oct  4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
Oct  4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
Oct  4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
Oct  4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct  4 10:01:48 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 10:03:18 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

Oct  4 10:03:05 localhost systemd-networkd[623]: eth0: DHCPv4 address
192.168.5.124/24 via 192.168.5.1 -> here begin two ip address state

Oct  4 10:03:05 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
Oct  4 10:03:05 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
Oct  4 10:03:05 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
Oct  4 10:03:15 localhost systemd-timesyncd[996]: Timed out waiting for reply 
from 91.189.89.199:123 (ntp.ubuntu.com).

[Touch-packages] [Bug 1720342] Re: After update to kernel 4.13, can no longer connect Bluetooth Speaker (Sony SRS-SB40)

2017-10-04 Thread Slomo

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

** This bug has been marked a duplicate of bug 1719210
   Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 
to 4.13 in artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1720342

Title:
  After update to kernel 4.13, can no longer connect Bluetooth Speaker
  (Sony SRS-SB40)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Speaker / Microphone worked perfectly with linux kernel 4.12, and
  still does if I reboot into that kernel. But it doesn't work with
  4.13, or 4.13.1 which I just installed (from mainline kernel
  repository). Haven't tried 4.14 yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  2150 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 13:24:11 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-19 (101 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.54
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720342/+subscriptions

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

[Touch-packages] [Bug 1721217] [NEW] package ca-certificates 20170717~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-10-04 Thread Dr. Heimo Wissing

Public bug reported:

..at installation of the update, the update installer reported the bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20170717~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Oct  4 11:46:21 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2013-09-23 (1471 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.25
SourcePackage: ca-certificates
Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2016-08-18 (411 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1721217

Title:
  package ca-certificates 20170717~16.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  ..at installation of the update, the update installer reported the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Oct  4 11:46:21 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-09-23 (1471 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.25
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-18 (411 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1721217/+subscriptions

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

[Touch-packages] [Bug 1720342] Re: After update to kernel 4.13, can no longer connect Bluetooth Speaker (Sony SRS-SB40)

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1720342

Title:
  After update to kernel 4.13, can no longer connect Bluetooth Speaker
  (Sony SRS-SB40)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Speaker / Microphone worked perfectly with linux kernel 4.12, and
  still does if I reboot into that kernel. But it doesn't work with
  4.13, or 4.13.1 which I just installed (from mainline kernel
  repository). Haven't tried 4.14 yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  2150 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 13:24:11 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-19 (101 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.54
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720342/+subscriptions

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

[Touch-packages] [Bug 1721217] Re: package ca-certificates 20170717~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-10-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1721217

Title:
  package ca-certificates 20170717~16.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  ..at installation of the update, the update installer reported the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Oct  4 11:46:21 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-09-23 (1471 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.25
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-18 (411 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1721217/+subscriptions

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

[Touch-packages] [Bug 1711752] Re: Some right click items are untranslated

2017-10-04 Thread Didier Roche

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu Artful) =>
glib2.0 (Ubuntu Artful)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1711752

Title:
  Some right click items are untranslated

Status in glib2.0 package in Ubuntu:
  Triaged
Status in glib2.0 source package in Artful:
  Triaged

Bug description:
  When clicking the icons of Terminal, Nautilus etc., some things are
  being shown as the untranslated (English) strings even though they are
  translated upstream (GNOME). For example the "New Terminal" for GNOME
  Terminal, that is correctly translated (in Czech localization) as
  "Nový terminál" in GNOME panel, but untranslated when clicking the
  GNOME Terminal icon in the ubuntu-dock extension. Another example is
  the "New Window" item in Nautilus. See the attached screenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1711752/+subscriptions

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

[Touch-packages] [Bug 1711752] [NEW] Some right click items are untranslated