[Touch-packages] [Bug 1354560] [NEW] Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

Public bug reported:

After connecting to a hidden wifi network the indicator does not
correctly show the connection status. Instead of the connected icon in
the top bar there's just a blank space, the hidden network shows up in
the indicator's network list twice, and there's no check mark next to
either of the entries in the network list. The phone is associated with
the wireless network however and has a functioning network connection.

I'm attaching screenshots of the indicator when this is happening as
well as other data requested in bug #1202806.

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Assignee: Antti Kaijanmäki (kaijanmaki)
 Status: New

** Attachment added: indicator-1.png
   
https://bugs.launchpad.net/bugs/1354560/+attachment/4173009/+files/indicator-1.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: indicator-3.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173011/+files/indicator-3.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: menumodel.txt
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173014/+files/menumodel.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: nmcli_d_wifi_list.txt
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173015/+files/nmcli_d_wifi_list.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: indicator-2.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173010/+files/indicator-2.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: actiongroup.txt
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173013/+files/actiongroup.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the connected icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

[Seth Forshee]

Okay - bug #1354560.

Just one note though - bug #1333135 talks specifically about landscape
orientation, but I was using the phone in portrait orientation.

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1202806/+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 1393206] Re: SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic

[Seth Forshee]

It looks like apparmor isn't allowing the mount.

[ 7963.575900] audit: type=1400 audit(1416145652.685:70):
apparmor=DENIED operation=mount info=failed mntpnt match error=-13
profile=/usr/lib/lightdm/lightdm-guest-session
name=/run/user/127/gvfs/ pid=7101 comm=gvfsd-fuse fstype=fuse
.gvfsd-fuse srcname=gvfsd-fuse flags=rw, nosuid, nodev

I'm not sure which package is really to blame here, but I'm pretty sure
it isn't the kernel. I'm changing this to affect apparmor, as I'm
guessing someone there ought to know which package has actually caused
this to regress.

** Package changed: linux (Ubuntu) = apparmor (Ubuntu)

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

Title:
  SD/mmc card with exFAT fs not automatically mounted since upgrade to
  utopic

Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  Inserting a memory card formatted with exFAT in my built-in memory
  reader doesn't automatically mount the partition since I upgraded to
  utopic (from trusty). Before this it mounted the partition without any
  problems. I have installed exfat-fuse and exfat-utils as before.

  udisks2 detects the partition correctly but gvfs ignores it:
  17:00:48.133: Added /org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95
org.freedesktop.UDisks2.Drive:
  CanPowerOff:false
  Configuration:  {}
  ConnectionBus:  sdio
  Ejectable:  false
  Id: SU64G-0xa21a0d95
  Media:  flash_sd
  MediaAvailable: true
  MediaChangeDetected:true
  MediaCompatibility: flash_sd
  MediaRemovable: true
  Model:  SU64G
  Optical:false
  OpticalBlank:   false
  OpticalNumAudioTracks:  0
  OpticalNumDataTracks:   0
  OpticalNumSessions: 0
  OpticalNumTracks:   0
  Removable:  true
  Revision:   
  RotationRate:   0
  Seat:   seat0
  Serial: 0xa21a0d95
  SiblingId:  
  Size:   63864569856
  SortKey:01hotplug/1416153648130773
  TimeDetected:   1416153648130773
  TimeMediaDetected:  1416153648130773
  Vendor: 
  WWN:
  17:00:48.134: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
  Configuration:  []
  CryptoBackingDevice:'/'
  Device: /dev/mmcblk0
  DeviceNumber:   45824
  Drive:  
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
  HintAuto:   true
  HintIconName:   
  HintIgnore: false
  HintName:   
  HintPartitionable:  true
  HintSymbolicIconName:   
  HintSystem: false
  Id: 
  IdLabel:
  IdType: 
  IdUUID: 
  IdUsage:
  IdVersion:  
  MDRaid: '/'
  MDRaidMember:   '/'
  PreferredDevice:/dev/mmcblk0
  ReadOnly:   false
  Size:   63864569856
  Symlinks:   /dev/disk/by-id/mmc-SU64G_0xa21a0d95
org.freedesktop.UDisks2.PartitionTable:
  Type:   dos
  17:00:48.183: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
  Configuration:  []
  CryptoBackingDevice:'/'
  Device: /dev/mmcblk0p1
  DeviceNumber:   45825
  Drive:  
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
  HintAuto:   true
  HintIconName:   
  HintIgnore: false
  HintName:   
  HintPartitionable:  true
  HintSymbolicIconName:   
  HintSystem: false
  Id: 
  IdLabel:
  IdType: 
  IdUUID: 
  IdUsage:
  IdVersion:  
  MDRaid: '/'
  MDRaidMember:   '/'
  PreferredDevice:/dev/mmcblk0p1
  ReadOnly:   false
  Size:   63863521280
  Symlinks:   /dev/disk/by-id/mmc-SU64G_0xa21a0d95-part1
org.freedesktop.UDisks2.Partition:
  Flags:  0
  IsContained:false
  

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

[Seth Forshee]

** Changed in: linux (Ubuntu)
   Status: Incomplete = In Progress

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

Title:
  kernel fails to load iwlwifi firmware - disable
  CONFIG_FW_LOADER_USER_HELPER

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in openSUSE:
  Fix Released

Bug description:
  Using current vivid, when using udev 217 wlan0 is missing, it's there
  and working fine when downgrading to 215

  Right after boot, kernel shows

  [ 6.586593] iwlwifi :02:00.0: Direct firmware load failed with error -2
  [ 6.586598] iwlwifi :02:00.0: Falling back to user helper

  After manually enabling the card, kernel shows

  Dec  2 11:37:08 localhost kernel: [  127.133185] iwlwifi :02:00.0:
  loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 80-net-name-slot.rules 81-canonij_prn.rules
  Date: Tue Dec  2 17:39:08 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-09 (1515 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=555ebc11-d747-44d3-af56-5e7d17851ce3 ro quiet splash 
init=/bin/systemd vt.handoff=7
  SourcePackage: systemd
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0HNGW4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/21/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0HNGW4:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398458/+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 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

[Seth Forshee]

I used https://github.com/mcgrof/fake-firmware-test to confirm that
disabling CONFIG_FW_LOADER_USER_HELPER eliminates use of the user helper
and the associated delay when the firmware is missing. Patch has been
sent to the kernel team mailing list.

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

Title:
  kernel fails to load iwlwifi firmware - disable
  CONFIG_FW_LOADER_USER_HELPER

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in openSUSE:
  Fix Released

Bug description:
  Using current vivid, when using udev 217 wlan0 is missing, it's there
  and working fine when downgrading to 215

  Right after boot, kernel shows

  [ 6.586593] iwlwifi :02:00.0: Direct firmware load failed with error -2
  [ 6.586598] iwlwifi :02:00.0: Falling back to user helper

  After manually enabling the card, kernel shows

  Dec  2 11:37:08 localhost kernel: [  127.133185] iwlwifi :02:00.0:
  loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 80-net-name-slot.rules 81-canonij_prn.rules
  Date: Tue Dec  2 17:39:08 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-09 (1515 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=555ebc11-d747-44d3-af56-5e7d17851ce3 ro quiet splash 
init=/bin/systemd vt.handoff=7
  SourcePackage: systemd
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0HNGW4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/21/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0HNGW4:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398458/+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 1337239] Re: Digitiser still works when phone locked

[Seth Forshee]

This isn't really a problem with powerd. As far as I know there's no
standard interface (and likely as not no interface at all) for telling
an input driver to stop sending events other than closing the input
device, and powerd can't close the device on behalf of another process.
The input stack needs to close the input device (preferably, or else
stop listening to events from the touchscreen input device) whenever the
screen is off.

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

Title:
  Digitiser still works when phone locked

Status in Music application for Ubuntu devices:
  Invalid
Status in PowerD:
  Confirmed
Status in “powerd” package in Ubuntu:
  Confirmed

Bug description:
  Boot Ubuntu on a Nexus 4
  Open music app
  Start playing songs
  Tap the power button to lock the screen
  Swipe in from left or top edge
  Tap the power button to unlock the screen
  Observe the launcher (left) or indicator (top) have opened, while the screen 
was 'locked'

  Reproduced this on #106 and #111, only happens if you launch music
  first and play music it seems. Launching music and _not_ playing a
  song isn't sufficient to trigger this.

  Here's a video showing it. https://www.youtube.com/watch?v=0Y_JoVfzDmA

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1337239/+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 1359530] Re: Device trying to suspend when screen is turned off by proximity sensor (during a call)

[Seth Forshee]

Why isn't it valid for the system CPU to suspend during a phone call?
Does android enforce such a restriction?

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

Title:
  Device trying to suspend when screen is turned off by proximity sensor
  (during a call)

Status in PowerD:
  In Progress
Status in Unity System Compositor:
  Invalid
Status in “powerd” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 202
  device name: krillin
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-08-21 03:59:43
  version version: 202
  version ubuntu: 20140821
  version device: 20140811.1

  Device tries to suspend when the screen is turned off by the proximity
  sensor (when a voicecall is in place).

  Looking at powerd, there's no active suspend blocker when the
  proximity sensor disables the screen, forcing powerd to go in suspend
  state.

  The device shouldn't try to suspend when a voicecall is active (or
  when the proximity sensor is the one turning the screen off).

  When the call starts:
  powerd-cli: Running as user is not fully supported.
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.18, State: 1

  After putting my hand on top of the device (to trigger the proximity sensor):
  phablet@ubuntu-phablet:~$ powerd-cli list
  powerd-cli: Running as user is not fully supported.
  System State Requests:
    None

To manage notifications about this bug go to:
https://bugs.launchpad.net/powerd/+bug/1359530/+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 1355441] Re: Wifi dropping

[Seth Forshee]

It looks like the disconnections are initiated by NetworkManager, which
gives the reason 'ip-config-unavailable'. Maybe some kind of dhcp
problem, I'm not sure. Right now it isn't looking like a driver problem
but something higher in the stack, so I'm updating the bug to affect
network manager so that someone more familiar with that level of the
network stack can take a look.

** Package changed: linux (Ubuntu) = network-manager (Ubuntu)

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

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

Title:
  Wifi dropping

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Environment

  Lenovo T440s
  Ubuntu 14.04
  Kernel: 3.13.0-32-generic #57-Ubuntu SMP  x86_64
  Firmware version: Aug 11 14:17:58 dave kernel: [3.336421] iwlwifi 
:03:00.0: loaded firmware version 22.1.7.0 op_mode iwlmvm
  # I have also tried version 22.1.8.0
  sudo lshw -C network
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan0
 version: 83
 serial: e8:2a:ea:b3:5a:1f
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=3.13.0-32-generic firmware=22.1.7.0 ip=192.168.1.121 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
 resources: irq:61 memory:f040-f0401fff
  sudo iwconfig:
wlan0 IEEE 802.11abgn  ESSID:nfu2  
Mode:Managed  Frequency:2.437 GHz  Access Point: 68:7F:74:A2:56:27  
 
Bit Rate=54 Mb/s   Tx-Power=16 dBm   
Retry  long limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70  Signal level=-22 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:119   Missed beacon:0
  grep wifi /var/log/syslog:
Aug 11 14:17:58 dave kernel: [3.336421] iwlwifi :03:00.0: loaded 
firmware version 22.1.7.0 op_mode iwlmvm
(30x of these:) Aug 11 16:52:15 dave kernel: [ 9256.926634] iwlwifi 
:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dave   1907 F pulseaudio
   /dev/snd/controlC0:  dave   1907 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug 11 16:46:39 2014
  HibernationDevice: RESUME=UUID=b447ca85-41cc-44f1-b4b4-8a44bf215053
  InstallationDate: Installed on 2014-07-21 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20AQCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=a5f87e7d-a068-4cf1-94c5-0a4d068328f4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1355441/+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 1337753] Re: [mako] can not create an ad-hoc network

[Seth Forshee]

As far as the errors from the driver goes, the first one I see is could
not activate Heartbeat timer (not sure yet what the heartbeat timer
does, perhaps expiring peer STAs in the IBSS network when beacons aren't
seen for some period). This is printed using some internal logging
functions and has the log level LOGP, and any message of this log level
will trigger the stack trace.

There's a few ways for enabling the heartbeat timer to fail. The first
is that some ACTIVEMODE_OFFLOAD feature is enabled, the second is that
the timer hasn't been initialized, and the third is that the actual
timer activation fails for any of a variety of reasons. There's no clues
in the log about why it failed.

However it's also not apparent whether or not failing to activate the
heartbeat timer is fatal. The driver just logs the error and continues
on. Without digging deeper into the driver I can't tell whether it's the
cause for IBSS not working; it could just be a symptom of a larger
hardware misconfiguration or even unrelated to the other observed
issues.

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

Title:
  [mako] can not create an ad-hoc network

Status in “linux-mako” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “wpa” package in Ubuntu:
  Incomplete

Bug description:
  When trying to create an adhoc network using network-manager with mako
  kernel Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri
  Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux the creation
  fails with:

  NetworkManager[1347]: info Activation (wlan0) starting connection 'Ubuntu 
hotspot'
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-SCAN-STARTED 
  kernel: [ 1202.120128] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid 00:1e:ab:04:92:77 chan= 1, rssi = -83, countryCode TW
  kernel: [ 1202.120341] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid c8:60:00:dc:42:90 chan= 8, rssi = -66, countryCode GB
  kernel: [ 1202.120616] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2928: Information about current country Bssid c8:60:00:dc:42:90 chan= 8, rssi = 
-66, countryCode GB
  wpa_supplicant[1735]: wlan0: Trying to associate with SSID 'Ubuntu hotspot'
  NetworkManager[1347]: info (wlan0): supplicant interface state: 
disconnected - associating
  kernel: [ 1202.989958] wlan: [1352:E :PE ] limMlmAddBss: 1672: TRYING TO HIDE 
SSID 0
  kernel: [ 1202.990477] wlan: [1352:E :PE ] mlm_add_sta: 1573: GF: 0, 
ChnlWidth: 0, MimoPS: 0, lsigTXOP: 0, dsssCCK: 0, SGI20: 0, SGI400
  kernel: [ 1203.007416] wlan: [1352:F :PE ] limProcessIbssMlmAddBssRsp: 2524: 
could not activate Heartbeat timer
  kernel: [ 1203.008087] VOS ASSERT in logDebug Line 219
  kernel: [ 1203.008759] [ cut here ]
  kernel: [ 1203.008850] WARNING: at 
/build/buildd/linux-mako-3.4.0/drivers/staging/prima/CORE/SYS/legacy/src/utils/src/logApi.c:219
 logDebug+0xc0/0xf4()
  kernel: [ 1203.008881] Modules linked in:
  kernel: [ 1203.008972] [c00150d0] (unwind_backtrace+0x0/0xe8) from 
[c08cbf68] (dump_stack+0x20/0x24)
  kernel: [ 1203.009033] [c08cbf68] (dump_stack+0x20/0x24) from [c0075628] 
(warn_slowpath_common+0x5c/0x74)
  kernel: [ 1203.009094] [c0075628] (warn_slowpath_common+0x5c/0x74) from 
[c00756fc] (warn_slowpath_null+0x2c/0x34)
  kernel: [ 1203.009186] [c00756fc] (warn_slowpath_null+0x2c/0x34) from 
[c069aad4] (logDebug+0xc0/0xf4)
  kernel: [ 1203.009247] [c069aad4] (logDebug+0xc0/0xf4) from [c05e06cc] 
(limLog+0x48/0x50)
  kernel: [ 1203.009339] [c05e06cc] (limLog+0x48/0x50) from [c05fdce8] 
(limProcessMlmAddBssRsp+0x168/0xd40)
  kernel: [ 1203.009400] [c05fdce8] (limProcessMlmAddBssRsp+0x168/0xd40) from 
[c05f5010] (limProcessMessages+0xe74/0x10ac)
  kernel: [ 1203.009491] [c05f5010] (limProcessMessages+0xe74/0x10ac) from 
[c05f5560] (limMessageProcessor+0x274/0x2bc)
  kernel: [ 1203.009552] [c05f5560] (limMessageProcessor+0x274/0x2bc) from 
[c05db1a8] (peProcessMessages+0x54/0x5c)
  kernel: [ 1203.009613] [c05db1a8] (peProcessMessages+0x54/0x5c) from 
[c06ba540] (VosMCThread+0x44c/0x68c)
  kernel: [ 1203.009705] [c06ba540] (VosMCThread+0x44c/0x68c) from 
[c0095954] (kthread+0x9c/0xa8)
  kernel: [ 1203.009766] [c0095954] (kthread+0x9c/0xa8) from [c000ee74] 
(kernel_thread_exit+0x0/0x8)
  kernel: [ 1203.009827] ---[ end trace 4821fc77d3719675 ]---
  NetworkManager[1347]: warn Activation (wlan0/wireless): Ad-Hoc network 
creation took too long, failing activation.
  NetworkManager[1347]: info (wlan0): device state change: config - failed 
(reason 'supplicant-timeout') [50 120 11]
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 
reason=3 locally_generated=1

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

-- 

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

[Seth Forshee]

I don't think it makes sense to change this in the 3.16 kernel, which is
currently what's being used in vivid. On the surface it makes sense to
disable CONFIG_FW_LOADER_USER_HELPER in the 3.18 branch, except that
ultimately the vivid kernel will also be released for trusty. In theory
things should still just work, but potentially there are some corner
cases which still rely on the fallback.

In the end I guess we probably ought to change it though.

** Changed in: linux (Ubuntu)
   Status: Triaged = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Seth Forshee (sforshee)

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

Title:
  kernel fails to load iwlwifi firmware - disable
  CONFIG_FW_LOADER_USER_HELPER

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in openSUSE:
  Fix Released

Bug description:
  Using current vivid, when using udev 217 wlan0 is missing, it's there
  and working fine when downgrading to 215

  Right after boot, kernel shows

  [ 6.586593] iwlwifi :02:00.0: Direct firmware load failed with error -2
  [ 6.586598] iwlwifi :02:00.0: Falling back to user helper

  After manually enabling the card, kernel shows

  Dec  2 11:37:08 localhost kernel: [  127.133185] iwlwifi :02:00.0:
  loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 80-net-name-slot.rules 81-canonij_prn.rules
  Date: Tue Dec  2 17:39:08 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-09 (1515 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=555ebc11-d747-44d3-af56-5e7d17851ce3 ro quiet splash 
init=/bin/systemd vt.handoff=7
  SourcePackage: systemd
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0HNGW4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/21/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0HNGW4:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398458/+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 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

[Seth Forshee]

It looks like I don't have any of the affected hardware. I put up a test
build at the link below; Sebastien, could you give it a try (with the
workaround removed obviously) and confirm that it fixes the problem?

http://people.canonical.com/~sforshee/lp1398458/linux-3.18.0-5.6+lp1398458v201412031026/

** Changed in: linux (Ubuntu)
   Status: In Progress = Incomplete

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

Title:
  kernel fails to load iwlwifi firmware - disable
  CONFIG_FW_LOADER_USER_HELPER

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in openSUSE:
  Fix Released

Bug description:
  Using current vivid, when using udev 217 wlan0 is missing, it's there
  and working fine when downgrading to 215

  Right after boot, kernel shows

  [ 6.586593] iwlwifi :02:00.0: Direct firmware load failed with error -2
  [ 6.586598] iwlwifi :02:00.0: Falling back to user helper

  After manually enabling the card, kernel shows

  Dec  2 11:37:08 localhost kernel: [  127.133185] iwlwifi :02:00.0:
  loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 80-net-name-slot.rules 81-canonij_prn.rules
  Date: Tue Dec  2 17:39:08 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-09 (1515 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=555ebc11-d747-44d3-af56-5e7d17851ce3 ro quiet splash 
init=/bin/systemd vt.handoff=7
  SourcePackage: systemd
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0HNGW4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/21/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0HNGW4:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398458/+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 1450017] Re: Sometimes resuming leaves only a black lit screen, no unity8

[Seth Forshee]

The powerd main thread only ever checks fb_state with the mutex locked,
and the monitor thread only ever changes it with the mutex locked. The
main thread also only calls pthread_cond_wait() *after* finding fb_state
!= FB_AWAKE *without any intervening unlock of the mutex.* So the
scenario you describe is impossible. If the monitor thread changes
fb_state to FB_AWAKE before the main thread locks the mutex, it will see
fb_state == FB_AWAKE on the first loop iteration and never call
pthread_cond_wait(). If the main thread locks the mutex before the
monitor thread changes the state then the monitor thread cannot change
the state until pthread_cond_wait() releases the mutex, then the
subsequent pthread_cond_signal() call will awaken the main thread.

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

Title:
  Sometimes resuming leaves only a black lit screen, no unity8

Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when I turn my dogfooding mako device on (running stable
  channel), I see a back lighted screen, but no unity8.  It stays like
  that indefinitely, and I just have to hard-reset.

  I haven't noticed any obvious correlations to the behavior.  It just
  happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1450017/+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 1421455] Re: Slow wake up time on physical power button pressed

[Seth Forshee]

Yeah it seems likely that some driver is probably being slow in its
late_resume handler. There may be something in dmesg which shows how
long individual late_resume calls are making, I can't remember (there
may also be some debug option which has to be enabled).

Iirc the reason we have to wait for the fb state to change was because
you can hit deadlocks with some of the phone kernels if you write state
changes to /sys/power/state without waiting. Android also waits for the
framebuffer state to change, so that's the only arrangement that's
probably tested by the phone makers as well.

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

Title:
  Slow wake up time on physical power button pressed

Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Device: bq Aquaris E4.5 running: Stable #17

  When pressing on physical power button on device to wake it up
  sometime it even takes up to 2-3 secs before anything appears on the
  screen. This time wary but its hard to tell then its shorter and when
  is longer.

  This is not so bad on nexus4.

  
  Should you need more info, I'm happy to help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1421455/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

[Seth Forshee]

In addition to the requested logs could someone provide steps to
reproduce, preferably in a VM without MAAS?

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

Title:
  installing or upgrading libc6 in Trusty removes all content from /tmp
  directory

Status in eglibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We are seeing an issue with installation of dkms package during a
  curtin installation which ends up with /tmp directory being wiped
  clean. This is very bad for curtin as it saves critical installation
  files in /tmp.

  It turns out that it's the of upgrading libc6, which is triggered as a
  result of installing dependencies, that removes content of /tmp. For
  example, installation of gcc results in the same result since it ends
  up with libc6 being upgraded. The only way that this won't be
  recreated is if the latest libc6 is already installed.

  This problem does not exist in precise. It can also be recreated by
  installing the .deb file for any version in trusty including 2.17.

  
  ubuntu@host:~$ ls /tmp
  tmpHHbRkP
  ubuntu@sirrush:~$ sudo apt-get install libc6
  sudo: unable to resolve host sirrush
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    libc-dev-bin libc6-dev
  Suggested packages:
    glibc-doc
  Recommended packages:
    manpages-dev
  The following packages will be upgraded:
    libc-dev-bin libc6 libc6-dev
  3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
  Need to get 6,714 kB of archives.
  After this operation, 6,144 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 
2.19-0ubuntu6.6 [1,910 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin 
amd64 2.19-0ubuntu6.6 [68.9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 
2.19-0ubuntu6.6 [4,735 kB]
  Fetched 6,714 kB in 0s (18.5 MB/s)
  Preconfiguring packages ...
  (Reading database ... 57798 files and directories currently installed.)
  Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
  Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
  Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  ubuntu@host:~$ ls /tmp
  ubuntu@host:~$
  

  This is very recreatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

[Seth Forshee]

I've also reproduced it in a VM using Stefan's method. Both Stefan and I
have verified that stubbing out or removing /etc/init/mounted-tmp.conf
eliminates the problem, so it seems that this job is getting triggered
somehow.

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

Title:
  installing or upgrading libc6 in Trusty removes all content from /tmp
  directory

Status in eglibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We are seeing an issue with installation of dkms package during a
  curtin installation which ends up with /tmp directory being wiped
  clean. This is very bad for curtin as it saves critical installation
  files in /tmp.

  It turns out that it's the of upgrading libc6, which is triggered as a
  result of installing dependencies, that removes content of /tmp. For
  example, installation of gcc results in the same result since it ends
  up with libc6 being upgraded. The only way that this won't be
  recreated is if the latest libc6 is already installed.

  This problem does not exist in precise. It can also be recreated by
  installing the .deb file for any version in trusty including 2.17.

  
  ubuntu@host:~$ ls /tmp
  tmpHHbRkP
  ubuntu@sirrush:~$ sudo apt-get install libc6
  sudo: unable to resolve host sirrush
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    libc-dev-bin libc6-dev
  Suggested packages:
    glibc-doc
  Recommended packages:
    manpages-dev
  The following packages will be upgraded:
    libc-dev-bin libc6 libc6-dev
  3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
  Need to get 6,714 kB of archives.
  After this operation, 6,144 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 
2.19-0ubuntu6.6 [1,910 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin 
amd64 2.19-0ubuntu6.6 [68.9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 
2.19-0ubuntu6.6 [4,735 kB]
  Fetched 6,714 kB in 0s (18.5 MB/s)
  Preconfiguring packages ...
  (Reading database ... 57798 files and directories currently installed.)
  Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
  Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
  Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  ubuntu@host:~$ ls /tmp
  ubuntu@host:~$
  

  This is very recreatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

[Seth Forshee]

Also I forgot to mention that Chris Arges pointed out that there's a
eglibc postinst script which does a re-exec of upstart, which is an
important piece of the puzzle.

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

Title:
  installing or upgrading libc6 in Trusty removes all content from /tmp
  directory

Status in eglibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We are seeing an issue with installation of dkms package during a
  curtin installation which ends up with /tmp directory being wiped
  clean. This is very bad for curtin as it saves critical installation
  files in /tmp.

  It turns out that it's the of upgrading libc6, which is triggered as a
  result of installing dependencies, that removes content of /tmp. For
  example, installation of gcc results in the same result since it ends
  up with libc6 being upgraded. The only way that this won't be
  recreated is if the latest libc6 is already installed.

  This problem does not exist in precise. It can also be recreated by
  installing the .deb file for any version in trusty including 2.17.

  
  ubuntu@host:~$ ls /tmp
  tmpHHbRkP
  ubuntu@sirrush:~$ sudo apt-get install libc6
  sudo: unable to resolve host sirrush
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    libc-dev-bin libc6-dev
  Suggested packages:
    glibc-doc
  Recommended packages:
    manpages-dev
  The following packages will be upgraded:
    libc-dev-bin libc6 libc6-dev
  3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
  Need to get 6,714 kB of archives.
  After this operation, 6,144 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 
2.19-0ubuntu6.6 [1,910 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin 
amd64 2.19-0ubuntu6.6 [68.9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 
2.19-0ubuntu6.6 [4,735 kB]
  Fetched 6,714 kB in 0s (18.5 MB/s)
  Preconfiguring packages ...
  (Reading database ... 57798 files and directories currently installed.)
  Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
  Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
  Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  ubuntu@host:~$ ls /tmp
  ubuntu@host:~$
  

  This is very recreatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

[Seth Forshee]

http://paste.ubuntu.com/11768305/

That link shows upstart-monitor output during the libc6 upgrade. I see
the mountall job starting, then later I see a mounted event for /tmp
which triggers the mounted-tmp job, which is what ends up clearing out
/tmp. In fact, generally it looks to me like many of the startup jobs
are running, so I suspect upstart must be emitting a startup event.

Just glancing briefly at the upstart code, it seems to support a restart
flag to be passed on reexec which would prevent the startup event from
being emitted. The logic is a bit weird though - on re-exec upstart only
seems to pass --restart if the current upstart isn't a re-exec ... so if
you re-execed twice you don't want the flag?

Anyway, I think at this point I'll throw it back over to Steve, as I
don't see any evidence at all that this is a kernel issue.

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

Title:
  installing or upgrading libc6 in Trusty removes all content from /tmp
  directory

Status in eglibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We are seeing an issue with installation of dkms package during a
  curtin installation which ends up with /tmp directory being wiped
  clean. This is very bad for curtin as it saves critical installation
  files in /tmp.

  It turns out that it's the of upgrading libc6, which is triggered as a
  result of installing dependencies, that removes content of /tmp. For
  example, installation of gcc results in the same result since it ends
  up with libc6 being upgraded. The only way that this won't be
  recreated is if the latest libc6 is already installed.

  This problem does not exist in precise. It can also be recreated by
  installing the .deb file for any version in trusty including 2.17.

  
  ubuntu@host:~$ ls /tmp
  tmpHHbRkP
  ubuntu@sirrush:~$ sudo apt-get install libc6
  sudo: unable to resolve host sirrush
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    libc-dev-bin libc6-dev
  Suggested packages:
    glibc-doc
  Recommended packages:
    manpages-dev
  The following packages will be upgraded:
    libc-dev-bin libc6 libc6-dev
  3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
  Need to get 6,714 kB of archives.
  After this operation, 6,144 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 
2.19-0ubuntu6.6 [1,910 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin 
amd64 2.19-0ubuntu6.6 [68.9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 
2.19-0ubuntu6.6 [4,735 kB]
  Fetched 6,714 kB in 0s (18.5 MB/s)
  Preconfiguring packages ...
  (Reading database ... 57798 files and directories currently installed.)
  Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
  Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
  Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  ubuntu@host:~$ ls /tmp
  ubuntu@host:~$
  

  This is very recreatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+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 1485659] [NEW] Date/time indicator doesn't update after changing time zone

[Seth Forshee]

Public bug reported:

After changing the timezone the time displayed in the date/time
indicator is still in my old time zone. I sent a signal to the
indicator-datetime-service process, and after it restarted the correct
time was displayed.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 17 08:51:44 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-02-19 (178 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150110)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug wily

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

Title:
  Date/time indicator doesn't update after changing time zone

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After changing the timezone the time displayed in the date/time
  indicator is still in my old time zone. I sent a signal to the
  indicator-datetime-service process, and after it restarted the correct
  time was displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 17 08:51:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (178 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150110)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+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 1498162] Re: unable to make backup link of `./usr/sbin/uuidd' before installing new version: Operation not permitted

[Seth Forshee]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  unable to make backup link of `./usr/sbin/uuidd' before installing new
  version: Operation not permitted

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Upon trying to do an apt-get upgrade I run into this error:

  
  sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
uuid-runtime
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  Need to get 0 B/12.3 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 27622 files and directories currently installed.)
  Preparing to unpack .../uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb ...
  Unpacking uuid-runtime (2.20.1-5.1ubuntu20.7) over (2.20.1-5.1ubuntu20.6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb (--unpack):
   unable to make backup link of `./usr/sbin/uuidd' before installing new 
version: Operation not permitted
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.7
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Mon Sep 21 19:43:02 2015
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498162/+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 1498162] Re: unable to make backup link of `./usr/sbin/uuidd' before installing new version: Operation not permitted

[Seth Forshee]

I have a fix, but I will want to run it by upstream before we apply it
to be sure we aren't opening up any security issues. In the meantime
I've put up a test build, please give it a try and verify that the uuid-
runtime upgrade can be successfully installed.

http://people.canonical.com/~sforshee/lp1498162/

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

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

Title:
  unable to make backup link of `./usr/sbin/uuidd' before installing new
  version: Operation not permitted

Status in linux package in Ubuntu:
  Incomplete
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Upon trying to do an apt-get upgrade I run into this error:

  
  sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
uuid-runtime
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  Need to get 0 B/12.3 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 27622 files and directories currently installed.)
  Preparing to unpack .../uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb ...
  Unpacking uuid-runtime (2.20.1-5.1ubuntu20.7) over (2.20.1-5.1ubuntu20.6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb (--unpack):
   unable to make backup link of `./usr/sbin/uuidd' before installing new 
version: Operation not permitted
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.7
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Mon Sep 21 19:43:02 2015
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498162/+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 1506888] Re: wifi status not remembered after reboot

[Seth Forshee]

Losing the state when using the network indicator sounds like a network-
manager bug, so I'm going to change this to affecting that package. The
issue when using a key could be caused by network-manager, the kernel,
or your system firmware depending on how it's implemented for your
machine.

** Package changed: linux-firmware (Ubuntu) => network-manager (Ubuntu)

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

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

Title:
  wifi status not remembered after reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have HP ZBook 15 (1st generation, 2013) with ubuntu-MATE 64-bit;
  latest updates installed. I am presently using an ethernet cable
  network so I turn the wireless network off. After each new start or
  reboot of the machine the wifi radio gets always on and I always have
  to switch it off manually.

  The notebook uses an Intel Corporation Centrino Advanced-N 6235 (rev
  24) wireless adapter (I hope this is a hardware version, not a driver
  one).

  I think that the On status by default is not good for several reasons:
  - energy consumption is higher
  - security may be affected
  - more electromagnetic radiation in environment

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-firmware 1.149
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Oct 16 16:16:11 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-10-04 (11 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20151003)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1506888/+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 1530617] Re: FUSE in wily image with upstart installed causes chaos

[Seth Forshee]

I'm seeing a direct correlation here between the symptom and the kernel
emitting uevents. For example, in the host run:

 $ udevadm --monitor

And in another terminal in the host run:

 # losetup /dev/loop0 foo

This causes the symptoms even though it has no direct impact on the
container, but does generate a uevent. I've seen the same thing
consistently so far - any command I run which causes a uevent to be
generated also results in processes in the container being killed. You
can also observe that fuse mount command cause uevents to be generated.

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

Title:
  FUSE in wily image with upstart installed causes chaos

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  New

Bug description:
  Host:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.10
  DISTRIB_CODENAME=wily
  DISTRIB_DESCRIPTION="Ubuntu 15.10"

  lxc version: 1.1.4-0ubuntu1

  In a LXC container running Ubuntu 15.10, install upstart-sysv to
  replace systemd. Using FUSE then causes almost all processes in the
  container to be killed.

  The following steps reproduce the problem using sshfs:

  # create a wily container and attach to it
  sudo lxc-create -t download -n wily -- -d ubuntu -r wily -a amd64
  sudo lxc-start -n wily
  sudo lxc-attach -n wily

  # inside the container, install upstart-sysv and reboot
  apt-get update && apt-get -y install upstart-sysv
  reboot

  # on the host, reattach to the container
  sudo lxc-attach -n wily

  # back in the container, install ssh and sshfs
  apt-get -y install openssh-server sshfs

  # create an ssh key pair in /root/.ssh
  ssh-keygen

  # set up passwordless ssh
  mkdir ~ubuntu/.ssh
  cat /root/.ssh/id_rsa.pub >> ~ubuntu/.ssh/authorized_keys
  eval $(ssh-agent)
  ssh-add /root/.ssh/id_rsa

  # take a note of the running processes and their PIDs
  ps axjf

  # run sshfs
  mkdir /fuse
  sshfs ubuntu@localhost:/ /fuse

  # we are kicked out of the container
  # run ps again in the container
  sudo lxc-attach -n wily -- ps axjf

  # a whole bunch of processes are now gone. the getty processes now
  have new PIDs, indicating they have been restarted.

  
  Other debugging performed:
  - On a 14.10 host with lxc version 1.1.0~alpha2-0ubuntu3.3, the problem does 
not occur. FUSE works fine.
  - On the same 14.10 host with lxc upgraded to 1.1.5-0ubuntu3~ubuntu14.04.1, 
the problem occurs.
  - On a 15.10 host, when running a wily container without upstart, the problem 
does not occur.
  - On a 15.10 host, when running a trusty container, the problem does not 
occur.
  - The problem can't be reproduced outside a container (15.10 host, install 
upstart-sysv, then use FUSE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530617/+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 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Seth Forshee]

@Amr: We cannot add this firmware to Ubuntu without a license from
Broadcom which allows redistribution. As far as I can see the sources
posted so far do not include such a license. Do you know of any sources
which do?

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

[Seth Forshee]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+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 1600124] Re: Adjust KBL PCI-ID's

[Seth Forshee]

Verified that i915_bpo.ko in 4.4.0-34.53 reflects the PCI id changes
from the patches.

** 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 libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1600124

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

** Attachment added: "Output of 'udevadm info --export-db'"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4743665/+files/udev-db.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] [NEW] udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

Public bug reported:

Since upgrading this machine to yakkety I've seen periodic hangs during
booting. If I wait long enough systemd give up and drops to maintenance
mode. Looking in the journal I see events like this:

Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-by
\x2duuid-63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start
timed out.

Searching on the internet indicates that this happen if devices reported
by udev don't have the "systemd" tag, and I find that they do not have
the tag when the boot times out but they do have the tag when boot does
not time out.

This happens once for every 3 or 4 boots and with both 4.4 and 4.8
kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm info
--export-db' from a timed-out boot.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: udev 231-6
ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
Uname: Linux 4.8.0-11-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 19 09:27:08 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-02-19 (577 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
dmi.bios.date: 05/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "Output of 'journalctl -xb'"
   
https://bugs.launchpad.net/bugs/1625217/+attachment/4743654/+files/journal.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

** Attachment added: "Output of 'udevadm info --export-db' from a good boot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751947/+files/udev-db.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

** Attachment added: "Output of 'udevadm info --export-db' from a failed boot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751945/+files/udev-db.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

** Attachment added: "Output of 'journalctl -xb' from a failed boot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751944/+files/journal.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

This is still happening, and it feels like a race. I've enabled debug
logging and captured the journal from good and bad boots. Comparing them
hasn't told me a whole lot; on the whole the udev debug logging isn't
very applicable. I do see that in both cases udev starts up and reads
the exact same set of rule files, and the statistics it prints about the
rule files are identical. Both have read in
/lib/udev/rules.d/99-systemd.rules which contains the rule for adding
the systemd tag. Nothing else has really stood out yet, but they are
pretty difficult to compare.

I also find that if I run 'udevadm trigger -c add
/sys/devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sda'
from recovery mode that udev does add the systemd tag at that point.

I'll attach my logs and udev databases from the good and bad boots.

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

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1625217] Re: udev sometimes doesn't apply systemd tag to devices

[Seth Forshee]

** Attachment added: "Output of 'journalctl -xb' from a good boot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751946/+files/journal.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/1625217

Title:
  udev sometimes doesn't apply systemd tag to devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading this machine to yakkety I've seen periodic hangs
  during booting. If I wait long enough systemd give up and drops to
  maintenance mode. Looking in the journal I see events like this:

  Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-
  by\x2duuid-
  63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed
  out.

  Searching on the internet indicates that this happen if devices
  reported by udev don't have the "systemd" tag, and I find that they do
  not have the tag when the boot times out but they do have the tag when
  boot does not time out.

  This happens once for every 3 or 4 boots and with both 4.4 and 4.8
  kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm
  info --export-db' from a timed-out boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-6
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 19 09:27:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (577 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+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 1611078] Re: Support snaps inside of lxd containers

[Seth Forshee]

Based on feedback from @jjohansen there will be follow-up patches to fix
the problems, but the patches already applied should be kept and do not
need to be reverted.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1611078] Re: Support snaps inside of lxd containers

[Seth Forshee]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

[Seth Forshee]

It does seem to be something in zesty. Not in the kernel though, I tried
xenial and yakkety kernels with zesty userspace and still got the hang.
But when I use a zesty kernel with yakkety userspace I don't see it.

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+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 1677377] [NEW] ADT failure in boot-smoke test with linux-hwe-edge

[Seth Forshee]

Public bug reported:

ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz

checking that there are no running jobs
FAIL: expected: '' actual: '663 lightdm.service start running'

Possibly an issue with lightdm or the kernel, I haven't been able to
determine the actual cause from the logs. I also haven't been able to
reproduce this failure locally.

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

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

Title:
  ADT failure in boot-smoke test with linux-hwe-edge

Status in systemd package in Ubuntu:
  New

Bug description:
  ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz

  checking that there are no running jobs
  FAIL: expected: '' actual: '663 lightdm.service start running'

  Possibly an issue with lightdm or the kernel, I haven't been able to
  determine the actual cause from the logs. I also haven't been able to
  reproduce this failure locally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1677377/+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 1674679] [NEW] lxc autopkgtest fails if http_proxy not set

[Seth Forshee]

Public bug reported:

debian/tests/exercise fails if http_proxy is not set, e.g.:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz

Since the script uses 'set -e' the expression 'if [ -n "${http_proxy}"
]' causes the script to terminate when http_proxy isn't set.

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

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

Title:
  lxc autopkgtest fails if http_proxy not set

Status in lxc package in Ubuntu:
  New

Bug description:
  debian/tests/exercise fails if http_proxy is not set, e.g.:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz

  Since the script uses 'set -e' the expression 'if [ -n "${http_proxy}"
  ]' causes the script to terminate when http_proxy isn't set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1674679/+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 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

[Seth Forshee]

The cause seems to be that TEST-12-ISSUE-3171 is hanging. I've
reproduced the problem with the 4.10.0-11 and 4.10.0-13 kernels and with
systemd 232-18ubuntu1 and 232-19. I'm attaching the journal from one of
the test runs, taken from within the nspawn container while the test was
hung (using linux 4.10.0-13 and systemd 232-19).

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+attachment/4837758/+files/journal.txt

** Description changed:

  Testing failed on:
-   amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
-   i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
-   ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz
+   amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
+   i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
+   ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz
  
  Upstream tests time out. Last thing displayed in the logs before the
- timeout is the login prompt from a VM.
+ timeout is the login prompt from a container running one of the tests.

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+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 1679598] Re: TEST-03-JOBS faliing in ADT

[Seth Forshee]

Here's an example with the test passing for the same kernel/systemd
versions as fail later (4.10.0-15/232-19):

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/s/systemd/20170328_002748_44e26@/log.gz

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

Title:
  TEST-03-JOBS faliing in ADT

Status in systemd package in Ubuntu:
  New

Bug description:
  In recent ADT runs TEST-03-JOBS has started failing with various
  systemd versions. Here's one with 232-19:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/s/systemd/20170403_174708_e037b@/log.gz

  and another with 232-21ubuntu2:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/s/systemd/20170330_184645_3ab85@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679598/+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 1679764] Re: systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

[Seth Forshee]

Note that the "error: org.freedesktop.systemd1.NoSuchUnit: Unit
c.service not found." is reported in bug #1672499.

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

Title:
  systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679764/+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 1679764] Re: systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

[Seth Forshee]

autopkgtest [17:28:29]: test boot-smoke: [---
reboot #0
bash: line 1: 32362 Killed  
/tmp/autopkgtest.eXsKq9/build.l7Q/systemd-232/debian/tests/boot-smoke 2> >(tee 
-a /tmp/autopkgtest.eXsKq9/boot-smoke-stderr >&2) > >(tee -a 
/tmp/autopkgtest.eXsKq9/boot-smoke-stdout)
autopkgtest [17:28:35]: test process requested reboot with marker 1
checking for failed unmounts for user systemd
checking for connection timeouts
checking that polkitd runs
219
checking that there are no running jobs
running jobs after remaining timeout -1:   2 dev-vda2.device start running
autopkgtest [17:29:33]: test boot-smoke: ---]

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

Title:
  systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679764/+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 1679764] [NEW] systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

[Seth Forshee]

Public bug reported:

Testing failed on:
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679764/+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 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

[Seth Forshee]

Confirmed that the test in the 232-21ubuntu3 source package no longer
hangs.

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

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
   * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
   * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).

  [Test Case]

   * ADT tests should pass on kvm architectures.

  [Regression Potential]

   * This is a testsuite fix for netcat-openbsd compat, does not affect
  systemd runtime binaries / libraries.

  [Other Info]
   
   * Original bug report.

  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+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 1671216] [NEW] ColdplugWifi test failures in ADT

[Seth Forshee]

Public bug reported:

We're seeing intermittent kernel ADT test failues against network-
manager due to the ColdplugWifi test timing out. This is happening
across multiple releases. Here's an example from xenial:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/i386/n/network-
manager/20170215_193017_bf4ec@/log.gz

and another from zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/i386/n/network-
manager/20170307_182040_787e9@/log.gz

In experimenting on zesty I've found that I can pretty easily recreate
the failures by running the ColdplugWifi test in a loop, usually within
10 iterations. I've also found that if I increase the timeout in the
test for reaching the activated state from 20 to 30 seconds I cannot
reproduce the error.

So it seems that perhaps the timeout on the test is too short and should
be increased.

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

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

Title:
  ColdplugWifi test failures in ADT

Status in network-manager package in Ubuntu:
  New

Bug description:
  We're seeing intermittent kernel ADT test failues against network-
  manager due to the ColdplugWifi test timing out. This is happening
  across multiple releases. Here's an example from xenial:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial/xenial/i386/n/network-
  manager/20170215_193017_bf4ec@/log.gz

  and another from zesty:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/i386/n/network-
  manager/20170307_182040_787e9@/log.gz

  In experimenting on zesty I've found that I can pretty easily recreate
  the failures by running the ColdplugWifi test in a loop, usually
  within 10 iterations. I've also found that if I increase the timeout
  in the test for reaching the activated state from 20 to 30 seconds I
  cannot reproduce the error.

  So it seems that perhaps the timeout on the test is too short and
  should be increased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671216/+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 1672499] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

[Seth Forshee]

Public bug reported:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

root-unittests fails:

-> Unit a.service:
Description: a.service
Instance: n/a
Unit Load State: not-found
Unit Active State: inactive
State Change Timestamp: n/a
Inactive Exit Timestamp: n/a
Active Enter Timestamp: n/a
Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit 
c.service not found.
Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
 Exit Timestamp: n/a

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

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on
  armhf

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

  root-unittests fails:

-> Unit a.service:
Description: a.service
Instance: n/a
Unit Load State: not-found
Unit Active State: inactive
State Change Timestamp: n/a
Inactive Exit Timestamp: n/a
Active Enter Timestamp: n/a
Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit 
c.service not found.
  Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
   Exit Timestamp: n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+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 1672542] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

[Seth Forshee]

Public bug reported:

Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

Upstream tests time out. Last thing displayed in the logs before the
timeout is the login prompt from a VM.

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

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

[Seth Forshee]

There are quite a few messages like these that lead me to believe where
running out of inotify watches.

Failed to acquire watch file descriptor: Too many open files
path-exists.path: Failed to enter waiting state: Too many open files

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

[Seth Forshee]

networkd-test.py FAIL non-zero exit status 1
root-unittests   FAIL non-zero exit status 1


networkd-test:

==
FAIL: test_catchall_config (__main__.UnmanagedClientTest)
Verify link states with a catch-all config, hot-plug.
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.0R9oTG/build.WC8/systemd-233/test/networkd-test.py", 
line 1009, in test_catchall_config
m0unm='managed')
  File "/tmp/autopkgtest.0R9oTG/build.WC8/systemd-233/test/networkd-test.py", 
line 145, in assert_link_states
(iface, expected, actual))
AssertionError: Link m1man expects state managed, found unmanaged


root-unittests:

== test-path ===
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
path-exists.service: state = dead; result = success 
FAIL: test-path (code: 1)
Test timeout when testing path-exists.path

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710654] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

[Seth Forshee]

Public bug reported:

Testing failed on:
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

[Seth Forshee]

I failed to follow up.

There were no failures when re-running the test, and no errors with
4.12.0-5.6, so marking this invalid.

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

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

Title:
  systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

Status in systemd package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

[Seth Forshee]

This patch fixes the tests for me. Turns out that we can't simply skip
writing to path_max as that seems to break the test case completely, so
I changed it to print an XFAIL message and abort the test.

** Patch added: "fix-longpath-test.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+attachment/4904113/+files/fix-longpath-test.patch

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1700211] Re: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Seth Forshee]

E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.

This seems to be related to an initramfs hook for casper, so marking
this bug as also affecting casper.

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

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

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

Bug description:
  Unable to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 09:21:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-19 (124 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1700211/+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 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

[Seth Forshee]

By the time BLKRRPART returns the partition device nodes should have
been created in devtmpfs, so there shouldn't be any need to wait for
things to settle. I'm not sure where a race could exist.

Yet it's odd that this failed only for ppc since all the code which
deals with this is generic, not platform-specific. It would be nice if
we had dmesg, unfortunately we do not.

I'm re-running the test just to see if it happens consistently. We have
a ppc test machine, however it's currently occupied running tests. Once
it's free I can do some testing there.

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

Title:
  systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+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 1700806] [NEW] systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

[Seth Forshee]

Public bug reported:

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+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 1684213] Re: Intel Wireless 7260 often crashes

[Seth Forshee]

Zesty already has the latest 7260 firmware (revision 459231), and
according to the attached CurrentDmesg.txt that's what being using:

[8.000329] iwlwifi :01:00.0: loaded firmware version 17.459231.0
op_mode iwlmvm

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+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 1707267] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

[Seth Forshee]

Public bug reported:

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707267/+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 1707267] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

[Seth Forshee]

autopkgtest [11:09:53]: test boot-smoke: [---
...
checking that there are no running jobs
running jobs after remaining timeout -1:
 61 apt-daily-upgrade.timerstart waiting
209 systemd-hostnamed.service  start running
 64 NetworkManager-wait-online.service start running
 59 timers.target  start waiting
 63 network-online.target  start waiting
 62 apt-daily.timerstart waiting
autopkgtest [11:10:53]: test boot-smoke: ---]
autopkgtest [11:10:53]: test boot-smoke:  - - - - - - - - - - results - - - - - 
- - - - -
boot-smoke   FAIL non-zero exit status 1

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707267/+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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

[Seth Forshee]

What if the test was changed to check writability of path_max? Just
changing the the check for the sysfs path to -w won't work for root, but
maybe something like this (perhaps there's a simpler way to do the check
though):

if [[ -f /sys/module/apparmor/parameters/path_max &&
  $(stat -c "%a" /sys/module/apparmor/parameters/path_max) == "600" ]] ; 
then
buf_max=2048#standard x86 page size/2
old_max=`cat /sys/module/apparmor/parameters/path_max`
echo $buf_max > /sys/module/apparmor/parameters/path_max
else
echo "WARNING: This version of AppArmor does not support changing 
buffer size."
fi

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

[Seth Forshee]

Something more like this then.

if [ ! -f /sys/module/apparmor/parameters/path_max ] ; then
echo "WARNING: This version of AppArmor does not support changing 
buffer size."
else
mode=$(stat -c "%a" /sys/module/apparmor/parameters/path_max)
if (( 8#$mode & 0222 )); then
buf_max=2048#standard x86 page size/2
old_max=`cat /sys/module/apparmor/parameters/path_max`
echo $buf_max > /sys/module/apparmor/parameters/path_max
else
echo "WARNING: This version of AppArmor does not support 
changing buffer size."
fi
fi

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

[Seth Forshee]

I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1691836/+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 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

[Seth Forshee]

I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.

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

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1691836/+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 1692543] [NEW] Regression tests cannot write to apparmor path_max module parameter in artful/4.11

[Seth Forshee]

Public bug reported:

The longpath regression tests tries to write to
/sys/module/apparmor/parameters/path_max, but this is read-only in
artful/4.11:

commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
Author: John Johansen 
Date:   Thu Apr 6 05:14:20 2017 -0700

apparmor: Make path_max parameter readonly

This is causing ADT to fail.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful-canonical-kernel-team-
ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

  running longpath
  longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
  Fatal Error (longpath): Unexpected shell error. Run with -x to debug

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

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1691836] [NEW] lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

[Seth Forshee]

Public bug reported:

Testing failed on:
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1691836/+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 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

[Seth Forshee]

---
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
Getting instance for '86e24950-3b10-11e7-8eab-fa163ee158b9'
Creating rootfs using 'download', arch=ppc64el
Traceback (most recent call last):
  File "/tmp/tmp.MzGrfkfdXM", line 72, in 
assert(container.defined)
AssertionError
---

Network issue? We see this problem somewhat frequently.

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1691836/+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 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

[Seth Forshee]

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

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Artful:
  New
Status in linux source package in Artful:
  Fix Released

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[Seth Forshee]

Public bug reported:

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

[Seth Forshee]

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

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

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

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

Status in lxc package in Ubuntu:
  New

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

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

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

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

[Seth Forshee]

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

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

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

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

Status in ppc64-diag package in Ubuntu:
  New

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

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

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

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

[Seth Forshee]

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

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

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

Status in ppc64-diag package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

[Seth Forshee]

armhf failure:

==
FAIL: test_search_domains_too_long (__main__.NetworkdClientTest)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.WNuNXs/build.mwP/systemd-234/test/networkd-test.py", 
line 855, in test_search_domains_too_long
self.assertRegex(contents, 'search .*{p}0 {p}1 {p}2'.format(p=name_prefix))
AssertionError: Regex didn't match: 'search 
.*0 
1 
2' not found in '# 
This file is managed by man:systemd-resolved(8). Do not edit.\n#\n# This is a 
dynamic resolv.conf file for connecting local clients directly to\n# all known 
DNS servers.\n#\n# Third party programs must not access this file directly, but 
only through the\n# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) 
in a different way,\n# replace this symlink by a static file or a different 
symlink.\n#\n# See man:systemd-resolved.service(8) for details about the 
supported modes of\n# operation for /etc/resolv.conf.\n\nnameserver 
10.0.4.1\nnameserver 192.168.42.1\nsearch lxd one two three four five\n# Too 
many search domains configured, remaining ones ignored.\n'

--

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

Title:
  systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+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 1712865] [NEW] systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

[Seth Forshee]

Public bug reported:

Testing failed on:
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+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 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

[Seth Forshee]

s390x failure:

autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt 
pinning. Retrying with using all packages from proposed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:s390x < 0 @iU mK Nb Ib >
Broken autopkgtest-satdep:s390x Depends on gdm3:s390x < none @un H >
  Removing autopkgtest-satdep:s390x because I can't find gdm3:s390x
...
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
autopkgtest [12:54:05]: ERROR: erroneous package: Test dependencies are 
unsatisfiable. A common reason is that your testbed is out of date with respect 
to the archive, and you need to use a current testbed or run apt-get update or 
use -U.

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

Title:
  systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+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 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

[Seth Forshee]

armhf passed after re-running, so I guess we can ignore it. Since the
s390x failure is fixed in -proposed I'll close the bug as invalid, I can
hint away the kernel test failure since it's clearly not a kernel issue.

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

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

Title:
  systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+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 1713075] [NEW] lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-6.7

[Seth Forshee]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170825_140357_85137@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170825_135445_85137@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170825_133209_85137@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170825_140357_85137@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170825_135445_85137@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170825_133209_85137@/log.gz

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

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

[Touch-packages] [Bug 1713726] [NEW] lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

[Seth Forshee]

Public bug reported:

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

Status in lxc package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

Seems that s390x ADT does now run in VMs, which explains the change.

Since we don't have wireless support in our s390x kernels, these
failures are expected. Seems the tests will need to be changed to skip
these tests or make them expected failures.

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

Tests were previously getting skipped for s390, due to "Restrictions:
... isolation-machine" in the test control file. Possibly some sort of
infrastructure problem detecting that the tests are running in a
container.

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1716009] Re: problem with the sound since the latest update

[Seth Forshee]

I'm not sure why this was reported against alsa-drivers, you didn't
report any alsa packages in those that were upgraded when the problem
started. To get the bug noticed it's helpful to report the bug against
the appropriate package. If you believe the issue is related to a linux-
firmware update then please report the bug against that package.
Changing the bug to affect linux-firmware.

Do you know what version of linux-firmware you were using before the
update which broke your audio?

Please capture dmesg on your machine and attach it to this bug; let me
know if you need instructions for how to do this. Thanks!

** Package changed: alsa-driver (Ubuntu) => linux-firmware (Ubuntu)

** Changed in: linux-firmware (Ubuntu)
   Status: New => Incomplete

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

Title:
  problem with the sound since the latest update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1716009/+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 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

** Description changed:

  Testing failed on:
- i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/s/systemd/20171120_141956_c23d7@/log.gz
+ s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

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

Title:
  systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/s/systemd/20171120_141956_c23d7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+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 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

amd64 also passed on retry. s390x failure is present with 4.13 kernel
too, so not a regression in 4.14.

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

Title:
  systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/s/systemd/20171120_141956_c23d7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+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 1733328] [NEW] systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

Public bug reported:

Testing failed on:
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+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 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

Oops, didn't mean to file this yet as tests haven't completed. However
there are failures already.

On s390x, the test history leads me to believe that the tests started
failing when we switch to running tests in VMs.

Traceback (most recent call last):
  File "/tmp/autopkgtest.EztoIW/build.0Oh/src/debian/tests/systemd-fsckd", line 
267, in 
boot_with_systemd_distro()
  File "/tmp/autopkgtest.EztoIW/build.0Oh/src/debian/tests/systemd-fsckd", line 
243, in boot_with_systemd_distro
enable_plymouth()
  File "/tmp/autopkgtest.EztoIW/build.0Oh/src/debian/tests/systemd-fsckd", line 
224, in enable_plymouth
plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

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

Title:
  systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+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 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

autopkgtest [13:37:31]: test wpa-dhclient: [---
modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.14.0-6-generic
ERROR

==
ERROR: setUpClass (__main__.T)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest.J2UcbH/build.Dbb/network-manager-1.8.4/debian/tests/network_test_base.py",
 line 47, in setUpClass
subprocess.check_call(['modprobe', 'cfg80211'])
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'cfg80211']' returned 
non-zero exit status 1.

--
Ran 0 tests in 0.002s

FAILED (errors=1)
autopkgtest [13:37:32]: test wpa-dhclient: ---]

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

This and other errors are related to lacking the cfg80211 module, which
we do not build for s390. However we did not build it in artful either,
and we currently have the same version of network-manager in artful and
bionic, so it's odd that the tests are failing in bionic and not in
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/1731283

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1731283] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

Public bug reported:

Testing failed on:
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

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

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

Title:
  systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/s/systemd/20171120_141956_c23d7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+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 1776670] [NEW] systemd 237-3ubuntu10 ADT test failure with linux 4.17.0-2.3

[Seth Forshee]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/i386/s/systemd/20180613_003420_38c07@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 237-3ubuntu10 ADT test failure with linux 4.17.0-2.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/i386/s/systemd/20180613_003420_38c07@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776670/+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 1776669] [NEW] network-manager 1.10.6-2ubuntu1 ADT test failure with linux 4.17.0-2.3

[Seth Forshee]

Public bug reported:

Testing failed on:
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/s390x/n/network-manager/20180613_112923_bf26d@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  network-manager 1.10.6-2ubuntu1 ADT test failure with linux 4.17.0-2.3

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/s390x/n/network-manager/20180613_112923_bf26d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1776669/+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 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present

[Seth Forshee]

This is not a problem with linux-firmware itself, it does is trigger a
rebuild of the initrd for all installed kernels but it's initramfs-tools
which does this. It will try to generate an initrd for all kernels with
a file in /var/lib/initramfs-tools, so it sounds like you have a file
there for that kernel but no corresponding directory for that kernel in
/lib/modules.

Changing this bug report to be against initramfs-tools.

** Package changed: linux-firmware (Ubuntu) => initramfs-tools (Ubuntu)

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

Title:
  linux-firmware 1.157.19 attempts to generate
  /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no
  corresponding vmlinuz present

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic,
  4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed,
  sudo dpkg-reconfigure linux-firmware returns the following to Console:

  update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
  update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56
  WARNING: missing /lib/modules/4.8.0-56
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file 
or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0
  WARNING: missing /lib/modules/4.8.0
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory
  update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic

  Same configuration report for "Setting up linux-firmware..." with sudo
  apt(-get) install (--reinstall) linux-firmware and sudo apt-get
  upgrade linux-firmware.  Therefore:

  Reproducible: Always
  Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo 
dpkg-reconfigure linux-firmware.
  Actual results, excepting actually installed Kernel Image packages:

  update-initramfs: Generating /boot/initrd.img-4.8.0-56
  WARNING: missing /lib/modules/4.8.0-56
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file 
or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0
  WARNING: missing /lib/modules/4.8.0
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory

  Expected results, excepting actually installed Kernel Image packages:

  No attempt to generate /boot/initrd.img for missing kernels, thus no
  warnings, errors or fatals.

  ---
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Dependencies:

  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-05-17 (373 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: linux-firmware 1.157.19 [origin: unknown]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17
  Tags: xenial third-party-packages
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip 

[Touch-packages] [Bug 1778551] [NEW] Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Public bug reported:

== SRU Justification ==

Impact: The 4.15 hwe kernel includes some package shuffling, so the
VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
to be updated to include linux-modules* packages.

Fix: Backport the conf file changes from bionic.

Test Case: Confirm that linux-modules* packages are autoremoved
according to the same rules used for linux-image* packages.

Regression Potential: Minimal. Probably the worst case is that some
packages that should be autoremoved are not, but since these changes
have been in use in bionic for a while now no regressions are expected.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+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 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Other than simply checking the patterns in the file, I can't think of an
easier way to test. If you know of one please let me know. I do
currently have a vm set up to let me test it.

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+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 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Hmm, now that I actually look at how the file is used, I guess we could
verify the list generated by /etc/kernel/postinst.d/apt-auto-removal,
couldn't we?

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+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 1768001] Re: En Thinkpad T430 con controlador BCM20702A0

[Seth Forshee]

I'm afraid that the firmware files just look to be pulled out of Windows
drivers downloaded from arbitrary download sites. I'd be hesitant to
stick those into our linux-firmware package in any case, and without a
license which allows us to redistribute the files we simply cannot
distribute them in Ubuntu.

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

Title:
  En Thinkpad T430 con controlador BCM20702A0

Status in bluez package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  loa dispositivos se intentan conectar y se conectan/desconectan
  continuamente. Se hace inutilizable el bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 13:26:49 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349I62
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b9f1f5f8-77c7-404e-92e8-a58f7bd5fa9e ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349I62
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349I62:pvrThinkPadT430:rvnLENOVO:rn2349I62:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349I62
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:E5:43:C5:85:87  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1196 acl:0 sco:0 events:88 errors:0
TX bytes:4095 acl:0 sco:0 commands:86 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1768001/+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 1727850] Re: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Seth Forshee]

>From journal.txt in the adt artifacts:


Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Main process exited, 
code=exited, status=1/FAILURE
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Unit entered failed 
state.
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Failed with result 
'exit-code'.

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

Title:
  systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727850/+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 1727850] [NEW] systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Seth Forshee]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

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


** Tags: kernel-adt-failure-hwe-edge-4.13

** Tags added: kernel-adt-failure

** Description changed:

  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/s/systemd/20171025_134325_0db62@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

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

Title:
  systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

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