from:"Dave"

Public bug reported:

STEPS:
1. Open multiple apps and pin them to the corners
2. Use the system

EXPECTED:
I expect the system to remain working like this all day

ACTUAL:
At some point unity8 crashes and takes out all of the apps and the system.

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

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

Title:
  Random crash with multiple apps open

Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Open multiple apps and pin them to the corners
  2. Use the system

  EXPECTED:
  I expect the system to remain working like this all day

  ACTUAL:
  At some point unity8 crashes and takes out all of the apps and the system.

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

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

[Touch-packages] [Bug 1672335] Re: Black screen on quartered apps with a 5th overlapping

** Attachment added: "layout of windows"

https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672335/+attachment/4836941/+files/screenshot20170310_150942094.png

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

Title:
Black screen on quartered apps with a 5th overlapping

Status in unity8 package in Ubuntu:
New

Bug description:
STEPS:
1. open the following 5 apps in the deb version of unity8:
mines
thunderbird
firefox
ubuntu-terminal-app
system-settings
2. Open a youtube video in firefox
3. Sign into an email account on thunderbird
4. Start a game of mines
5. tail -f ~/.cache/upstart/unity8.log in terminal
6. Drop these four apps 1 in each corner so you see all four
7. Drop system-settings in the middle over lapping the other four

EXPECTED:
All 5 apps to run without issue

ACTUAL:
One of the apps will randomly trigger a blank window and title bar to overlay
the entire screen. If mines triggers it just displays the title bar no idea why
it is different. Thunderbird and Firefox seem to be the main culprits.

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

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

[Touch-packages] [Bug 1672335] Re: Black screen on quartered apps with a 5th overlapping

** Attachment added: "screenshot20170310_170113576.png"

https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672335/+attachment/4836940/+files/screenshot20170310_170113576.png

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

Title:
Black screen on quartered apps with a 5th overlapping

Status in unity8 package in Ubuntu:
New

EXPECTED:
All 5 apps to run without issue

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

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

[Touch-packages] [Bug 1672335] [NEW] Black screen on quartered apps with a 5th overlapping

Public bug reported:

STEPS:
1. open the following 5 apps in the deb version of unity8:
mines
thunderbird
firefox
ubuntu-terminal-app
system-settings
2. Open a youtube video in firefox
3. Sign into an email account on thunderbird
4. Start a game of mines
5. tail -f ~/.cache/upstart/unity8.log in terminal
6. Drop these four apps 1 in each corner so you see all four
7. Drop system-settings in the middle over lapping the other four

EXPECTED:
All 5 apps to run without issue

ACTUAL:
One of the apps will randomly trigger a blank window and title bar to overlay 
the entire screen. If mines triggers it just displays the title bar no idea why 
it is different. Thunderbird and Firefox seem to be the main culprits.

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

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

Title:
  Black screen on quartered apps with a 5th overlapping

Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. open the following 5 apps in the deb version of unity8:
  mines
  thunderbird
  firefox
  ubuntu-terminal-app
  system-settings
  2. Open a youtube video in firefox
  3. Sign into an email account on thunderbird
  4. Start a game of mines
  5. tail -f ~/.cache/upstart/unity8.log in terminal
  6. Drop these four apps 1 in each corner so you see all four
  7. Drop system-settings in the middle over lapping the other four

  EXPECTED:
  All 5 apps to run without issue

  ACTUAL:
  One of the apps will randomly trigger a blank window and title bar to overlay 
the entire screen. If mines triggers it just displays the title bar no idea why 
it is different. Thunderbird and Firefox seem to be the main culprits.

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

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

[Touch-packages] [Bug 1665384] [NEW] OEM switch to end user results in wifi not being available.

2017-02-16 Thread Dave Morley

Public bug reported:

STEPS:
1. Grab the latest xenial iso from 
http://cdimages.ubuntu.com/xenial/daily-live/current/
2. Install in oem mode
3. In the OEM desktop double click on Prepare for end user type in your 
password and reboot
4. Run through the end user wizard setting up wifi as you go
5. Login to the end user session
6. Note the empty Wifi symbol in indicator
7. Run nmcli d and see something like
DEVICE  TYPE  STATE CONNECTION
enp3s0  ethernet  Unavailable   --
wlo1wifi  Unavailable   --
lo  loopback  Unmanagaed--

WORKAROUND:
reboot
After reboot everything works as expected and the system autoconnects as 
expected.

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

Title:
  OEM switch to end user results in wifi not being available.

Status in network-manager package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Grab the latest xenial iso from 
http://cdimages.ubuntu.com/xenial/daily-live/current/
  2. Install in oem mode
  3. In the OEM desktop double click on Prepare for end user type in your 
password and reboot
  4. Run through the end user wizard setting up wifi as you go
  5. Login to the end user session
  6. Note the empty Wifi symbol in indicator
  7. Run nmcli d and see something like
  DEVICE  TYPE  STATE CONNECTION
  enp3s0  ethernet  Unavailable   --
  wlo1wifi  Unavailable   --
  lo  loopback  Unmanagaed--

  WORKAROUND:
  reboot
  After reboot everything works as expected and the system autoconnects as 
expected.

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

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

[Touch-packages] [Bug 1664369] [NEW] Super key always applied for VNC session

2017-02-13 Thread Dave Mustaine

Public bug reported:

This a regression report for bug 1440570 with the latest package
installed on 14.04 Trusty.

Problem still reproduces exactly as specified.  Every time I press 'N'
in terminal over VNC, a new window is opened.  I don't want to delete my
super key mappings, they are quite useful when interacting with the
machine locally but I also need remote access to things like a web
browser and VNC is most useful for this.

Unfortunately the super key is constantly on.  I saw that 1440570 was
closed with a fix, I might have undone the fix because I used gnome-
tweak-tool to swap my Alt-Win keys (Alt-Win behavior under typing).
Even after switching this back however, the problem persists over VNC,
making it unusable.

Let me know what I can do to help debug.

Output of apt list metacity:

Listing... Done
metacity/trusty-updates,now 1:2.34.13-0ubuntu4.1 amd64 [installed]

Output of lsb_release -rd:

Description:Ubuntu 14.04.5 LTS
Release:14.04

#regression-update

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Mon Feb 13 11:40:39 2017
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 oem-audio-hda-daily-lts-xenial, 0.201611160201~ubuntu14.04.1, 
4.4.0-62-generic, x86_64: installed
 synaptic-i2c-hid-3.13.0-32-backport, 1.6.4: added
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Dell Device [1028:06b9]
InstallationDate: Installed on 2016-12-16 (59 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
MachineType: Dell Inc. OptiPlex 7040
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=e4b640d9-85ce-43f1-9369-2744897fd9f5 ro pcie_aspm=off quiet splash 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.9
dmi.board.name: 0Y7WYT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7040
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Feb  8 15:18:04 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16485 
 vendor DEL
xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  Super key always applied for VNC session

Status in xorg package in Ubuntu:
  New

Bug description:
  This a regression report for bug 1440570 with the latest package
  installed on 14.04 Trusty.

  Problem still reproduces exactly as specified.  Every time I press 'N'
  in terminal over VNC, a new window is opened.  I don't want to delete
  my super key mappings, they are quite useful when interacting with the
  machine locally but I also need remote access to things like a web
  browser and VNC is most useful for this.

  Unfortunately the super key is constantly on.  I saw that 1440570 was
  closed with a fix, I might have undone the fix because I used gnome-
  tweak-tool to swap my Alt-Win keys (Alt-Win behavior under typing).
  Even after switching this back however, the problem persists over VNC,
  making it unusable.

  Let me know what

[Touch-packages] [Bug 1660402] [NEW] no sound

2017-01-30 Thread Dave H

Public bug reported:

I sent a bug report a few days ago but have not heard back. I had sound before 
the last upgrade. Now no sound. Would someone please respond!!
Dave

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jan 30 09:44:19 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
InstallationDate: Installed on 2017-01-02 (27 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP xw4600 Workstation
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=8fe009f5-768a-4c6c-9e7a-3a60657d80b4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F3 v01.10
dmi.board.asset.tag: 2UA8150PMT
dmi.board.name: 0AA0h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA8150PMT
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F3v01.10:bd03/21/2008:svnHewlett-Packard:pnHPxw4600Workstation:pvr:rvnHewlett-Packard:rn0AA0h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP xw4600 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jan 30 08:33:22 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: nouveau

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


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

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

Title:
  no sound

Status in xorg package in Ubuntu:
  New

Bug description:
  I sent a bug report a few days ago but have not heard back. I had sound 
before the last upgrade. Now no sound. Would someone please respond!!
  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jan 30 09:44:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
  InstallationDate: Installed on 2017-01-02 (27 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP xw4600 Workstation
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=8fe009f5-768a-4c6c-9e7a-3a60657d80b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F3

[Touch-packages] [Bug 1660388] Re: Window decorator corruption

2017-01-30 Thread Dave Chiluk

Uploading jpg a second time so it's obvious, and not missed in the maas
of auto-uploaded logs.

** Attachment added: "Awesome example of decorator corruption."
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1660388/+attachment/4810973/+files/corruption.jpg

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

Title:
  Window decorator corruption

Status in mesa package in Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  After switching back from another user or after lock screen I
  occasionally get corruption.  This usually takes a few weeks after a
  restart to reproduce.  Might be related to nvidia drivers or mesa, or
  compiz, or something else.  Experienced this before recent update to
  mesa 12.0.6, so I don't think this is a mesa regression.

  Decorations shown in jpg move with window, but are not selectable.

  Opening against unity, as the unity taskbar often shares similar
  corruption.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jan 30 10:54:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6163]
  InstallationDate: Installed on 2016-01-15 (380 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jan  9 00:41:06 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1660388] [NEW] Window decorator corruption

2017-01-30 Thread Dave Chiluk

Public bug reported:

After switching back from another user or after lock screen I
occasionally get corruption.  This usually takes a few weeks after a
restart to reproduce.  Might be related to nvidia drivers or mesa, or
compiz, or something else.  Experienced this before recent update to
mesa 12.0.6, so I don't think this is a mesa regression.

Decorations shown in jpg move with window, but are not selectable.

Opening against unity, as the unity taskbar often shares similar
corruption.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160906-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jan 30 10:54:45 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:6163]
InstallationDate: Installed on 2016-01-15 (380 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX79SI
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG28808-500
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jan  9 00:41:06 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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

** Affects: nvidia-graphics-drivers-367 (Ubuntu)
 Importance: Undecided
 Status: New

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


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

** Attachment added: "jpg of example decorator corruption"
   
https://bugs.launchpad.net/bugs/1660388/+attachment/4810946/+files/corruption.jpg

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

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

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

Title:
  Window decorator corruption

Status in mesa package in Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  After switching back from another user or after lock screen I
  occasionally get corruption.  This usually takes a few weeks after a
  restart to reproduce.  Might be related to nvidia drivers or mesa, or
  compiz, or something else.  Experienced this before recent update to
  mesa 12.0.6, so I don't think this is a mesa regression.

  Decorations shown in jpg move with window, but are not

[Touch-packages] [Bug 1659991] [NEW] no sound

2017-01-27 Thread Dave H

Public bug reported:

I installed a ASUS sound card which said it had GE Force 210 encoding.
After installing card I still had sound. I changed the driver to Nvidia
304.134 as requested by system settings.  I then did a apt-get upgrade,
now no sound. Did I do something wrong? Please let me know.

Thanks
Dave
dhot...@gmail.com

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.134  Fri Dec  9 11:30:02 
PST 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jan 27 16:31:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: nvidia-304, 304.134, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
InstallationDate: Installed on 2017-01-02 (25 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP xw4600 Workstation
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=8fe009f5-768a-4c6c-9e7a-3a60657d80b4 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F3 v01.10
dmi.board.asset.tag: 2UA8150PMT
dmi.board.name: 0AA0h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA8150PMT
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F3v01.10:bd03/21/2008:svnHewlett-Packard:pnHPxw4600Workstation:pvr:rvnHewlett-Packard:rn0AA0h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP xw4600 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jan 27 16:25:23 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  no sound

Status in xorg package in Ubuntu:
  New

Bug description:
  I installed a ASUS sound card which said it had GE Force 210 encoding.
  After installing card I still had sound. I changed the driver to
  Nvidia 304.134 as requested by system settings.  I then did a apt-get
  upgrade, now no sound. Did I do something wrong? Please let me know.

  Thanks
  Dave
  dhot...@gmail.com

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.134  Fri Dec  9 11:30:02 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/

[Touch-packages] [Bug 1656280] Re: Support installing subordinate systemd on Ubuntu Desktop 14.04.5

2017-01-26 Thread Dave Morley

I have tested this fix, I can run lxc1 from backports, lxd from
backports and lxc from stable. I can also install and run snaps as
expected.  I have also had no ill affects from using this version of
systemd.

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

Title:
  Support installing subordinate systemd on Ubuntu Desktop 14.04.5

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Add support for installing deputy systemd for snapd on Ubuntu Desktop
  14.04.5

  When installed, deputy systemd provides a subset of functionality as required 
for snapd:
  * Providing necessary units for power management via systemctl
  * Provides private socket API access (and thus systemctl as root) only, and 
is not present on the system D-Bus
  * Does not conflict with systemd-shim
  * Does not change behaviour of systemd-services nor udeb build in anyway

  [Impact]

   * Users can install snapd without regressing Desktop support,
  lxc/lxc1/lxd abilities.

  [Test Case]

   * Power management works (e.g. shutdown/reboot via indicator-system
  and via systemctl)

   * Timedatectl commands report NTP status enable/disabled correctly,
  and can change it

   * Can install and use snapd

   * Can install and use lxc / lxc1 / lxd

  [Regression Potential]

   * Minimal, as bin:systemd uses a separate build in the package with
  additional patches to not intefere with cgmanager's name=systemd
  cgroup; and instead deputy bin:systemd uses name=dsystemd cgroup for
  process management.

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

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

[Touch-packages] [Bug 1657729] [NEW] Webbrowser snap not showing ebay amazon kronensoehne websites

2017-01-19 Thread Dave Morley

Public bug reported:

STEPS:
1. Install the webbrowser-app set it up against ubuntu-app-platform
2. Open the app
3. Browse to ebay.com, amazon.com and kronensoehne.com

EXPECTED:
Sites open as normal

ACTUAL:
Sites are not displayed instead showing network error.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Webbrowser snap not showing ebay amazon kronensoehne websites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the webbrowser-app set it up against ubuntu-app-platform
  2. Open the app
  3. Browse to ebay.com, amazon.com and kronensoehne.com

  EXPECTED:
  Sites open as normal

  ACTUAL:
  Sites are not displayed instead showing network error.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2017-01-16 Thread Dave Chiluk

@jan-huebner

Please educate yourself about the stable release process and development process
https://wiki.ubuntu.com/StableReleaseUpdates
https://wiki.ubuntu.com/UbuntuDevelopment

A regression was discovered in another component.  This is the reason
for the delay.  This is very uncommon, but also the entire reason for
the SRU process.

If you are capable of contributing in a development manner, I will
gladly mentor you or help find a mentor for you.  Contributing solutions
is the best way to help speed fixes for which you may care about in the
open-source world.

As it sounds as though you are using in production in a mission critical 
application perhaps you'd consider financially supporting the project by 
purchasing a support contract, or donating when you download.
https://buy.ubuntu.com/

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends

[Touch-packages] [Bug 1655302] Re: [Trusty] systemd startup fails in the presence of cgmanager

2017-01-11 Thread Dave Morley

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

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

Title:
  [Trusty] systemd startup fails in the presence of cgmanager

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In trusty, systemd 204 clashes with cgmanager, with systemd failing to
  start up properly. As a consequence, snapd fails to operate properly.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2016-12-22 Thread Dave Chiluk

@Lukasz 
Looking good so far.  Appears resolved with 1.10.6-1ubuntu3.2.

Thanks,
Dave.

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

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

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vend

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-12-22 Thread Dave H

Hi Kyle and Michi,

Just to let you know, I still have the problem with the Today scope
refresh / messed up icons, on my MX4 with OTA-14 installed. I was
wondering if you had any time to look again at this problem.

Merry Christmas and happy new year to you all!

Best regards

Dave H

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1626166] Re: lvm2 not starting lvm2-lvmetad on package install

2016-12-13 Thread Dave Chiluk

** Description changed:

  [Impact]
  
-  * On Xenial after installing lvm2, you must reboot before you are able to 
run vgcreate. 
-  * The package installer should be starting lvmetad.service. 
-  *  $ sudo vgcreate localvg
-   /run/lvm/lvmetad.socket: connect failed: No such file or directory
-   WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
-   Please enter a physical volume path.
-   Run `vgcreate --help' for more information.
+  * On Xenial after installing lvm2, you must reboot before you are able to 
run vgcreate.
+  * The package installer should be starting lvmetad.service.
+  *  $ sudo vgcreate localvg
+   /run/lvm/lvmetad.socket: connect failed: No such file or directory
+   WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
+   Please enter a physical volume path.
+   Run `vgcreate --help' for more information.
  
  [Test Case]
  
-  * Running the below commands result in the following error.
-  
-$ sudo apt install lvm2
-$ sudo pvcreate /dev/sdb1 
-$ sudo vgcreate localvg
-   /run/lvm/lvmetad.socket: connect failed: No such file or directory
-   WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
-   Please enter a physical volume path.
-   Run `vgcreate --help' for more information.
+  * Running the below commands result in the following error.
+ 
+    $ sudo apt install lvm2
+    $ sudo pvcreate /dev/sdb1
+    $ sudo vgcreate localvg /dev/sdb1
+   /run/lvm/lvmetad.socket: connect failed: No such file or directory
+   WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
+   Please enter a physical volume path.
+   Run `vgcreate --help' for more information.
  
  [Regression Potential]
  
-  * Solution TBD, opening the bug so I don't forget this in the midst of
+  * Solution TBD, opening the bug so I don't forget this in the midst of
  a sprint.
  
-  * discussion of how regressions are most likely to manifest as a result
+  * discussion of how regressions are most likely to manifest as a result
  of this change.
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance

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

Title:
  lvm2 not starting lvm2-lvmetad on package install

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * On Xenial after installing lvm2, you must reboot before you are able to 
run vgcreate.
   * The package installer should be starting lvmetad.service.
   *  $ sudo vgcreate localvg
    /run/lvm/lvmetad.socket: connect failed: No such file or directory
    WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
    Please enter a physical volume path.
    Run `vgcreate --help' for more information.

  [Test Case]

   * Running the below commands result in the following error.

     $ sudo apt install lvm2
     $ sudo pvcreate /dev/sdb1
     $ sudo vgcreate localvg /dev/sdb1
    /run/lvm/lvmetad.socket: connect failed: No such file or directory
    WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
    Please enter a physical volume path.
    Run `vgcreate --help' for more information.

  [Regression Potential]

   * Solution TBD, opening the bug so I don't forget this in the midst
  of a sprint.

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.

   * This both shows the SRU team that the risks have been considered,
     and provides guidance to

[Touch-packages] [Bug 1649613] [NEW] Networking indicator for unity8 shown in unity7

2016-12-13 Thread Dave Morley

Public bug reported:

Unity8's network indicator is shown along side the nm-applet in unity7
desktops on zesty.

See http://people.canonical.com/~davmor2/personal-screenshots/wrong-
indicator.png

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Assignee: Pete Woods (pete-woods)
 Status: New

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Description changed:

  Unity8's network indicator is shown along side the nm-applet in unity7
  desktops on zesty.
+ 
+ See http://people.canonical.com/~davmor2/personal-screenshots/wrong-
+ indicator.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/1649613

Title:
  Networking indicator for unity8 shown in unity7

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Unity8's network indicator is shown along side the nm-applet in unity7
  desktops on zesty.

  See http://people.canonical.com/~davmor2/personal-screenshots/wrong-
  indicator.png

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

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

[Touch-packages] [Bug 1639233] Re: date setting takes much time to open from indicator-datetime

2016-12-13 Thread Dave Morley

This is a bug in system settings there is an issue on the m10 when
opening the date settings page on xenial.

** Package changed: indicator-datetime (Ubuntu) => ubuntu-system-
settings (Ubuntu)

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

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

Title:
  date setting takes much time to open from indicator-datetime

Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  current build number: 75
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-04 10:44:56
  version version: 75
  version ubuntu: 20161104
  version device: 20161014.0
  version custom: 20161104

  Steps to reproduce:

  1º Go to quick settings bar and drag down from the time icon
  2º Press over the date & time settings

  Current result: date & time setting is displayed after 20 seconds or
  so

  Expected result: date & time settings should be opened faster

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-09 Thread Dave Chiluk

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

** Changed in: maas-images
   Status: New => Invalid

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1648632] [NEW] OTA 14 new phone screen unlock very poor compared to OTA-13

2016-12-08 Thread Dave H

Public bug reported:

Hi, after updating my Meizu MX4 to OTA-14 the screen unlock has changed
to the poor looking desktop/tablet  version. When compared to the
original phone unlock screen (up to OTA-13) this new version looks very
weak, lacking the sophistication of the original version. You would not
see such a screen unlock on an Android or Apple devices. It would be
good to understand why this has been changed, I can only think that you
have settled for the one version, this is a real shame for the phone and
in my opinion is a retrograde step lowering the chances of normal users
adopting the Ubuntu phone.

Can you please consider changing the phone unlock screen back to the
version used before OTA-14.

Your support is appreciated,

Regards

Dave H

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

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

Title:
  OTA 14 new phone screen unlock very poor compared to OTA-13

Status in libusermetrics package in Ubuntu:
  New

Bug description:
  Hi, after updating my Meizu MX4 to OTA-14 the screen unlock has
  changed to the poor looking desktop/tablet  version. When compared to
  the original phone unlock screen (up to OTA-13) this new version looks
  very weak, lacking the sophistication of the original version. You
  would not see such a screen unlock on an Android or Apple devices. It
  would be good to understand why this has been changed, I can only
  think that you have settled for the one version, this is a real shame
  for the phone and in my opinion is a retrograde step lowering the
  chances of normal users adopting the Ubuntu phone.

  Can you please consider changing the phone unlock screen back to the
  version used before OTA-14.

  Your support is appreciated,

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-05 Thread Dave Chiluk

So apparently this is a feature of the dell-branded usb-c devices.
Please see the knowledge base.

http://www.dell.com/support/article/us/en/04/SLN301147

I've heard back from our contacts at dell, and the issue you are seeing
is apparently resolved via a firmware update.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-05 Thread Dave Chiluk

Another thought is that the pxe firmware of the usb-c device was missed
in the rebranding process by dell.  This is actually quite likely in my
opinion.

Either way we need to engage Dell in order to remedy this.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-05 Thread Dave Chiluk

Do you know where the 9c-eb-e8-3c-52-cc originates from? There is
nothing we can do so long as the request to maas originates from the 9c-
eb-e8-3c-52-cc mac address. If the firmware is somehow masking the
actual mac address with the above then that needs to be fixed in the
firmware, or via a firmware setting.

Please attempt to figure out where the 9c-eb-e8-3c-52-cc is.
If it helps a mac search on 9c-eb-e8 yeilds: BizLink (Kunshan) Co. Ltd.
A mac search of 84-7b-eb yeilds Dell Inc.

I suspect they are really the same device. I have a feeling the usb-c
adapter or docking station you are using is really just Bizlink device
that Dell has rebranded.

This really looks like a firmware bug, where the firmware uses the non-
rebranded mac of the device for pxe while in efi, and the rebranded mac
address in the OS after boot.

Have you tried updating the firmware on your machine, and possibly also
the firmware of the usb-c device?

Thanks,
Dave Chiluk

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

Title:
Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
Invalid
Status in maas-images:
New
Status in initramfs-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid

Bug description:
After upgrade from MAAS 2.0 to MAAS 2.1:

Cannot enlist/commission client machines via network boot (or pre-
staging machine) when using usb-c network adapter D59GG (e.g.
Precision 5510). This was working ok with MAAS 2.0.

Using the Xenial 16.04 base image for enlist/commission (no minimum
kernel set).

Enlist/Commission/Deploy works fine with other laptop and desktop
models which have a built in NIC.

From an already deployed Precision 5510 system (16.04.1) I can see the
following module is loaded when the usb-c adapter is connected (and
working):

$ lsmod
usbnet45056 1 cdc_ether

Errors received on client during enlisting with MAAS:

no /run/net-bootif.conf
lvmetad is not activated
...invalid path for logical volume.
gave up waiting for root device
common problems: boot args (cat /proc/cmdline)
check rootdelay = (did system wait long enough)
check root = (did the system wait for the right device?)
missing modules (cat /proc/modules)
ALERT!
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
does not exist. Dropping to shell!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver

- cat /proc/cmdline shows mac address that of usb-c network adapter.
- cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
- cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

I've tried enlisting with older boot image and different kernel versions
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

It seems like the usb-c network adapter isn't loading properly or
maybe just not quickly enough?

Please let me know if you require any more info. I can provide info
from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-02 Thread Dave Chiluk

Alright so the problem at present appears to be that the machine is pxe
booting off of a nic with a mac address that is not showing up after the
kernel boots.

The way the boot works is the bios/efi launches a pxe network stack.
This typically makes a dhcp request. The DHCP server responds with an
IP address, and the address of the PXE/TFTP server *(in this case the
maas server). The network stack firmware on the client then requests
the kernel, initramfs and kernel arguments from the PXE server. The
bios/efi pxe network stack then downloads this, and executes the kernel.

One of the arguments maas is responding with BOOTIF=01-9c-
eb-e8-3c-52-cc. This means the original pxe request originates from
this mac address. When the initramfs starts it runs a script function
called configure_networking that attempts to set up the BOOTIF=01-9c-
eb-e8-3c-52-cc NIC, but it doesn't appear to exist to the OS.

This could mean a few things.
- The NIC doing the initial pxe request is different than the usb-c one. Is
there a chance that there's a wireless nic that has a pxe stack that you've
configured? I know some newer machines are able to pxe boot off of their
network cards so this would be useful to check.
- The mac address is changing between the pxe request and the OS boot.
- IPv6 is in the mix. Are you attempting to boot via ipv6?
- The PXE server is responding with the incorrect mac address in BOOTIF.
The last two can be checked by looking at /var/log/rackd.log on your maas
server. You should be able to grep for 01-9c-eb-e8-3c-52-cc or
01-84-7b-eb-55-c1-95 in the rackd.log to see which nic is making the pxe
request. If 01-9c-eb-e8-3c-52-cc shows up in the rackd.log then it's pretty
definitive that the issue is booting using a nic with that mac somehow.

Please check the above and let me know what you discover.

Thanks,
Dave.

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

Title:
Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
Invalid
Status in maas-images:
New
Status in initramfs-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid

Bug description:
After upgrade from MAAS 2.0 to MAAS 2.1:

Cannot enlist/commission client machines via network boot (or pre-
staging machine) when using usb-c network adapter D59GG (e.g.
Precision 5510). This was working ok with MAAS 2.0.

Using the Xenial 16.04 base image for enlist/commission (no minimum
kernel set).

Enlist/Commission/Deploy works fine with other laptop and desktop
models which have a built in NIC.

From an already deployed Precision 5510 system (16.04.1) I can see the
following module is loaded when the usb-c adapter is connected (and
working):

$ lsmod
usbnet45056 1 cdc_ether

Errors received on client during enlisting with MAAS:

I've tried enlisting with older boot image and different kernel versions
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

It seems like the usb-c network adapter isn't loading properly or
maybe just not quickly enough?

Please let me know if you require any more info. I can provide info
from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)

2016-12-02 Thread Dave Jones

My backup was indeed slapcat / slapadd (for both the main directory and
the cn=config stuff). I'd *guess* that if the package state is "ii" you
may not need the patch (incidentally the patch is in bug description at
the top), particularly if the server's starting fine and everything
queries happily. Mine didn't start after the upgrade so I definitely
needed the patch, but I wouldn't like to guess about other situations
(given how variable LDAP setups can be).

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

Title:
  Database upgrade/migration fails with nested db directories (lucid to
  precise)

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Precise:
  Confirmed
Status in openldap package in Debian:
  Fix Released

Bug description:
  Hi,

  I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
  LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
  supported yet).

  The incompatible database upgrading process in the preinst/postinst
  files failed in the following scenario.

  We have two suffixes/databases at the following paths:-

   * /var/lib/ldap
   * /var/lib/ldap/accesslog

  The preinst database dumping part of the process worked just fine and
  created the appropriate LDIF files under
  /var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
  stating:-

  """
    Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
    - directory dc=REDACTEDs,dc=co,dc=uk... failed.

  Loading the database from the LDIF dump failed with the following
  error while running slapadd:
  4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
  4fbdfebf config error processing olcDatabase={2}hdb,cn=config: 
olcDbDirectory: value #0: invalid path: No such file or directory
  slapadd: bad configuration directory!
  """

  This is because when move_incompatible_databases_away() runs it finds
  the main database first (/var/lib/ldap) and moves all top level
  entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
  and this includes the accesslog subdirectory which then no longer
  exists. When slapadd runs it checks config specifying that directory
  and bails with the above error given it is indeed missing.

  I've tested a tentative fix and that's to patch the two find commands
  (one in is_empty_dir() one in move_old_database_away to also specify
  -type f so that the directory structure is preserved when moving the
  old database away (accesslog will be backed up separately when its
  suffx is iterated over in move_incompatible_databases_away()).

  The simple and very tentative patch for this is:-

  """
  # diff -u slapd.scripts-common.old slapd.scripts-common
  --- slapd.scripts-common.old  2012-05-24 10:33:01.746206585 +0100
  +++ slapd.scripts-common  2012-05-24 10:33:23.967902747 +0100
  @@ -391,7 +391,7 @@
     echo -n "  - directory $suffix... " >&2
     mkdir -p "$backupdir"
     find "$databasedir" -mindepth 1 -maxdepth 1\
  - -exec mv {} "$backupdir" \;
  + -type f -exec mv {} "$backupdir" \;
     echo done. >&2
    else
     cat >&2 /dev/null`
    if [ -n "$output" ]; then
     return 1
    else
  """

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

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

[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)

2016-11-30 Thread Dave Jones

Hi Andre - I did take a backup of the LDAP directory prior to "do-
release-upgrade" (actually I had nightly backups running so I just
grabbed a copy of the last one of those). That's what I was referring to
when I stated "restore the old-version backup...". It's been a few
months now but I vaguely recall that the upgrade procedure needs the
state of the database prior to the (failed) upgrade in order to succeed
after patching.

Hence, if my recollection is accurate, my procedure was:

1. Patch the slapd.postinst script
2. Restore the database to its state prior to the (failed) upgrade
3. Run "dpkg --configure -a" to cause the slapd postinst script to upgrade the 
database successfully

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

Title:
  Database upgrade/migration fails with nested db directories (lucid to
  precise)

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Precise:
  Confirmed
Status in openldap package in Debian:
  Fix Released

Bug description:
  Hi,

  I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
  LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
  supported yet).

  The incompatible database upgrading process in the preinst/postinst
  files failed in the following scenario.

  We have two suffixes/databases at the following paths:-

   * /var/lib/ldap
   * /var/lib/ldap/accesslog

  The preinst database dumping part of the process worked just fine and
  created the appropriate LDIF files under
  /var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
  stating:-

  """
    Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
    - directory dc=REDACTEDs,dc=co,dc=uk... failed.

  Loading the database from the LDIF dump failed with the following
  error while running slapadd:
  4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
  4fbdfebf config error processing olcDatabase={2}hdb,cn=config: 
olcDbDirectory: value #0: invalid path: No such file or directory
  slapadd: bad configuration directory!
  """

  This is because when move_incompatible_databases_away() runs it finds
  the main database first (/var/lib/ldap) and moves all top level
  entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
  and this includes the accesslog subdirectory which then no longer
  exists. When slapadd runs it checks config specifying that directory
  and bails with the above error given it is indeed missing.

  I've tested a tentative fix and that's to patch the two find commands
  (one in is_empty_dir() one in move_old_database_away to also specify
  -type f so that the directory structure is preserved when moving the
  old database away (accesslog will be backed up separately when its
  suffx is iterated over in move_incompatible_databases_away()).

  The simple and very tentative patch for this is:-

  """
  # diff -u slapd.scripts-common.old slapd.scripts-common
  --- slapd.scripts-common.old  2012-05-24 10:33:01.746206585 +0100
  +++ slapd.scripts-common  2012-05-24 10:33:23.967902747 +0100
  @@ -391,7 +391,7 @@
     echo -n "  - directory $suffix... " >&2
     mkdir -p "$backupdir"
     find "$databasedir" -mindepth 1 -maxdepth 1\
  - -exec mv {} "$backupdir" \;
  + -type f -exec mv {} "$backupdir" \;
     echo done. >&2
    else
     cat >&2 /dev/null`
    if [ -n "$output" ]; then
     return 1
    else
  """

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-28 Thread Dave Chiluk

One of my collegues informed me that maas 2.1 is meant to use 
https://images.maas.io/ephemeral-v3/daily/
Instead of the ephemeral-v2 images.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-28 Thread Dave Chiluk

1. So this indicates to me that the kernel is unable to control the usb
device. When you mentioned earlier that you were able to investigate
the usb-c device with a 16.04.1 machine, what exact kernel version was
that machine running. uname -a output should be sufficient.

2. Can you similarly provide the exact kernel version that you are using
during commissioning, when dropped to shell?

3. Were you able to utilize the device under this kernel or did it
simply load the kernel driver there as well? I.e. do you see a device
for the usb device in /sys/class/net/?

4. Also can you please provide the lsusb -vv output from that machine as
well. I'd like to look up the device id's against the cdc_ether driver
to see if the device id was added to one of the later 4.4 kernels.

5. Also are you using stable images or daily images. If you haven't done so
already can you enable the daily images, and check using those?
Instructions are available here
http://maas.io/docs/en/installconfig-images
The images I'm referring to are available here
https://images.maas.io/ephemeral-v2/daily/

Thank you,

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

Title:
Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
Invalid
Status in maas-images:
New
Status in initramfs-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid

Bug description:
After upgrade from MAAS 2.0 to MAAS 2.1:

Cannot enlist/commission client machines via network boot (or pre-
staging machine) when using usb-c network adapter D59GG (e.g.
Precision 5510). This was working ok with MAAS 2.0.

Using the Xenial 16.04 base image for enlist/commission (no minimum
kernel set).

Enlist/Commission/Deploy works fine with other laptop and desktop
models which have a built in NIC.

From an already deployed Precision 5510 system (16.04.1) I can see the
following module is loaded when the usb-c adapter is connected (and
working):

$ lsmod
usbnet45056 1 cdc_ether

Errors received on client during enlisting with MAAS:

I've tried enlisting with older boot image and different kernel versions
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

It seems like the usb-c network adapter isn't loading properly or
maybe just not quickly enough?

Please let me know if you require any more info. I can provide info
from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-23 Thread Dave Chiluk

>From the initramfs shell can you provide me the output for

ls -la /sys/class/net/*
and
cat /sys/class/net/*/address

I have a feeling you'll only see lo and enx847beb55c195.  Specifially I'm 
looking for the device name that matches your BOOTIF mac address.  However if 
it's showing up please attempt to run 
$ ipconfig -t 100 

Then see if the nic comes up from there with ip a.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-23 Thread Dave Chiluk

If the device is not being detected I have a feeling there may be
something going wrong with udev.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-23 Thread Dave Chiluk

So from the best I can determine it looks like configure_networking out
of scripts/functions of the initramfs is failing to properly bring up
the network device.  I'm going through the process now to figure out
what logic might actually be stopping it from functioning.  I'll let you
know more when I have something more concrete.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1633227] Re: After update to 16.10 second screen background is not cleared

2016-11-22 Thread Dave H

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

This bug was affecting me as well but seems to have been fixed in the
last week or so.

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

Title:
  After update to 16.10 second screen background is not cleared

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I just updated from 16.04 to 16.10 and now the window background is
  not cleared anymore - so when you drag windows they leave resedue
  which looks like the screenshot I attached

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

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

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-18 Thread Dave Chiluk

@Richard Lovell
Can you please provide me the console log messages that exist above the "no 
/run/net-bootif.conf"?

Additionally can I get the output of following commands from the laptop after 
the message "Dropping to shell!"
- ip a # I'm not sure if this available, but ifconfig or similar would be 
helpful.  Basically I need the name of the nic as discovered.  I have a feeling 
that the initramfs is not correctly checking for this name when it attempts to 
bring up the interfaces.
- lsmod 
- cat /proc/cmdline

More commands may be necessary after I have this output and am able to
investigate the initramfs.

Thanks

** Changed in: maas
   Status: Incomplete => Invalid

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

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1556274] Re: MX4 bluetooth not pairing with Jaguar XKR 2007

2016-11-16 Thread Dave H

Hi, Just wondered if anyone was looking at the above. My Meizu MX4 is
now on OTA-13 and although the car can see the phone and identifies it
as an MX4 it will not pair with the phone. I can understand that it may
not be possible to use the high end feature of the Jaguar blue-tooth
connection but I would have though the car should at least pair with the
phone.

Any idea's would be welcome. Thanks for your continued great work.

Regards

Dave H

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

Title:
  MX4 bluetooth not pairing with Jaguar XKR 2007

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi I have an MX4 with OTA-9.1 update installed. The phone has never
  been able to pair with my Jaguar XKR 2007. The car finds the Meizu MX4
  and displays the phone type, but will not pair to it Any help to
  improve this would be appreciated.

  Just to say, really enjoying Ubuntu Touch, once miracast is added it
  will be the one to beat.

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2016-11-14 Thread Dave Hartley

HP Elitebook 850 G3 with a fresh install of 16.04.1 had the suspend bug
(laptop would not suspend when the lid was closed).

Adding the line in login.confd worked for suspending, but I now have to
press the power button to resume from suspend. Opening the lid does not
resume.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-10 Thread Dave H

Hi Michi,

OK thanks for checking and I agree with your explanation as you can see
similar problems with other scopes. I guess the Today scope looks worse
(and more annoying) as its the main scope you see each time the phone is
active, others are not always checked or used. Also the scopes with
multiple feeds are more effected. This problem wouldn’t be so bad if
they cleared them selves once a good  wifi signal returns, but as it is
now you sometimes have to restart the phone. If this could be resolved I
think it would make Ubuntu Touch look more stable for normal every day
use, so should be given a high priority for OTA-14 / 15.

Note, have attached this mornings Today scope crash. In this case the
wifi has been active with good signal all night. Looking at the settings
in my 4G EE home broadband router, the DHCP lease time is set to 86400s
(1 day) so the IP number could have changed overnight, note sure if this
could also be related to general wifi issues.

Thanks for your continued support and hard work,

Best regards

Dave H

** Attachment added: "Today scope - morning result - after refresh still no 
good."
   
https://bugs.launchpad.net/today-scope/+bug/1637841/+attachment/4775237/+files/screenshot20161110_083755884.png

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Dave H

Hi Kyle,

Thanks for the Test scope. I installed it and found a similar result to
you. If you keep repeating the refresh every 30s (ten times in my case)
you get a mixed result.

1. 1 unknown / 2 unknown

2. 1 unknown / 2 unknown

3. 1 connected / 2 unknown (after pull refresh in Today scope and
recheck Test scope)

4. 1 connected / 2 unknown

5. 1 unknown / 2 unknown

6. 1 connected / 2 unknown

7. 1 unknown / 2 unknown

8. 1 unknown / 2 unknown

9. 1 connected / 2 unknown

10. 1 unknown / 2 unknown

See picture attached (for 1 connected / 2 unknown)

If you need me to try anything else let me know.

Regards

Dave H

** Attachment added: "Test scope result.png"

https://bugs.launchpad.net/today-scope/+bug/1637841/+attachment/4772502/+files/Test%20scope%20result.png

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

Title:
Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
Incomplete
Status in unity-scopes-api package in Ubuntu:
New

Bug description:
Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
or no wifi the today scope is messed up, in the same way as the below
report I found for the BQE4.5. If you try to refresh it the problem is
not resolved (such as only half the date shown, or no date or no
pictures). Even after returning to a good wifi signal and performing
the pulldown refresh the problem is not resolved. As I have seen this
problem from the start on older OTA versions (I have reported before),
my feeling is there is a fundamental problem with the way scopes are
refreshed when you pull down the screen. I have also screen the "no
pictures" on other scopes and the refresh not working, could this be a
common scope problem and nothing to do with the today scope?.

Note, when the today scope is messed up if you un-tick the "day info"
then refresh and then tick day info again, this sometimes helps. If no
pictures displayed (today and other scopes) I normally have to reset
the phone to correct the problem.

Your support us appreciated,

Regards

Dave H

Similar bug (BQE4.5 & OTA9)

* Upon updating today screen (swipe-down) get partially updated info, see
attached step01.png
* Activating side bar/pressing on Ubuntu icon shows that the rest of scopes
were updated, but they somehow ended up above today screen controls, see
attached step02.png
* Activating side bar again makes it look like on attached step03.png
* Finally, pressing on Ubuntu icon once more results in empty today screen,
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Dave H

** Description changed:

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Dave H

Hi Kyle,

Thanks for all your efforts to try to resolve this issue. I have install
the file you sent using the below method:

Logged onto my MX4 in developer mode using adb shell (in read only
mode). Copied your file to the phone Download directory and:

phablet@ubuntu-phablet:~/Downloads$ pkcon --allow-untrusted install-
local  com.canonical.scopes.dashboard_4.11.1_armhf.click

The package installed OK!  (I am no software engineer, but will have a
go)

Have just tried the New Today scope version 4.11.1, please see below result.
Long distance weak wifi - on refresh on the data shown. 
Moving into just 3G - after a few refreshes first the data then weather and BBC 
shown. 
Moving back into weak wifi - on refresh just date icon shown (no weather or BBC)
Back to my house with strong wifi - still only date shown even after 5 pulldown 
refresh actions. 
After more refreshes the screen went blank. 
Checked my wifi speed with FAST app , OK about 24M
Checked internet - all OK 

Looking at the Today scope again, refresh sometimes shows the date icon
only or blank screen.

Entered Today scope settings and turned off weather and BBC (I dont have 
holidays selected and cant see any elpais option on my phone). My selected 
items in the Today scope settings are listed below. 
Location data
Contacts
Day Info
Weather Channel
BBC
euronews

Now on refresh the euronews pictures are back, sometimes!
I then turned the BBC and weather back on (in Today scope settings)- strange, 
sometimes I get the weather other times just the date icon. 


>From this point, no number of refreshes could correct the today scope so I 
>reset the phone. 
All then back to normal. 

Hope this helps

Regards

Dave H

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

2016-11-01 Thread Dave Shilson

+10 users affected here (16.04 LTS)

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

Title:
  tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  i need

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic i686
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct  8 16:04:40 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-13 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xad14eb08 :mov
(%eax),%eax
   PC (0xad14eb08) ok
   source "(%eax)" (0x007c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
  Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-28 Thread Dave Chiluk

I spoke too soon still exists in Yakkety.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1637281] [NEW] issue with what to do when the sidestage empties

2016-10-27 Thread Dave Morley

Public bug reported:

STORY:
You open the music player play some music, you move the player to the side 
stage and open the webbrowser to do some work, you find browsing albums easier 
in main stage so you drag the music app back out to find an album.

STEPS:
prerequisite frieza with some music on it
1. Open the music player
2. Set some music playing
3. three finger drag the music app to the side stage
4. Open the browser
5. Note the browser adjusts it's size to match the sidestage
6. Drag the Music app back out of side stage
7. at this point the player control are now under the sidestage

EXPECTED:
I either expect the windows to remain resized to fit the available screen or 
for the side stage to close upon emptying.

ACTUAL:
The empty sidestage covers the right hand side of the application under it 
meaning you have to close the stage in order to interact with that portion of 
the screen.  This is very demonstratable on music app on the Frieza Tablet due 
to the convergent design of music app.

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

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

Title:
  issue with what to do when the sidestage empties

Status in unity8 package in Ubuntu:
  New

Bug description:
  STORY:
  You open the music player play some music, you move the player to the side 
stage and open the webbrowser to do some work, you find browsing albums easier 
in main stage so you drag the music app back out to find an album.

  STEPS:
  prerequisite frieza with some music on it
  1. Open the music player
  2. Set some music playing
  3. three finger drag the music app to the side stage
  4. Open the browser
  5. Note the browser adjusts it's size to match the sidestage
  6. Drag the Music app back out of side stage
  7. at this point the player control are now under the sidestage

  EXPECTED:
  I either expect the windows to remain resized to fit the available screen or 
for the side stage to close upon emptying.

  ACTUAL:
  The empty sidestage covers the right hand side of the application under it 
meaning you have to close the stage in order to interact with that portion of 
the screen.  This is very demonstratable on music app on the Frieza Tablet due 
to the convergent design of music app.

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

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

[Touch-packages] [Bug 1636760] [NEW] Crash on Xenial

2016-10-26 Thread Dave Morley

Public bug reported:

STEPS:
1. Flash the Frieza with xenial image
2. Open the browser app

EXPECTED:
I expected the app to open and work as expected

ACTUAL:
It opens starts to display the loading page line for the home page and then
locks up.

** Affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "application-legacy-webbrowser-app-.log"

https://bugs.launchpad.net/bugs/1636760/+attachment/4767487/+files/application-legacy-webbrowser-app-.log

** Description changed:

STEPS:
- 1. Flash the m10 with xenial image
+ 1. Flash the Frieza with xenial image
2. Open the browser app

EXPECTED:
I expected the app to open and work as expected

ACTUAL:
It opens starts to display the loading page line for the home page and then
locks up.

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

Title:
Crash on Xenial

Status in webbrowser-app package in Ubuntu:
New

Bug description:
STEPS:
1. Flash the Frieza with xenial image
2. Open the browser app

EXPECTED:
I expected the app to open and work as expected

ACTUAL:
It opens starts to display the loading page line for the home page and then
locks up.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-25 Thread Dave Chiluk

With my recent update to Yakkety I no longer seem to be experiencing
this issue.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1633012] Re: indicator-network show no wi-fi ap's (amd64)

2016-10-13 Thread Dave Morley

** Changed in: network-manager (Ubuntu)
   Status: New => 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/1633012

Title:
  indicator-network show no wi-fi ap's (amd64)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Enviroment:

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  HW: intel+intel graphics+ intel wireless 3160 Laptop &&
  amd+nvidia+ralink PC

  1º I did an OEM installation on my laptop and a manual partitioning in PC
  2º On first boot check indicator-network status

  Current result: if you connected to Wi-Fi during installation, on
  first boot it does not connect to it. Indicator-network shows no wi-fi
  ap's but ethernet works fine when you plug the rj45

  Expected result: indicator-network should remember the Wi-Fi you
  connected during installation and automatically connect to it(not in
  OEM)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 11:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  IpRoute:
   default via 192.168.1.1 dev enp0s25  proto static  metric 100 
   169.254.0.0/16 dev enp0s25  scope link  metric 1000 
   192.168.1.0/24 dev enp0s25  proto kernel  scope link  src 192.168.1.55  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH
   Conexión cableada 1  4774df2a-6439-34e9-bbe9-9089c987c290  802-3-ethernet   
1476351437  jue 13 oct 2016 11:37:17 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes enp0s25  
activated  /org/freedesktop/NetworkManager/ActiveConnection/2 
   Hedmonhater  4f551ad5-dbcb-4894-ac36-d031439936fe  802-11-wireless  
1476349793  jue 13 oct 2016 11:09:53 CEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s25  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Conexión cableada 1  4774df2a-6439-34e9-bbe9-9089c987c290  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   wlp2s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set

Regression tracked via bug #1631474

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Description changed:

  [Impact]
  
   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp
  
   * Regression-updates
  
   * The fix better parses the ip= command line argument.
  
  [Test Case]
  
   * Create a machine that boots using an nfsroot.
  
   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.
  
   * Discover that the device never comes up because, networking is not
  configured correctly.
  
  [Regression Potential]
  
   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.
  
  [Other Info]
  
-  * There are a number of other issues in this code base that are not solved 
by this fix.
+  * There are a number of other issues in this code base that are not solved 
by this fix. 
+- The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken 
+- 
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.
  
  Original Bug Description Follows==
  
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if this
  issue is specific to AWS or will occur with different hardware or in
  different environments.
  
  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in
  networking being configured.
  
  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.
  
  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with it.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix. 
 - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken 
 - 
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

I tested maas's command line as well.

/proc/cmdline from a maas pxe boot is
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=192.168.1.5 iscsi_target_port=3260 iscsi_initiator=bonusvm2
ip=bonusvm2:BOOTIF ro
root=/dev/disk/by-path/ip-192.168.1.5:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily-lun-1
overlayroot=tmpfs
cloud-config-url=http://192.168.1.5/MAAS/metadata/latest/by-id/4y3h7t/?op=get_preseed
log_host=192.168.1.5 log_port=514
initrd=ubuntu/amd64/hwe-y/yakkety/daily/boot-initrd BOOTIF=01-52-54-00-ca-c0-9e

Notable variables are
ip=bonusvm2:BOOTIF BOOTIF=01-52-54-00-ca-c0-9e

This use case continues to function.

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

Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option

Status in initramfs-tools package in Ubuntu:
In Progress
Status in initramfs-tools source package in Xenial:
Confirmed
Status in initramfs-tools source package in Yakkety:
In Progress

Bug description:
[Impact]

* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp

* Regression-updates

* The fix better parses the ip= command line argument.

[Test Case]

* Create a machine that boots using an nfsroot.

* Use ip=:eth0:dhcp on the kernel command line. To set up
networking.

* Discover that the device never comes up because, networking is not
configured correctly.

[Regression Potential]

* Regressions potential is limited to machines using
ip={""|*|on|any|dhcp} on the kernel command line. As this is
already broken regression potential is minimal. This is common on
machines that use nfsroot or otherwise pxe boot.

[Other Info]

* There are a number of other issues in this code base that are not solved
by this fix.
* The networking configuration does not strictly follow the kernel
documentation as described
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This
should be fixed.

Original Bug Description Follows==

initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
networking is not initialized when the boot option "ip=dhcp" is
provided. We are seeing this problem in AWS, but cannot confirm if
this issue is specific to AWS or will occur with different hardware or
in different environments.

Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
in networking being configured.

The issue does not occur with 0.122ubuntu8.2 or previous versions when
"ip=dhcp" is set.

AWS has no console so debugging is not a trivial task. I do have a
console log with some output, and will update this bug shortly with
it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Description changed:

  [Impact]
  
-  * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+  * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp
  
-  * Regression-updates
+  * Regression-updates
  
-  * The fix better parses the ip= command line argument.
+  * The fix better parses the ip= command line argument.
  
  [Test Case]
  
-  * Create a machine that boots using an nfsroot.
+  * Create a machine that boots using an nfsroot.
  
-  * Use ip=:eth0:dhcp on the kernel command line.  To set up
-networking.
+  * Use ip=:eth0:dhcp on the kernel command line.  To set up
+    networking.
  
-  * Discover that the device never comes up because, networking is not
- conifgured correctly.
+  * Discover that the device never comes up because, networking is not
+ configured correctly.
  
  [Regression Potential]
  
-  * Regressions potential is limited to machines using
+  * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
- already broken regression potential is minimal.
+ already broken regression potential is minimal.  This is common on
+ machines that use nfsroot or otherwise pxe boot.
  
  [Other Info]
-  
-  * There are a number of other issues in this code base that are not solved 
by this fix.
-  * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.
+ 
+  * There are a number of other issues in this code base that are not solved 
by this fix.
+  * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.
  
  Original Bug Description Follows==
  
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if this
  issue is specific to AWS or will occur with different hardware or in
  different environments.
  
  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in
  networking being configured.
  
  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.
  
  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with it.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

I have uploaded a new version of initramfs-tools to my ppa, I would
again appreciate testing on this.  Notably I fixed an bug that was
causing all_netbootable_devices to be tried instead of the interface
specified on the command line.

I also now handle the case where ip=:bootif , which really shouldn't
be a concern to most.

I still think ip=bootif might fail *(if /run/net-${DEVICE}.conf does not
exist), but as this is an anaconda use case and not a mainline kernel
use case I'll ignore it for the purpose of the SRU.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Patch added: "lp1631474.yakkety.debdiff"

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff

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

Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option

Status in initramfs-tools package in Ubuntu:
In Progress
Status in initramfs-tools source package in Xenial:
Confirmed

Bug description:
[Impact]

* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp

* Regression-updates

* The fix better parses the ip= command line argument.

[Test Case]

* Create a machine that boots using an nfsroot.

* Use ip=:eth0:dhcp on the kernel command line. To set up
networking.

* Discover that the device never comes up because, networking is not
conifgured correctly.

[Regression Potential]

* Regressions potential is limited to machines using
ip={""|*|on|any|dhcp} on the kernel command line. As this is
already broken regression potential is minimal.

[Other Info]

Original Bug Description Follows==

Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
in networking being configured.

The issue does not occur with 0.122ubuntu8.2 or previous versions when
"ip=dhcp" is set.

AWS has no console so debugging is not a trivial task. I do have a
console log with some output, and will update this bug shortly with
it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

Updated debdiff to handle ip=:bootif use case.

** Patch added: "lp1631474.xenial.debdiff"

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff

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

Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option

Status in initramfs-tools package in Ubuntu:
In Progress
Status in initramfs-tools source package in Xenial:
Confirmed

Bug description:
[Impact]

* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp

* Regression-updates

* The fix better parses the ip= command line argument.

[Test Case]

* Create a machine that boots using an nfsroot.

* Use ip=:eth0:dhcp on the kernel command line. To set up
networking.

* Discover that the device never comes up because, networking is not
conifgured correctly.

[Regression Potential]

* Regressions potential is limited to machines using
ip={""|*|on|any|dhcp} on the kernel command line. As this is
already broken regression potential is minimal.

[Other Info]

Original Bug Description Follows==

Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
in networking being configured.

The issue does not occur with 0.122ubuntu8.2 or previous versions when
"ip=dhcp" is set.

AWS has no console so debugging is not a trivial task. I do have a
console log with some output, and will update this bug shortly with
it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-11 Thread Dave Chiluk

** Patch removed: "lp1631474.yakkety.debdiff"

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff

** Patch removed: "lp1631474.xenial.debdiff"

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff

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

Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option

Status in initramfs-tools package in Ubuntu:
In Progress
Status in initramfs-tools source package in Xenial:
Confirmed

Bug description:
[Impact]

* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp

* Regression-updates

* The fix better parses the ip= command line argument.

[Test Case]

* Create a machine that boots using an nfsroot.

* Use ip=:eth0:dhcp on the kernel command line. To set up
networking.

* Discover that the device never comes up because, networking is not
conifgured correctly.

[Regression Potential]

* Regressions potential is limited to machines using
ip={""|*|on|any|dhcp} on the kernel command line. As this is
already broken regression potential is minimal.

[Other Info]

Original Bug Description Follows==

Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
in networking being configured.

The issue does not occur with 0.122ubuntu8.2 or previous versions when
"ip=dhcp" is set.

AWS has no console so debugging is not a trivial task. I do have a
console log with some output, and will update this bug shortly with
it.

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

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

[Touch-packages] [Bug 1614987] Re: cannot connect BT speaker to laptop running unity8

2016-10-11 Thread Dave Morley

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

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

Title:
  cannot connect BT speaker to laptop running unity8

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Laptop running unity8::

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  BT speaker: Avrha Strauss P/N:11BQALT01

  Steps to reproduce:

  1º On your laptop running unity8, go to System settings>Bluetooth and turn it 
on
  2º Turn on your BT speaker as well(on this model just press the BT button a 
few seconds for being discoverable)
  3º After a few seconds BT speaker should be found by the laptop, but it 
doesn't

  Current result: Laptop can discover and pair with Utouch and android
  devices, but is not seeing the BT speaker

  Expected result: Laptop should discover and be able to pair BT
  speakers

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

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

[Touch-packages] [Bug 1632275] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

2016-10-11 Thread Dave Morley

Seems easy to reproduce on i386 but not so easy on amd64

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

Title:
  indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Live session on i386 has an issue immediately which reports that
  network-manager indicator crashed

  On the installed version it is impossible to connect to the net via
  wifi

  Will check on amd64 but as far as I can tell it is fine there.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CasperVersion: 1.379
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 11 10:17:39 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ExecutableTimestamp: 1475255305
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCwd: /home/ubuntu
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb779ceba :   mov0x4(%eax),%ebx
   PC (0xb779ceba) ok
   source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
   #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   n = 
   list = 
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   ?? ()
  Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.indicator-network.log: indicator-network stop/pre-start, process 5765

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

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

[Touch-packages] [Bug 1632275] [NEW] indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

2016-10-11 Thread Dave Morley

Public bug reported:

Live session on i386 has an issue immediately which reports that
network-manager indicator crashed

On the installed version it is impossible to connect to the net via wifi

Will check on amd64 but as far as I can tell it is fine there.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
CasperVersion: 1.379
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Oct 11 10:17:39 2016
ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
ExecutableTimestamp: 1475255305
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
ProcCwd: /home/ubuntu
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb779ceba : mov0x4(%eax),%ebx
 PC (0xb779ceba) ok
 source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-network
Stacktrace:
 #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
 n = 
 list = 
 #1  0x in ?? ()
 No symbol table info available.
StacktraceTop:
 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
 ?? ()
Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.indicator-network.log: indicator-network stop/pre-start, process 5765

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


** Tags: apport-crash apport-failed-retrace i386 yakkety

** Information type changed from Private to Public

** Description changed:

- Live session on i386 has an issues immediately which reports that
+ Live session on i386 has an issue immediately which reports that
  network-manager indicator crashed
  
  On the installed version it is impossible to connect to the net via wifi
  
  Will check on amd64 but as far as I can tell it is fine there.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CasperVersion: 1.379
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 11 10:17:39 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ExecutableTimestamp: 1475255305
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCwd: /home/ubuntu
  ProcEnviron:
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0xb779ceba :   mov0x4(%eax),%ebx
-  PC (0xb779ceba) ok
-  source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
-  destination "%ebx" ok
+  Segfault happened at: 0xb779ceba :   mov0x4(%eax),%ebx
+  PC (0xb779ceba) ok
+  source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
+  destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
-  #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
-  n = 
-  list = 
-  #1  0x in ?? ()
-  No symbol table info available.
+  #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
+  n = 
+  list = 
+  #1  0x in ?? ()
+  No symbol table info available.
  StacktraceTop:
-  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62)

[Touch-packages] [Bug 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3

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

I'd really appreciate if you tested the ppa available in bug 1631474,
and reported back.

I don't have access to a full nfsroot environment so this would be very 
helpful.  Also, 
Please move back to the ip=:eth0:dhcp, as this should be working once more. 
 IP=eth0, is an undocumented behavior, and ip=:eth0:dhcp should be more 
universally accepted.

Thanks,
Dave

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

Title:
  Some network configuration cmdline arguments doesn't work anymore with
  version 0.122ubuntu8.3

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  In the past, until the version  0.122ubuntu8.1, we used the syntax
  "ip=:eth0:dhcp" as described in the kernel's documentation :
  https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

  The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0"
  syntax as far as i have tested it.

  So, the current last package version leaves the machine without
  network on boot. Any host that needs network on boot (nfsroot / using
  dropbear for example) might not boot properly.

  Regards

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Description changed:

+ [Impact]
+ 
+  * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+ ip=dhcp or ip=:eth0:dhcp
+ 
+  * Regression-updates
+ 
+  * The fix better parses the ip= command line argument.
+ 
+ [Test Case]
+ 
+  * Create a machine that boots using an nfsroot.
+ 
+  * Use ip=:eth0:dhcp on the kernel command line.  To set up
+networking.
+ 
+  * Discover that the device never comes up because, networking is not
+ conifgured correctly.
+ 
+ [Regression Potential]
+ 
+  * Regressions potential is limited to machines using
+ ip={""|*|on|any|dhcp} on the kernel command line.  As this is
+ already broken regression potential is minimal.
+ 
+ [Other Info]
+  
+  * There are a number of other issues in this code base that are not solved 
by this fix.
+  * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.
+ 
+ Original Bug Description Follows==
+ 
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if this
  issue is specific to AWS or will occur with different hardware or in
  different environments.
  
  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in
  networking being configured.
  
  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.
  
  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with it.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
 networking.

   * Discover that the device never comes up because, networking is not
  conifgured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.

  [Other Info]
   
   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Patch added: "lp1631474.yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

I fixed up the comment, and the changelog comment and resubmit the
debdiff.

** Patch added: "lp1631474.xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Patch removed: "lp1631474.xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Patch added: "lp1631474.xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

I created a PPA with a proposed solution to this issue.  If I could get
some testing with this ppa I would appreciate it.  Additionally if you
test the ppa please report back and include your /proc/cmdline in your
comment.

Thank you,
Dave Chiluk

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

Woops I forgot to include the PPA
https://launchpad.net/~chiluk/+archive/ubuntu/lp1631474

I will remove this ppa when the package hits -proposed.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3

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

Marking as duplicate of 1631474 as I'm already working this over there.
Normally we'd dupe the newer against the older, but I'm already working
over there, and I don't want to lose history in the switch.

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

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** This bug has been marked a duplicate of bug 1631474
   No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

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

Title:
  Some network configuration cmdline arguments doesn't work anymore with
  version 0.122ubuntu8.3

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  In the past, until the version  0.122ubuntu8.1, we used the syntax
  "ip=:eth0:dhcp" as described in the kernel's documentation :
  https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

  The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0"
  syntax as far as i have tested it.

  So, the current last package version leaves the machine without
  network on boot. Any host that needs network on boot (nfsroot / using
  dropbear for example) might not boot properly.

  Regards

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

Dediff from 8.2 to 8.3.
http://launchpadlibrarian.net/286956415/initramfs-tools_0.122ubuntu8.2_0.122ubuntu8.3.diff.gz

** Tags added: cpc sts

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option