[Touch-packages] [Bug 1652491] Re: Sync elfutils 0.166-2.2 (main) from Debian unstable (main)

[Amr Ibrahim]

** Changed in: elfutils (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 elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1652491

Title:
  Sync elfutils 0.166-2.2 (main) from Debian unstable (main)

Status in elfutils package in Ubuntu:
  Fix Released

Bug description:
  Please sync elfutils 0.166-2.2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Don't run the run-backtrace-native-biarch test.

  The test was fixed in -2.2. I confirmed that the package builds
  successfully on all normal PPA architectures.

  Changelog entries since current zesty version 0.166-2ubuntu1:

  elfutils (0.166-2.2) unstable; urgency=medium

* Non-maintainer upload.
* testsuite-amd64-fix-backtrace-native.patch: Backport upstream
  patch to fix FTBFS on amd64 (Closes: #841124)

   -- James Clarke   Tue, 18 Oct 2016 08:13:34 +0100

  elfutils (0.166-2.1) unstable; urgency=medium

* Non-maintainer upload.
* Build-Depend on gcc-multilib and libc6-dbg on sparc64 (Closes: #832584)

   -- James Clarke   Fri, 07 Oct 2016 15:16:09 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1652491/+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 1718575] Re: Screen blanks in less than 15 seconds

[Spaceboy ross]

The blanking started on Friday. I've had the install for 8 days, so it's
not a DRM problem.

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

Title:
  Screen blanks in less than 15 seconds

Status in xorg package in Ubuntu:
  New

Bug description:
  I've spent the last week looking for help to fix this bug for Ubuntu
  17.04 where the screen goes blank before the time in the settings.
  I've tried disabling DPMS and the screensaver, didn't work. I've
  changed the settings for my battery and display, didn't work. I've ran
  about 10 different scripts, didn't work. Tried caffeine, didn't
  install. This needs to be fixed, it even effects videos.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 20 21:11:29 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
  InstallationDate: Installed on 2017-09-13 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/28/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718575/+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 1718575] Re: Screen blanks in less than 15 seconds

[dino99]

Dmesg shows a drm problem (probably related to your dell hardware model
(dig around on the net)):

Call Trace:
[   13.380327]  dump_stack+0x63/0x81
[   13.380330]  __warn+0xcb/0xf0
[   13.380333]  warn_slowpath_fmt+0x5f/0x80
[   13.380338]  ? finish_wait+0x56/0x70
[   13.380356]  drm_wait_one_vblank+0x1aa/0x1b0 [drm]
[   13.380360]  ? wake_atomic_t_function+0x60/0x60
[   13.380383]  ? drm_atomic_state_clear+0x30/0x30 [drm]
[   13.380471]  intel_get_load_detect_pipe+0x5ff/0x650 [i915]
[   13.380506]  intel_tv_detect+0x158/0x550 [i915]
[   13.380512]  drm_helper_probe_single_connector_modes+0x2c4/0x520 
[drm_kms_helper]
[   13.380518]  drm_setup_crtcs+0x7b/0x9d0 [drm_kms_helper]
[   13.380521]  ? update_load_avg+0x6b/0x510
[   13.380522]  ? set_next_entity+0xc3/0x1b0
[   13.380527]  drm_fb_helper_initial_config+0x79/0x3e0 [drm_kms_helper]
[   13.380529]  ? __switch_to+0x23c/0x520
[   13.380564]  intel_fbdev_initial_config+0x18/0x30 [i915]
[   13.380565]  async_run_entry_fn+0x37/0x150
[   13.380567]  process_one_work+0x1fc/0x4b0
[   13.380569]  worker_thread+0x4b/0x500
[   13.380571]  kthread+0x109/0x140
[   13.380572]  ? process_one_work+0x4b0/0x4b0
[   13.380574]  ? kthread_create_on_node+0x60/0x60
[   13.380576]  ret_from_fork+0x2c/0x40
[   13.380578] ---[ end trace 667bb6ab8e236ef6 ]---
[   13.520246] [ cut here ]
[   13.520267] WARNING: CPU: 0 PID: 101 at 
/build/linux-3PuzWO/linux-4.10.0/drivers/gpu/drm/drm_irq.c:1237 
drm_wait_one_vblank+0x1aa/0x1b0 [drm]

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

Title:
  Screen blanks in less than 15 seconds

Status in xorg package in Ubuntu:
  New

Bug description:
  I've spent the last week looking for help to fix this bug for Ubuntu
  17.04 where the screen goes blank before the time in the settings.
  I've tried disabling DPMS and the screensaver, didn't work. I've
  changed the settings for my battery and display, didn't work. I've ran
  about 10 different scripts, didn't work. Tried caffeine, didn't
  install. This needs to be fixed, it even effects videos.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 20 21:11:29 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
  InstallationDate: Installed on 2017-09-13 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/28/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

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

[Touch-packages] [Bug 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display

[Launchpad Bug Tracker]

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

** Changed in: pm-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  close lid suspends correctly and wakealarm resumes from suspend to run
  cron jobs but opening lid reveals no display

Status in pm-utils package in Ubuntu:
  Expired

Bug description:
  [Problem]

  When I close the laptop lid, pm-action runs the following code which I
  have added:

  sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm
  sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > 
/sys/class/rtc/rtc0/wakealarm" # set alarm

  and then suspends. At 7:30 AM the next day, the laptop resumes from
  suspend with the lid closed and executes cron jobs (e.g. some
  backups). If I open the lid then there is no display. I tried several
  options to resume the display:

  - [FAILS] all sorts of keyboard combinations
  - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 
/usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no 
DISPLAY variable)
  - [MANUAL HACK] closing the lid causes the laptop to suspend and then opening 
the lid causes it to resume with a normal working display

  I would like a solution or SOFTWARE HACK which I could add to /usr/lib
  /pm-utils/sleep.d/99video during resume from suspend triggered by
  wakealarm so that opening the lid would reveal a working display.

  [Laptop System Information]

  laptop = MacBookPro5,5
  pm-utils version = 1.4.1-13ubuntu0.2
  kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 
(Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
  OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr"
  desktop environment = XFCE
  video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA 
controller])
  video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1

  [Additional Information]

  After my cron backup job is finished it will check if the lid is
  closed. If it is closed then it will run pm-suspend. If I then open
  the lid, the laptop resumes with a normal working display. So the
  problem of no visible display occurs only when I open the lid after
  resume from wakealarm and before the backup job suspends the laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1705551/+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 1718575] [NEW] Screen blanks in less than 15 seconds

[Spaceboy ross]

Public bug reported:

I've spent the last week looking for help to fix this bug for Ubuntu
17.04 where the screen goes blank before the time in the settings. I've
tried disabling DPMS and the screensaver, didn't work. I've changed the
settings for my battery and display, didn't work. I've ran about 10
different scripts, didn't work. Tried caffeine, didn't install. This
needs to be fixed, it even effects videos.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Wed Sep 20 21:11:29 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Latitude D630 [1028:01f9]
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
InstallationDate: Installed on 2017-09-13 (8 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Latitude D630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0KU184
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/28/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1

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


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

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

Title:
  Screen blanks in less than 15 seconds

Status in xorg package in Ubuntu:
  New

Bug description:
  I've spent the last week looking for help to fix this bug for Ubuntu
  17.04 where the screen goes blank before the time in the settings.
  I've tried disabling DPMS and the screensaver, didn't work. I've
  changed the settings for my battery and display, didn't work. I've ran
  about 10 different scripts, didn't work. Tried caffeine, didn't
  install. This needs to be fixed, it even effects videos.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 20 21:11:29 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
  InstallationDate: Installed on 2017-09-13 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no 

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch to detect no link-local address" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that continues the
  loop is one possible solution.

  .case " $out " in
  .*\ dadfailed\ *)
  .error "$dev: ipv6 dad failed."
  .return 1;;
  .*\ tentative\ *) :;;
  +    "  ")
  +    :
  +    ;;
  .*) return 0;;
  .esac

  At least in my situation, this prevents the failure of dhclient due to
  the link-local address not being "ready" yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+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 1718568] Re: dhclient-script fails to wait for link-local address

[Jeff]

Confirmed to resolve issue seen here.

I won't be concerned if you prefer alternate sh-script formatting over
mine.

** Patch added: "Patch to detect no link-local address"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4954114/+files/dhclient-script.diff

** Description changed:

  Summary:
  
  
  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.
  
  Discussion:
  ===
  
  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu
  17.04, I was finding that on boot I was getting failures with the logged
  message "no link-local IPv6 address for "
  
  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-facing
  interface), and worked around it with a script that looks at
  
    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'
  
  and loops for a fixed number of times for that to be successful.
  
  On looking at /sbin/dhclient-script it appears that it *tries* to do the
  same thing in
  
    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()
  
  this code sets
  
    out=$(ip -6 -o address show dev "$dev" scope link)
  
  then checks it with a case statement inside of a loop for
  
  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac
  
  If there is no link-local address, $out will be empty. The default case
  is taken, and the loop exits immediately:
  
  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default
  
  As a result, there is no "wait for link-local address" and when there is
  no link-local address, dhclient fails later on.
  
  Possible Fix:
  =
  
  Adding "the missing case" for "no address" case that continues the loop
  is one possible solution.
  
- case " $out " in
- *\ dadfailed\ *)
- error "$dev: ipv6 dad failed."
- return 1;;
- *\ tentative\ *) :;;
-     "  ")
-     :
-     ;;
- *) return 0;;
- esac
+ .case " $out " in
+ .*\ dadfailed\ *)
+ .error "$dev: ipv6 dad failed."
+ .return 1;;
+ .*\ tentative\ *) :;;
+ +    "  ")
+ +    :
+ +    ;;
+ .*) return 0;;
+ .esac
  
  At least in my situation, this prevents the failure of dhclient due to
  the link-local address not being "ready" yet.

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)

[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

[Jeff]

This does *not* appear to resolve a closely related problem where the
link-local address has not yet been assigned. See LP: 1718568

In brief, the loop

case " $out " in
*\ dadfailed\ *)
error "$dev: ipv6 dad failed."
return 1;;
*\ tentative\ *) :;;
*) return 0;;
esac

exits with 'return 0' with the lack of a link-local address as "  "
($out empty) matches the default pattern as would a valid, link-local
address.

One possible solution is to add "the missing case" that matches $out
being empty that performs the "wait and try again" action.

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+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 298781] Re: qt4-qtconfig does not save font settings

[widon1104]

still present in ubuntu mate 16.04

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

Title:
  qt4-qtconfig does not save font settings

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  If you run qtconfig-qt4 and then make any changes to the font
  settings, they are never applied. If you open qtconfig again, the old
  font settings will be there. It is not possible to change them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/298781/+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 1718568] Re: dhclient-script fails to wait for link-local address

[Jeff]

Confirmed that the same apparent flaw in dhclient-script appears to
exist in 4.3.3-5ubuntu12.7 under Ubuntu 16.04.3 LTS

This appears related to / caused by LP: #1633479
based on 
http://launchpadlibrarian.net/291516262/isc-dhcp_4.3.3-5ubuntu15_4.3.3-5ubuntu15.1.diff.gz


** Description changed:

  Summary:
  
  
  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.
  
  Discussion:
  ===
  
  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu
  17.04, I was finding that on boot I was getting failures with the logged
  message "no link-local IPv6 address for "
  
  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-facing
  interface), and worked around it with a script that looks at
  
    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'
  
  and loops for a fixed number of times for that to be successful.
  
  On looking at /sbin/dhclient-script it appears that it *tries* to do the
  same thing in
  
    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()
  
  this code sets
  
    out=$(ip -6 -o address show dev "$dev" scope link)
  
  then checks it with a case statement inside of a loop for
  
  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac
  
  If there is no link-local address, $out will be empty. The default case
  is taken, and the loop exits immediately:
  
  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default
  
  As a result, there is no "wait for link-local address" and when there is
  no link-local address, dhclient fails later on.
  
  Possible Fix:
  =
  
  Adding "the missing case" for "no address" case that continues the loop
  is one possible solution.
  
  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
-  "  ")
-   :
-   ;;
+     "  ")
+     :
+     ;;
  *) return 0;;
  esac
  
  At least in my situation, this prevents the failure of dhclient due to
  the link-local address not being "ready" yet.

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that continues 

[Touch-packages] [Bug 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

[Bug Watch Updater]

** Changed in: binutils
   Status: Confirmed => Fix Released

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in dpkg package in Debian:
  Fix Released

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1715641/+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 1718568] [NEW] dhclient-script fails to wait for link-local address

[Jeff]

Public bug reported:

Summary:


If a interface does not yet have a link-local address (as it may have
just been brought up), dhclient -6  will fail. The built-in
"wait for link-local address" loop does not function properly, causing
DHCP failure.

Discussion:
===

In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu
17.04, I was finding that on boot I was getting failures with the logged
message "no link-local IPv6 address for "

I found that it took several seconds for the link-local address to be
assigned when the interface came up (in this case, the ISP/modem-facing
interface), and worked around it with a script that looks at

  /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

and loops for a fixed number of times for that to be successful.

On looking at /sbin/dhclient-script it appears that it *tries* to do the
same thing in

  # set the link up and wait for ipv6 link local dad to finish
  ipv6_link_up_and_dad()

this code sets

  out=$(ip -6 -o address show dev "$dev" scope link)

then checks it with a case statement inside of a loop for

case " $out " in
*\ dadfailed\ *)
error "$dev: ipv6 dad failed."
return 1;;
*\ tentative\ *) :;;
*) return 0;;
esac

If there is no link-local address, $out will be empty. The default case
is taken, and the loop exits immediately:

$ echo "'$out'" ; case " $out " in
> *\ dadfailed\ *)
> echo "dadfailed"
> ;;
> *\ tentative\ *)
> echo "tentative"
> ;;
> *)
> echo "default"
> esac
''
default

As a result, there is no "wait for link-local address" and when there is
no link-local address, dhclient fails later on.

Possible Fix:
=

Adding "the missing case" for "no address" case that continues the loop
is one possible solution.

case " $out " in
*\ dadfailed\ *)
error "$dev: ipv6 dad failed."
return 1;;
*\ tentative\ *) :;;
 "  ")
  :
  ;;
*) return 0;;
esac

At least in my situation, this prevents the failure of dhclient due to
the link-local address not being "ready" yet.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: isc-dhcp (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: ipv6

** Description changed:

  Summary:
  
  
- If a interface does not have a link-local address, dhclient -6 
- will fail. The built-in "wait for link-local address" loop does not
- function properly, causing DHCP failure.
+ If a interface does not yet have a link-local address (as it may have
+ just been brought up), dhclient -6  will fail. The built-in
+ "wait for link-local address" loop does not function properly, causing
+ DHCP failure.
  
  Discussion:
  ===
  
  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu
  17.04, I was finding that on boot I was getting failures with the logged
  message "no link-local IPv6 address for "
  
  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-facing
  interface), and worked around it with a script that looks at
  
-   /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'
+   /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'
  
  and loops for a fixed number of times for that to be successful.
  
  On looking at /sbin/dhclient-script it appears that it *tries* to do the
  same thing in
  
-   # set the link up and wait for ipv6 link local dad to finish
-   ipv6_link_up_and_dad()
+   # set the link up and wait for ipv6 link local dad to finish
+   ipv6_link_up_and_dad()
  
  this code sets
  
-   out=$(ip -6 -o address show dev "$dev" scope link)
+   out=$(ip -6 -o address show dev "$dev" scope link)
  
  then checks it with a case statement inside of a loop for
  
- case " $out " in
- *\ dadfailed\ *)
- error "$dev: ipv6 dad failed."
- return 1;;
- *\ tentative\ *) :;;
- *) return 0;;
- esac
+ case " $out " in
+ *\ dadfailed\ *)
+ error "$dev: ipv6 dad failed."
+ return 1;;
+ *\ tentative\ *) :;;
+ *) return 0;;
+ esac
  
  If there is no link-local address, $out will be empty. The default case
  is taken, and the loop exits immediately:
  
  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default
  
  As a result, there is no "wait for link-local address" and when there is
  no link-local address, dhclient fails later on.
  
- 
  Possible Fix:
  =
  
  Adding "the missing case" for "no address" case that continues the loop
  is one 

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[Carlos Eduardo Moreira dos Santos]

Reboot in 4.10-0-33 and youtube is muted on Dummy Output. Tried VLC with
same results. The weird thing is that I could hear audio in 4.10.0-35 in
some occasions, with my device being correctly displayed in pavucontrol.
Suddenly, it had a Dummy Output again...

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not 

[Touch-packages] [Bug 1718560] [NEW] overall

[silva ahmad]

Public bug reported:

overall

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Sep 21 08:28:41 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90a8]
InstallationDate: Installed on 2017-07-02 (80 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Sony Corporation SVT13133CVS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=744f398e-dc10-4f2c-b425-92e3d8a483dd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1100D4
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:bvnInsydeCorp.:bvrR1100D4:bd11/14/2012:svnSonyCorporation:pnSVT13133CVS:pvrC904XP3Z:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVT13133CVS
dmi.product.version: C904XP3Z
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Sep 21 07:52:40 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  overall

Status in xorg package in Ubuntu:
  New

Bug description:
  overall

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Sep 21 08:28:41 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90a8]
  InstallationDate: Installed on 2017-07-02 (80 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Sony Corporation SVT13133CVS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=744f398e-dc10-4f2c-b425-92e3d8a483dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1100D4
  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:bvnInsydeCorp.:bvrR1100D4:bd11/14/2012:svnSonyCorporation:pnSVT13133CVS:pvrC904XP3Z:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVT13133CVS
  dmi.product.version: C904XP3Z
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  

[Touch-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

[Philip Langdale]

I patched and built a package locally and confirmed the fix works.

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1718554/+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 1718558] Re: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network manager is disabled and dpkg is unable to update something ...

  Setting up network-manager-config-connectivity-ubuntu (1.8.2-1ubuntu8) ...
  NetworkManager.service is not active, cannot reload.
  invoke-rc.d: initscript network-manager, action "force-reload" failed.
  dpkg: error processing package network-manager-config-connectivity-ubuntu 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   network-manager-config-connectivity-ubuntu
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 20 20:28:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-09 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.1.1 dev br0 
   169.254.0.0/16 dev br0 scope link metric 1000 
   192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.15 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718558/+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 1718558] [NEW] package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

[Istvan Matyas-Balassy]

Public bug reported:

Network manager is disabled and dpkg is unable to update something ...

Setting up network-manager-config-connectivity-ubuntu (1.8.2-1ubuntu8) ...
NetworkManager.service is not active, cannot reload.
invoke-rc.d: initscript network-manager, action "force-reload" failed.
dpkg: error processing package network-manager-config-connectivity-ubuntu 
(--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 network-manager-config-connectivity-ubuntu
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Wed Sep 20 20:28:18 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-09-09 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
IpRoute:
 default via 192.168.1.1 dev br0 
 169.254.0.0/16 dev br0 scope link metric 1000 
 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.15 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~rc4
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: 
Error: NetworkManager is not running.

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


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network manager is disabled and dpkg is unable to update something ...

  Setting up network-manager-config-connectivity-ubuntu (1.8.2-1ubuntu8) ...
  NetworkManager.service is not active, cannot reload.
  invoke-rc.d: initscript network-manager, action "force-reload" failed.
  dpkg: error processing package network-manager-config-connectivity-ubuntu 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   network-manager-config-connectivity-ubuntu
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 20 20:28:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-09 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.1.1 dev br0 
   169.254.0.0/16 dev br0 scope link metric 1000 
   192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.15 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with 

[Touch-packages] [Bug 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Bug Watch Updater]

** Changed in: gdk-pixbuf
   Status: Unknown => Fix Released

** Changed in: gdk-pixbuf
   Importance: Unknown => Medium

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+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 1718554] [NEW] Need updated libimobiledevice to mount IOS 11 devices

[Philip Langdale]

Public bug reported:

After upgrading to IOS 11, I stopped being able to mount my ipad in
ubuntu.

The relevant log lines from gvfs-afc are:

gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
gvfsd[1855]: afc: Lockdown client try #0
gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

The fix is here in the upstream github:

https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1718554/+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 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Jeremy Bicha]

This is fixed in 2.36.10-2. We can sync that version from Debian
tomorrow.

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Fix Committed

** Changed in: gdk-pixbuf (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+subscriptions

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

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

[Brian Murray]

I found the description somewhat confusing because 'Unattended-Upgrade
::Remove-New-Unused-Dependencies "true"; doesn't actually exist in
/etc/apt/apt.conf.d/50unattended-upgrades, rather that's the default
setting in unattended-upgrades since 0.90. Regardless, I was able to
recreate the issue on an Ubuntu 16.04 system via the following
procedure.

1) Use apt-get install to install a new kernel (linux-image-generic)
2) Run unattended-upgrades (observe "no pending auto-removals")

However, running 'sudo apt autoremove' does want to remove an old
kernel.

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Jeremy Bicha]

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

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

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+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 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Sebastien Bacher]

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => High

** Changed in: gdk-pixbuf (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Tags added: block-proposed

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+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 1691096] Re: mysql in lxd fails to start with systemd 233, 234: failed at step KEYRING

[Bug Watch Updater]

** Changed in: systemd
   Status: New => Fix Released

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

Title:
  mysql in lxd fails to start with systemd 233, 234: failed at step
  KEYRING

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Artful:
  Triaged

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1691096/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

[Brian Murray]

I've uploaded this to the SRU queue for review by the SRU team.

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

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

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

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

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

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  
  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  [other info]

  related to bug 1532146

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1663747] Re: unity_inspector_get_unity_running improperly returns true on KDE 5.6

[Peter Maciejko]

Do you plan to release any patch for this issue?

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

Title:
  unity_inspector_get_unity_running improperly returns true on KDE 5.6

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  Chromium uses unity_inspector_get_unity_running to determine if 
close/minimize/maximize buttons are hidden when in a maximized state.
  
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/unity_service.cc?rcl=0ddb4374a9221dba28e9ea8a1edaacb32dcc0861=124

  libunity checks if the com.canonical.Unity Dbus service is created and
  uses that as the return value for unity_inspector_get_unity_running.
  (see src/unity-inspector.vala)

  KDE Plasma 5.6 supports the unity launcher API and creates a
  com.canonical.Unity service.  Even though unity is certainly not
  running, UnityInspector thinks it is.

  Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=594490

  KDE bug report:
  https://bugs.kde.org/show_bug.cgi?id=360403

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1663747/+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 1718526] [NEW] Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Harry]

Public bug reported:

After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the tiff 
files cannot be opened any more.
For example Eye of Gnome claims the file type tiff is unknown.
Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue and 
tiff's are OK.

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful-proposed

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1718526/+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 1648183] Re: Crackling and popping sound when using headphones

[Erikas]

Slight updated SYSTEMD workaround script from my previous comment (used
to fail on boot). See updated at
https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX430#Headphones_audio_is_too_low

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Jarno Suni]

Tried version 0.90ubuntu0.8 and it worked ok.

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1544942

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 152756] Re: stale files in /var/lib/initramfs-tools after removing kernel

[Brendan]

Just for posterity's sake, I was able to solve my issue of older
initrd's consuming all of the space in /boot by removing the ones whose
kernel had been purged.

I had a /boot partition that was quite small and nearly every kernel
upgrade would fail with "no space left on device" messages.

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

Title:
  stale files in /var/lib/initramfs-tools after removing kernel

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  Removing a kernel image and accompanying headers with apt-get remove
  --purge does not seem to remove the corresponding configuration file
  in  /var/lib/initramfs-tools. This leads to problems when either grub,
  a kernel, initramfs-tools or any other package which leads to a grub
  menu rebuild is installed, updated or removed. Eg. after having
  removed a kernel image (2.6.23-t23-04 - a homebrew image made with
  make-kpkg) this happens when I try to use apt:

  # apt-get install some_package
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem. 

  # dpkg --configure -a
  Setting up initramfs-tools (0.85eubuntu20) ...
  update-initramfs: deferring update (trigger activated)

  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.23-t23-04
  Cannot find /lib/modules/2.6.23-t23-04
  update-initramfs: failed for /boot/initrd.img-2.6.23-t23-04
  dpkg: subprocess post-installation script returned error exit status 1

  Removing the stale configuration files in /var/lib/initramfs-tools
  makes dpkg happy again

  As to whether this is a bug in initramfs-tools (which could ignore or
  remove configuration files for which no corresponding kernel image is
  found) or the kernel package (which could contain a config file
  reference to  /var/lib/initramfs-tools/version_number-release) I'll
  leave to the respective package maintainers.

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

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

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

[Tyler Hicks]

I had previously attached a slightly old version of the lp1567597-test.c
program that contained a mistake. I'm now attaching the corrected
version after fetching it from my testing VM.

** Attachment removed: "lp1567597-test.c"
   
https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4953120/+files/lp1567597-test.c

** Attachment added: "lp1567597-test.c"
   
https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4954002/+files/lp1567597-test.c

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

Title:
  [FFe] implement 'complain mode' in seccomp for developer mode with
  snaps

Status in Snappy:
  Confirmed
Status in libseccomp package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  The exit code should be 0 and you should have an entry in the system
  log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  [Regression Potential]

  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older
  kernels that don't support it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1567597/+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 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

[netikras]

BTW I'm on Mint Sarah

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Jan 28 11:57:37 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+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 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

[netikras]

I'll spill some gasoline on this fire.

I've been suffering from laptop (dell xps 13 w/ skylake) freezes after
it shuts down the screen due to inactivity. I call that frezes because
when it happens there is no way to wake the screen up. SSH is down.
ctrl-alt-f1 and bling-typing is not working. suspend button is not
responding. s2ram command is ignorant too. And since I do not have a
screen (a laptop, remember?) I try all these things blindly.

So the laptop basically stops responding. Each time (3-5 occurences this
year) post mortem analysis reveals that one of last syslog entries is:

syslog.1:9316:Sep 20 20:51:56 netikras-xps kernel: [477714.359255]
[drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on
pipe A (start=330999 end=331000) time 147 us, min 1788, max 1799,
scanline start 1785, end 1801


As you see from the log attached this error occurs rather often. Maybe it's a 
coincidence, maybe it's not. But I have surely noticed that this error is 
always one of the last syslog records ante mortem.

Ping me if anyone needs any more details, I'm subscribing to this thread

** Attachment added: "zegrep -Hn tomic syslog*"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+attachment/4954000/+files/atomic.grep

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
 

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Balint Reczey]

@Ethan Based on profiling real-life scenario (updating unstable with 100+ 
packages) I believe I was able to make u-u ~10 > times faster that should bring 
down the time of your test of upgrading xenial with all security updates to 
below one hour.
Since running only dpkg's part took more than 30  minutes I think this state is 
good for Artful and for backporting the fixes to older releases.
I've set up a separate PPA for u-u testing if you would like to verify the 
speedup & other fixes:
https://launchpad.net/~rbalint/+archive/ubuntu/unattended-upgrades

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

[Balint Reczey]

** Tags added: artful

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u by ~90% which brings current worst-case (xenial
  with no security fixes -> fully updated) run-time down to tolerable
  levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
     * Handle recovering from broken dh_installinit override on Ubuntu, too
     * Declare needs-reboot for autopkgtests
     * Clean up more test artifacts
     * Run u-u-s only when running on AC power
     * Catch SystemError from fetcher.run(), too
     * Default to MinimalSteps=True in most tests to excercise default setting
     * Check only changed packages in check_changes_for_sanity()
     * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1399945] Re: Settings, Preferences, ect. - All keyboard input is added twice

[Paul Gevers]

I just found this link¹; does it help to prevent the issue?

'''
Typing in edit fields generate duplicate letters

This is more likely to happen under Ubuntu and Ubunto derived distros,
and with GNOME Desktop but other distros/Desktop environments can be
affected too.

The problem is originated by bugs in the ibus Input Method System.
Unfortunately Ibus is the default input method of GNOME desktop.

If you don't know what an IM is, this means that you do not need it, and
therefore the easiest way is to disable IM's at all.

In order to do that you have a number of options, namely:

1 - Disable (or set to "none") the Input Method in System
Settings->Preferences->Input Method

2 - Add the three following lines in /etc/profile (system wide)

export GTK_IM_MODULE=gtk-im-context-simple
export QT_IM_MODULE=simple
export XMODIFIERS=@im=none

3 - Add a file named input_method.sh containing just the 3 lines
above in /etc/profile.d (system wide)

4 - Add the 3 lines above in the home directory ~/.xprofile (per
user). If there's no ~/.xprofile in your home directory, you should
create one.

5 - Create a Lazarus launching script containing the same 3 lines.
(affects only Lazarus)

Methods 1 and 2 may not survive after a system update, while 3,4 and 5
will.

Be aware that both GTK and QT applications may change dynamically the
IM. If you experience the problem in an apparently random way, chances
are good that some other application is enabling again an IM and fails
to set to default when terminates. If such is the case method 5 is the
only one suitable.

You may find more information about Input Methods, and how to deal with
them in:

https://fedoraproject.org/wiki/I18N/InputMethods[2] (This is Fedora
specific but most informations apply in general)

http://www.pinyinjoe.com/linux/ubuntu-12-chinese-setup.htm[3] (This is Ubuntu 
specific, but again most informations apply in general. It explains how to 
enable IM but the info can be used also to disable it) 
'''

¹
http://wiki.lazarus.freepascal.org/Lazarus_Faq#Typing_in_edit_fields_generate_duplicate_letters

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

Title:
  Settings, Preferences, ect. - All keyboard input is added twice

Status in Winff:
  Unknown
Status in ibus package in Ubuntu:
  New
Status in winff package in Ubuntu:
  New

Bug description:
  Test Case:
  Open winff
  Try to edit or add something using keyboard. All characters are doubled
  Screen shows attempt to add /Videos to Output Folder  box

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: winff 1.5.3-4ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.15-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  6 10:32:03 2014
  InstallationDate: Installed on 2014-11-16 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114)
  PackageArchitecture: all
  SourcePackage: winff
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/winff/+bug/1399945/+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 1713560] Re: Lenovo Ideapad 320 touchpad not detected

[n]

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

This is a duplicate of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 since you
have the ELAN0608 touchpad according to your UdevDb.txt. Your touchpad
should work on the latest upstream kernel. Otherwise, follow the bug I
linked to.

** This bug has been marked a duplicate of bug 1708852
   Touchpad not detected

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

Title:
  Lenovo Ideapad 320 touchpad not detected

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04

  xserver-xorg-input-synaptics:
Installed: 1.9.0-1ubuntu1
Candidate: 1.9.0-1ubuntu1
Version table:
   *** 1.9.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I get no response from touchpad. External mouse working.

  Touchpad not detected in /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=101400800100c03 430 0 2
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=0bda Product=58ea Version=0008
  N: Name="EasyCamera"
  P: Phys=usb-:00:14.0-8/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event11 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0005 Vendor=046d Product=b012 Version=0014
  N: Name="MX Master"
  P: Phys=C8:3D:D4:F8:3E:78
  S: Sysfs=/devices/virtual/misc/uhid/0005:046D:B012.0001/input/input14
  U: Uniq=CB:2B:20:FA:A0:6B
  H: Handlers=sysrq kbd mouse0 event12 
  B: PROP=0
  B: EV=100017
  B: KEY= 10007 ff8007ff febeffdfffef 
fffe
  B: REL=143
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 28 

[Touch-packages] [Bug 1718498] [NEW] My computer doesn't recognise my HP laserjet P2014 printer

[Ramón Molina Castillo]

Public bug reported:

I plug the printer and the computer doesn't recognise it has been
plugged and, consequently, I can't install drivers or whatever to print.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Sep 20 19:31:37 2017
DistUpgraded: 2016-12-05 16:25:32,245 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Falló al ejecutar el proceso hijo 
«./xorg_fix_proprietary.py» (No existe el archivo o el directorio))
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] G96M [GeForce 9600M GT] [1025:0146]
InstallationDate: Installed on 2016-10-18 (337 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
MachineType: Acer Aspire 6935
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=feacfa40-5ec5-4181-b5d1-17727adeb3bb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-05 (289 days ago)
dmi.bios.date: 08/07/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 6935
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd08/07/2008:svnAcer:pnAspire6935:pvrV1.05:rvnAcer:rnAspire6935:rvrPSMBOU-1234567:cvnAcer:ct1:cvrN/A:
dmi.product.name: Aspire 6935
dmi.product.version: V1.05
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Sep 20 19:30:38 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.4
xserver.video_driver: nouveau

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


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

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

Title:
  My computer doesn't recognise my HP laserjet P2014 printer

Status in xorg package in Ubuntu:
  New

Bug description:
  I plug the printer and the computer doesn't recognise it has been
  plugged and, consequently, I can't install drivers or whatever to
  print.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 20 19:31:37 2017
  DistUpgraded: 2016-12-05 16:25:32,245 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Falló al ejecutar el proceso hijo 
«./xorg_fix_proprietary.py» (No existe el archivo o el directorio))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] G96M [GeForce 9600M GT] [1025:0146]
  InstallationDate: Installed on 2016-10-18 (337 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 6935
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=feacfa40-5ec5-4181-b5d1-17727adeb3bb ro quiet 

[Touch-packages] [Bug 1718496] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  internal ubuntu error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports:
   640:0:124:33427801:2017-09-19 18:50:03.186740159 +0200:2017-09-19 
18:50:04.186740159 +0200:/var/crash/_usr_sbin_apache2.0.crash
   640:1000:124:6951329:2017-09-20 12:00:08.761954307 +0200:2017-09-20 
12:00:09.761954307 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:124:126808:2017-09-20 11:59:59.477667643 +0200:2017-09-20 
11:56:53.87844 +0200:/var/crash/_usr_bin_compiz.1000.crash
   640:1000:124:1088730:2017-09-19 10:43:45.377321243 +0200:2017-09-19 
10:43:46.377321243 
+0200:/var/crash/_opt_teamviewer_tv_bin_TeamViewer_Desktop.1000.crash
   640:1000:124:4533173:2017-09-20 12:00:03.257773920 +0200:2017-09-20 
12:00:00.057684024 
+0200:/var/crash/_opt_teamviewer_tv_bin_TVGuiDelegate.1000.crash
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Sep 20 12:00:03 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-08-27 (23 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SegvAnalysis:
   Segfault happened at: 0x7fe0edd39009:mov(%rbx),%rdi
   PC (0x7fe0edd39009) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-31 (20 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin nopasswdlogin 
plugdev sambashare scanner sudo tape video www-data

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

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

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

[Jarno Suni]

** Tags added: full-boot

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1695583] Re: package resolvconf 1.78ubuntu2 [modified: lib/systemd/system/resolvconf.service usr/share/doc/resolvconf/changelog.gz] failed to install/upgrade: package resolvconf

[Launchpad Bug Tracker]

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

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

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

Title:
  package resolvconf 1.78ubuntu2 [modified:
  lib/systemd/system/resolvconf.service
  usr/share/doc/resolvconf/changelog.gz] failed to install/upgrade:
  package resolvconf is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  vcvvv

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2 [modified: 
lib/systemd/system/resolvconf.service usr/share/doc/resolvconf/changelog.gz]
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  2 07:23:57 2017
  DuplicateSignature:
   package:resolvconf:1.78ubuntu2 [modified: 
lib/systemd/system/resolvconf.service usr/share/doc/resolvconf/changelog.gz]
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package resolvconf (--configure):
package resolvconf is not ready for configuration
  ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-22 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 [modified: 
lib/systemd/system/resolvconf.service usr/share/doc/resolvconf/changelog.gz] 
failed to install/upgrade: package resolvconf is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1695583/+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 1718487] [NEW] package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: пакет dnsmasq-base не готов к настройке настройка невозможна (текущее состояние: «half-insta

[Alexander]

Public bug reported:

LTS 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 20 15:09:22 2017
ErrorMessage: пакет dnsmasq-base не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
InstallationDate: Installed on 2016-09-22 (362 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: dnsmasq
Title: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: 
пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее 
состояние: «half-installed»)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade:
  пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  LTS 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 15:09:22 2017
  ErrorMessage: пакет dnsmasq-base не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2016-09-22 (362 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: 
пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее 
состояние: «half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1718487/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

[Ubuntu Foundations Team Bug Bot]

The attachment "lp1718055-trusty.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  
  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  [other info]

  related to bug 1532146

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1717241] Re: nautilus crashed with signal 5 in _XReply() - drag and drop crash

[Rodrigo Alconchel]

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nautilus crashed with signal 5 in _XReply() - drag and drop crash

Status in nautilus package in Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  To reproduce on a fully updated Ubuntu Desktop 16.04 system with
  Unity:

  Step 1: Start nautilus

  Step 2: Drag and drop a file to any target: to a different folder in
  the same nautilus window, to another folder in a different nautilus
  window, etc. ... The target is irrelevant.

  Expected to happen: File successfully copied or moved.

  Actually happened: Mouse pointer changes to a hand with a plus sign.
  Source file moves only slightly and then freezes, never makes it to
  the target. Application locks up for a few seconds, and then the
  application window vanishes. Crash report is then generated.

  Ubuntu release: Ubuntu 16.04.3 LTS

  Nautilus package version: Installed: 1:3.18.4.is.3.14.3-0ubuntu6

  Additional (and maybe relevant) notes:

  1) Drag and drop function seems broken generally, across applications,
  not just in nautilus. For instance, same behavior appears when trying
  to drag and drop a Thunderbird message to another Thunderbird folder,
  or when trying to drag and drop a cell or a range of cells within the
  same Libreoffice Calc spreadsheet.

  2) Interestingly, application windows can be dragged and dropped
  across display monitors (3 monitor setup), without any problems.

  3) I am using proprietary NVIDIA drivers, but please do not suggest
  using nouveau drivers, because they work horribly (heavy display
  corruption, pixelated screen, and constant mouse flickering)

  4) Graphics setup: NVIDIA Quadro NVS 450 card with twin GPU and 4
  heads. NVIDIA proprietary driver version 340.102 (installed from
  ubuntu repositories, not from proprietary NVIDIA installer; this is
  the correct driver version for this card according to NVIDIA
  documentation). 3 monitors connected in a simple horizontal layout.

  5) Nautilus extension installed: nautilus-share  0.7.3-2ubuntu1

  6) Attaching a nautilus debugging log from terminal command:
  G_DEBUG="all" NAUTILUS_DEBUG ="All" nautilus

  7) Attaching X Org log file with -logverbose 6 option

  8) Attaching xorg.conf configuration file

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 640:1000:116:10641522:2017-09-14 12:49:07.088649823 
+0200:2017-09-14 12:27:03.381461842 
+0200:/var/crash/_usr_bin_nautilus.1000.crash
  CurrentDesktop: Unity
  Date: Thu Sep 14 11:02:40 2017
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1481715745
  PackageArchitecture: all
  ProcCmdline: nautilus
  ProcCwd: /var/crash
  Signal: 5
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XShapeGetRectangles () from /usr/lib/x86_64-linux-gnu/libXext.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2017-09-14T09:20:26.397971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1717241/+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 1714429] Re: hang on shutdown with static network configuration

[Balint Reczey]

When you see the messages appearing on the screenshot u-u is
downloading/installing packages in the background and unattended-
upgrade-shutdown is waiting for u-u to finish.

Do you see related activity in /var/log/unattended-upgrades/* ?

I assume you have not changed u-u configuration.

There should be no difference in using DHCP/static network
configuration, but the upgrade process starts only on AC power and is
triggered by /lib/systemd/system/apt-daily-upgrade.timer which may also
influence testing.

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

Title:
  hang on shutdown with static network configuration

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Hi Folks


  Problem:

  system doesn't reboot/shutdown but *only* when the network
  configuration is static (described below). When I change the network
  configuration to dhcp, the bug doesn't occur.


  The network configuration is set to static:

  iface eth0 inet static
address my_ip
netmask 255.255.255.224
gateway router_ip
dns-nameservers primary_dns secondary_dns 8.8.8.8 8.8.4.4
  (I have masked some configuration values)


  lsb_release -rd
  Release:16.04


  apt-cache policy unattended-upgrades
  Installed: 0.90ubuntu0.7
  Candidate: 0.90ubuntu0.7


  symptoms:

  a python3 process appears ~2sec after the shutdown command: 2005
  python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown

  Screenshot of the VM virtual display output as attachment.

  only / is mounted, all other file systems are unmounted already:
  /boot, /var, /tmp, /var/log, /var/tmp


  other informations:

  The network still works. I can ping different addresses like
  google.com, debian.org, and other stuff.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714429/+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 1717241] Re: nautilus crashed with signal 5 in _XReply() - drag and drop crash

[Rodrigo Alconchel]

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

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

Title:
  nautilus crashed with signal 5 in _XReply() - drag and drop crash

Status in nautilus package in Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  To reproduce on a fully updated Ubuntu Desktop 16.04 system with
  Unity:

  Step 1: Start nautilus

  Step 2: Drag and drop a file to any target: to a different folder in
  the same nautilus window, to another folder in a different nautilus
  window, etc. ... The target is irrelevant.

  Expected to happen: File successfully copied or moved.

  Actually happened: Mouse pointer changes to a hand with a plus sign.
  Source file moves only slightly and then freezes, never makes it to
  the target. Application locks up for a few seconds, and then the
  application window vanishes. Crash report is then generated.

  Ubuntu release: Ubuntu 16.04.3 LTS

  Nautilus package version: Installed: 1:3.18.4.is.3.14.3-0ubuntu6

  Additional (and maybe relevant) notes:

  1) Drag and drop function seems broken generally, across applications,
  not just in nautilus. For instance, same behavior appears when trying
  to drag and drop a Thunderbird message to another Thunderbird folder,
  or when trying to drag and drop a cell or a range of cells within the
  same Libreoffice Calc spreadsheet.

  2) Interestingly, application windows can be dragged and dropped
  across display monitors (3 monitor setup), without any problems.

  3) I am using proprietary NVIDIA drivers, but please do not suggest
  using nouveau drivers, because they work horribly (heavy display
  corruption, pixelated screen, and constant mouse flickering)

  4) Graphics setup: NVIDIA Quadro NVS 450 card with twin GPU and 4
  heads. NVIDIA proprietary driver version 340.102 (installed from
  ubuntu repositories, not from proprietary NVIDIA installer; this is
  the correct driver version for this card according to NVIDIA
  documentation). 3 monitors connected in a simple horizontal layout.

  5) Nautilus extension installed: nautilus-share  0.7.3-2ubuntu1

  6) Attaching a nautilus debugging log from terminal command:
  G_DEBUG="all" NAUTILUS_DEBUG ="All" nautilus

  7) Attaching X Org log file with -logverbose 6 option

  8) Attaching xorg.conf configuration file

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 640:1000:116:10641522:2017-09-14 12:49:07.088649823 
+0200:2017-09-14 12:27:03.381461842 
+0200:/var/crash/_usr_bin_nautilus.1000.crash
  CurrentDesktop: Unity
  Date: Thu Sep 14 11:02:40 2017
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1481715745
  PackageArchitecture: all
  ProcCmdline: nautilus
  ProcCwd: /var/crash
  Signal: 5
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XShapeGetRectangles () from /usr/lib/x86_64-linux-gnu/libXext.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2017-09-14T09:20:26.397971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1717241/+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 1718476] [NEW] dont know

[adage n]

Public bug reported:

I don't know

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Sep 20 21:20:59 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
InstallationDate: Installed on 2017-08-25 (26 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Inspiron 3521
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=92f99876-c22f-40f0-849b-7afdc26f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0FXP6Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:pnInspiron3521:pvrA10:rvnDellInc.:rn0FXP6Y:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron 3521
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1

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


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

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

Title:
  dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 20 21:20:59 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  InstallationDate: Installed on 2017-08-25 (26 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3521
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=92f99876-c22f-40f0-849b-7afdc26f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FXP6Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:pnInspiron3521:pvrA10:rvnDellInc.:rn0FXP6Y:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  

[Touch-packages] [Bug 1717309] Re: 17.10 Artful Aardvark Mascot

[Launchpad Bug Tracker]

** Branch linked: lp:ubiquity-slideshow-ubuntu

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

Title:
  17.10 Artful Aardvark Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Aardvark attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1717309/+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 500175] Re: Canceling an installation in Software Center crashes debconf with "Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.

[Sebastien Bacher]

Unsure why that was added to the artful list, software-center is not
used there and gnome-software is using packagkit and not aptdaemon now,
setting as notfixing for this cycle

** Tags removed: rls-aa-incoming
** Tags added: rls-aa-notfixing

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

Title:
  Canceling an installation in Software Center crashes debconf with "Use
  of uninitialized value $reply in scalar chomp at
  /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,"

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  Confirmed
Status in aptdaemon source package in Lucid:
  Won't Fix
Status in debconf source package in Lucid:
  Won't Fix
Status in software-center source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: acroread

  I accidentally clicked "Cancel" when it asked me if I wanted to set
  Adobe Reader as the default PDF viewer. It then apparently crashed.

  == HOW TO REPRODUCE ==
  In software-center choose "Adobe Reader 9" and install it.
  At prompt "Set Adobe Reader as the default PDF viewer" click "Cancel"
  The installation crashes with the error below

  The relevant error is
  =
  Setting up acroread (9.2-1karmic1) ...
  Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 6.
  Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 6.
  Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 6.
  Use of uninitialized value in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 202,  line 6.
  Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 6.
  Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 6.
  Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 6.
  Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212,  line 6.
  Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104,  line 6.
  Use of uninitialized value $val in substitution (s///) at 
/usr/share/perl5/Debconf/Format/822.pm line 83,  line 4.
  Use of uninitialized value $val in concatenation (.) or string at 
/usr/share/perl5/Debconf/Format/822.pm line 84,  line 4.
  dpkg: error processing acroread (--configure):
   subprocess installed post-installation script returned error exit status 128
  =

  ProblemType: Package
  AptOrdering:
   acroread: Install
   acroread: Configure
  Architecture: i386
  Date: Thu Dec 24 17:06:00 2009
  DistroRelease: Ubuntu 9.10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  NonfreeKernelModules: wl
  Package: acroread (not installed)
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: acroread
  Title: package acroread (not installed) failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/500175/+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 1718006] Re: gnome-control-center segfault on vpn changes

[Sebastien Bacher]

there is a working patch upstream now

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  gnome-control-center segfault on vpn changes

Status in gnome-control-center:
  Confirmed
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Maybe when I was configuring a printer

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 20:55:47 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1475 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: gnome-control-center printers
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe50b4232cc : testb  
$0x4,0x16(%rdx)
   PC (0x7fe50b4232cc) ok
   source "$0x4" ok
   destination "0x16(%rdx)" (0x10016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1718006/+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 1718450] Re: package libdbus-1-3 1.10.6-1ubuntu3.3 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz usr/share/doc/libdbus-1-3/copyright]

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libdbus-1-3 1.10.6-1ubuntu3.3 [modified:
  usr/share/doc/libdbus-1-3/NEWS.gz
  usr/share/doc/libdbus-1-3/changelog.Debian.gz
  usr/share/doc/libdbus-1-3/copyright] failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is
  different from other instances of package libdbus-1-3:i386

Status in dbus package in Ubuntu:
  New

Bug description:
  Bug occurred while attempting to reinstall TeamViewer, after it
  disappeared from my system. I have asked an Ask Ubuntu question here
  https://askubuntu.com/questions/957745/libdbus-shared-object-library-
  causing-teamviewer-issues with some details on the troubleshooting
  process I was going through when this error occurred, though there
  were many more stages to the initial debugging process. My current
  hypothesis is that perhaps the 64 bit and 32 bit versions of the
  libdbus shared library have become incorrectly cross-linked in some
  way and this is blocking be from correctly installing or removing the
  library.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 15:39:45 2017
  DuplicateSignature:
   package:libdbus-1-3:1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
   Unpacking libdbus-1-3:i386 (1.10.6-1ubuntu3.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libdbus-1-3_1.10.6-1ubuntu3.3_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is 
different from other instances of package libdbus-1-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libdbus-1-3/copyright', which is different from other instances 
of package libdbus-1-3:i386
  InstallationDate: Installed on 2017-07-04 (78 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: dbus
  Title: package libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is different 
from other instances of package libdbus-1-3:i386
  UpgradeStatus: Upgraded to xenial on 2017-09-12 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1718450/+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 1718450] [NEW] package libdbus-1-3 1.10.6-1ubuntu3.3 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz usr/share/doc/libdbus-1-3/copyrigh

[Peter Carter]

Public bug reported:

Bug occurred while attempting to reinstall TeamViewer, after it
disappeared from my system. I have asked an Ask Ubuntu question here
https://askubuntu.com/questions/957745/libdbus-shared-object-library-
causing-teamviewer-issues with some details on the troubleshooting
process I was going through when this error occurred, though there were
many more stages to the initial debugging process. My current hypothesis
is that perhaps the 64 bit and 32 bit versions of the libdbus shared
library have become incorrectly cross-linked in some way and this is
blocking be from correctly installing or removing the library.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 20 15:39:45 2017
DuplicateSignature:
 package:libdbus-1-3:1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
 Unpacking libdbus-1-3:i386 (1.10.6-1ubuntu3.3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libdbus-1-3_1.10.6-1ubuntu3.3_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is 
different from other instances of package libdbus-1-3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libdbus-1-3/copyright', which is different from other instances 
of package libdbus-1-3:i386
InstallationDate: Installed on 2017-07-04 (78 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: dbus
Title: package libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is different 
from other instances of package libdbus-1-3:i386
UpgradeStatus: Upgraded to xenial on 2017-09-12 (8 days ago)

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


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

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

Title:
  package libdbus-1-3 1.10.6-1ubuntu3.3 [modified:
  usr/share/doc/libdbus-1-3/NEWS.gz
  usr/share/doc/libdbus-1-3/changelog.Debian.gz
  usr/share/doc/libdbus-1-3/copyright] failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is
  different from other instances of package libdbus-1-3:i386

Status in dbus package in Ubuntu:
  New

Bug description:
  Bug occurred while attempting to reinstall TeamViewer, after it
  disappeared from my system. I have asked an Ask Ubuntu question here
  https://askubuntu.com/questions/957745/libdbus-shared-object-library-
  causing-teamviewer-issues with some details on the troubleshooting
  process I was going through when this error occurred, though there
  were many more stages to the initial debugging process. My current
  hypothesis is that perhaps the 64 bit and 32 bit versions of the
  libdbus shared library have become incorrectly cross-linked in some
  way and this is blocking be from correctly installing or removing the
  library.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 15:39:45 2017
  DuplicateSignature:
   package:libdbus-1-3:1.10.6-1ubuntu3.3 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz 
usr/share/doc/libdbus-1-3/copyright]
   Unpacking libdbus-1-3:i386 (1.10.6-1ubuntu3.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libdbus-1-3_1.10.6-1ubuntu3.3_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libdbus-1-3/copyright', which is 
different from other instances of package libdbus-1-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libdbus-1-3/copyright', which is different from other instances 
of package libdbus-1-3:i386
  InstallationDate: Installed on 2017-07-04 (78 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: dbus
  Title: package libdbus-1-3 1.10.6-1ubuntu3.3 [modified: 

[Touch-packages] [Bug 1718006] [NEW] gnome-control-center segfault on vpn changes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Maybe when I was configuring a printer

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 20:55:47 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-03 (1475 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: gnome-control-center printers
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe50b4232cc :   testb  
$0x4,0x16(%rdx)
 PC (0x7fe50b4232cc) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x10016) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

** Affects: gnome-control-center
 Importance: Medium
 Status: Confirmed

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: amd64 apport-crash artful rls-aa-incoming
-- 
gnome-control-center segfault on vpn changes
https://bugs.launchpad.net/bugs/1718006
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1713803] Re: replacement of resolvconf with systemd needs integration

[Scott Moser]

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

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

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  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 x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+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 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

[Philipp Kern]

This is fixed in v232 and up.

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

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+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 1718444] [NEW] systemd-sysctl in Xenial is not obeying the order of the sysctls

[Philipp Kern]

Public bug reported:

systemd-sysctl in Xenial forces itself over procps by shipping a link
for procps.service to systemd-sysctl.service. However, it does not obey
the order both of the files and also of the sysctls within the files.
Instead it uses a simple hashmap. As it turns out that's fixed upstream
and systemd master uses an ordered hashmap because of this, which at
least preserves order within single files. Traditionally files in
sysctl.d have been prefixed with numbers to ensure an order and that's
now completely non-deterministic on Xenial.

Relevant upstream commit:
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

Note that conf_files_list_nulstr in master sorts the configuration files
using strcmp, so even order of configuration files should be obeyed.

** Affects: systemd (Ubuntu)
 Importance: Medium
 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/1718444

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+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 1311503] Re: compiz crashes with segfault error in libnux-graphics

[La Luz]

Today I had the same issue with 16.04 and installing that package solved
it

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

Title:
  compiz crashes with segfault error in libnux-graphics

Status in Nux:
  Invalid
Status in nux package in Ubuntu:
  Invalid

Bug description:
  When I login compiz crashes with a segfault error in libnux-graphics.
  My screen turns blue (with nouveau driver) or with white blocks
  (nvidia current driver). In dmesg the following messages are shown:

  [  808.965220] compiz[7568]: segfault at b0 ip 7f9246244a0f sp 
7fff0a7a1450 error 4 in libnux-graphics-4.0.so.0.6.0[7f92461f8000+cb000]
  [  813.851368] compiz[7722]: segfault at b0 ip 7f34215bca0f sp 
7fffe2e356d0 error 4 in libnux-graphics-4.0.so.0.6.0[7f342157+cb000]

  I only get this error with my Nvidia GTX 460 card. I do not get these
  errors with my radeon and intel video cards (my other pc and laptop).
  All running latest Trusty 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1311503/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

[Dan Streetman]

** Patch added: "lp1718055-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+attachment/4953633/+files/lp1718055-trusty.debdiff

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  
  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  [other info]

  related to bug 1532146

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Chris J Arges]

Hello Jarno, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.90ubuntu0.8 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 1717309] Re: 17.10 Artful Aardvark Mascot

[Mathieu Trudel-Lapierre]

** Also affects: ubiquity-slideshow-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: New => In Progress

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Importance: Undecided => High

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

Title:
  17.10 Artful Aardvark Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Aardvark attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1717309/+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 1718434] [NEW] Crash while playing video

[Aravind R]

Public bug reported:

Crash while playing video

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 20 19:29:52 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0408:a030 Quanta Computer, Inc. 
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575G:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575G
dmi.product.version: V1.25
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83+git1708241830.f19dbb~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3~git1708280730.242212~gd~x
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Sep 20 19:18:12 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages ubuntu xenial

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

Title:
  Crash while playing video

Status in xorg package in Ubuntu:
  New

Bug description:
  Crash while playing video

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: 

[Touch-packages] [Bug 1706818] Update Released

[Chris J Arges]

The verification of the Stable Release Update for ntp 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 ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1706818

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Released
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  System Information:

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

   apt-cache policy ntpdate:

     ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

   apt-cache policy ntp:

     

[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.8p4+dfsg-3ubuntu5.7

---
ntp (1:4.2.8p4+dfsg-3ubuntu5.7) xenial; urgency=medium

  * d/ntp.init: fix lock path to match the ntpdate ifup hook. Furthermore
drop the usage of lockfile-progs calls and instead use flock directly.
This is a backport of changes made in 1:4.2.8p7+dfsg-1 (LP: #1706818)

 -- Christian Ehrhardt   Tue, 05 Sep
2017 17:24:43 +0200

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

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Released
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  System Information:

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

   apt-cache policy ntpdate:

     ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 

[Touch-packages] [Bug 1718431] [NEW] crash report

[Aravind R]

Public bug reported:

crash report

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 20 19:24:35 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0408:a030 Quanta Computer, Inc. 
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575G:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575G
dmi.product.version: V1.25
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83+git1708241830.f19dbb~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3~git1708280730.242212~gd~x
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Sep 20 19:18:12 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages ubuntu xenial

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

Title:
  crash report

Status in xorg package in Ubuntu:
  New

Bug description:
  crash report

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: 

[Touch-packages] [Bug 1718435] [NEW] package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Mary]

Public bug reported:

,,

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports:
 640:0:116:106174:2017-09-20 10:57:31.266966581 -0300:2017-09-20 
10:57:32.266966581 -0300:/var/crash/apport.0.crash
 644:0:116:0:2017-09-20 10:57:34.246948771 -0300:2017-09-20 10:57:34.246948771 
-0300:/var/crash/apport.0.upload
 600:109:116:0:2017-09-20 10:57:36.726927044 -0300:2017-09-20 
10:57:36.726927044 -0300:/var/crash/apport.0.uploaded
 600:0:116:89250:2017-09-20 10:56:25.335798501 -0300:2017-09-20 
10:57:45.018858231 -0300:/var/crash/apport-gtk.0.crash
Date: Wed Sep 20 10:56:26 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2015-08-11 (770 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to xenial on 2016-08-08 (408 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in apport package in Ubuntu:
  New

Bug description:
  ,,

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   640:0:116:106174:2017-09-20 10:57:31.266966581 -0300:2017-09-20 
10:57:32.266966581 -0300:/var/crash/apport.0.crash
   644:0:116:0:2017-09-20 10:57:34.246948771 -0300:2017-09-20 
10:57:34.246948771 -0300:/var/crash/apport.0.upload
   600:109:116:0:2017-09-20 10:57:36.726927044 -0300:2017-09-20 
10:57:36.726927044 -0300:/var/crash/apport.0.uploaded
   600:0:116:89250:2017-09-20 10:56:25.335798501 -0300:2017-09-20 
10:57:45.018858231 -0300:/var/crash/apport-gtk.0.crash
  Date: Wed Sep 20 10:56:26 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2015-08-11 (770 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (408 days ago)

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

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

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

[Tyler Hicks]

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

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

Title:
  [FFe] implement 'complain mode' in seccomp for developer mode with
  snaps

Status in Snappy:
  Confirmed
Status in libseccomp package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  The exit code should be 0 and you should have an entry in the system
  log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  [Regression Potential]

  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older
  kernels that don't support it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1567597/+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 1586941] Re: Randomly segfault on BYT with 4.4 kernel

[Yuan-Chen Cheng]

too old.

** Changed in: oem-priority
   Status: Confirmed => Won't Fix

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

Title:
  Randomly segfault on BYT with 4.4 kernel

Status in OEM Priority Project:
  Won't Fix
Status in upstart :
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  
  We have a randomly crash bug when using 14.04 (trusty) upstart 
(1.12.1-0ubuntu4.2).

  We've tried the workarounds of LP:1447756 but it doesn't work.
  Also the test case doesn't crash. So we think this is a new bug.

  The bug is also happened on very early stages. And inside the
  installer, it crashes more often then the system. We see it core
  dumped in the installer, but not about to get the core file because
  the squashfs only keeps file in the memory.

  Also when run on system, the filesystem seems to be read-only then so
  there's also no logs.

  We are using 4.4 kernel (linux-image-4.4.0-22-generic
  4.4.0-22.40~14.04.1)

  I'll paste some images and logs after.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1586941/+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 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

[Balint Reczey]

** Patch added: "debdiff compared to Debian's version"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+attachment/4953527/+files/unattended-upgrades_0.97ubuntu1.patch

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** Description changed:

  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow
  
- 0.97 speeds up u-u ~90% which brings current worst-case (xenial with no
- security fixes -> fully updates) run-time down to tolerable levels.
+ 0.97 speeds up u-u by ~90% which brings current worst-case (xenial with
+ no security fixes -> fully updated) run-time down to tolerable levels.
  
  Changes:
-  unattended-upgrades (0.97) unstable; urgency=medium
-  .
-* Handle recovering from broken dh_installinit override on Ubuntu, too
-* Declare needs-reboot for autopkgtests
-* Clean up more test artifacts
-* Run u-u-s only when running on AC power
-* Catch SystemError from fetcher.run(), too
-* Default to MinimalSteps=True in most tests to excercise default setting
-* Check only changed packages in check_changes_for_sanity()
-* Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor
+  unattended-upgrades (0.97) unstable; urgency=medium
+  .
+    * Handle recovering from broken dh_installinit override on Ubuntu, too
+    * Declare needs-reboot for autopkgtests
+    * Clean up more test artifacts
+    * Run u-u-s only when running on AC power
+    * Catch SystemError from fetcher.run(), too
+    * Default to MinimalSteps=True in most tests to excercise default setting
+    * Check only changed packages in check_changes_for_sanity()
+    * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u by ~90% which brings current worst-case (xenial
  with no security fixes -> fully updated) run-time down to tolerable
  levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
     * Handle recovering from broken dh_installinit override on Ubuntu, too
     * Declare needs-reboot for autopkgtests
     * Clean up more test artifacts
     * Run u-u-s only when running on AC power
     * Catch SystemError from fetcher.run(), too
     * Default to MinimalSteps=True in most tests to excercise default setting
     * Check only changed packages in check_changes_for_sanity()
     * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Yuan-Chen Cheng]

** Tags added: xenial

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Triaged
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

[Balint Reczey]

** Patch added: "debdiff compared to latest Ubuntu version"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+attachment/4953526/+files/unattended-upgrades_0.96ubuntu1_to_0.97ubuntu1.patch

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u by ~90% which brings current worst-case (xenial
  with no security fixes -> fully updated) run-time down to tolerable
  levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
     * Handle recovering from broken dh_installinit override on Ubuntu, too
     * Declare needs-reboot for autopkgtests
     * Clean up more test artifacts
     * Run u-u-s only when running on AC power
     * Catch SystemError from fetcher.run(), too
     * Default to MinimalSteps=True in most tests to excercise default setting
     * Check only changed packages in check_changes_for_sanity()
     * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.8.2-1ubuntu8

---
network-manager (1.8.2-1ubuntu8) artful; urgency=medium

  * debian/network-manager.postinst: drop in an empty override file for
NetworkManager to manage all devices for upgrade from any version, as long
as there is no netplan configuration yet. (LP: #1676547)

 -- Brian Murray   Mon, 11 Sep 2017 10:20:18 -0700

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

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Fix Released
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in dpkg package in Debian:
  Fix Released

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1715641/+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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.8.2-1ubuntu8

---
network-manager (1.8.2-1ubuntu8) artful; urgency=medium

  * debian/network-manager.postinst: drop in an empty override file for
NetworkManager to manage all devices for upgrade from any version, as long
as there is no netplan configuration yet. (LP: #1676547)

 -- Brian Murray   Mon, 11 Sep 2017 10:20:18 -0700

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

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

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

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

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

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

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

  Regression Potential
  

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

  Original Description
  

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => In Progress

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u ~90% which brings current worst-case (xenial with
  no security fixes -> fully updates) run-time down to tolerable levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
 * Handle recovering from broken dh_installinit override on Ubuntu, too
 * Declare needs-reboot for autopkgtests
 * Clean up more test artifacts
 * Run u-u-s only when running on AC power
 * Catch SystemError from fetcher.run(), too
 * Default to MinimalSteps=True in most tests to excercise default setting
 * Check only changed packages in check_changes_for_sanity()
 * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1718419] [NEW] Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

[Balint Reczey]

Public bug reported:

The update fixes issues which surfaced when u-u switched installing
updates in minimal steps, most notably the minimal-steps method being
very slow

0.97 speeds up u-u ~90% which brings current worst-case (xenial with no
security fixes -> fully updates) run-time down to tolerable levels.

Changes:
 unattended-upgrades (0.97) unstable; urgency=medium
 .
   * Handle recovering from broken dh_installinit override on Ubuntu, too
   * Declare needs-reboot for autopkgtests
   * Clean up more test artifacts
   * Run u-u-s only when running on AC power
   * Catch SystemError from fetcher.run(), too
   * Default to MinimalSteps=True in most tests to excercise default setting
   * Check only changed packages in check_changes_for_sanity()
   * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

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

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u ~90% which brings current worst-case (xenial with
  no security fixes -> fully updates) run-time down to tolerable levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
 * Handle recovering from broken dh_installinit override on Ubuntu, too
 * Declare needs-reboot for autopkgtests
 * Clean up more test artifacts
 * Run u-u-s only when running on AC power
 * Catch SystemError from fetcher.run(), too
 * Default to MinimalSteps=True in most tests to excercise default setting
 * Check only changed packages in check_changes_for_sanity()
 * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1717280] Re: systemctl stop unattended-upgrades.service hangs during upgrade

[Balint Reczey]

Needs SRU, IMO.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  systemctl stop unattended-upgrades.service hangs during upgrade

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  This morning unattended-upgrades tried to upgrade itself from
  0.93.1ubuntu2.2 to 0.93.1ubuntu2.3. It seems like the prerm script
  tried to run "systemctl stop unattended-upgrades.service" which simply
  hung.  I repeated the command manually and it hung for me as well.
  During this time, dpkg was holding a lock and I could not
  install/upgrade any other packages.  Eventually, after around 10
  minutes, it must have timed out or something and the process finally
  ended.

  It did detect the crash and uploaded the crash report to whatever
  magical place those go...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1717280/+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 1717280] Re: systemctl stop unattended-upgrades.service hangs during upgrade

[Balint Reczey]

I believe i fixed this issue in 0.95, with this commit:
https://github.com/mvo5/unattended-upgrades/commit/ffd53631219b32dfd28cd5dfd447bddd3d8b3d5e

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

Title:
  systemctl stop unattended-upgrades.service hangs during upgrade

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  This morning unattended-upgrades tried to upgrade itself from
  0.93.1ubuntu2.2 to 0.93.1ubuntu2.3. It seems like the prerm script
  tried to run "systemctl stop unattended-upgrades.service" which simply
  hung.  I repeated the command manually and it hung for me as well.
  During this time, dpkg was holding a lock and I could not
  install/upgrade any other packages.  Eventually, after around 10
  minutes, it must have timed out or something and the process finally
  ended.

  It did detect the crash and uploaded the crash report to whatever
  magical place those go...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1717280/+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 1718408] [NEW] Google Login with 2-factor authentication leaves white screen

[Christian Ego]

Public bug reported:

With the current version of Ubuntu 17.04 and GNOME Shell 3.24.0 I can not use 
the online accounts (again!).
This time the dialog shows a white screen after login. 
Google askes on my phone for the access (as expected) but even if I accept it 
shows just a white screen and nothing like confirm or ok.

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

** Attachment added: "Screenshot-20170920140011-737x545.png"
   
https://bugs.launchpad.net/bugs/1718408/+attachment/4953472/+files/Screenshot-20170920140011-737x545.png

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

Title:
  Google Login with 2-factor authentication leaves white screen

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  With the current version of Ubuntu 17.04 and GNOME Shell 3.24.0 I can not use 
the online accounts (again!).
  This time the dialog shows a white screen after login. 
  Google askes on my phone for the access (as expected) but even if I accept it 
shows just a white screen and nothing like confirm or ok.

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

[gatopeich]

This issue has been bothering more of a hundred users for more than a
year. In my case there was a workaround at some point, by downgrading
openvpn to an older version (can't remember which).

Being so prevailing and old, it is quite disgraceful that this is not
being addressed on Ubuntu 16 LTS.

Instead, I see some wall of text here (e.g. comment 80) trying to excuse
the inexcusable.

** Description changed:

  [Triage Notes]
  
- This bug can no longer make progress. Please see comment 50 for details
- and further instructions.
+ Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
+ Please see wall of text on comment 50 for a long excuse.
  
  [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

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

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Triaged
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1718386] Re: package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  just tried to update packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu20
  Uname: Linux 4.12.0-999-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 11:21:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-12-02 (657 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718386/+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 1718386] [NEW] package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Muelli]

Public bug reported:

just tried to update packages

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu20
Uname: Linux 4.12.0-999-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 20 11:21:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2015-12-02 (657 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: systemd
Title: package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed third-party-packages xenial

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

Title:
  package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  just tried to update packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu20
  Uname: Linux 4.12.0-999-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 11:21:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-12-02 (657 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718386/+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 1709500] Re: Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

[Sebastien Bacher]

** Tags added: rls-aa-incoming

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Low => High

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

Title:
  Headerbar buttons that are highlighted/coloured in Adwaita are not
  coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1709500/+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 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

[wiz]

Still present in 17.10. Adding permission from #11 appears to solve it.

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

Title:
  Apparmor profile violated: cupsd does mknod on
  /var/cache/samba/gencache.tdb

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+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 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Jarno Suni]

Also please show the output of:
dpkg-query -Wf'${db:Status-Abbrev} ${Package}\n' | grep -E ' 
linux-(.*-)?image-[0-9]'

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+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 1718371] Re: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"

[Marius Gedminas]

Here's the full journal log of the shutdown process.

** Attachment added: "Journal of the shutdown process"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+attachment/4953370/+files/reboot-hangs.txt

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

Title:
  Reboot hangs forever because /bin/systemctl --force reboot fails with
  "Failed to execute operation: Connection timed out"

Status in systemd package in Ubuntu:
  New

Bug description:
  This morning unattended-upgrades had a reboot scheduled for 6:30 AM.
  The reboot process succeeded in turning off all network access but
  failed to actually reboot.  As far as I can tell, this is because

  Sep 20 06:50:44 fridge systemd[1]: Starting Reboot...
  Sep 20 06:51:09 fridge systemctl[3886]: Failed to execute operation: 
Connection timed out
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Main process 
exited, code=exited, status=1/FAILURE
  Sep 20 06:53:54 fridge systemd[1]: Failed to start Reboot.
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Unit entered 
failed state.
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Failed with 
result 'exit-code'.

  (Don't ask me why it took 20 minutes to get to this point.  Most
  everything was already shut down by 06:35.)

  After this the journal shows a few other random-looking service
  messages

  Sep 20 07:13:44 fridge systemd[1]: Stopping LVM2 metadata daemon...
  Sep 20 07:13:44 fridge systemd[1]: Stopped LVM2 metadata daemon.
  Sep 20 07:51:48 fridge systemd[1]: Started LVM2 metadata daemon.
  Sep 20 07:51:48 fridge systemd[1]: Stopped target Shutdown.

  and the end of a cron session that initiated the unattended-upgrade
  shutdown -r 06:30 call, presumably

  Sep 20 07:52:54 fridge CRON[1176]: pam_unix(cron:session): session
  closed for user root

  and then the machine sat idle waiting for keyboard input, which I
  provided in the form of Alt+SysRq+S,U,B a few hours later.

  
  This has never happened before on this server, which is running Ubuntu 16.04 
LTS since November 2016.  I haven't tried to reproduce this (yet).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 11:10:34 2017
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic 
root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-11-07 (316 days ago)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33TL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD89517-803
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33TL:rvrAAD89517-803:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+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 1718373] [NEW] FTBFS on s390x on ubuntu

[Dimitri John Ledkov]

Public bug reported:

FTBFS on s390x on ubuntu

** Affects: pcre3 (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: New


** Tags: ftbfs s390x

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

Title:
  FTBFS on s390x on ubuntu

Status in pcre3 package in Ubuntu:
  New

Bug description:
  FTBFS on s390x on ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1718373/+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 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Jarno Suni]

Could you attach logs in
/var/log/unattended-upgrades/
from such a system?

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+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 1718371] [NEW] Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"

[Marius Gedminas]

Public bug reported:

This morning unattended-upgrades had a reboot scheduled for 6:30 AM.
The reboot process succeeded in turning off all network access but
failed to actually reboot.  As far as I can tell, this is because

Sep 20 06:50:44 fridge systemd[1]: Starting Reboot...
Sep 20 06:51:09 fridge systemctl[3886]: Failed to execute operation: 
Connection timed out
Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Main process 
exited, code=exited, status=1/FAILURE
Sep 20 06:53:54 fridge systemd[1]: Failed to start Reboot.
Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Unit entered 
failed state.
Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Failed with 
result 'exit-code'.

(Don't ask me why it took 20 minutes to get to this point.  Most
everything was already shut down by 06:35.)

After this the journal shows a few other random-looking service messages

Sep 20 07:13:44 fridge systemd[1]: Stopping LVM2 metadata daemon...
Sep 20 07:13:44 fridge systemd[1]: Stopped LVM2 metadata daemon.
Sep 20 07:51:48 fridge systemd[1]: Started LVM2 metadata daemon.
Sep 20 07:51:48 fridge systemd[1]: Stopped target Shutdown.

and the end of a cron session that initiated the unattended-upgrade
shutdown -r 06:30 call, presumably

Sep 20 07:52:54 fridge CRON[1176]: pam_unix(cron:session): session
closed for user root

and then the machine sat idle waiting for keyboard input, which I
provided in the form of Alt+SysRq+S,U,B a few hours later.


This has never happened before on this server, which is running Ubuntu 16.04 
LTS since November 2016.  I haven't tried to reproduce this (yet).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 20 11:10:34 2017
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic 
root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-11-07 (316 days ago)
dmi.bios.date: 10/02/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33TL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD89517-803
dmi.chassis.type: 2
dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33TL:rvrAAD89517-803:cvn:ct2:cvr:

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

Title:
  Reboot hangs forever because /bin/systemctl --force reboot fails with
  "Failed to execute operation: Connection timed out"

Status in systemd package in Ubuntu:
  New

Bug description:
  This morning unattended-upgrades had a reboot scheduled for 6:30 AM.
  The reboot process succeeded in turning off all network access but
  failed to actually reboot.  As far as I can tell, this is because

  Sep 20 06:50:44 fridge systemd[1]: Starting Reboot...
  Sep 20 06:51:09 fridge systemctl[3886]: Failed to execute operation: 
Connection timed out
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Main process 
exited, code=exited, status=1/FAILURE
  Sep 20 06:53:54 fridge systemd[1]: Failed to start Reboot.
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Unit entered 
failed state.
  Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Failed with 
result 'exit-code'.

  (Don't ask me why it took 20 minutes to get to this point.  Most
  everything was already shut down by 06:35.)

  After this the journal shows a few other random-looking service
  messages

  Sep 20 07:13:44 fridge systemd[1]: Stopping LVM2 metadata daemon...
  Sep 20 07:13:44 fridge systemd[1]: Stopped LVM2 metadata daemon.
  Sep 20 07:51:48 fridge systemd[1]: Started LVM2 metadata daemon.
  Sep 20 07:51:48 fridge systemd[1]: Stopped target Shutdown.

  and the end of a cron session that initiated the unattended-upgrade
  shutdown -r 06:30 call, presumably

  Sep 20 07:52:54 fridge CRON[1176]: pam_unix(cron:session): session
  closed for user root

  and then the machine sat idle waiting for keyboard input, which I
  provided in the form of Alt+SysRq+S,U,B a few hours later.

  
  This has never happened before on this server, which is running Ubuntu 16.04 
LTS since November 2016.  I haven't tried to reproduce this (yet).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 11:10:34 2017
 

[Touch-packages] [Bug 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.29-13ubuntu1

---
binutils (2.29-13ubuntu1) artful; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.29-13) unstable; urgency=medium

  * Build again all cross packages.

binutils (2.29-12) unstable; urgency=medium

  * Update, taken from the 2.29 branch 20170919.
- Fix PR ld/21441, PowerPC64 stubs don't match calculated size.
  Closes: #876134.
- Fix PR ld/22048, Incorrect .eh_frame section in libc.so.
- Fix PR ld/22150, ld keeps a version reference for gc'd symbols.
  Closes: #874585. LP: #1715641.
- Fix PR ld/22148, Integer overflow in elf64-x86-64.c.
- Fix PR ld/21924, Require GCC 5 or above for 3 x86 tests.
  * Fix installation of test summaries.
  * Compare test summaries for cross builds.

 -- Matthias Klose   Tue, 19 Sep 2017 13:09:15 +0200

** Changed in: binutils (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Fix Released
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in dpkg package in Debian:
  Fix Released

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1715641/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[cyba]

Same problem here, affects me on 4.4.0-93-generic. Dell E7450 with
docking station and 2 monitors, used to work flawlessly on 14.04.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Didier Roche]

** Tags added: rls-aa-incoming

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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