date:20170906

Just reinstalled again and got the old message again:

[ ***  ] (2 of 2) A start job is running for Hold until boot process
finishes up (21s / no limit)

** Description changed:

  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:
  
+ [ ***  ] (2 of 2) A start job is running for Hold until boot process
+ finishes up (21s / no limit)
+ 
+ or
+ 
  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)
  
+ ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

** Summary changed:

- A live session can't be terminated properly due to "[ ***  ] (2 of 2) A start 
job is running for Wait for Network to be Configured (21s / no limit)"
+ A live session can't be terminated properly due to "[ ***  ] (2 of 2) A start 
job is running for ... (21s / no limit)"

** Summary changed:

- A live session can't be terminated properly due to "[ ***  ] (2 of 2) A start 
job is running for ... (21s / no limit)"
+ A live session can't be shut down due to "[ ***  ] (2 of 2) A start job is 
running for ... (21s / no limit)"

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+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 735665] [NEW] Impossible to disable middle-click paste without breaking the middle mouse button

You have been subscribed to a public bug:

I've found plenty of forum posts from other people complaining about
this but I couldn't find an existing but report in Launchpad.

It baffles me to find that there is no way to disable the middle-click
screen buffer "paste" feature without breaking the middle-click button
on the mouse altogether.  I'm sure there are lots of people who think
it's nifty.  However, for me and others, it is just annoying.

If I am scrolling in a text editor like Gedit and the middle-click
button actually gets pressed, it often pastes a chunk of text in the
middle of the document and I don't notice because I scroll right by.
This leads to trouble later on.

My searching indicates that a common solution to this problem is to re-
map the middle-click button to something else (so that it behaves like
either the left or right button, or just does nothing), using xinput or
by editing Xorg.conf.  However, this breaks other applications that use
the middle mouse button for other things (opening and closing tabs in
Firefox, middle-click scroll).

There should be a solution to this problem other than "map the middle-
click button to something else" and "get a new mouse that doesn't
accidentally click."  I don't care if it's setting an option in an
obscure text file.


To reproduce:

 - Open Gedit.
 - Type some text.
 - Select some text.
 - Middle-click somewhere in the document.
 - Selected text is copied to where you middle-clicked.
 - No (documented) way to disable this behavior without re-mapping the 
middle-mouse button, breaking other middle-click functionality.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntu-desktop 1.207
ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic x86_64
Architecture: amd64
Date: Tue Mar 15 15:00:42 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta

** Affects: gnome-settings-daemon
 Importance: Medium
 Status: Confirmed

** Affects: xorg-server
 Importance: Medium
 Status: Won't Fix

** Affects: gtk+3.0 (Ubuntu)
 Importance: Wishlist
 Status: Fix Released


** Tags: amd64 apport-bug maverick
-- 
Impossible to disable middle-click paste without breaking the middle mouse 
button
https://bugs.launchpad.net/bugs/735665
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.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 1706939] Re: A live session can't be terminated properly due to "[ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit)"

** Description changed:

  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
- Hangs basically forever'
+ Hangs basically forever with:
+ 
+ [ *** ] (2 of 2) A start job is running for Wait for Network to be
+ Configured (21s / no limit)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

Title:
  A live session can't be terminated properly due to "[ ***  ] (2 of 2)
  A start job is running for Wait for Network to be Configured (21s / no
  limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+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 1706939] Re: A live session can't be terminated properly due to "[ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit)"

It's still happening (slightly different message?) with last night's Sep
6 image.

** Summary changed:

- A live session can't be terminated properly due to "[***   ]A start job is 
running for Hold for boot processes to finish up(XX/no limit)
+ A live session can't be terminated properly due to "[ ***  ] (2 of 2) A start 
job is running for Wait for Network to be Configured (21s / no limit)"

** Also affects: systemd (Ubuntu)
   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/1706939

Title:
  A live session can't be terminated properly due to "[ ***  ] (2 of 2)
  A start job is running for Wait for Network to be Configured (21s / no
  limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

** Summary changed:

- can't lock screen with keyboard shortcuts
+ Can't lock screen with keyboard shortcuts when using lightdm

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

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

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

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  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/1715435/+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 1553669] Re: Annoying "call from" message

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

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

** Tags added: a2dp

** Summary changed:

- Annoying "call from" message
+ Annoying "call from" message when connecting Bose devices

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1704508] Re: add-apt-repository traceback when hitting ctrl-c

** Branch linked: lp:software-properties

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

Title:
  add-apt-repository traceback when hitting ctrl-c

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  add-apt-repository says to hit ctrl-c to cancel adding a PPA.  Then it
  tracebacks when you do:

  ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
   This PPA holds new upstream development releases, usually development 
releases. Currently, it is holding the 2.2 series.
   More info: https://launchpad.net/~maas/+archive/ubuntu/next
  Press [ENTER] to continue or ctrl-c to cancel adding it
  ^CTraceback (most recent call last):
File "/usr/bin/add-apt-repository", line 143, in 
  sys.stdin.readline()
  KeyboardInterrupt

  
  I understand why the trace is generated, but this is ugly (users should never 
see tracebacks for known conditions, IMO).  

  The KeyboardInterrupt exception should be handled properly like any
  other exception.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Fri Jul 14 23:17:57 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1704508/+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 1704508] Re: add-apt-repository traceback when hitting ctrl-c

2017-09-06 Thread Brian Murray

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

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  add-apt-repository traceback when hitting ctrl-c

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  add-apt-repository says to hit ctrl-c to cancel adding a PPA.  Then it
  tracebacks when you do:

  ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
   This PPA holds new upstream development releases, usually development 
releases. Currently, it is holding the 2.2 series.
   More info: https://launchpad.net/~maas/+archive/ubuntu/next
  Press [ENTER] to continue or ctrl-c to cancel adding it
  ^CTraceback (most recent call last):
File "/usr/bin/add-apt-repository", line 143, in 
  sys.stdin.readline()
  KeyboardInterrupt

  
  I understand why the trace is generated, but this is ugly (users should never 
see tracebacks for known conditions, IMO).  

  The KeyboardInterrupt exception should be handled properly like any
  other exception.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Fri Jul 14 23:17:57 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1704508/+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 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

2017-09-06 Thread jzacsh

fwiw, this has been happening to my laptop for a couple months (i just
now had the time to look into the logs). i've had the laptop for a year
(samsung ativ book 9) without problems before this.

I get continuous log output from the kernel for as long as the lid is
closed, and my laptop is unrecoverable until hard rebooted (eg: close my
laptop, stick in bag, then 4 hours later I'll have 16M of logs[1]; 400+
log-lines a second).

It seems everything[2] failing -- NetworkManager, sd-resolve, syncthing
-- to shutdown is networking related, at least today. I'll start looking
at this more in the future, as this happens to me (6 boots ago was only
`cups-browsed`).

I'm on 4.10.0-34-generic, and Ubuntu 16.04.1.

Please let me know if I can add anything useful to this thread.

[1]: measuring the output of: journalctl --catalog --boot -1  | sed -n 
'/kernel:\ Freezing\ of\ tasks\ failed\ after/,$p'
[2]: i'm guessing here; not much experience reading these logs. this is based 
on the output of: journalctl --catalog --boot -1  | grep -A 1 -E 'kernel:\ 
*Freezing\ of\ tasks\ failed\ after'  | grep -v 'Freezing.of.tasks.failed' | 
cut -f 6 -d ' ' | sort | uniq # (ie: looking at the reported process just after 
the kernel "freezing failed" line).

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1680421] Re: Computer suspends/sleeps before login

2017-09-06 Thread Jonatã Bolzan Loss

Error still present on Ubuntu 17.10 (daily builds)

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

Title:
  Computer suspends/sleeps before login

Status in systemd:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  I am not able to login into the system because it sleeps in the boot
  process. To fix this, I need to edit (in recovery mode) the
  /etc/systemd/logind.conf to replace the following options:

  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore

  This behaviour started in Ubuntu 14.10.

  Some other users have this issue too:
  
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  6 08:25:20 2017
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
  MachineType: Positivo Positivo Mobile
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: M5X0V
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Positivo Mobile
  dmi.product.version: VT6198
  dmi.sys.vendor: Positivo
  mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1680421/+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 1715481] [NEW] wget -N ignores file size differences

2017-09-06 Thread Andrew

Public bug reported:

The man page states:

"The time-stamping in GNU Wget is turned on using ‘--timestamping’
(‘-N’) option, or through timestamping = on directive in .wgetrc. With
this option, for each file it intends to download, Wget will check
whether a local file of the same name exists. If it does, and the remote
file is not newer, Wget will not download it.

If the local file does not exist, or the sizes of the files do not
match, Wget will download the remote file no matter what the time-stamps
say. "

Note the last sentence carefully:  "...the sizes of the files do not
match... no matter what the timestamps say."

To duplicate:
wget -N 
cp /dev/null 
wget -N 

Note, it will state "HTTP request sent, awaiting response... 304 Not Modified
File ‘’ not modified on server. Omitting download.

Obviously the sizes of the files do not match and it should download the
file.  You can also edit the file and manually delete (or add I suppose)
a few lines.

Not related, however I would like to also point out that if I change the
string "$1000" to "$4000" in a document on the remote, the size of the
file does not change, however the files and data are clearly different.
This case usage would break anything depending on actual changes.  Such
as automatically getting a vendor's price lists, not just changes to
what is essentially the outer envelope of the file. Kind of important,
no?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wget 1.17.1-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep  6 12:42:20 2017
InstallationDate: Installed on 2016-09-11 (359 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: wget
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  wget -N ignores file size differences

Status in wget package in Ubuntu:
  New

Bug description:
  The man page states:

  "The time-stamping in GNU Wget is turned on using ‘--timestamping’
  (‘-N’) option, or through timestamping = on directive in .wgetrc. With
  this option, for each file it intends to download, Wget will check
  whether a local file of the same name exists. If it does, and the
  remote file is not newer, Wget will not download it.

  If the local file does not exist, or the sizes of the files do not
  match, Wget will download the remote file no matter what the time-
  stamps say. "

  Note the last sentence carefully:  "...the sizes of the files do not
  match... no matter what the timestamps say."

  To duplicate:
  wget -N 
  cp /dev/null 
  wget -N 
  
  Note, it will state "HTTP request sent, awaiting response... 304 Not Modified
  File ‘’ not modified on server. Omitting download.

  Obviously the sizes of the files do not match and it should download
  the file.  You can also edit the file and manually delete (or add I
  suppose) a few lines.

  Not related, however I would like to also point out that if I change
  the string "$1000" to "$4000" in a document on the remote, the size of
  the file does not change, however the files and data are clearly
  different.  This case usage would break anything depending on actual
  changes.  Such as automatically getting a vendor's price lists, not
  just changes to what is essentially the outer envelope of the file.
  Kind of important, no?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  6 12:42:20 2017
  InstallationDate: Installed on 2016-09-11 (359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: wget
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1715481/+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 1714596] Re: PDF images are blank

2017-09-06 Thread Seth Arnold

Even Rouault has been checking in a huge number of fixes for upstream
openjpeg, and he's been remarkably responsive to Agostino Sarubbo's
fuzzing efforts. I suspect the next time I review the openjpeg codebase
I'll find something far more sustainable than the last time around.

Thanks

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1714596/+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 1699216] Re: Encrypted home support

2017-09-06 Thread Jeremy Soller

I have extra whitespace changes in there, I will resubmit with `-w`

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support

2017-09-06 Thread Jeremy Soller

tsimonq2, here id a debdiff file

** Patch added: "Accountservice Encrypt Home Debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945505/+files/accountsservice_encrypt_home.debdiff

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support

2017-09-06 Thread Jeremy Soller

Here is a better patch, ignoring whitespace changes.

** Patch added: "accountsservice_encrypt_home.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1715476] [NEW] Incorrect icon on wireless connection

2017-09-06 Thread Sancho

Public bug reported:

On my new installation of Xenial, the Network Manager behaves strangely.

When I booted the first time with no known networks, I received a notification
about available networks.
I checked the list of available, created one configuration and connected.
So far, OK.
However, after restart, when the notebook boots and there is already a known
network, it connects, but instead of wireless signal strength the nm applet
displays icon for wired network.
Connection information shows it is a wifi network (Interface: 802.11 WiFi
(wlp63s0)), but reports very weird speed (6 Mb/s) - the real speed is ~200
Mb/s. Also, the list of available networks is empty.
Opening nmtui and listing connections in "Activate a connection" I can see
other networks.
But the applet shows no wireless networks and sometimes does not even show the
disconnect item in wireless (sometimes it does). I did not recognize a pattern
when it shows the menu item and when it does not.
When I run `sudo service network-manager restart`, everything fixes to the
proper state - I seen wlan icon, available networks, only connection
information keeps telling me I am connected with 6Mb/s.
The package version is 1.2.6-0ubuntu0.16.04.1.
The wireless adapter is Qualcomm Atheros QCA6174 802.11ac, using module
ath10k_pci.

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

** Tags: atheros icon wireless

** Attachment added: "NetworkManager problem.png"

https://bugs.launchpad.net/bugs/1715476/+attachment/4945506/+files/NetworkManager%20problem.png

** Attachment removed: "NetworkManager problem.png"

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1715476/+attachment/4945506/+files/NetworkManager%20problem.png

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

Title:
Incorrect icon on wireless connection

Status in network-manager package in Ubuntu:
New

Bug description:
On my new installation of Xenial, the Network Manager behaves
strangely.

When I booted the first time with no known networks, I received a
notification about available networks.
I checked the list of available, created one configuration and connected.
So far, OK.
However, after restart, when the notebook boots and there is already a known
network, it connects, but instead of wireless signal strength the nm applet
displays icon for wired network.
Connection information shows it is a wifi network (Interface: 802.11 WiFi
(wlp63s0)), but reports very weird speed (6 Mb/s) - the real speed is ~200
Mb/s. Also, the list of available networks is empty.
Opening nmtui and listing connections in "Activate a connection" I can see
other networks.
But the applet shows no wireless networks and sometimes does not even show
the disconnect item in wireless (sometimes it does). I did not recognize a
pattern when it shows the menu item and when it does not.
When I run `sudo service network-manager restart`, everything fixes to the
proper state - I seen wlan icon, available networks, only connection
information keeps telling me I am connected with 6Mb/s.
The package version is 1.2.6-0ubuntu0.16.04.1.
The wireless adapter is Qualcomm Atheros QCA6174 802.11ac, using module
ath10k_pci.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1715476/+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 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

2017-09-06 Thread Harald W Griesshammer

ubuntu 16.04 unity: find same problem that .XCompose with alt-right key
works in terminal and terminal-based applications (vi, yes I am that
old) -- but not in firefox, libreoffice, thunderbird, emacs, etc.

In my case, rm -f ~/.config/dconf/user did not work, nor did any of the
other tricks.

Maybe this sheds light on things: my Settings-> Language lists "IBus" as
keyboard input method, but ibus does not run on startup/login. Instead,
ibus-setup starts with message that demon is not running. And yes, I did
follow the proposed fix ("make IBus kbd input method in Languages") --
that did not help. However, after just starting ibus-setup and closing
it again, special characters suddenly work in all applications.

However, just starting ibus from terminal as ibus-daemon -d does not
work.

There are some ibus-setup messages on the terminal: 
/usr/share/ibus/setup/main.py:38: PyGIWarning: Gtk was imported without 
specifying a version first. Use gi.require_version('Gtk', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/share/ibus/setup/main.py:39: PyGIWarning: IBus was imported without 
specifying a version first. Use gi.require_version('IBus', '1.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import IBus

Can that bring you closer to a solution?

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

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 20:45:33 2016
  InstallationDate: Installed on 2013-12-16 (857 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+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 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

2017-09-06 Thread Harald W Griesshammer

ubuntu 16.04 unity: find same problem that .XCompose with alt-right key
works in terminal and terminal-based applications (vi, yes I am that
old) -- but not in firefox, libreoffice, thunderbird, emacs, etc.

In my case, rm -f ~/.config/dconf/user did not work, nor did any of the
other tricks.

Maybe this sheds light on things: my Settings-> Language lists "IBus" as
keyboard input method, but ibus does not run on startup/login. Instead,
ibus-setup starts with message that demon is not running. And yes, I did
follow the proposed fix ("make IBus kbd input method in Languages") --
that did not help. However, after just starting ibus-setup and closing
it again, special characters suddenly work in all applications.

However, just starting ibus from terminal as ibus-daemon -d does not
work.

There are some ibus-setup messages on the terminal: 
/usr/share/ibus/setup/main.py:38: PyGIWarning: Gtk was imported without 
specifying a version first. Use gi.require_version('Gtk', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/share/ibus/setup/main.py:39: PyGIWarning: IBus was imported without 
specifying a version first. Use gi.require_version('IBus', '1.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import IBus

Can that bring you closer to a solution?

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

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 20:45:33 2016
  InstallationDate: Installed on 2013-12-16 (857 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+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 1714596] Re: PDF images are blank

2017-09-06 Thread Bryan Quigley

The internal openjpeg parser has been disabled by default and can be re-
enabled by passing --enable-libopenjpeg=unmaintained - I tested this and
it fixes this bug.

It is not only unmaintained and not recommended to use but they mention
having known security issues with the code (and perhaps no plans to
fix*).
https://lists.freedesktop.org/archives/poppler/2017-May/012229.html

Adding security team as I'd definitely want their opinion before moving
forward.

*It appears at least one likely related CVE was fixed by security team -
"fix NULL pointer dereference in JPXStream::readUByte" but not
upstreamed.

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1714596/+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 1715452] [NEW] apport don't come up

2017-09-06 Thread Majestyx

Public bug reported:

after upgrade ubuntu - apport don't start...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports:
 644:0:114:0:2017-09-03 17:55:19.310694562 +0200:2017-09-03 17:55:19.310694562 
+0200:/var/crash/_sbin_plymouthd.0.upload
 640:0:114:1414401:2017-09-03 17:55:17.586719512 +0200:2017-09-03 
17:55:18.586719512 +0200:/var/crash/_sbin_plymouthd.0.crash
 600:108:114:0:2017-09-03 17:55:20.742646659 +0200:2017-09-01 
19:24:48.277299923 +0200:/var/crash/_sbin_plymouthd.0.uploaded
CurrentDesktop: GNOME
Date: Wed Sep  6 19:46:17 2017
InstallationDate: Installed on 2016-11-02 (307 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apport don't come up

Status in apport package in Ubuntu:
  New

Bug description:
  after upgrade ubuntu - apport don't start...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   644:0:114:0:2017-09-03 17:55:19.310694562 +0200:2017-09-03 
17:55:19.310694562 +0200:/var/crash/_sbin_plymouthd.0.upload
   640:0:114:1414401:2017-09-03 17:55:17.586719512 +0200:2017-09-03 
17:55:18.586719512 +0200:/var/crash/_sbin_plymouthd.0.crash
   600:108:114:0:2017-09-03 17:55:20.742646659 +0200:2017-09-01 
19:24:48.277299923 +0200:/var/crash/_sbin_plymouthd.0.uploaded
  CurrentDesktop: GNOME
  Date: Wed Sep  6 19:46:17 2017
  InstallationDate: Installed on 2016-11-02 (307 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1715452/+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 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

2017-09-06 Thread Stéphane Graber

Yeah, we need to get another fix in for that. We released LXC 2.1
yesterday which contains that fix, but are waiting for a freeze
exception.

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

Title:
  lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713726/+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 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.

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

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

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

Title:
  Volume control doesn't work automatically when connecting Bluetooth
  device.

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I connect a Bluetooth device, sound is automatically forwarded to
  the device but volume controls still control the internal sound card
  device.  I must open the sound settings and click on the Bluetooth
  output device to use volume controls.

  I wish that the volume controls would automatically control whatever
  output device is actually active. :)

  This bug has existed for many versions of Ubuntu now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+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 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.

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

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

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

Title:
  Volume control doesn't work automatically when connecting Bluetooth
  device.

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I connect a Bluetooth device, sound is automatically forwarded to
  the device but volume controls still control the internal sound card
  device.  I must open the sound settings and click on the Bluetooth
  output device to use volume controls.

  I wish that the volume controls would automatically control whatever
  output device is actually active. :)

  This bug has existed for many versions of Ubuntu now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+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 1553669] Re: Annoying "call from" message

2017-09-06 Thread Justin Abrahms

Can reproduce the same with 16.04.3 and Bose QC35 headphones.

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

Title:
  Annoying "call from" message

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

2017-09-06 Thread D. Charles Pyle

I had the latest DisplayLink driver and it still did the same thing to
me.  And it gets worse than that.  No errors are generated but the speed
is so slow it is almost unbearable whenever the DisplayLink device is in
use.  I could click the icon for Files to launch Nautilus from the Unity
favorites bar, and it would not appear for almost two whole minutes!
Disconnect the device and reboot, and all was fine with the world--
except that it wasn't.  I could not use my third monitor to do editing
work.

Unfortunately, it became easier just to remove Ubuntu from my system and
move to another distribution that does work with DisplayLink devices.
There were serious problems with power saving, too.  Suspend would crash
the machine rather than suspend to memory, and this was on a system that
I purchased because it was certified for Ubuntu!

In Fedora, the distribution I now am using exclusively, I still see
flickering when the mouse is moved to the top of the screen but the
flickering is bearable compared to the ungodly slowness on the screen
with that flickering, in Ubuntu 16.04.2.  I do not know what the problem
is on Ubuntu with DisplayLink devices but it was too unbearable, and
that is unfortunate because I really liked working in Ubuntu, with Unity
being my chosen interface.  But I hear that even Unity will be going
away.

I hope that one day the display bugs involving DisplayLink displays will
be fixed.  Until then, if I want to get work done, and not have to spend
time waiting between mouse clicks and app launches, I have to go
elsewhere for at least the time being.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+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 1713984] Re: started raise network interfaces - times out

2017-09-06 Thread Brian Murray

I'm not certain this is related but I did not experience the delay when
using lightdm, but do when using gdm3.

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

** Changed in: systemd (Ubuntu Artful)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

  Test Case AutoResize

  choose to encrypt home drive, install all updates and non free codecs
  for the installation options

  On boot (and every subsequent boot) I see in the boot sequence

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

  
  On login, fired up chromium and connected to google so the networking is ok.

  Question - why the 1 minute 30 seconds delay?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 30 12:24:23 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 
(20170829)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713984/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

2017-09-06 Thread Christopher M. Penalver

Tomasz Raganowicz, the DisplayLink driver you are using is outdated
(latest is 1.3.54).

Despite this, the article you linked doesn't point to Launchpad at all.
Likely, because this report hasn't been fully root caused, and folks
simply add "Me too!" comments that aren't helpful for a developer to
solve the problem.

Also, given the details in your comment are impossible to use to fix the issue 
you have, it will help immensely if you use the computer the problem is 
reproducible with, file a new report with Ubuntu by first ensuring the package 
xdiagnose is installed, click the Yes button for attaching additional debugging 
information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+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 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-09-06 Thread Brian Murray

** Also affects: systemd (Ubuntu Artful)
   Importance: High
   Status: Confirmed

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17

[Touch-packages] [Bug 1715397] Re: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

I see adt failures with 4.12 as well, looks like a regression in
ppc64-diag. Changing affected package.

** Package changed: systemd (Ubuntu) => ppc64-diag (Ubuntu)

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

Title:
  systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

Status in ppc64-diag package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppc64-diag/+bug/1715397/+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 1715397] Re: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

ep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Service hold-off time over, scheduling restart.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Stopped ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Service hold-off time over, scheduling restart.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Stopped ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Service hold-off time over, scheduling restart.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Stopped ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Service hold-off time over, scheduling restart.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Stopped ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Service hold-off time over, scheduling restart.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Stopped ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Start request repeated too quickly.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
Failed to start ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Unit entered failed state.
Sep 06 12:23:42 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: 
rtas_errd.service: Failed with result 'start-limit-hit'.
FAIL

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

Title:
  systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

Status in ppc64-diag package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppc64-diag/+bug/1715397/+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 1715424] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar s

2017-09-06 Thread Luis Galarza

Public bug reported:

ubuntu 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Wed Sep  6 10:12:16 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2016-03-12 (542 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: Upgraded to xenial on 2016-07-30 (402 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  El paquete está en un estado grave de inconsistencia - debe
  reinstalarlo  antes de intentar su configuración.

Status in openssl package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Wed Sep  6 10:12:16 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-03-12 (542 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (402 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1715424/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

2017-09-06 Thread Carlo Lobrano

No worries. About gedit, I can't reproduce the issue. I changed gedit's
font to Ubuntu regular (initially it was Ubuntu Mono, so a monospace
context menu was expected, I guess) and the context menu is not in
monospace.

However, if you're still able to reproduce the issue with a not
monospace font, could you please open a dedicated bug?

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1700931] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1

2017-09-06 Thread Joshua Powers

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

Thanks for taking the time to file a bug.

This looks like a duplicate of LP: #1646731. If you are still facing
this issue, it would be very very helpful if you could collect the
output of the following commands and attach it to LP: 1646731

sudo dpkg --audit
dpkg --verify tomcat7
dpdk --verify plymouth
ls -l /etc/rc*/tomcat
ls -l /etc/rc*/plymouth
ls -l /etc/init.d/tomcat
ls -l /etc/plymouth/tomcat
cat /etc/init.d/tomcat
cat /etc/init.d/plymouth

** This bug has been marked a duplicate of bug 1646731
   insserv: Starting tomcat depends on plymouth and therefore on system 
facility `$all' which can not be true!

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  子进程 已安装 post-installation 脚本 返回错误状态 1

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  update-rc.d: error: insserv rejected the script header
  dpkg: 处理软件包 openssh-server (--configure)时出错：
   子进程 已安装 post-installation 脚本 返回错误状态 1
  在处理时有错误发生：
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 28 16:49:30 2017
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-06-27 (1 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: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1700931/+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 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-09-06 Thread Joshua Powers

Thank you for taking the time to file a bug report.

Per the log message above, you may have changed the default Python
version from 2 to 3. This leads to unexpected behavior like the errors
you are currently seeing. Can you confirm that /usr/bin/python is
version 2?

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in six package in Ubuntu:
  Incomplete

Bug description:
  kflkt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 06:44:23 2017
  Dependencies:
   
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-03 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1715062/+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 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-06 Thread Alfonso Sanchez-Beato

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

@smb, actually, there is no create time field in the fs header, see

http://paste.ubuntu.com/25478756/

(this comes from a file with the mount time already corrected). This is
a partition created with android tools, as the ones from mkfs.ext4 do
not work for this device (for unknown reasons). I understand this is
sort of a special case though.

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

Title:
  fixrtc is ineffective when there is no battery for the RTC

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  When there is no battery for the RTC, fixrtc is not able to find a
  good enough date. To fix the clock, this script is using the last time
  the root filesystem was mounted, but as that is done before there is
  any network, and as after a reboot/poweroff the RTC time is always
  reset (because time is not kept due to lack of battery), the mount
  time will never be good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+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 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-09-06 Thread Joshua Powers

>From log:

Removing python-pip (8.1.1-2ubuntu0.4) ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax

Removing python-pkg-resources (20.7.0-1) ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax

Removing python-six (1.10.0-3) ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax

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

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in six package in Ubuntu:
  Incomplete

Bug description:
  kflkt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 06:44:23 2017
  Dependencies:
   
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-03 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1715062/+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 1714505] Re: systemd kmod builtin uses out of date kmod context

2017-09-06 Thread Eric Desrochers

** Also affects: systemd (Ubuntu Artful)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

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

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

** Also affects: systemd (Ubuntu Zesty)
   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/1714505

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1714505/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Sorry, I haven't seen your patch, I see that you have done the same
thing there as me above (I was referring to Hồng's original patch).

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-09-06 Thread Andrea Lazzarotto (Lazza)

As said above, it is fixed in 17.04 so you just have to upgrade.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

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

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

2017-09-06 Thread Carlo Lobrano

Ok, I think this should have been discussed in patch's code review here

  https://code.launchpad.net/~c-lobrano/ubuntu-
themes/fix-1700218/+merge/327422

however, the original patch should already take into account the
context-menu's font style, at least in gitg it does. Let me have a look
into gedit, maybe it uses a different class

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1714319] Re: initramfs has duplicate copies of libnss_files on x86_64

2017-09-06 Thread Scott Moser

** No longer affects: initramfs-tools (Ubuntu)

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

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

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

Title:
  initramfs has duplicate copies of libnss_files on x86_64

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure why this ends up happening, but

  $ dpkg -S `which mkinitramfs`
  initramfs-tools-core: /usr/sbin/mkinitramfs

  $ dpkg-query --show initramfs-tools-core
  initramfs-tools-core  0.125ubuntu9

  $ sudo update-initramfs -t -c -k $(uname -r)
  update-initramfs: Generating /boot/initrd.img-4.12.0-11-generic

  $ rm -Rf x; mkdir -p x; 
  $ /usr/lib/dracut/skipcpio /boot/initrd.img-4.12.0-11-generic | zcat | ( cd x 
&& cpio -uid )
  91209 blocks

  $ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 lib/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 lib/libnss_files.so.2 -> 
libnss_files-2.24.so
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files.so.2 -> libnss_files-2.24.so

  $ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files.so.2
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files.so.2

  $ grep -r nss /usr/lib/initramfs-tools/ || echo nothing obvious
  nothing obvious

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:52:28 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1714319/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

2017-09-06 Thread Stefan Bader

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Triaged
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Triaged

Bug description:
  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+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 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-06 Thread Stefan Bader

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

** This bug has been marked a duplicate of bug 1623125
   fixrtc script does not catch "Last mount time: n/a" string

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

Title:
  fixrtc is ineffective when there is no battery for the RTC

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  When there is no battery for the RTC, fixrtc is not able to find a
  good enough date. To fix the clock, this script is using the last time
  the root filesystem was mounted, but as that is done before there is
  any network, and as after a reboot/poweroff the RTC time is always
  reset (because time is not kept due to lack of battery), the mount
  time will never be good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Carlo, now I remember why I got confused. It happens in gedit (when
right clicking the text area), with or without Hồng's patch.

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 349469] Start participating

2017-09-06 Thread GIANLUCA

To do well, read all you can about the opinions, tool and strategies  of both 
experts and peers. But before you  even start, choose  a niche  about  which 
you're passionate.
The  more you truly enjoy what you're immersed in, the more  likely you are to 
transform your affiliate marketing  and money-making venture into a huge 
success.
Take a  look 
http://seibertkeck.com/dengi-life_n2x.php?m=EMzQ5NDY5QGJ1Z3MubGF1bmNocGFkLm5ldA--

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Incomplete
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

With the latest upload tests still fail, but it seems to get slightly
farther. Is this a different issue?

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful-canonical-kernel-team-
unstable/artful/amd64/l/lxc/20170906_003748_d668f@/log.gz

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

Title:
  lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713726/+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-09-06 Thread Juerg Haefliger

This is looking great so far.  Instance booted nicely, no signs of a
kernel panic.  The driver was happily picked up in the initramfs.  I'm
going to run it through some stress-ng tests to make sure everything is
fine but we're off to a good start.

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

-- 
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 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 1715397] [NEW] systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

Public bug reported:

Testing failed on:
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715397/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

I mitigated this by clearing the property from children (such as the
pop-up menu):

/* Fix Gitg source view */
.monospace {
font-family: "Monospace";
}

.monospace * {
font-family: initial;
}

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Without the proposed patch.

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Sorry, I  messed up. With the proposed patch.

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1714319] Re: initramfs has duplicate copies of libnss_files on x86_64

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/plymouth/+git/plymouth/+merge/330286

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

Title:
  initramfs has duplicate copies of libnss_files on x86_64

Status in initramfs-tools package in Ubuntu:
  New
Status in plymouth package in Ubuntu:
  New

Bug description:
  I'm not sure why this ends up happening, but

  $ dpkg -S `which mkinitramfs`
  initramfs-tools-core: /usr/sbin/mkinitramfs

  $ dpkg-query --show initramfs-tools-core
  initramfs-tools-core  0.125ubuntu9

  $ sudo update-initramfs -t -c -k $(uname -r)
  update-initramfs: Generating /boot/initrd.img-4.12.0-11-generic

  $ rm -Rf x; mkdir -p x; 
  $ /usr/lib/dracut/skipcpio /boot/initrd.img-4.12.0-11-generic | zcat | ( cd x 
&& cpio -uid )
  91209 blocks

  $ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 lib/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 lib/libnss_files.so.2 -> 
libnss_files-2.24.so
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files.so.2 -> libnss_files-2.24.so

  $ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files.so.2
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files.so.2

  $ grep -r nss /usr/lib/initramfs-tools/ || echo nothing obvious
  nothing obvious

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:52:28 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1714319/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-09-06 Thread mc

It still exists in 16.04.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

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

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

2017-09-06 Thread Carlo Lobrano

Do you mean, using the proposed patch?

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

By the way, if you right click on the diff in gitg, the menu font is
monospaced, although it shouldn't be. Not sure if related.

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1370953] Re: layout switch is delayed

2017-09-06 Thread Alex

bla-bla-bla
keyboard layout switcher is not a rocket science. this is system BASE feature. 
It must work perfectly, as it had already worked some time ago. If you do 
something do it good, or do not do it at all. Even if it is free.

i have reviewed half of the internet for a solution and would not write
here, if it exists.

talk about the problem, not about me.

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1715376] [NEW] ip link add command return: Error: either "dev" is duplicate, or "enp1s0" is a garbage.

2017-09-06 Thread Po-Hsu Lin

Public bug reported:

With iproute2 3.12 on Trusty, command:
sudo ip link add type veth peer enp1s0 name testveth0

Will return:
Error: either "dev" is duplicate, or "enp1s0" is a garbage.

However, this command works fine since Xenial (iproute2 4.3.0)

As we will need this for kenrel SRU testing, it will be great to have
this fixed on Trusty.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: iproute2 3.12.0-2ubuntu1
ProcVersionSignature: User Name 3.13.0-129.178-generic 3.13.11-ckt39
Uname: Linux 3.13.0-129-generic aarch64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: arm64
Date: Wed Sep  6 10:54:47 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: iproute2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 trusty uec-images

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

Title:
  ip link add command return: Error: either "dev" is duplicate, or
  "enp1s0" is a garbage.

Status in iproute2 package in Ubuntu:
  New

Bug description:
  With iproute2 3.12 on Trusty, command:
  sudo ip link add type veth peer enp1s0 name testveth0

  Will return:
  Error: either "dev" is duplicate, or "enp1s0" is a garbage.

  However, this command works fine since Xenial (iproute2 4.3.0)

  As we will need this for kenrel SRU testing, it will be great to have
  this fixed on Trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: iproute2 3.12.0-2ubuntu1
  ProcVersionSignature: User Name 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: arm64
  Date: Wed Sep  6 10:54:47 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1715376/+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 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-06 Thread Stefan Bader

Looking at the complete fixrtc-mount script (the part which was fixed in bug 
#1623125 makes me think that this would fix your problem as well. And that with 
much less required change. That script checks not only mount but also create 
time of the fs. If create time is more recent than mount time, then it will set 
the time to that. And the time of creating the Ubuntu Core image should be 
recent enough to meet any expectations of the certificates. What I think has 
happened is that the "n/a" result was causing date to return an error. And 
because the scripts are executed with "-e" this would stop execution right 
there and the time was not set at all.
With the check for "n/a" as the change is in its original form, it would set 
mount time to 1999 but then use the create time which is newer. And since that 
is done pre-mount, this will set mount time to create time, too.

So right now I tend to mark this bug as duplicate of bug #1623125, then
get that fix in (preferred because it would be much smaller/simpler).
Should this turn out to not be enough, we still can un-dup and look for
a bigger solution. Thank you for your efforts, and sorry for me being so
resistant. I am just trying to fix the problem with as little change as
possible. The less change, the less one can break.

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

Title:
  fixrtc is ineffective when there is no battery for the RTC

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  When there is no battery for the RTC, fixrtc is not able to find a
  good enough date. To fix the clock, this script is using the last time
  the root filesystem was mounted, but as that is done before there is
  any network, and as after a reboot/poweroff the RTC time is always
  reset (because time is not kept due to lack of battery), the mount
  time will never be good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+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 1692111] Re: Unable to configure raw.id_map with multiple entries

2017-09-06 Thread Christian Brauner

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

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

Title:
  Unable to configure raw.id_map with multiple entries

Status in lxc package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  I am trying to map two users (999, 1001) to one of my containers. I
  added both IDs to /etc/subgid and /etc/subuid. I followed by setting
  raw.id_map property value (as instructed here
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2017-March/013034.html):

  "echo -e "both 999 999\nboth 1001 1001" |  lxc config set mycontainer
  raw.idmap -"

  However upon starting the container, I get errors (log excerpt below).
  If, on the other hand, I set idmap to either "both 999 999" or "both
  1001 1001" only - i.e. if I map only one user at the time, the
  container starts just fine and the user is mapped as expected.

  My subgid and subuid look as follows:

  lxd:10:65536
  root:10:65536
  root:1001:1
  root:999:1

  Log excerpt:

  Name: mycontainer
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/02/22 18:54 UTC
  Status: Stopped
  Type: persistent
  Profiles: default

  Log:

  lxc 20170519204102.895 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer" already existed.
  lxc 20170519204102.896 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed.
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-8: No such file or directory
  lxc 20170519204102.901 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgro

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-06 Thread Lukas Dzunko

@joll-nicholas I just want to add my view of this situation to this bug
report. :) It was more like message to all in this thread ... my
apologize if it was not written properly (I am not native speaker)

@kantlivelong ... yeah, for now (I mentioned this also in initial
report) but it may not be case in future. Canonical already removed
package for GUI and there is no guarantee that they will leave at least
package for daemons there ...

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

2017-09-06 Thread Andy Whitcroft

@ubuntu-security -- could we have an oppinion on this patch which is
enabling %VERIFY_ALLOW_SIGN_RSA_MD5 for trusty.  Looking to understand
if this is overly broad and therefore a security issue.

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Released
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect smtp.sdeziel.info:587 -starttls smtp 
2>/dev/null | grep -E '^[[:space:]]+(Protocol|Cipher)'
  Protocol  : TLSv1.2
  Cipher: ECDHE-RSA-AES128-GCM-SHA256

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  $ apt-cache polic

[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

2017-09-06 Thread Julian Andres Klode

So, I believe the proposed 2nd trusty might accidentally allow MD5
everywhere, when the problem only is root certificates with MD5 self
signatures. I believe this might be related:

https://gitlab.com/gnutls/gnutls/commit/b93ae1abf1b84fdc094f2474f1b2e4848081810e

But I'm not sure if it fixes the issue and if any other patches are
needed from 2.12.24.

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Released
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect smtp.sdeziel.info:587 -starttls smtp 
2>/dev/null | grep -E '^[[:space:]]+(Protocol|Cipher)'
  Protocol  : TLSv1.2
  Cipher

[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

2017-09-06 Thread Dimitri John Ledkov

Test of  0.93.1ubuntu2.3 &  1.4.6~17.04.1 together are fine. please
release the two together.

@mikini - it is prudent from OS vendor point of view to enable and
install security updates by default, as most users neglect to set it up
themselves. unattanded-upgrades is one way to do this, but it is an
optional component of the system and many users use other means to keep
their systems secure. The constraints on randomising downloads is due to
mirror load spikes. The constraint on consistent and predicable
application of updates is due to unexpected behavior experienced by our
user base when random application of updates was in place. Overall it is
a sensible default. We do monitor crash and error rates, and that data
suggests to us that people routinely postpone upgrades or delay them. As
for key crashes we reach 90% of updates applied within 2 weeks. Thus
defaults to apply updates within a day are sensible. Please note that
adjusting .timer frequency alone will not be sufficient as apt has its
own internal timestamps too which throttle unattanded upgrades. If you
want full control of upgrades do execute / automate them in a manner
that is appropriate for your deployment. There is nothing in place that
would prevent you from doing that. Many people use other mechanisms for
upgrades, e.g. landscape.

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download /
     unattended upgrade are all performed on boot.

   * Downgrade systemd to the release version of the package (from
     -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*.
 Then run 'sudo systemctl start apt-daily.service'.
     Confirm that the systemd package is downloaded, but not upgraded.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do
     everything at random times throughout the day". If there are specific

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-09-06 Thread Dimitri John Ledkov

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

** Tags removed: regression-proposed

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

2017-09-06 Thread Dimitri John Ledkov

** Tags removed: verification-needed-zesty
** Tags added: verification-done-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/1686470

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download /
     unattended upgrade are all performed on boot.

   * Downgrade systemd to the release version of the package (from
     -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*.
 Then run 'sudo systemctl start apt-daily.service'.
     Confirm that the systemd package is downloaded, but not upgraded.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do
     everything at random times throughout the day". If there are specific
     deployments that rely on the previous types of behaviour they will be
     able to adjust manually the systemd timers with the overrides to be
     executed exactly as they wish; or match the .0 release behaviour that
     they prefer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+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 1709193] Update Released

2017-09-06 Thread Andy Whitcroft

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

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Released
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect smtp.sdeziel.info:587

[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

This bug was fixed in the package gnutls28 - 3.5.6-4ubuntu4.2

---
gnutls28 (3.5.6-4ubuntu4.2) zesty; urgency=medium

  * use_normal_priority_for_openssl_sslv23.diff by Andreas Metzler:
OpenSSL wrapper: SSLv23_*_method translates to NORMAL GnuTLS priority,
which includes TLS1.2 support. (LP: #1709193)

 -- Simon Deziel   Thu, 10 Aug 2017 12:47:14
+

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

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Released
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect smtp.sdeziel.info:587 -st

[Touch-packages] [Bug 951120] Re: AirPlay - AirTunes (Airport Express) support over UDP for shairplay and Speakers that use shairplay

Now released upstream:
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/

Although we likely will wait till Ubuntu 18.04 to bring that in.

** Tags added: pulse11

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

Title:
  AirPlay  - AirTunes (Airport Express) support over UDP  for shairplay
  and Speakers that use shairplay

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  If you install "paprefs"pulse audio preferences manager  on the
  first tab you can enable the support for :

  Make discoverable Apple AirTunes  sound devices available locally.

  I have it enabled i can see  my AirTune  device as an Output device
  on sound settings  but when i select it  its doesnt transmit the sound
  ( Actually the player stops playing like there is no output device ) .

  My airtune device is working great with any other way   like control
  over iphone   itunes etc .

  EDIT : The culprit found by others is that Pulseaudio raop is using
  TCP for data stream  in conflict that the Shairplay use only UDP .

  Pulseaudio should move on UDP as well because every Speaker-device on
  the market is using shairplay  - UDP

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu12
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zzecool2218 F pulseaudio
   /dev/snd/pcmC0D0p:   zzecool2218 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48'
     Mixer name : 'SigmaTel STAC9872AK'
     Components : 'HDA:83847662,104d1c00,00100201 
HDA:14f12c06,104d1700,0010'
     Controls  : 18
     Simple ctrls  : 9
  Date: Fri Mar  9 22:15:39 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2012-02-16 (22 days ago)
  dmi.bios.date: 12/21/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R2110J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31Z:pvrC6006UGW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FZ31Z
  dmi.product.version: C6006UGW
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/951120/+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 1702794] Re: Automatically switch audio devices on connection