[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Phill Kelley]

I am also seeing this same problem on a Raspberry Pi4 4GB.

I purchased the Pi last November and installed from the then-available
2019-09-26-raspbian-buster.zip but routinely keep it updated (apt update
/ apt upgrade).

The Pi was rock solid and did not exhibit any problems until 2020-02-24
when I applied some updates followed by a "sudo reboot" but the boot
process did not complete. The Pi runs headless so I don't know whether
it never actually completed the shutdown, or failed to reboot. I power-
cycled the device and it came back OK.

Another set of updates were applied on 2020-03-11 and the subsequent
reboot completed without incident so I assumed the earlier problem was a
one-off.

Then, on 2020-03-14 the Pi froze. Wouldn't respond to pings, ssh or vnc.
It is Ethernet-connected but the WiFi interface is active and it did not
occur to me to try connecting via WiFi. I just did another power-cycle
and then started nosing around through the logs. Which brought me to:

Mar 14 12:48:16 iot-hub avahi-daemon[361]: Withdrawing address record for 
192.168.132.60 on eth0.
Mar 14 12:48:16 iot-hub avahi-daemon[361]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.132.60.
Mar 14 12:48:16 iot-hub avahi-daemon[361]: Interface eth0.IPv4 no longer 
relevant for mDNS.

and, from there, to this post.

The main reasons I'm adding a comment to this post are (a) as a "me too"
as of March 2020, and (b) in case the pattern of the RPi being perfectly
OK until 2020-02-24 causes someone to say "ahah!"

The updates in question were (from the history log): Upgrade:
libpython3.7-minimal:armhf (3.7.3-2, 3.7.3-2+deb10u1), libraspberrypi-
bin:armhf (1.20200114-1, 1.20200212-1), libopenjp2-7:armhf (2.3.0-2,
2.3.0-2+deb10u1), rc-gui:armhf (1.34, 1.36), libcom-err2:armhf
(1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libcups2:armhf (2.2.10-6+deb10u1,
2.2.10-6+deb10u2), libraspberrypi-dev:armhf (1.20200114-1,
1.20200212-1), libraspberrypi-doc:armhf (1.20200114-1, 1.20200212-1),
python3.7-venv:armhf (3.7.3-2, 3.7.3-2+deb10u1), raspberrypi-ui-
mods:armhf (1.20200127, 1.20200218), qt5-gtk-platformtheme:armhf
(5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm4:armhf
(1.3.1-1+rpt12, 1.3.1-1+rpt13), libsystemd0:armhf (241-7~deb10u2+rpi1,
241-7~deb10u3+rpi1), raspi-config:armhf (20200205, 20200207), libfm-
modules:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), libfm-extra4:armhf
(1.3.1-1+rpt12, 1.3.1-1+rpt13), mariadb-common:armhf
(1:10.3.17-0+deb10u1, 1:10.3.22-0+deb10u1), binutils:armhf
(2.31.1-16+rpi1, 2.31.1-16+rpi2), e2fsprogs:armhf (1.44.5-1+deb10u2,
1.44.5-1+deb10u3), sudo:armhf (1.8.27-1+deb10u1, 1.8.27-1+deb10u2),
libqt5dbus5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3),
libqt5sql5-sqlite:armhf (5.11.3+dfsg1-1+rpi1,
5.11.3+dfsg1-1+rpi1+deb10u3), python3-pil:armhf (5.4.1-2,
5.4.1-2+deb10u1), libpython3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1),
python3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1), openssh-sftp-server:armhf
(1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libqt5widgets5:armhf
(5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm-gtk4:armhf
(1.3.1-1+rpt12, 1.3.1-1+rpt13), udev:armhf (241-7~deb10u2+rpi1,
241-7~deb10u3+rpi1), python3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1),
binutils-arm-linux-gnueabihf:armhf (2.31.1-16+rpi1, 2.31.1-16+rpi2),
libpython3.7-stdlib:armhf (3.7.3-2, 3.7.3-2+deb10u1), libudev1:armhf
(241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), python3.7-minimal:armhf
(3.7.3-2, 3.7.3-2+deb10u1), libqt5xml5:armhf (5.11.3+dfsg1-1+rpi1,
5.11.3+dfsg1-1+rpi1+deb10u3), libqt5printsupport5:armhf
(5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), raspberrypi-
kernel:armhf (1.20200114-1, 1.20200212-1), libss2:armhf
(1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libqt5concurrent5:armhf
(5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libext2fs2:armhf
(1.44.5-1+deb10u2, 1.44.5-1+deb10u3), raspberrypi-bootloader:armhf
(1.20200114-1, 1.20200212-1), libexif12:armhf (0.6.21-5.1,
0.6.21-5.1+deb10u1), libqt5gui5:armhf (5.11.3+dfsg1-1+rpi1,
5.11.3+dfsg1-1+rpi1+deb10u3), libimobiledevice6:armhf
(1.2.1~git20181030.92c5462-1, 1.2.1~git20181030.92c5462-2), gldriver-
test:armhf (0.4, 0.5), ssh:armhf (1:7.9p1-10+deb10u1,
1:7.9p1-10+deb10u2), systemd-sysv:armhf (241-7~deb10u2+rpi1,
241-7~deb10u3+rpi1), guile-2.2-libs:armhf (2.2.4+1-2,
2.2.4+1-2+deb10u1), realvnc-vnc-server:armhf (6.6.0.41949, 6.7.1.42348),
libpython3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1), libpam-systemd:armhf
(241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), libmatroska6v5:armhf (1.4.9-1,
1.4.9-1+deb10u1), systemd:armhf (241-7~deb10u2+rpi1,
241-7~deb10u3+rpi1), libwebkit2gtk-4.0-37:armhf (2.26.3-1~deb10u1+rpi1,
2.26.4-1~deb10u1+rpi1), libqt5core5a:armhf (5.11.3+dfsg1-1+rpi1,
5.11.3+dfsg1-1+rpi1+deb10u3), piwiz:armhf (0.8, 0.9),
libraspberrypi0:armhf (1.20200114-1, 1.20200212-1), openssh-server:armhf
(1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), openssh-client:armhf
(1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libmysofa0:armhf (0.6~dfsg0-3,
0.6~dfsg0-3+deb10u1), rpi-chromium-mods:armhf 

[Touch-packages] [Bug 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

[Phill]

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

Although the buttons are integral to the touchpad, they are clearly
marked with a dividing line. Having read the proposed duplicate, while
this issue may have the same underlying cause, this is not a mere
configuration preference on this device because it has clearly
identified buttons, albeit with nothing more than a coloured dividing
line.

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  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/1773516/+subscriptions

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

[Touch-packages] [Bug 1773516] [NEW] Right click not working on Lenovo touchpad

[Phill]

Public bug reported:

The right click is not working on Lenovo Yoga touch pad after upgrade to
18.04, worked minutes before on 17.10.

I think it works on the Think Pad out-of-the-box (after upgrade from
17.10), if that helps.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat May 26 10:34:57 2018
DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
InstallationDate: Installed on 2018-01-18 (128 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 80M0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C0CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Mini
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J33995WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 300-11IBY
dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
dmi.product.family: IDEAPAD
dmi.product.name: 80M0
dmi.product.version: Lenovo YOGA 300-11IBY
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
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 N/A
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 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/1773516

Title:
  Right click not working on Lenovo touchpad

Status in xorg package in Ubuntu:
  New

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 

[Touch-packages] [Bug 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV

[Phill]

Sorry, I commented on the wrong bug, I think #1665643 may be a duplicate
or dependency on this.

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

Title:
  python-crypto throws exception ValueError: CTR mode needs counter
  parameter, not IV

Status in OpenStack Charm Test Infra:
  Confirmed
Status in python-crypto package in Ubuntu:
  Fix Released

Bug description:
  We've recently upgraded python-crypto package on 14.04 due to this USN
  https://www.ubuntu.com/usn/usn-3199-1/

  
  apt history log

  ```
  Start-Date: 2017-02-16  23:43:48
  Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef dist-upgrade
  Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13)
  End-Date: 2017-02-16  23:43:52
  ```

  Then our python script which uses paramiko failed with this exception

  ```
  Traceback (most recent call last):
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1583, in run
  self.kex_engine.parse_next(ptype, m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 68, in parse_next
  return self._parse_kexdh_reply(m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 107, in _parse_kexdh_reply
  self.transport._activate_outbound()
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1881, in _activate_outbound
  engine = self._get_cipher(self.local_cipher, key_out, IV_out)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1500, in _get_cipher
  return self._cipher_info[name]['class'].new(key, 
self._cipher_info[name]['mode'], iv, counter)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in 
new
  return AESCipher(key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
  blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 
141, in __init__
  self._cipher = factory.new(key, *args, **kwargs)
  ValueError: CTR mode needs counter parameter, not IV

  ```

  packages versions

  ```
  pycrypto==2.6.1
  paramiko==1.12.0
  ```

  which works okay BEFORE the upgrade.

  Maybe Debian bug report: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=850025

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+subscriptions

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

[Touch-packages] [Bug 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV

[Phill]

Possible duplicate of #1665598 or maybe just a dependency, depends on
point of view.

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

Title:
  python-crypto throws exception ValueError: CTR mode needs counter
  parameter, not IV

Status in OpenStack Charm Test Infra:
  Confirmed
Status in python-crypto package in Ubuntu:
  Fix Released

Bug description:
  We've recently upgraded python-crypto package on 14.04 due to this USN
  https://www.ubuntu.com/usn/usn-3199-1/

  
  apt history log

  ```
  Start-Date: 2017-02-16  23:43:48
  Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef dist-upgrade
  Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13)
  End-Date: 2017-02-16  23:43:52
  ```

  Then our python script which uses paramiko failed with this exception

  ```
  Traceback (most recent call last):
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1583, in run
  self.kex_engine.parse_next(ptype, m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 68, in parse_next
  return self._parse_kexdh_reply(m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 107, in _parse_kexdh_reply
  self.transport._activate_outbound()
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1881, in _activate_outbound
  engine = self._get_cipher(self.local_cipher, key_out, IV_out)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1500, in _get_cipher
  return self._cipher_info[name]['class'].new(key, 
self._cipher_info[name]['mode'], iv, counter)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in 
new
  return AESCipher(key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
  blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 
141, in __init__
  self._cipher = factory.new(key, *args, **kwargs)
  ValueError: CTR mode needs counter parameter, not IV

  ```

  packages versions

  ```
  pycrypto==2.6.1
  paramiko==1.12.0
  ```

  which works okay BEFORE the upgrade.

  Maybe Debian bug report: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=850025

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+subscriptions

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Phill]

@auspex In my experience the physical act of bringing a computer out of
suspend takes longer than network manager takes to restart and reconnect
(well under 0.5 seconds). It's not only negligible, but I think it's
inevitable that there will be some latency in reconnecting after
suspend.

I have to agree with other comments supporting the restart workaround.
However, it's clear this issue is not going to see any action. Does
anyone know of a Debian that's not affected?

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 615239] Re: Every Wi-Fi disconnection is treated as an authentication error

[Phill]

There is a potential security issue here.

Whenever a legitimate program is seen asking for a password as the
result of an automatic operation people come to think of it as normal.
This undermines the suspicion that we would otherwise encourage in
people to help them avoid scams and malicious software.

A more serious security issue arises if you are using a normal user
account and the connection in question is shared. In this case you get a
second dialogue box asking for an administrator password for privilege
escalation. In this case we have users socially engineered to provide
privilege escalation to any user-space program that impersonates this
bug.

I think it would be preferable that it didn't ask for a password (even
if we know that's what's wrong) and just retried from time-to-time. If
the user wants to remedy the situation they can just go through what
they did first time they connected, at least then they expect to be
asked for a password so no harm is done.

Observations based on 16.04.

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

Title:
  Every Wi-Fi disconnection is treated as an authentication error

Status in Canonical System Image:
  Confirmed
Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I'm using lucid, with the 0.8-0ubuntu3, in a laptop, and is incredible that 
the nm-applet couldn't diagnostic why the wireless connection was lost and only 
trow the password prompt when I've lost the signal. nm-applet should see the 
kern.log or dmesg to react at signal lost. For example, when the kernel try 3 
times probe the AP and don't get response nm-applet say The pc are far away 
from the access point and can not be connected. Please, move close to the 
access point or try another more near. And by the way, when the authentication 
fails, or the association.
  --- 
  Architecture: i386
  CRDA: Error: [Errno 2] No existe el archivo o directorio
  CheckboxSubmission: ee8ebec101005ce57a9c3355b36ca8a7
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  DistroRelease: Ubuntu 10.04
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IpRoute:
   172.16.254.0/24 dev wlan1  proto kernel  scope link  src 172.16.254.5  
metric 2 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   default via 172.16.254.200 dev wlan1  proto static
  Keyfiles: Error: [Errno 2] No existe el archivo o directorio
  Package: network-manager 0.8-0ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_DO.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags: lucid
  Uname: Linux 2.6.32-24-generic i686
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/615239/+subscriptions

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

[Touch-packages] [Bug 1495063] Re: Networking occasionally doesn't recover from suspend

[Phill]

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

Not a duplicate of #1380480 as that bug report clearly states that
disabling and enabling networking in the applet restores the network.
This bug report clearly states that has been tried and does not work.

Note that since 16.04 I've been getting this on all computers that I
have and a lot more frequently. A separate bug has been raised for that
as it was a different operating system and affects different hardware.
See #1589125.

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

Title:
  Networking occasionally doesn't recover from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, networking is disabled upon recovery from suspend.
  Clicking "Enable Networking" on the menu from the notification icon
  has no effect. It requires network-manager to be restarted with
  `service network-manager restart`.

  I can't identify a pattern to the problem. I can suspend the computer
  for minutes or hours without it happening.

  I've not noticed it on other computers running 14.04 that I have, so
  it's probably limited to my this particular hardware.

  I didn't notice it on previous versions of Ubuntu on this hardware.
  However, due to the nature of the problem it will not be practical to
  bisect the kernel as I don't have a reliable method of reproducing the
  fault as of yet.

  My network devices are as follows (I use the wireless one only):

  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 02)
  Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 12 12:44:30 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-07-13 (60 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1  proto static 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   HTC Portable Hotspot DF99 b31b75bc-5b76-4592-9b4a-d9d860ea34aa   
802-11-wireless   1441832180   Wed 09 Sep 2015 21:56:20 BST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   TALKTALK-D069DC   700ea4cb-a660-479e-aa32-c00ad71e9064   
802-11-wireless   1442058263   Sat 12 Sep 2015 12:44:23 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1589125] Re: WiFi does not work after about 1 in 4 suspends

[Phill]

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

Probably not a duplicate of #1585863 because that bug says that the
network can be restored by performing `sudo wpa_cli scan`. I just tried
this and it does not work for me, only `sudo service network-manager
restart` seems to work as indicated in the bug description.

** Description changed:

  Steps: Suspend, wait, resume, a few times.
  
  The Network Manager applet shows WiFi is enabled and shows just one or a
  handful of WiFi names, they don't include some that are known to be
  available and in use on other computers.
  
  Disabling and enabling WiFi does not fix the problem.
  
  Disabling and enabling networking does not fix the problem.
  
  Adding the following does not help:
- /etc/pm/config.d/unload_modules 
+ /etc/pm/config.d/unload_modules
  SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"
+ 
+ Running `sudo wpa_cli scan` does not restore the network connection. I
+ only mention this because of a similar bug where this is an effective
+ workaround.
  
  Only workaround which works perfectly and instantly is to run:
  sudo service network-manager restart
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 18:18:50 2016
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2016-05-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
-  default via 192.168.43.1 dev wlp2s0  proto static  metric 600 
-  169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
-  192.168.43.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.43.89  
metric 600
+  default via 192.168.43.1 dev wlp2s0  proto static  metric 600
+  169.254.0.0/16 dev wlp2s0  scope link  metric 1000
+  192.168.43.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.43.89  
metric 600
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

-  wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
HTC Portable Hotspot DF99  c29b59ba-b6ef-49db-b159-75ec21d3f436  
/org/freedesktop/NetworkManager/ActiveConnection/0 
-  enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
-  lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
+  DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH
+  wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
HTC Portable Hotspot DF99  c29b59ba-b6ef-49db-b159-75ec21d3f436  
/org/freedesktop/NetworkManager/ActiveConnection/0
+  enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
+  lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

Title:
  WiFi does not work after about 1 in 4  suspends

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps: Suspend, wait, resume, a few times.

  The Network Manager applet shows WiFi is enabled and shows just one or
  a handful of WiFi names, they don't include some that are known to be
  available and in use on other computers.

  Disabling and enabling WiFi does not fix the problem.

  Disabling and enabling networking does not fix the problem.

  Adding the following does not help:
  /etc/pm/config.d/unload_modules
  SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"

  Running `sudo wpa_cli scan` does not restore the network connection. I
  only mention this because of a similar bug where this is an effective
  

[Touch-packages] [Bug 1589125] Re: WiFi does not work after about 1 in 4 suspends

[Phill]

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

Maybe not a duplicate of 1576747 as I have no network communication on
resume. The description of 1576747 states "Oddly enough, I'm still able
to communicate on the network that I was connected to prior to suspend".

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

Title:
  WiFi does not work after about 1 in 4  suspends

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps: Suspend, wait, resume, a few times.

  The Network Manager applet shows WiFi is enabled and shows just one or
  a handful of WiFi names, they don't include some that are known to be
  available and in use on other computers.

  Disabling and enabling WiFi does not fix the problem.

  Disabling and enabling networking does not fix the problem.

  Adding the following does not help:
  /etc/pm/config.d/unload_modules 
  SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"

  Only workaround which works perfectly and instantly is to run:
  sudo service network-manager restart

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 18:18:50 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.43.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.43.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.43.89  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
HTC Portable Hotspot DF99  c29b59ba-b6ef-49db-b159-75ec21d3f436  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1495063] Re: Networking occasionally doesn't recover from suspend

[Phill]

I have also confirmed this problem on a completely different computer,
it uses the ath9k driver:

$ lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated 
Graphics Controller (rev 03)
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio 
Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root 
Port 1
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI 
Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)
02:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a 
Controller (rev 70)

sudo lshw -C network
[sudo] password for phill: 
  *-network   
   description: Wireless interface
   product: AR9287 Wireless Network Adapter (PCI-Express)
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:01:00.0
   logical name: wlp1s0
   version: 01
   serial: 64:70:02:6e:fe:03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=ath9k driverversion=4.4.0-22-generic 
firmware=N/A ip=192.168.43.218 latency=0 link=yes multicast=yes wireless=IEEE 
802.11bgn
   resources: irq:16 memory:feaf-feaf

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

Title:
  Networking occasionally doesn't recover from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, networking is disabled upon recovery from suspend.
  Clicking "Enable Networking" on the menu from the notification icon
  has no effect. It requires network-manager to be restarted with
  `service network-manager restart`.

  I can't identify a pattern to the problem. I can suspend the computer
  for minutes or hours without it happening.

  I've not noticed it on other computers running 14.04 that I have, so
  it's probably limited to my this particular hardware.

  I didn't notice it on previous versions of Ubuntu on this hardware.
  However, due to the nature of the problem it will not be practical to
  bisect the kernel as I don't have a reliable method of reproducing the
  fault as of yet.

  My network devices are as follows (I use the wireless one only):

  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 02)
  Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 12 12:44:30 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-07-13 (60 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1  proto static 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  

[Touch-packages] [Bug 1589125] [NEW] WiFi does not work after about 1 in 4 suspends

[Phill]

Public bug reported:

Steps: Suspend, wait, resume, a few times.

The Network Manager applet shows WiFi is enabled and shows just one or a
handful of WiFi names, they don't include some that are known to be
available and in use on other computers.

Disabling and enabling WiFi does not fix the problem.

Disabling and enabling networking does not fix the problem.

Adding the following does not help:
/etc/pm/config.d/unload_modules 
SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"

Only workaround which works perfectly and instantly is to run:
sudo service network-manager restart

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun  4 18:18:50 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-30 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.43.1 dev wlp2s0  proto static  metric 600 
 169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
 192.168.43.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.43.89  
metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  HTC 
Portable Hotspot DF99  c29b59ba-b6ef-49db-b159-75ec21d3f436  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
  ----  
   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
  ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589125

Title:
  WiFi does not work after about 1 in 4  suspends

Status in network-manager package in Ubuntu:
  New

Bug description:
  Steps: Suspend, wait, resume, a few times.

  The Network Manager applet shows WiFi is enabled and shows just one or
  a handful of WiFi names, they don't include some that are known to be
  available and in use on other computers.

  Disabling and enabling WiFi does not fix the problem.

  Disabling and enabling networking does not fix the problem.

  Adding the following does not help:
  /etc/pm/config.d/unload_modules 
  SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"

  Only workaround which works perfectly and instantly is to run:
  sudo service network-manager restart

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 18:18:50 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.43.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.43.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.43.89  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
HTC Portable Hotspot DF99  c29b59ba-b6ef-49db-b159-75ec21d3f436  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
   lo  loopback  

[Touch-packages] [Bug 1549529] Re: The keyboard is still installed as US-English even if another language is selected during the installation

[Phill Whiteside]

Mathieu Trudel-Lapierre you are a little angel. 
This is not the 1st bug I've been following where your clean pair of eyes and 
attitude solves things quickly.
I'll say thank-you and break bug rules.

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

Title:
  The keyboard is still installed as US-English even if another language
  is selected during the installation

Status in casper package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  In Progress

Bug description:
  - Particularly serious in UEFI mode (when grub is the only boot
  loader).

  - Affects at least Lubuntu and Xubuntu

  - Affects not only Swedish, at least also French, probably all languages 
except US-English.
  -

  Workaround:

  If I install Swedish language in the live session *before* starting the 
installer, it works to get Swedish keyboard in the installed system.
  -

  This bug is reported from a system installed from Lubuntu Xenial
  alternate i386, but the corresponding desktop version is also
  affected. It is a rather new bug, that seems to have appeared at about
  the same time as the big problems with starting Ubiquity.

  Selecting another language in the installer looks the same in the
  alternate installer. But it looks different in the desktop installer.
  The locale is not pre-selected, you click on the world map, and you
  are asked if the selected keyboard is correct. The following window
  with alternative keyboards is empty. But that would be OK, if the
  installer would do, what it promises.

  After installation a lot of text is in the selected language, Swedish
  in my  case, for example the pulldown menus in lxterminal. But when I
  type, the US English keyboard is still there. I have to run

  setxkbmap se

  to get Swedish keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 25 00:21:47 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-24 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160224)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1532355] Re: package linux-image-4.3.0-5-generic 4.3.0-5.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Phill Whiteside]

Regarding UpgradeStatus: Upgraded to xenial on 2016-01-08 (0 days ago)

The kernel team have decided that we have the linux LTS kernel 4.4 in
our own 16.04 LTS. This makes perfect sense, my suggestion is to pull in
the 'unstable' ppa from the kernel team and install the 4.4 kernel. (do
not forget to un-install that ppa, else the kernel team will send you
all sorts of "not tested" kernels :D )

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

Title:
  package linux-image-4.3.0-5-generic 4.3.0-5.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Xenial:
  Triaged

Bug description:
  hung during the boot time , after many retries.. it came back to the
  login prompt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic i686
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sysadmin   2731 F pulseaudio
   /dev/snd/controlC1:  sysadmin   2731 F pulseaudio
  Date: Thu Jan  7 23:24:23 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=0aaeb789-574f-4293-b953-3f84f02fe743
  InstallationDate: Installed on 2015-08-22 (139 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  Lsusb:
   Bus 003 Device 031: ID 04f3:0111 Elan Microelectronics Corp. 
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=d3dfa265-52b0-4d9e-88c9-211a0272d159 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-5-generic 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-01-08 (0 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.asset.tag: 562268
  dmi.board.name: 085VV3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 562268
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn085VV3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1531824] Re: Xorg freeze

[Phill]

** Attachment added: "i915_error_state taken from the terminal during a freeze."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531824/+attachment/4545516/+files/i915_error_state

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It occurs several times a week, usually after several hours of suspend.

  It started a few months ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan  7 11:29:40 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
   virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
  InstallationDate: Installed on 2015-07-13 (177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan  7 11:11:57 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41085 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1531824] Re: Xorg freeze

[Phill]

** Attachment added: "Xorg.0.log taken from the terminal during a freeze."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531824/+attachment/4545515/+files/Xorg.0.log

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It occurs several times a week, usually after several hours of suspend.

  It started a few months ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan  7 11:29:40 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
   virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
  InstallationDate: Installed on 2015-07-13 (177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan  7 11:11:57 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41085 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1531824] [NEW] Xorg freeze

[Phill]

Public bug reported:

Symptoms:

* Video is frozen.

Observations:

* Mouse moves normally.
* There is no hard-disc activity.
* Once  minute or so the video will respond like it's doing so a frame at a 
time.
* Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a terminal.
* Text terminals work normally without any problems.
* Pressing ALT+F7 from a text terminal puts you into either black frozen screen 
or a frozen graphical display.
* Restarting LightDM doesn't resolve the problem, it shows the login screen and 
freezes.

When does it occur:

* More often than not on or immediately after resume from suspend.
* Occasionally, but not very often, during normal use.
* It occurs several times a week, usually after several hours of suspend.

It started a few months ago.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jan  7 11:29:40 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
 virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
   Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
InstallationDate: Installed on 2015-07-13 (177 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: System manufacturer V-P5G45
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: V-P5G45
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: V-P5G45
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jan  7 11:11:57 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   41085 
 vendor DEL
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It 

[Touch-packages] [Bug 1513448] [NEW] DB Update failed, database locked

[Phill]

Public bug reported:

Every day at around 0630 GMT I get output from the daily cron job:

```
Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
```

Reporting:

```
/etc/cron.daily/apt:
DB Update failed, database locked
```

I have unattended-upgrades installed and set up if that is of any
relevance.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.8
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Nov  5 11:56:40 2015
InstallationDate: Installed on 2014-11-28 (341 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  DB Update failed, database locked

Status in apt package in Ubuntu:
  New

Bug description:
  Every day at around 0630 GMT I get output from the daily cron job:

  ```
  Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  ```

  Reporting:

  ```
  /etc/cron.daily/apt:
  DB Update failed, database locked
  ```

  I have unattended-upgrades installed and set up if that is of any
  relevance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.8
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu Nov  5 11:56:40 2015
  InstallationDate: Installed on 2014-11-28 (341 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1341279] Re: Num Lock turned off when log-in page shown

[Phill]

I'm aware of the work configuration workaround detailed in your link but
I think the lightdm should respect the BIOS settings and not require
further configuration.

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

Title:
  Num Lock turned off when log-in page shown

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Whenever the log-in page shows, num lock is turned off.

  It's OK when unlocking, the state is preserved, it's just on start-up
  or after a log-out.

  To reproduce either turn on Num Lock then log-out, or set Num Lock on
  in the BIOS (as I do) and start the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 13 13:25:19 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-05-07 (431 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (76 days ago)

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

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

[Touch-packages] [Bug 1497742] [NEW] Clicks and noise over S/PDIF at 44100Hz

[Phill]

Public bug reported:

Bus 002 Device 005: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
Sound Device connected using S/PDIF optical out.

Playing audio at 44100Hz has clicks and a quiet cyclical noise at
roughly 5 cycles per second. The noise is like a really quiet shaker.
Clicking seems random and of varying intensity.

Affects multiple applications including Rhythmbox and Kodi. Even `aplay`
using a raw CD file copied to disk.

Higher playback rates of 48000Hz are clean and work fine with AC3 and
DTS encoded pass-through. I tested this in Kodi where you can pick the
playback rate with on-the-fly re-sampling. Same sound re-sampled and
played at 48000Hz plays flawlessly, everything at 44100Hz has the
problem.

Previous sound card (integrated) is fine. HDMI output is also fine.

Tried the `tsched=0` workaround, did not work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
Uname: Linux 3.16.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mediacentre   3018 F pulseaudio
 /dev/snd/controlC0:  mediacentre   3018 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Sun Sep 20 15:10:57 2015
InstallationDate: Installed on 2015-07-02 (80 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1681IG6 VER.109
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: Micro-Star International
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: Micro-Star International
dmi.chassis.version: Ver.001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1681IG6VER.109:bd07/21/2010:svnMicro-StarInternational:pnCalpellaplatform:pvrVer.001:rvnMicro-StarInternational:rnTobefilledbyO.E.M.:rvrVer.001:cvnMicro-StarInternational:ct9:cvrVer.001:
dmi.product.name: Calpella platform
dmi.product.version: Ver.001
dmi.sys.vendor: Micro-Star International
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2015-09-20T15:04:55.963646

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


** Tags: amd64 apport-bug trusty

** Description changed:

  Bus 002 Device 005: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
  Sound Device connected using S/PDIF optical out.
  
- Playing audio at 41000Hz has clicks and a quiet cyclical noise at
+ Playing audio at 44100Hz has clicks and a quiet cyclical noise at
  roughly 5 cycles per second. The noise is like a really quiet shaker.
  Clicking seems random and of varying intensity.
  
  Affects multiple applications including Rhythmbox and Kodi. Even `aplay`
  using a raw CD file copied to disk.
  
  Higher playback rates of 48000Hz are clean and work fine with AC3 and
  DTS encoded pass-through. I tested this in Kodi where you can pick the
  playback rate with on-the-fly re-sampling. Same sound re-sampled and
- played at 48000Hz plays flawlessly, everything at 41000Hz has the
+ played at 48000Hz plays flawlessly, everything at 44100Hz has the
  problem.
  
  Previous sound card (integrated) is fine. HDMI output is also fine.
  
  Tried the `tsched=0` workaround, did not work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  mediacentre   3018 F pulseaudio
-  /dev/snd/controlC0:  mediacentre   3018 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  mediacentre   3018 F pulseaudio
+  /dev/snd/controlC0:  mediacentre   3018 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Sep 20 15:10:57 2015
  InstallationDate: Installed on 2015-07-02 (80 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1681IG6 VER.109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: Micro-Star International
  dmi.board.version: 

[Touch-packages] [Bug 1495063] [NEW] Networking occasionally doesn't recover from suspend

[Phill]

Public bug reported:

Occasionally, networking is disabled upon recovery from suspend.
Clicking "Enable Networking" on the menu from the notification icon has
no effect. It requires network-manager to be restarted with `service
network-manager restart`.

I can't identify a pattern to the problem. I can suspend the computer
for minutes or hours without it happening.

I've not noticed it on other computers running 14.04 that I have, so
it's probably limited to my this particular hardware.

I didn't notice it on previous versions of Ubuntu on this hardware.
However, due to the nature of the problem it will not be practical to
bisect the kernel as I don't have a reliable method of reproducing the
fault as of yet.

My network devices are as follows (I use the wireless one only):

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 02)
Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
Uname: Linux 3.16.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep 12 12:44:30 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-07-13 (60 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
 default via 192.168.1.1 dev wlan1  proto static 
 192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.2  metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 HTC Portable Hotspot DF99 b31b75bc-5b76-4592-9b4a-d9d860ea34aa   
802-11-wireless   1441832180   Wed 09 Sep 2015 21:56:20 BST   yes   
no /org/freedesktop/NetworkManager/Settings/1
 TALKTALK-D069DC   700ea4cb-a660-479e-aa32-c00ad71e9064   
802-11-wireless   1442058263   Sat 12 Sep 2015 12:44:23 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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


** Tags: amd64 apport-bug trusty

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

Title:
  Networking occasionally doesn't recover from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, networking is disabled upon recovery from suspend.
  Clicking "Enable Networking" on the menu from the notification icon
  has no effect. It requires network-manager to be restarted with
  `service network-manager restart`.

  I can't identify a pattern to the problem. I can suspend the computer
  for minutes or hours without it happening.

  I've not noticed it on other computers running 14.04 that I have, so
  it's probably limited to my this particular hardware.

  I didn't notice it on previous versions of Ubuntu on this hardware.
  However, due to the nature of the problem it will not be practical to
  bisect the kernel as I don't have a reliable method of reproducing the
  fault as of yet.

  My network devices are as follows (I use the wireless one only):

  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 02)
  Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 12 12:44:30 2015
  IfupdownConfig:
   # interfaces(5) file used by 

[Touch-packages] [Bug 1489518] [NEW] Application windows opened in firefox, rather than being confined to the webapp container

[Phill]

Public bug reported:

Using the Google Calendar launcher and Google Docs launcher as installed
from Firefox.

In calendar, if your session expires and you are asked to log back in,
on clicking Sign Inthe calendar window is opened in firefox. If you
sign out, the webapp window shows Please wait while the calendar
you're trying to sign out of opens in firefox.

Similar experience with Google Docs. When you open a document it opens
in firefox, not the web application container.

I would expect the web-app container to confine Google Calendar (or
whatever domain you're in) to it's window, otherwise it defeats the
whole point.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: webapp-container 0.23+14.04.20140428-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
Uname: Linux 3.16.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Aug 27 16:06:40 2015
ExecutablePath: /usr/bin/webapp-container
InstallationDate: Installed on 2015-07-13 (44 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: webbrowser-app
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Application windows opened in firefox, rather than being confined to
  the webapp container

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Using the Google Calendar launcher and Google Docs launcher as
  installed from Firefox.

  In calendar, if your session expires and you are asked to log back in,
  on clicking Sign Inthe calendar window is opened in firefox. If you
  sign out, the webapp window shows Please wait while the calendar
  you're trying to sign out of opens in firefox.

  Similar experience with Google Docs. When you open a document it opens
  in firefox, not the web application container.

  I would expect the web-app container to confine Google Calendar (or
  whatever domain you're in) to it's window, otherwise it defeats the
  whole point.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: webapp-container 0.23+14.04.20140428-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 27 16:06:40 2015
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2015-07-13 (44 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1419944] [NEW] all information / editing for n-m vanishes at latest update

[Phill Whiteside]

Public bug reported:

I'm running 15.04 Lubuntu. The install and Live CD work fine, but when
applying the latest updates there is simply a greyed out 'No network
devices are available' (I'm typing this using WiFi on the machine it
says has no network devices), or VPN Connections.

Screen shot is at http://imgur.com/l9iQZ1A

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.16-0ubuntu1
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon Feb  9 19:17:01 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-02-06 (2 days ago)
InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141113)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
 NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  READONLY  DBUS-PATH  
ACTIVE  DEVICE  STATE  ACTIVE-PATH
nmcli-dev:
 Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
 DEVICE  TYPE  STATE  DBUS-PATH  CONNECTION  CON-UUID  CON-PATH
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug vivid

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

Title:
  all information / editing for n-m vanishes at latest update

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running 15.04 Lubuntu. The install and Live CD work fine, but when
  applying the latest updates there is simply a greyed out 'No network
  devices are available' (I'm typing this using WiFi on the machine it
  says has no network devices), or VPN Connections.

  Screen shot is at http://imgur.com/l9iQZ1A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Feb  9 19:17:01 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-02-06 (2 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141113)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  READONLY  
DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   DEVICE  TYPE  STATE  DBUS-PATH  CONNECTION  CON-UUID  CON-PATH
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1419944] Re: all information / editing for n-m vanishes at latest update

[Phill Whiteside]

Have just installed Setting up network-manager (0.9.10.0-4ubuntu6) ...
Now to reboot.

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

Title:
  all information / editing for n-m vanishes at latest update

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running 15.04 Lubuntu. The install and Live CD work fine, but when
  applying the latest updates there is simply a greyed out 'No network
  devices are available' (I'm typing this using WiFi on the machine it
  says has no network devices), or VPN Connections.

  Screen shot is at http://imgur.com/l9iQZ1A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Feb  9 19:17:01 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-02-06 (2 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141113)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  READONLY  
DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   DEVICE  TYPE  STATE  DBUS-PATH  CONNECTION  CON-UUID  CON-PATH
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1419944] Re: all information / editing for n-m vanishes at latest update

[Phill Whiteside]

Have just installed Setting up network-manager (0.9.10.0-4ubuntu6) ...
Now to reboot.

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

Title:
  all information / editing for n-m vanishes at latest update

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I'm running 15.04 Lubuntu. The install and Live CD work fine, but when
  applying the latest updates there is simply a greyed out 'No network
  devices are available' (I'm typing this using WiFi on the machine it
  says has no network devices), or VPN Connections.

  Screen shot is at http://imgur.com/l9iQZ1A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Feb  9 19:17:01 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-02-06 (2 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141113)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  READONLY  
DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   DEVICE  TYPE  STATE  DBUS-PATH  CONNECTION  CON-UUID  CON-PATH
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1419944] Re: all information / editing for n-m vanishes at latest update

[Phill Whiteside]

0.9.10.0-4ubuntu6 fixes this issue.

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

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

Title:
  all information / editing for n-m vanishes at latest update

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I'm running 15.04 Lubuntu. The install and Live CD work fine, but when
  applying the latest updates there is simply a greyed out 'No network
  devices are available' (I'm typing this using WiFi on the machine it
  says has no network devices), or VPN Connections.

  Screen shot is at http://imgur.com/l9iQZ1A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Feb  9 19:17:01 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-02-06 (2 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141113)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  READONLY  
DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   Warning: nmcli (0.9.10.0) and NetworkManager (0.9.8.8) versions don't match. 
Use --nocheck to suppress the warning.
   DEVICE  TYPE  STATE  DBUS-PATH  CONNECTION  CON-UUID  CON-PATH
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 835532] Re: lightdm does not keep numlock status on boot

[Phill]

** Tags added: trusty

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

Title:
  lightdm does not keep numlock status on boot

Status in LightDM GTK+ Greeter:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Oneiric:
  Won't Fix

Bug description:
  when booting or logging out, the numlock status 'on' is not kept for
  password or pin input via numpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  Date: Sat Aug 27 12:22:27 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-08-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/835532/+subscriptions

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

[Touch-packages] [Bug 1267679] Re: Copy dialog disappears, no way to bring it back.

[Phill]

Apparently same issue in 14.04, let me know what details you need and
how to get them.

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

Title:
  Copy dialog disappears, no way to bring it back.

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I was just copying many files to and from server at once, then copied
  over some files over that required merge, and clicking replace,
  replace... replace-all. Then I noticed that there was no longer any
  transfer window - not with Alt-tab and looking at all the Nautilus
  filebrowser windows, and not with Super+W windows overview. It had
  completely disappeared, however, the status-bar in the Unity panel to
  the left showed its status bar going on and eventually finishing.

  I try Super+W, Show copy dialog from rightclick, alt-tab, nothing will
  show the copy dialog, though copying works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan  9 14:52:19 2014
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b'851x737+599+170'
  InstallationDate: Installed on 2013-11-23 (47 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1380774] Re: debian-installer does not find kernel

[Phill Whiteside]

Brian, if wxl (release manager lubuntu) requests a respin of the
alternate ISO's will it pick up the new apt?

Regards,

Phill.

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

Title:
  debian-installer does not find kernel

Status in APT:
  Fix Released
Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Utopic:
  Triaged

Bug description:
  HOW TO REPRODUCE
  1. From http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/, 
boot any Lubuntu Alternate or Ubuntu Server image.
  2. Follow http://iso.qa.ubuntu.com/qatracker/testcases/1437/info test-case.

  EXPECTED BEHAVIOUR
  The installation to finish successfully.

  REAL BEHAVIOUR
  The installer can't find a kernel to install, as seen in the attached 
screen-shot.

  DistroRelease: Ubuntu 14.10
  Package: apt
  Architecture: i386, amd64, amd64+mac, ppc

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

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

[Touch-packages] [Bug 1380774] Re: debian-installer does not find kernel

[Phill Whiteside]

confirm on
http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82097/testcases

Well done guys and gals. A late show-stopper resolved :)

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

Title:
  debian-installer does not find kernel

Status in APT:
  Fix Released
Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Utopic:
  Fix Released

Bug description:
  HOW TO REPRODUCE
  1. From http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/, 
boot any Lubuntu Alternate or Ubuntu Server image.
  2. Follow http://iso.qa.ubuntu.com/qatracker/testcases/1437/info test-case.

  EXPECTED BEHAVIOUR
  The installation to finish successfully.

  REAL BEHAVIOUR
  The installer can't find a kernel to install, as seen in the attached 
screen-shot.

  DistroRelease: Ubuntu 14.10
  Package: apt
  Architecture: i386, amd64, amd64+mac, ppc

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

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

[Touch-packages] [Bug 1378423] Re: Virtualbox boots to black screen with daily

[Phill Whiteside]

VirtualBox 4.3.18 r96516 running on Lubuntu Utopic can install and run
Lubuntu Desktop amd64

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

Title:
  Virtualbox boots to black screen with daily

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Boot the daily image.

  Get a black screen.

  Go to tty1 - lightdm has started - running sudo service lightdm status
  echoes start/waiting

  Return to tty7 and the login dialogue has now appeared

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.344
  Date: Tue Oct  7 15:53:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1380774] Re: debian-installer does not find kernel

[Phill Whiteside]

Fixed upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765458

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

Title:
  debian-installer does not find kernel

Status in APT:
  Unknown
Status in “apt” package in Ubuntu:
  Confirmed
Status in “apt” source package in Utopic:
  Confirmed

Bug description:
  To reproduce boot the daily live utopic-alternate-i386 daily from
  10-13. Then continue through testcase 1437 to install to the entire
  disk it will create paritions, write to disk, and then try to load
  kernel and say it failed to load the kernel.

  Ubuntu 14.10 utopic unicorn i386

  the version of debian installer is
  debian-installer (20101020ubuntu348)

  I expected this to install a kernel and boot instead the installation
  could not find a kernel.

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

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

Re: [Touch-packages] [Bug 1380774] Re: debian-installer does not find kernel

[Phill Whiteside]

How long until incorporation and the server edition and lubuntu alternates
being re-spun?

Regards,
Phill.

On 17 October 2014 02:03, Bug Watch Updater 1380...@bugs.launchpad.net
wrote:

 ** Changed in: apt
Status: Unknown = Fix Released

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1380774

 Title:
   debian-installer does not find kernel

 Status in APT:
   Fix Released
 Status in apt package in Ubuntu:
   Triaged
 Status in apt source package in Utopic:
   Triaged

 Bug description:
   HOW TO REPRODUCE
   1. From 
 http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/, boot
 any Lubuntu Alternate or Ubuntu Server image.
   2. Follow http://iso.qa.ubuntu.com/qatracker/testcases/1437/info
 test-case.

   EXPECTED BEHAVIOUR
   The installation to finish successfully.

   REAL BEHAVIOUR
   The installer can't find a kernel to install, as seen in the attached
 screen-shot.

   DistroRelease: Ubuntu 14.10
   Package: apt
   Architecture: i386, amd64, amd64+mac, ppc

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



-- 
https://wiki.ubuntu.com/phillw

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

Title:
  debian-installer does not find kernel

Status in APT:
  Fix Released
Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Utopic:
  Triaged

Bug description:
  HOW TO REPRODUCE
  1. From http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/, 
boot any Lubuntu Alternate or Ubuntu Server image.
  2. Follow http://iso.qa.ubuntu.com/qatracker/testcases/1437/info test-case.

  EXPECTED BEHAVIOUR
  The installation to finish successfully.

  REAL BEHAVIOUR
  The installer can't find a kernel to install, as seen in the attached 
screen-shot.

  DistroRelease: Ubuntu 14.10
  Package: apt
  Architecture: i386, amd64, amd64+mac, ppc

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

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