[Touch-packages] [Bug 1598505] Re: adb usage has typo disbled => disabled

[Kevin Dalley]

** Summary changed:

- adb usage has typo disabled => disabled
+ adb usage has typo disbled => disabled

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

Title:
  adb usage has typo disbled => disabled

Status in android-tools package in Ubuntu:
  New

Bug description:
  type "adb shell help"

  get the following output, include "disbled" below

  Please correct disbled to disabled

  pm list packages: prints all packages, optionally only
those whose package name contains the text in FILTER.  Options:
  -f: see their associated file.
  -d: filter to only show disbled packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: android-tools-adb 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul  2 09:59:40 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (411 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (32 days ago)

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

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

[Touch-packages] [Bug 1588395] Re: 70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it contains a space

[Kevin Dalley]

Add double quotes around the right hand side of the assignment
definitely solved the problem for me.

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

Title:
  70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it
  contains a space

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  In /etc/X11/Xsession.d/70gconfd_path-on-session these lines fail if
  there is a space in ${DESKTOP_SESSION}:

export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path

  The error output to ~/.xsession-errors is:

  /etc/X11/Xsession: 6: export: Session.mandatory.path: bad variable
  name

  I'm not sure why the error is pointing to the wrong file. Adding quotes 
around the variables in those lines makes the error go away. This error totally 
prevents logging into X. It happens when using LXDM to start Xfce, because LXDM 
sets DESKTOP_SESSION to Name from /usr/share/xsessions/xfce.desktop :
  Name=Xfce Session

  These LXDM bugs relate to the problem, but I guess the lack of quoting
  here is the root cause. I'm not sure if setting DESKTOP_SESSION to the
  Name from the .desktop file and having a space in it is wise, but
  everything seems to work after fixing the quoting. Proper quoting is
  used elsewhere.

  https://sourceforge.net/p/lxde/bugs/420/

  https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/875991

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gconf2-common 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun  2 10:16:46 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

I did not install the image, just ran it from the USB stick.

By default, it does not not have a login screen, since there is a single
user, I believe.

I added a second user, and logged in to that user, which was successful.

But this may be different from what I see on my long-installed system.

Does the default use lightdm?

I didn't check.

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  WORKAROUND: Use GNOME Flashback (Metacity).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Finally getting back to this.

My notes on setting enable_rc6 aren't very good.

I may have started using it as a possible way to extend battery life, as
mentioned here.

I don't notice a difference now that I have removed it.

https://askubuntu.com/questions/93654/why-does-my-computer-get-less-
battery-life-with-ubuntu-compared-to-windows#38194

I tried the cdimage mentioned above, and it works.

What does that ultimately suggest?

I didn't have a login screen for the cdimage, of course.

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  WORKAROUND: Use GNOME Flashback (Metacity).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Thanks for your suggestions.

I just installed:
gnome-session-flashback

Working:
Gnome Flashback (Metacity)

not working:
Gnome Flashback (Compiz)


And a new item in /var/crash:

** Attachment added: 
"/var/crash/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144845/+files/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Since filing this bug, I have been successfully using lxdm as a worked
around, with lxde

Recently, after I open this bug, I built my own version of

xserver-xorg-input-synaptics

following the instructions here:
https://askubuntu.com/questions/462135/touchpad-issue-jumping-cursor-while-typing-ubuntu-14-04-syndaemon-dont-help

That solved the problem with using the touchpad, but did not affect
lightdm.

I have some other programs I built myself, digikam, for example.
I suspect that none of the others are at fault, but I'm not positive.

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Since filing this bug, I have been successfully using lxdm as a worked
around, with lxde

Recently, after I open this bug, I built my own version of

xserver-xorg-input-synaptics

following the instructions here:
https://askubuntu.com/questions/462135/touchpad-issue-jumping-cursor-while-typing-ubuntu-14-04-syndaemon-dont-help

That solved the problem with using the touchpad, but did not affect
lightdm.

I have some other programs I built myself, digikam, for example.
I suspect that none of the others are at fault, but I'm not positive.

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_xfce4-power-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144822/+files/_usr_bin_xfce4-power-manager.1000.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_plasmashell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144821/+files/_usr_bin_plasmashell.1000.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_sbin_unity-greeter.119.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144823/+files/_usr_sbin_unity-greeter.119.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_kwin_wayland.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144820/+files/_usr_bin_kwin_wayland.1000.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

After removing:

i915.i915_enable_rc6=1

I still have problems.

I'll attach a few files from /var/crash


** Attachment added: "From /var/crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144819/+files/_usr_bin_ksplashqml.1000.crash

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

** Attachment added: "Results of systemctl status lightdm"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1771232/+attachment/5139562/+files/lightdm-status

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

I commented out pam_kwallet.so in /etc/pam.d/
lightdm and lightdm-greeter

since this shared library does not exist, and I received warning
messages about it.

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1771232] [NEW] Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

Public bug reported:

Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
have been able to use lxdm, somewhat, if I use LXDE.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon May 14 17:06:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (1092 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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


** Tags: amd64 apport-bug bionic

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1770306] [NEW] X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Public bug reported:

I can manually start lightdm, and that will give me a login screen,

Unfortunately, most of the desktop environments crash after login.

Only plasma gives me a little bit of clients, though even plasma
complains

All shell packages missing
And
Vboxclient warning

Under 17.10, I successfully used Wayland

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Wed May  9 19:15:12 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 5500 [1028:0665]
InstallationDate: Installed on 2015-05-18 (1087 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. XPS 13 9343
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash 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/1770306

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1620774] [NEW] lxc container does not start: cgroupfs failed to detect cgroup metadata

[Kevin Dalley]

Public bug reported:

lxc container failed to start until after I installed cgroupfs-mount

After a recent upgrade, I received the following error messages when
start an lxc container:

kevin@awabi:~$ sudo lxc-start -F -n escale_build
lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup 
metadata
lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support
  
lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build'
  lxc-start: 
tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained 
by setting the --logfile and --logpriority options.


aptitude install cgroupfs-mount

Then I could successful start my container.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep  6 11:26:12 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (477 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  lxc container does not start: cgroupfs failed to detect cgroup
  metadata

Status in lxc package in Ubuntu:
  New

Bug description:
  lxc container failed to start until after I installed cgroupfs-mount

  After a recent upgrade, I received the following error messages when
  start an lxc container:

  kevin@awabi:~$ sudo lxc-start -F -n escale_build
  lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup 
metadata
  lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support

lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build'
lxc-start: 
tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  
  aptitude install cgroupfs-mount

  Then I could successful start my container.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:26:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (477 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1598505] [NEW] adb usage has typo disabled => disabled

[Kevin Dalley]

Public bug reported:

type "adb shell help"

get the following output, include "disbled" below

Please correct disbled to disabled

pm list packages: prints all packages, optionally only
  those whose package name contains the text in FILTER.  Options:
-f: see their associated file.
-d: filter to only show disbled packages.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: android-tools-adb 5.1.1r36+git20160322-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul  2 09:59:40 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (411 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: android-tools
UpgradeStatus: Upgraded to xenial on 2016-05-30 (32 days ago)

** Affects: android-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  adb usage has typo disabled => disabled

Status in android-tools package in Ubuntu:
  New

Bug description:
  type "adb shell help"

  get the following output, include "disbled" below

  Please correct disbled to disabled

  pm list packages: prints all packages, optionally only
those whose package name contains the text in FILTER.  Options:
  -f: see their associated file.
  -d: filter to only show disbled packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: android-tools-adb 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul  2 09:59:40 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (411 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (32 days ago)

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

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

[Touch-packages] [Bug 1598459] [NEW] adb man page has incorrect link

[Kevin Dalley]

Public bug reported:

The man page for adb has the following link:

http://developer.android.com/guide/developing/tools/adb.html

This link no longer exists

The following link is a better link:

https://developer.android.com/studio/command-line/adb.html

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: android-tools-adb 5.1.1r36+git20160322-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul  2 09:08:06 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (411 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: android-tools
UpgradeStatus: Upgraded to xenial on 2016-05-30 (32 days ago)

** Affects: android-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  adb man page has incorrect link

Status in android-tools package in Ubuntu:
  New

Bug description:
  The man page for adb has the following link:

  http://developer.android.com/guide/developing/tools/adb.html

  This link no longer exists

  The following link is a better link:

  https://developer.android.com/studio/command-line/adb.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: android-tools-adb 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul  2 09:08:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (411 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (32 days ago)

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

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

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

[Kevin Dalley]

** Attachment added: "dmesg_boot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690364/+files/dmesg_boot

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

Title:
  Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

[Kevin Dalley]

** Attachment added: "List of devices"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690363/+files/devices

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

Title:
  Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

[Kevin Dalley]

** Attachment added: "New dmesg entries"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690365/+files/dmesg_diff

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

Title:
  Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

[Kevin Dalley]

** Attachment added: "Full  Xorg.0"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690362/+files/Xorg.0.log_tmp

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

Title:
  Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1596248] [NEW] Touchpad stops working occasionally

[Kevin Dalley]

Public bug reported:

Occasionally, my cursor stops following my mouse movements.

I followed instructions described here:

https://wiki.ubuntu.com/DebuggingTouchpadDetection

If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in the 
kernel itself and you should follow these steps:
Provide the general information.

Directly after logging in to GNOME, KDE, or Xfce open a terminal and
enter the following commands:

cat /proc/bus/input/devices > ~/devices
dmesg > ~/dmesg_boot
cp /var/log/Xorg.0.log ~/Xorg.0.log 
Wait until your touchpad stops working.
Open a Virtual Terminal by pressing Ctrl-Alt-F1.
Enter the following commands:

LANG=C
dmesg > ~/dmesg
diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 25 17:57:40 2016
DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
InstallationDate: Installed on 2015-05-18 (404 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
LightdmLog:
 [+7057.65s] DEBUG: Seat seat0 changes active session to 
 [+7063.85s] DEBUG: Seat seat0 changes active session to 40
 [+7145.78s] DEBUG: Seat seat0 changes active session to c7
 [+7145.78s] DEBUG: Session c7 is already active
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


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

** Attachment added: "Xorg.0 updates up until problem"
   
https://bugs.launchpad.net/bugs/1596248/+attachment/4690340/+files/Xorg.0.log_diff

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

Title:
  Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing 

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

I suggest that README.Debian (or Ubuntu) mention the workarounds
regarding bind9 and ipv6.

It might save some time in debugging lxc problems.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

What I should do is try to back out some of my changes and determine
whether I can duplicate the problem.

Then I can determine which changes matter and which ones don't.

I won't have time for a few days, but I will do my best.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

And suddenly, it has started working.

I don't know why.

I did a reboot
sudo systemctl status lxc-net


The above command suddenly had results which looked familiar, in a good way.

Before this, I had unsuccessfully tried a few of the sample lxc.

Perhaps I updated something which fixed the problems.

Thanks for your help.

I wish I knew exactly what I did.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

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

I had missed restart lxc-net.

Unfortunately, that didn't make any difference.

kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log 
--logpriority 3 -F
lxc-start: conf.c: instantiate_veth: 2621 failed to attach 'vethKW0GNU' to the 
bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: lxc_create_network: 2904 failed to create netdev
lxc-start: start.c: lxc_spawn: 920 failed to create the network
lxc-start: start.c: __lxc_start: 1172 failed to spawn 'escale_build'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

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

Thanks for your help.

Unfortunately, I didn't have any luck with this either.

I added

listen-on { ! 10.0.3.1; };


just before the final "}" line.
restarted bind9, and I have the same error message.

Perhaps I'm missing something.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

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

I have now added

listen-on-v6 { none; };
restarted bind9, and again nothing:

kevin@awabi:~/src$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log 
--logpriority 3 -Flxc-start: conf.c: instantiate_veth: 2621 failed to attach 
'vethQCSVBP' to the bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: lxc_create_network: 2904 failed to create netdev
lxc-start: start.c: lxc_spawn: 920 failed to create the network
lxc-start: start.c: __lxc_start: 1172 failed to spawn 'escale_build'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.


I don't desparately need bind9, if that is really the problem.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

kevin@awabi:~/notes/security$  sudo netstat -lap| grep LISTEN
[sudo] password for kevin: 
tcp0  0 usscc-mvetter.co:domain *:* LISTEN  
1192/named  
tcp0  0 192.168.43.174:domain   *:* LISTEN  
1192/named  
tcp0  0 192.168.122.1:domain*:* LISTEN  
32446/dnsmasq   
tcp0  0 awabi:domain*:* LISTEN  
3337/dnsmasq
tcp0  0 localhost:domain*:* LISTEN  
1192/named  
tcp0  0 *:ssh   *:* LISTEN  
1198/sshd   
tcp0  0 localhost:ipp   *:* LISTEN  
4504/cupsd  
tcp0  0 localhost:postgresql*:* LISTEN  
1188/postgres   
tcp0  0 localhost:afs3-callback *:* LISTEN  
10935/nxnode.bin
tcp0  0 *:4505  *:* LISTEN  
2455/python 
tcp0  0 localhost:953   *:* LISTEN  
1192/named  
tcp0  0 *:4506  *:* LISTEN  
2533/python 
tcp0  0 *:db-lsp*:* LISTEN  
10312/dropbox   
tcp0  0 *:iscsi-target  *:* LISTEN  
1211/tgtd   
tcp0  0 *:35357 *:* LISTEN  
4300/python 
tcp0  0 *:microsoft-ds  *:* LISTEN  
2963/smbd   
tcp0  0 *:19455 *:* LISTEN  
16987/cli   
tcp0  0 localhost:17600 *:* LISTEN  
10312/dropbox   
tcp0  0 *:4000  *:* LISTEN  
3558/nxd
tcp0  0 localhost:12001 *:* LISTEN  
10935/nxnode.bin
tcp0  0 *:zabbix-agent  *:* LISTEN  
4572/zabbix_agentd
tcp0  0 localhost:20130 *:* LISTEN  
2794/nxserver.bin
tcp0  0 localhost:17603 *:* LISTEN  
10312/dropbox   
tcp0  0 localhost:gpsd  *:* LISTEN  
1/init  
tcp0  0 *:5000  *:* LISTEN  
4300/python 
tcp0  0 *:25672 *:* LISTEN  
1237/beam.smp   
tcp0  0 *:8200  *:* LISTEN  
2356/minidlnad  
tcp0  0 localhost:25001 *:* LISTEN  
11005/nxclient.bin
tcp0  0 localhost:27017 *:* LISTEN  
991/mongod  
tcp0  0 localhost:mysql *:* LISTEN  
2078/mysqld 
tcp0  0 *:netbios-ssn   *:* LISTEN  
2963/smbd   
tcp0  0 localhost:45708 *:* LISTEN  
16987/cli   
tcp6   0  0 [::]:epmd   [::]:*  LISTEN  
1541/epmd   
tcp6   0  0 [::]:4242   [::]:*  LISTEN  
2618/java   
tcp6   0  0 localhost:4243  [::]:*  LISTEN  
2618/java   
tcp6   0  0 [::]:domain [::]:*  LISTEN  
1192/named  
tcp6   0  0 [::]:ssh[::]:*  LISTEN  
1198/sshd   
tcp6   0  0 ip6-localhost:ipp   [::]:*  LISTEN  
4504/cupsd  
tcp6   0  0 [::]:3128   [::]:*  LISTEN  
2490/(squid-1)  
getnameinfo failed
tcp6   0  0 ip6-local:afs3-callback [::]:*  LISTEN  
10935/nxnode.bin
tcp6   0  0 ip6-localhost:953   [::]:*  LISTEN  
1192/named  
tcp6   0  0 [::]:iscsi-target   [::]:*  LISTEN  
1211/tgtd   
tcp6   0  0 [::]:microsoft-ds   [::]:*  LISTEN  
2963/smbd   
tcp6   0  0 [::]:4000   [::]:*  LISTEN  
3558/nxd
tcp6   0  0 [::]:8000   [::]:*  LISTEN  
2314/(squid-1)  
tcp6   0  0 [::]:zabbix-agent   [::]:*  LISTEN  
4572/zabbix_agentd
tcp6   0  0 ip6-localhost:gpsd  [::]:*  LISTEN  
1/init  
tcp6   0  0 [::]:amqp   [::]:*  LISTEN  
1237/beam.smp   
tcp6   0  0 [::]:netbios-ssn[::]:*  LISTEN  
2963/smbd   
unix  2  [ ACC ] STREAM LISTENING 5093748  14560/dbus-daemon   

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

Thanks again.

kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start

dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign 
requested address
Failed to setup lxc-net.
kevin@awabi:~/tmp$ sudo brctl show
bridge name bridge id   STP enabled interfaces
virbr0  8000.52540063031d   yes virbr0-nic

No luck with starting it.

Here is /etc/default/lxc-net

# This file is auto-generated by lxc.postinst if it does not
# exist.  Customizations will not be overridden.
# Leave USE_LXC_BRIDGE as "true" if you want to use lxcbr0 for your
# containers.  Set to "false" if you'll use virbr0 or another existing
# bridge, or mavlan to your host's NIC.
USE_LXC_BRIDGE="true"
# USE_LXC_BRIDGE="false"

# If you change the LXC_BRIDGE to something other than lxcbr0, then
# you will also need to update your /etc/lxc/default.conf as well as the
# configuration (/var/lib/lxc//config) for any containers
# already created using the default config to reflect the new bridge
# name.
# If you have the dnsmasq daemon installed, you'll also have to update
# /etc/dnsmasq.d/lxc and restart the system wide dnsmasq daemon.
LXC_BRIDGE="lxcbr0"
LXC_ADDR="10.0.3.1"
LXC_NETMASK="255.255.255.0"
LXC_NETWORK="10.0.3.0/24"
LXC_DHCP_RANGE="10.0.3.2,10.0.3.254"
LXC_DHCP_MAX="253"
# Uncomment the next line if you'd like to use a conf-file for the lxcbr0
# dnsmasq.  For instance, you can use 'dhcp-host=mail1,10.0.3.100' to have
# container 'mail1' always get ip address 10.0.3.100.
#LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf

# Uncomment the next line if you want lxcbr0's dnsmasq to resolve the .lxc
# domain.  You can then add "server=/lxc/10.0.3.1' (or your actual )
# to /etc/dnsmasq.conf, after which 'container1.lxc' will resolve on your
# host.
#LXC_DOMAIN="lxc"

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

Thanks.

kevin@awabi:~$ sudo brctl show
bridge name bridge id   STP enabled interfaces
virbr0  8000.52540063031d   yes virbr0-nic
kevin@awabi:~$ sudo ifconfig -a
loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:410820 errors:0 dropped:0 overruns:0 frame:0
  TX packets:410820 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:43000462 (43.0 MB)  TX bytes:43000462 (43.0 MB)

virbr0Link encap:Ethernet  HWaddr 52:54:00:63:03:1d  
  inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

virbr0-nic Link encap:Ethernet  HWaddr 52:54:00:63:03:1d  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:500 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet  HWaddr 34:68:95:ee:9f:bb  
  inet addr:10.23.28.210  Bcast:10.23.28.255  Mask:255.255.255.0
  inet6 addr: fdca:f995:220a:8005:3668:95ff:feee:9fbb/64 Scope:Global
  inet6 addr: fe80::3668:95ff:feee:9fbb/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1280  Metric:1
  RX packets:8661210 errors:0 dropped:0 overruns:0 frame:5987785
  TX packets:13518413 errors:10494 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:4112935761 (4.1 GB)  TX bytes:1210222618 (1.2 GB)
  Interrupt:19 

kevin@awabi:~$ sudo journalctl -u lxc-net
-- No entries --
kevin@awabi:~$ sudo systemd-detect-virt
none

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

Thanks.

kevin@awabi:~$ sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
  lxc-start 1446650865.960 INFO lxc_start_ui - lxc_start.c:main:264 - 
using rcfile /var/lib/lxc/escale_build/config
  lxc-start 1446650865.961 WARN lxc_confile - 
confile.c:config_pivotdir:1801 - lxc.pivotdir is ignored.  It will soon become 
an error.
  lxc-start 1446650865.961 WARN lxc_cgmanager - cgmanager.c:cgm_get:993 
- do_cgm_get exited with error
  lxc-start 1446650865.961 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM 
security driver AppArmor
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for reject_force_umount 
action 0
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for reject_force_umount 
action 0
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .[all].
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .kexec_load errno 1.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for kexec_load action 327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for kexec_load action 327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .open_by_handle_at errno 1.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for open_by_handle_at action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for open_by_handle_at action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .init_module errno 1.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for init_module action 327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for init_module action 327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .finit_module errno 1.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for finit_module action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for finit_module action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:324 - processing: .delete_module errno 1.
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:426 - Adding native rule for delete_module action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:429 - Adding compat rule for delete_module action 
327681
  lxc-start 1446650865.961 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:436 - Merging in the compat seccomp ctx into the main 
one
  lxc-start 1446650865.962 DEBUGlxc_start - start.c:setup_signal_fd:262 
- sigchild handler set
  lxc-start 1446650865.962 DEBUGlxc_console - 
console.c:lxc_console_peer_default:500 - opening /dev/tty for console peer
  lxc-start 1446650865.962 DEBUGlxc_console - 
console.c:lxc_console_peer_default:506 - using '/dev/tty' as console
  lxc-start 1446650865.962 DEBUGlxc_console - 
console.c:lxc_console_sigwinch_init:179 - 12835 got SIGWINCH fd 9
  lxc-start 1446650865.962 DEBUGlxc_console - 
console.c:lxc_console_winsz:88 - set winsz dstfd:6 cols:80 rows:24
  lxc-start 1446650865.962 INFO lxc_start - start.c:lxc_init:454 - 
'escale_build' is initialized
  lxc-start 1446650865.963 DEBUGlxc_start - start.c:__lxc_start:1145 - 
Not dropping cap_sys_boot or watching utmp
  lxc-start 1446650865.968 ERRORlxc_conf - conf.c:instantiate_veth:2621 
- failed to attach 'vethIY9I09' to the bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: instantiate_veth: 2621 failed to attach 'vethIY9I09' to the 
bridge 'lxcbr0': Operation not permitted
  lxc-start 1446650865.998 ERRORlxc_conf - 
conf.c:lxc_create_network:2904 - failed to create netdev
lxc-start: conf.c: lxc_create_network: 2904 failed to create netdev
  lxc-start 1446650865.998 ERRORlxc_start - start.c:lxc_spawn:920 - 
failed to create the network
lxc-start: start.c: lxc_spawn: 920 failed to create the network
 

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

Host is:

Linux awabi 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux


container is:

Linux escalebuild 3.16.0-51-generic #69~14.04.1-Ubuntu SMP Wed Oct 7
15:32:41 UTC 2015 x86_64 GNU/Linux

here is output from my attempt to start:

kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log 
--logpriority 3
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.
kevin@awabi:~$ less /tmp/lxc-log 
kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log 
--logpriority 3 -F
lxc-start: conf.c: instantiate_veth: 2621 failed to attach 'vethJ6CTXM' to the 
bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: lxc_create_network: 2904 failed to create netdev
lxc-start: start.c: lxc_spawn: 920 failed to create the network
lxc-start: start.c: __lxc_start: 1172 failed to spawn 'escale_build'
lxc-start: lxc_start.c: main: 344 The container failed to start.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

I upgraded to Wiley, and the problem has shown up again. I haven't
managed to fix it yet under Wiley, though I could fix it under Vivid

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
 CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
 ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1109 lockfile-touch /var/lock/ntpdate-ifup
 ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
 ├─1128 lockfile-create /var/lock/ntpdate-ifup
 └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  ...
  inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

[Kevin Dalley]

And, so far, these steps are needed each time I reboot. 2 reboots after
initial success.

As you suggested, stopping and restarting the lxc-net systemd job is
necessary. Just starting it does not work.

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

Title:
  container does not receive IP address after 15.04 upgrade

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Perhaps this is an upgrade issue, perhaps it is a installation issue.

  In either case, there should be more information about upgrading lxc.

  After upgrading to Ubuntu 15.04, my container no longer started.

  After upgrading, I had to remove the following line from the config
  file for my container:

  lxc.network.link = lxcbr0

  Here is the attempt at starting before commenting out the line:

  kevin@nereocystis:~$ sudo  lxc-start -F -n escale_build
  lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to 
the bridge 'lxcbr0': Operation not permitted
  lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev
  lxc-start: start.c: lxc_spawn: 914 failed to create the network
  lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build'
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  After commenting out this line, the container starts, but no IP address is 
assigned in the container.

  But no IP address was assigned:

  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/9a:9b:92:81:87:62
  Sending on   LPF/eth0/9a:9b:92:81:87:62
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.
  done.

  
  Eventually, I purged lxc, and reinstalled it, with the same results.

  I also tried creating a new container from scratch using the
  instructions in:

  https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network

  sudo lxc-create --template download --name u1

  Again, no IP address.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  3 10:44:23 2015
  InstallationDate: Installed on 2013-06-02 (699 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  KernLog:
   [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED 
operation=mount info=failed flags match error=-13 
profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, 
remount, relatime
   [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd 
flags=ro, nosuid, nodev, noexec, remount, strictatime
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

[Kevin Dalley]

Thanks. That works.

Stopping and starting systemtl once fixed the problem.

I did have some issues with the upgrade in general, and discovered a
memory problem. Bad memory is now gone.

Perhaps that was responsible for some of the problem. Perhaps not.

I expected that reinstalling lxc with good memory should have fixed any
problem caused by bad memory.

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

Title:
  container does not receive IP address after 15.04 upgrade

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Perhaps this is an upgrade issue, perhaps it is a installation issue.

  In either case, there should be more information about upgrading lxc.

  After upgrading to Ubuntu 15.04, my container no longer started.

  After upgrading, I had to remove the following line from the config
  file for my container:

  lxc.network.link = lxcbr0

  Here is the attempt at starting before commenting out the line:

  kevin@nereocystis:~$ sudo  lxc-start -F -n escale_build
  lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to 
the bridge 'lxcbr0': Operation not permitted
  lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev
  lxc-start: start.c: lxc_spawn: 914 failed to create the network
  lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build'
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  After commenting out this line, the container starts, but no IP address is 
assigned in the container.

  But no IP address was assigned:

  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/9a:9b:92:81:87:62
  Sending on   LPF/eth0/9a:9b:92:81:87:62
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.
  done.

  
  Eventually, I purged lxc, and reinstalled it, with the same results.

  I also tried creating a new container from scratch using the
  instructions in:

  https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network

  sudo lxc-create --template download --name u1

  Again, no IP address.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  3 10:44:23 2015
  InstallationDate: Installed on 2013-06-02 (699 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  KernLog:
   [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED 
operation=mount info=failed flags match error=-13 
profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, 
remount, relatime
   [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd 
flags=ro, nosuid, nodev, noexec, remount, strictatime
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

[Kevin Dalley]

Thanks.

No sign of lxcbr0.

kevin@nereocystis:/home/kevin$ ps -ef | grep lxcbr0
kevin17684 17583  0 13:06 pts/000:00:00 grep lxcbr0


I attached the original config file which does not work under 15.04, but did 
work under 14.10 and 14.04.


** Attachment added: Original config which does not work under 15.04
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1451232/+attachment/4390854/+files/config

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

Title:
  container does not receive IP address after 15.04 upgrade

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Perhaps this is an upgrade issue, perhaps it is a installation issue.

  In either case, there should be more information about upgrading lxc.

  After upgrading to Ubuntu 15.04, my container no longer started.

  After upgrading, I had to remove the following line from the config
  file for my container:

  lxc.network.link = lxcbr0

  Here is the attempt at starting before commenting out the line:

  kevin@nereocystis:~$ sudo  lxc-start -F -n escale_build
  lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to 
the bridge 'lxcbr0': Operation not permitted
  lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev
  lxc-start: start.c: lxc_spawn: 914 failed to create the network
  lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build'
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  After commenting out this line, the container starts, but no IP address is 
assigned in the container.

  But no IP address was assigned:

  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/9a:9b:92:81:87:62
  Sending on   LPF/eth0/9a:9b:92:81:87:62
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.
  done.

  
  Eventually, I purged lxc, and reinstalled it, with the same results.

  I also tried creating a new container from scratch using the
  instructions in:

  https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network

  sudo lxc-create --template download --name u1

  Again, no IP address.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  3 10:44:23 2015
  InstallationDate: Installed on 2013-06-02 (699 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  KernLog:
   [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED 
operation=mount info=failed flags match error=-13 
profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, 
remount, relatime
   [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd 
flags=ro, nosuid, nodev, noexec, remount, strictatime
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1451232] [NEW] container does not receive IP address after 15.04 upgrade

[Kevin Dalley]

Public bug reported:

Perhaps this is an upgrade issue, perhaps it is a installation issue.

In either case, there should be more information about upgrading lxc.

After upgrading to Ubuntu 15.04, my container no longer started.

After upgrading, I had to remove the following line from the config file
for my container:

lxc.network.link = lxcbr0

Here is the attempt at starting before commenting out the line:

kevin@nereocystis:~$ sudo  lxc-start -F -n escale_build
lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to the 
bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev
lxc-start: start.c: lxc_spawn: 914 failed to create the network
lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.


After commenting out this line, the container starts, but no IP address is 
assigned in the container.

But no IP address was assigned:

For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/9a:9b:92:81:87:62
Sending on   LPF/eth0/9a:9b:92:81:87:62
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.


Eventually, I purged lxc, and reinstalled it, with the same results.

I also tried creating a new container from scratch using the
instructions in:

https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network

sudo lxc-create --template download --name u1

Again, no IP address.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun May  3 10:44:23 2015
InstallationDate: Installed on 2013-06-02 (699 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
KernLog:
 [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED 
operation=mount info=failed flags match error=-13 
profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, 
remount, relatime
 [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd 
flags=ro, nosuid, nodev, noexec, remount, strictatime
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug vivid

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

Title:
  container does not receive IP address after 15.04 upgrade

Status in lxc package in Ubuntu:
  New

Bug description:
  Perhaps this is an upgrade issue, perhaps it is a installation issue.

  In either case, there should be more information about upgrading lxc.

  After upgrading to Ubuntu 15.04, my container no longer started.

  After upgrading, I had to remove the following line from the config
  file for my container:

  lxc.network.link = lxcbr0

  Here is the attempt at starting before commenting out the line:

  kevin@nereocystis:~$ sudo  lxc-start -F -n escale_build
  lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to 
the bridge 'lxcbr0': Operation not permitted
  lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev
  lxc-start: start.c: lxc_spawn: 914 failed to create the network
  lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build'
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  After commenting out this line, the container starts, but no IP address is 
assigned in the container.

  But no IP address was assigned:

  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/9a:9b:92:81:87:62
  Sending on   LPF/eth0/9a:9b:92:81:87:62
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
  DHCPDISCOVER on eth0 to